Installation Instructions for Hot Fix H77004

64-bit Enabled Solaris

Hot fix H77004 addresses the issue(s) in SAS Activity-Based Management 7.2_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/H77.html#H77004

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

H74004  updates  SAS Activity-Based Costing 7.2_M1
H75004  updates  SAS Activity-Based Management Mid-Tier 7.2_M1

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

Do NOT extract the contents of H77004pt.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. If you are using WebSphere as your web application server, you may run into a “Configuration Failure” error while applying the hotfix. Confirm that the deployment manager and node manager are started and then select Retry.

6. If you are configuring SAS Activity-Based Management 7.2 with Java 7, you must use the JDBC jar as recommended by your database vendor. The JDBC recommendation is typically specific to a database version. You may see numerous random errors if the correct version of JDBC jar is not used while running the application.

7. If you are using Java 7 the following option must be defined before running the Re-build Web Application step in the POST-INSTALLATION INSTRUCTIONS section of the hot fix installation documentation.

   JAVA_TOOL_OPTIONS=-Djdk.lang.Process.allowAmbigousCommands=true

   See http://support.sas.com/resources/thirdpartysupport/v93/jres.html for more details about the Oracle supplied workaround.

   An updated sasdm.ini may appear similar to the following after making the modification.

   [properties]
   MASTERPROP=C:\Program Files\SASHome\sassw.config
   
   [default]
   launchercmd=
   launcherargs=-Djdk.lang.Process.allowAmbigousCommands=true -Xmx1024M -jar "C:\Program Files\SASHome\SASDeploymentManager\9.3\products\deploywiz__93610__prt__xx__sp0__1\deploywiz\setup.jar" -startuplocation "C:\Program Files\SASHome\SASDeploymentManager\9.3" -configure -javaoptions "-Djdk.lang.Process.allowAmbigousCommands=true -Xmx1024M"
   

INSTALLATION

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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 H77004pt.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

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

POST-INSTALLATION INSTRUCTIONS

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

H74004  updates  SAS Activity-Based Costing 7.2_M1
H76003  updates  SAS Activity-Based Management Client 7.21
H75004  updates  SAS Activity-Based Management Mid-Tier 7.2_M1

H74004  updates  SAS Activity-Based Costing 7.2_M1

NONE

H76003  updates  SAS Activity-Based Management Client 7.21

Updates to your SAS Activity-Based Management Client machines are also required. Since the clients can only be installed on Windows, you must download H77004 for Windows to your client machines and apply the hot fix per the installation instructions provided.

H75004  updates  SAS Activity-Based Management Mid-Tier 7.2_M1

Updates to the SAS Activity-Based Management Mid-Tier 7.2 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.3

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

<SASHOME>/SASDeploymentManager/9.3

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 Activity-Based Mgmt 7.2 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 Activity-Based Management Mid-Tier 7.2 ear in

<SASCONFIGDIR>/Web/Staging

<SASCONFIGDIR>/Web/Staging/Backup

Re-deploy Web Application

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

Change "Class Loader Order" setting in WebSphere Application Server (WAS)

After re-building and re-deploying the web application the Class Loader Order setting in WebSphere Application Server must be changed to Class loaded with local class loader first (parent last) in order to prevent failures with ABM client connections. To change this setting

1. Open WAS console

2. Browse to "Enterprise Applications > SASActivityBasedManagement7.2 > Manage Modules"

3. The three ABM related WAR files should be displayed

4. Click on the first "war" file

5. In the Configuration Tab, under *Class Loader order: select Classes Loaded with local class loader first (parent last)

6. Perform this step for all other "war" files

7. Select Apply->Review->Sychronize and Save these settings

8. Restart SASServer9.

Execute scripts to correct the SQL queries for Oracle or MySQL

In some cases when trying to delete a SAS Activity-Based Management model, the system can potentially delete more database objects than it should. The issue can occur if SAS Activity-Based Management is running on Oracle or MySQL. This is not an issue if SAS Activity-Based Management is running on SQL Server.

To fix this issue, the MT_DELETE_MODEL SQL procedure needs to be updated by running database-specific script.

1. Open a database tool that allows you to run scripts.

2. Connect to SAS Activity-Based Management database/schema using a credential that has capabilities to drop/create SQL procedures.

3. Open the database specific SQL script in the tool, i.e.

   <SASHOME>/SASActivityBasedManagementMidTier/7.2/Config/deploy/db/scripts/mysql/MT_DELETE_MODEL.sql <SASHOME>/SASActivityBasedManagementMidTier/7.2/Config/deploy/db/scripts/oracle/MT_DELETE_MODEL.sql

4. Execute the script

PLEASE NOTE: It is important that once the SQL procedure is modified, the procedure itself should never be executed directly from the database tool. Doing so will delete many database objects and a full database restore will be required.

This completes the installation of hot fix H77004 on 64-bit Enabled Solaris.