Installation instructions for hot fix T66001 on 64-bit Enabled AIX

Installation Instructions for Hot Fix T66001

64-bit Enabled AIX

Hot fix T66001 addresses the issue(s) in SAS Enterprise Case Management 3.2_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/T66.html#T66001

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

K35007 updates SAS Enterprise Case Management Mid-Tier 3.2_M1
T65001 updates SAS Enterprise Case Management Server 3.2_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, T66001pt.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 T66001pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of T66001pt.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 T66001 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 Enterprise Case Management 3.2_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 T66001pt.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

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

K35007 updates SAS Enterprise Case Management Mid-Tier 3.2_M1
T65001 updates SAS Enterprise Case Management Server 3.2_M1

K35007 updates SAS Enterprise Case Management Mid-Tier 3.2_M1

Re-build and Re-deploy Web Application

This hot fix requires that the WebApp be rebuilt and redeployed. Use the following steps to perform this post-installation task:

Step 1: Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
1.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

1.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select Enterprise Case Management 3.2 as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
This process will update the Enterprise Case Management MidTier 3.2 ear in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear file will be placed in the directory below:

<SASCONFIGDIR>/Web/Staging/Backup

Step 2: Re-deploy Web Applications
Re-deploy the web applications based on the instructions for the web application server you are using.

You can turn on X-Frame-Options for ECM by adding a new property to the ECM Application Object in SAS metadata.

1. Open SAS Metadata Console and connect to the metadata server.
2. Click the Plug-ins tab on the left.
3. Navigate to Application Management -> Configuration Manager -> SAS Application Infrastructure -> Ent Case Mgmt Mid-Tier 3.2_M1.
4. Select Ent Case Mgmt Mid-Tier 3.2_M1 and use the right mouse button to open the Properties popup.
5. Click on the Advanced tab.
6. Click the Add button.
7. Set Property Name to ECM.XFrame.Option
8. Set Property value to either NONE or SAMEORIGIN.
9. Click OK to close the new property dialog and then OK to close the Ent Case Mgmt 3.2_M1 Properties dialog.
10. Finally, re-start the ECM app server – usually SASServer8.

T65001 updates SAS Enterprise Case Management Server 3.2_M1

NONE