Hot fix B82003 addresses the issue(s) in SAS Merchandise Intelligence 4.2 on Windows for x64 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/B82.html#B82003
This hot fix contains updates to the following software components:
SAS Merchandise Intelligence Server 4.2
SAS Size Profiling 2.2
SAS Merchandise Intelligence Mid-Tier 4.2
If the updated components of this product are installed on multiple operating systems, you must download the hot fix for the appropriate operating system(s) and follow the installation instructions provided to complete the deployment of this hot fix.
To install this hot fix execute the following steps.
1. The installer downloaded is B82003x6.exe.
2. Execute B82003x6.exe
This will initiate the installation wizard, which will guide you through the hot fix
installation process.
See the Maintenance Installation Tool
(MIT) documentation for more details on the installation of hot fixes.
Post-Installation Instructions for the Middle Tier
Updates to the SAS Merchandise Intelligence Mid-Tier 4.2 provided in this hot fix require that the
Web Application be rebuilt and redeployed. If this component is installed on Windows, follow the steps below to
rebuild and redeploy the web application:
Re-build Web Application
In order for this step to execute correctly, the Metadata Server must be running.
1. Invoke the SAS Deployment Manager 9.2
From the SASDeploymentManager directory launch config.exe.
SAS Deployment Manager is installed in the following default location:
<SASHOME>\SASDeploymentManager\9.2
2. Select a language in the Choose Language box
3. Select Rebuild Web Applications
4. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
5. Specify Connection Information, including the sasadm User ID and Password
6. Select SAS Merchandise Intelligence Mid-Tier 4.2 as the Web Application to Rebuild
7. Verify the information on the Summary screen and select Start
8. Select Finish when the deployment is complete
This process will update the SAS Merchandise Intelligence Mid-Tier 4.2 ear in
<SASCONFIGDIR>\Lev1\Web\StagingA backup of the original ear file will be placed in the directory
<SASCONFIGDIR>\Lev1\Web\Staging\Backup
1. Re-deploy the SAS Merchandise Intelligence Mid-Tier 4.2 web application (only). Details are provided at
Note: Select sas.miserver4.2.ear when re-deploying the web application.2. Stop and restart the Web application server.
Note for WebLogic: If the SAS Merchandise Intelligence Mid-Tier is not started automatically after following the instructions in the link above, you will need to manually start it from the WebLogic Admin Console.
Alternative Method: The SAS Merchandise Intelligence Mid-Tier can be re-deployed to WebLogic using
the following steps. The equivalent steps for WebSphere are documented in the Replace the entire application
method in the detailed document link above.
1. Ensure all the services are running, including WebLogic Admin Console and Managed Server, i.e. SASServer1.
2. Login to WebLogic Admin Console.
3. Click on Lock and Edit.
4. Select the sas.miserver4.2 ear and click on the Update button.
5. Accept the default path and click on OK.
6. Click on the Activate changes button.
The web application server does not need to be restarted after using the alternative method. The Activate changes step will restart the SAS Merchandise Intelligence Mid-Tier internally.
Post-Installation Instructions for the Client Tier (SAS Size Profiling Only)
To finish deploying the hot fix, you must locate your copied profiles, and then unpublish and delete the copied profiles. (These profiles are missing store group membership data). You can then recopy and publish the profiles.
1. To locate copied profiles, use the Profiles view and check the Independent profiles only check box to search for all independent profiles in the system.
2. Unpublish the profiles that were published from copied profiles. This will clean up the published profile library for the profiles that are missing store group membership.
3. Delete the copied profiles since these profiles do not have the appropriate store group membership data.
4. If you need to re-publish the above profiles:
a. Re-copy those profiles.Previously copied-and-published profiles with missing store groups data will now be created correctly via the newly copied profiles.
b. Make your changes to the newly-copied profiles.
c. Re-publish the newly copied profiles.
This completes the installation of hot fix B82003 on Windows for x64.