Installation Instructions for Hot Fix M56005

Windows


Hot fix M56005 addresses the issue(s) in SAS Size Optimization 3.2_M3 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/M56.html#M56005


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

M40007  updates  SAS Merchandise Intelligence Client 5.21_M3
M45007  updates  SAS Merchandise Intelligence Grid Server 5.21_M3
M41007  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M3
M42007  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M3
M57004  updates  SAS Merchandise Intelligence Server 5.21_M3
M43007  updates  SAS Merchandise Intelligence Workbench Server 5.21_M3
M44007  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M3
P99001  updates  SAS Pack Optimization Server 3.2_M3
M83001  updates  SAS Size Profiling Server 3.2_M3

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

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


IMPORTANT NOTES

  1. You must have SAS Merchandise Intelligence 5.2_M3 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 M56005 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 Size Optimization 3.2_M3 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 M56005pt.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.

M40007  updates  SAS Merchandise Intelligence Client 5.21_M3
M45007  updates  SAS Merchandise Intelligence Grid Server 5.21_M3
M41007  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M3
M42007  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M3
M57004  updates  SAS Merchandise Intelligence Server 5.21_M3
M43007  updates  SAS Merchandise Intelligence Workbench Server 5.21_M3
M44007  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M3
P99001  updates  SAS Pack Optimization Server 3.2_M3
M83001  updates  SAS Size Profiling Server 3.2_M3


M40007  updates  SAS Merchandise Intelligence Client 5.21_M3

NONE


M45007  updates  SAS Merchandise Intelligence Grid Server 5.21_M3

NONE


M41007  updates  SAS Merchandise Intelligence Mid-Tier 5.21_M3

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


Step 5:    Change the Middle Tier Property com.sas.solutions.di.server.epupdateinone to True
To change the middle-tier property, follow these steps.

  1. Make sure the Merchandise Intelligence Mid-Tier server is stopped by stopping JBoss. See "Starting and Stopping the Servers" on page 230 of the Administrator's Guide for more information.
  2. Open the SAS Management Console and navigate to Application Management ->Configuration Manager->Merchandise Intell Mid-Tier 5.2 .
  3. Right-click and select Properties, and then click the Advanced tab.
  4. Click Add to display the Define New Property dialog box.
  5. Enter the property name as shown and specify the property value: Property Name: com.sas.solutions.di.server.epupdateinone Property Value:True
  6. Click OK. Click OK.
  7. Start the Merchandise Intelligence Mid-Tier server.
To verify that the setting is in effect, when you initially log into the client check the mid-tier log for the following message. Using value true for property "com.sas.solutions.di.server.epupdateinone"


M42007  updates  SAS Merchandise Intelligence Plug-in for SAS Management Console 5.21_M3

NONE


M57004  updates  SAS Merchandise Intelligence Server 5.21_M3

Note: This hot fix adds the ALLOW_UNITS_FOR_ZERO_NEED global setting. For details, see the Administrator’s Guide Errata document.

Run the Update Data Mart Script To update the existing data mart:

  1. Log on as MI ETL User (sasmietl).

  2. From the sasmietl home directory, run the migration script:
    \Lev1\Applications\SASMerchIntellServer5.2\sas\update_datamart.bat

  3. Check the log file (update_datamart.log) for output and errors.

Note: When you run the migration script, the system adds a date and time stamp to the name of the log file. This enables the system to maintain multiple versions of the log files. It also makes it easier to identify which log files correspond to specific runs of the scripts.

Here is an example of a log file that results from a script run on May 8, 2012, at 9:44 a.m.:
         update_datamart_20120508_0944.log


For SAS Size Profiling Only, MGPS_ACTIVATE_ALL_SIZES setting in the PRF_CONFIG Table
For information about the MGPS_ACTIVATE_ALL_SIZES setting in the PRF_CONFIG table, refer to the Errata document for the SAS Size Profiling Reference Guide.


M43007  updates  SAS Merchandise Intelligence Workbench Server 5.21_M3

NONE


M44007  updates  SAS Merchandise Solutions Configuration Workbench 5.21_M3

NONE


P99001  updates  SAS Pack Optimization Server 3.2_M3

NONE


M83001  updates  SAS Size Profiling Server 3.2_M3

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 M56005 on Windows.

Copyright 2016 SAS Institute Inc. All Rights Reserved.