SAS 9.3 Web Applications: Clustering - Index of - SAS

34 Chapter 4 / Oracle WebLogic Server 11g Clustering
-Dsas.appserver.instance.id=SASServer2
-Dsas.wrs.keyUserActionLog.path=
/opt/SAS/Config/Lev1/Web/Logs/SASServer2
Also add this parameter to each server instance, using the appropriate server
instance ID value. This value is used in logging.
Click Save.
Create a Cluster and Assign the Servers
Create a cluster from the newly cloned servers. Leave SASServer1 as the standalone
server. Follow these steps:
1 In the Domain Structure panel, select Environment � Clusters and then click
New.
2 On the Create a New Cluster page, provide a name for the cluster such as
SASCluster1. The other values can remain unchanged. Click OK.
3 Select SASCluster1.
4 Click Servers and then click Add.
5 On the Add a Server to Cluster page, select a cloned server from the list and
then click Next.
6 Add additional servers to the cluster in the same way.
Target the Mail Session to the Cluster
The SAS Mail Session must be targeted to all servers in the cluster and the standalone
server. To target the SAS Mail Session, follow these steps:
1 In the Domain Structure panel, select Services � Mail Sessions.
2 Select SASMailSession.
3 Click Targets. Select the check box for each server in the cluster and the standalone
server.
Click Save.
Reconfigure the JMS Resources
Strategy
The Events Generation Framework and other SAS Web applications use JMS
resources. The SAS Deployment Wizard configured the JMS resources for the first