Configuration Guidelines and Details for "HOSTNAME"

Overview

Warnings and Notices
SAS Management Console
SAS Application Servers
SAS Spawners
SAS Framework Data 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\EBIserver\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 [EBIserver-Lev1] SASMeta - Metadata Server
Shortcuts	Programs > SAS > Configuration > EBIserver - 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\EBIserver\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 EBIserver - 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 - OLAP Server

Host machine	HOSTNAME.example.com
Port	5451
Log directory	C:\SAS\EBIserver\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 [EBIserver-Lev1] SASApp - OLAP Server
Shortcuts	Programs > SAS > Configuration > EBIserver - Lev1

SASApp - Stored Process Server

Host machine	HOSTNAME.example.com
Port	8601
Log directory	C:\SAS\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\Lev1\SASMeta\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\EBIserver\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 [EBIserver-Lev1] Object Spawner
Shortcuts	Programs > SAS > Configuration > EBIserver - Lev1

SAS Framework Data Server

Host machine	HOSTNAME.example.com
Port	22031
Log directory	C:\SAS\EBIserver\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 [EBIserver-Lev1] FrameworkServer - SAS Framework Data Server
Shortcuts	Programs > SAS > SAS Configuration > EBIserver - Lev1

SAS Deployment Tester Server

Host machine	HOSTNAME.example.com
Port	10021
Execution type	Windows service SAS [EBIserver-Lev1] Deployment Tester Server
Shortcuts	Programs > SAS > Configuration > EBIserver - 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\EBIserver\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\EBIserver\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\EBIserver\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\EBIserver\Lev1\Web\Logs
JES Java Batch Server	Name = "SASApp - JES Java Batch Server"
Configuration	Configuration Directory = "C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPSchedulingServices9.3" Deployment Directory = "C:\SAS\EBIserver\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 [EBIserver-Lev1] Remote Services
Shortcuts	Programs > SAS > Configuration > EBIserver - Lev1
Validation steps	Execute 'C:\SAS\EBIserver\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 > EBIserver - 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 > EBIserver - Lev1 > Remote Services - Stop

Web Application Server

Application Server Name	WebLogic
Vendor	Oracle
Version	10.3
WebLogic Install Directory (WL_HOME)	C:\Oracle\Middleware\wlserver_10.3
Domain Name	SASDomain
Domain Directory	C:\SAS\EBIserver\Lev1\Web\SASDomain
Java JDK Vendor	Sun
JDK Install Directory	C:\Program Files\Java\jdk1.6.0_32
Host machine	HOSTNAME.example.com
WebLogic Server Administration Console URL	http://HOSTNAME.example.com:7501/console

Configuring your WebLogic Application Server (Domain Configuration)

A basic WebLogic Server configuration has been created for you that uses SAS authentication and insecure connections. This configuration should support a small number of users.If you need to set up a more sophisticated topology such as web server authentication or single sign-on, 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 at http://support.sas.com/93administration for additional details. Detailed configuration instructions on WebLogic are also available at the third-party vendor web site located at http://www.oracle.com/technology/documentation.

WebLogic Configuration Scripting Tool

New for SAS 9.3, a WebLogic Server 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 performed a manual configuration, you can execute the scripting tool to create a domain 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 tool is located at C:\SAS\EBIserver\Lev1\Web\Scripts\Weblogic.

If WebLogic is not installed on the machine where you run the SAS Deployment Wizard, you can copy the entire Web directory(include the scripts directory,the ear files, and all the contents under the directory) for your web applications to the machine where WebLogic Server 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 WebLogic Configuration Scripting Tool can be found in the SAS Intelligence Platform: Middle-Tier Administration Guide, located at Scripting Tool for WebLogic Server.

WebLogic Node Manager

The domain that has been created is configured with a customized installation of Node Manager. It has been customized so that servers that are launched use the correct JDK and command line options that are recommended by SAS. The administration server and managed server(s) have been launched for you during the configuration process through this Node Manager.

This Node Manager has been installed as a service. It will be automatically restarted after you reboot your machine.

Listen Port	5556
Node Manager Home Directory	C:\SAS\EBIserver\Lev1\Web\SASDomain\nodemanager
Node Manager Log File	C:\SAS\EBIserver\Lev1\Web\SASDomain\nodemanager\nodemanager.log

WebLogic Administration Server - AdminServer

Listen Address	HOSTNAME.example.com
Listen Port	7501
HTTPS Port	7502
JVM Options	-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Xms256m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:CompileThreshold=8000 -Dweblogic.serverStart.allowQuotes=true -Dweblogic.deploy.UploadLargeFile=true -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=0
Server Logs Directory	C:\SAS\EBIserver\Lev1\Web\SASDomain\servers\AdminServer\logs

WebLogic Managed Server - SASServer1

Listen Address	HOSTNAME.example.com
Listen Port	7001
HTTPS Port	7002
JVM Options	-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Dsas.server.name=Server -Djava.endorsed.dirs="C:\Program Files\Java\jdk1.6.0_32\jre\lib\endorsed;C:\SAS\EBIserver\Lev1\Web\SASDomain\endorsed" -Xms1024m -Xss256k -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=768m -XX:NewSize=128m -XX:MaxNewSize=256m -XX:+UseTLAB -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:+CMSClassUnloadingEnabled -Xrs -Djava.awt.headless=true -Dweblogic.serverStart.allowQuotes=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsas.jms.authentication.decorator=false -Dweblogic.deploy.UploadLargeFile=true -Dsas.container.identifier=weblogic -Dcom.sas.services.logging.disableRemoteList=true -Dcom.sas.services.logging.disableRemoteLogging=true -Dtheme.sleep.time=10000 -Dtheme.max.tries=360 -Dsas.scs.host=HOSTNAME.example.com -Dsas.scs.port=7001 -Dwebreportstudio.file.cleanup.interval=60 -Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl -Dsas.auto.publish.port=7001 -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false -Dmulticast_udp_ip_ttl=0 -Dmulticast.address=239.11.13.224 -Dmulticast.port=8561 -Dcom.sas.log.config.url=file:///C:/SAS/EBIserver/Lev1/Web/Common/LogConfig/ -Djava.security.auth.login.config="C:\SAS\EBIserver\Lev1\Web\Common\SASDomain\weblogicLogin.config"
Server Logs Directory	C:\SAS\EBIserver\Lev1\Web\SASDomain\servers\SASServer1\logs

WebLogic Windows Service Scripts

Scripts to install the WebLogic Servers as a Windows Service have been created in C:\SAS\EBIserver\Lev1\Web\SASDomain\bin. If you prefer to run the WebLogic Administration Server and Managed Servers as a Windows Service please following instructions below.

Server Name	Install Script	Un-install Script
AdminServer	installAdminServerSvc.cmd	uninstallAdminServerSvc.cmd
SASServer1	installSASServer1Svc.cmd	uninstallSASServer1Svc.cmd

Shutdown the WebLogic Administration Server and all managed servers.
Run the install service script for the Administration server and each managed server.
For each service, set the windows account the Service should use:
- On the Services control panel, right click the WebLogic Server Windows service and click Properties.
- In the Properties window, click the Log On tab.
- Under "Log on as", select "This account".
- Enter the user name and password of the account which ran the SAS Deployment Wizard.
- Click Ok.

MailSession Configuration - SASMailSession

Name	SASMailSession
JNDI Name	sas/mail/Session
JavaMail Properties	mail.debug=false mail.smtp.host=localhost mail.transport.protocol=smtp
Target Managed Server	SASServer1

JMS Server - SASJMSServer

Name	SASJMSServer
Target	SASServer1

JMS Module - sasJmsSystemResource Configuration

JMS Module Name	sasJmsSystemResource
Targets	SASServer1

JMS SubDeployment - (SASServer1SubDeployment) Configuration

JMS Subdeployment Name	SASServer1SubDeployment
JMS Module Name	sasJmsSystemResource
Targets	SASJMSServer

JMS Connection Factory - SASQueueConnectionFactory

JMS Connection Factory Name	SASQueueConnectionFactory
Target JMS Module	sasJmsSystemResource
Target SubDeployment	SASServer1SubDeployment
JNDI Name	sas/jms/QueueConnectionFactory

JMS Connection Factory - SASTopicConnectionFactory

JMS Connection Factory Name	SASTopicConnectionFactory
Target JMS Module	sasJmsSystemResource
Target SubDeployment	SASServer1SubDeployment
JNDI Name	sas/jms/TopicConnectionFactory

JMS Queue Configuration - AlertQueue:

JMS Queue Name	AlertQueue
JNDI Name	sas/jms/AlertQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - AuditQueue:

JMS Queue Name	AuditQueue
JNDI Name	sas/jms/AuditQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - scheduler.pip.jobQueue:

JMS Queue Name	scheduler.pip.jobQueue
JNDI Name	sas/jms/scheduler.pip.jobQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - scheduler.pip.outputQueue:

JMS Queue Name	scheduler.pip.outputQueue
JNDI Name	sas/jms/scheduler.pip.outputQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - scheduler.pip.resultsQueue:

JMS Queue Name	scheduler.pip.resultsQueue
JNDI Name	sas/jms/scheduler.pip.resultsQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - WorkflowCommandQueue:

JMS Queue Name	WorkflowCommandQueue
JNDI Name	sas/jms/WorkflowCommandQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - WorkflowEventsQueue:

JMS Queue Name	WorkflowEventsQueue
JNDI Name	sas/jms/app/WorkflowEventsQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Queue Configuration - WorkflowQueue:

JMS Queue Name	WorkflowQueue
JNDI Name	sas/jms/WorkflowQueue
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Topic Configuration - JESEventTopic

JMS Queue Name	JESEventTopic
JNDI Name	sas/jms/JESEventTopic
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Topic Configuration - NotificationEventTopic

JMS Queue Name	NotificationEventTopic
JNDI Name	sas/jms/NotificationEventTopic
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Topic Configuration - SASPublishedEventTopic

JMS Queue Name	SASPublishedEventTopic
JNDI Name	sas/jms/SASPublishedEventTopic
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

JMS Topic Configuration - scheduler.pip.broadcastTopic

JMS Queue Name	scheduler.pip.broadcastTopic
JNDI Name	sas/jms/scheduler.pip.broadcastTopic
Target SubDeployment	SASServer1SubDeployment
Target JMS Module	sasJmsSystemResource

Data Source Configuration

DataSource Name	SharedServices
JNDI Name	sas/jdbc/SharedServices
DataBase Server Host	HOSTNAME.example.com
DataBase Server Port	22031
DataBase User Name	********
JDBC Driver Class Name	com.sas.tkts.TKTSDriver
Connection URL	jdbc:sastkts://HOSTNAME.example.com:22031
Connection Properties	stmtPooling=0 constring=(DSN=SharedServices;encoding=UNICODE_FSS)
Target Server	SASServer1
Driver Jar(s)	C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\icu4j.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\log4j.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.core.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.core.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.icons.contents.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.icons.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.icons.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.intrnet.javatools.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.intrnet.javatools.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.nls.collator.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.oda.tkts.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.oda.tkts.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.rutil.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.rutil.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.security.sspi.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.svc.connection.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sas.svc.connection.nls.jar C:\SAS\EBIserver\Lev1\Web\Applications\SASWIPServices9.3\JDBCDrivers\sastpj.rutil.jar

Securing Your WebLogic Domain

The WebLogic domain that was created by SDW may be accessible to other users. This means that other users may be able to change into the domain directory and execute scripts located in the domain bin directory. Log files and other files created and managed by the WebLogic server processes may also be readable by others. If you wish to secure these files, you will need to follow operating system specific procedures to ensure that files are created with appropriate access rights. If you wish to make files in the WebLogic domain accessible to others, we recommend restricting access to a controlled group.

A WebLogic domain that is created by SAS Deployment Wizard or by using the scripting tools generated during a SAS deployment contains files that may contain some sensitive information. The files C:\SAS\EBIserver\Lev1\Web\SASDomain\nodemanager\nmUserConfigFile.secure and C:\SAS\EBIserver\Lev1\Web\SASDomain\nodemanager\nmUserKeyFile.secure contain encrypted passwords. These files are necessary to allow the scripting framework and SAS Deployment Wizard to connect to the nodemanager and the administration server without user intervention. Read access to these files will also allow anyone to connect to the AdminServer with wlst.cmd without a password, so you need to control access to these files.

The weblogic server start scripts that are generated by the SAS configuration specify the following option on the server command line: -Dweblogic.system.BootIdentityFile="C:\SAS\EBIserver\Lev1\Web\SASDomain\servers\ManagedServerName\data\nodemanager\boot.properties" Note that the same boot.properties credentials are used for all servers. This allows servers to be started without specifying credentials. You may want to remove this option if your local security policies require more restricted access.

Log files and other files created and managed by the WebLogic server processes may still be readable by others. If you wish to make these files accessible to others, we recommend restricting access to a controlled group.

The JAAS Login Module file C:\SAS\EBIserver\Lev1\Web\Common\SASDomain\weblogicLogin.config contains the base-64 encoded trusted user name and password. This file should also be protected.

Starting your WebLogic Application Servers

Starting the Node Manager

There are two options for starting the Node Manager on Windows:

Windows Service: Node Manager can be started by running the "Oracle WebLogic NodeManager (C_SAS_EBIserver_Lev1)" Windows service. SAS Deployment Wizard has installed and started the service.If you should ever need to reinstall it, a SAS configured installer is available at C:\SAS\EBIserver\Lev1\Web\SASDomain\bin\installNodeMgrSvc.cmd.

Startup Script:

startNodeManager.cmd HOSTNAME.example.com 5556

Starting the Administration Server

Admin Server using Startup File: C:\SAS\EBIserver\Lev1\Web\SASDomain\bin\startWebLogic.cmd
The Admin Server can also be started from Node Manager using wlst. This is how SAS Deployment Wizard has started your Adminstrative Server during configuration.

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:
```
C:\SAS\EBIserver\Lev1\Web\SASDomain\bin\startManagedWebLogic.cmd 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

Foreign JNDI Provider Name	SharedServicesJNDIProvider
Provider URL	t3://HOSTNAME.example.com:7001
Initial Context Factory	weblogic.jndi.WLInitialContextFactory

Foreign Link Name	Local JNDI Name	Remote JNDI Name
SharedServicesAlertQueueLink	sas/jms/SharedServicesAlertQueue	sas/jms/AlertQueue
SharedServicesAuditQueueLink	sas/jms/SharedServicesAuditQueue	sas/jms/AuditQueue
SharedServicesJESEventTopicLink	sas/jms/SharedServicesJESEventTopic	sas/jms/JESEventTopic
SharedServicesQueueConnectionFactoryLink	sas/jms/SharedServicesQueueConnectionFactory	sas/jms/QueueConnectionFactory
SharedServicesSASPublishedEventTopicLink	sas/jms/SharedServicesSASPublishedEventTopic	sas/jms/SASPublishedEventTopic
SharedServicesTopicConnectionFactoryLink	sas/jms/SharedServicesTopicConnectionFactory	sas/jms/TopicConnectionFactory
SharedServicesWorkflowQueueLink	sas/jms/SharedServicesWorkflowQueue	sas/jms/WorkflowQueue

Deployed Applications on WebLogic Application Server

The following table lists the applications that have been deployed to your WebLogic Servers

Application Name	Location	Target
SASWebInfrastructurePlatformServices9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.wip.services9.3.ear	SASServer1
SASWebInfrastructurePlatformApplications9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.wip.apps9.3.ear	SASServer1
SASWIPAdmin9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.wip.admin9.3.ear	SASServer1
SASWIPResources9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.wip.resources9.3.ear	SASServer1
SASStoredProcess9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.storedprocess9.3.ear	SASServer1
SASWorkflow9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.workflow9.3.ear	SASServer1
SASContentServer9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.wip.scs9.3.ear	SASServer1
SASFlexThemes3.4	C:\SAS\EBIserver\Lev1\Web\Staging\sas.flexthemes3.4.ear	SASServer1
SASThemeDesigner3.4ForFlex	C:\SAS\EBIserver\Lev1\Web\Staging\sas.themedesigner3.4.ear	SASServer1
SASThemes9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.themes.ear	SASServer1
SASWebReportStudio4.3	C:\SAS\EBIserver\Lev1\Web\Staging/sas.webreportstudio4.3.ear	SASServer1
SASPortal4.3	C:\SAS\EBIserver\Lev1\Web\Staging/sas.portal4.3.ear	SASServer1
SASPackageViewer4.3	C:\SAS\EBIserver\Lev1\Web\Staging/sas.packageviewer4.3.ear	SASServer1
SASBIDashboard4.3	C:\SAS\EBIserver\Lev1\Web\Staging/sas.bidashboard4.3.ear	SASServer1
SASWebDoc9.3	C:\SAS\EBIserver\Lev1\Web\Staging\sas.webdocmd9.3.ear	SASServer1
SASBIPortlets4.3	C:\SAS\EBIserver\Lev1\Web\Staging/sas.biportlets4.3.ear	SASServer1

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\EBIserver\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\EBIserver\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:7001/SASStoredProcess/do
Log file	C:\SAS\EBIserver\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:7001/SASAdmin
Log file	C:\SAS\EBIserver\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:7001/SASWebReportStudio
Log directory	C:\SAS\EBIserver\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:7001/SASPortal
Log file	C:\SAS\EBIserver\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\EBIserver\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\EBIserver\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.
Validation steps	Login to the portal. Add the SAS Navigator Portlet to a portal page. Navigate to different locations.

Notes:

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:7001/SASBIDashboard
Log	C:\SAS\EBIserver\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:7001/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:7001/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, and then running the SAS Deployment Manager to rebuild web applications. Note that some SAS web applications do not support custom content. The custom content root directory for a given web application is

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

For example,

C:\SAS\EBIserver\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.