Hot fix W43009 addresses the issue(s) in SAS Web Application Server 9.42 on Linux for x64 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/W43.html#W43009
The hot fix downloaded, W43009pt.zip, contains the updated files required to address
the documented issues.
This hot fix should be applied to all applicable operating systems on which SAS Web Application Server 9.42 has been installed.
Do NOT extract the contents of W43009pt.zip. The hot fix installation process will extract the contents as needed.
This hot fix requires that your software must already be configured prior to installation. If no configuration directory exists at the time of installation, security updates built into this hot fix will not be completed, leaving your software in a vulnerable state.
After downloading W43009pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.
Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.
The content of this hot fix is listed in the hot fix manifest.
IMPORTANT NOTE: If your SAS Web Server is configured for TLS, you will need to install the latest Java 7 Update. Please visit the Updates for Java 7 download page for the latest available updates.
Upgrade-in-place installations or update existing configuration in SAS Deployment Manager:
Due to changes in the xml files during upgrade-in-place scenarios, the SAS Deployment Manager will show a failure during the upgrade of existing configuration for SAS Web Application Server after this hot fix has been applied. In a clustered configuration, this failure could happen on the primary machine and all cluster nodes. When this occurs, leave the SAS Deployment Manager running and use a separate session to make the following change:
NOTE: The '?' in SASServer1_? can be an integer starting from 1 in a configuration with vertical cluster nodes. If you have custom server names, the server instance names should end with 1_?.
Change<ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory" type="org.apache.activemq.ActiveMQConnectionFactory"/>
to
<ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory" type="javax.jms.ConnectionFactory"/>
Make the following changes to <SASConfig>/LevX/Web/WebAppServer/SASServer1_X/bin/setenv.sh if
Environment Manager MidTier is configured on SASServer1_X (for a single server configuration).
Make the following changes to <SASConfig>/LevX/Web/WebAppServer/SASServer2_X/bin/setenv.sh if
Environment Manager MidTier is configured on SASServer2_X (for a multiple server configuration).
If Environment Manager MidTier is not configured, this step can be skipped.
Insert:
JAVA_WHITELIST="-Dorg.apache.activemq.SERIALIZABLE_PACKAGES=java.lang,java.util,org.apache.activemq,org.fusesource.hawtbuf,com.thoughtworks.xstream.mapper,com.sas.ev.framework.registry"
below the line containing
JAVA_LIBRARY_PATH="".
Add:
$JAVA_WHITELISTUpdate to sas.vfabrictcsvr.jar
to the end of the JAVA_OPTS line to make
JAVA_OPTS="$JVM_OPTS $AGENT_PATHS $JAVA_AGENTS $JAVA_LIBRARY_PATH $JAVA_WHITELIST".
NOTE: If you find multiple <SASHOME>/SASDeploymentManager/9.4/products/cfgwizard* directories, copy the sas.vfabrictcsvr.jar to the cfgwizard* directory that contains the highest number in its naming string.
This completes the installation of hot fix W43009 on Linux for x64.
Copyright 2021 SAS Institute Inc. All Rights Reserved.