Hot fix K90009 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#K90009
K90009 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
K67006 updates SAS Customer Intelligence Common Logical Types 6.1_M1
M74001 updates SAS Customer Intelligence Common Public Type Metadata 6.1_M1
M66002 updates SAS Customer Intelligence Common Server 6.1_M1
K68007 updates SAS Customer Intelligence Studio 6.1_M1
K89009 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
K88009 updates SAS Digital Marketing Logical Types 6.1_M1
K85009 updates SAS Digital Marketing Server Components 6.1_M1
K86009 updates SAS Digital Marketing Studio 6.1_M1
K87009 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1
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, K90009pt.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 K90009pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of K90009pt.zip. The hot fix installation process will extract the contents as needed.
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 K90009pt.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.logfor 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.
For example: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.
copy_files.sh /SAS/Config/Lev1 SDM
K67006 updates SAS Customer Intelligence Common Logical Types 6.1_M1
K68007 updates SAS Customer Intelligence Studio 6.1_M1
K89009 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
K88009 updates SAS Digital Marketing Logical Types 6.1_M1
K85009 updates SAS Digital Marketing Server Components 6.1_M1
K86009 updates SAS Digital Marketing Studio 6.1_M1
K87009 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1
Please review the SAS Deployment Registry report (SAS Note 35968) to confirm which was the last hot fix you installed.
- 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
K67006 updates SAS Customer Intelligence Common Logical Types 6.1_M1
NONE
K68007 updates SAS Customer Intelligence Studio 6.1_M1
NONE
K89009 updates SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.1_M1
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 Customer Intelligence Studio 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 Studio 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 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.
K88009 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.
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.
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.
K85009 updates SAS Digital Marketing Server Components 6.1_M1
NONE
K86009 updates SAS Digital Marketing Studio 6.1_M1
NONE
K87009 updates SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.1_M1
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 SAS Digital Marketing Web Studio and Web Reporting Infrastructure 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 Digital Marketing Web Studio and Web Reporting Infrastructure in
<CONFIGDIR>\Lev1\Web\Staging. Two ear files are created: “bess.ear” and “sas.DigitalMarketingWebStudio6.1.ear”.
If you are running in a double bess.war architecture, then a second copy of the bess.ear file is also provided, bess_proxy.ear,
for the external application server. Each of these must be redeployed into their respective application servers following
this step.
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 listed above 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.
This completes the installation of hot fix K90009 on 64-bit Enabled Solaris.