SAS 9.3 Web Applications: Clustering - Index of - SAS

20 Chapter 3 / JBoss Clustering
Application Target
sas.wip.admin9.3.ear This Web application can be clustered, but you might prefer to
deploy it to the stand-alone server because it is not used by
business users.
sas.wip.apps9.3.ear Target all servers in the cluster.
sas.wip.resources9.3.ear Target all servers in the cluster.
sas.wip.scs9.3.ear Target all servers in the cluster.
sas.wip.services9.3.ear Target all servers in the cluster.
sas.workflow9.3.ear Target all servers in the cluster if you have performed the steps
in “Reconfigure SAS Workflow” on page 9. Otherwise, target the
stand-alone server.
Configure Additional JBoss Server
Instances
Configure Port Numbers
JBoss AS 4.2.3.GA and JBoss EAP 4.3
1 Edit the SASServer2\conf\jboss-service.xml file. Change all instances of
SASServer1 to SASServer2 as shown in this example:
SASServer2
C:\jboss\server\SASServer2\conf\port-bindings.xml
org.jboss.services.binding.XMLServicesStoreFactory
2 For vertical cluster deployments, with multiple instances of JBoss on the same
machine, edit the SASServer2\conf\port-bindings.xml file to avoid port
conflicts. Change the instances of ports-01 to SASServer2. This change sets
SASServer2 to use a unique set of ports. All the ports are incremented by 100
over the ports used by SASServer1. This typically results in SASServer2 using
port 8180 for HTTP. See this example: