Installation Instructions for Hot Fix J17001

Windows for x64


Hot fix J17001 addresses the issue(s) in SAS Revenue Optimization 5.2_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/J17.html#J17001


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

J09002  updates  SAS Merchandise Intelligence Client 5.21_M1
J11002  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M1
J10002  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M1
J20001  updates  SAS Merchandise Intelligence Server 5.21_M1
J18001  updates  SAS Merchandise Intelligence Workbench Server 5.21_M1
J19001  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M1
J24001  updates  SAS Promotion Optimization 5.2_M1
J23001  updates  SAS Regular Price Optimization 5.2_M1
J21001  updates  SAS Revenue Optimization Server 5.2_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, J17001x6.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 J17001x6.zip on each machine or save it in a network location that is accessible to all machines.

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


IMPORTANT NOTES

  1. You must have SAS Merchandise Intelligence 5.2_M1 installed on your system before applying this hot fix. Refer to SN-35968 for instructions on how to determine which product releases you have installed.

  2. At a minimum, back up your system:
    a.    For SAS, refer to the SAS 9.3 Guide to Software Updates for documentation about back up tasks:
    http://support.sas.com/documentation/cdl/en/whatsdiff/63859/HTML/default/viewer.htm#titlepage.htm

    b.    For SAS Merchandise Intelligence, backup the MI data mart and database.
    Technical Support strongly suggests that you back up all of your files. You should always try to include the current date in the name of the backup file created to distinguish between versions of backup files. By doing this, you will maintain a history of the file, which will be helpful when multiple iterations of a maintenance release have been applied to the same file. For example:
           cp com.sas.solutions.di.server.jar com.sas.solutions.di.server.jar.08202012
           where 08202012 is the date when the maintenance release is applied.
    The extension must be appended after the .jar extension, as it appears above.

  3. You must have Administrator Privileges on your CLIENT or SERVER machine.

  4. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix:

  5. This hot fix should be installed using the same userid who performed the initial software installation.

  6. You must deploy the hot fix in the following timeframe


INSTALLATION

Hot Fix J17001 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 Revenue Optimization 5.2_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.

After downloading J17001x6.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

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

J09002  updates  SAS Merchandise Intelligence Client 5.21_M1
J11002  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M1
J10002  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M1
J20001  updates  SAS Merchandise Intelligence Server 5.21_M1
J18001  updates  SAS Merchandise Intelligence Workbench Server 5.21_M1
J19001  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M1
J24001  updates  SAS Promotion Optimization 5.2_M1
J23001  updates  SAS Regular Price Optimization 5.2_M1
J21001  updates  SAS Revenue Optimization Server 5.2_M1


J09002  updates  SAS Merchandise Intelligence Client 5.21_M1

NONE


J11002  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M1

Web application Update

Updates to the SAS Merchandise Intelligence Mid-Tier 5.21 provided in this hot fix require that Web Applications be rebuilt and redeployed. If this component is installed on Unix, follow the steps below to rebuild and redeploy the web application:

Step 1.    Remove com.sas.app.launcher.cacheFile

Delete

<SASHOME>\SASVersionedJarRepository\eclipse\com.sas.app.launcher.cacheFile

Step 2:   Re-build Web Applications

Note: In order for this step to execute correctly, the Metadata Server must be running.

Re-build the Merchandise Intelligence Mid-Tier 5.2 Web application as instructed here:

SAS(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide


Note: Select Merchandise Intell Mid-Tier 5.2 Web Applications to Rebuild


This process will update the SAS Merchandise Intelligence Mid-Tier 5.2 ear in

<CONFIGDIR>\Lev1\Web\Staging
A backup of the original ear file will be placed in the Backup directory.


Step 3:   Re-deploy Web Applications

Re-deploy the Merchandise Intell Mid-Tier 5.2 Web application (only). Re-deploy the SAS Web Applications as instructed here:

SAS(R) 9.3 Intelligence Platform: Middle-Tier Administration Guide

Note: Select sas.miserver5.2.ear when re-deploying the Web application.


Step 4:    Stop and restart the Web application server.


J10002  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M1

NONE


J20001  updates  SAS Merchandise Intelligence Server 5.21_M1

NONE


J18001  updates  SAS Merchandise Intelligence Workbench Server 5.21_M1

NONE


J19001  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M1

NONE


J24001  updates  SAS Promotion Optimization 5.2_M1

NONE


J23001  updates  SAS Regular Price Optimization 5.2_M1

NONE


J21001  updates  SAS Revenue Optimization Server 5.2_M1

NONE


After completing all of the post-install sections above, run your weekly ETL and back-end jobs.


This completes the installation of hot fix J17001 on Windows for x64.