Installation Instructions for Hot Fix C18006

Solaris for x64


Hot fix C18006 addresses the issue(s) in SAS Marketing Automation 5.3_M3 on Solaris for x64 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/C18.html#C18006


This hot fix contains updates to the following software components:

Marketing Automation Launcher 5.3_M3
SAS Customer Intelligence Logical Types 5.3_M3 or SAS Marketing Automation Logical Types
SAS Customer Intelligence Core Mid-Tier 5.3_M3
SAS Customer Intelligence Plug-ins for SAS Management Console 5.3_M3
SAS Customer Intelligence Processes 5.3_M2
SAS Customer Intelligence Studio 5.3_M3
SAS Customer Intelligence Utilities 5.3_M3
SAS Customer Intelligence Web Components 5.3_M3
SAS Marketing Automation Integration Utilities for MA 5.3_M3
SAS Customer Intelligence Reporting Mid-Tier

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 software components and release numbers should match the list of software components updated by the individual hot fix installers.


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. After application of this SAS Marketing Automation hot fix, you may receive the following type of warning message when you log on to SAS Management Console:
    The following plug-ins attempted to load versions of jars that are not allowed in the framework.
    -emasmc
    Click OK to remove the error message and proceed. The error message is indicating a difference in the version of the jar files on the system, but this does not cause any problems.
    You should apply the latest version of the SAS Management Console hot fix to resolve this issue.

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

  7. If you use SAS Marketing Automation integrated with SAS Digital Marketing and you use JBOSS as your Web Application Server, after the application of this hot-fix, please follow the additional instructions detailed in SAS Note 39481 "RemoteException occurred in server thread" error occurs when choosing a Recipient List Type of CI Export Definition in SASŪ Digital Marketing Studio. Please contact Technical Support if you require further information.


INSTALLATION


The installer downloaded is C18006sx.bin. Copy C18006sx.bin to each Solaris for x64 machine on which SAS Marketing Automation 5.3_M3 components are installed.

To install the hot fix, on each machine:

1. Verify that the installation binary has execute permission. If it does not, use the chmod command to make it executable.

$> chmod 755 C18006sx.bin
2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:0
3. Execute C18006sx.bin
<path_to_downloaded_file>/C18006sx.bin
    For example:
./C18006sx.bin

This will initiate the installation wizard, which will guide you through the hot fix installation process. During the installation you will be prompted for the SASHOME location to be updated. You should provide the path to the top level SAS directory where the deploymntreg directory exists.

The installation process will determine which components of SAS Marketing Automation 5.3_M3 are installed on the machine, and apply the appropriate updates.

If components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.


See the Maintenance Installation Tool (MIT) documentation for more details on the installation of hot fixes.


This completes the installation of C18006. Please perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.


POST-INSTALLATION INSTRUCTIONS

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

Marketing Automation Launcher 5.3_M3
SAS Customer Intelligence Logical Types 5.3_M3
SAS Customer Intelligence Core Mid-Tier 5.3_M3
SAS Customer Intelligence Plug-ins for SAS Management Console 5.3_M3
SAS Customer Intelligence Processes 5.3_M2
SAS Customer Intelligence Studio 5.3_M3
SAS Customer Intelligence Utilities 5.3_M3
SAS Customer Intelligence Web Components 5.3_M3
SAS Marketing Automation Integration Utilities for MA 5.3_M3
SAS Customer Intelligence Reporting Mid-Tier 5.3_M3


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

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

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

SAS Note 40093 A Split node returns zero counts when you use values from a data item that is either of type DATE or of type TIMESTAMP
http://support.sas.com/kb/40093

Marketing Automation Launcher 5.3_M3

NONE


SAS Customer Intelligence Logical Types 5.3_M3

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



SAS Customer Intelligence Core Mid-Tier 5.3_M3

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

From the SASDeploymentManager directory launch config.sh. The default installation path for the SAS Deployment Manager is

SASHOME/SASDeploymentManager/9.2

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 5.3 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 web applications based on the instructions in the SAS Web Application Administration Guide. Note: The hot fix C18006 only contains a new SASCustIntellCore5.3.ear file which needs to be re-deployed typically for /server/SASServer6


SAS Customer Intelligence Plug-ins for SAS Management Console 5.3_M3

NONE


SAS Customer Intelligence Processes 5.3_M2

NONE


SAS Customer Intelligence Studio 5.3_M3

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

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

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

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


SAS Customer Intelligence Utilities 5.3_M3

NONE


SAS Customer Intelligence Web Components 5.3_M3

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

From the SASDeploymentManager directory launch config.sh. The default installation path for the SAS Deployment Manager is

SASHOME/SASDeploymentManager/9.2

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 5.3 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 Web 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 web applications based on the instructions in the SAS Web Application Administration Guide. Note: The hot fix C28006 only contains a new sasCustIntellWeb5.3.ear file which needs to be re-deployed typically for /server/SASServer6


SAS Marketing Automation Integration Utilities for MA 5.3_M3

NONE


SAS Customer Intelligence Reporting Mid-Tier 5.3_M3

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

From the SASDeploymentManager directory launch config.sh. The default installation path for the SAS Deployment Manager is

SASHOME/SASDeploymentManager/9.2

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 5.3_M3 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 Reporting 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 web applications based on the instructions in the SAS Web Application Administration Guide. Note: The hot fix C28006 only contains a new sasCustIntellWeb5.3.ear file which needs to be re-deployed typically for /server/SASServer6

This completes the installation of hot fix C18006 on Solaris for x64.