Configuration Guidelines and Details for "HOSTNAME"

Overview

Warnings and Notices
SAS Management Console
SAS Application Servers
SAS Spawners
SAS Framework Data Server
SAS/SHARE Server
SAS Deployment Tester Server
Operating System Services Scheduling Server
SAS BI Lineage Scheduling Server
SAS Web Infrastructure Platform Scheduling Services
Remote Services
Web Application Server
SAS Web Applications
Web Application Custom Content
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"
```
The default ports are:
JBoss: 8080
WebLogic: 7001
WebSphere: 9080
You indicated that security policies could be modified by the SAS Deployment Wizard. As a result, the user HOSTNAME\sasdemo was granted the local security policy Log on as a batch job (SeBatchLogonRight). This policy allows a user to be logged on by means of a batch-queue facility and is required when this account is used with SASApp - Workspace Server.

The policy will take effect the next time HOSTNAME\sasdemo authenticates against the operating system. Therefore, if HOSTNAME\sasdemo is currently logged on to the system, a reboot will be needed for this policy to take effect.
You indicated that security policies could be modified by the SAS Deployment Wizard. As a result, the user HOSTNAME\sasdemo was granted the local security policy Log on as a batch job (SeBatchLogonRight). This policy allows a user to be logged on by means of a batch-queue facility and is required when this account is used with SASMeta - Workspace Server.

The policy will take effect the next time HOSTNAME\sasdemo authenticates against the operating system. Therefore, if HOSTNAME\sasdemo is currently logged on to the system, a reboot will be needed for this policy to take effect.

SAS Management Console

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

Shortcut	Programs > SAS > SAS Management Console 9.3
User ID	SAS Administrator user ID
Password	Enter the password you created in the SAS Deployment Wizard.

SAS Application Servers

SASMeta - Metadata Server

Host machine	HOSTNAME.example.com
Port	8561
Log directory	C:\SAS\EBIEDIEG\Lev1\SASMeta\MetadataServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Execution type	Windows service SAS [EBIEDIEG-Lev1] SASMeta - Metadata Server
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1

Notes:

The metadata server is configured to perform unassisted metadata server backups. The backups are performed at 1 a.m. server-local time and stored in the C:\SAS\EBIEDIEG\Lev1\SASMeta\MetadataServer\Backups directory. Backups are retained for seven days. To learn about the metadata server backup facility, see "Backing Up the SAS Metadata Server" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
The metadata server is configured to use journaling. The journal is a high-speed disk file that is used in conjunction with the new server backup facility to support unassisted metadata server backups and provide roll-forward recovery of transactions beyond a backup to a specified point in time.
The metadata server is configured to send an alert e-mail message to noreply@localhost in the event of a system, backup, or recovery failure. You can test that the alert-email notification subsystem is configured properly by opening the active metadata server's Properties sheet in the SAS Management Console Metadata Manager and sending a test message. If the system is configured properly, you will receive a test e-mail from SASMeta - Metadata Server EBIEDIEG - Lev1 <noreply@localhost>. To change or add an alert e-mail recipient, you must modify the value of the option in the omaconfig.xml file. Aftering editing the file, you must stop and restart the metadata server for the change to take effect.

SASApp - Connect Server

Validation steps

In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.
Expand SASApp.
Expand SASApp - Logical Connect Server.
Highlight the SASApp - Connect Server.
Right mouse click this server and select Validate (you can enter HOSTNAME\sasdemo or the SAS Spawned Servers account for the user ID). You should see a Validation Successful message.

SASApp - OLAP Server

Host machine	HOSTNAME.example.com
Port	5451
Log directory	C:\SAS\EBIEDIEG\Lev1\SASApp\OLAPServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Expand SASApp. Highlight the SASApp - Logical OLAP Server. Right mouse click this server and select Validate. You should see a Validation Successful message.
Execution type	Windows service SAS [EBIEDIEG-Lev1] SASApp - OLAP Server
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1

SASApp - Stored Process Server

Host machine	HOSTNAME.example.com
Port	8601
Log directory	C:\SAS\EBIEDIEG\Lev1\SASApp\StoredProcessServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Expand SASApp. Highlight the SASApp - Logical Stored Process Server. Right mouse click this server and select Validate. You should see a Validation Successful message.

SASMeta - Workspace Server

Host machine	HOSTNAME.example.com
Validation steps	The SASMeta - Workspace Server should be used for only a few designated administrative tasks. It is appropriate to defer validation of this server until you have set up the SAS users who will perform these tasks. This server requires an external account and is available to only the SAS Administrators group.

Notes:

The C:\SAS\EBIEDIEG\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

Host machine	HOSTNAME.example.com
Port	8591
Log directory	C:\SAS\EBIEDIEG\Lev1\SASApp\WorkspaceServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Expand SASApp. Highlight the SASApp - Logical Workspace Server. Right mouse click this server and select Validate (you can enter HOSTNAME\sasdemo or the SAS Spawned Servers account for the user ID). You should see a Validation Successful message.

Notes:

The C:\SAS\EBIEDIEG\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

Query Cache Library

Name ="SASApp - wrstemp"

In SAS Management Console, on the Plug-ins tab, select the "+" to expand the Data Library Manager node.
Select "+" to expand Libraries.
Select the library listed above.
Right mouse click this library and select Properties.
Click the Options tab and locate the path to the library in the Selected items text box.

Review the documentation provided to determine if permissions need to be modified for the library or directory to which the library points.

For details, view the http://support.sas.com/93administration and refer to the document called SAS Intelligence Platform 9.3: Web Application Administration Guide.
See the section called Improving the Performance of SAS Web Report Studio.
This section will contain a list of Suggestions for Improving the Performance of SAS Web Report Studio. Go to the information titled "Using the Query Cache".
Refer to the subsection called Security Considerations for the Query Cache Libraries for information regarding permissions.

Distribution Library

Name ="SASApp - wrsdist"

In SAS Management Console, on the Plug-ins tab, select the "+" to expand the Data Library Manager node.
Select "+" to expand Libraries.
Select the library listed above.
Right mouse click this library and select Properties.
Click the Options tab and locate the path to the library in the Selected items text box.

Review the documentation provided to determine if permissions need to be modified for the library or directory to which the library points.

For details, view the http://support.sas.com/93administration and refer to the document called SAS Intelligence Platform 9.3: Web Application Administration Guide.
See the section called Pre-generated Reports From SAS Web Report Studio.
Refer to the subsection called Verifying Permissions for the Distribution Library for information regarding permissions.

Validation steps

In SAS Management Console, on the Plug-ins tab, select "+" to expand the Data Library Manager node.
Verify the libraries named above are listed under the Data Library Manager.
In SAS Management Console, on the Plug-ins tab, select "+" to expand the Application Management node.
Select "+" to expand the Configuration Manager
Highlight BI Rep Svc Wkspace Config 4.3
Right mouse click and select Properties.
Click the Settings tab.
Validate the query cache library and the distribution library. They should match the libraries listed under Data Libraries.

SAS BI Report Services

Log directory	C:\SAS\EBIEDIEG\Lev1\Applications\SASBIReportServices4.3\Logs For more details about how to modify your log format and to see what logging entails, see the SAS Intelligence Platform 9.3: Web Application Administration Guide at http://support.sas.com/93administration.
Java Batch Server	Name ="SASApp - BRM Java Batch Server"
Configuration	Configuration Directory = "C:\SAS\EBIEDIEG\Lev1\Applications\SASBIReportServices4.3"
Validation steps	Java Batch Server In SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Select "+" to expand SASApp. Select "+" to expand the SASApp - Logical SAS Java Batch Server. Verify the existence of the java batch server(s) referenced above. Right mouse click this server and select Properties. Click the Options tab. Validate the command line by examining the parameter values and verifying file locations and the repository name. Local Services In SAS Management Console, on the Plug-ins tab, select "+" to expand the Foundation Services Manager node. Select "+" to expand the SASBIReportServices4.3 Local Services Definition. Select "+" to expand Core. Select the Logging Service. Right mouse button and choose Properties. Click the Service Configuration tab. Click the Configuration button. Verify the logging contexts. Refer to the logging documentation at the link specified above for details. outputgen.ini file The file outputgen.ini may need to be modified. This file is located in the install folder C:\Program Files\SASHome\SASBIReportServices\4.31. The following default settings for Java command line options appear in this file: java.net.preferIPv4Stack=true and java.net.preferIPv6Addresses=false. If the system is configured to use IPv6, these values must be changed to: java.net.preferIPv4Stack=false and java.net.preferIPv6Addresses=true.

SASApp - Pooled Workspace Server

Host machine	HOSTNAME.example.com
Port	8701
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Expand SASApp. Highlight the SASApp - Logical Pooled Workspace Server. Right mouse click this server and select Validate. You should see a Validation Successful message.

SASMeta - SAS DATA Step Batch Server

Host machine	HOSTNAME.example.com
Log directory	C:\SAS\EBIEDIEG\Lev1\SASMeta\BatchServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	Select this link: C:\SAS\EBIEDIEG\Lev1\SASMeta\BatchServer\sasbatch.bat If SAS starts successfully, the DATA step batch server has been validated.

SASApp - SAS DATA Step Batch Server

Host machine	HOSTNAME.example.com
Log directory	C:\SAS\EBIEDIEG\Lev1\SASApp\BatchServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	Select this link: C:\SAS\EBIEDIEG\Lev1\SASApp\BatchServer\sasbatch.bat If SAS starts successfully, the DATA step batch server has been validated.

SAS Spawners

Object Spawner

Host machine	HOSTNAME.example.com
Port	8581
Log directory	C:\SAS\EBIEDIEG\Lev1\ObjectSpawner\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Execution type	Windows service SAS [EBIEDIEG-Lev1] Object Spawner
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1

Connect Spawner

Host machine	HOSTNAME.example.com
Ports	7551
Log directory	C:\SAS\EBIEDIEG\Lev1\SASApp\ConnectServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Execution type	Windows service SAS [EBIEDIEG-Lev1] Connect Spawner
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1

SAS/SHARE Server

Host machine	HOSTNAME.example.com
Port	8551
Log directory	C:\SAS\EBIEDIEG\Lev1\ShareServer\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Execution type	Windows service SAS [EBIEDIEG-Lev1] Share Server
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1

SAS Framework Data Server

Host machine	HOSTNAME.example.com
Port	22031
Log directory	C:\SAS\EBIEDIEG\Lev1\FrameworkServer\dffedsvrcfg\Logs For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/93administration.
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Expand FrameworkServer - Logical SAS Framework Data Server. Highlight the FrameworkServer - SAS Framework Data Server. Right mouse click this server and select Validate. You should see a Validation Successful message.
Execution type	Windows service SAS [EBIEDIEG-Lev1] FrameworkServer - SAS Framework Data Server
Shortcuts	Programs > SAS > SAS Configuration > EBIEDIEG - Lev1

SAS Deployment Tester Server

Host machine	HOSTNAME.example.com
Port	10021
Execution type	Windows service SAS [EBIEDIEG-Lev1] Deployment Tester Server
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1
Validation steps	In SAS Management Console, on the Plug-ins tab, select "+" to expand the Application Management node. Select "+" to expand Deployment Tester Highlight the host machine: HOSTNAME.example.com Right mouse click and select Run All Test Suites. Select "+" to expand the Results. Validate the results for each test suite. All tests should pass. If you are prompted for credentials, select the "Help" button in the Credentials dialog box to display the accounts that can be used for each test suite.

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 SASMC plug-in allows for tests to be executed on remote systems from a single SASMC instance.
When you are done validating your deployment with SAS Deployment Tester, the Deployment Tester Server can safely be shut down without affecting the rest of your SAS deployment. Deployment Tester Server is a stand-alone server, independent of the rest of SAS, that can be started and used periodically to verify the health of your SAS deployment. You should consider verifying the health of your SAS deployment after initial installation, after applying maintenance and hot fixes, or when you make any other significant changes to the deployment.
More detailed information on validating your SAS deployment with Deployment Tester can be found in the "Using the Deployment Tester" section of the SAS 9.3 Intelligence Platform: System Administration Guide, which is available at http://www.support.sas.com/93administration.

Operating System Services Scheduling Server

Host machine	HOSTNAME.example.com
Port	8451
Log directory	C:\SAS\EBIEDIEG\Lev1\SchedulingServer\Logs
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Highlight Operating System Services - HOSTNAME.example.com. Right mouse click this server and select Validate (you can enter HOSTNAME\sasdemo or the SAS Spawned Servers account for the user ID). You should see a Validation Successful message.

SAS BI Lineage Scheduling Server

Java Batch Server

Name = "SASApp - BIL Java Batch Server"

Configuration

Configuration Directory = "C:\SAS\EBIEDIEG\Lev1\Applications\SASBILineage4.3"

Validation steps

Java Batch Server

In SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.
Select "+" to expand SASApp.
Select "+" to expand the SASApp - Logical SAS Java Batch Server.
Verify the existence of the Java batch server referenced above.
Right mouse click this server and select Properties.
Click the Options tab.
Validate the command line.

ScanDriver.bat file

Verify the existence of the file ScanDriver.bat. This file is located in the configuration folder C:\SAS\EBIEDIEG\Lev1\Applications\SASBILineage4.3.

Software Component

In SAS Management Console, on the Folders tab, select "+" to expand the System folder.
Select "+" to expand the Applications folder.
Select "+" to expand the SAS BI Lineage Scheduling Server folder.
Verify the existence of the BI Lineage Sched Svr 4.3 software component.

SAS Web Infrastructure Platform Scheduling Services

Log directory	C:\SAS\EBIEDIEG\Lev1\Web\Logs
JES Java Batch Server	Name = "SASApp - JES Java Batch Server"
Configuration	Configuration Directory = "C:\SAS\EBIEDIEG\Lev1\Web\Applications\SASWIPSchedulingServices9.3" Deployment Directory = "C:\SAS\EBIEDIEG\Lev1\WIPSchedBatch"
Validation steps	JES Java Batch Server In SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Select "+" to expand SASApp. Select "+" to expand the SASApp - Logical SAS Java Batch Server. Verify the existence of the java batch server(s) referenced above. Right mouse click this server and select Properties. Click the Options tab. Validate that the command line and arguments are appropriate for this java batch server. servicetrigger.ini file The file servicetrigger.ini may need to be modified. This file is located in the install folder C:\Program Files\SASHome\SASWebInfrastructurePlatformSchedulingServices\9.3. The following default settings for Java command line options appear in this file: java.net.preferIPv4Stack=true and java.net.preferIPv6Addresses=false. If the system is configured to use IPv6, these values must be changed to: java.net.preferIPv4Stack=false and java.net.preferIPv6Addresses=true.

Remote Services

Host machine	HOSTNAME.example.com
Port	5091
Execution type	Windows service SAS [EBIEDIEG-Lev1] Remote Services
Shortcuts	Programs > SAS > Configuration > EBIEDIEG - Lev1
Validation steps	Execute 'C:\SAS\EBIEDIEG\Lev1\Web\Applications\RemoteServices\RemoteServices.bat status' and verify that the 'STATE' is 'RUNNING'. Execute the Deployment Tester plug-in to the SAS Management Console to validate the configuration, deployment and usage of the Remote Services application.

Notes:

A shortcut has been created to start SAS Remote Services and can be found in your Start Menu at: Programs > SAS > Configuration > EBIEDIEG - Lev1 > Remote Services - Start
A shortcut has been created to stop SAS Remote Services and can be found in your Start Menu at: Programs > SAS > Configuration > EBIEDIEG - Lev1 > Remote Services - Stop

Web Application Server

Host machine	HOSTNAME.example.com
Application Server Vendor	IBM
Application Server Name	WebSphere
WebSphere Version	7.0.0.17
WebSphere Fix Pack Level	17
WebSphere Java Version	"1.6.0"
WebSphere Java Runtime	Java(TM) SE Runtime Environment (build pwa6460sr9fp1ifix-20110401_01(SR9 FP1+IZ95392+IZ95393+IZ97453))
WebSphere Installation Directory	C:\IBM\WebSphere\AppServer
WebSphere Admin Console URL	http://HOSTNAME.example.com:9060/ibm/console
WebSphere Admin Console Http Port	9060
WebSphere Admin Console Https Port	9043
WebSphere Cell Name	SASDmgr01Cell
WebSphere Deployment Manager Profile Name	SASDmgr01
WebSphere Dmgr Node Name	SASDmgr01Node
WebSphere Dmgr Server Logs Directory	C:\IBM\WebSphere\AppServer\profiles\SASDmgr01\logs\dmgr
WebSphere Managed Node Profile Name	SASHOSTNAME01Node
WebSphere Managed Node Name	SASHOSTNAME01Node
WebSphere Managed Node Logs Directory	C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\logs

====================	=========================================================================================
Application Server Name	SASServer1
Application Server Id	server
Application Server Http Port	9080
Application Server Log Directory	C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\logs\SASServer1
Application Server JVM Options	-Xms1024m -Xmx2048m -Xss256k -Xmso256k -Xgcpolicy:optavgpause -Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Dsas.container.identifier=websphere -Dcom.sas.services.logging.disableRemoteList=true -Dcom.sas.services.logging.disableRemoteLogging=true -Dsas.scs.host=HOSTNAME.example.com -Dsas.scs.port=9080 -Dwebreportstudio.file.cleanup.interval=60 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=0 -Dmulticast.address=239.16.12.250 -Dmulticast.port=8561 -Dcom.sas.log.config.url=file:///C:/SAS/EBIEDIEG/Lev1/Web/Common/LogConfig/ -Dsas.auto.publish.port=9080 -Xcompressedrefs

Configuring your WebSphere Application Server Environment

NOTE ABOUT AUTO-CONFIGURATION: Since you have requested that the WebSphere environment be auto-configured, please review the following documentation to see the tasks that were automatically performed for you to configure WebSphere during execution of the SAS Deployment Wizard.
A basic WebSphere configuration has been created that uses SAS authentication and unsecure connections. If you need to setup a more sophisticated topology such as web server authentication or single sign-on, please see the SAS 9.3 Intelligence Platform: Security Administration Guide.
For reverse proxy server and secure socket connections, see the SAS 9.3 Intelligence Platform: Web Application Administration Guide.

NOTE ABOUT AUTO-DEPLOYMENT: Since you have requested that the SAS web applications be auto-deployed, you can review documentation beginning at "Deployment for application..." to see the deployments that were performed.
For reference, EAR files for the SAS web applications that have been automatically deployed are located in the "C:\SAS\EBIEDIEG\Lev1\Web\Staging" directory.

The WebSphere Application Server environment has been configured automatically

Because Auto Configuration of the WebSphere Application Server (WAS) was selected when running the SAS Deployment Wizard (SDW), the WAS environment has been automatically configured. All appservers have been created and customized to support the SAS webapps, so no further manual configuration of WAS should be necessary. However, a new SAS WebSphere Configuration Scripting Tool now exists, which enables configuration of WAS outside of the SDW. A general description of the SAS WebSphere Configuration Scripting Tool is provided below for reference.

WebSphere Configuration Scripting Tool

New for SAS 9.3, a WebSphere Application Server (WAS) Configuration Scripting Tool is generated during a SAS Deployment Wizard configuration. This tool allows you to manually execute configuration steps through a command line interface. If you selected to perform a manual configuration, you can execute the scripting tool to create the WAS profiles and the functional cell and to configure the resources equivalent to what would have been built during SAS configuration if you had chosen to perform an automated configuration. If you performed an automated configuration, the tool can reconfigure each resource exactly as they were configured during the SAS configuration step.

The scripting tools are located at C:\SAS\EBIEDIEG\Lev1\Web\Scripts\WebSphere.

If WAS is not installed on the machine where you ran the SAS Deployment Wizard, you can copy the Scripts directory or folder and its contents and the ear files for your web applications to the machine where WAS is installed and run the scripting tool on that machine. It is also possible to execute the individual steps and make changes to your configuration by modifying property files and rerunning steps. Detailed instructions for the WebSphere Configuration Scripting Tool can be found in the SAS Intelligence Platform: Middle-Tier Administration Guide.

Create WebSphere Profiles

Create the WebSphere dmgr profile to manage SAS application server node(s)

The following is the general overview of the steps required to create the WebSphere dmgr "SASDmgr01" profile:

Create dmgr profile "SASDmgr01"
If you are configuring WAS manually, you will need to start the dmgr at this point, and logon to the WAS Admin Console
Set dmgr Http Ports
Set Http ports for the admin_host virtualhosts alias
Set Generic JVM Arguments for dmgr
Set the SOAP or RMI Read Timeout value for dmgr-to-nodeagent communications by updating the appropriate property file.
If auto-configuration for WAS is being performed, dmgr will now be started

Detailed Instructions to Create the WebSphere "SASDmgr01" dmgr Profile

Create the "SASDmgr01" profile using the "manageprofiles" command to construct a new cell which will contain the dmgr server.

Command to create dmgr profile: "C:\IBM\WebSphere\AppServer\bin\manageprofiles.bat" -response "C:\SAS\EBIEDIEG\Lev1\Web\Scripts\WebSphere\props\create.DmgrProfile.CELL.response.SASDmgr01.properties"
Update dmgr SOAP Read Timeout Property in the "C:\IBM\WebSphere\AppServer\profiles\SASDmgr01\properties\soap.client.props" file. Since there is no way to perform this function using the WAS Admin Console, use a text editor to set the "com.ibm.SOAP.requestTimeout" property to a value of "900" (without the "quotes").
Stop the dmgr manager using the "stopManager" command.
Command to stop the dmgr server: "C:\IBM\WebSphere\AppServer\bin\stopManager.bat" -profileName "SASDmgr01"
Set dmgr Ports to the following values by either editing the "C:\IBM\WebSphere\AppServer\profiles\SASDmgr01\config\cells\SASDmgr01Cell\nodes\SASDmgr01Node\serverindex.xml" file or using the WAS Admin Console "System administration->Deployment manager->ports" navigation to perform this task.
- Set dmgr WC_adminhost port to 9060
- Set dmgr WC_adminhost_secure port to 9043
- Set dmgr BOOTSTRAP_ADDRESS port to 9809
- Set dmgr SOAP_CONNECTOR_ADDRESS port to 8879
Set the Http ports for the admin_host virtualhost alias to match port 9060 for dmgr to the following values by either editing the "C:\IBM\WebSphere\AppServer\profiles\SASDmgr01\config\cells\SASDmgr01Cell\virtualhosts.xml" file or using the WAS Admin Console "Environment->Virtual Hosts->admin_host->Host Aliases" navigation to perform this task.
- Set the admin_host alias for "*" to the Http port 9060 for dmgr
- Set the admin_host alias for "*" to the Https port 9043 for dmgr
Set the dmgr JVM Initial Heap Size and Maximum Heap Size. From the WAS Admin Console, navigate through the "System administration->Deployment manager->Java and Process Management->Process Definition->Java Virtual Machine" menus.
- Set dmgr "Initial Heap Size" to 512
- Set dmgr "Maximum Heap Size" to 768
- Set dmgr server Generic JVM Arguments to "-Xms512m -Xmx768m" (NOTE: remember to exclude the beginning and ending quotes.)
Start the dmgr manager using the "startManager" command.
Command to start the dmgr server: "C:\IBM\WebSphere\AppServer\bin\startManager.bat" -profileName "SASDmgr01"

At this point, the dmgr profile "SASDmgr01" should be created.

Creation of WAS Dmgr profile should be complete at this point. You should be able to run the "manageprofiles" command with the "-listProfiles" parameter to verify that the "SASDmgr01" profile exists. In addition, you should see a Java process running for the "dmgr" server. You should also be able logon to the WAS Admin Console using the URL: http://HOSTNAME.example.com:9060/ibm/console.

Create the WebSphere managed node profile for the nodeagent and SAS application servers.

The following is the general overview of the steps required to create the WebSphere custom managed node "SASHOSTNAME01Node" profile:

If auto-configuration for WAS is being performed, it is assumed that the dmgr is started
Create the App Server managed profile "SASHOSTNAME01Node"
Set nodeagent RMI and SOAP Ports, if necessary
Set Generic JVM Arguments for nodeagent
Set the SOAP or RMI Read Timeout value for dmgr-to-nodeagent communications by updating the appropriate property file.
Federate the new managed node "SASHOSTNAME01Node" into the dmgr "SASDmgr01Cell" cell
If on Windows, ensure the nodeagent is stopped and create a Windows Service for the nodeagent
Synchronize the managed node with the dmgr before starting the nodeagent using the syncNode command
Ensure the nodeagent is started for the newly federated node

Detailed Instructions to Create the WebSphere "SASHOSTNAME01Node" Managed Node Profile

Create the App Server managed profile "SASHOSTNAME01Node" using the "manageprofiles" command.
Command to create the app server profile: "C:\IBM\WebSphere\AppServer\bin\manageprofiles.bat" -response "C:\SAS\EBIEDIEG\Lev1\Web\Scripts\WebSphere\props\create.NodeProfile.NODE.response.SASHOSTNAME01Node.properties"
Stop the nodeagent using the "stopNode" command.
Command to stop the nodeagent: "C:\IBM\WebSphere\AppServer\bin\stopNode.bat" -profileName "SASHOSTNAME01Node"
Update nodeagent SOAP Read Timeout Property in the "C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\properties\soap.client.props" file. Since there is no way to perform this function using the WAS Admin Console, use a text editor to set the "com.ibm.SOAP.requestTimeout" property to a value of "900" (without the "quotes").
Federate the new "SASHOSTNAME01Node" node to the dmgr cell using the "addNode" command.
Command to federate the new node: "C:\IBM\WebSphere\AppServer\bin\addNode.bat" HOSTNAME.example.com 8879 -conntype SOAP -profileName "SASHOSTNAME01Node" -includeapps -noagent
Set nodeagent Ports to the following values by either editing the "C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\config\cells\SASDmgr01Cell\nodes\SASHOSTNAME01Node\serverindex.xml" file or using the WAS Admin Console "System administration->Node agents->nodeagent for "SASHOSTNAME01Node"->ports" navigation to perform this task.
- Set nodeagent BOOTSTRAP_ADDRESS port to 2810
- Set nodeagent SOAP_CONNECTOR_ADDRESS port to 8878
Set the nodeagent JVM Initial Heap Size and Maximum Heap Size. From the WAS Admin Console, navigate through the "System administration->Node agents->nodeagent for Node "SASHOSTNAME01Node"->Java and Process Management->Process Definition->Java Virtual Machine" menus.
- Set nodeagent "Initial Heap Size" to 50
- Set nodeagent "Maximum Heap Size" to 256
- Set nodeagent server Generic JVM Arguments to "-Xms50m -Xmx256m" (NOTE: remember to exclude the beginning and ending quotes.)
Synchronize the nodeagent and dmgr repositories using the "syncNode" command.
Command to synchronize the nodeagent with the dmgr: "C:\IBM\WebSphere\AppServer\bin\syncNode.bat" "HOSTNAME.example.com" 8879 -conntype SOAP -profileName "SASHOSTNAME01Node"
Create a Windows Service for the nodeagent using the "WASService" command.
Command to create a Windows Service for the nodeagent: "C:\IBM\WebSphere\AppServer\bin\WASService" -add SASHOSTNAME01Node -servername nodeagent -restart true -startType automatic -profilePath "C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node"
Start the nodeagent using the "startNode" command.
Command to start the nodeagent: "C:\IBM\WebSphere\AppServer\bin\startNode.bat" -profileName "SASHOSTNAME01Node"

Creation of WAS managed node profile should be complete at this point. You should be able to run the "manageprofiles" command with the "-listProfiles" parameter to verify that the "SASHOSTNAME01Node" profile exists. In addition, you should see a Java processes running for the "nodeagent" server.

JAAS Login Module Alias "PFS" for module "com.sas.services.security.login.OMILoginModule" added to the JAAS Application logins in cell "SASDmgr01Cell"

The definition for the "PFS" JAAS Login Module Alias has been added using information from the tables below.

Values for JAAS Login Module general settings:
JAAS Application logins alias:	PFS
JAAS Module Class name:	com.sas.services.security.login.OMILoginModule
JAAS Authentication strategy:	required

Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule"
Custom Property Name:	Custom Property Value:
debug	false
domain	DefaultAuth
host	HOSTNAME.example.com
port	8561
repository	Foundation
trustedpw	Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;)
trusteduser	Enter the SAS trusted user ID

JAAS Login Module Alias "SASTRUSTED" for module "com.sas.services.security.login.TrustedLoginModule" added to the JAAS Application logins in cell "SASDmgr01Cell"

The definition for the "SASTRUSTED" JAAS Login Module Alias has been added using information from the tables below.

Values for JAAS Login Module general settings:
JAAS Application logins alias:	SASTRUSTED
JAAS Module Class name:	com.sas.services.security.login.TrustedLoginModule
JAAS Authentication strategy:	required

Custom Properties for JAAS Login Module "com.sas.services.security.login.TrustedLoginModule"
Custom Property Name:	Custom Property Value:
aliasdomain	MidtierInternal
debug	false
domain	DefaultAuth
host	HOSTNAME.example.com
port	8561
repository	Foundation
trustedpw	Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;)
trusteduser	Enter the SAS trusted user ID

JAAS Login Module Alias "SCS" for module "com.sas.services.security.login.OMILoginModule" added to the JAAS Application logins in cell "SASDmgr01Cell"

The definition for the "SCS" JAAS Login Module Alias has been added using information from the tables below.

Values for JAAS Login Module general settings:
JAAS Application logins alias:	SCS
JAAS Module Class name:	com.sas.services.security.login.OMILoginModule
JAAS Authentication strategy:	required

Custom Properties for JAAS Login Module "com.sas.services.security.login.OMILoginModule"
Custom Property Name:	Custom Property Value:
debug	false
domain	DefaultAuth
holdopenconnection	true
host	HOSTNAME.example.com
port	8561
repository	Foundation
trustedpw	Enter the SAS-encoded password for the SAS trusted user ID. (Use this SAS program to encode the value: PROC PWENCODE IN='password'; RUN;)
trusteduser	Enter the SAS trusted user ID

JAAS Login Module Alias "UsernamePassword" for module "com.platform.SASLogin.UsernamePasswordLogin" added to the JAAS Application logins in cell "SASDmgr01Cell"

The definition for the "UsernamePassword" JAAS Login Module Alias has been added using information from the tables below.

Values for JAAS Login Module general settings:
JAAS Application logins alias:	UsernamePassword
JAAS Module Class name:	com.platform.SASLogin.UsernamePasswordLogin
JAAS Authentication strategy:	required

Custom Properties for JAAS Login Module "com.platform.SASLogin.UsernamePasswordLogin"
Custom Property Name:	Custom Property Value:
debug	false

Create Application Server "SASServer1" Overview

Create Application Server "SASServer1"
Set SASServer1 Http Ports
Set Http ports for the default_host virtualhosts alias
Set Generic JVM Arguments for "SASServer1"
Enable Java 2 Security for "SASServer1", if restrictive policy support for access to local resources is desired.
Set the required Web Container custom properties for "SASServer1"
Create the Service Integration Bus for "SASServer1"
Add server "SASServer1" as a member on the Service Integration Bus
Perform a Full Resynchronize of the dmgr and nodeagent

Create Application Server Detailed Instructions

Server "SASServer1" has been created.
Server "SASServer1" has been stopped using: "C:\IBM\WebSphere\AppServer\bin\stopServer.bat" "SASServer1" -profileName "SASHOSTNAME01Node"
Set Http Ports for "SASServer1" to the following values by either editing the "C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\config\cells\SASDmgr01Cell\nodes\SASHOSTNAME01Node\serverindex.xml" file or using the WAS Admin Console by navigating to Servers->Server Types->WebSphere application servers->SASServer1->Ports->Details to perform this function.
- Set SASServer1 WC_defaulthost port to 9080
- Set SASServer1 WC_defaulthost_secure port to 9443
Set the Http ports for the default_host virtualhost alias to match the Http ports for "SASServer1". The following Http port values should be set by either editing the "C:\IBM\WebSphere\AppServer\profiles\SASHOSTNAME01Node\config\cells\SASDmgr01Cell\virtualhosts.xml" file or using the WAS Admin Console by navigating to Environment->Virtual hosts->default_host->Host Aliases to perform this task.
- Set the default_host alias for "*" to match the Http port 9080 for SASServer1
- Set the default_host alias for "*" to match the Https port 9443 for SASServer1
Set Generic JVM Arguments for server "SASServer1" using the WAS Admin Console. after navigating to Servers->Server types->WebSphere application servers->SASServer1->Java and Process Management->Process definition->Java Virtual Machine.
SASServer1 Generic JVM Arguments (exclude the beginning and ending "quotes"):
- Set SASServer1 "Initial Heap Size" to 1024
- Set SASServer1 "Maximum Heap Size" to 2048
- Set SASServer1 Generic JVM Arguments to: "-Xms1024m -Xmx2048m -Xss256k -Xmso256k -Xgcpolicy:optavgpause -Djavax.management.builder.initial= -Dcom.sun.management.jmxremote -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Dsas.container.identifier=websphere -Dcom.sas.services.logging.disableRemoteList=true -Dcom.sas.services.logging.disableRemoteLogging=true -Dsas.scs.host=HOSTNAME.example.com -Dsas.scs.port=9080 -Dwebreportstudio.file.cleanup.interval=60 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=0 -Dmulticast.address=239.16.12.250 -Dmulticast.port=8561 -Dcom.sas.log.config.url=file:///C:/SAS/EBIEDIEG/Lev1/Web/Common/LogConfig/ -Dsas.auto.publish.port=9080 -Xcompressedrefs " (NOTE: remember to exclude the beginning and ending quotes.)
Set the required Web Container custom properties for server "SASServer1" using the WAS Admin Console.
Using the Servers->Server types->WebSphere application servers->SASServer1->Web Container Settings->Web container->Custom Properties menu in the WAS Admin Console, there are two custom properties that must be set for proper SAS web application function.
- Create a new property with a name of "prependSlashToResource" and a value of "true" (without the "quotes").
- Create a new property with a name of "com.ibm.ws.webcontainer.channelwritetype" and a value of "sync" (again, without the "quotes").
Using the Servers->Server types->WebSphere application servers->SASServer1->Session management menu in the WAS Admin Console, set the session management cookie name to ensure a unique JSESSIONID is associated with this server.
- Enable cookies by checking the "Enable cookies" checkbox.
- Set the cookie name to "JSESSIONIDSASServer1"
Java 2 Security for server "SASServer1" is disabled.
Java 2 Security has been left disabled for server "SASServer1".
Create the Service Integration Bus for server "SASServer1" using the WAS Admin Console.
Using the "Service integration" menu in the WAS Admin Console, create a new bus with the name "SAS_Messaging_Bus" (without the "quotes"). Bus security is not enabled for this bus.
Add server "SASServer1" as a member on the Service Integration Bus "SAS_Messaging_Bus" created in the step above using the WAS Admin Console.
From the the Service integration->Buses menu in the WAS Admin Console, select "SAS_Messaging_Bus", use the Bus members link to add "SASHOSTNAME01Node:SASServer1" as a new member of the bus. The "Server" radio button should be selected with the "SASHOSTNAME01Node:SASServer1" (without the "quotes") drop-down menu item. Choose all the pre-selected and pre-filled defaults on the remaining definition pages.
After saving your work, perform a Full Resynchronize of the dmgr and nodeagent using the WAS Admin Console.
From the the System administration menu, choose the "SASHOSTNAME01Node" and perform a Full Resynchronize to ensure all new server definitions are propagated from the master repository to the nodeagent.

Creation of server "SASServer1" should now be complete. The base JVM and Web Container configuration for the new "SASServer1" has been completed. All remaining configuration steps will use these base server definitions to complete the customization of the J2EE server functions for the SAS web applications.

Create Mail Session "SASMailSession" at the "SERVER" level.

A new Mail Session named "SASMailSession" has been created at scope "SASDmgr01Cell.SASHOSTNAME01Node.SASServer1" with the following properties:

Values for the Create Mail Session
Scope:	Node=SASHOSTNAME01Node, Server=SASServer1
Mail Session Name:	SASMailSession
JNDI Name:	sas/mail/Session
SMTP Host Name:	localhost
Mail Debug:	false
Mail Transport Protocol:	smtp
Mail SMTP Host Requires Authentication:	false

Start server "SASServer1" using: "C:\IBM\WebSphere\AppServer\bin\startServer.bat" "SASServer1" -profileName "SASHOSTNAME01Node"

JMS Queue Connection Factory "SASQueueConnectionFactory" has been created at the "CELL" level.

A new JMS Queue Connection Factory "SASQueueConnectionFactory" definition has been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Connection Factory Definition:
Scope:	Cell=SASDmgr01Cell
Connection Factory Type:	Queue
Queue Connection Factory name:	SASQueueConnectionFactory
JMS resource provider:	Default messaging provider
JNDI name:	sas/jms/QueueConnectionFactory
Bus name:	SAS_Messaging_Bus
Maximum connection pool size:	10
Minimum connection pool size:	1
Connection timeout:	180
Aged timeout:	0
Unused connection timeout:	1800
Reap time:	180
Purge policy:	EntirePool

JMS Topic Connection Factory "SASTopicConnectionFactory" has been created at the "CELL" level.

A new JMS Topic Connection Factory "SASTopicConnectionFactory" definition has been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Topic Connection Factory Definition:
Scope:	Cell=SASDmgr01Cell
Connection Factory Type:	Topic
Topic Connection Factory name:	SASTopicConnectionFactory
JMS resource provider:	Default messaging provider
JNDI name:	sas/jms/TopicConnectionFactory
Bus name:	SAS_Messaging_Bus
Maximum connection pool size:	10
Minimum connection pool size:	1
Connection timeout:	180
Aged timeout:	0
Unused connection timeout:	1800
Reap time:	180
Purge policy:	EntirePool

JMS Queue "AlertQueue" has been created at the "CELL" level.

A JMS Queue "AlertQueue" and Service Integration Bus Destination "AlertQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	AlertQueue
JNDI name:	sas/jms/AlertQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	AlertQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "AuditQueue" has been created at the "CELL" level.

A JMS Queue "AuditQueue" and Service Integration Bus Destination "AuditQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	AuditQueue
JNDI name:	sas/jms/AuditQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	AuditQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "scheduler.pip.jobQueue" has been created at the "CELL" level.

A JMS Queue "scheduler.pip.jobQueue" and Service Integration Bus Destination "scheduler.pip.jobQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	scheduler.pip.jobQueue
JNDI name:	sas/jms/scheduler.pip.jobQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	scheduler.pip.jobQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "scheduler.pip.outputQueue" has been created at the "CELL" level.

A JMS Queue "scheduler.pip.outputQueue" and Service Integration Bus Destination "scheduler.pip.outputQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	scheduler.pip.outputQueue
JNDI name:	sas/jms/scheduler.pip.outputQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	scheduler.pip.outputQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "scheduler.pip.resultsQueue" has been created at the "CELL" level.

A JMS Queue "scheduler.pip.resultsQueue" and Service Integration Bus Destination "scheduler.pip.resultsQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	scheduler.pip.resultsQueue
JNDI name:	sas/jms/scheduler.pip.resultsQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	scheduler.pip.resultsQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "WorkflowCommandQueue" has been created at the "CELL" level.

A JMS Queue "WorkflowCommandQueue" and Service Integration Bus Destination "WorkflowCommandQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	WorkflowCommandQueue
JNDI name:	sas/jms/WorkflowCommandQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	WorkflowCommandQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "WorkflowQueue" has been created at the "CELL" level.

A JMS Queue "WorkflowQueue" and Service Integration Bus Destination "WorkflowQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Cell=SASDmgr01Cell
Queue name:	WorkflowQueue
JNDI name:	sas/jms/WorkflowQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	WorkflowQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Queue "WorkflowEventsQueue" has been created at the "SERVER" level.

A JMS Queue "WorkflowEventsQueue" and Service Integration Bus Destination "WorkflowEventsQueue" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell.SASHOSTNAME01Node.SASServer1" using information from the following table:

Values for the JMS Queue Definition:
Scope:	Node=SASHOSTNAME01Node, Server=SASServer1
Queue name:	WorkflowEventsQueue
JNDI name:	sas/jms/app/WorkflowEventsQueue
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	WorkflowEventsQueue
Delivery mode:	Application
Read ahead:	AsConnection

JMS Topic "NotificationEventTopic" has been created at the "CELL" level.

A JMS Topic "NotificationEventTopic" and Service Integration Bus destination "NotificationEventTopic" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Topic Definition:
Scope:	Cell=SASDmgr01Cell
Topic name:	NotificationEventTopic
Topic space:	NotificationEventTopic
JNDI name:	sas/jms/NotificationEventTopic
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	NotificationEventTopic
Delivery mode:	Application
Read ahead:	AsConnection

JMS Topic "SASPublishedEventTopic" has been created at the "CELL" level.

A JMS Topic "SASPublishedEventTopic" and Service Integration Bus destination "SASPublishedEventTopic" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Topic Definition:
Scope:	Cell=SASDmgr01Cell
Topic name:	SASPublishedEventTopic
Topic space:	SASPublishedEventTopic
JNDI name:	sas/jms/SASPublishedEventTopic
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	SASPublishedEventTopic
Delivery mode:	Application
Read ahead:	AsConnection

JMS Topic "scheduler.pip.broadcastTopic" has been created at the "CELL" level.

A JMS Topic "scheduler.pip.broadcastTopic" and Service Integration Bus destination "scheduler.pip.broadcastTopic" on Service Integration Bus "SAS_Messaging_Bus" have been created at scope "SASDmgr01Cell" using information from the following table:

Values for the JMS Topic Definition:
Scope:	Cell=SASDmgr01Cell
Topic name:	scheduler.pip.broadcastTopic
Topic space:	scheduler.pip.broadcastTopic
JNDI name:	sas/jms/scheduler.pip.broadcastTopic
Bus name:	SAS_Messaging_Bus
"SAS_Messaging_Bus" destination:	scheduler.pip.broadcastTopic
Delivery mode:	Application
Read ahead:	AsConnection

JDBC Provider "SharedServices MySQL JDBC Provider" has been created at the "SERVER" level.

A JDBC Provider "SharedServices MySQL JDBC Provider" definition has been created at scope "SASDmgr01Cell.SASHOSTNAME01Node.SASServer1" using information from the following table:

Values for the JDBC Provider Definition:
Scope:	Node=SASHOSTNAME01Node, Server=SASServer1
JDCB Provider Name:	SharedServices MySQL JDBC Provider
JDBC Provider Database type:	User-defined JDBC Provider
JDBC Provider Classpath:	C:\SAS\EBIEDIEG\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\mysql-connector-java-5.1.10-bin.jar
JDBC Provider Implementation class name:	com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource
JDBC Provider XA capable: (true or false)	false

Data Source "SharedServices" has been created at the "SERVER" level.

A new Data Source "SharedServices" definition has been created at scope "SASDmgr01Cell.SASHOSTNAME01Node.SASServer1" using information from the following table:

Values for the JDBC Data Source Definition:
Scope:	Node=SASHOSTNAME01Node, Server=SASServer1
Data Source Name:	SharedServices
JNDI Name:	sas/jdbc/SharedServices
JDBC Provider Name:	SharedServices MySQL JDBC Provider
JDBC Provider Type:	User-defined JDBC Provider
Connection URL:	jdbc:mysql://HOSTNAME.example.com:3306/SharedServices
Data store helper class name:	com.ibm.websphere.rsadapter.GenericDataStoreHelper
JAAS - J2C Authentication Data - JAAS Alias Name:	MySQLJAASAlias
JAAS - J2C Authentication Data - JAAS Alias User ID:	The User ID used to make the database connection for the "SharedServices" data source.
JAAS - J2C Authentication Data - JAAS Alias Password:	The password used to make the database connection for the "SharedServices" data source.
WebSphere Application Server data source properties - Statement cache size:	10

In addition, custom properties for the "SharedServices" Data Source were created with names and values as specified in the following table:

Custom Properties for Data Source "SharedServices"
Custom Property Name:	Custom Property Value:
autoReconnect	true
connectionCollation	utf8_bin
dataSourceName	SharedServices
databaseName	SharedServices
password	The password used to make the database connection for the "SharedServices" data source.
portNumber	3306
relaxAutoCommit	true
serverName	HOSTNAME.example.com
serverUrl	jdbc:mysql://HOSTNAME.example.com:3306/SharedServices
useServerPrepStmts	false
user	The User ID used to make the database connection for the "SharedServices" data source.

Deployment for application "SASBIDashboard4.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASBIDashboard4.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASBIDashboard4.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging/sas.bidashboard4.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASBIPortlets4.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASBIPortlets4.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASBIPortlets4.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging/sas.biportlets4.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with parent class loader first (PARENT_FIRST)"
WAR Classloader mode has been set to "Classes loaded with parent class loader first (PARENT_FIRST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASContentServer9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASContentServer9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASContentServer9.3"
Application startup order: 4
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.wip.scs9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASFlexThemes3.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASFlexThemes3.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASFlexThemes3.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.flexthemes3.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASPackageViewer4.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASPackageViewer4.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASPackageViewer4.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging/sas.packageviewer4.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASPortal4.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASPortal4.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASPortal4.3"
Application startup order: 5
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging/sas.portal4.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASStoredProcess9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASStoredProcess9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASStoredProcess9.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.storedprocess9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASThemeDesigner3.3ForFlex" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASThemeDesigner3.3ForFlex" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASThemeDesigner3.3ForFlex"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.themedesigner3.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASThemes9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASThemes9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASThemes9.3"
Application startup order: 1
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.themes.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWebDoc9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWebDoc9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWebDoc9.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.webdocmd9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWebInfrastructurePlatformApplications9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWebInfrastructurePlatformApplications9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWebInfrastructurePlatformApplications9.3"
Application startup order: 3
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.wip.apps9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWebInfrastructurePlatformServices9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWebInfrastructurePlatformServices9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWebInfrastructurePlatformServices9.3"
Application startup order: 2
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.wip.services9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWebReportStudio4.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWebReportStudio4.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWebReportStudio4.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging/sas.webreportstudio4.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWIPAdmin9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWIPAdmin9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWIPAdmin9.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.wip.admin9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWIPResources9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWIPResources9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWIPResources9.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.wip.resources9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

Deployment for application "SASWorkflow9.3" on "SASServer1".

Because you have requested auto-configuration of WAS and auto-deployment of the SAS web applications, application "SASWorkflow9.3" has been automatically deployed and made ready for SAS operations using the following information:

Application name: "SASWorkflow9.3"
Application startup order: 100
EAR location: C:\SAS\EBIEDIEG\Lev1\Web\Staging\sas.workflow9.3.ear
EAR Classloader policy has been set to "Class loader for each WAR file in application (MULTIPLE)"
EAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)"
WAR Classloader mode has been set to "Classes loaded with local class loader first (PARENT_LAST)" for all modules in the EAR
"Deploy enterprise beans" checkbox has been unchecked; EJB deployment EJBDeploy tool is not required.
"Deploy Web services" checkbox has been checked; the wsdeploy Web services deploy tool will be run.
Full Resynchronize was performed to ensure the new application definition is propagated between dmgr and nodeagent

During Auto-Configure, WebSphere Application Server "SASServer1" has been stopped.

Command executed to stop server "SASServer1" was: "C:\IBM\WebSphere\AppServer\bin\stopServer.bat" "SASServer1" -profileName "SASHOSTNAME01Node"

Starting the WebSphere Server(s)

Starting the Dmgr server: Issue "C:\IBM\WebSphere\AppServer\bin\startManager.bat" -profileName "SASDmgr01" or, if on Windows, by starting the the Windows service.
Starting the Node Agent server: Issue "C:\IBM\WebSphere\AppServer\bin\startNode.bat" -profileName "SASHOSTNAME01Node" or, if on Windows, by starting the Windows service.
Starting Application Server "SASServer1": Issue "C:\IBM\WebSphere\AppServer\bin\startServer.bat" "SASServer1" -profileName "SASHOSTNAME01Node"

SAS Web Applications

SAS Themes

Validation steps

SAS Themes are used by SAS theme-enabled web applications. If you go to the logon screen for the Portal or Web Report Studio and see images then SAS Themes are working properly.

SAS Web Infrastructure Platform

Log directory	C:\SAS\EBIEDIEG\Lev1\Web\Logs
Validation steps	Access the Comment Service. Log in using the HOSTNAME\sasdemo credentials provided during configuration. Verify that you can add a comment.

SAS Content Server

Log file	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASContentServer9.3.log
Validation steps	In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node. Highlight the SAS Content Server. Right mouse click this server and select Validate. Log in using valid credentials for an unrestricted user defined in the SAS Metadata Server. You should see a Validation Successful message.

SAS Stored Process Web Application

URL	http://HOSTNAME.example.com:9080/SASStoredProcess/do
Log file	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASStoredProcess9.3.log
Validation steps	Access the URL provided above. Log in using the HOSTNAME\sasdemo credentials provided during configuration. On the Welcome page, click the "Sample: Shoe Sales by Region" link to access the custom input form for this sample stored process. Select an ODS style or accept the default value, and click the "Display SAS Output" button. The output from the stored process is a static table and a clickable chart. Click a bar segment on the chart to drill down to the data for that country.

SAS Web Administration Console

URL	http://HOSTNAME.example.com:9080/SASAdmin
Log file	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASAdmin9.3.log
Validation steps	Access the URL provided above. Log in using the sasadm@saspw credentials provided during configuration. On the main page, expand the "Environment Management" folder in the tree and select the "Users" node. Verify that "sasadm" appears in the "Authenticated Users" section in the right frame. Click the checkbox in the far right column of the "sasadm" row. Click the menu icon directly above the checkbox and select "Send E-mail". Enter your email address in the "To:" field and click "Send". Verify that you received the email.

SAS Web Report Studio

URL	http://HOSTNAME.example.com:9080/SASWebReportStudio
Log directory	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASWebReportStudio4.3.log For more details about how to modify your log format and to see what logging entails, see "Logging for SAS Web Applications" in the SAS Intelligence Platform: Web Application Administration Guide at http://support.sas.com/93administration.
Validation steps	Access the URL provided above. Login using valid credentials defined in the SAS Metadata Server.

SAS Information Delivery Portal

URL	http://HOSTNAME.example.com:9080/SASPortal
Log file	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASPortal4.3.log For more details about how to modify your log format and to see what logging entails, see "Logging for SAS Web Applications" in the SAS Intelligence Platform: Web Application Administration Guide at http://support.sas.com/93administration.
Validation steps	Access the URL provided above. Login using the HOSTNAME\sasdemo credentials provided during configuration. Since the Portal samples were installed, verify that a Home page was created and contains two portlets, My Collections and Bookmarks. Perform a search to verify that you have access to SAS content.

Notes:

The SAS Portlets are located at: C:\SAS\EBIEDIEG\Lev1\Web\Applications\SASPortlets4.3\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 BI Portlets

Log file	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASBIPortlets4.3.log For more details about how to modify your log format and to see what logging entails, see "Logging for SAS Web Applications" in the SAS Intelligence Platform: Web Application Administration Guide at http://support.sas.com/93administration.
Manual steps	Copy the sas.portlet.container.runtime.extensions.jar file from the 'C:\SAS\EBIEDIEG\Lev1\Web\Staging\exploded\sas.biportlets4.3.ear\lib' directory of the sas.biportlets4.3.ear file to the lib directory of the WebSphere Application Server. Restart the WebSphere Application Server.
Validation steps	Login to the portal. Add the SAS Navigator Portlet to a portal page. Navigate to different locations.

Notes:

The classes for BI Portlets should be loaded after its parent class loader (PARENT_FIRST).
SAS reports must be defined in order to use the SAS Report Portlet
SAS stored processes must be defined in order to use the SAS Stored Process Portlet
SAS dashboards must be defined in order to use the SAS BI Dashboard Portlet

SAS BI Dashboard

URL	http://HOSTNAME.example.com:9080/SASBIDashboard
Log	C:\SAS\EBIEDIEG\Lev1\Web\Logs\SASBIDashboard4.3.log For more details about how to modify your log format and to see what logging entails, see "Logging for SAS Web Applications" in the SAS Intelligence Platform: Web Application Administration Guide at http://support.sas.com/93administration.
Validation Steps	Grant the user "SAS Demo User" access to SAS BI Dashboard 4.3. In SAS Management Console, on the Plug-ins tab, select the User Manager node. Right select "BI Dashboard Administrators" and select Properties. Select the "Members" tab Double click on SAS Demo User to add it to the group. Select OK. Access the URL provided above. Login using the "HOSTNAME\sasdemo" credentials provided during configuration. Select Manage Dashboards. Select New Indicator Data. Enter a name for the Indicator Data, and then select OK. Select Data source: SQL query. Enter this SQL query: *select from sashelp.prdsale. Select Apply Query Changes. File > Save. Navigate to Products/BI Dashboard 4.3/ModelConfigs, and select Save. File > New > Indicator Enter a Name for the Indicator. Select Display type: Pie Chart. Select Browse, navigate to the indicator data just created, and select OK. Select OK again. Select Category value: COUNTRY. Select Response value: ACTUAL. File > Save. Navigate to Products/BI Dashboard 4.3/IndicatorDefinitions, and select Save. File > New > Dashboard Enter a Name for the Dashboard, and select OK. In the Objects pane, navigate to Products/BI Dashboard 4.3/IndicatorDefinitions. Drag-n-drop the indicator just created onto the dashboard. File > Save. Navigate to Products/BI Dashboard 4.3/DashboardConfigs, and select Save. View > Go to Dashboard Viewer** Verify that you have access to this dashboard by adding the BI Dashboard Portlet to a Portal page. Documentation at http://support.sas.com/documentation/onlinedoc/bidashboard/index.html is available to assist you.

SAS Flex Application Themes

Validation steps	SAS Flex Themes are used by SAS theme-enabled Flex applications. If after logging into SAS BI Dashboard you see images then SAS Flex Themes are working properly.
Validation steps	SAS Theme Designer for Flex is accessible from http://HOSTNAME.example.com:9080/SASThemeDesignerForFlex. In order to use this application, you must be a member of the role "Theme Designer for Flex: Administration".

SAS Help Viewer for Midtier Applications

URL	http://HOSTNAME.example.com:9080/SASWebDoc
Validation steps	Use the URL above and examine the Installed Products Page, if there were any errors configuring help content, they will be reported on that page.

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

C:\SAS\EBIEDIEG\Lev1\Web\Common\Server Name\Application Name\CustomContent

For example,

C:\SAS\EBIEDIEG\Lev1\Web\Common\SASServer1\SASWebReportStudio4.3\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.

Obtaining Additional Information

Additional SAS Intelligence Platform documentation is available from the SAS 9.3 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

Your metadata server is configured to perform unassisted metadata server backups and roll-forward recovery to a specified point in time. The first backup was taken immediately after the completion of the SAS Metadata Server configuration step. Because roll-forward recovery is configured, all metadata updates made by subsequent configuration steps will be captured in the server's journal file. When your installation is complete, you can choose to execute an ad hoc server backup immediately or wait for the next scheduled backup to occur.

Server backups are requested in the Server Backup node of the SAS Management Console Metadata Manager. Right-click the Server Backup folder and select Run Backup Now from the menu. The default backup configuration performs nightly server backups at 1 a.m. To modify the backup schedule, select Server Backup->Backup Schedule.

Caution: The server backup facility only backs up your metadata server. This includes SAS metadata repositories and metadata server configuration files. It does not include other SAS Intelligence Platform configuration directories or SAS software. You will need to make regular system backups as well as metadata server backups in order to restore your SAS configuration. Metadata server backups should be scheduled to occur just before system backups so that each system backup has a timely metadata server backup.

From the Server Backup node, administrators can also:

monitor the backup history
modify the default backup configuration
execute a roll-forward recovery of the metadata server from a selected backup.

Regular metadata server backups using SAS backup tools are crucial to ensuring the health of your SAS 9.3 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/93administration.