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

Do NOT extract the contents of K90004pt.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 K90004 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 (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.

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

Navigate to the directory where SAS Versioned Jar repository is configured. By default, this directory is &ltSASHOME>/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 &ltSASHome>/SASCustomerIntelligenceStudio/6.1/Config/hfscripts directory launch ‘copy_files.sh’ via a command prompt, supplying the path of the Config directory

For example: copy_files.sh /SAS/Config/Lev1

After running the copy_files.sh file please review the cicstudio_hf.log for errors. The log can be found in the &ltCONFIGDIR>/Lev1/Logs directory.

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

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 52324 In SAS® Digital Marketing, the range of ports opened between the bess.war server and
the SAS® Digital Marketing server needs to be controlledhttp://support.sas.com/kb/52324

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 &ltSASHOME>/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 &ltSASHOME>/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 &ltjar 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.

This process will update the Digital Marketing Web Studio and Web Reporting Infrastructure ear in
<CONFIGDIR>\Lev1\Web\Staging. Two ear files are created: “bess.ear” and “sas.DigitalMarketingWebStudio6.1.ear”.
Each of these must be redeployed into their respective application servers following this step. In a double bess.war deployment, both internal and external application servers must also be updated.
A backup of the original ear file will be placed in the Backup directory.