Installation Instructions for Hot Fix R47014

Linux for x64


Hot fix R47014 addresses the issue(s) in SAS Digital Marketing 6.3 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/R47.html#R47014


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

R40015  updates  SAS Customer Intelligence Common Logical Types 6.3
S57003  updates  SAS Customer Intelligence Common Server 6.3
R41015  updates  SAS Customer Intelligence Studio 6.3
R48014  updates  SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.3
R46014  updates  SAS Digital Marketing Logical Types 6.3
R43014  updates  SAS Digital Marketing Server Components 6.3
R44014  updates  SAS Digital Marketing Studio 6.3
R45015  updates  SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.3

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

Do NOT extract the contents of R47014pt.zip. The hot fix installation process will extract the contents as needed.


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. If you have SSL enabled in your SAS Customer Intelligence architecture, please review SAS Note 56670 before applying the hot fix on the mid-tier.

  6. If you see this message displayed by SAS Deployment Manager during the install process:

    The specified configuration directory and level do not contain any product configurations that require hot fixes.

    Uncheck the ”Configure SAS hot fix” checkbox and continue with the hot fix install.


INSTALLATION

If your installation has any combination of SAS Marketing Automation (MA), SAS Marketing Optimization (MO), and/or SAS Digital Marketing (SDM), the Apply Hot Fixes, Rebuild Web Applications, and Deploy Web Applications steps can be combined and performed for MA, MO, and SDM in one iteration per step. This can be performed as follows:

Hot Fix R47014 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.3 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 R47014pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: 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

  1. Copy ci_common.xml

    Before running the steps for "Web Application Update", you will need to copy ci_common.xml
    from:
    <SASHome>/SASCustomerIntelligenceStudio/6.3/Config/hfmisc
    to:
    <SASHome>/SASDeploymentManager/9.4/products/cfgwizard__**__prt__xx__sp0__1/Utilities/contrib/customerintelligence

    where ** is the highest number, if there is more than one cfgwizard directory.

  2. Web Application Update

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

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

    Rebuild the following Web Applications:

    Redeploy the following Web Applications:

    For more information about how to rebuild and redeploy Web Applications, see the SASŪ 9.4 Intelligence Platform, Middle-Tier Administration Guide, Chapter 8 Administering SAS Web Applications on Rebuilding the SAS Web Applications and Redeploying the SAS Web Applications.

    This process will update the Digital Marketing Web Studio and Web Reporting Infrastructure in <CONFIGDIR>/Lev1/Web/Staging/exploded. If you are running in a double bess.war architecture, then a second copy of the bess.war file is also provided (bess_proxy.war) for the external web application server. A backup of the original archives will be placed in the Staging/Backup directory. The <CONFIGDIR>/Lev1/Web/Staging/exploded/bess.ear/bess.war and <CONFIGDIR>/Lev1/Web/Staging/exploded/bess_proxy.ear/bess_proxy.war directories must be deployed to their respective web application servers following this step (Note: Deploying the bess.war and bess_proxy.war files is a manual step).

  3. For each product installed, click the link to be redirected to post-installation instructions.
    R40015  updates  SAS Customer Intelligence Common Logical Types 6.3
    S57003  updates  SAS Customer Intelligence Common Server 6.3
    R41015  updates  SAS Customer Intelligence Studio 6.3
    R48014  updates  SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.3
    R46014  updates  SAS Digital Marketing Logical Types 6.3
    R43014  updates  SAS Digital Marketing Server Components 6.3
    R44014  updates  SAS Digital Marketing Studio 6.3
    R45015  updates  SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.3
  4. 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 R47001, you need to review R47001 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.

    R47012
    SAS Note 56379 An error occurs when you run certain reports on the SASŪ Digital Marketing server
    http://support.sas.com/kb/56379

    SAS Note 60293 Names in the legend for SASŪ Digital Marketing reports are incorrectly formatted
    http://support.sas.com/kb/60293

    R47010
    SAS Note 58871 You cannot connect to the SASŪ Digital Marketing server following a system restart in a clustered environment
    http://support.sas.com/kb/58871

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

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


R40015  updates  SAS Customer Intelligence Common Logical Types 6.3

NONE


S57003  updates  SAS Customer Intelligence Common Server 6.3

NONE


R41015  updates  SAS Customer Intelligence Studio 6.3

NONE


R48014  updates  SAS Digital Marketing Extensions for SAS Customer Intelligence Studio 6.3

NONE


R46014  updates  SAS Digital Marketing Logical Types 6.3

NONE


R43014  updates  SAS Digital Marketing Server Components 6.3

NONE


R44014  updates  SAS Digital Marketing Studio 6.3

NONE


R45015  updates  SAS Digital Marketing Web Studio and Web Reporting Infrastructure 6.3

Review the instructions in this SAS Note 56374 The options to prevent duplicate emails and to identify preview messages fail after the SASŪ Digital Marketing web applications are rebuilt
http://support.sas.com/kb/56374


This completes the installation of hot fix R47014 on Linux for x64.

Copyright 2018 SAS Institute Inc. All Rights Reserved.