Overview

1. Warnings and Notices
2. SAS Management Console
3. SAS Application Servers
4. SAS Spawners
5. SAS Table Server
6. SAS Deployment Tester Server
7. Remote Services
8. Web Application Server
9. SAS Web Applications
10. Web Application Custom Content
11. Completing Your Deployment
12. Obtaining Additional Information

Warnings and Notices

The following issues occurred during the automated portion of your configuration and must be addressed before proceeding.

• Some of the clients in your environment may need access to the SAS/GRAPH Java applets to view graphical output generated by SAS processes. If so, add the APPLETLOC option to the sasv9_usermods.cfg file located in each SAS Application Server context directory specifying the location to be used in generating graphical output. APPLETLOC should point to a network accessible copy of the SAS/GRAPH Java applets.

  Since your deployment includes the SAS Web Infrastructure Platform, the applets can be made available (you must use the correct host and port) via:

  -APPLETLOC "http://mid-tier-server:mid-tier-port/sasweb/graph"

• Permissions on the logs directory (/data/SASConfigManualM2/Lev1/Web/Logs) are currently set at 777. We strongly recommend that you narrow access to this directory. To facilitate creation of logs, make sure that the SAS Installer (sasinst) and the invoker of the Web application server can write to this directory. To facilitate appropriate use of the logs, make sure that administrators can see the directory.

• Because you selected to not automatically deploy your SAS Web Applications, you will need to perform some manual steps to complete the configuration of your SAS Web Applications. Once you have deployed the SAS Web Infrastructure Platform, you will need to manually load content to the SAS Content Server. Follow the instructions below to accomplish this.

SAS Management Console

SAS Management Console is required to complete many of the following steps.

SAS Application Servers

SASMeta - Metadata Server

Notes:

• The metadata server is configured to use journaling. The metadata journal file is located at /data/SASConfigManualM2/Lev1/SASMeta/MetadataServer/Journal/MetadataJournal.dat. The metadata journal file is updated more quickly than repositories and updated metadata becomes available to clients sooner. Journaling also improves the ability to recover the server and can be recovered from the state of the journal file when the metadata server is restarted.
• In the event of severe problems, the metadata server has been instructed to send alert e-mail to admin@example.com with the sender of the e-mail being identified as SASMeta - Metadata Server (SASConfigManualM2 - Lev1) <admin@example.com>.

SASApp - OLAP Server

SASApp - Stored Process Server

SASMeta - Workspace Server

Notes:

• The /data/SASConfigManualM2/Lev1/SASMeta/WorkspaceServer/Logs directory is intended to serve as a placeholder for workspace server logs. Workspace server logs may be directed to this directory in the event that your SAS or IT administrator enables logging. The following default attributes are associated with the Logs directory:
  • Universal read, write or execute access is disabled for the directory in order to comply with default installation security requirements
  • Execution of a workspace server does not populate the Logs directory
  • The Logs directory serves as a placeholder should you enable logging for workspace servers
  
  Enabling workspace server logging should be carefully considered, due to the proliferation of workspace server logs, as well as the requirement to grant universal write access to the Logs directory. To enable workspace server logging, perform the following steps:
  • Enable read, write and execute access to the Logs directory
  • Modify the workspace server logconfig.xml to enable the desired levels of logging
  • Alternately, enable the logconfig.trace.xml logging file to capture workspace server diagnostic logging

SASApp - Workspace Server

Notes:

• The /data/SASConfigManualM2/Lev1/SASApp/WorkspaceServer/Logs directory is intended to serve as a placeholder for workspace server logs. Workspace server logs may be directed to this directory in the event that your SAS or IT administrator enables logging. The following default attributes are associated with the Logs directory:
  • Universal read, write or execute access is disabled for the directory in order to comply with default installation security requirements
  • Execution of a workspace server does not populate the Logs directory
  • The Logs directory serves as a placeholder should you enable logging for workspace servers
  
  Enabling workspace server logging should be carefully considered, due to the proliferation of workspace server logs, as well as the requirement to grant universal write access to the Logs directory. To enable workspace server logging, perform the following steps:
  • Enable read, write and execute access to the Logs directory
  • Modify the workspace server logconfig.xml to enable the desired levels of logging
  • Alternately, enable the logconfig.trace.xml logging file to capture workspace server diagnostic logging

SAS BI Report Services Workspace Configuration

SAS BI Report Services 4.2

SASApp - Pooled Workspace Server

SASMeta - SAS DATA Step Batch Server

SAS Spawners

Object Spawner

SAS Table Server

SAS Deployment Tester Server

Notes:

• Deployment Tester Server is used to run tests on SAS products and servers to validate functionality and proper operation. The Deployment Tester Server in conjunction with the Deployment Tester SMC plug-in allows for tests to be executed on remote systems from a single SMC instance. Select Help on Deployment Tester in the SMC Help menu for more information.

Remote Services

Web Application Server

Configure your WebLogic Application Server (Domain Configuration)

The following instructions provide a basic WebLogic configuration that uses SAS authentication and unsecure connections. This configuration should support a small number of users. If you need to setup a more sophisticated topology that includes reverse proxy servers, web server authentication, single sign-on, or secure socket connections, please see the SAS 9.2 Intelligence Platform: Web Application Administration Guide at http://support.sas.com/92administration for additional details. Detailed configuration instructions on WebLogic are also available at the third-party vendor website located at http://edocs.bea.com/. Before configuring your WebLogic domain for SAS applications, be sure to review the WebLogic Post-Installation Steps if you have not already done so.

Since this is a manual configuration you will need to either create a new WebLogic domain or add servers to an existing one. You can create new domains or manage existing ones using the WebLogic Configuration Wizard. For your reference, a sample domain has been created. Depending on the SAS applications included in your plan, you will also need to configure other resources as listed below.

Sample Domain Location: /data/SASConfigManualM2/Lev1/Web/SASDomain

Configuration steps prior to starting WebLogic servers for your SAS domain:

• Set EnforceValidBasicAuthCredentials to False
  1. Locate and edit the config.xml file in your domain. It is located here:

     /data/SASConfigManualM2/Lev1/Web/SASDomain/config/config.xml

  2. Add the following line within the <security-configuration> element:

     <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

Configure Node Manager

There are several ways to manage the starting and stopping of WebLogic servers. If you wish to launch servers through the Weblogic Server Administration Console, you will need to configure and start a WebLogic Node Manager. You can also use scripts to launch the servers. The generated sample domain includes the appropriate scripts and configuration to support both methods.

The WebLogic Server installation provides scripts to launch Node Manager in /data/bea923sdw/weblogic92/server/bin. If you use these scripts to run a Node Manager that controls SAS domains, you will need to modify the script /data/bea923sdw/weblogic92/common/bin/commEnv.sh. The settings in this script affect all WebLogic domains running this version of WebLogic on this machine.

The sample SAS domain contains Node Manager scripts that call a wrapper script for commEnv.sh that provides the correct settings for the SAS domain. By adopting this SAS wrapper script and the modified scripts to start Node Manager provided in the SAS sample domain, you can launch a separate copy of Node Manager for your SAS domain without impacting other WebLogic domains running on the same machine. Alternatively, you can incorporate the settings found in /data/SASConfigManualM2/Lev1/Web/SASDomain/bin/commEnvSAS.sh into your WebLogic installation directly.

By default, the Node Manager home directory is located in the WebLogic install area. The scripts provided with the SAS sample domain set the location to /data/SASConfigManualM2/Lev1/Web/SASDomain/nodemanager. This prevents conflicts if other Node Managers are configured for non-SAS applications.

Start Node Manager

Be sure to read the section Configure Node Manager before launching the Node Manager. Depending on how you've chosen to configure your WebLogic installation and domain, you may choose to launch your own node manager script or the default script provided with WebLogic which is located at /data/bea923sdw/weblogic92/server/bin/startNodeManager.sh

You can start the process with nohup to allow it to continue running after you logout. Alternatively, you can run it as a daemon process.

Configure the WebLogic Administration Server (AdminServer)

There are no special SAS requirements for configuring the WebLogic Administration Server. Here are some of the configuration attributes for the sample domain:

• Listen Port: 7501
• Server Logs Directory: /data/SASConfigManualM2/Lev1/Web/SASDomain/servers/AdminServer/logs
• JVM Options: -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xms256m -Xmx512m -XX:PermSize=48m -XX:MaxPermSize=128m

Start the WebLogic Administration Server

To start the Administration Server for your domain, execute the startWebLogic.sh. For the sample domain, the script is located here: /data/SASConfigManualM2/Lev1/Web/SASDomain/bin/bin/startWebLogic.sh

Configuration steps to be performed from the WebLogic Administration Console:

Once the administration server is started, the remaining steps can be performed from the WebLogic Administration Console.

• Ensure that Tunneling is enabled (TunnelingEnabled is set to true)
1. In the Domain Structure panel, go to Environment -> Servers.
2. On the Summary of Servers page, select the link AdminServer(admin).
3. On the Settings for AdminServer page, select the Protocols tab.
4. Select the Enable Tunneling checkbox.

Configure the WebLogic Managed Servers

There are two ways to launch the WebLogic Managed Servers. You can use the WebLogic Administration Console or batch scripts. These servers must be launched with the appropriate command line options. You will need to perform configuration steps to setup both methods.

• Configure Managed Servers through the WebLogic Administration Console

  For each managed server listed below, perform these instructions:

  1. In the Domain Structure panel, go to Environment -> Servers.
  2. On the Summary of Servers page, select the link for the Managed Server to be configured.
  3. On the "Settings for SASServerN" page, select the link Server Start tab.
  4. Paste the JVM Options listed below for the appropriate server into the Arguments text box.
• Configure Managed Server Scripts
  1. Locate and edit the file setDomainEnv.sh for your domain. Also, look at the copy in the sample domain:

     /data/SASConfigManualM2/Lev1/Web/SASDomain/bin/bin/setDomainEnv.sh

  2. In the sample domain version of setDomainEnv.sh, you will find SAS code between two sets of comments. You should copy this code into the equivalent location in your domain's copy of setDomainEnv.sh:

     # set the following for SAS installs
     ...
     # end set for SAS installs 

WebLogic Managed Server Configuration Properties:

WebLogic Managed Server - SASServer1

WebLogic Managed Server - SASServer2

Configure MailSession - SASMailSession

Using the WebLogic Administration Console, create a mail session.

1. In the Domain Structure panel, go to Services -> Mail Sessions.
2. Click the New button.
3. Enter the name SASMailSession in the Name field, and click OK.
4. Select the link SASMailSession.
5. In the JNDI Name field, enter sas/mail/Session.
6. In the JavaMail Properties text area, enter the following lines and then save the changes:

   mail.debug=false
   mail.transport.protocol=smtp
   mail.smtp.host=mailhost.example.com
   

7. Select the Targets tab.
8. Select the checkbox for all configured managed servers (but not AdminServer).

Configure JMS Server - SASJMSServer1

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Servers.
2. Click New
.
3. On the JMS Server Properties page, enter SASJMSServer1 in the Name field; then click Next.
4. On the Select targets page, set the Target to SASServer1, and click Finish.

Define JMS Module - sasJmsSystemResource

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click New.
3. On the properties page, set the Name to sasJmsSystemResource, and set the Descriptor File Name to jms/sasjmssystemresource-jms.xml; then click Next.
4. On the targets page, select SASServer1, and click Next.
5. On the Add resources to this JMS system module page, click Finish.

Create a SubDeployment (SASJMSServer1SubDeployment) for the JMS Module (sasJmsSystemResource)

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. Select the Subdeployments tab.
4. Click New.
5. Enter the name SASJMSServer1SubDeployment in the Subdeployment Name field and click Next.
6. In the Targets page, select SASJMSServer1, and click Finish.

Create JMS Connection Factory - SASTopicConnectionFactory

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the Create a New JMS System Module Resource page, select Connection Factory, and click Next.
5. On the ConnectionFactory Properties page, set the Name to SASTopicConnectionFactory, and set the JNDI Name to sas/jms/TopicConnectionFactory, and click Next.
6. On the targets page, click Advanced Targeting.
7. On the next page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Create JMS Connection Factory - SASQueueConnectionFactory

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the Create a New JMS System Module Resource page, select Connection Factory, and click Next.
5. On the ConnectionFactory Properties page, set the Name to SASQueueConnectionFactory, and set the JNDI Name to sas/jms/QueueConnectionFactory, and click Next.
6. On the targets page, click Advanced Targeting.
7. On the next page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Create JMS Queue - AlertQueue

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the next page, select Queue, and click Next.
5. Enter AlertQueue in the Name field and the string sas/jms/AlertQueue in the JNDI Name field. Then click Next.
6. On the properties page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Create JMS Queue - WorkflowQueue

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the next page, select Queue, and click Next.
5. Enter WorkflowQueue in the Name field and the string sas/jms/WorkflowQueue in the JNDI Name field. Then click Next.
6. On the properties page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Create JMS Queue - WorkflowCommandQueue

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the next page, select Queue, and click Next.
5. Enter WorkflowCommandQueue in the Name field and the string sas/jms/WorkflowCommandQueue in the JNDI Name field. Then click Next.
6. On the properties page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Create JMS Queue - WorkflowEventsQueue

1. In the Domain Structure panel, go to Services -> Messaging -> JMS Modules.
2. Click the link sasJmsSystemResource.
3. On the Summary of Resources page, click New.
4. On the next page, select Queue, and click Next.
5. Enter WorkflowEventsQueue in the Name field and the string sas/jms/app/WorkflowEventsQueue in the JNDI Name field. Then click Next.
6. On the properties page, select the subdeployment SASJMSServer1SubDeployment, and click Finish.

Configure JDBC Driver - com.sas.tkts.TKTSDriver for (SharedServices)

1. Copy the jars located in ${tableserver.temp.dir} to your domain lib directory. For the sample domain, this location is /data/SASConfigManualM2/Lev1/Web/SASDomain/lib
2. Restart the WebLogic Administration Server and the Node Manager. If any managed servers were already running, they should also be restarted.

Configure Data Source - SharedServices

1. In the Domain Structure panel, go to Services -> JDBC -> Data Sources.
2. Click New.
3. On the page JDBC Data Source Properties enter the following values:
   • Name: SharedServices
   • JNDI Name: sas/jdbc/SharedServices
   • Database Type: Other
   Then click Next.
4. On the page Transaction Options, click Next.
5. On the page Connection Properties, enter the following values:
   • Database Name: SharedServices
   • Host Name: HOSTNAME.example.com.
   • Port: 2171.
   • Database User Name: sastrust@saspw.
   • Password and Confirm Password: Enter the password for sastrust@saspw.
   Click Next.
6. On the Test Database Connection page, enter the following values:
   • Driver Class Name: com.sas.tkts.TKTSDriver
   • URL: jdbc:sastkts://HOSTNAME.example.com:2171
   • Properties:

     user=sastrust@saspw
     stmtPooling=0 constring=(DSN=SharedServices)

7. The other values don't require changes. Click Next.
8. On the Select Targets page, select the server SASServer1.
9. Click Finish.

Securing Your WebLogic Domain

The sample WebLogic Domain that was created by SDW has been secured with file permissions that only allow access by the installer user (sasinst). This means that other users cannot change into the domain directory and can't execute scripts in the domain bin directory. You may wish to employ similar security settings in your production domain.

Also, consider that log files and other files created and managed by the WebLogic server processes may be readable by others. If you wish to lock these files, you will need to use the Unix umask command to ensure that files are created with appropriate access rights. If you wish to make files in the WebLogic domain accessable to others, we recommend restricting access to a controlled group.

Start the WebLogic Managed Servers

• Starting the managed servers using scripts

  The startup scripts are located in your domain's bin directory. Enter the following command:

  /data/SASConfigManualM2/Lev1/Web/SASDomain/bin/startManagedWebLogic.sh ServerName t3://HOSTNAME.example.com:7501

• Starting the managed server using the WebLogic Administration Console

  1. In the Domain Structure panel, go to Environment -> Servers.
  2. On the Summary of Servers page, select the name of the targeted server.
  3. Select the Control tab.
  4. Select the Start button.

Configure Foreign JNDI Provider

1. In the Domain Structure panel, go to Services -> Foreign JNDI Providers.
2. Click New.
3. On the page Create a Foreign JNDI Provider enter the name SharedServicesJNDIProvider
and then click OK.
4. On the page Summary of Foreign JNDI Providers, select SharedServicesJNDIProvider.
5. On the page Settings for SharedServicesJNDIProvider enter the following values:
   • Initial Context Factory: SharedServicesJNDIProvider
   • Provider URL: SharedServicesJNDIProvider
   • Leave the remaining fields blank.
   • Select the links tab.
   • For each symbol in the table below, do the following:
   1. Select New
   2. On the Create a Foreign JNDI Link page, edit the fields to match a row in the table below.
   3. Select OK

Deploying Applications on WebLogic Application Server

The directory /data/SASConfigManualM2/Lev1/Web/Staging contains deployable EAR files and a sub-directory called exploded. Please use the exploded location to deploy all the applications that exist there. Those applications that do not exist in the exploded directory may be deployed as EAR files. To deploy the SAS applications with the WebLogic Administration Console, perform the following steps for each application in the table below:

1. In the Domain Structure panel, go to Deployments.
2. Click Install
3. You could walk through the directory structure to locate the application EAR file from the Install Application Assistant page, however it is easier to click on the link labeled upload your files and then select the path to the ear from the table below and enter it into the Deployment Archive field on the next screen.
4. Select the application Ear file and then select Next.
5. Select Install this deployment as an application then select Next.
6. Select the recommended target from the table below and then select Next.
7. In the Name field, enter the name of the EAR from the table below. Note that the default value will include the name up to the first period in the Ear name, which will always be sas.
8. Select Finish.

SAS Web Applications

SAS Themes

SAS Web Infrastructure Platform

SAS Content Server

SAS Stored Process Web Application

SAS Web Report Studio

SAS Web OLAP Viewer for Java

SAS Information Delivery Portal

Notes:

• The SAS Portlets are located at: /data/SASConfigManualM2/Lev1/Web/Applications/SASPortlets4.2/Deployed
• If your network has a proxy server, you must specify the following parameters on the Application Server start-up command so that syndication channels and the URL Display Portlet can access content outside of your network.
  • -Dhttp.proxyHost=host
  • -Dhttp.proxyPort=port

SAS Shared Services

Notes:

SAS BI Dashboard 4.2

Notes:

• The SAS BI Dashboard 4.2 sample files are located at: /data/SAS92M2/SASBIDashboard/4.2/SampleData. Please refer the sample files install guide for more information.

SAS Help Viewer Metadata Configuration

Web Application Custom Content

If you wish to add custom content into SAS web applications, you may do so by placing your custom content into the appropriate custom content directory structure for the given application, and then running the SAS Deployment Manager to rebuild web applications. The custom content root directory for a given web application is

/data/SASConfigManualM2/Lev1/Web/Common/Server Name/Application Name/CustomContent

For example,

/data/SASConfigManualM2/Lev1/Web/Common/SASServer1/SASWebReportStudio4.2/CustomContent

Within that directory, there are subdirectories (for example, ears or wars) corresponding to specific archive types (ear and war files, respectively). Under the archive type directories, there are subdirectories for each specific archive—these are the root directories for each archive within the application. Custom content should be placed in the archive's directory tree corresponding to where the content should appear within the archive.

For example, to add the ear_addon.xml file into the addons directory in the sas.webreportstudio ear file, create the

.../CustomContent/ears/sas.webreportstudio/addons

directory, and place ear_addon.xml in it. Our process knows which war files are contained within ear files, so if you want to add war_addon.jar into the WEB-INF/lib directory in the sas.webreportstudio war file within the sas.webreportstudio ear file, then create

.../CustomContent/wars/sas.webreportstudio/WEB-INF/lib

directory, and place war_addon.jar in it.

Once all your custom content is ready to be consumed, run the SAS Deployment Manager and choose to rebuild web applications. Doing so will rebuild the web applications, inserting the custom content into the archives under the appropriate paths. Note that if custom content has the same path and name of content normally included in the archive, then the custom content takes precedence.

Completing Your Deployment

In order to complete your deployment on this machine, certain manual steps have to be performed. The SAS Content Server must be running before you attempt these steps.

Loading Content to the SAS Content Server

• Since you selected to not automatically deploy your SAS Web Applications, manual steps are required to ensure the proper content is loaded to the SAS Content Server. The file, /data/SASConfigManualM2/Lev1/Web/Utilities/manualLoadContent.sh, has been created to facilitate this process.

• Execute /data/SASConfigManualM2/Lev1/Web/Utilities/manualLoadContent.sh to automatically load content for the SAS Web Applications that require it.

The steps detailed above resulted in the creation of log files, which can be found in /data/SASConfigManualM2/Lev1/Logs/Configure. Review the contents of the scripts you executed for the name of the log files that were created. Review these logs and make sure there were no errors. Each execution of these scripts results in the logs from previous executions being overwritten. Therefore, prior to rerunning these scripts, you may wish to make appropriate backups of the logs.

These manual steps required the use of the SAS Administrator account. The scripts contain the SAS Administrator's credentials with the password encrypted at the sas002 level. The scripts are not intended for further use once your deployment is complete. Since these scripts contain the SAS Administrator's credentials, it is highly recommended that you delete them once your deployment is complete.

Obtaining Additional Information

Additional SAS Intelligence Platform documentation is available from the SAS 9.2 administration documentation web site.

There may be additional configuration steps required for your SAS Foundation software. Consult the SAS Foundation Configuration instructions available for your operating system for product-specific post-installation steps. The configuration instructions are available from the SAS Install Center web site.

Backing up your SAS Metadata Server

After completing your SAS Intelligence Platform configuration, we strongly recommend that you create a backup of your newly configured SAS Metadata Server. If you have adequate disk space to accommodate a copy of all of your metadata repositories on the metadata server host, use the MetadataServer.sh script provided in the /data/SASConfigManualM2/Lev1/SASMeta/MetadataServer directory. To execute the script, type:

./MetadataServer.sh backup

The script copies all critical metadata server files to a SASBackup subdirectory of the MetadataServer directory.

If disk space is an issue, then use the SAS Backup wizard provided in the SAS Management Console Metadata Manager or the %OMABAKUP macro to perform the backup. Both of these tools copy all critical metadata server files and permit you to specify a different backup destination. For more information, see "About the Backup Wizard" and "About %OMABAKUP" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/92administration.

Regular metadata server backups using SAS backup tools are crucial to ensuring the health of your SAS 9.2 Intelligence Platform configuration, but they are just one part of backing up a SAS Intelligence Platform configuration. To devise a backup strategy for your entire SAS Intelligence Platform configuration, see "Best Practices for Backing Up and Restoring Your System" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/92administration.

Copyright © 2008-9 SAS Institute Inc., Cary, NC, USA. All Rights Reserved.