How to install SAS Studio

how to install sas data integration studio and how much does sas studio cost and how to use sas studio online and how to learn sas di studio sas forecast studio
LexiWills Profile Pic
LexiWills,United Kingdom,Professional
Published Date:31-07-2017
Your Website URL(Optional)
Comment
® ™ SAS AppDev Studio 4.4 Eclipse Plug-ins User’s Guide ® SAS Documentation® ™ The correct bibliographic citation for this manual is as follows: SAS Institute Inc 2013. SAS AppDev Studio 4.4 Eclipse Plug-ins: User's Guide. Cary, NC: SAS Institute Inc. ® ™ SAS AppDev Studio 4.4 Eclipse Plug-ins: User's Guide Copyright © 2013, SAS Institute Inc., Cary, NC, USA All rights reserved. Produced in the United States of America. For a hardcopy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc. For a Web download or e-book:Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication. U.S. Government License Rights; Restricted Rights: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227–19 Commercial Computer Software- Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. Electronic book 1, December 2013 ® SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/ publishing or call 1-800-727-3228. ® SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.Contents What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Chapter 1 • Installing AppDev Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Installation and Post-Installation of SAS AppDev Studio . . . . . . . . . . . . . . . . . . . . . . . . 2 Accessibility Features of AppDev Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Chapter 2 • Overview of AppDev Studio 4.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 The SAS AppDev Studio 4.4 Eclipse Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Migrating Applications to AppDev Studio 4.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Chapter 3 • Projects, Profiles, and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 SAS Web Application Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Minimize the Number of Open Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Server Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Template Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Chapter 4 • Walk-Through for Web Infrastructure Platform Templates . . . . . . . . . . . . . . . . . . . 13 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Part I: Create the Project and the Application Metadata . . . . . . . . . . . . . . . . . . . . . . . . 14 Part II: Add the JDBC TableView Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Part III: Add a Welcome Page and Run the Application . . . . . . . . . . . . . . . . . . . . . . . . 21 Add a ReportViewer Servlet Template to the Project . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Add a SAS Stored Process Servlet Template to the Project . . . . . . . . . . . . . . . . . . . . . . 24 Input and Output Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Chapter 5 • Walk-Through for Data-Driven Project Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Create an Information Map Fixed Portlet from Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 The Portlet Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Chapter 6 • Template and Testing Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Files Added by the Metadata Creation Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Copying the Application Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Files Added by the Stored Process Java Client Template . . . . . . . . . . . . . . . . . . . . . . . 39 Files Added by the Stored Process Servlet Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Tomcat Configuration Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Deployment and Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Chapter 7 • Exporting Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Exporting Java and SAS Java Projects as a Set of JAR Files . . . . . . . . . . . . . . . . . . . . . 45 Exporting a SAS Web Application Project as a WAR File . . . . . . . . . . . . . . . . . . . . . . 46 Exporting a Project Using a Deployment Descriptor File . . . . . . . . . . . . . . . . . . . . . . . 47 Chapter 8 • Managing the JAR Files in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 The SAS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Opening the SAS Repository Properties Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Identifying Dependent JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51vi Contents Removing JAR Files from the Classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Changing the Order of JAR Files in the Classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Adding New JAR Files to the Classpath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Adding Dependent JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Specifying the Current Versions of JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Specifying Other JAR File Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Removing Version Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Reporting the Classpath JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Reporting JAR File Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Finding a Class in a JAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Changing Default Classes for SAS Java Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Chapter 9 • Using the SAS Editor Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Introduction to SAS Editor Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Accessing SAS Component API Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Adding Missing Import Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Attaching a SAS Model to a Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 SAS Snippets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Appendix 1 • Creating a SAS Web Application That Does Not Use the Web Infrastructure Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77vii What’s New About This Book This book has been updated to cover the first maintenance release for AppDev Studio 4.4. Significant differences between the initial release of AppDev Studio 4.4 and the first maintenance release for AppDev Studio 4.4 are noted.viii What’s New1 Chapter 1 Installing AppDev Studio Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Supported Versions of SAS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Install Eclipse 4.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Java Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installation and Post-Installation of SAS AppDev Studio . . . . . . . . . . . . . . . . . . . . . 2 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Post-Installation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Eclipse Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Accessibility Features of AppDev Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Installation Prerequisites Supported Versions of SAS Software To work correctly, a SAS AppDev Studio 4.4 project must match the maintenance level of the SAS 9.4 installation on which it is run. You need to apply a maintenance update to SAS AppDev Studio only if you are developing SAS projects for SAS 9.4 installations that have also had maintenance applied. The first maintenance release for SAS AppDev Studio 4.4 requires the first maintenance release for SAS 9.4. Install Eclipse 4.2.2 You must have Eclipse 4.2.2 installed before installing AppDev Studio 4.4. The AppDev Studio installation updates the Eclipse environment, and without a compatible version of Eclipse installed, you cannot install AppDev Studio. Install Eclipse by following these steps: 1. Create a working directory for Eclipse 4.2.2 (for example, C:\Eclipse422). 2. Download Eclipse 4.2.2. The supported release of Eclipse can be found on the SAS Third-party Downloads page located at http://support.sas.com/ resources/thirdpartysupport/v94/othersw.htmleclipse. 3. Extract the Eclipse archive to C:\Eclipse422. You should now have an eclipse directory inside your working directory (for example, C: \Eclipse422\eclipse). 2 Chapter 1 • Installing AppDev Studio Java Platform Requirements The SAS AppDev Studio 4.4 development bundle requires Java 2 Standard Edition (J2SE) 1.7.0_15 or higher for application and web application development, and execution of applications at run time. Note that AppDev Studio 4.4 has only been tested with the Oracle JRE. For supported web browsers and application servers, see the Third-Party Software for SAS 9.4 information at http://support.sas.com/resources/ thirdpartysupport/v94/index.html. Although the Eclipse IDE for Java EE Developers version 4.2.2 requires Java 6 at a minimum, SAS AppDev Studio 4.4 was tested with Java 7, and that version is recommended. See also http://www.eclipse.org/downloads/moreinfo/ jre.php. Installation and Post-Installation of SAS AppDev Studio Installation Instructions The SAS Deployment Wizard provides two ways to install AppDev Studio. The first is to install all the software that you need for development on a single machine. This plan installs and runs all three tiers on the same machine. This includes a scaled- down Business Intelligence (BI) server, a middle tier, and the AppDev Studio Eclipse Plug-ins. This type of installation is needed when the necessary servers, such as an Enterprise Business Intelligence (EBI) environment, are not available elsewhere. Running all three tiers on one machine is computationally intensive, so plan accordingly. With this plan you can also interact with existing remote tiers, which AppDev Studio makes easy using profiles. To select this type of installation, use the installation plan AppDev Studio, one machine. The second way is to install only the AppDev Studio Eclipse Plug-ins. This installation assumes that the necessary servers already exist. To select this type of installation, use the plan AppDev Studio, three machine, and install only the AppDev Studio Eclipse Plug-ins client. Follow these steps to begin a guided installation of AppDev Studio: 1. Start the SAS Deployment Wizard, select Install SAS Software, and click Next. 2. Select Perform a Planned Deployment and Install SAS Software. a. If you are installing all three tiers using the one machine plan, also select Configure SAS Software. b. If you are installing only the AppDev Studio Eclipse Plug-ins using the three machine plan, clear the Configure SAS Software check box. 3. Click Next. 4. Follow the on-screen instructions for installing the software.Installation and Post-Installation of SAS AppDev Studio 3 Post-Installation Configuration Before you start AppDev Studio, you must connect it to an Eclipse installation and then configure it. 1. Connect AppDev Studio to an Eclipse installation by following these steps: a. Start the SAS AppDev Studio Eclipse Configuration Tool (Start ð All Programs ð SAS ð SAS AppDev Studio 4.4 Eclipse Configuration Tool). b. In the Configuration Tool, select Eclipse ð Search and specify the top level of an Eclipse installation that you want to connect to AppDev Studio. The search is recursive, and a search of C:\Eclipse422\ will find the Eclipse installed at C:\Eclipse422\eclipse. If you have multiple Eclipse installations under one directory, point to the containing directory to find all the Eclipse installations under that directory. c. When the search is complete, select from the main Configuration Tool window the Eclipse installation that you want to connect to AppDev Studio, and then select Eclipse ð Connect. The connection process modifies the Eclipse installation to run AppDev Studio and can take several minutes. d. Exit the AppDev Studio Eclipse Configuration Tool. 2. Perform the New Workspace setup for each Eclipse workspace that you want to use. When you initially launch AppDev Studio within an empty Eclipse workspace, the New Workspace Setup cheat sheet starts and guides you through the following processes: • creating compatible Java runtimes • specifying Eclipse compiler options • setting the correct server run time for web application development • creating a BI Server Profile • creating a connection profile for the BI server • configuring a Tomcat server for testing To start this cheat sheet, launch the Eclipse attached to AppDev Studio. If the New Workspace Setup cheat sheet is not automatically displayed, select Help ð Cheat Sheets, and then expand SAS AppDev Studio and choose New Workspace Setup. Eclipse Memory Settings Because of a memory intensive Java EE task in the Eclipse Web Tools Platform, if you like to have several SAS Web Application projects open in your workspace, you should specify the maximum heap size to be at least 768 MB. On rare occasions this task can be triggered simultaneously on multiple worker threads in Eclipse. When this happens, Eclipse can run out of memory if the heap is not large enough, causing Eclipse to become unstable. To change the maximum heap size, modify the -Xmx setting in the eclipse.ini file for the Eclipse installation to which SAS AppDev Studio is connected. For example: -Xmx768m4 Chapter 1 • Installing AppDev Studio See Also “Minimize the Number of Open Projects” on page 8 Accessibility Features of AppDev Studio SAS AppDev Studio Eclipse 4.4 Plug-ins includes accessibility and compatibility features that improve the usability of the product for users with disabilities. These features are related to accessibility standards for electronic information technology that were adopted by the U.S. Government under Section 508 of the U.S. Rehabilitation Act of 1973, as amended. However, portions of the AppDev Studio interface are implemented using Java controls, and do not always comply with Section 508 guidelines. Notable exceptions include: • In some cases, screen-reading technology is unable to read text, read field labels in the correct order, or read only the text that is currently visible. • The color of the text in the Help window of the AppDev Studio Configuration Tool cannot be changed. • The portlet editor does not scroll vertically via keyboard controls. If you have questions or concerns about the accessibility of SAS products, send e-mail to accessibilitysas.com.5 Chapter 2 Overview of AppDev Studio 4.4 The SAS AppDev Studio 4.4 Eclipse Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Migrating Applications to AppDev Studio 4.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 The SAS AppDev Studio 4.4 Eclipse Plug-ins The SAS AppDev Studio 4.4 Eclipse Plug-ins support SAS application developers who use the open-source Eclipse IDE or a third-party IDE based on the Eclipse platform. Templates are provided that assist with the development of applications and web applications, including portlets, SAS Stored Processes, web-based reporting, and OLAP solutions. AppDev Studio 4.4 also enhances the standard Eclipse Java editor by integrating the SAS component API documentation into the Eclipse Help system. AppDev Studio 4.4 creates SAS web applications only for SAS 9.4, and those projects are now automatically configured to work with SAS 9.4 and the SAS Web Infrastructure Platform. New Features The first maintenance for SAS AppDev Studio 4.4 contains the following new features: • a new command for configuring a Tomcat server to use for testing SAS web applications. • new versions of the SAS Java Components and SAS Web Infrastructure Platform facets.6 Chapter 2 • Overview of AppDev Studio 4.4 Migrating Applications to AppDev Studio 4.4 AppDev Studio 4.4 cannot automatically migrate projects from previous versions. There are a few manual steps that you must perform. See the SAS AppDev Studio 4.4 Eclipse Plug-ins Migration Guide, Second Edition on the AppDev Studio Developer's Site (support.sas.com/rnd/appdev/) for information.7 Chapter 3 Projects, Profiles, and Templates SAS Web Application Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Minimize the Number of Open Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Server Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 BI Server Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Metadata Server Connection Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Template Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SAS DataBean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SAS Information Delivery Portal Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SAS Foundation Services Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 SAS Web Application Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SAS Web Infrastructure Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SAS Stored Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 SAS Web Application Projects SAS AppDev Studio web application development is as flexible as you need it to be. You can add to a project your code and third-party classes or tag libraries such as Apache Struts or JavaServer Faces. You can also add a JAR file of Java utility classes to a web application's \WEB-INF\lib directory. SAS Web Application Projects also support the SAS Java Components and the SAS Web Infrastructure Platform, which includes features such as the Logon Manager, themes, and SAS Platform Services. This support is achieved by adding to the project static content, Eclipse Web Tools Platform facets (www.eclipse.org/webtools/), and JAR files from the SAS Versioned Jar Repository. The static content can include configuration information, such as declarations in web.xml, other configuration files, and also file resources that are served by the web application. Facets are a feature of the Web Tools Platform, and define functionality that can be added to a project. Two facets are added to every SAS Web Application Project: the “SAS Java Components” facet and the “SAS Web Infrastructure Platform” facet. (The “SAS Java Components” facet is the SAS 9.4 equivalent of the “SAS Web Module with WIK” facet.) Facets are versioned, and the 9.4.0.0000 version of the SAS Java 8 Chapter 3 • Projects, Profiles, and Templates Components and SAS Web Infrastructure Platform facets corresponds to the initial release of SAS 9.4. AppDev Studio 4.4 for the first maintenance of SAS 9.4 uses version 9.4.1.0000 facets. You can view the facets of a SAS Web Application project by opening the project’s Properties and selecting Project Facets. In AppDev Studio 4.4, the SAS Web Application Project wizard always adds both facets to a new SAS Web Application project. Neither facet can be removed from the project. This means the SAS Web Application Project wizard cannot be used to create a SAS Web Application project if you do not want to include the “SAS Web Infrastructure Platform” facet. For a process to create a SAS Web Application project with only the “SAS Java Components” facet see “Creating a SAS Web Application That Does Not Use the Web Infrastructure Platform” on page 71. The SAS Versioned Jar Repository is attached to the project and adds the JAR files needed to support the two included facets. The JAR files added to the project by the SAS Versioned Jar Repository are also included in the application’s \WEB-INF\lib\ directory. You can view these included JAR files by opening the project’s SAS Repository. See “Opening the SAS Repository Properties Editor” on page 50. In addition to the SAS Repository, there is also a SAS Tooling library included in the build path of the project. This library includes a JAR file that provides classes that are needed at only build time, such as the annotation classes. Because these classes are not needed at run time, this JAR file is not included when the project is deployed or exported to a WAR file. Minimize the Number of Open Projects Because of the resources devoted to each open project, you should minimize the number of projects that you have open at one time. The fewer projects that you have open, the more responsive the development environment will be. To open an existing project, right-click the project in the Project Explorer, and select Open Project. Open projects are indicated with an open folder icon. To close an existing project, right-click the project and select Close Project. Server Profiles Introduction To avoid repeatedly entering host names, port numbers, and other settings for the numerous servers in a SAS BI Server installation, AppDev Studio 4.4 provides server profiles that you can define and then use to simplify development against a specific BI installation. There are two types of server profiles used by AppDev Studio 4.4: the BI Server Profile, and the Metadata Server Connection Profile. A BI Server Profile contains only enough information to uniquely identify a BI Server installation. The profile enables AppDev Studio 4.4 to communicate with an installation, and acquire additional information from it. Some tasks in AppDev Studio 4.4, such as adding template content to a project, let you select the BI Server Profile for the BI Server Templates 9 installation that you want to target. When you do this the settings needed to complete the task are obtained from the BI Server Profile, avoiding the need for manual entry. A Metadata Server Connection Profile is used to log in to the SAS Metadata Server for a particular BI Server installation. The Connection Profile contains credentials for the login and which BI Server Profile to use to connect to the associated Metadata Server. Because both profiles provide information and connection to required servers, you should create these profiles before starting a project. BI Server Profiles A BI Server Profile contains information about a particular BI Server installation. To create a new BI Server Profile, use the “Create a SAS BI Server Profile” cheat sheet: 1. From Eclipse, select Help ð Cheat Sheets. 2. Expand SAS AppDev Studio, select Create a SAS BI Server Profile, and then click OK. If the “Create a SAS BI Server Profile” cheat sheet has already been run, reset it by right-clicking the cheat sheet name and selecting Restart all tasks. Metadata Server Connection Profiles Connection Profiles help automate logging in to a SAS Metadata Server by managing the relationship between user credentials and SAS BI Server profile. You can connect via one Connection Profile at a time. To create a new Connection Profile, use the “Create a Connection Profile” cheat sheet: 1. From Eclipse, select Help ð Cheat Sheets. 2. Expand SAS AppDev Studio, select Create a Connection Profile, and then click OK. Templates The SAS templates consist of code that helps you rapidly develop SAS Web Applications or implement a particular feature. You can add these templates to a project when it is created, or add them to an existing project later. The SAS Web Application Examples templates provide you with code and resources in various states of completion. The amount of work needed to make the example functional depends on the template. Some templates create examples that are ready to run using only the information provided when you add the template. Although this User's Guide focuses on SAS Web Applications created in AppDev Studio 4.4 or migrated from a previous version, non-Web application projects (SAS Java Projects and Eclipse Web Tools Dynamic Web projects) are also supported in AppDev Studio 4.4. If you add a SAS Web Application Examples template to an Eclipse Dynamic Web project, the project is converted to a SAS Web Application Project.10 Chapter 3 • Projects, Profiles, and Templates Template Descriptions The SAS AppDev Studio 4.4 templates by category. SAS DataBean SAS JDBC Databean Class creates a JDBC Java data class that provides access to a data table. SAS Information Delivery Portal Portlets DisplayURL Portlet displays the contents of an HTML page. The URL of the page is specified at run time. Editable Portlet displays the contents of a string. The string is specified at run time. Information Map Fixed Portlet displays the contents of an Information Map. The Information Map is specified at design time and displays the map at run time. Information Map Runtime Portlet displays a list of Information Maps defined on your server and displays the selected map. JSP Portlet displays the output of a single JSP that is contained in your project. Remote Portlet displays the contents of a remote page inside a frame. The URL of the remote page is specified at design time. Stored Process List Portlet displays a list of SAS Stored Processes and executes the selected stored processes. The list is specified at design time. Stored Process Single Portlet displays the results of executing a single SAS Stored Process. The stored process is specified at design time. SAS Foundation Services Support Context Listener For Local Services creates a ServletContextListener class for deploying and destroying local SAS Foundation Services. JAAS Login Configuration File creates a login configuration file for JAAS authentication using a SAS Metadata Server. Log4J Logging Configuration adds a simple Log4J logging configuration file to the web application.Template Descriptions 11 SAS Web Application Examples All the SAS Web Application Examples templates, listed below, use the SAS Web Infrastructure Platform (SAS WIP). For each template listed there is a corresponding template available in the AppDev Studio interface that uses the legacy SAS Foundation Services (SAS FS). Information Map Default Servlet (uses SAS WIP) creates a Default Information Map based on the Model 2 (MVC) Web Application Architecture. Both a JSP page and a Java file containing the servlet's class are created. Information Map OLAPTableView Servlet (uses SAS WIP) creates an Information Map OLAPTableView example based on the Model 2 (MVC) Web Application Architecture for use with OLAP data. Both a JSP page containing OLAPTableView custom tags and a Java file containing the servlet's class are created. Information Map TableView Servlet (uses SAS WIP) creates an Information Map TableView example based on the Model 2 (MVC) Web Application Architecture for use with relational data. Both a JSP page containing TableView custom tags and a Java file containing the servlet's class are created. JDBC Default Servlet (uses SAS WIP) creates a Default JDBC example based on the Model 2 (MVC) Web Application Architecture. Both a JSP page and a Java file containing the servlet's class are created. JDBC TableView Servlet (uses SAS WIP) creates a JDBC TableView example based on the Model 2 (MVC) web application architecture. Both a JSP page containing TableView custom tags and a Java file containing the servlet's class are created. Report Viewer Servlet (uses SAS Web Report Viewer and SAS WIP) creates a report viewer example that uses a servlet to access relational and OLAP data. The selected report is viewed in SAS Web Report Viewer. A Java file containing the servlet's class is created. SAS Stored Process Servlet (uses SAS WIP) creates a stored process example that uses a servlet to display the output of a stored process. SAS Web Infrastructure Platform Support Examples Welcome Page adds a JSP page that lists the SAS Web Applications Examples added to the project. SAS Web Infrastructure Platform Applications Metadata Creation creates support files for creating and deploying Application metadata that is required by the SAS Web Infrastructure Platform. Log4J Logging Configuration adds a simple Log4J logging configuration file to the web application.12 Chapter 3 • Projects, Profiles, and Templates SAS Stored Process Java Client for executing a SAS Stored Process creates a simple Java client that executes a SAS Stored Process and writes the results to a file.

Advise: Why You Wasting Money in Costly SEO Tools, Use World's Best Free SEO Tool Ubersuggest.