Installation instructions for hot fix K90014 on 64-bit Enabled AIX

Installation Instructions for Hot Fix K90014

64-bit Enabled AIX

Hot fix K90014 addresses the issue(s) in SAS Digital Marketing 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/K90.html#K90014

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

K67010 updates SAS Customer Intelligence Common Logical Types 6.1_M1
M74001 updates SAS Customer Intelligence Common Public Type Metadata 6.1_M1
M66003 updates SAS Customer Intelligence Common Server 6.1_M1
K68012 updates SAS Customer Intelligence Studio 6.1_M1
K89014 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
K88014 updates SAS Digital Marketing Logical Types 6.1_M1
K85014 updates SAS Digital Marketing Server Components 6.1_M1
K86014 updates SAS Digital Marketing Studio 6.1_M1
K87014 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1

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

Do NOT extract the contents of K90014pt.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 K90014 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 Digital Marketing 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. 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 K90014pt.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 SDM (in upper case) argument.
For example:
copy_files.sh /SAS/Config/Lev1 SDM
After running the copy_files.sh file please review the cicstudio_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.

K67010 updates SAS Customer Intelligence Common Logical Types 6.1_M1
K68012 updates SAS Customer Intelligence Studio 6.1_M1
K89014 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
K88014 updates SAS Digital Marketing Logical Types 6.1_M1
K85014 updates SAS Digital Marketing Server Components 6.1_M1
K86014 updates SAS Digital Marketing Studio 6.1_M1
K87014 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1
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 K90003, you need to review K90003 and above sets of SAS Notes.
Please review the SAS Deployment Registry report (SAS Note 35968) to confirm which was the last hot fix you installed.

K90010

SAS Note 54786 SAS® Digital Marketing does not work with Integrated Windows Authentication (IWA)
http://support.sas.com/kb/54786

K90008

SAS Note 53194 Lines of text disappear within ASP-type broadcasts in SAS® Digital Marketing
http://support.sas.com/kb/53194

K90006

SAS Note 52978 There might be a delay in updates to the SAS® Digital Marketing tables
http://support.sas.com/kb/52978

SAS Note 50612 The SAS® Digital Marketing opt-out table is vulnerable to malicious corruption
http://support.sas.com/kb/50612

SAS Note 50444 SAS® Digital Marketing broadcasts fail to complete, resulting in the system becoming unresponsive and a server reboot being necessary
http://support.sas.com/kb/50444

SAS Note 49036 Enabling an additional debugging option when you have problems sending e-mails or SMS messages in SAS® Digital Marketing
http://support.sas.com/kb/49036

K90004

SAS Note 52324 In SAS® Digital Marketing, the range of ports opened between the bess.war server and the SAS® Digital Marketing server needs to be controlled
http://support.sas.com/kb/52324
Refresh Web-browser Cache
Please refresh your web-browser cache if issues do not seem to be resolved in SAS Customer Intelligence Studio, after you apply this hot fix. For further information, please review SAS Note 60238

K67010 updates SAS Customer Intelligence Common Logical Types 6.1_M1

NONE

K68012 updates SAS Customer Intelligence Studio 6.1_M1

NONE

K89014 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
K87014 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1

Web Application Update

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

In order to successfully rebuild the bess.ear web application the SAS Deployment Manager requires that the configured bess.ear be available in the [CONFIG]/Lev1/Web/Staging directory. If a copy of the bess.ear is not available from this location the embedded passwords will not be rebuilt and the bess.ear will not be able authenticate against the SAS Digital Marketing server. To avoid this issue, if you have not used the default Staging directory, you should place a copy of your configured bess.ear file in this location before continuing.

Step 1: Re-build Web Applications

In order for this step to execute correctly, the Metadata Server must be running, so restart this server if necessary.

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 the following as the Web Applications to Rebuild:

Customer Intelligence Studio
SAS Digital Marketing Web Studio and Web Reporting Infrastructure

(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).

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

Step 2: Re-deploy Web Applications

2.1 Re-deploy the updated ear files listed above (together with any other SAS Customer Intelligence ear files you have re-built, see Note above in 1.6), to the web application servers 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.

K88014 updates SAS Digital Marketing 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.

K85014 updates SAS Digital Marketing Server Components 6.1_M1

NONE

K86014 updates SAS Digital Marketing Studio 6.1_M1

NONE

Each client machine should have the internet browser cache cleared in order to pick up new files that are available in this hot fix. See SAS Note: 59491 for further information.