Configuration Guidelines and Details for "busas"

Overview

Warnings and Notices
SAS Management Console
SAS Application Servers
SAS Environment Manager Agent Configuration
Obtaining Additional Information

Warnings and Notices

Review the Hot Fix Instructions document at /opt/sasinside/sashome/InstallMisc/HotFixes/Documents/HotFixInstructions.html for manual steps required to complete your deployment.

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 via:
```
-APPLETLOC="http://web-server:port/sasweb/graph"
```
The web server port is typically 80 on Windows deployments and 7980 on other deployments. Deployments that do not use a web server can point directly to the SAS Web Application Server, which typically uses port 8080.
NOTE: Do not add this line to the sasv9_usermods.cfg file until the SAS middle tier is configured. After updating the file, restart the object spawner and validate your Workspace, Pooled Workspace, and the Stored Process servers again.

SAS Management Console

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

Startup command	/opt/sasinside/sashome/SASManagementConsole/9.4/sasmc For easier access, the installation directory /opt/sasinside/sashome/SASManagementConsole/9.4 can be placed in the executable path environment variable. Likewise, aliases or symbolic links can be created to reference the command.
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	busas.binghamton.edu
Port	8561
Log directory	/opt/sasinside/config/metadata/Lev1/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/94administration.
Execution type	Shell script /opt/sasinside/config/metadata/Lev1/SASMeta/MetadataServer/MetadataServer.sh

Notes:

The metadata server is configured to perform unassisted metadata server backups. The backups are performed every day at 1 a.m. except on Sunday and stored in the "/opt/sasinside/config/metadata/Lev1/SASMeta/MetadataServer/Backups" directory. Backups are retained for seven days. To learn about the metadata server backup facility, see "Backing Up and Recovering the SAS Metadata Server" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/94administration.
The metadata server is configured to send an alert e-mail message to ksmith@binghamton.edu 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 Properties sheet for the active metadata server 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 metadata - Lev1 <noreply@rtms.binghamton.edu>. If you want to change your alert e-mail options, see the section "Managing Alert E-mail Options for the SAS Metadata Server" in the chapter "Metadata Server Configuration Tasks" of the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/94administration.

SAS Environment Manager Agent Configuration

SAS Environment Manager Agent Home Dir	/opt/sasinside/config/metadata/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE
SAS Environment Manager Agent Host Name	busas.binghamton.edu
SAS Environment Manager Agent Port	2144
Log directory	/opt/sasinside/config/metadata/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/log

Starting and Stopping SAS Environment Manager Agent

You can start and stop your SAS Environment Manager Agent with the following commands.

To start SAS Environment Manager Agent, enter

cd /opt/sasinside/config/metadata/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/bin
./hq-agent.sh start

To stop SAS Environment Manager Agent, enter

./hq-agent.sh stop

To restart SAS Environment Manager Agent, enter

./hq-agent.sh restart

The "restart" command will force the agent to contact the SAS Environment Manager and then save the connection settings to the agent's /opt/sasinside/config/metadata/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/data directory.

Obtaining Additional Information

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

The SAS system now includes a Deployment Backup utility that can back up the following components of your SAS deployment:

the metadata server
selected data and configuration directories on any SAS server tier
the SAS Content Server repository
any SAS Web Infrastructure Data Server databases
custom directories configured for your site

If the Deployment Backup utility is configured on your system, it will automatically run every Sunday at 1 a.m. The automatic backup schedule can be changed or disabled. For more information, see "Using the Deployment Backup and Recovery Tool" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/94administration.

Caution: Regular backups of your SAS system are crucial to ensuring the health of your SAS 9.4 Intelligence Platform configuration. It is recommended that you schedule regular system backups to occur just after the SAS metadata or deployment backups so that each system backup includes a timely backup of your SAS components. For more information, see "Best Practices for Backup and Restore" in the SAS Intelligence Platform: System Administration Guide at http://support.sas.com/94administration.