About Installing Third-Party Products

The SAS desktop client applications and majority of Java applications are supported on Microsoft Windows systems only. The exception is SAS Management Console, which also runs on several UNIX platforms. All of the Java applications require the Java Runtime Environment (JRE), which includes a Java Virtual Machine (JVM) that executes the application and a set of standard Java class libraries. The SAS Deployment Wizard will install the default version of the 32-bit JRE with which SAS has been tested. If a different supported version of the JRE is required, it can be obtained from the appropriate vendor's Web site. Links to the appropriate JRE vendor's Web site can be found on the SAS 9.3 third-party support site located at http://support.sas.com/resources/thirdpartysupport/v93.
During a first-time SAS 9.3 deployment, the SAS Deployment Wizard prompts you for the version of the JRE that you want to use with the SAS Java applications. Your options are to have the deployment wizard install a JRE that SAS has certified to run with SAS 9.3, or to point to a JRE that you have already installed. (In most situations where you are updating or adding a product to SAS 9.3, the deployment wizard does not prompt you for a JRE. However, you can override this behavior. For more information, see Specify a Different JRE.)
On z/OS only, your options are to point to a JRE that you have already installed, or install your software without a JRE.
In most cases, before you can install and configure a SAS 9.3 middle tier, you must have installed a Web application server and a 64-bit JDK that is supported by SAS. (If you are using WebSphere Application Server, then the JDK is supplied when you install WebSphere Application Server.) SAS identifies the supported software versions at: http://support.sas.com/resources/thirdpartysupport/v93.
When you run the deployment wizard on the middle-tier machine, it prompts you for paths to these third-party software products, checks to make sure that the software versions are supported by SAS, and does not allow you to proceed with the software installation unless the software is installed. However, some sites separate SAS administration from Web application server administration, and it might not be possible to run the deployment wizard on the middle-tier machine.
For the sites that do not permit running the deployment wizard on the middle-tier machine, the wizard enables the SAS administrator to create a middle-tier configuration on a machine that does not contain a Web application server. After the configuration is complete, the SAS administrator compresses the Web tier configuration and hands it off to his Web administrator counterpart to deploy on the target Web application server machine. For more information, see Building a Web Application Server Configuration for Deployment on Another Machine.
The Web application server administrator can then choose to use configuration scripting tools provided by SAS to configure the middle-tier environment on the target machine, or the administrator can configure the middle-tier manually. For more information about the configuration scripting tools, see SAS Configuration Scripting Tools in SAS Intelligence Platform: Middle-Tier Administration Guide.
Note: SAS 9.3 supports JRockit as an alternative JDK for WebLogic. For more information, see http://support.sas.com/resources/thirdpartysupport/v93/jdks.html.
Use the manufacturer's distribution package to install the JDK. Make sure that you have a properly defined Java environment. (On Windows, a reboot of the machine might be required.) Open a DOS command prompt on Windows, or a console on UNIX, and at the operating system prompt, enter the following command to validate the Java environment and return the version information (including bitness) for the installed package: java -version.
For more information about configuration steps for your Web application server, go to http://support.sas.com/resources/thirdpartysupport/v93/appservers/index.html and select the product name of your Web application server.