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.
    1. If you are installing all three tiers using the one machine plan, also select Configure SAS Software.
    2. 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.

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:
    1. Start the SAS AppDev Studio Eclipse Configuration Tool (Startthen selectAll Programsthen selectSASthen selectSAS AppDev Studio 4.4 Eclipse Configuration Tool).
    2. In the Configuration Tool, select Eclipsethen selectSearch 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.
    3. 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 Eclipsethen selectConnect. The connection process modifies the Eclipse installation to run AppDev Studio and can take several minutes.
    4. 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 Helpthen selectCheat 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:
-Xmx768m

See Also

Minimize the Number of Open Projects
Copyright © SAS Institute Inc. All rights reserved.