Hot fix P38005 addresses the issue(s) in SAS Web Application Server 9.4 on Windows for x64 as documented in the Issue(s) Addressed section of the hot fix download page:
The hot fix downloaded, P38005pt.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.4 has been installed.
Do NOT extract the contents of P38005pt.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 P38005pt.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.
activemq_jarfix_m0.bat <SASHome location>
where <SASHome location> is the full path to SASHome
activemq_jarfix_m0.bat <SASHome location> <SAS Configuration location>Note: The tool can safely be run multiple times.
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_?.
<ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory" type="org.apache.activemq.ActiveMQConnectionFactory"/>
<ResourceLink global="sas/jms/QueueConnectionFactory" name="jms/QueueConnectionFactory" type="javax.jms.ConnectionFactory"/>
This completes the installation of hot fix P38005 on Windows for x64.
Copyright 2018 SAS Institute Inc. All Rights Reserved.