Installation instructions for hot fix T43022 on Linux for x64

Installation Instructions for Hot Fix T43022

Linux for x64

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

U89002 updates SAS Financial Management 5.5
T44012 updates SAS Financial Management Add-in for Microsoft Excel 5.5
A7P007 updates SAS Financial Management Add-in for Microsoft Excel 5.51
T47017 updates SAS Financial Management Data Tier 5.5
T45017 updates SAS Financial Management JAR Files 5.5
T48017 updates SAS Financial Management Mid-Tier 5.5
T49017 updates SAS Financial Management Query Processor 5.5
T46017 updates SAS Financial Management Studio 5.5
T52017 updates SAS Financial Management Web Data Entry 5.5
T50017 updates SAS OLAP Data and Compute Server Mid-Tier for Solutions 5.5
T51017 updates SAS Solutions Services Logical Types 5.5

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

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

INSTALLATION

Hot Fix T43022 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 Financial Management 5.5 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 T43022pt.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.

Security Update

The following instruction applies only for environments running SAS 9.4 M6 or earlier:

SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at https://tshf.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.

POST-INSTALLATION INSTRUCTIONS

Security Update for SAS Financial Management Studio 5.5

The following instruction applies only for environments running SAS 9.4 M6 or earlier:

Web application Update

Updates provided in this hot fix require that the following Web Applications be rebuilt and redeployed.

T48017 updates SAS Financial Management Mid-Tier 5.5
T52017 updates SAS Financial Management Web Data Entry 5.5
T50017 updates SAS OLAP Data and Compute Server Mid-Tier for Solutions 5.5

Stop SASServer3, SASServer4, and SASServer5 if they are currently running.

Delete the contents of the following directories:

<SAS-Configuration-Directory>\Web\WebAppServer\SASServer3_1\odcs
<SAS-Configuration-Directory>\Web\WebAppServer\SASServer4_1\odcsReadOnly

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 the mid-tier applications listed above as the Web Applications 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 ears in

<SASCONFIGDIR>/Web/Staging

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

<SASCONFIGDIR>/Web/Staging/Backup

9. Exit the SAS Deployment Manager 9.4

Re-deploy Web Application

1. Restart all SAS sessions, daemons, spawners and servers.

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

3. Select a language in the Choose Language box

4. Select Deploy Web Applications

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

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

7. Check the Allow the application server to stop checkbox

8. Select mid-tier applications listed above as the Web Application to Deploy

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

10. Select Finish and exit the SAS Deployment Manager when the deployment is complete