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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configure JBoss to Use mod_jk<br />
At this stage <strong>of</strong> the reconfiguration, Apache HTTP Server is prepared to load balance<br />
HTTP requests. There is a stand-alone JBoss server that does not participate in<br />
clustering and at least two JBoss servers that are prepared to run in a cluster. This<br />
stage describes the steps that you must perform to configure each managed server<br />
to interface with the load-balancing HTTP server. Follow these steps for each JBoss<br />
server:<br />
1 Edit the server.xml file. Select the correct location:<br />
n JBoss AS 4.2.3.GA and JBoss EAP 4.3<br />
JBOSS_HOME\server\<strong>SAS</strong>Servern\deploy\jboss-web.deployer<br />
n JBoss AS 5.1.0.GA<br />
JBOSS_HOME\server\<strong>SAS</strong>Servern\deploy\jbossweb.sar<br />
Make the following changes:<br />
a Confirm that the AJP Connector is enabled:<br />
<br />
b Add a jvmRoute attribute to the existing Engine element:<br />
<br />
Use "<strong>SAS</strong>Server2" when you edit the file for <strong>SAS</strong>Server2. These jvmRoute<br />
values match the names and case that is used in the worker.properties and<br />
uriworkermap.properties files. If the case does not match, then session affinity<br />
does not work.<br />
2 (Optional) Enable logging <strong>of</strong> access requests by enabling the AccessLogValve in<br />
the server.xml file. You can disable this after confirming that your configuration is<br />
stable:<br />
<br />
<br />
Perform Common Configuration Tasks<br />
Perform Common Configuration Tasks 27<br />
To complete JBoss clustering, perform the tasks in “Common Tasks” on page 53.
Change language