Installation Instructions: SAS Web Infrastructure Kit
Release 1.0

Introduction

This document provides instructions for installing Version 1.0 of the SAS Web Infrastructure Kit.

Personal or Advanced Installation vs. Installation Using the Software Index

Personal or Advanced installation: A Personal or Advanced installation uses information from a planning document as input to the SAS Software Navigator and the SAS Configuration Wizard. You can use one of the standard plans that are provided with the wizard, or you can use your own customized plan that has been stored in a SAS project directory. For a Personal or Advanced installation, you should follow the customized instructions that are generated based on your plan. The customized instructions will direct you to specific steps in this document as needed. For more information about Personal and Advanced installations, refer to the SAS 9.1.3 Intelligence Platform: Installation Guide on the SAS Web site.

Installation Using the Software Index: An installation using the Software Index is performed without the use of plans and SAS project directories. For this type of installation, you should follow all of the pre-installation, installation, and post-installation steps that are provided in this document.

Single Machine Installation vs. Distributed Installation

The Web applications that are included in the SAS Web Infrastructure Kit are designed to operate in a tiered environment using various servers, each of which can run on a separate machine. To help you get the applications up and running, the steps in this procedure will result in an initial installation in which all of the required servers and applications are running in the same container on the same machine.

If either the SAS Stored Process Web application or the SAS Web Report Viewer application will be running in a different container in your environment, then you must change your configuration files to enable the portal Web application to access the remote application. For instructions, see Redistributing Applications and Servers in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site. To expedite the installation process, you should read these instructions and make the configuration file changes before you run the configuration scripts in Step 6.

You can also use these instructions to move applications and servers after you have successfully installed the SAS Web Infrastructure Kit on a single machine. However, you will then need to rerun the configuration script (Step 6) and redeploy the Web applications (Step 11).

Limited User vs. Multiple User Environments

The default installation process configures the software to support only a limited number of users. If a large number of users will be accessing the portal Web application (and, in turn, the SAS servers), then additional performance tuning is required. Step 8, Step 10, and Step 15 in this document provide references to additional information that you can use to tune the SAS servers and the middle tier after your software is up and running.

Upgrading an Existing SAS 9 Installation

In order to upgrade an existing SAS 9 installation with the latest software, you must follow the upgrade instructions in the Technical Support paper "Upgrading a SASŪ 9.1 or 9.1.2 System SASŪ 9.1.3 System".

Application Components

The installation procedure for the SAS Web Infrastructure Kit installs the following application components:

SAS Portal Web Application Shell
a portal-like Web application shell that is used by other SAS Web applications (Note: For full portal capabilities, you must install the SAS Information Delivery Portal.)

SAS Stored Process Web Application
a Web application that enables stored processes to be run from the Web

SAS Services Application
a command line application that manages services that are shared by SAS applications

SAS Documentation Web Application
a Web application that manages SAS documentation

SAS Preferences Web Application
a Web application that manages user preferences for the portal Web application and for SAS solutions that are delivered through the portal

SAS Themes Web Application
a Web application that contains definitions for themes that are used by the portal Web application and by SAS solutions that are delivered through the portal

Installation Using the Software Index:
Installing the SAS Web Infrastructure Kit

If you use the Software Index to install the SAS Web Infrastructure Kit, then you must follow these pre-installation, installation, and post-installation steps:

Pre-Installation:

  1. Install the Java Runtime Environment.
  2. Install the required SAS Software.
  3. Install a servlet container.
  4. (Optional) Install a WebDAV server.

Installation:

  1. Run the installation program.

Post-Installation:

  1. Run the configuration script.
  2. Configure the SAS Metadata Server, create a repository, and create required users and groups.
  3. Install metadata.
  4. Set up the SAS Object Spawner.
  5. Prepare the servlet container environment.
  6. Deploy Web application files into the servlet container.
  7. Make graph applets available.
  8. Set up the SAS Services application.
  9. Start the servers.
  10. Tune the servlet container.
  11. Access the Web Infrastructure Kit's Web applications.

Pre-Installation Steps


Step 1: Install the Java Runtime Environment

The current release of the SAS Web Infrastructure Kit requires the Java Runtime Environment (JRE) for installation and configuration. The servlet container where the Web applications will be deployed will require the Java 2 Software Development Kit (SDK), Standard Edition.

For the most recent list of third-party software versions and patches that are required for installation and configuration of SAS components, see Third-Party Software Downloads on the SAS Web site.

Note: The version of the JRE required for installation and configuration is different than the version of the JDK required to run the Web applications.


Step 2: Install the Required SAS Software

The current version of the SAS Web Infrastructure Kit requires the following SAS software:

Version 9.1 of the SAS System
At a minimum, you must install Base SAS and SAS Integration Technologies.

SAS Management Console
SAS Management Console enables you to create and manage your SAS Metadata Repository.

SAS Foundation Services
SAS Foundation Services includes a plug-in for SAS Management Console which enables you to manage SAS services and software used to run the SAS Services application as a Windows service.


Step 3: Install a Servlet Container

In order to run the servlets and JavaServer Pages (JSPs) that are included in the SAS Web Infrastructure Kit, you must install a supported servlet container. A servlet container provides a runtime environment that supports concurrency, life cycle management, deployment, and other services for servlets and JSPs.

For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.

Note: If the servlet container that you are using does not include the required version of the J2SDK, you must install it at this time.

Restriction: The name of the directory in which you install the servlet container cannot contain spaces. The remote method invocation (RMI) server that is started by the SAS Services application requires the servlet container to be installed in a directory that does not contain spaces.

Installation Tips: Installation Tips for specific servlet containers are provided throughout this document. These tips, which are enclosed in boxes, will help you get the SAS Web Infrastructure Kit up and running quickly. These tips are based on the version of the servlet container that was required at the time this document was written.

Windows Systems

Installation Tips for Apache Tomcat 4.1 on Windows Systems
  1. Do not install Tomcat into a path name that includes spaces. If you use the Tomcat Windows installer, then do not choose the default directory (C:\Program Files\Apache Tomcat 4.0). Instead, we recommend installing into the path C:\Tomcat4.1. The RMI server that is started by the SAS Services application requires the servlet container to be installed in a directory that does not contain spaces.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. If you install Tomcat as a service, then you will need to customize the service to enable security and to set Java Virtual Machine (JVM) system variables. Security is enabled with the following options:

-Djava.security.manager
-Djava.security.policy=CATALINA_HOME%/conf/catalina.policy

The JVM system variables that are used to tune performance must be set in the CATALINA_OPTS environment variable. See Step 10 for details on setting the recommended JVM system variables.

Use the following command to install the Tomcat service (if you copy and paste this code, then you must remove the line breaks):

%CATALINA_HOME%/bin/tomcat.exe
 -install Apache-Catalina
 %JAVA_HOME%/jre/bin/server/jvm.dll
 -Djava.security.manager
 -Djava.security.policy=
     CATALINA_HOME%/conf/catalina.policy
 -Djava.class.path=
     %CATALINA_HOME%/bin/bootstrap.jar;
     %JAVA_HOME%/lib/tools.jar
 -Dcatalina.home=%CATALINA_HOME% %CATALINA_OPTS%
 -Xrs
 -start org.apache.catalina.startup.BootstrapService
 -params start
 -stop org.apache.catalina.startup.BootstrapService
 -params stop
 -out %CATALINA_HOME%/logs/stdout.log
 -err %CATALINA_HOME%/logs/stderr.log
Use the following command to uninstall the Tomcat service:
%CATALINA_HOME%/bin/tomcat.exe -uninstall Apache-Catalina
  1. If you use the Apache Tomcat servlet container with the Apache HTTP server, then you will need to use a connector in order to surface the Web Infrastructure Kit servlets through the HTTP server. At a minimum, you will need to mount the following servlets:
    • /Portal
    • /SASDoc
    • /SASStoredProcess
    • /SASPreferences
    • /SASTheme_default
    Depending on your setup, you might also need to mount:
    • /sasweb
    • /SASWebReportStudio
    • /SASWebReportViewer

Installation Tips for BEA WebLogic 8.1 on Windows Systems
  1. BEA recommends that you install WebLogic into the path C:\bea and that you set the product installation directory to C:\bea\weblogic81. The RMI server that is started by the SAS Services application requires the servlet container to be installed in a directory that does not contain spaces.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. Make sure that you configure WebLogic to use one of the supported J2SDK versions that is specified at the beginning of Step 3.
  1. Run the BEA WebLogic Configuration Wizard to create a new server domain, using commands similar to the following:

    cd C:\bea\weblogic81\common\bin
    config.cmd
    

    As you run the wizard, you can use the following responses as a guide:

    1. Select Create a new WebLogic configuration, and then select the Next button.

    2. Select Basic WebLogic Server Domain, and then select the Next button.

    3. Select Custom to create a custom installation, and then select the Next button.

    4. Select the Next button to use the default values for the Administration Server.

    5. Select Yes to create a Managed Server, and then select the Next button.

    6. Select the Add button to create a Managed Server definition, and then enter a Name and Listen Port for that server (for example, managedServer_1 and 7100). Select the Next button.

      The listen port that you specify on this screen must be also be specified as the Container Port on the Common Web Infrastructure Configuration screen of the Web Infrastructure Kit installation program. You will run the Web Infrastructure Kit installation program in Step 5.

    7. Select the Next button to skip cluster configuration.

    8. Select the Next button to skip machine configuration.

    9. Select No to skip JDBC configuration, and then select the Next button.

    10. Select No to skip JMS configuration, and then select the Next button.

    11. Add a configure username and password (for example weblogic and Weblogic123), and then select the Next button.

    12. Configure the Windows options as needed, and then select the Next button.

    13. Optionally, configure the Start Menu Entries as needed, and then select the Next button.

    14. Select Production Mode, select Other Java SDK and browse for the required version of the Java SDK, and then select the Next button.

    15. Select Create to create the configuration in the default location, and then select the Done button. The default location is C:\bea\user_projects\domains\mydomain.

  1. If you have the WebLogic Node Manager installed and running, you can start the managed server from the WebLogic console. If not, you must edit the startManagedWebLogic.cmd script located in the domain's default location. In this file, change the SERVER_NAME environment variable to the Managed Server name that you specified in Step c above.

Installation Tips for IBM WebSphere 6.1 on Windows Systems
  1. Although you can install IBM WebSphere in any location, these instructions assume that you have installed it into C:\apps\WebSphere.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. Use the WebSphere Administrative Console to configure the WebSphere Application Server, as follows:

    1. Start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Global Security wizard (for example, Security -> Secure administration, applications, and infrastructure).

    5. Enable Java 2 security by selecting the Use Java 2 security to restrict application access to local resources check box.

    6. Save the changes by selecting the Apply button, then selecting the Save link in the Save directly to the master configuration dialog.

Unix Systems

Installation Tips for Apache Tomcat 4.1 on Unix Systems
  1. Although you can install Tomcat in any location, these instructions assume that you have installed it into /usr/local/Tomcat4.1.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. If you use the Tomcat servlet container with the Apache HTTP server, then you will need to use a connector to surface the Web Infrastructure Kit servlets through the HTTP server. At a minimum, you will need to mount the following servlets:
    • /Portal
    • /SASDoc
    • /SASStoredProcess
    • /SASPreferences
    • /SASTheme_default
    Depending on your setup, you might also need to mount:
    • /sasweb
    • /SASWebReportStudio
    • /SASWebReportViewer

Installation Tips for BEA WebLogic 8.1 on Unix Systems
  1. Although you can install BEA WebLogic in any location, these instructions assume that you have installed it into /usr/local/bea and that you have set the product installation directory to /usr/local/bea/weblogic81.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. Make sure to configure WebLogic to use one of the supported J2SDK versions that is specified at the beginning of Step 3.
  1. Run the BEA WebLogic Configuration Wizard to create a new server domain, using commands similar to the following:
    cd /usr/local/bea/weblogic81/common/bin
    config.sh
    

    As you run the wizard, you can use the following responses as a guide:

    1. Select Create a new WebLogic configuration, and then select the Next button.

    2. Select Basic WebLogic Server Domain, and then select the Next button.

    3. Select Custom to create a custom installation, and then select the Next button.

    4. Select the Next button to use the default values for the Administration Server.

    5. Select Yes to create a Managed Server, and then select the Next button.

    6. Select the Add button to create a Managed Server definition, and then enter a Name and Listen Port for that server (for example, managedServer_1 and 7100). Select the Next button.

      The listen port that you specify on this screen must be also be specified as the Container Port on the Common Web Infrastructure Configuration screen of the Web Infrastructure Kit installation program. You will run the Web Infrastructure Kit installation program in Step 5.

    7. Select the Next button to skip cluster configuration.

    8. Select the Next button to skip machine configuration.

    9. Select No to skip JDBC configuration, and then select the Next button.

    10. Select No to skip JMS configuration, and then select the Next button.

    11. Add a configure username and password (for example weblogic and Weblogic123), and then select the Next button.

    12. Select Production Mode, select Other Java SDK and browse for the required version of the Java SDK, and then select the Next button.

    13. Select Create to create the configuration in the default location, and then select the Done button. The default location is /usr/local/bea/user_projects/domains/mydomain.

  1. If you have the WebLogic Node Manager installed and running, you can start the managed server from the WebLogic console. If not, you must edit the startManagedWebLogic.sh script located in the domain's default location. In this file, change the SERVER_NAME environment variable to the Managed Server name that you specified in Step c above.
  1. If you are installing WebLogic 8.1 on AIX: You must set the following JVM option to work around a configuration bug (if you copy and paste this code, then you must remove the line break):
    -Dlogin.configuration.provider=
       com.ibm.security.auth.login.ConfigFile
    
    If you have the WebLogic Node Manager installed and running, you can set this option in the managed server from the WebLogic console. If not, you must edit the startManagedWebLogic.sh script located in the domain's default location.

Installation Tips for IBM WebSphere 6.1 on Unix Systems
  1. Although you can install IBM WebSphere in any location, these instructions assume that you have installed it into /usr/local/websphere.

    Note: For the most recent list of third-party software versions and patches that are required for running SAS components, see Third-Party Software Downloads on the SAS Web site. It is strongly recommended that you read this information before installing the required third-party software.
  1. Use the WebSphere Administrative Console to configure the WebSphere Application Server, as follows:

    1. Start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Global Security wizard (for example, Security -> Secure administration, applications, and infrastructure).

    5. Enable Java 2 security by selecting the Use Java 2 security to restrict application access to local resources check box.

    6. Save the changes by selecting the Apply button, then selecting the Save link in the Save directly to the master configuration dialog.


Step 4: (Optional) Install a WebDAV Server

The next step is to install a WebDAV server according to the instructions provided by your server vendor. This step is optional.

If you choose to install the Xythos WebFile Server, then the following capabilities of the SAS Web Infrastructure Kit will be enabled. If you do not install the Xythos WebFile Server, then these capabilities will be disabled.

Xythos WebFile Server

The Xythos WebFile Server installation process will create the directory structure that SAS software requires in order to store content and user definitions. The WFSInstaller script will display the prompt Enter the path to the user area. The recommended default value for this field is /sasdav/Users. If you enter this default value, then the WFSInstaller2 script (which executes after the WFSInstaller script finishes) will create a top-level directory called /sasdav on the server. This directory is referred to as the base path root. The WFSInstaller2 script will also create a /sasdav/Users directory to store each user's personal content.

Note: The base path root that you specify during the Xythos WebFile Server installation must match the value that you specify during the SAS Web Infrastructure Kit installation in Step 5.


Installation Step


Step 5: Run the Installation Program

Run the installation program that is provided on the distribution CD. You must run this program on the same machine that will run the servlet container.

As the installation program executes, answer the prompts to provide the requested information about your installation environment. Using this information, the installation program will create an installation properties file that contains name and value pairs. This file, which is called install.properties, will be located in the PortalConfigure folder of the setup directory.

Note: Since you will need to enter some of the values from the install.properties file in later steps of the installation process, you might want to print a copy of this file for reference.

If you are performing a Personal or Advanced installation, then continue with the SAS Software Navigator after the installation program has completed successfully.

If you are using the Software Index to perform the installation, and if you plan to install the SAS Information Delivery Portal Web Application directly after the SAS Web Infrastructure Kit, then you can stop here. To streamline the installation process, it is recommended that you install the SAS Information Delivery Portal Web Application before you complete the post-installation steps that begin with Step 6.

If you are performing a Personal or Advanced installation and you do not plan to install the SAS Information Delivery Portal Web Application in the immediate future, then you should continue with Step 6.

Structure of the Setup Directory

The installation program copies the components of the SAS Web Infrastructure Kit to your computer in the path that you specify. On Windows systems, the default installation location is C:\Program Files\SAS\Web\Portal2.0.1. On Unix systems, the default installation location is /usr/local/SAS/Web/Portal2.0.1. In this document, the Portal2.0.1 directory is referred to as the setup directory.

The setup directory is organized into the following subdirectories:

_uninstIDP
if installed, contains the procedure and data for uninstalling the SAS Information Delivery Portal

_uninstWIK
contains the procedure and data for uninstalling the SAS Web Infrastructure Kit

DeployedPortlets
contains portlets, in the form of portlet archive (PAR) files, that are used by the portal Web application shell

OMR
contains SAS program (.sas) files which are used to load the required and demonstration metadata onto the SAS Metadata Server

Portal
contains the portal Web application shell that will be installed in your servlet container

PortalConfigure
contains the install.properties file and the Web infrastructure configuration tool

Samples
contains sample code

SASPreferences
contains the SAS Preferences Web application

SASServices
contains the SAS Services application

SASServicesConfig
contains files that are used to configure the SAS Java Foundation Services

SASStoredProcess
contains the SAS Stored Process Web application that will be installed in your servlet container

sasweb
contains the SAS graph applets that will be installed in your servlet container

themes
contains exploded versions of the SAS theme WAR files

Tools
contains a tool that you can use to remove the metadata that is used by the portal Web application shell


Post-Installation Steps


Note: If you are using the Software Index to perform the installation, and if you plan to install the SAS Information Delivery Portal Web Application directly after the SAS Web Infrastructure Kit: To streamline the installation process, it is recommended that you install the SAS Information Delivery Portal Web Application before you complete the following post-installation steps.

Step 6: Run the Configuration Script

When you are finished running the installation program, you must run a configuration script which does the following:

Follow these steps to run the configuration script:

  1. If either the SAS Stored Process Web application or the SAS Web Report Viewer application will be running in a different container in your environment, then you must change your configuration files to enable the portal Web application to access the remote application. For instructions, see Redistributing Applications and Servers in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site. To expedite the installation process, you should read these instructions and make the configuration file changes before you run the configuration script.

    You can also redistribute applications and servers after you have successfully installed the SAS Web Infrastructure Kit on a single machine. However, you will then need to rerun the configuration script (Step 6-d) and redeploy the Web applications (Step 11).

  2. In the following situations, you must update the install.properties file before you run the configuration script. The install.properties file can be found in the PortalConfigure subdirectory of the setup directory. The required changes are as follows:

    • If you choose to run a WebDAV Server but you choose not to run the Xythos WebFile Server: Add the following line to the install.properties file before you run the configuration script:

      $DAV_XYTHOS$=false
      

      The $DAV_XYTHOS$=false setting disables the WebDAV capabilities that require the use of the Xythos WebFile Server.

    • If you choose not to run a WebDAV Server: Add the following lines to the install.properties file before you run the configuration script:

      $DAV_AUTOCONNECT$=false
      $DAV_XYTHOS$=false
      

      The $DAV_AUTOCONNECT$=false setting prevents the Web applications that are included in the SAS Web Infrastructure Kit from automatically trying to connect to the WebDAV server. The $DAV_XYTHOS$=false setting disables WebDAV capabilities that are supported only with the Xythos WebFile Server.

  3. (Optional) You can update the install.properties file to specify the application name that is to appear in the banner of the portal Web application. As a default, the application name "SAS Portal" is displayed in the banner.

    If you want to display a different application name, then add the following property to the install.properties file before you run the configuration script:

    $NAME_IN_BANNER$=Application Name
    
    where Application Name is the name that you want to display.

  4. Run the configuration script, as follows:

    • On Windows systems: Go to the setup directory and run configure_wik.bat.

    • On Unix systems: Go to the setup directory and run configure_wik.sh.

    Note: On both Windows and Unix systems, the Java executable must be present in your path.

    The configuration script configures the Web applications, copies local and remote services deployment files and configuration files to the appropriate directory, and creates WAR files.


Step 7: Configure the SAS Metadata Server, Create a Repository, and Create Required Users and Groups

The SAS Web Infrastructure Kit uses the SAS Metadata Server, which is a repository for maintaining metadata that is used by SAS products throughout the enterprise. The form of user authentication that you choose to use (host authentication, LDAP authentication, Microsoft Active Directory authentication, or Web server authentication) influences how the SAS Metadata Server is configured.

These instructions apply to a SAS Metadata Server that is configured for host authentication. If your metadata server is configured for another type of authentication, refer to one of the following sections of the SAS Web Infrastructure Kit: Administrator's Guide:

If your metadata server is configured for host authentication, the following instructions will help you configure the SAS Metadata Server for the Web applications that are included in the SAS Web Infrastructure Kit:

  1. For the operating system of the machine where the SAS Metadata Server is installed, set up the necessary accounts for the required and demonstration users. Use the appropriate procedure for your operating system to add the following user accounts to the machine:

    • SAS (required for Unix and z/OS only): Add an individual account for the SAS user and a group account for the SAS group. For example, specify a user ID such as sas and a password such as Admin123, and specify the group ID sas (or sasgrp on z/OS) and the password Admin123. (Note: You did not enter information for this user and group when you ran the installation program).

      This user identity should be used to start SAS servers.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS Administrator (Required): Add an individual account for the SAS Administrator user. Specify a user ID such as sasadm and a password such as Admin123. (Note: You did not enter information for this user when you ran the installation program.)

      The SAS Administrator user has privileges to manage user accounts and to administer the metadata server. The user ID has unrestricted access to the metadata and should be protected accordingly.

      Windows Systems

      On Windows systems, give this user the user right Log on as a batch job.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS Trusted User (Required): Add an individual account for the SAS Trusted user. Specify a user ID such as sastrust and a password such as Trust123. (Note: You must specify exactly the same user ID and password that you specified when you ran the installation program. If you do not remember the user ID and password, then refer to the install.properties file, which is located in the PortalConfigure subdirectory of the setup directory.)

      The SAS Trusted user account is used by SAS servers to connect to the metadata server, to perform trusted Web logins, and to act as the pool administrator when workspace pooling is configured. Because this user ID is a trusted ID, SAS servers can use it to impersonate authenticated clients on the metadata server (that is, the servers can use it to communicate with the metadata server on behalf of clients).

      Windows Systems

      On Windows systems, give this user the user right Log on as a batch job.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS General Servers (Required): Add a shared account for the SAS General Servers group (shared) login. A shared account is an account that maps to a login that is owned by a SAS group on the SAS Metadata Server. Specify a user ID such as sassrv and a password such as Admin123. (Note: You must specify exactly the same user ID and password that you specified when you ran the installation program.)

      These credentials are used by stored process clusters and workspace puddles to connect to servers.

      Windows Systems

      For the following Windows systems, give this account the specified user rights:

      • On Windows NT and 2000: Act as part of the Operating System
      • On all Windows systems: Log on as a batch job

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS Guest (Required): Add an individual account for the SAS Guest user. Specify a user ID such as sasguest and a password such as Guest123. (Note: You must specify exactly the same user ID and password that you specified when you ran the installation program.)

      This account is a generic user account. It has the lowest level of security privileges.

      Windows Systems

      On Windows systems, give this user the user right Log on as a batch job.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS Web Administrator (Required): Add an individual account for the SAS Web Administrator user. Specify a user ID such as saswbadm and a password such as Admin123. (Note: You must specify exactly the same user ID and password that you specified when you ran the installation program).

      This account has permission to administer the metadata for the SAS Web Infrastructure Kit.

      Windows Systems

      On Windows systems, give this user the user right Log on as a batch job.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

    • SAS Demo User (Optional): Add an individual account for the SAS Demo user. Specify a user ID such as sasdemo and a password such as Demo123. (Note: You must specify exactly the same user ID and password that you specified when you ran the installation program.)

      This account has permission to run the Web applications that are included in the SAS Web Infrastructure Kit.

      Windows Systems

      On Windows systems, give this user the user right Log on as a batch job.

      Unix Systems

      There are no special instructions for Unix systems.

      z/OS Systems

      There are no special instructions for z/OS systems.

  2. To set up your SAS Metadata Server, see the setup instructions that are provided in the SAS 9 SAS Metadata Server Setup Guide on the SAS Web site.

    If your metadata server is configured for host authentication, use the following guidelines to set up the server. (Note: The links will direct you to specific sections of the SAS 9 SAS Metadata Server Setup Guide on the SAS Web site.)

    1. Create directories for the metadata server, repository manager, and repositories.

    2. Set directory and file access permissions.

      Note: Give the SAS account (which you created in the previous step) the required permissions to this directory.

    3. Set system access permissions.

      The Windows system access permissions for each account are specified in Step 7-a.

    4. Set server configuration options in an omaconfig.xml file.

      Note: Make sure that the file omaconfig.xml contains the security setting <OMA AUTHCHCK="INHERIT"/>. For example:

      <OMAconfig>
        <OMA AUTHCHCK="INHERIT"/>
      </OMAconfig>
      
    5. Configure special users in the adminUsers.txt and trustedUsers.txt files.

      Notes:

      • In the file adminUsers.txt, add an entry for the SAS Administrator user. For Windows systems, this entry must be fully qualified with the Windows domain or machine name. In addition, to grant unrestricted access to this user (so that the user can locate users to load metadata), you must place an asterisk in the first character position of the fully qualified user ID.

      • In the file trustedUsers.txt, add an entry for the SAS Trusted User. For Windows systems, this entry must be fully qualified with the Windows domain or machine name.

    6. Start the metadata server

      Note: When you create the script that is used to start the SAS Metadata Server:

      • Specify the same port number that you specified when you ran the installation program. If you do not remember what value you specified, check the value of the $SERVICES_OMI_PORT$ property in the install.properties file (located in the PortalConfigure subdirectory of the setup directory).

      • Specify the correct path for sas.exe.

  3. Start SAS Management Console, and create a new profile and metadata repository. Use the following values when you respond to the prompts:

    • Machine Name. Specify the same machine name that you specified when you ran the installation program. If you do not remember the value that you specified, check the value of the $SERVICES_OMI_HOST$ property in the install.properties file (located in the PortalConfigure subdirectory of the setup directory).

    • Port. Assign the same port that you specified when you ran the installation program. If you do not remember the value that you specified, check the value of the $SERVICES_OMI_PORT$ property in the install.properties file.

    • Add Repository. If you are creating a new repository, it must be a Foundation repository. Assign the same repository name that you specified when you ran the installation program. If you do not remember the value that you specified, check the value of the $SERVICES_OMI_REPOSITORY$ property in the install.properties file.

      Specify the default engine (Base), and set the repository path to the repository directory that you created in Step 7-b.

  4. While SAS Management Console is still connected to your new repository, use SAS Management Console's User Manager to add the required and demonstration users and their logins to the repository.

    For host authentication, each user must have access to login credentials for all of the authentication domains that contain resources that the user will access. Before you set up users, you should understand the portal Web application shell's requirements for authentication domains and user credentials. For details, see Understanding and Verifying Authentication Domains in the SAS Web Infrastructure Kit: Administrator's Guide.

    If you have already created a user definition for one of these users as part of another installation, do not create the definition again. Instead, modify the login definitions as specified. For details about defining SAS users, see Defining a User in the SAS Management Console: User's Guide on the SAS Web site.

    When you define or modify a new user and login definition, the User Manager requires that you make entries in the following fields on the General tab and the Logins tab:

    • General tab:

      Name
      the name of the user (for example, SAS Administrator)

    • Logins tab:

      User ID
      the fully qualified user ID for the login credentials of the user (for example, RALEIGH\sasadm)

      Password
      the password for the user ID (for example, Admin123)

      Authentication Domain
      the logical grouping that associates logins and resources together (for example, DefaultAuth)

    Add new user definitions for the following users and associated user IDs:

    • SAS Administrator. Add a new user and login definition for the SAS Administrator user. You must specify the following:

      • a user name such as SAS Administrator

      • exactly the same fully qualified user ID (for example, RALEIGH\sasadm) that you specified for this user in Step 7.a

      The password and authentication domain are not required and should be left blank because this user definition is only used for authorization decisions.

    • SAS Trusted User. Add a new user and login definition for the SAS Trusted User. You must specify the following:

      • exactly the same user name that you specified for this user when you ran the installation program (for example, SAS Trusted User). If you do not remember the name that you specified, refer to the install.properties file.

      • exactly the same fully qualified user ID (for example, RALEIGH\sastrust) that you specified for this user in Step 7.a.

      • the default authentication domain (for example, DefaultAuth) that you specified when you ran the installation program. If you do not remember the value that you specified, refer to the $SERVICES_OMI_DOMAIN$ property in the install.properties file.

      The password is not required and should be left blank because this user definition is only used for authorization decisions.

    • SAS Web Administrator. Add a new user and login definition for the SAS Web Administrator user. You must specify the following:

      • exactly the same user name that you specified for this user when you ran the installation program (for example, SAS Web Administrator). If you do not remember the name that you specified, refer to the install.properties file.

      • exactly the same fully qualified user ID (for example, RALEIGH\saswbadm) and password (for example, Admin123) that you specified for this user in Step 7.a.

      • the default authentication domain (for example, DefaultAuth) that you specified when you ran the installation program. If you do not remember the value that you specified, refer to the $SERVICES_OMI_DOMAIN$ property in the install.properties file.

    • SAS Guest. Add a new user and login definition for the SAS Guest user. You must specify the following:

      • exactly the same user name that you specified for this user when you ran the installation program (for example, SAS Guest). If you do not remember the name that you specified, refer to the install.properties file.

      • exactly the same fully qualified user ID (for example, RALEIGH\sasguest) and password (for example, Guest123) that you specified for this user in Step 7.a.

      • the default authentication domain (for example, DefaultAuth) that you specified when you ran the installation program. If you do not remember the value that you specified, refer to the $SERVICES_OMI_DOMAIN$ property in the install.properties file.

    • SAS Demo User. Add a new user and login definition for the SAS Demo user. You must specify the following:

      • exactly the same user name that you specified for this user when you ran the installation program (for example, SAS Demo User). If you do not remember the name that you specified, refer to the install.properties file.

      • exactly the same fully qualified user ID (for example, RALEIGH\sasdemo) and password (for example, Demo123) that you specified for this user in Step 7.a.

      • the default authentication domain (for example, DefaultAuth) that you specified when you ran the installation program. If you do not remember the value that you specified, refer to the $SERVICES_OMI_DOMAIN$ property in the install.properties file.

  5. While SAS Management Console is still connected to your new repository, use SAS Management Console's User Manager to add the initial groups to the repository and to add the necessary users to those groups.

    If you have already created a group definition for one of these groups as part of another installation, do not create the definition again. However, you must make sure that all of the specified users have been added to the group.

    • SAS General Servers: Add a group login definition that specifies the login credentials for the SAS General Servers account that you defined on the host authentication provider. You must specify exactly the same name (for example, SAS General Servers), fully qualified user ID (for example, RALEIGH\sassrv), and password (for example, Admin123) that you specified in the installation program and in Step 7.a.

      Note: Specify the default authentication domain that you specified when you ran the installation program. If you do not remember the value that you specified, check the value of the $SERVICES_OMI_DOMAIN$ property in the install.properties file.

      Add the SAS Trusted User as a member of the SAS General Servers group.

    • SAS System Services: Add a new group definition for SAS System Services. For this group, specify the name SAS System Services. Add the SAS Trusted User and SAS Web Administrator users as members of this group.

    • Portal Admins: Add a new group definition for Portal Admins. For this group, specify the name Portal Admins. Add the SAS Web Administrator user as a member of this group.

    • Portal Demos. Add a new group definition for Portal Demos. For this group, specify the name Portal Demos. Add the SAS Demo user as a member of this group.

  6. While SAS Management Console is still connected to your new repository, use SAS Management Console's Authorization Manager to define default authorizations for the resources in this repository. By default, all authenticated users have access to this repository. Since it is a common practice to limit access after adding more users to the system, you must define some additional authorizations that are needed by the SAS services.

    If you have already performed these tasks as part of another installation, do not perform them again.

    1. Expand the Authorization Manager node, and then expand the Access Control Templates folder that it contains.

    2. Under Access Control Templates, select the Default ACT template. Then select File -> Properties (or click the right mouse button, and select Properties).

    3. Select the Users and Permissions tab.

    4. Click Add.

    5. In the Add Users or Group dialog box, move the SAS System Services group identity from the Available Identities list to the Selected Identities list. Click OK to save the change.

    6. With SAS Systems Services highlighted in the list of names on the Users and Permissions tab, check the Permissions list at the bottom of the tab to verify that the ReadMetadata permission is granted to this identity.

    7. Click Add again.

    8. In the Add Users or Group dialog box, move the SAS Administrator user identity from the Available Identities list to the Selected Identities list. Click OK to save the change.

    9. With SAS Administrator highlighted in the list of names on the Users and Permissions tab, select the Grant check box for each permission in order to grant all permissions to this user.

    10. Click OK to save the changes.

For more information about defining users and groups, refer to the SAS Management Console User Manager Help and to Defining Users, Groups, and Logins in the SAS Integration Technologies: Server Administrator's Guide.


Step 8: Install Metadata

The next step is to install required and demonstration metadata for the common infrastructure, the portal structure, users, groups, stored processes, and servers into your metadata repository.

To load most of the metadata, you can run SAS programs that are provided with the SAS Web Infrastructure Kit. These programs are in files with the extension .sas. You must run these programs on a machine that has the SAS Foundation installed.

Two versions of every SAS program file are provided:

Caution: The SAS programs that are provided with the SAS Web Infrastructure Kit will abort if they are run more than once.

Caution: If you want to load the demonstration metadata, be sure to complete this entire step before you bring up the portal Web application shell.

Follow these steps:

  1. (Required): To load the required metadata into your metadata repository, follow the appropriate procedure for your platform:

    • On Windows systems, follow these steps:

      1. Go to the OMR subdirectory of the setup directory.

      2. Right-click on LoadDefaultPreferences.sas or LoadDefaultPreferences_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      3. Right-click on LoadPreferencesConnection.sas or LoadPreferencesConnection_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      4. Right-click on LoadThemeConnection.sas or LoadThemeConnection_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

    • On Unix systems, follow these steps:

      1. Go to the OMR subdirectory of the setup directory.

      2. Submit LoadDefaultPreferences.sas or LoadDefaultPreferences_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      3. Submit LoadPreferencesConnection.sas or LoadPreferencesConnection_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      4. Submit LoadThemeConnection.sas or LoadThemeConnection_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

    • On z/OS systems, follow these steps:

      1. Go to the OMR subdirectory of the setup directory.

      2. Use the ftp utility to transfer all of the SAS programs as text files from the setup machine to the z/OS system.

      3. Log on to the z/OS system.

      4. On the z/OS system, submit LoadDefaultPreferences.sas or LoadDefaultPreferences_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      5. On the z/OS system, submit LoadPreferencesConnection.sas or LoadPreferencesConnection_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      6. On the z/OS system, submit LoadThemeConnection.sas or LoadThemeConnection_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

    Note: For additional information on changing preferences once they are installed, see Changing the Default Preferences in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site.

    Note: For additional information on changing theme metadata, see Theme Deployment in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site.

  2. (Optional): To load the demonstration metadata into your metadata repository, follow the appropriate procedure for your platform:

    • On Windows systems, follow these steps in the order specified:

      1. Go to the OMR subdirectory of the setup directory.

      2. Right-click on LoadPortalStructure.sas or LoadPortalStructure_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      3. Right-click on LoadStoredProcessSamples.sas or LoadStoredProcessSamples_utf8.sas, and select Batch Submit with SAS 9.1. When the program is finished, view the log file to validate the metadata installation.

        Note: In some cases this program may prompt you for credentials to access the metadata server. If you are prompted for credentials, use the user ID and password you created for the SAS Administrator user in Step 7 above.

    • On Unix systems, follow these steps in the order specified:

      1. Go to the OMR subdirectory of the setup directory.

      2. Submit LoadPortalStructure.sas or LoadPortalStructure_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      3. Submit LoadStoredProcessSamples.sas or LoadStoredProcessSamples_utf8.sas with SAS 9.1. When the program is finished, view the log file to validate the metadata installation.

        Note: In some cases this program may prompt you for credentials to access the metadata server. If you are prompted for credentials, use the user ID and password you created for the SAS Administrator user in Step 7 above.

    • On z/OS systems, follow these steps in the order specified:

      1. Go to the OMR subdirectory of the setup directory.

      2. Use the ftp utility to transfer all of the SAS programs as text files from the setup machine to the z/OS system.

      3. Log on to the z/OS system.

      4. On the z/OS system, submit LoadPortalStructure.sas or LoadPortalStructure_utf8.sas with SAS 9.1. When the program is finished, look for the message "NOTE: Successfully loaded metadata" near the bottom of the log file to validate the metadata installation.

      5. On the z/OS system, submit LoadStoredProcessSamples.sas or LoadStoredProcessSamples_utf8.sas with SAS 9.1. When the program is finished, view the log file to validate the metadata installation.

        Note: In some cases this program may prompt you for credentials to access the metadata server. If you are prompted for credentials, use the user ID and password you created for the SAS Administrator user in Step 7 above.

    Note: For additional information on removing portal metadata, see SAS Portal Metadata Tool in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site. After running this tool, it is safe to reload LoadPortalStructure.sas.

    Note: For additional information on changing stored process server definitions, see Services, Server, Portlet, and Theme Deployment in the SAS Web Infrastructure Kit: Administrator's Guide on the SAS Web site.

    Note: For information about converting the workspace server to a pooled workspace server, see the chapter titled "Configuring Your SAS Servers for Better Performance" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site. Workspace pooling enhances the performance of SAS servers when they are running in a multiple-user environment.

  3. (Required if you use the Xythos WebDAV server): You must create an entry for an HTTP server in your metadata repository. To create this entry:

    1. Start SAS Management Console, and access the Server Manager plug-in.

    2. Create a new HTTP server entry for your Xythos WebFile Server. Use the WebDAV-related values that you specified when you ran the installation program. If you do not remember what values you specified, check the following values in the install.properties file (located in the PortalConfigure subdirectory of the setup directory):

      • $DAV_DOMAIN$
      • $DAV_BASE$
      • $DAV_HOST$
      • $DAV_PORT$

  4. (Required if you are using the SAS Metadata Server as the location for SAS Foundation Services metadata): When you ran the installation program, you were prompted to select either XML File or SAS Metadata Server as the location for foundation services metadata. If you used the default location or selected SAS Metadata Server as the location, then you must perform the following steps in order to load the metadata.

    If you do not remember what location you selected, check the value of the $SERVICES_OMI_METADATA_LOCATION$ property in the install.properties file (located in the PortalConfigure subdirectory of the setup directory). If the value of this property is omr, then you must perform the following steps:

    1. Start SAS Management Console, and access the Foundation Services Manager.

    2. From the Actions menu, select Import Service Deployment...

    3. On the Import Service Deployment dialog box, click Add... and then select the following service deployment files, which are located in the SASServicesConfig subdirectory of the setup directory:

      • sas_services_idp_local_omr.xml
      • sas_services_idp_remote_omr.xml

    4. While the Import Service Deployment dialog box is still open, click OK to import the files.

    Note: If the install.properties file is changed after you perform this step and the configuration script (configure_wik.bat or configure_wik.sh) is rerun, then the foundation services metadata may be affected. To ensure that the foundation services metadata changes are applied, you must:

    1. Use SAS Management Console to delete the service deployments from the SAS Metadata Server.

    2. Re-import the service deployment files as described above.

      Any changes that had been made to the previous service deployments using SAS Management Console will be lost.

For additional information on loading metadata, see the Loading Initial Portal Metadata topic of the SAS Web Infrastructure Kit: Administrator's Guide.


Step 9: Set Up the SAS Object Spawner

The SAS Web Infrastructure Kit uses a SAS Stored Process Server and a SAS Workspace Server for various functions, including executing stored processes and accessing information maps. These servers are started by the SAS Object Spawner. To set up the SAS Object Spawner, follow the appropriate steps for your operating system environment.

Windows Systems

  1. Create a directory for the spawner configuration and log files. The recommended directory name is ObjectSpawner. The directory should be located in the server home location that you specified when you ran the installation program (for example, C:\Program Files\SAS\Servers\ObjectSpawner).

    If you do not remember the server home location, check the value of the $IOM_SERVERS_HOME$ property in the install.properties file, which is located in the PortalConfigure subdirectory of the setup directory.

  2. Use the Metadata Server Connections utility to create the metadata configuration file for the spawner, as follows:

    1. Start SAS 9.1 from the Windows Start menu.

    2. In the SAS command bar, type METACON. Then press Enter. The Metadata Server Connections window is displayed.

    3. Click the Add button to add a new connection definition. Enter SAS Object Spawner in the Name field, and enter the connection parameters. In the User Name and Password fields, enter the SAS Trusted User credentials that you specified when you ran the installation program. You can find these credentials in the $SERVICES_OMI_USER_ID$ and $SERVICES_OMI_USER_PASSWORD$ properties in your install.properties file.

    4. If the SAS Metadata Server is running, you can test your configuration by clicking the Test button.

    5. Export the connection definition by clicking the Export button and then saving the connection to a file named MetadataServer.xml in the spawner configuration directory.

    6. Click OK to close the Metadata Server Connections window. You can now exit SAS 9.1.

    Note: The metadata configuration file that you just created contains trusted access credentials for the metadata server. To control access to this information, you must set appropriate access controls on the spawner configuration directory.

  3. Create a startup script in the new directory, and save the script using the name StartSpawner.bat.

    Here is an example startup script for an installation using default values.

    Note: If you copy and paste this code, you must remove the line breaks from the objspawn start line. The values that are displayed in italics might need to be changed for your installation.

    @echo off
    cd /d "C:\Program Files\SAS\Servers\ObjectSpawner"
    echo STARTING OBJECT SPAWNER ...
    SET I=0
    :LOOP
    SET /A I=I+1
    IF EXIST spawner_%I%.log GOTO LOOP
    
    start/min "SAS Object Spawner"
              "C:\Program Files\SAS\SAS 9.1\objspawn"
                    -sasSpawnercn "localhost Spawner"
                    -xmlConfigFile MetadataServer.xml
                    -slf spawner_%I%.log
    

    The -sasSpawnercn option in the objspawn start line specifies the name of the spawner definition in the metadata repository. This option should be set to the name of the SAS server machine (as specified in the $STP_HOST$ property of the install.properties file) followed by Spawner.

  4. Create a directory for stored process server log files. The recommended directory name is STPDemo, and the recommended location is the server home location that you specified when you ran the installation program (for example, C:\Program Files\SAS\Servers\STPDemo).

    If you do not remember the server home location, see the $STP_HOME$ property in the install.properties file.

  5. If needed, set up a SAS General Servers account on the spawner machine's operating system, including a name (for example, SAS General Servers), a user ID (for example, sassrv), and a password (for example, Admin123). You must use the exact user ID and password that you specified when you ran the installation program. The spawner uses these credentials to launch the SAS Stored Process Server as a multi-user server.

    On Windows NT and Windows 2000, the SAS General Servers account must have the Act as part of the Operating System security policy.

  6. Give the SAS General Servers account write permission to the stored process directory that was created in the previous step.

  7. For the user who invokes the spawner, define the appropriate user rights as described in Step 1 of the Starting the Spawner on Windows section of the SAS Integration Technologies: Server Administrator's Guide.

Unix Systems

  1. Create a directory for spawner configuration and log files. The recommended directory name is ObjectSpawner in the server home location that you specified when you ran the installation program (for example, /usr/local/SAS/Servers/ObjectSpawner).

    If you do not remember the server home location, then see the $IOM_SERVERS_HOME$ property in the install.properties file located in the PortalConfigure subdirectory of the setup directory.

  2. Use the Metadata Server Connections utility to create the metadata configuration file for the spawner, as follows:

    1. Start SAS 9.1 in display manager mode (use the -DMS option).

    2. Type METACON in the command bar, and press the Enter key.

    3. Click the Add button to add a new connection definition. Enter the connection name SAS Object Spawner, and fill in the connection parameters. In the User Name and Password fields, enter the SAS Trusted User credentials that you specified when you ran the installation program. You can find these credentials in the $SERVICES_OMI_USER_ID$ and $SERVICES_OMI_USER_PASSWORD$ properties in your install.properties file.

    4. If the SAS Metadata Server is running, then you can test your configuration by clicking the Test button.

    5. Export the connection definition by selecting the Export button, and save the connection to a file named MetadataServer.xml in the spawner configuration directory.

    6. Click OK to close the window. You can now exit SAS 9.1.

    Note: The metadata configuration file that you just created contains trusted access credential for the metadata server. To control access to this information, you must set appropriate access controls on the configuration file or the spawner configuration directory.

  3. Create a startup script in the new directory, and save the script using the name StartSpawner.sh.

    Here is an example startup script for an installation using default values:

    Note: If you copy and paste this code, make sure to remove the line break from the objspawn line. The values in italics might need to be changed for your installation.

    #!/bin/ksh
    cd "/usr/local/SAS/Servers/ObjectSpawner"
    echo STARTING OBJECT SPAWNER ...
    I=1
    while test -f spawner_$I.log; do let I=$I+1; done;
    
    /usr/local/SAS/utilities/bin/objspawn
            -sasSpawnercn "localhost Spawner"
            -xmlConfigFile MetadataServer.xml
            -slf spawner_$I.log
    

    The -sasSpawnercn option in the objspawn start line specifies the name of the spawner definition in the metadata repository. This option should be set to the name of the SAS server machine (as specified by the $STP_HOST$ property in the install.properties file) followed by Spawner.

  4. Create a directory for stored process server log files. The recommended directory name is STPDemo, and the recommended location is the server home location that you specified when you ran the installation program (for example, /usr/local/SAS/Servers/STPDemo).

    To verify the server home location, see the $STP_HOME$ property in the install.properties file.

  5. If needed, set up the SAS General Servers account on the spawner machine's operating system. For example, you could specify the name SAS General Servers, the user ID sassrv, and the password Admin123. (Note: You must specify the exact user ID and password that you specified when you ran the installation program.) The spawner uses these credentials to launch the SAS Stored Process Server as a multi-user server.

  6. Give this user write permission to the stored process directory that you created in the previous step.

  7. For the user who invokes the spawner, define the appropriate user rights as outlined in Step 1 of the Starting the Spawner on Unix section of the SAS Integration Technologies: Server Administrator's Guide.

z/OS

On z/OS systems, use the z/OS configuration wizard to set up SAS servers.


Step 10: Prepare the Servlet Container Environment

The SAS Web Infrastructure Kit requires a security manager to be running in the Java Virtual Machine (JVM) that the servlet container uses. You might also want to set JVM system variables for system tuning or to access content through a firewall. The following settings might be useful in helping you set up your servlet container environment. Some of these options are specific to a particular JVM. You should always refer to the documentation for your servlet container and JVM before setting any options.

-Djava.awt.headless=true
Required: This parameter specifies that the JVM should use graphics methods that support running without a display, keyboard, and mouse. This parameter is needed for environments in which a display, keyboard, or mouse may not be available (for example, dedicated servers).

The IBM JDK currently does not support the java.awt.headless parameter. This parameter can be safely removed when running the IBM JDK on Windows. When running the IBM JDK on AIX, you must ensure that the JVM has access to a valid X display. This can be accomplished by either setting the DISPLAY environment variable to point to a running X server, or by configuring IBM's X Virtual Frame Buffer (XVFB).

-Dhttp.proxyHost=host
Optional: This parameter specifies the proxy server machine name. You must specify this parameter only if your network has a proxy server.

-Dhttp.proxyPort=port
Optional: This parameter specifies the proxy server port. You must specify this parameter only if your network has a proxy server.

Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site. The settings that are specified in the Installation Tips sections below are the minimal settings needed to bring up the SAS Web Infrastructure Kit Web applications. These settings must be modified if additional Web applications are running in the same JVM or if multiple users will be accessing the SAS Web Infrastructure Kit Web applications.

Windows Systems

Installation Tips for Apache Tomcat 4.1 on Windows Systems
  1. If you install Tomcat as a service, then JVM system variables that are used to tune performance must be set in the CATALINA_OPTS environment variable. Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site.
  1. If you start and stop Tomcat manually, then you will need to create a startup script. In the Tomcat bin directory, create a new startup script named StartWithSASEnvironment.bat (for example, C:\Tomcat4.1\bin\StartWithSASEnvironment.bat). The following is an example startup script with no tuning. Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site.
    @echo off
    
    set CLASSPATH=
    set JAVA_HOME=C:\j2sdk1.4.2_02
    set CATALINA_HOME=C:\Tomcat4.1
    set CATALINA_OPTS=-Xms256m -Xmx256m
    
    "%CATALINA_HOME%\bin\catalina.bat" run -security
    
    The -security option that is passed into catalina.bat is required in order to enable the Java security manager.
  1. In the Tomcat conf directory, modify the Java policy file (catalina.policy) to grant appropriate permissions to the SAS Web Infrastructure Kit Web applications. These applications require different permissions depending on how the applications are installed.

    To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.tomcat.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.tomcat.policy defines more restrictive security settings. This file should be used in a production environment.

    For example, if your CATALINA_HOME environment variable points to the directory where your Web applications are deployed, you should concatenate the sas.wik.allpermissions.tomcat.policy file to the end of the C:\Tomcat4.1\conf\catalina.policy file.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:

      mkdir C:\Program Files\SAS\Documentation\9.1\SASDoc
      
    2. Using a tool such as WinZip, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    3. In the Tomcat conf directory, modify the Java policy file (catalina.policy) to grant appropriate permissions to the SAS Documentation Web application. The permissions that this application requires are defined in the sasdoc.tomcat.permissions file, which is located in the SASDoc\WEB-INF directory that you just created.
  1. If you use the sas.wik.tomcat.policy file, and if you configured your RMI server to run on localhost, then you will need to modify the catalina.policy file after you have concatenated the sas.wik.tomcat.policy file to the end. In each of the grant sections for the SAS Web Infrastructure Kit applications, locate the following lines:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.tomcat.policy file, then you might need additional permissions in order to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.
  1. The RUNNING.TXT file that is included with Tomcat contains a section titled "(4) Advanced Configuration - Multiple Tomcat 4 Instances." This section discusses sharing a single copy of a Tomcat 4 binary distribution among multiple users on the same server. If your Tomcat installation is configured this way, then you must change the codebase that is used in the grant statements of the policy file to reflect your setup.
  1. To stop the Tomcat server once it is running, you should use the shutdown.bat script that is located in the Tomcat bin directory .

Installation Tips for BEA WebLogic 8.1 on Windows Systems
  1. In the new server domain, update the startManagedWebLogic.cmd script to include the appropriate JVM system variables for the managed server. The script is located in the path C:\bea\user_projects\domains\mydomain\.

    Before the line in the script that starts the JVM, set JVM tuning values in the JAVA_OPTIONS environment variable. The following is an example with no tuning. Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site.

    set JAVA_OPTIONS=-Xms256m -Xmx256m
  1. In the WebLogic weblogic81\server\lib directory, modify the Java policy file weblogic.policy to grant appropriate permissions to the SAS Web Infrastructure Kit Web applications. These applications require different permissions depending on how the applications are installed.

    To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.weblogic.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.weblogic.policy defines more restrictive security settings. This file should be used in a production environment.

    Permissions are granted based on the location of the JAR files in the file system. WebLogic copies the JAR files from the exploded application archives directory (see Step 11 for details) into a working directory in the WebLogic domain (created in Step 3). For example, you might concatenate the sas.wik.allpermissions.weblogic.policy file to the end of the C:\bea\weblogic81\server\lib\weblogic.policy file.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:

      mkdir C:\Program Files\SAS\Documentation\9.1\SASDoc
      
    2. Using a tool such as WinZip, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    3. In the WebLogic weblogic81\server\lib directory, modify the Java policy file (weblogic.policy) to grant appropriate permissions to the SAS Documentation Web application. The permissions that this application requires are defined in the sasdoc.weblogic.permissions file, which is located in the SASDoc\WEB-INF directory that you just created.

  1. In the BEA weblogic.policy file, you may need to modify the codebase in the grant statement to point to the correct directory for your installation. By default, this value is set to file:${/}bea${/}user_projects${/}domains${/}mydomain${/}managedServer_1${/}-.

    Note: The default codebase has changed from file:${/}bea${/}user_projects${/}domains${/}mydomain${/}myserver${/}- in previous installations to file:${/}bea${/}user_projects${/}domains${/}mydomain${/}managedServer_1${/}-. This default assumes that you use the startManagedWebLogic.cmd script to start the managed servers.

    Note: If you start your managed servers from the node manager, then you will need to modify the codebase. For example: file:${/}bea${/}weblogic81${/}common${/}nodemanager${/}managedServer_1${/}-.

  1. If you use the sas.wik.weblogic.policy file, and if you configured your RMI server to run on localhost, then you must modify the BEA weblogic.policy file after you have concatenated the sas.wik.weblogic.policy file to the end. In the grant section for the SAS Web Infrastructure Kit applications, locate the following lines:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.weblogic.policy file, then additional permissions might be needed to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.

Installation Tips for IBM WebSphere 6.1 on Windows Systems
  1. Use the WebSphere Administrative Console to set the Java Virtual Machine system variables, as follows:

    1. If necessary, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Application Servers wizard (for example, Servers -> Application Servers ).

    5. On the next screen, select the link for your server (for example, server1).

    6. On the next screen, select the Java and Process Management link.

    7. On the next screen, select the Process Definition link.

    8. On the next screen, select the Java Virtual Machine link.

    9. Update the Java Virtual Machine configuration as follows:

      Select the OK button when you are finished.

    10. Selecting the Save link in the Save directly to the master configuration dialog.

  1. Update WebSphere's JAAS configuration file to include the authentication information that is used by SAS Web Infrastructure Kit Web applications. To do so, concatenate the contents of the login.config file (located in the SASServicesConfig folder of the setup directory) to your server's JAAS configuration file (located in the WebSphere AppServer\profiles\AppSrv01\properties directory). As a default, the server's JAAS configuration file is called wsjaas.conf.

Unix Systems

Installation Tips for Apache Tomcat 4.1 on Unix Systems
  1. In the Tomcat bin directory, create a new startup script named StartWithSASEnvironment.sh (for example,
    /usr/local/Tomcat4.1/bin/StartWithSASEnvironment.sh). The following is an example startup script with no tuning. Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site.
    #!/bin/sh
    
    CLASSPATH=
    export CLASSPATH
    JAVA_HOME=/usr/local/j2sdk1.4.2_02
    export JAVA_HOME
    CATALINA_HOME=/usr/local/Tomcat4.1
    export CATALINA_HOME
    CATALINA_OPTS="-Xms256m -Xmx256m"
    export CATALINA_OPTS
    
    $CATALINA_HOME/bin/catalina.sh run -security
    
    The -security option that is passed into catalina.sh is required in order to enable the Java security manager.
  1. In the Tomcat conf directory, modify the Java policy file (catalina.policy) to grant appropriate permissions to the SAS Web Infrastructure Kit Web applications. These applications require different permissions depending on how the applications are installed.

    To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files, which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.tomcat.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.tomcat.policy defines more restrictive security settings. This file should be used in a production environment.

    For example, if your CATALINA_HOME environment variable points to the directory where your Web applications are deployed, concatenate the sas.wik.allpermissions.tomcat.policy file to the end of the /usr/local/Tomcat4.1/conf/catalina.policy file.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:
      mkdir /usr/local/SAS/Documentation/9.1/SASDoc
      
    2. Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    3. In the Tomcat conf directory, modify the Java policy file (catalina.policy) to grant appropriate permissions to the SAS Documentation Web application. The permissions that this application requires are defined in the sasdoc.tomcat.permissions file, which is located in the SASDoc/WEB-INF directory that you just created.
  1. If you use the sas.wik.tomcat.policy file, and if you configured your RMI server to run on localhost, then you will need to modify the catalina.policy file after you have concatenated the sas.wik.tomcat.policy file to the end. In each of the grant sections for the SAS Web Infrastructure Kit applications, locate the following lines:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.tomcat.policy file, additional permissions might be needed to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.
  1. The RUNNING.TXT file that is included with Tomcat contains a section titled "(4) Advanced Configuration - Multiple Tomcat 4 Instances." This section discusses sharing a single copy of a Tomcat 4 binary distribution among multiple users on the same server. If your Tomcat installation is configured this way, then you must change the codebase that is used in the grant statements of the policy file to reflect your setup.
  1. To stop the Tomcat server once it is running, you should use the shutdown.sh script that is located in the Tomcat bin directory.

Installation Tips for BEA WebLogic 8.1 on Unix Systems
  1. In the new server domain, update the startManagedWebLogic.sh script to include the appropriate JVM system variables for the managed server. The script is located in the path /usr/local/bea/user_projects/domains/mydomain/.

    Before the line in the script that starts the JVM, set JVM tuning values in the JAVA_OPTIONS environment variable. The following is an example with no tuning. Details on tuning the JVM can be found in the chapter titled "Best Practices for Configuring Your Middle Tier" in the SAS 9.1.3 Intelligence Platform: Administration Guide on the SAS Web site.

    JAVA_OPTIONS="-Xms256m -Xmx256m"
    
  1. In the WebLogic weblogic81/server/lib directory, modify the Java policy file ( weblogic.policy) to grant appropriate permissions to the SAS Web Infrastructure Kit Web applications. These applications require different permissions depending on how the applications are installed.

    To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.weblogic.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.weblogic.policy defines more restrictive security settings. This file should be used in a production environment.

    Permissions are granted based on the location of the JAR files in the file system. WebLogic copies the JAR files from the exploded application archives directory (see Step 11 for details) into a working directory in the WebLogic domain (created in Step 3). For example, you might concatenate the sas.wik.allpermissions.weblogic.policy file to the end of the /usr/local/bea/weblogic81/server/lib/weblogic.policy file.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:
      mkdir /usr/local/SAS/Documentation/9.1/SASDoc
      
    2. Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    3. In the WebLogic weblogic81/server/lib directory, modify the Java policy file (weblogic.policy) to grant appropriate permissions to the SAS Documentation Web application. The permissions that this application requires are defined in the sasdoc.weblogic.permissions file, which is located in the SASDoc/WEB-INF directory that you just created.
  1. In the BEA weblogic.policy file, you may need to modify the codebase in the grant statement to point to the correct directory for your installation. By default, this value is set to file:${/}bea${/}user_projects${/}domains${/}mydomain${/}managedServer_1${/}-.

    Note: The default codebase has changed from file:${/}bea${/}user_projects${/}domains${/}mydomain${/}myserver${/}- in previous installations to file:${/}bea${/}user_projects${/}domains${/}mydomain${/}managedServer_1${/}-. This default assumes that you use the startManagedWebLogic.sh script to start the managed servers.

    Note: If you start your managed servers from the node manager, then you will need to modify the codebase. For example: file:${/}bea${/}weblogic81${/}common${/}nodemanager${/}managedServer_1${/}-.

  1. If you use the sas.wik.weblogic.policy file, and if you configured your RMI server to run on localhost, then you will need to modify the BEA weblogic.policy file after you have concatenated the sas.wik.weblogic.policy file to the end. In the grant section for the SAS Web Infrastructure Kit Applications, locate the following lines:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.weblogic.policy file, additional permissions might be needed to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.

Installation Tips for IBM WebSphere 6.1 on Unix Systems
  1. Use the WebSphere Administrative Console to set the Java Virtual Machine system variables, as follows:

    1. If necessary, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Application Servers wizard (for example, Servers -> Application Servers ).

    5. On the next screen, select the link for your server (for example, server1).

    6. On the next screen, select the Java and Process Management link.

    7. On the next screen, select the Process Definition link.

    8. On the next screen, select the Java Virtual Machine link.

    9. Update the Java Virtual Machine configuration as follows:

      Select the OK button when you are finished.

    10. Selecting the Save link in the Save directly to the master configuration dialog.
  1. Update WebSphere's JAAS configuration file to include the authentication information that is used by SAS Web Infrastructure Kit Web applications. To do so, concatenate the contents of the login.config file (located in the SASServicesConfig folder of the setup directory) to your server's JAAS configuration file (located in the WebSphere AppServer\profiles\AppSrv01\properties directory). As a default, the server's JAAS configuration file is called wsjaas.conf.


Step 11: Deploy Web Application Files into the Servlet Container

You must manually deploy the SAS Web Infrastructure Kit Web applications from the setup directory to the servlet container. The following installation tips contain the procedures for each servlet container and system environment.

Windows Systems

Installation Tips for Apache Tomcat 4.1 on Windows Systems
  1. From the setup directory, run the tomcat_deploy.bat script to deploy files to the Tomcat webapps directory. This script is new to the 9.1.3 Service Pack 4 release. For example:
    cd "C:\Program Files\SAS\Web\Portal2.0.1"
    tomcat_deploy.bat
    
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    From the SAS Documentation setup directory that you specified when you ran the installation program, copy the SASDoc.war file to the Tomcat webapps directory. For example:
    cd "C:\Program Files\SAS\Documentation\9.1"
    copy SASDoc.war C:\Tomcat4.1\webapps
    
  1. From the Tomcat directory, delete the following subdirectories, if they are present, and their contents.
    • webapps\SASDoc
    • work\Standalone\localhost\Portal
    • work\Standalone\localhost\SASStoredProcess
    • work\Standalone\localhost\SASPreferences
    • work\Standalone\localhost\SASTheme_default
    • work\Standalone\localhost\SASDoc

Installation Tips for BEA WebLogic 8.1 on Windows Systems
The SAS Web Infrastructure Kit requires Web application files to be deployed as exploded application archives. The following instructions describe how to explode the Web applications.
  1. First, create the directories for the exploded application archives to be moved to. For example:
    mkdir C:\bea\webapps
    mkdir C:\bea\webapps\Portal
    mkdir C:\bea\webapps\SASStoredProcess
    mkdir C:\bea\webapps\SASPreferences
    mkdir C:\bea\webapps\SASTheme_default
    mkdir C:\bea\webapps\SASDoc
    
  1. From the setup directory, recursively copy the contents of the Portal, SASStoredProcess, and SASPreferences directories to the directories that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories. For example:
cd "C:\Program Files\SAS\Web\Portal2.0.1"
xcopy Portal           C:\bea\webapps\Portal /S
xcopy SASStoredProcess C:\bea\webapps\SASStoredProcess /S
xcopy SASPreferences   C:\bea\webapps\SASPreferences /S
  1. Using a tool such as WinZip, unpack the SASTheme_default.war file from the setup directory into the directory that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories.
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    Using a tool such as WinZip, unpack the SASDoc.war file from the SAS Documentation setup directory (which you specified when you ran the installation program) into the directory that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories.
  1. Using the WebLogic console, deploy the exploded Web applications from the directories that you created in the previous steps, as follows:

    1. Start the WebLogic server. First, make sure that the startWebLogic.cmd script has been used to start the administrative server. When the administrative server is in the RUNNING Mode, use the startManagedWebLogic.cmd script to start the managed server. If the WebLogic Node Manager Service is installed and running, then you can start the managed server from the WebLogic console. For example:
      cd \bea\user_projects\domains\mydomain
      startWebLogic.cmd
      startManagedWebLogic.cmd
      
    2. Point your browser to the console Web application (for example, http://localhost:7001/console).

    3. Log on using the account and password that you created in Step 3 (for example, weblogic and Weblogic123).

    4. Use Steps v through xi to deploy each of the following Web applications. The Web applications should be deployed in the same order that they appear on this list:

      1. SASTheme_default
      2. SASPreferences
      3. SASDoc
      4. Portal
      5. SASStoredProcess

    5. After you have logged on, use the tree on the left side of the console to navigate to the Web application deployment wizard (for example, mydomain -> Deployments -> Web Application Modules).

    6. On the wizard's Configuration tab, select Deploy a new Web Application Module...

    7. Navigate to the C:\bea\webapps directory.

    8. On the Deploy a Web Application Module screen, select the appropriate directory, and then select the Target Module button.

    9. On the next screen, select the managed server that you created in Step 3, and then select the Continue button.

    10. On the next screen, select the Deploy button.

    11. Repeat Steps v, vi, vii, viii, ix, and x for each Web application.

  1. After all of the Web applications have been deployed, adjust the load order for the SASTheme_default application, as follows:

    1. Use the tree on the left side of the console to navigate back to the Web application deployment wizard (for example, mydomain -> Deployments -> Web Application Modules).

    2. Select the SASTheme_default Web application.

    3. Select the Configuration tab, and then select the General tab that is located below it.

    4. Change the Load Order to a value that is less than the load order assigned to the other Web applications (for example, 50). Then select the Apply button.

    5. Shut down the WebLogic server.

Installation Tips for IBM WebSphere 6.1 on Windows Systems
  1. Create a staging directory for the Web application archive files. For example:
    mkdir C:\apps\WebSphere\webapps
    
  1. From the setup directory, copy the Portal.war, SASStoredProcess.war, SASPreferences.war, and SASTheme_default.war files to the staging directory that you created in the previous step. For example:
    cd "C:\Program Files\SAS\Web\Portal2.0.1"
    copy Portal.war           C:\apps\WebSphere\webapps
    copy SASStoredProcess.war C:\apps\WebSphere\webapps
    copy SASPreferences.war   C:\apps\WebSphere\webapps
    copy SASTheme_default.war C:\apps\WebSphere\webapps
    
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    From the SAS Documentation setup directory that you specified when you ran the installation program, copy the SASDoc.war file to the staging directory that you created in Step a. For example:
    cd "C:\Program Files\SAS\Documentation\9.1"
    copy SASDoc.war C:\apps\WebSphere\webapps
    
  1. Using the WebSphere Administrative Console, deploy the Web applications from the staging directory that you created in Step a, as follows:

    1. If needed, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. Use the Preparing for application installation wizard, as described in Steps v through xiv below, to deploy each of the following Web applications. The Web applications should be deployed in the order that they are listed here:

      1. SASTheme_default
      2. SASPreferences
      3. SASDoc
      4. Portal
      5. SASStoredProcess

    5. After you have logged on, use the tree on the left side of the console to navigate to the Preparing for application installation wizard (for example, Applications -> Install New Application).

    6. On the first screen, set the Local path (or Remote path for a remote server deployment) by using the browse button to navigate to the C:\apps\WebSphere\webapps directory and selecting the appropriate Web application.

    7. Set the Context Root to the name of the Web application (the filename without the .war extension), and then select the Next button.

    8. The next screen is step 1 of the Install New Application wizard. At steps 1 through 3, click on the Next button to accept the defaults. On step 4, click on the Finish button to accept the defaults.
    9. When this last step finishes (it takes a few minutes), you will see a link to Save directly to Master Configuration. Click on the link, then click on the Save button.
    10. Repeat Steps v, vi, vii, viii, and ix for each Web application.

  1. After all of the Web applications have been deployed, adjust the settings for the SASTheme_default, SASPreferences, and Portal Web applications as follows:

    1. Use the tree on the left side of the console to navigate to the Enterprise Applications wizard (for example, Applications -> Enterprise Applications).

    2. Select the SASTheme_default Web application link.

    3. Select Startup behavior and change the Startup order to 1. Then select the OK button.

    4. Select the SASPreferences Web application link.

    5. Select Startup behavior and change the Startup order to 2. Then select the OK button.

    6. Select the Portal Web application link.

    7. Select Startup behavior and change the Startup order to 3. Then select the OK button. 

    8. Click Save on the Save directly to the master configuration dialog.

    9. Restart the WebSphere server.
  1. Grant appropriate permissions to the SAS Web Infrastructure Kit Web applications by adding a Java policy file to each deployed Web application. These applications require different permissions depending on how the applications are installed. To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files, which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.websphere.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.websphere.policy defines more restrictive security settings. This file should be used in a production environment.

    The remaining steps detail this process.

  1. If you configured your RMI server to run on localhost, and if you are using the sas.wik.websphere.policy file, then you will need to modify this file by locating the following lines in the grant section for the SAS Web Infrastructure Kit applications:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
Change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.websphere.policy file, additional permissions might be needed to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.

  1. Copy the appropriate policy file (either sas.wik.allpermissions.websphere.policy or sas.wik.websphere.policy) into the META-INF directory of the deployed Portal, SASStoredProcess, and SASPreferences Web applications. In the destination directory, assign the policy file the name was.policy.

    The Web applications are deployed into the following WebSphere directory:

    Note: For a Network Deployment environment, the was.policy file must be copied to both the Base and Deployment Manager profiles.

    AppServer\profiles\profileName\config\cells\hostNameCell01\applications
      \appName_war.ear\deployments\appName_war\META-INF

    where:

    • profileName is 'AppSrv01' for a Base environment and 'Dmgr01' for a Network Deployment.
    • hostName is the name of the host where WebSphere is installed.
    • appName is the name of the application WAR file.

    For example, deploying the Portal web application:

cd "C:\Program Files\SAS\Web\Portal2.0.1\SASServicesConfig"
copy sas.wik.allpermissions.websphere.policy
  C:\apps\WebSphere\AppServer\profiles\AppSvr01\config\cells\hostCell01\applications
  \Portal_war.ear\deployments\Portal_war\META-INF\was.policy

For a Network Deployment environment, you must also perform the following:

copy sas.wik.allpermissions.websphere.policy
  C:\apps\WebSphere\AppServer\profiles\Dmgr01\config\cells\hostCell01\applications
  \Portal_war.ear\deployments\Portal_war\META-INF\was.policy

Note: If you copy and paste this code, then you must remove the line breaks and spaces. Use this pattern for updating the policy file for the other applications.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:
    2. mkdir "C:\Program Files\SAS\Documentation\9.1\SASDoc"
    3. Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    4. Copy the sasdoc.websphere.permissions policy file into the META-INF directory of the deployed SASDoc Web application. In the destination directory, assign the policy file the name was.policy.

      The Web application is deployed into the following WebSphere directory:

      Note: For a Network Deployment environment, the was.policy file must be copied to both the Base and Deployment Manager profiles.

      AppServer\profiles\profileName\config\cells\hostNameCell01\applications
        \SASDoc_war.ear\deployments\SASDoc_war\META-INF

      where:

      • profileName is 'AppSrv01' for a Base environment and 'Dmgr01' for a Network Deployment.
      • hostName is the name of the host where WebSphere is installed.

      For example:

    cd "C:\Program Files\SAS\Documentation\9.1\SASDoc\WEB-INF"
    copy sas.wik.allpermissions.websphere.policy
      C:\apps\WebSphere\AppServer\profiles\AppSvr01\config\cells\hostCell01\applications
      \SASDoc_war.ear\deployments\SASDoc_war\META-INF\was.policy
    

    For a Network Deployment environment, you must also perform the following:

    copy sas.wik.allpermissions.websphere.policy
      C:\apps\WebSphere\AppServer\profiles\Dmgr01\config\cells\hostCell01\applications
      \SASDoc_war.ear\deployments\SASDoc_war\META-INF\was.policy
    

    Note: If you copy and paste this code, then you must remove the line breaks and spaces.

Unix Systems

Installation Tips for Apache Tomcat 4.1 on Unix Systems
  1. From the setup directory, run the tomcat_deploy.sh script to deploy files to the Tomcat webapps directory. This script is new to the 9.1.3 Service Pack 4 release. For example:
    cd /usr/local/SAS/Web/Portal2.0.1
    tomcat_deploy.sh
    
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    From the SAS Documentation setup directory that you specified when you ran the installation program, copy the SASDoc.war file to the Tomcat webapps directory. For example:
    cd /usr/local/SAS/Documentation/9.1
    cp SASDoc.war /usr/local/Tomcat4.1/webapps
    
  1. From the Tomcat directory, delete the following subdirectories, if they are present, and their contents.
    • webapps/SASDoc
    • work/Standalone/localhost/Portal
    • work/Standalone/localhost/SASStoredProcess
    • work/Standalone/localhost/SASPreferences
    • work/Standalone/localhost/SASTheme_default
    • work/Standalone/localhost/SASDoc

Installation Tips for BEA WebLogic 8.1 on Unix Systems
The SAS Web Infrastructure Kit requires WAR files to be deployed as exploded application archives. The following instructions describe how to explode the Web applications.

  1. First, create the directory for the exploded application archives to be moved to. For example:
    mkdir /usr/local/bea/webapps
    mkdir /usr/local/bea/webapps/SASTheme_default
    
    If you have not already installed the SASDoc Web application, then create the directory for that application. For example:
    mkdir /usr/local/bea/webapps/SASDoc
    
  1. From the setup directory, recursively copy the contents of the Portal, SASStoredProcess, and SASPreferences directories to the directories that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories. For example:
    cd /usr/local/SAS/Web/Portal2.0.1
    cp -r Portal           /usr/local/bea/webapps
    cp -r SASStoredProcess /usr/local/bea/webapps
    cp -r SASPreferences   /usr/local/bea/webapps
    
  1. Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASTheme_default.war file from the setup directory into the directory that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories.
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASDoc.war file from the SAS Documentation setup directory (which you specified when you ran the installation program) into the directory that you created in the previous step. This process is equivalent to exploding the Web applications in the target directories.
  1. Using the WebLogic console, deploy the exploded Web applications from the directories that you created in the previous steps, as follows:

    1. Start the WebLogic server. First, make sure that the startWebLogic.sh script has been used to start the administrative server. When the administrative server is in the RUNNING Mode, use the startManagedWebLogic.sh script to start the managed server. If the WebLogic Node Manager Service is installed and running, then you can start the managed server from the WebLogic console. For example:
      cd /usr/local/bea/user_projects/domains/mydomain
      startWebLogic.sh
      startManagedWebLogic.sh
      
    2. Point your browser to the console Web application (for example, http://localhost:7001/console).

    3. Log on using the account and password that you created in Step 3 (for example, weblogic and Weblogic123).

    4. Use Steps v through xi to deploy each of the following Web applications. The Web applications should be deployed in the same order that they appear on this list:

      1. SASTheme_default
      2. SASPreferences
      3. SASDoc
      4. Portal
      5. SASStoredProcess

    5. After you have logged on, use the tree on the left side of the console to navigate to the Web application deployment wizard (for example mydomain -> Deployments -> Web Application Modules).

    6. On the wizard's Configuration tab, select Deploy a new Web Application Module....

    7. Navigate to the /usr/local/bea/webapps directory.

    8. On the Deploy a Web Application Module screen, select the appropriate directory, and then select the Target Module button.

    9. On the next screen select the managed server that you created in Step 3, and then select the Continue button.

    10. On the next screen, select the Deploy button.

    11. Repeat Steps v, vi, vii, viii, ix, and x for each Web application.

  1. After all of the Web applications have been deployed, adjust the load order for the SASTheme_default application, as follows:

    1. Use the tree on the left side of the console to navigate back to the Web application deployment wizard (for example, mydomain -> Deployments -> Web Application Modules).

    2. Select the SASTheme_default Web application.

    3. Select the Configuration tab, and then select the General tab located below it.

    4. Change the Load Order to a value that is less than the load order assigned to the other Web applications (for example, 50). Then select the Apply button.

    5. Shut down the WebLogic server.

Installation Tips for IBM WebSphere 6.1 on Unix Systems
  1. Create a staging directory for the Web application archive files. For example:
    mkdir /usr/local/websphere/webapps
    
  1. From the setup directory, copy the Portal.war, SASStoredProcess.war, SASPreferences.war, and SASTheme_default.war files to the staging directory that you created in the previous step. For example:
    cd /usr/local/SAS/Web/Portal2.0.1
    cp Portal.war           /usr/local/websphere/webapps
    cp SASStoredProcess.war /usr/local/websphere/webapps
    cp SASPreferences.war   /usr/local/websphere/webapps
    cp SASTheme_default.war /usr/local/websphere/webapps
    
  1. If you have already installed the SASDoc Web application, then you can skip this step.

    From the SAS Documentation setup directory that you specified when you ran the installation program, copy the SASDoc.war file to the staging directory that you created in Step a. For example:
    cd /usr/local/SAS/Documentation/9.1
    cp SASDoc.war /usr/local/websphere/webapps
    
  1. Using the WebSphere Administrative Console, deploy the Web applications from the staging directory that you created in Step a, as follows:

    1. If needed, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. Use the Preparing for application installation wizard, as described in Steps v through xiv below, to deploy each of the following Web applications. The Web applications should be deployed in the order that they are listed here:

      1. SASTheme_default
      2. SASPreferences
      3. SASDoc
      4. Portal
      5. SASStoredProcess

    5. After you have logged on, use the tree on the left side of the console to navigate to the Preparing for application installation wizard (for example, Applications -> Install New Application).

    6. On the first screen, set the Local path (or Remote path for a remote server deployment) by using the browse button to navigate to the C:\apps\WebSphere\webapps directory and selecting the appropriate Web application.

    7. Set the Context Root to the name of the Web application (the filename without the .war extension), and then select the Next button.

    8. The next screen is step 1 of the Install New Application wizard. At steps 1 through 3, click on the Next button to accept the defaults. On step 4, click on the Finish button to accept the defaults.
    9. When this last step finishes (it takes a few minutes), you will see a link to Save directly to Master Configuration. Click on the link, then click on the Save button.
    10. Repeat Steps v, vi, vii, viii, and ix for each Web application.

  1. After all of the Web applications have been deployed, adjust the settings for the SASTheme_default, SASPreferences, and Portal Web applications as follows:

    1. Use the tree on the left side of the console to navigate to the Enterprise Applications wizard (for example, Applications -> Enterprise Applications).

    2. Select the SASTheme_default Web application link.

    3. Select Startup behavior and change the Startup order to 1. Then select the OK button.

    4. Select the SASPreferences Web application link.

    5. Select Startup behavior and change the Startup order to 2. Then select the OK button.

    6. Select the Portal Web application link.

    7. Select Startup behavior and change the Startup order to 3. Then select the OK button. 

    8. Click Save on the Save directly to the master configuration dialog.
    9. Restart the WebSphere server.
  1. Grant appropriate permissions to the SAS Web Infrastructure Kit Web applications by adding a Java policy file to each deployed Web application. These applications require different permissions depending on how the applications are installed. To help you get the Web applications running, the SAS Web Infrastructure Kit includes two policy files, which are located in the SASServicesConfig folder of the setup directory:

    • The file sas.wik.allpermissions.websphere.policy allows the Web applications to run without security restrictions. This file should be used during the initial installation.

    • The file sas.wik.websphere.policy defines more restrictive security settings. This file should be used in a production environment.

    The remaining steps detail this process.

  1. If you configured your RMI server to run on localhost, and if you are using the sas.wik.websphere.policy file, then you will need to modify this file by locating the following lines in the grant section for the SAS Web Infrastructure Kit applications:
// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
    "listen, connect, accept, resolve";
Change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.
  1. If you use the sas.wik.websphere.policy file, additional permissions might be needed to access some content. This content includes, but is not limited to, information maps in a distributed environment, stored processes running in a distributed environment, and syndication channels. For more information, see Adding Permissions to Policy Files in the SAS Web Infrastructure Kit: Administrator's Guide.

  1. Copy the appropriate policy file (either sas.wik.allpermissions.websphere.policy or sas.wik.websphere.policy) into the META-INF directory of the deployed Portal, SASStoredProcess, and SASPreferences Web applications. In the destination directory, assign the policy file the name was.policy.

    The Web applications are deployed into the following WebSphere directory:

    Note: For a Network Deployment environment, the was.policy file must be copied to both the Base and Deployment Manager profiles.

    AppServer/profiles/profileName/config/cells/hostNameCell01/applications
      /appName_war.ear/deployments/appName_war/META-INF

    where:

    • profileName is 'AppSrv01' for a Base environment and 'Dmgr01' for a Network Deployment.
    • hostName is the name of the host where WebSphere is installed.
    • appName is the name of the application WAR file.

    For example, deploying the Portal web application:

cd "/usr/local/SAS/Web/Portal2.0.1/SASServicesConfig"
copy sas.wik.allpermissions.websphere.policy
  /usr/local/websphere/AppServer/profiles/AppSvr01/config/cells/hostCell01/applications
  /Portal_war.ear/deployments/Portal_war/META-INF/was.policy

For a Network Deployment environment, you must also perform the following:

copy sas.wik.allpermissions.websphere.policy
  /usr/local/websphere/AppServer/profiles/Dmgr01/config/cells/hostCell01/applications
  /Portal_war.ear/deployments/Portal_war/META-INF/was.policy

Note: If you copy and paste this code, then you must remove the line breaks and spaces. Use this pattern for updating the policy file for the other applications.

  1. If you have already installed the SASDoc Web application, then you can skip this step.

    1. Create a SASDoc directory in the SAS Documentation setup directory (which you specified when you ran the installation program). For example:
    2. mkdir /usr/local/SAS/Documentation/9.1/SASDoc
    3. Using a tool such as the jar utility (if you have the J2SDK installed) or the unzip utility, unpack the SASDoc.war file (located in the SAS Documentation setup directory) into the directory that you created in the previous step.

    4. Copy the sasdoc.websphere.permissions policy file into the META-INF directory of the deployed SASDoc Web application. In the destination directory, assign the name was.policy to the policy file.

      The Web application is deployed into the following WebSphere directory:

    5. Copy the sasdoc.websphere.permissions policy file into the META-INF directory of the deployed SASDoc Web application. In the destination directory, assign the policy file the name was.policy.

      The Web application is deployed into the following WebSphere directory:

      Note: For a Network Deployment environment, the was.policy file must be copied to both the Base and Deployment Manager profiles.

      AppServer/profiles/profileName/config/cells/hostNameCell01/applications
        /SASDoc_war.ear/deployments/SASDoc_war/META-INF

      where:

      • profileName is 'AppSrv01' for a Base environment and 'Dmgr01' for a Network Deployment.
      • hostName is the name of the host where WebSphere is installed.

      For example:

    cd "/usr/local/SAS/Documentation/9.1/SASDoc/WEB-INF"
    copy sas.wik.allpermissions.websphere.policy
      /usr/local/websphere/AppServer/profiles/AppSvr01/config/cells/hostCell01/applications
      /SASDoc_war.ear/deployments/SASDoc_war/META-INF/was.policy
    

    For a Network Deployment environment, you must also perform the following:

    copy sas.wik.allpermissions.websphere.policy
      /usr/local/websphere/AppServer/profiles/Dmgr01/config/cells/hostCell01/applications
      /SASDoc_war.ear/deployments/SASDoc_war/META-INF/was.policy
    

    Note: If you copy and paste this code, then you must remove the line breaks and spaces.


Step 12: Make Graph Applets Available

Both the portal Web application shell and the stored process servlet use graph applets for some types of output. These applets must be available as /sasweb/graph from either the servlet container or the Web server that runs these applications. The following installation tips contain the procedures for each servlet container and system environment.

Windows Systems

Installation Tips for Apache Tomcat 4.1 on Windows Systems
  1. Tomcat includes a default Web application called ROOT which is used to serve Web content. In the Tomcat webapps\ROOT directory, create a sasweb directory. For example:
    mkdir C:\Tomcat4.1\webapps\ROOT\sasweb
    
  1. From the SAS Web Infrastructure Kit setup directory, recursively copy the contents of the sasweb directory to the directory that you created in the previous step. For example:
    cd "C:\Program Files\SAS\Web\Portal2.0.1"
    xcopy sasweb\*.* C:\Tomcat4.1\webapps\ROOT\sasweb /S
    

Installation Tips for BEA WebLogic 8.1 on Windows Systems
When you define a new server domain, BEA WebLogic does not create a default Web application for serving Web content. However, you can deploy the sasweb directory as an exploded application archive, as follows:
  1. Create a sasweb directory for the sasweb Web application. For example:
    mkdir C:\bea\webapps\sasweb
    
  1. From the SAS Web Infrastructure Kit setup directory, recursively copy the contents of the sasweb directory to the directory that you created in the previous step. For example:
    cd "C:\Program Files\SAS\Web\Portal2.0.1"
    xcopy sasweb\*.* C:\bea\webapps\sasweb /S
    
  1. Using the WebLogic console, deploy the exploded Web application as follows:

    1. Start the WebLogic server. First, make sure that the startWebLogic.cmd script has been used to start the administrative server. When the administrative server is in the RUNNING Mode, use the startManagedWebLogic.cmd script to start the managed server. If the WebLogic Node Manager Service is installed and running, then you can start the managed server from the WebLogic console. For example:
      cd \bea\user_projects\domains\mydomain
      startWebLogic.cmd
      startManagedWebLogic.cmd
      
    2. Point your browser to the console Web application (for example, http://localhost:7001/console).

    3. Log in using the account and password that you created in Step 3 (for example, weblogic and Weblogic123).

    4. After you have logged in, use the tree on the left side of the console to navigate to the Web application deployment wizard (for example mydomain -> Deployments -> Web Application Modules).

    5. Use the Deploy a new Web Application Module... link on the Configuration tab of the wizard to deploy the sasweb Web application.

    6. Navigate to the C:\bea\webapps directory.

    7. On the Deploy a Web Application Module screen, select sasweb. Then select the Target Module button.

    8. On the next screen, select the managed server that you created in Step 3, and then select the Continue button.

    9. On the next screen, select the Deploy button.

Installation Tips for IBM WebSphere 6.1 on Windows Systems
When you define a new server domain, IBM WebSphere does not create a default Web application for serving Web content . However, you can deploy the sasweb Web application as follows:
  1. From the setup directory, copy the sasweb.war file to the directory that you created in Step 11. For example:
    cd "C:\Program Files\SAS\Web\Portal2.0.1"
    copy sasweb.war C:\apps\WebSphere\webapps
    
  1. Using the WebSphere Administrative Console, deploy the Web applications from the directory that you created in the previous steps, as follows:

    1. If needed, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Preparing for application installation wizard (for example, Applications -> Install New Application).

    5. Use the wizard to deploy the sasweb Web application, as described in Steps vi through xv.

    6. On the first screen, set the Local path (or Server path for a network deployment) by using the browse button to navigate to the C:\apps\WebSphere\webapps directory and selecting the sasweb Web application.

    7. Set the Context Root to sasweb, and then select the Next button.

    8. The next screen is step 1 of the Install New Application wizard. At steps 1 through 3, click on the Next button to accept the defaults. On step 4, click on the Finish button to accept the defaults.

    9. When this last step finishes (it takes a few minutes), you will see a link to Save directly to Master Configuration. Click on the link, then click on the Save button.  
    10. Restart the WebSphere server.

Unix Systems

Installation Tips for Apache Tomcat 4.1 on Unix Systems
  1. Tomcat includes a default Web application called ROOT which is used to serve Web content. In the Tomcat webapps/ROOT directory, create a sasweb directory. For example:
    mkdir /usr/local/Tomcat4.1/webapps/ROOT/sasweb
    
  1. From the SAS Web Infrastructure Kit setup directory, recursively copy the contents of the sasweb directory to the directory that you created in the previous step. For example:
    cd /usr/local/SAS/Web/Portal2.0.1/sasweb
    cp -r * /usr/local/Tomcat4.1/webapps/ROOT/sasweb/
    

Installation Tips for BEA WebLogic 8.1 on Unix Systems
BEA WebLogic does not create a default Web application for serving Web content when you define a new server domain. However, you can deploy the sasweb directory as an exploded application archive as follows:
  1. In the directory that you created in Step 11, create a sasweb directory. For example:
    mkdir /usr/local/bea/webapps/sasweb
    
  1. From the SAS Web Infrastructure Kit setup directory, recursively copy the contents of the sasweb directory to the directory that you created in the previous step. For example:
    cd /usr/local/SAS/Web/Portal2.0.1/sasweb
    cp -r * /usr/local/bea/webapps/sasweb
    
  1. Use the WebLogic console to deploy the exploded Web application, as follows:

    1. Start the WebLogic server. First, make sure that the startWebLogic.sh script has been used to start the administrative server. When the administrative server is in the RUNNING Mode, use the startManagedWebLogic.sh script to start the managed server. If the WebLogic Node Manager Service is installed and running, then you can start the managed server from the WebLogic console. For example:
      cd /usr/local/bea/user_projects/domains/mydomain
      startWebLogic.sh
      startManagedWebLogic.sh
      
    2. Point your browser to the console Web application (for example, http://localhost:7001/console).

    3. Log in using the account and password that you created in Step 3 (for example, weblogic and Weblogic123).

    4. After you have logged on, use the tree on the left side of the console to navigate to the Web application deployment wizard (for example mydomain -> Deployments -> Web Application Modules).

    5. Use the Deploy a new Web Application Module... link on the Configuration tab of the wizard to deploy the sasweb Web application .

    6. Navigate to the /usr/local/bea/webapps directory.

    7. On the Deploy a Web Application Module screen, select sasweb, and then select the Target Module button.

    8. On the next screen, select the managed server that you created in Step 3, and then select the Continue button.

    9. On the next screen, select the Deploy button.

Installation Tips for IBM WebSphere 6.1 on Unix Systems
When you define a new server domain, IBM WebSphere does not create a default Web application for serving Web content . However, you can deploy the sasweb Web application as follows:
  1. From the setup directory, copy the sasweb.war file to the directory that you created in Step 11. For example:
    cd /usr/local/SAS/Web/Portal2.0.1
    cp sasweb.war /usr/local/websphere/webapps
    
  1. Using the WebSphere Administrative Console, deploy the Web applications from the directory that you created in the previous steps, as follows:

    1. If needed, start the WebSphere application server.

    2. Point your browser to the WebSphere Administrative Console Web application (for example, http://localhost:9060/ibm/console/).

    3. Log on to the WebSphere Administrative Console. By default, you do not need to enter an account and password.

    4. After you have logged on, use the tree on the left side of the console to navigate to the Preparing for application installation wizard (for example, Applications -> Install New Application).

    5. Use the wizard to deploy the sasweb Web application, as described in Steps vi through xv.

    6. On the first screen, set the Local path (or Server path for a network deployment) by using the browse button to navigate to the C:\apps\WebSphere\webapps directory and selecting the sasweb Web application.

    7. Set the Context Root to sasweb, and then select the Next button.

    8. The next screen is step 1 of the Install New Application wizard. At steps 1 through 3, click on the Next button to accept the defaults. On step 4, click on the Finish button to accept the defaults.

    9. When this last step finishes (it takes a few minutes), you will see a link to Save directly to Master Configuration. Click on the link, then click on the Save button.  
    10. Restart the WebSphere server.


Step 13: Set Up the SAS Services Application

The SAS Services application is a command line application that manages services that are shared by SAS applications. A script is provided to start this application. To run the script, follow the procedures for the appropriate system environment, as described below.

Windows Systems

On Windows systems, the start script StartRemoteServices.bat is located in the SASServices\WEB-INF subdirectory of the setup directory. You must be in the SASServices\WEB-INF subdirectory to run this script.

The SAS Services application runs with a Java security manager. To help you get the application running, the SAS Web Infrastructure Kit includes two policy files, which are located in the SASServicesConfig folder of the setup directory:

By default, the start script uses a copy of the sas.wik.allpermissions.sasservices.policy file. The configuration script that you ran in Step 6 placed this policy file in the RemoteServices subdirectory of the Foundation Services directory that you specified when you ran the installation program (for example, C:\Program Files\SAS\SASFoundationServices\Deployments\RemoteServices). To verify the path, check the value of the $SERVICES_DIR$ property in the install.properties file (located in the PortalConfigure subdirectory of the setup directory). To tighten security, edit the start script to use the sas.wik.sasservices.policy file.

If you use the sas.wik.sasservices.policy file, and if you configured your RMI server to run on localhost, then you must modify this file. In the grant section, locate the following lines:

// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
       "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
       "listen, connect, accept, resolve";

and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.

Note: SAS 9.1.3 and higher provides the capability to run the remote SAS Services application as a Windows service. This capability is enabled through the use of the Java Service Wrapper from Tunaki Software, which is provided with SAS Foundation Services. For more information, see Running Remotely Deployed Services as a Windows Service in the SAS Web Infrastructure Kit: Administrator's Guide.

Unix Systems

On Unix systems, the start script (StartRemoteServices.sh) is located in the SASServices/WEB-INF subdirectory of the setup directory. You must be in the SASServices/WEB-INF subdirectory to run this script.

The SAS Services application runs with a Java security manager. To help you get the application running, the SAS Web Infrastructure Kit includes provided two policy files, which are located in the SASServicesConfig folder of the setup directory:

By default, the start script uses a copy of the sas.wik.allpermissions.sasservices.policy file. The configuration script that you ran in Step 6 placed this file in the RemoteServices subdirectory of the Foundation Services directory that you specified when you ran the installation program (for example, /usr/local/SAS/SASFoundationServices/Deployments/RemoteServices). To verify the path, check the value of the $SERVICES_DIR$ property in the install.properties file (located in the PortalConfigure subdirectory of the setup directory). To tighten security, edit the start script to use the sas.wik.sasservices.policy file.

If you use the sas.wik.sasservices.policy file, and if you configured your RMI server to run on localhost, then you must modify this file. In the grant section, locate the following lines:

// RMI server - need both domain qualified machine name
     and localhost
permission java.net.SocketPermission "localhost:1024-",
        "listen, connect, accept, resolve";
permission java.net.SocketPermission "localhost:1024-",
        "listen, connect, accept, resolve";

and change one of the localhost values to the domain-qualified name of the machine where your RMI server is running.


Step 14: Start Servers

Because some servers depend on services that are provided by other servers, it is important to start the servers in the correct order. The dependencies are as follows:

Server Dependency
SAS Metadata Server none
Xythos WebFile Server none
SAS Stored Process Server SAS Metadata Server
SAS Workspace Server SAS Metadata Server
SAS Services Application SAS Metadata Server
Servlet Container / Application Server SAS Metadata Server, Xythos WebFile Server, SAS Stored Process Server, SAS Workspace Server, SAS Services Application

The metadata server should already be running from earlier steps. You must start the following additional servers in the order specified.

  1. Start the WebDAV server that you installed in Step 4.

  2. Use the script that you created in Step 9 to start the SAS Object Spawner.

  3. Start the SAS Services application that you installed in Step 13. You must start and initialize this application before you start the servlet container.

  4. Use the script that you created or modified in Step 10 to start the servlet container (which you installed in Step 3). If the servlet container is already running, then you must restart it at this time.


Step 15: Tune the Servlet Container

You should complete the following tuning steps in order to work around known servlet container bugs and to improve performance.

Installation Tips for Apache Tomcat 4.1
To work around a known problem with Apache Tomcat 4.1 commons logging, you must make sure that the Tomcat commons logging and log4j JAR files are the same version as those that were provided with SAS software. In addition, you must make sure that those JAR files are loaded in the same classloader. Follow these steps:
  1. Stop the Tomcat servlet container.

  2. Delete commons-logging-api.jar from the Tomcat common\lib directory. This JAR file contains an older version of the commons logging API that will not be needed after you complete the next step.

  3. Add the commons-logging.jar and log4j-1.2.3.jar files that are provided with the SAS Web Infrastructure Kit to the Tomcat common\lib directory.

    To perform this update, you can copy the Portal\WEB-INF\lib\commons-logging.jar and Portal\WEB-INF\lib\log4j-1.2.3.jar files from the SAS Web Infrastructure Kit setup directory into the Tomcat common\lib directory.

  4. Update the commons-logging.jar file in the Tomcat server\lib directory to the version that is provided with the SAS Web Infrastructure Kit.

    To perform this update, you can copy the Portal\WEB-INF\lib\commons-logging.jar file from the SAS Web Infrastructure Kit setup directory into the Tomcat server\lib directory.

  5. In each of the Web applications that were provided with the SAS Web Infrastructure Kit, remove the commons-logging.jar and log4j-1.2.3.jar files from the WEB-INF\lib directory.

  6. Use the script that you created or modified in Step 10 to start the servlet container that you installed in Step 3 .

Installation Tips for BEA WebLogic 8.1
If you are running in Development Mode, then the Web applications that you deployed in Step 11 have the Servlet Reload Check Secs and JSPPage Check Secs intervals set to 1 by default. To improve overall performance, you can set these values to a larger number; or you can set the values to -1 to disable the checks. Follow these steps:
  1. Point your browser to the BEA console Web application (for example, http://localhost:7001/console).

  2. Log in using the account and password that you created in Step 3 (for example, weblogic and Weblogic123).

  3. After you have logged on, use the tree on the left side of the console to navigate to each Web application (for example mydomain -> Deployments -> Web Application Modules -> Portal).

  4. Select the Descriptor tab in the Configuration wizard, and set the appropriate configuration values. Select the Apply button when you are finished.


Step 16: Access the Web Infrastructure Kit's Web Applications

Point your Web browser to the address of the Web application that you want to run. Cookies and Javascript support must be enabled on the browser in order for the applications to run. The default addresses for the SAS Web Infrastructure Kit Web applications are provided below.

Portal Web Application Shell

Installation Tips for Apache Tomcat 4.1
http://host/Portal

Installation Tips for BEA WebLogic 8.1
http://host:7100/Portal

Installation Tips for IBM WebSphere 6.1
http://host:9080/Portal

In the addresses that are listed above, host is the name of the machine where the servlet container is installed. If you are running your Web browser on the same machine as the servlet container, you can replace host with localhost.

The portal Web application shell should be displayed in the browser window with publicly available content. To view additional content, log on with a valid user ID and password. For example, if you used the defaults that were suggested in Step 7.a, then you can enter the user ID sasdemo and the password Demo123.

Stored Process Servlet

Installation Tips for Apache Tomcat 4.1
http://host/SASStoredProcess/Welcome.htm

Installation Tips for BEA WebLogic 8.1
http://host:7100/SASStoredProcess/Welcome.htm

Installation Tips for IBM WebSphere 6.1
http://host:9080/SASStoredProcess/Welcome.htm

In the addresses that are listed above, host is the name of the machine where the servlet container is installed. If you are running your Web browser on the same machine as the servlet container, you can replace host with localhost.

The stored process welcome page should be displayed in the browser window with options to run stored processes. To run a demonstration stored process, select the Stored Process Samples link, and select a stored process to run.



Copyright © 2005 SAS Institute Inc., Cary, NC, USA. All Rights Reserved.