Installation Instructions for Hot Fix V77006

HP-UX IPF


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

V76006  updates  SAS Environment Manager 2.5
V75001  updates  SAS Web Server 9.42

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.


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

Do NOT extract the contents of V77006pt.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

Hot Fix V77006 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of SAS Web Server 9.4_M3 require updating on the machine. See SAS Note 44810 for more details.

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 V77006pt.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
for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

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.

V76006  updates  SAS Environment Manager 2.5
V75001  updates  SAS Web Server 9.42


V76006  updates  SAS Environment Manager 2.5

  1. Make sure that the SAS Environment Manager Server has been stopped.

    If you have previously installed any of the V76 hot fixes, please skip to #5 below:

  2. Copy vfws-plugin.jar from
    <SASHome>/SASEnvironmentManager/2.5/plugins/ directory
    to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/hq-plugins/ directory.

  3. Copy sas.hyperic.security.sso.jar file from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
    to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib directory.

  4. Copy groovy-all-1.7.0.jar file from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
    to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib directory and
    <SASHome>/SASEnvironmentManager/2.5/installer/lib directory and
    <SASHome>/SASEnvironmentManagerAgent/2.5/installer/lib directory.

  5. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/agent-5.8.0-EE/bundles/agent-5.8.0/pdk/plugins/scripting directory
    1. Delete file: groovy-all-2.3.7.jar

    2. Copy file groovy-all-2.3.7.jar from <SASHome>/SASEnvironmentManager/2.5/hotfix directory
      to
      the current directory.

  6. Delete below files:
    <SASHome>/SASEnvironmentManager/2.5/installer/lib/commons-collections-3.2.1.jar
    <SASHome>/SASEnvironmentManagerAgent/2.5/installer/lib/commons-collections-3.2.1.jar
    <SASConfig>/LevX/Web/SASEnvironmentManager/agent-5.8.0-EE/bundles/agent-5.8.0/pdk/lib/commons-collections-3.2.1.jar
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib/commons-collections-3.2.jar
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib/commons-collections-2.1.1.jar

  7. Copy commons-collections.jar from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
    to
    <SASHome>/SASEnvironmentManager/2.5/installer/lib directory and
    <SASHome>/SASEnvironmentManagerAgent/2.5/installer/lib directory and
    <SASConfig>/LevX/Web/SASEnvironmentManager/agent-5.8.0-EE/bundles/agent-5.8.0/pdk/lib directory and
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib directory and
    <SASConfig>/LevX/Web/Scripts/SASEnvironmentManagerAgent/lib directory and
    <SASConfig>/LevX/Web/Scripts/SASEnvironmentManager/lib directory

  8. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/tomcatserverconfig/WEB-INF/lib directory
    1. Delete file: org.springframework.web-3.0.4.RELEASE.jar

    2. Copy file org.springframework.web-3.0.7.jar from <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
      to
      the current directory.

  9. Copy struts-core-1.3.10.jar file from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
    to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/lib directory.

  10. Windows platform:
    Unzip tomcat-6.0.44.B.RELEASE.zip
    in the <SASHome>/SASEnvironmentManager/2.5/hotfix/ into sub-directory tomcat-6.0.44.B.RELEASE.

    Unix Like platform:
    Untar and unzip tomcat-6.0.44.B.RELEASE.tar.gz
    in the <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory using the following commands:

    > gunzip tomcat-6.0.44.B.RELEASE.tar.gz
    > tar -xvf tomcat-6.0.44.B.RELEASE.tar

  11. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/tomcat-6.0.35.A.RELEASE directory

  12. Delete all files and directories in this location

  13. Copy all files and subfolders from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/tomcat-6.0.44.B.RELEASE directory
    to the
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/tomcat-6.0.35.A.RELEASE directory

  14. Navigate to <SASHome>/SASEnvironmentManager/2.5/hotfix directory

  15. Delete the following files, if they exist:
    activemq-broker-5.12.0.jar
    activemq-client-5.12.0.jar
    activemq-jms-pool-5.12.0.jar
    activemq-kahadb-store-5.12.0.jar
    activemq-openwire-legacy-5.12.0.jar
    activemq-pool-5.12.0.jar
    activemq-spring-5.12.0.jar
    commons-pool2-2.3.jar

  16. Navigate to <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/lib directory

  17. Delete the following files if they exist:
    activemq-broker-5.12.0.jar
    activemq-client-5.12.0.jar
    activemq-jms-pool-5.12.0.jar
    activemq-kahadb-store-5.12.0.jar
    activemq-openwire-legacy-5.12.0.jar
    activemq-pool-5.12.0.jar
    activemq-spring-5.12.0.jar
    commons-pool2-2.3.jar
    activeio-core-3.1.2.jar
    activemq-all-5.3.0.jar
    activemq-core-5.3.0.jar
    activemq-pool-5.3.0.jar
    activemq-protobuf-1.0.jar

  18. Copy files below from the <SASHome>/SASEnvironmentManager/2.5/hotfix directory to the current directory:
    activeio-core-3.1.4.jar
    activemq-broker-5.12.2.jar
    activemq-client-5.12.2.jar
    activemq-jms-pool-5.12.2.jar
    activemq-kahadb-store-5.12.2.jar
    activemq-openwire-legacy-5.12.2.jar
    activemq-pool-5.12.2.jar
    activemq-protobuf-1.1.jar
    activemq-spring-5.12.2.jar
    commons-pool2-2.4.2.jar
    hawtbuf-1.11.jar
    hawtbuf-proto-1.11.jar

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

  20. Delete the following files if they exist:
    activemq-broker-5.12.0.jar
    activemq-client-5.12.0.jar
    activemq-jms-pool-5.12.0.jar
    activemq-kahadb-store-5.12.0.jar
    activemq-openwire-legacy-5.12.0.jar
    activemq-pool-5.12.0.jar
    activemq-protobuf-1.1.jar
    activemq-spring-5.12.0.jar
    commons-pool2-3.2.jar
    activeio-core-3.1.2.jar
    activemq-all-5.3.0.jar
    activemq-core-5.3.0.jar
    activemq-pool-5.3.0.jar
    activemq-protobuf-1.0.jar

  21. Copy files below from <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory to the current directory:
    activeio-core-3.1.4.jar
    activemq-broker-5.12.2.jar
    activemq-client-5.12.2.jar
    activemq-jms-pool-5.12.2.jar
    activemq-kahadb-store-5.12.2.jar
    activemq-openwire-legacy-5.12.2.jar
    activemq-pool-5.12.2.jar
    activemq-protobuf-1.1.jar
    activemq-spring-5.12.2.jar
    commons-pool2-2.4.2.jar
    hawtbuf-1.11.jar
    hawtbuf-proto-1.11.jar

  22. Copy activemq-plugin.jar from
    <SASHome>/SASEnvironmentManager/2.5/hotfix/ directory
    to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/webapps/ROOT/WEB-INF/hq-plugins directory.

  23. Copy hqee-bootstrap-5.8.0.jar from <SASHome>/SASEnvironmentManager/2.5/hotfix to
    <SASConfig>/LevX/Web/SASEnvironmentManager/server-5.8.0-EE/lib

    replacing the original hqee-bootstrap-5.8.0.jar.

Important Note: For the steps below, you will need to restart all servers before these steps can be completed.
If you have not already applied hot fix W43002, please do so before you restart all servers.

  1. Start EV server and EV agent.

  2. Logon the SAS Environment Manager and perform the following steps
    1. Select the 'Manage' page.
    2. Select the 'Plug-in Manager' page.
    3. Open the 'plugin upload' dialog by click the 'Add/Update Plug-in(s)' button.
    4. Select the plugin file postgresql-plugin.jar under the directory '<SASHome>/SASEnvironmentManager/2.5/hotfix/' then click 'Upload' button.
    5. Wait for the agent syncronize progress finish.


V75001  updates  SAS Web Server 9.42

If you have previously installed hot fix V75001, the entire section below can be skipped:

  1. Edit <SASHOME>/SASWebServer/9.4/httpd-2.2.31.0-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:

    > rm httpd-2.2
    > ln -s httpd-2.2.31.0-64 httpd-2.2

  3. If you configure the Web Server to use the secure sockets HTTPS protocol then the SAS Environment Manager plugin will not be able to monitor the Web Server. In that case the following steps will not apply and they 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 should look like: xxxxxxxx Pivotal Web Server 5.x WebServer.

    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 V77006 on HP-UX IPF.


Copyright 2015 SAS Institute Inc. All Rights Reserved.