Installation instructions for hot fix E88018 on Solaris for x64

Installation Instructions for Hot Fix E88018

Solaris for x64

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

https://tshf.sas.com/techsup/download/hotfix/HF2/E88.html#E88018

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

F41013 updates Marketing Automation Launcher 5.41
E84017 updates SAS Customer Intelligence Core Mid-Tier 5.41
E87015 updates SAS Customer Intelligence Logical Types 5.41
E85013 updates SAS Customer Intelligence Plug-ins for SAS Management Console 5.41
G02012 updates SAS Customer Intelligence Processes 5.41
F69009 updates SAS Customer Intelligence Reporting Mid-Tier 5.41
F38013 updates SAS Customer Intelligence Studio 5.41
E86014 updates SAS Customer Intelligence Utilities 5.41
F40014 updates SAS Customer Intelligence Web Components 5.41
F39013 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, E88018pt.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 E88018pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of E88018pt.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.
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.
If you use SAS Marketing Operations Management (MOM) integrated with SAS Marketing Automation please call SAS Technical Support prior to installing this hotfix. The SAS Marketing Operations Management Integration Web-Services consume a jar file from SAS Marketing Automation, and these jar file need to be synchronized. Without the correct jar file in place for MOM 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 Operations Management hot-fix being made available, but we would recommend waiting to install both hot-fixes together.

INSTALLATION

Hot Fix E88018 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. 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 E88018pt.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.

F41013 updates Marketing Automation Launcher 5.41
E84017 updates SAS Customer Intelligence Core Mid-Tier 5.41
E87015 updates SAS Customer Intelligence Logical Types 5.41
E85013 updates SAS Customer Intelligence Plug-ins for SAS Management Console 5.41
G02012 updates SAS Customer Intelligence Processes 5.41
F69009 updates SAS Customer Intelligence Reporting Mid-Tier 5.41
F38013 updates SAS Customer Intelligence Studio 5.41
E86014 updates SAS Customer Intelligence Utilities 5.41
F40014 updates SAS Customer Intelligence Web Components 5.41
F39013 updates SAS Marketing Automation Integration Utilities for MA 5.41

Review SAS Notes
After the installation of this hot fix and product post-installation instructions, please review the following SAS Notes for details on changes that are required to take advantage of the hot fixes. The SAS Notes below are organized by the hot fix they were introduced in. Knowing the last hot fix you installed will help you determine which sets of SAS Notes, below, need to be reviewed. For example, if your last hot fix was E88005, you need to review both E88007 and E88009 sets of SAS Notes.

Please review the SAS Deployment Registry report (SAS Note 35968) to confirm which was the last hot fix you installed.

E88009

SAS Note 51058 A parse error occurs in the JBoss 5.1 web application server log
http://support.sas.com/kb/51058

SAS Note 50762 Scheduling recurrent campaigns in SAS Customer Intelligence Studio do not exceed 106 occurrences
http://support.sas.com/kb/50762

SAS Note 50616 In SAS Marketing Automation, a change in a campaign schedule results in the Campaign Occurrence numbers being reset and the history overwritten
http://support.sas.com/kb/50616

SAS Note 50515 SAS Customer Intelligence campaigns that run for a long period of time fail to finish
http://support.sas.com/kb/50515

SAS Note 49673 Generating MAMetadata fails when the underlying data is held in SAS Scalable Performance Data Server
http://support.sas.com/kb/49673

E88007

SAS Note 49346 The SAS Real-Time Decision Manager arbitration process might log an "RTDMTimeoutException" error message and fail to finish
http://support.sas.com/kb/49346

E88005

SAS Note 48567 SAS Real-Time Decision Manager arbitration returns "Unable to execute query" when it receives more than 32KB of treatment data
http://support.sas.com/kb/48567

E88003

SAS Note 46976 SAS Customer Intelligence campaigns occasionally become unresponsive when executing
http://support.sas.com/kb/46976

SAS Note 46999 An error might occur when you open Microsoft Excel files that have been created from a SAS Marketing Automation Export node or Communication node
http://support.sas.com/kb/46999

E88002

SAS Note 45809 SAS Marketing Automation returns "ERROR: Teradata row not delivered (trget): Transaction ABORTed due to deadlock" when you publish a campaign
http://support.sas.com/kb/45809

SAS Note 43410 When SAS Marketing Automation has a large number of concurrent users, some of its processes might fail to respond, and fail to complete
http://support.sas.com/kb/43410

E88001

SAS Note 43630 The campaign-group schedule date overwrites a campaign schedule date
http://support.sas.com/kb/43630

F41013 updates Marketing Automation Launcher 5.41

NONE

E84017 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 E84017 only contains a new SASCustIntellCore5.4.ear file which needs to be re-deployed typically for /server/SASServer6

E87015 updates SAS Customer Intelligence Logical Types 5.41

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 <SASHOME>/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.

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

NONE

G02012 updates SAS Customer Intelligence Processes 5.41

Copy SAS Changes to <CONFIGDIR>

Backup the original file

Windows: <CONFIGDIR>\Lev1\Applications\SASCustomerIntelligence5.4\Data\MAMisc\mapublish.map
Unix: <CONFIGDIR>/Lev1/Applications/SASCustomerIntelligence5.4/Data/MAMisc/mapublish.map
Copy file from

Windows: <SASHOME>\SASFoundation\9.3\ma\sasmisc\mapublish.map
Unix: <SASHOME>/SASFoundation/9.3/misc/ma/mapublish.map
to
Windows: <CONFIGDIR>\Lev1\Applications\SASCustomerIntelligence5.4\Data\MAMisc\mapublish.map
Unix: <CONFIGDIR>/Lev1/Applications/SASCustomerIntelligence5.4/Data/MAMisc/mapublish.map

F69009 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 F69009 only contains a new SASCustIntellReporting5.4.ear file which needs to be re-deployed typically for /server/SASServer6

F38013 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.41 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.41/

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

JBoss: <SASHOME>/SASCustomerIntelligenceStudio/5.41/campaignsdo_jboss_fs/default/gen
WebLogic: <SASHOME>/SASCustomerIntelligenceStudio/5.41/campaignsdo_weblogic_fs/default/gen
WebSphere: <SASHOME>/SASCustomerIntelligenceStudio/5.41/campaignsdo_websphere_fs/default/gen

Copy the file "picklist" from the appropriate folder back to:

<SASHOME>/SASCustomerIntelligenceStudio/5.41

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

E86014 updates SAS Customer Intelligence Utilities 5.41

NONE

F40014 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 F40014 only contains a new sasCustIntellWeb5.4.ear file which needs to be re-deployed typically for /server/SASServer6

F39013 updates SAS Marketing Automation Integration Utilities for MA 5.41

NONE