Installation instructions for hot fix H46032 on Windows for x64

Installation Instructions for Hot Fix H46032

Windows for x64

You MUST apply H46016 before applying this hot fix.

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

H47026 updates SAS Financial Management Add-in for Microsoft Excel 5.3
I53024 updates SAS Financial Management Add-in for Microsoft Excel 5.31
H99021 updates SAS Financial Management JAR Files 5.3_M1
I04023 updates SAS Financial Management Mid-Tier 5.3_M1
I01021 updates SAS Financial Management Studio 5.3_M1
I02021 updates SAS Financial Management Studio 5.3_M2
I11023 updates SAS Financial Management Web Data Entry 5.3_M1
I05015 updates SAS OLAP Data and Compute Server Mid-Tier for Solutions 5.3_M1
I07014 updates SAS Solutions Services Data Server JAR Files 5.3_M1
I09014 updates SAS Solutions Services Extensions for SAS Strategy Management 5.3_M1
I08014 updates SAS Solutions Services Logical Types 5.3_M1
I06014 updates SAS Solutions Services Mid-Tier 5.3_M1

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

Do NOT extract the contents of H46032pt.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 H46032 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.3_M1 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 H46032pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.3: 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

Data tier Update

From a command window, log into MySQL and connect to the sassdm database.

Mysql -usqladmin -pOrion123 -P3306 -h hostname sassdm

Modify the command to contain the correct password, port, and hostname used in your environment.
After connecting to the sassdm database, enter the following command:

ALTER TABLE `sassdm`.`sas_dim_type_member_selector` ADD INDEX
`Rule_ID`(`CELL_PROTECTION_RULE_ID`);

Web application Update

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

I04023 updates SAS Financial Management Mid-Tier 5.3_M1
I11023 updates SAS Financial Management Web Data Entry 5.3_M1
I05015 updates SAS OLAP Data and Compute Server Mid-Tier for Solutions 5.3_M1
I06014 updates SAS Solutions Services Mid-Tier 5.3_M1

Re-build Web Application

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

Invoke the SAS Deployment Manager 9.3
From the SASDeploymentManager directory launch sasdm.exe.
SAS Deployment Manager is installed in the following default location:
<SASHOME>\SASDeploymentManager\9.3
Select a language in the Choose Language box
Select Rebuild Web Applications
Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
Specify Connection Information, including the sasadm User ID and Password
Select the mid-tier applications listed above as the Web Applications to Rebuild
Verify the information on the Summary screen and select Start
Select Finish when the deployment is complete

This process will update the ears in

<SASCONFIGDIR>\Web\Staging

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

<SASCONFIGDIR>\Web\Staging\Backup

Re-deploy Web Application

For detailed instructions on how to re-deploy Web Applications, refer to the Intelligence Platform Midtier Administration Guide.

Remove the cache for the updated ear files under the web application servers that correspond to the ears that were rebuilt.
For example, for WebLogic, delete the folder _WL_user for servers 3, 4, and 5.
<drive>:\SAS\Config\Lev1\Web\SASDomain\servers\SASServer4\tmp\_WL_user
(delete entire folder for each ear file)

For JBoss, delete the contents of the tmp folder for servers 3 and 5 (assuming you have combined servers 3 and 4 to improve performance.
For additional information on combining servers 3 and 4, contact SAS Tech Support
Re-deploy the web application using WebLogic Admin console.
To deploy this application it is important to deploy from <SASCONFIGDIR>\Web\Staging.
Verify that in the settings overview tab for the Financial Management Mid-Tier and Financial Management Web Data Entry ear files to be re-deployed that the deployment order is set to 110.
Verify that in the settings overview tab for the Solutions Services Mid-Tier and OLAP Data and Compute Server Mid-Tier for Solutions ear files to be re-deployed that the deployment order is set to 100.
Re-deploy WebSphere Application.
Re-deploy the web application using WebSphere Admin console by using the Update function.
To deploy this application it is important to deploy from /Web/Staging.
Verify that the Deploy WebServices checkbox is selected
Re-deploy JBoss Application.
Re-deploy the web application by updating the filesystem under \server\SASServer3\deploy_sas.
To deploy this application it is important to deploy from /Web/Staging/exploded.
Stop the JBoss application servers, SASServer3 and SASServer 5 (SASServer4 should have previously been reconfigured into SASServer3).
For additional information on combining servers 3 and 4, contact SAS Tech Support
Remove the current ears under the folder above and copy the application ears updated into the proper directory.

Re-start the Web Application Servers

Shut down the Web Application servers
Restart SAS Remote Services.
Restart the Web Application servers.