Installation instructions for hot fix I40001 on Windows for x64

Installation Instructions for Hot Fix I40001

Windows for x64

Hot fix I40001 addresses the issue(s) in SAS Merchandise Intelligence 4.2_M3 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/I40.html#I40001

I40001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated. See the Container Hot Fixes section in the Maintenance Install Tool (MIT) Usage Guide for more information about container hot fixes.

I42001 for SAS Merchandise Intelligence Client 4.2_M3
I45001 for SAS Merchandise Intelligence Mid-Tier 4.2_M3
I44001 for SAS Merchandise Intelligence Plug-in for SAS Management Console 4.2_M3
I43001 for SAS Merchandise Solutions Configuration Workbench 4.2_M3

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 software components and release numbers should match the list of software components updated by the individual hot fix installers.

IMPORTANT NOTES

You must have SAS Merchandise Intelligence 4.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.
At a minimum, back up your system:
a. For SAS, refer to the SAS 9.2 maintenance release documentation about back up tasks:
http://support.sas.com/documentation/cdl/en/whatsdiff/63928/HTML/default/viewer.htm#p083vd5jhklkfun1dxrana9mo7co.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.02232009
where 02232009 is the date when the maintenance release is applied. The extension must be appended after the .jar extension, as it appears above.
You must have the appropriate administrative privileges to perform the steps described in these instructions.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix:
- Stop the MI Mid-Tier Server. To stop the MI Mid-Tier Server, stop the Web application server, which also stops the MI Mid-Tier Server.
- Stop the SAS Services Application (Remote Services).
- Ensure that all stored processes are finished.
- Stop the SAS object spawner or stop all server sessions, and then ensure that all server sessions have finished running.
- (Optional) Stop the SAS/CONNECT spawner and the SAS Deployment Tester.
- Stop the SAS Metadata Server
This hot fix should be installed using the same userid who performed the initial software installation.
You must deploy the hot fix in the following timeframe
- after your weekly activity has completed
- before the weekly ETL and back-end job

PRE-INSTALLATION INSTRUCTIONS

SAS Merchandise Intelligence Client 4.2_M3

Please perform below step on all SAS Merchandise Intelligence Client machines before installing Merchandise Intelligence client pieces for hotfix.

Make a backup of the file config.ini, then delete config.ini from following client installation directory:

<SASHOME>\SASMerchandiseIntelligenceClient\4.2\configuration

SAS Merchandise Solutions Configuration Workbench 4.2_M3

Please perform below step on all SAS Merchandise Solutions Configuration Workbench machines before installing Merchandise Solutions Configuration Workbench pieces for hotfix.

Make a backup of the file config.ini, then delete config.ini from following client installation directory:

<SASHOME>\SASMerchandiseSolutionsConfigurationWorkbench\4.2\configuration

INSTALLATION

This hot fix must be installed on each machine where the updated components of the product, listed above, are installed. The installation process will determine which components of SAS Merchandise Intelligence 4.2_M3 are installed on each machine, and apply the appropriate updates.

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.

The installer downloaded is I40001x6.exe.

When downloading SAS 9.2 hot fix packages, you must choose to Save the hot fix to disk, then execute the install from the saved location. Attempting to install a hot fix directly from the download page results in the error documented in SAS Note 37104.

To install this hot fix execute I40001x6.exe from command prompt with -skipVersionCheck option
Example:
c:\Temp>I40001x6.exe -skipVersionCheck

This will initiate the installation wizard, which will guide you through the hot fix installation process.

Note: If your Windows operating system is Windows Vista, Windows 7 or Windows Server 2008, it may be necessary to "right-click" I40001x6.exe and select "Run as administrator".

See the Maintenance Install Tool (MIT) Usage Guide for more details on the installation of hot fixes.

The content of this hot fix is listed in the hot fix manifest.

This completes the installation of I40001. You must perform any "Post-Installation Instructions" documented below to successfully complete the deployment of this hot fix.

POST-INSTALLATION INSTRUCTIONS

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

I42001 for SAS Merchandise Intelligence Client 4.2_M3
I45001 for SAS Merchandise Intelligence Mid-Tier 4.2_M3
I44001 for SAS Merchandise Intelligence Plug-in for SAS Management Console 4.2_M3
I43001 for SAS Merchandise Solutions Configuration Workbench 4.2_M3

I42001 for SAS Merchandise Intelligence Client 4.2_M3

The installation of the hot fix to the SAS Merchandise Intelligence Client assumes that the client is installed in

C:\Program Files\SAS\

If the client is installed in a location other than C:\Program Files\SAS, the file

<SASHOME>\SASMerchandiseIntelligenceClient\4.2\configuration\config.ini

must be manually modified. All occurences of

C:\Program Files\SAS\

must be changed the location to where the client is installed. You should confirm that the SASVersionedJarRepository paths are correct for your installation.

I45001 for SAS Merchandise Intelligence Mid-Tier 4.2_M3

Updates to the SAS Merchandise Intelligence Mid-Tier 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:

Note: The metadata server must be up and running before the web application is re-built.

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\Staging

A backup of the original ear file will be placed in the directory

<SASCONFIGDIR>\Lev1\Web\Staging\Backup

Re-deploy Web Application

1. Re-deploy the SAS Merchandise Intelligence Mid-Tier 4.2 web application (only). Details are provided at

http://support.sas.com/documentation/cdl/en/biwaag/63536/HTML/default/viewer.htm#/documentation/cdl/en/biwaag/63536/HTML/default/a003308992.htm

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.

I44001 for SAS Merchandise Intelligence Plug-in for SAS Management Console 4.2_M3

NONE

I43001 for SAS Merchandise Solutions Configuration Workbench 4.2_M3

The installation of the hot fix to the SAS Merchandise Solutions Configuration Workbench assumes that the client is installed in

C:\Program Files\SAS\

If the client is installed in a location other than C:\Program Files\SAS, the file

<SASHOME>\SASMerchandiseSolutionsConfigurationWorkbench\4.3\configuration\config.ini

must be manually modified. All occurences of

C:\Program Files\SAS\

must be changed the location to where the Configuration Workbench is installed. You should confirm that the SASVersionedJarRepository paths are correct for your installation.

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

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