Installation Instructions for Hot Fix W43008

64-bit Enabled Solaris

Hot fix W43008 addresses the issue(s) in SAS Web Application Server 9.42 on 64-bit Enabled Solaris as documented in the Issue(s) Addressed section of the hot fix download page:

The hot fix downloaded,, 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 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.


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


The W43008 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, 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:

  1. For SASServer1, navigate to <SASConfig>/LevX/Web/WebAppServer/SASServer1_?/conf/Catalina/localhost/

    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_?.

  2. Edit the SASWorkflowServices.xml file as follows:

    <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"/>

  3. Once this change has been made, return to the SDM and click the retry button. This should allow the SDM to complete the upgrade configuration task.
Perform the following steps for each configured SAS tc Server instance

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


below the line containing


to the end of the JAVA_OPTS line to make

Update to sas.vfabrictcsvr.jar
  1. Stop all mid-tier servers.

  2. Copy <SASHome>/SASWebApplicationServer/9.4/hotfix/sas.vfabrictcsvr.jar to the <SASConfig>/Lev1/Web/WebAppServer/SASServer1_1/lib/ directory.

  3. Repeat Step 2 for each SASServer1_<X> instance (where <X> indicates the server instance number, eg: SASServer1_6) by copying the sas.vfabrictcsvr.jar to the corresponding SASServer1_<X>/lib directory.

  4. Copy <SASHome>/SASWebApplicationServer/9.4/hotfix/sas.vfabrictcsvr.jar to the <SASHome>/SASDeploymentManager/9.4/products/cfgwizard__94496__prt__xx__sp0__1/Utilities/AppServer/Source/Config/vfabrictcsvr/jars/sas/ directory.

    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.

  5. Restart all mid-tier servers including each SASServer1_<X> instance where the jar was copied.

This completes the installation of hot fix W43008 on 64-bit Enabled Solaris.

Copyright 2019 SAS Institute Inc. All Rights Reserved.