Installation Instructions for Hot Fix W43001
Windows for x64
Hot fix W43001 addresses the issue(s) in SAS Web Application Server 9.42 on Windows for x64 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/W43.html#W43001
The hot fix downloaded, W43001pt.zip, contains the updated files required to address
the documented issues.
Do NOT extract the contents of W43001pt.zip. The hot fix installation process will extract
the contents as needed.
IMPORTANT NOTES
-
You must have SAS Web Application Server 9.42 installed on your system before applying this hot fix.
Refer to SN-35968 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 required 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 W43001 hot fix for SAS Web Application Server 9.42 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 W43001pt.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
This hot fix delivers the following files to the <SASHome>\SASWebApplicationServer\9.4 directory:
apache-activemq-5.12.0-bin.zip
apache-activemq-5.12.0-bin.tar.gz
activemq-client-5.12.0.jar
activemq-kahadb-store-5.12.0.jar
hawtbuf-1.11.jar
activemq-jms-pool-5.12.0.jar
activemq-pool-5.12.0.jar
commons-pool2-2.3.jar
Follow the instructions below to upgrade the ActiveMQ standalone server:
-
Navigate to the <SASHome>/SASDeploymentManager/9.4/products/cfgwizard__#####__prt__xx__sp0__1/Utilities/AppServer/
Source/Config/vfabrictcsvr directory
NOTE: You may have multiple cfgwizard_* directories.
Choose the one that has the highest number represented by the ##### in the location above.
-
Rename apache-activemq-5.7.0-bin.zip
to
apache-activemq-5.7.0-bin.zip.bkup
-
Copy
<SASHome>\SASWebApplicationServer\9.4\apache-activemq-5.12.0-bin.zip
to
the current directory
(ie:
<SASHome>\SASDeploymentManager\9.4\products\cfgwizard__#####__prt__xx__sp0__1\Utilities\AppServer\Source\Config\vfabrictcsvr
directory)
-
Rename
apache-activemq-5.12.0-bin.zip
to
apache-activemq-5.7.0-bin.zip
-
Copy
<SASHome>\SASWebApplicationServer\9.4\apache-activemq-5.12.0-bin.zip
to
the <SASConfig>\LevX\Web directory
-
Navigate to the <SASConfig>\LevX\Web directory
-
Unzip apache-activemq-5.12.0-bin.zip:
This will create a <SASConfig>\LevX\Web\apache-activemq-5.12.0 directory.
-
Rename
the <SASConfig>\LevX\Web\activemq directory
to
activemq.bkup
-
Rename
the <SASConfig>\LevX\Web\apache-activemq-5.12.0 directory
to
activemq
-
Rename <SASConfig>\LevX\Web\activemq\bin\win64\wrapper.conf
to
wrapper.conf.bkup
-
Copy <SASConfig>\LevX\Web\activemq.bkup\bin\win64\wrapper.conf
to
<SASConfig>\LevX\Web\activemq\bin\win64 directory
-
Edit <SASConfig>\LevX\Web\activemq\bin\win64\wrapper.conf, as follows:
Replace line 41 of wrapper.conf, which is:
wrapper.java.classpath.2=%ACTIVEMQ_HOME%\bin\run.jar
with
wrapper.java.classpath.2=%ACTIVEMQ_HOME%\bin\activemq.jar
Note: If you made customizations to the pre-hotfix version of activemq.xml, i.e. <SASConfig>\LevX\Web\activemq.bkup\conf\activemq.xml, including port numbers, they will be lost unless you apply them back to the updated version in <SASConfig>\LevX\Web\activemq\conf\activemq.xml.
This completes the steps needed to upgrade the ActiveMQ standalone server.
Follow the steps below to copy the ActiveMQ client jars used by SAS web apps.
-
Navigate to
<SASHome>\SASDeploymentManager\9.4\products\cfgwizard__#####__prt__xx__sp0__1\Utilities\AppServer\Source\Config\vfabrictcsvr\jars\ directory
-
Rename activemq
to
activemq.bkup
-
Create a new directory named activemq
-
Copy the following jars from
<SASHome>\SASWebApplicationServer\9.4 directory
to
the activemq directory:
activemq-client-5.12.0.jar
activemq-kahadb-store-5.12.0.jar
hawtbuf-1.11.jar
activemq-jms-pool-5.12.0.jar
activemq-pool-5.12.0.jar
commons-pool2-2.3.jar
-
Perform the following steps for each configured SAS tc Server instance
-
Create a Backup subdirectory in each instance's <SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib directory
-
Move the following jar files from each web app server'
<SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib directory
into
<SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib\Backup directory:
activemq-core-5.7.0.jar
kahadb-5.7.0.jar
activemq-pool-5.7.0.jar
commons-pool-1.6.jar
-
Copy all the jar files delivered to
<SASHome>\SASWebApplicationServer\9.4
into
<SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib directory.
-
Inspect each <SASConfig>/LevX/Web/WebAppServer/SASServerX_X/conf/server.xml file. Make changes below if
org.apache.activemq.pool.AmqJNDIPooledConnectionFactory appears in server.xml. If the string is not found, this step
can be skipped.
Change:
org.apache.activemq.pool.AmqJNDIPooledConnectionFactory
to
org.apache.activemq.pool.PooledConnectionFactory (e.g. in the EVQueueConnectionFactory Resource statements).
Other Resources containing Resource statements that reference org.apache.activemq.pool.AmqJNDIPooledConnectionFactory should also
be changed to org.apache.activemq.pool.PooledConnectionFactory, if they exist.
-
Delete the following file:
<SASHome>\SASWebApplicationServer\9.4\templates\sas\lib\activemq-core-5.4.3.jar
-
Restart the standalone ActiveMQ server, ActiveMQ clients and web app servers with web apps that use ActiveMQ
Note: Please see SAS Note 5707 if if appears that the SAS Java Message
broker is not running.
This completes the installation of hot fix W43001 on Windows for x64.
Copyright 2015 SAS Institute Inc. All Rights Reserved.