Installation Instructions for Hot Fix E88002

64-bit Enabled AIX


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

http://ftp.sas.com/techsup/download/hotfix/HF2/E88.html#E88002


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

F41002  updates  Marketing Automation Launcher 5.41
E84002  updates  SAS Customer Intelligence Core Mid-Tier 5.41
E87002  updates  SAS Customer Intelligence Logical Types 5.41
E85002  updates  SAS Customer Intelligence Plug-ins for SAS Management Console 5.41
G02001  updates  SAS Customer Intelligence Processes 5.41
F69001  updates  SAS Customer Intelligence Reporting Mid-Tier 5.41
F38002  updates  SAS Customer Intelligence Studio 5.41
E86002  updates  SAS Customer Intelligence Utilities 5.41
F40002  updates  SAS Customer Intelligence Web Components 5.41
F39002  updates  SAS Marketing Automation Integration Utilities for MA 5.41

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

Do NOT extract the contents of E88002pt.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 use SAS Marketing Automation integrated with SAS Marketing Optimization, you should apply both the Marketing Automation and corresponding Marketing Optimization hot-fix to your system, at the same time. This is needed as Marketing Optimization consumes a jar file from Marketing Automation, and these jar files need to synchronized. Without the correct jar file in place for Marketing Optimization, communication between the two products might not function correctly. You might receive serialization errors due to the API signature being out of date. At times, there may be a delay in the corresponding Marketing Optimization hot-fix being made available, but we would recommend waiting to install both hot-fixes together. Contact Technical Support for further details.


INSTALLATION

Hot Fix E88002 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 5.41 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 E88002pt.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide; see the Applying Hot Fixes for Windows and UNIX section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.


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.

F41002  updates  Marketing Automation Launcher 5.41
E84002  updates  SAS Customer Intelligence Core Mid-Tier 5.41
E87002  updates  SAS Customer Intelligence Logical Types 5.41
E85002  updates  SAS Customer Intelligence Plug-ins for SAS Management Console 5.41
G02001  updates  SAS Customer Intelligence Processes 5.41
F69001  updates  SAS Customer Intelligence Reporting Mid-Tier 5.41
F38002  updates  SAS Customer Intelligence Studio 5.41
E86002  updates  SAS Customer Intelligence Utilities 5.41
F40002  updates  SAS Customer Intelligence Web Components 5.41
F39002  updates  SAS Marketing Automation Integration Utilities for MA 5.41


F41002  updates  Marketing Automation Launcher 5.41

NONE


E84002  updates  SAS Customer Intelligence Core Mid-Tier 5.41

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 Core Mid-Tier 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 Core 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.
Note: The hot fix E88002 only contains a new SASCustIntellCore5.4.ear file which needs to be re-deployed typically for /server/SASServer6


E87002  updates  SAS Customer Intelligence Logical Types 5.41

You must reconfigure and restart SAS Remote Services so the changes in SAS Customer Intelligence are surfaced.

  1. Verify that your X server is running and is available.

  2. At the UNIX prompt, navigate to the directory where SAS Versioned Jar repository is configured. Usually, this directory is <SASHOME>/SASVersionedJarRepository/eclipse

  3. Delete the file: com.sas.app.launcher.cacheFile. Because this file is automatically generated, it is not necessary to create a back-up of this file before you delete it.

  4. Next, navigate to the directory where SAS Remote Services is configured. Usually, this directory is <SASHOME>/Lev1/Web/Applications/RemoteServices

  5. If SAS Remote Services is currently running, type: ./RemoteServices.sh stop before you delete it.

  6. To start SAS Remote Services, type ./RemoteServices.sh start.
    Upon Restart of Remote Services, you may receive Warnings 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.



E85002  updates  SAS Customer Intelligence Plug-ins for SAS Management Console 5.41

NONE


G02001  updates  SAS Customer Intelligence Processes 5.41

NONE


F69001  updates  SAS Customer Intelligence Reporting Mid-Tier 5.41

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 SAS Customer Intelligence Reporting Mid-Tier 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 Core 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.
Note: The hot fix F690001 only contains a new SASCustIntellReporting5.4.ear file which needs to be re-deployed typically for /server/SASServer6


F38002  updates  SAS Customer Intelligence Studio 5.41

To complete the installation of SAS Customer Intelligence Studio , you must update the picklist so that it cooresponds to your app-server type.
Upon hot fix installation 3 folders containing unique "picklist" files will be delivered to the 5.4 installation root for SAS Customer Intelligence Studio.

By default the folders: campaignsdo_jboss_fs, campaignsdo_weblogic_fs, and campaignsdo_websphere_fs

will be located in:

[SASHOME]/SASCustomerIntelligenceStudio/5.4/

Choose the folder cooresponding to your app-server type as follows:

JBoss: [SASHOME]/SASCustomerIntelligenceStudio/5.4/campaignsdo_jboss_fs/default/gen
WebLogic: [SASHOME]/SASCustomerIntelligenceStudio/5.4/campaignsdo_weblogic_fs/default/gen
WebSphere: [SASHOME]/SASCustomerIntelligenceStudio/5.4/campaignsdo_websphere_fs/default/gen
Copy the file "picklist" from the appropriate folder back to:
[SASHOME]/SASCustomerIntelligenceStudio/5.4

NOTE: After installing this hot fix it could take up to 5 minutes to start SAS Customer Intelligence Studio for the first time.



E86002  updates  SAS Customer Intelligence Utilities 5.41

NONE


F40002  updates  SAS Customer Intelligence Web Components 5.41

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 Web Components 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 Core 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.
Note: The hot fix F40001 only contains a new sasCustIntellWeb5.4.ear file which needs to be re-deployed typically for /server/SASServer6


F39002  updates  SAS Marketing Automation Integration Utilities for MA 5.41

NONE


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