Installation instructions for hot fix U31006 on Linux for x64

Installation Instructions for Hot Fix U31006

Linux for x64

Hot fix U31006 addresses the issue(s) in SAS Cost and Profitability Management 8.1_M2 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/U31.html#U31006

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

U32004 updates SAS Cost and Profitability Management IOM Server 8.1_M2
U40002 updates SAS Cost and Profitability Management Mid-Tier 8.1_M2
W26001 updates SAS Cost and Profitability Management Client 8.1_M2

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

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

IMPORTANT NOTES

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.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.

INSTALLATION

Hot Fix U31006 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 Cost and Profitability Management 8.1_M2 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 U31006pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

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.

U32004 updates SAS Cost and Profitability Management IOM Server 8.1_M2
W26001 updates SAS Cost and Profitability Management Client 8.1_M2
U40002 updates SAS Cost and Profitability Management Mid-Tier 8.1_M2
Required updates to SAS Cost and Profitability Management Client 8.1_M2

U32004 updates SAS Cost and Profitability Management IOM Server 8.1_M2

NONE

W26001 updates SAS Cost and Profitability Management Client 8.1_M2

NONE

U40002 updates SAS Cost and Profitability Management Mid-Tier 8.1_M2

Updates to the SAS Cost and Profitability Management 8.1_M2 provided in this hot fix require that Web Applications be rebuilt and redeployed. If this component is installed on Unix, follow the steps below to rebuild and redeploy the web application:

Remove com.sas.app.launcher.cacheFile

1. Delete

<SASHOME>/SASVersionedJarRepository/eclipse/com.sas.app.launcher.cacheFile

Re-build Web Application

In order for this step to execute correctly, the Metadata Server must be running.

1. Invoke the SAS Deployment Manager 9.4

From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location:

<SASHOME>/SASDeploymentManager/9.4

2. Select a language in the Choose Language box

3. Select Rebuild Web Applications

4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

5. Specify Connection Information, including the sasadm User ID and Password

6. Select SAS Cost and Profitability Management 8.1 as the Web Application to Rebuild

7. Verify the information on the Summary screen and select Start

8. Select Finish when the deployment is complete

This process will update the SAS Cost and Profitability Management 8.1 ear in

<SASCONFIGDIR>/Web/Staging

A backup of the original ear file will be placed in the directory

<SASCONFIGDIR>/Web/Staging/Backup

Re-deploy Web Application

Re-deploy the web application using the process documented for the initial deployment process.

Required updates to SAS Cost and Profitability Management Client 8.1_M2

In ABM client bin folder, open the configuration file sasabm.exe.config in a text editor and change the value for "ConnectionTimeOut" to “72000”. The result of the change should appear as:

<add key="ConnectionTimeOut" value="720000"/>