Installation Instructions for Hot Fix W43002

Windows for x64


Hot fix W43002 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#W43002


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


IMPORTANT NOTES

  1. 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.

  2. 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.

  3. You must have Administrator Privileges on your CLIENT or SERVER machine.

  4. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  5. This hot fix should be installed using the same userid who performed the initial software installation.

  6. This hot fix should be applied each time that the SAS Web Application servers are configured.

  7. 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 W43002 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 W43002pt.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\hotfix directory:

apache-activemq-5.12.2-bin.zip
apache-activemq-5.12.2-bin.tar.gz
activemq-client-5.12.2.jar
activemq-kahadb-store-5.12.2.jar
hawtbuf-1.11.jar
activemq-jms-pool-5.12.2.jar
activemq-pool-5.12.2.jar
commons-pool2-2.4.2.jar
Follow the instructions below to upgrade an ActiveMQ standalone server on the main Middle Tier node. These steps should not be performed on a Middle Tier cluster node:
  1. Navigate to the <SASConfig>\LevX\Web directory

  2. Copy <SASHome>\SASWebApplicationServer\9.4\hotfix\apache-activemq-5.12.2-bin.zip
    to
    the current directory
    (ie: <SASConfig>\LevX\Web directory)

  3. Unzip apache-activemq-5.12.2-bin.zip:
    This will create a <SASConfig>\LevX\Web\apache-activemq-5.12.2 directory.

  4. Rename the <SASConfig>\LevX\Web\activemq directory
    to
    activemq.bkup

  5. Rename the <SASConfig>\LevX\Web\apache-activemq-5.12.2 directory
    to
    activemq

  6. Rename <SASConfig>\LevX\Web\activemq\bin\win64\wrapper.conf
    to
    wrapper.conf.bkup

  7. Copy <SASConfig>\LevX\Web\activemq.bkup\bin\win64\wrapper.conf
    to
    <SASConfig>\LevX\Web\activemq\bin\win64 directory

  8. 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
  9. Rename <SASConfig>\LevX\Web\activemq\conf\activemq.xml
    to
    activemq.xml.bkup

  10. Copy <SASConfig>\LevX\Web\activemq.bkup\conf\activemq.xml
    to
    <SASConfig>\LevX\Web\activemq\conf directory

Note: If you made customizations to the pre-hotfix versions of files other than win64/wrapper.conf and conf/activemq.xml, they will be lost unless you re-apply them. The files in activemq.bkup will contain the previous customizations.

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. These steps should be performed on all Middle Tier nodes, including cluster nodes:

  1. Perform the following steps for each configured SAS tc Server instance

    1. Create a Backup subdirectory in each instance's <SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib directory

    2. Move the following jar files from each web app server's <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

    3. Copy all the jar files delivered to <SASHome>\SASWebApplicationServer\9.4\hotfix
      into
      <SASConfig>\LevX\Web\WebAppServer\SASServerX_X\lib directory.

    4. 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.

    5. Make the following changes to <SASConfig>/LevX/Web/WebAppServer/SASServer1_X/bin/setenv.bat 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.bat 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:

      set 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
      set JAVA_LIBRARY_PATH=.

      Add:

      %JAVA_WHITELIST%
      to the end of the JAVA_OPTS line to make
      set JAVA_OPTS=%JVM_OPTS% %AGENT_PATHS% %JAVA_AGENTS% %JAVA_LIBRARY_PATH% %JAVA_WHITELIST%.

  2. Delete the following files:
    <SASHome>\SASWebApplicationServer\9.4\templates\sas\lib\activemq-core-5.4.3.jar
    <SASHome>\SASWebApplicationServer\9.4\templates\sas\lib\xalan.jar

  3. Restart the standalone ActiveMQ server, ActiveMQ clients and web app servers with web apps that use ActiveMQ



    4. Note: Please see SAS Note 5707 if it appears that the SAS Java Message broker is not running.



This completes the installation of hot fix W43002 on Windows for x64.


Copyright 2015 SAS Institute Inc. All Rights Reserved.