After applying SAS Web Application Server hot fixes, manual post-installation steps are required to complete configuration of a horizontal mid-tier cluster.
Important Note: These instructions assume that you have applied the latest SAS Web Server hot fixes available. The latest SAS Web Server hot fixes are listed at the bottom of the Updates for Java Deserialization Vulnerability page under the "Product-Specific Hot Fixes" section.
Complete the following steps for each middle-tier cluster node.
- Shut down all SAS sessions, daemons, spawners, servers and agents.
- Copy all the delivered JAR files from the folder <SASHome>/SASWebApplicationServer/9.4/hotfix on the main node to the following location on each cluster node:
<SASConfig>/Web/WebAppServer/SASServerX_X/lib
Note: Once copied, you will need to delete any previous versions of the same jars in the destination directory
- Update <SASConfig>/Web/WebAppServer/SASServerX_X/conf/server.xml by replacing all occurrences of
“org.apache.activemq.pool.AmqJNDIPooledConnectionFactory”
with
“org.apache.activemq.pool.PooledConnectionFactory”.
- Find <SASConfig>/Web/WebAppServer/SASServerX_X/bin/setenv.sh (for UNIX) or <SASConfig>/Web/WebAppServer/SASServerX_X/bin/setenv.bat (for Windows) on the primary cluster node. Copy the entry in the file that begins as described below and then paste it into the file with the same name in each secondary cluster node.
For Windows:
set JAVA_WHITELIST=<…>
For UNIX:
JAVA_WHITELIST=“<…>”
- Find <SASConfig>/Web/WebAppServer/SASServerX_X/conf/wrapper.conf on the primary node. Copy the entry in the file that begins as described below and then paste it into the file with the same name in each secondary cluster node.
wrapper.java.additional.##=<…>