Installation instructions for hot fix M3P003 on Solaris for x64

Installation Instructions for Hot Fix M3P003

Solaris for x64

Hot fix M3P003 addresses the issue(s) in SAS Web Application Server 9.48 on Solaris for x64 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/M3P.html#M3P003

The hot fix downloaded, M3P003pt.zip, contains the updated files required to address the documented issues.
Do NOT extract the contents of M3P003pt.zip. The hot fix installation process will extract the contents as needed.

IMPORTANT NOTES

You must have SAS Web Application Server 9.48 installed on your system before applying this hot fix. Refer to SAS KB0036131 for instructions on how to determine which product releases you have installed.
Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.

INSTALLATION

The M3P003 hot fix for SAS Web Application Server 9.48 will be installed using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>/InstallMisc/HotFixes/New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading M3P003pt.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.

POST-INSTALLATION INSTRUCTIONS

In a multi-tier deployment, the ActiveMQ client jars will also be present on the Metadata Server and Server (Compute) Tiers. This hot fix, M3P003, cannot be installed on these Tiers, so these jars are not removed or updated by the hotfix. The jars (5.17.2 or 5.17.4 versions) are not in use and can be safely removed from these Tiers.

The jars are located under the following SAS-configuration-directories:

/Web/Scripts/AppServer/src/Config/vfabrictcsvr/jars/activemq/activemq-*.jar
/Web/Scripts/SASEnvironmentManagerAgent/src/Config/vfabrictcsvr/jars/activemq/activemq-*.jar

Hot Fix Notes

This hot fix must be installed separately. It is not included in the SAS Software Depot.
If this hot fix is installed on a 94M8 environment and that environment is upgraded to a later release of 94M8, the older version of the ActiveMQ jars will be reinstalled on the environment during the upgrade in place process. It is necessary to re-install this hot fix in such cases.
With SSL/FIPS configured, a Warning appears in the Tomcat log file about unsupported ciphers:
WARN (main) [org.apache.tomcat.util.net.openssl.OpenSSLUtil] Tomcat interprets the [ciphers] attribute in a manner consistent with the latest OpenSSL development branch. Some of the specified [ciphers] are not supported by the configured SSL engine for this connector (which may use JSSE or an older OpenSSL version) and have been skipped: [[<<<A list of skipped ciphers appears here>>>]]
This Warning indicates that some of the specified ciphers are skipped and is not a security issue. See https://bz.apache.org/bugzilla/show_bug.cgi?id=67628#c10 for more information.