SAS 9.3 Web Applications: Clustering - Index of - SAS
SAS 9.3 Web Applications: Clustering - Index of - SAS
SAS 9.3 Web Applications: Clustering - Index of - SAS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
2 For all servers except the stand-alone server, prevent the clustered JBoss<br />
instances from creating JMS connection factories by editing the<br />
<strong>SAS</strong>Server2\deploy\messaging\connection-factories-service.xml<br />
file. Comment out the two bindings that are related to <strong>SAS</strong> JMS resources:<br />
<br />
<br />
<br />
/ConnectionFactory<br />
/XAConnectionFactory<br />
java:/ConnectionFactory<br />
java:/XAConnectionFactory<br />
<br />
<br />
Use JMS Resources on the Stand-Alone Server<br />
This section applies to all versions <strong>of</strong> JBoss Application Server. Reconfigure the<br />
clustered <strong>Web</strong> application servers to use the JMS resources on <strong>SAS</strong>Server1:<br />
1 Edit the <strong>SAS</strong>Server2\conf\jboss-service.xml file and add the following<br />
mbean:<br />
<br />
<strong>SAS</strong>Server1JNDI<br />
<br />
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory<br />
java.naming.provider.url=jnp://<strong>SAS</strong>Server1-ip-address:1099<br />
<br />
true<br />
jboss:service=Naming<br />
<br />
Note: <strong>SAS</strong>Server1JNDI does not need to be the JNDI name. Just make sure<br />
that you use the same value in the next step.<br />
2 For the following <strong>Web</strong> applications, change the WEB-INF\jboss-web.xml file.<br />
Replace all occurrences <strong>of</strong> sas/jms with <strong>SAS</strong>Server1JNDI/sas/jms for all<br />
the elements.<br />
n deploy_sas\sas.wip.services<strong>9.3</strong>.ear\sas.wip.services.war<br />
n deploy_sas\sas.wip.services<strong>9.3</strong>.ear<br />
\sas.wipsoapservices.war<br />
Configure Additional JBoss Server Instances 23<br />
n deploy_sas\sas.workflow<strong>9.3</strong>.ear\sas.workflow.war<br />
Note: Modify sas.workflow.war only if you are using the <strong>Web</strong> application in<br />
the cluster.<br />
The strategy described in this section leaves the stand-alone server as a single<br />
point <strong>of</strong> failure for JMS resources. If the deployment requires high availability,<br />
then consider the options described in “Hot and Cold Standby Strategy” on page
Change language