Installation Instructions for Hot Fix V77016

Windows for x64

Hot fix V77016 addresses the issue(s) in SAS Web Server 9.4_M3 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/V77.html#V77016

V77016 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

V75007  updates  SAS Web Server 9.42

Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, V77016pt.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save V77016pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of V77016pt.zip. The hot fix installation process will extract the contents as needed.

SPECIAL NOTE REGARDING SECURITY VULNERABILITY

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.

IMPORTANT NOTES

1. Special Note regarding Windows 2008, 2008R, 2012 and 2012R

   If you are running on one of the above mentioned operating systems, you will need to download and install updated VC++ libraries from Microsoft.
   Please visit https://www.microsoft.com/en-us/download/details.aspx?id=52685 to obtain these libraries.
   Failure to do so will result in SAS Web Server being unable to restart after applying this hot fix.

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

7. If your SAS Web Application Server is configured with FIPS enabled, then you will need to follow the information contained in SAS Note 61795.

INSTALLATION

The hot fix will be applied 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 V77016pt.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 hot fix installation process generates the log file

<!SASHOME>/InstallMisc/InstallLogs/IT_date-and-time-stamp.log

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the ‘member’ hot fix id in the name of the file and are also written to the <!SASHOME>/InstallMisc/InstallLogs directory. There is one postexec log for each ‘member’ hot fix applied (member hot fixes are listed at the top of these instructions).

POST-INSTALLATION INSTRUCTIONS

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.

IMPORTANT NOTES Regarding hot fix updates:

1. This hot fix will create a backup configuration directory under <SASConfig>/LevX/Web/WebServerBackup. If you manually changed any configuration settings for SAS Web Server, you must manually merge these settings back into the new web server configuration.

2. This hot fix updates the Apache httpd server from version 2.2 to version 2.4. Any manually configured changes for SAS Web Server related to Apache 2.2 will need to be updated to reflect Apache 2.4.

3. For SiteMinder configuration using the updated Apache version, please review information in SAS® 9.4 Intelligence Platform: Middle-Tier Administration Guide, Fourth Edition
   For the updated Apache version delivered in this hot fix, step 2 under "Configuring SAS Web Server for the Web Agent" should read as follows:
   
   Edit the SAS-configuration-directory\Levn\Web\WebServer\conf\httpd.conf file. Add lines that are similar to the following at the beginning of the LoadModule directives:

   LoadModule sm_module "C:/Program Files (x86)/CA/webagent/bin/mod_sm24.dll"
   SmInitFile "C:/SAS/Config/Lev1/Web/WebServer/conf/WebAgent.conf"

   For UNIX deployments, the name of the library is libmod_sm24.so instead of mod_sm24.dll.

1. For multi-tier or clustered deployments, manually copy JAR files listed below from the node where SAS Web Server is installed to other nodes in the deployment.

   The standard locations of the JAR files on the SAS Web Server node are (note that "LevX" refers to the configuration level directory, such as Lev1):

   <SASConfig>/LevX/Web/Scripts/WebServer/lib/commons-collections.jar
   <SASConfig>/LevX/Web/Scripts/WebServer/lib/groovy-all.jar
   

   Copy the files above to the following locations on the other nodes if the directory exists:

   <SASConfig>/LevX/Web/Scripts/WebServer/lib/commons-collections.jar
   < SASConfig>/LevX/Web/Scripts/WebServer/lib/groovy-all.jar

   <SASConfig>/LevX/Web/Scripts/AppServer/lib/commons-collections.jar
   < SASConfig>/LevX/Web/Scripts/AppServer/lib/groovy-all.jar

   <SASConfig>/LevX/Web/Scripts/SASEnvironmentManager/lib/commons-collections.jar
   < SASConfig>/LevX/Web/Scripts/ SASEnvironmentManager/lib/groovy-all.jar

   <SASConfig>/LevX/Web/Scripts/SASEnvironmentManagerAgent/lib/commons-collections.jar
   < SASConfig>/LevX/Web/Scripts/SASEnvironmentManagerAgent/lib/groovy-all.jar

2. If you have configured TLS manually for SAS Web Server post-deployment, to use SAS Environment Manager to monitor SAS Web Server, complete the following steps:
   1. Edit the <SASConfig>/LevX/Web/WebServer/conf/httpd.conf file and make the following changes:

      Replace the line

      Listen 80

      with the following line:

      Listen localhost:7980

      IMPORTANT NOTE:  If you use a non-default port, please enter that port number instead of the one listed above

   2. Edit the <SASConfig>/LevX/Web/WebServer/conf/extra/httpd-ssl.conf file and make the following changes:

      Locate the following lines for the certificate file and key file and enter the correct filenames: SSLCertificateFile "ssl/myhost.crt"
      SSLCertificateKeyFile "ssl/myhost.key"
      SSLCertificateChainFile "ssl/myhost.crt

3. If you manually configured TLS for SAS Web Application Server, complete the following step

   1. Edit the <SASConfig>/LevX/Web/WebServer/conf/sas.conf file and add the following two lines:

      SSLProxyCheckPeerCN off
      SSLProxyCheckPeerName off

4. If you configured TLS for SAS Web Server, SAS Environment Manager is not configured for TLS, and is also on the same machine as the Web Server, complete this step if applicable:
   1. Edit the <SASConfig>/LevX/Web/WebServer/conf/sas.conf file and comment out the following directive:

      Replace the line

      Header set Strict-Transport-Security "max-age=31536000"

      with the following line:

      #Header set Strict-Transport-Security "max-age=31536000"

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


Copyright 2017 SAS Institute Inc. All Rights Reserved.