Installation Instructions for Hot Fix H8P027

64-bit Enabled AIX


Hot fix H8P027 addresses the issue(s) in SAS Marketing Automation 6.6 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/H8P.html#H8P027


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

H8B026  updates  SAS Customer Intelligence Common Logical Types 6.6
H8F026  updates  SAS Customer Intelligence Core Mid-Tier 6.6
H8H026  updates  SAS Customer Intelligence Logical Types 6.6
H9I007  updates  SAS Customer Intelligence Processes 6.6
H8D026  updates  SAS Customer Intelligence Reporting Mid-Tier 6.6
H8C026  updates  SAS Customer Intelligence Studio 6.6
H8I026  updates  SAS Customer Intelligence Utilities 6.6
H8J026  updates  SAS Marketing Automation Extensions for SAS Customer Intelligence Studio 6.6
H8E026  updates  SAS Marketing Automation Integration Utilities 6.6
H8G026  updates  SAS Marketing Automation Launcher 6.6

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

Do NOT extract the contents of H8P027pt.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. CONFIGURATION: No automatic configuration scripting is included 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.

  6. The AIX file cache must be cleared to avoid encountering locked files while applying the hotfix. To clear the cache, run the /usr/sbin/slibclean command using the root user ID.


INSTALLATION

If your installation has any combination of SAS Marketing Automation (MA), and SAS Marketing Optimization (MO), the Apply Hot Fixes, Rebuild Web Applications, and Deploy Web Applications steps can be combined and performed for MA and MO in one iteration per step. This can be performed as follows:

Hot Fix H8P027 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 Automation 6.6 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 H8P027pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.


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

SAS Security Updates
  1. The following instruction applies only for environments running SAS 9.4 M7 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.

  2. On all tiers in the environment, navigate to the directory where SAS Versioned Jar Repository is configured (by default, this directory is <SASHOME>/SASVersionedJarRepository/eclipse). If present, delete the com.sas.app.launcher.cacheFile file.

  3. If this hotfix was installed automatically by SAS Deployment Wizard during the initial software installation, or as part of your SAS 9.4M6 Update In Place, (as opposed to installing SAS Customer Intelligence hot fixes on an already configured system using SAS Deployment Manager), this step can be skipped. On the middle tier machine where the SAS Customer Intelligence Core Mid-Tier web application resides, navigate to the <SASConfig>/Web/Temp directory.
    Delete the sas.analytics.crm.webservices.integration folder.

Web Application Update

If this hotfix was installed automatically by SAS Deployment Wizard during the initial software installation, or as part of your SAS 9.4M6 Update In Place, (as opposed to installing SAS Customer Intelligence hot fixes on an already configured system using SAS Deployment Manager), these steps, Web Application Update, can be skipped.

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

(Note: If you are also installing other SAS Customer Intelligence hot fixes, along with this hot fix, you can select those web applications to rebuild at the same time. IMPORTANT: Refer to the hot fix installation instructions for each of these other SAS Customer Intelligence solutions and ensure you have followed all of the preceding instructions needed, before re-building and re-deploying the additional web applications that need to be re-built and re-deployed).

Rebuild the following Web Applications:

Redeploy the following Web Applications:

For more information about how to rebuild and redeploy Web Applications, see the SAS® 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications on Rebuilding the SAS Web Applications and Redeploying the SAS Web Applications.

Design Repository Update
In order to get the new code, SAS Note 66580 and SAS Note 67779, into the Design Repository you have to do the following:
  1. In SMC, delete the _SAS_RHUPDATE_DS2_ACTIVITY activity from SAS Folders\System\Applications\SAS Decision Services\Decision Services6.4\SASDSDesignRepository.
  2. In SMC, delete the _SAS_CHUPDATE_DS2_ACTIVITY activity from SAS Folders\System\Applications\SAS Decision Services\Decision Services6.4\SASDSDesignRepository.
  3. Restart SAS Server 6.

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

H8B026  updates  SAS Customer Intelligence Common Logical Types 6.6
H8F026  updates  SAS Customer Intelligence Core Mid-Tier 6.6
H8H026  updates  SAS Customer Intelligence Logical Types 6.6
H9I007  updates  SAS Customer Intelligence Processes 6.6
H8D026  updates  SAS Customer Intelligence Reporting Mid-Tier 6.6
H8C026  updates  SAS Customer Intelligence Studio 6.6
H8I026  updates  SAS Customer Intelligence Utilities 6.6
H8J026  updates  SAS Marketing Automation Extensions for SAS Customer Intelligence Studio 6.6
H8E026  updates  SAS Marketing Automation Integration Utilities 6.6
H8G026  updates  SAS Marketing Automation Launcher 6.6


H8B026  updates  SAS Customer Intelligence Common Logical Types 6.6

NONE


H8F026  updates  SAS Customer Intelligence Core Mid-Tier 6.6

NONE


H8H026  updates  SAS Customer Intelligence Logical Types 6.6

NONE


H9I007  updates  SAS Customer Intelligence Processes 6.6

NONE


H8D026  updates  SAS Customer Intelligence Reporting Mid-Tier 6.6

NONE


H8C026  updates  SAS Customer Intelligence Studio 6.6

NONE


H8I026  updates  SAS Customer Intelligence Utilities 6.6

NONE


H8J026  updates  SAS Marketing Automation Extensions for SAS Customer Intelligence Studio 6.6

NONE


H8E026  updates  SAS Marketing Automation Integration Utilities 6.6

NONE


H8G026  updates  SAS Marketing Automation Launcher 6.6

NONE


This completes the installation of hot fix H8P027 on 64-bit Enabled AIX.


Copyright 2023 SAS Institute Inc. All Rights Reserved.