Installation instructions for hot fix K84006 on HP-UX IPF

Installation Instructions for Hot Fix K84006

HP-UX IPF

Hot fix K84006 addresses the issue(s) in SAS Marketing Optimization 6.1_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/K84.html#K84006

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

K67005 updates SAS Customer Intelligence Common Logical Types 6.1_M1
M74001 updates SAS Customer Intelligence Common Public Type Metadata 6.1_M1
M66001 updates SAS Customer Intelligence Common Server 6.1_M1
K68006 updates SAS Customer Intelligence Studio 6.1_M1
K82006 updates SAS Marketing Optimization Extensions for SAS Customer Intelligence Studio 6.1_M1
K83005 updates SAS Marketing Optimization Launcher 6.1_M1
K80005 updates SAS Marketing Optimization Logical Types 6.1_M1
K81006 updates SAS Marketing Optimization Mid-Tier 6.1_M1
M68001 updates SAS Marketing Optimization Public Type Metadata 6.1_M1
K97004 updates SAS Marketing Optimization Server 6.1_M1
K98002 updates SAS Threaded Kernel Extensions for Marketing Optimization 6.1

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

Do NOT extract the contents of K84006pt.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 K84006 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 Marketing Optimization 6.1_M1 require updating on the machine. See SAS Note 44810 for more details.

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

Verify that your X server is running and is available.
Navigate to the directory where SAS Versioned Jar repository is configured. By default, this directory is <SASHOME>/SASVersionedJarRepository/eclipse
Delete the file: com.sas.app.launcher.cacheFile
copy_files.sh must be run on the mid-tier server prior to rebuilding any Web Applications.
From the <SASHome>/SASCustomerIntelligenceStudio/6.1/Config/hfscripts directory launch ‘copy_files.sh’ supplying the path of the Config directory and the MO (in upper case) argument.
For example:
copy_files.sh /SAS/Config/Lev1 MO
After running the copy_files.sh file please review the cictudio_hf.log for errors. The log can be found in the <CONFIGDIR>/Lev1/Logs directory.
For each product installed, click the link to be redirected to post-installation instructions.

K67005 updates SAS Customer Intelligence Common Logical Types 6.1_M1
K68006 updates SAS Customer Intelligence Studio 6.1_M1
K82006 updates SAS Marketing Optimization Extensions for SAS Customer Intelligence Studio 6.1_M1
K83005 updates SAS Marketing Optimization Launcher 6.1_M1
K80005 updates SAS Marketing Optimization Logical Types 6.1_M1
K81006 updates SAS Marketing Optimization Mid-Tier 6.1_M1
K97004 updates SAS Marketing Optimization Server 6.1_M1
K98002 updates SAS Threaded Kernel Extensions for Marketing Optimization 6.1

K67005 updates SAS Customer Intelligence Common Logical Types 6.1_M1

NONE

K68006 updates SAS Customer Intelligence Studio 6.1_M1

NONE

K82006 updates SAS Marketing Optimization Extensions for SAS Customer Intelligence Studio 6.1_M1

Web Application Update

This hot fix requires steps that will update the web application deployed to your application server.

Step 1: Re-build Web Applications

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. The default installation path for the SAS Deployment Manager is

<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 Customer Intelligence Studio 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 Customer Intelligence Studio ear in <CONFIGDIR>\Lev1\Web\Staging.
A backup of the original ear file will be placed in the Backup directory.

Step 2: Re-deploy Web Applications

2.1 Re-deploy the updated ear listed above to the web application server you are using based on the instructions appropriate for your web application server. See SAS 9.3 Intelligence Platform, Middle-Tier Administration Guide, Chapter 7, Administering SAS Web Applications, for more details.

K83005 updates SAS Marketing Optimization Launcher 6.1_M1

NONE

K80005 updates SAS Marketing Optimization Logical Types 6.1_M1

You must reconfigure and restart SAS Remote Services SPECIFICALLY through the following steps so that the changes in SAS Customer Intelligence are surfaced. These steps ensure proper picklist regeneration for the product.

Verify that your X server is running and is available.
Navigate to the directory where SAS Versioned Jar repository is configured. By default, this directory is <SASHOME>/SASVersionedJarRepository/eclipse
Delete the file: com.sas.app.launcher.cacheFile
Navigate to the directory where SAS Remote Services is configured. By default, this directory is <CONFIGDIR>/Lev1/Web/Applications/RemoteServices
Note: Review SAS Note 42547 and revert to the backup copy of the RemoteServices.sh script, if applicable. You can switch back to the modified script after completing the hot fix installation.
Type: ./RemoteServices.sh stop
Type: ./RemoteServices.sh start
You may receive warning messages similar to the following:
WARNING: request for HIGHER version of <jar file name> ignored
These warnings are the result of newer platform files being referenced in the hot fix installation and do not compromise the functionality delivered.

K81006 updates SAS Marketing Optimization Mid-Tier 6.1_M1