Installation Instructions for Hot Fix S47006

Windows for x64

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

http://ftp.sas.com/techsup/download/hotfix/HF2/S47.html#S47006

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

S45006  updates  SAS Environment Manager 2.3
P90003  updates  SAS Web Server 9.41

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, S47006pt.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 S47006pt.zip on each machine or save it in a network location that is accessible to all machines.

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

IMPORTANT NOTES

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

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

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

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

5. 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 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 S47006pt.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).

The content of this hot fix is listed in the hot fix manifest.

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

S45006  updates  SAS Environment Manager 2.3
P90003  updates  SAS Web Server 9.41

S45006  updates  SAS Environment Manager 2.3

1. Navigate to <SASHome>/SASEnvironmentManager/2.3/hotfix
   • Execute the following command:

     sasev23_jarfix.bat <SASHome location>

     where <SASHome location> is the full path to SASHome

   • Examine sasev23_jarfix.log located in the directory where the tool was executed. The log will contain the configuration directories the tool found specified with the text (SASCONFIG: ). If you have an installation where there are multiple configuration directories and one or more are missing from the log, re-execute the sasev23_jarfix tool and specify both SASHome and the SAS Configuration directory.

     For example:

     sasev23_jarfix.bat <SASHome location> <SAS Configuration location>

     Note: The tool can safely be run multiple times.

   • Any errors that are found will be written to the error log located in the same directory that the code is executed from.

2. Copy BaseAction.class from

   <SASHome>/SASEnvironmentManager/2.3/hotfix directory
   to
   <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/classes/org/hyperic/hq/ui/json/action/escalation directory

3. Copy BaseSessionInitializationStrategy.class from

   <SASHome>/SASEnvironmentManager/2.3/hotfix directory
   to
   <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/classes/org/hyperic/hq/ui/security directory

4. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib/ directory

   • Delete the following files

     commons-fileupload-1.2.1.jar
     poi-3.0.1-FINAL.jar

   • Copy the following files from <SASHome>/SASEnvironmentManager/2.3/hotfix directory to the current directory

     commons-fileupload-1.3.1.jar
     poi-3.10.1.jar

5. Navigate to <SASConfig>/LevX/Web/Scripts/AppServer/lib

   Rename groovy-all-1.7.0.jar to groovy-all.jar

6. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/conf directory

   • The server.xml file section as listed below is where changes need to be made

     <Connector port="${server.webapp.port}" executor="tomcatThreadPool"
     maxHttpHeaderSize="8192"
              emptySessionPath="true" protocol="HTTP/1.1"
              enableLookups="false" redirectPort="${server.webapp.secure.port}"
     acceptCount="100"
              connectionTimeout="20000" disableUploadTimeout="true" compression="on"
     compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript"/>
     

   • Edit the emptySessionPath property in your server.xml file, changing "true" to "false".

   • If you have a special requirement to run Environment Manager under SSL, you should change the <Connector/> for SSL, but not the non-SSL <Connector/>. The SSL <Connector/> is identified by SSLEnabled="true".

P90003  updates  SAS Web Server 9.41

If you have SAS Web Server 9.41 and SAS Environment Manager 2.3 on the same node, skip to step 3 below:

1. Edit <SASHOME>/SASWebServer/9.4/httpd-2.2.31.1-64/_instance/bin/httpdctl and change

   service_name="Pivotal httpd @ServerInstance@"
   to
   service_name="vFabric httpd @ServerInstance@"

2. Navigate to the <SASHOME>/SASWebServer/9.4/ directory. Delete the existing httpd-2.2 symbolic link and create a new one, for example (assuming your SASHome is in the default location):

   > makelink.exe httpd-2.2 "C:\Program Files\SASHome\SASWebServer\9.4\httpd-2.2.31.1-64"

3. If you have configured the Web Server to use the secure sockets HTTPS protocol then the following steps can be skipped. Otherwise, please complete these steps to activate the new plugin once the system has been restarted:
   1. Log into the SAS Environment Manager console.

   2. Select Resources -> Browse from the Resources dropdown. Then click the Servers link. A list of servers will be displayed.

   3. If there is a Web Server in the discovered server list, click its checkbox. The discovered Web Server name may look like "xxxxxxxx Pivotal Web Server 5.x WebServer" or "xxxxxxxx vFabric Web Server 5.x".

   4. Click the Delete button at the bottom of the webpage to remove this Web Server instance. Then click OK in the confirmation dialog.

   5. Select Dashboard in the webpage toolbar. If there is a Pivotal Web Server 5.5 in Auto-Discovery section, then check the resource and click the Add Into Inventory link. After you add the resource into inventory, please skip the following steps. Otherwise, complete the remaining steps to add the new Web Server to the inventory.

   6. Select Resources -> Browse again, and click the Platforms link. Then click on the machine platform where the Web Server is installed.

   7. Select New Auto-Discovery from the Tools Menu dropdown to request that a new discovery process run.

   8. On the New Auto-Discovery page, click on the Pivotal Web Server 5.5 checkbox. Then click the OK button near the bottom of the webpage.

   9. Select Dashboard in the webpage toolbar. Refresh the dashboard page repeatedly until the newly discovered Web Server appears in the webpage's Auto-Discovery section. Then check the resource and click the Add Into Inventory link.

      Note: If you cannot find the new Pivotal Web Server 5.5 resource in Resources -> Servers page after you clicked the Add Into Inventory link, login to the machine where the Pivotal Web Server 5.5 is installed, stop the Environment Manager Agent on this machine, re-name the data directory under <SASConfig>/LevX/Web/SASEnvironmentManager/agent-5.8.0-EE/ to data_backup, and then restart the Environment Manager Agent. The new Pivotal Web Server 5.5 resource should appear on the Auto-Discovery section. Select and click the Add Into Inventory link to add this new resource into inventory.

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


Copyright 2016 SAS Institute Inc. All Rights Reserved.