Hot fix B3R006 addresses the issue(s) in SAS Revenue Optimization 5.4 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/B3R.html#B3R006
B3R006 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
B3V009 updates SAS Merchandise Intelligence Client 5.41
B4A009 updates SAS Merchandise Intelligence Grid Server 5.41
B3W009 updates SAS Merchandise Intelligence Mid-Tier 5.41
B3U009 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.41
B3Z006 updates SAS Merchandise Intelligence Server 5.41
B3S009 updates SAS Merchandise Intelligence Workbench Server 5.41
B3T009 updates SAS Merchandise Solutions Configuration Workbench 5.41
B3X003 updates SAS Revenue Optimization Server 5.4
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, B3R006pt.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 B3R006pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of B3R006pt.zip. The hot fix installation process will extract the contents as needed.
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 B3R006pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.
Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.
The hot fix installation process generates the log file
<!SASHOME>\InstallMisc\InstallLogs\IT_date-and-time-stamp.logfor 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.
SAS Security Updates
The following instruction applies only for environments running SAS 9.4 M6 or earlier:
SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at https://tshf.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.
For each product installed, click the link to be redirected to post-installation instructions.
B3V009 updates SAS Merchandise Intelligence Client 5.41
B4A009 updates SAS Merchandise Intelligence Grid Server 5.41
B3W009 updates SAS Merchandise Intelligence Mid-Tier 5.41
B3U009 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.41
B3Z006 updates SAS Merchandise Intelligence Server 5.41
B3S009 updates SAS Merchandise Intelligence Workbench Server 5.41
B3T009 updates SAS Merchandise Solutions Configuration Workbench 5.41
B3X003 updates SAS Revenue Optimization Server 5.4
B3V009 updates SAS Merchandise Intelligence Client 5.41
NONE
B4A009 updates SAS Merchandise Intelligence Grid Server 5.41
NONE
B3W009 updates SAS Merchandise Intelligence Mid-Tier 5.41
This hot fix requires post-installation steps that will update the web application deployed to your application server. 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.
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.4
From the SASDeploymentManager directory launch sasdm.exe.
SAS Deployment Manager is installed in the following default location:
<SASHOME>\SASDeploymentManager\9.4
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 Merchandise Intelligence Mid-Tier 5.4 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 5.4 ear in
<SASCONFIGDIR>\Web\StagingA backup of the original ear file will be placed in the directory
<SASCONFIGDIR>\Web\Staging\Backup
9. Exit the SAS Deployment Manager 9.4
Re-deploy Web Application
1. Restart all SAS sessions, daemons, spawners and servers.
2. Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.exe.
SAS Deployment Manager is installed in the following default location:
<SASHOME>\SASDeploymentManager\9.4
3. Select a language in the Choose Language box
4. Select Deploy Web Applications
5. Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
6. Specify Connection Information, including the sasadm User ID and Password
7. Check the Allow the application server to stop checkbox
8. Select Merchandise Intelligence Mid-Tier 5.4 as the Web Application to Deploy
9. Verify the information on the Summary screen and select Start
10. Select Finish and exit the SAS Deployment Manager when the deployment is complete
Steps to perform changing the log level in the mid-tier log4j.xml
1. Find the <SASMerchIntelMidTier-log4j.xml> file @ location
/install/SASInstall/SASConfig/Lev1/Web/Common/LogConfig/
2. Observe the Threshold value for all FileAppender, DailyRollingFileAppender, RollingFileAppender
FileAppender:
<appender class="org.apache.log4j.FileAppender" name="SAS_FILE">DailyRollingFileAppender:
<param name="Threshold" value="WARN"/>
Modify the value of Threshold to "DEBUG"
<appender class="org.apache.log4j.DailyRollingFileAppender" name="SAS_FILE">RollingFileAppender:
<param name="Threshold" value="WARN"/>
Modify the value of Threshold to "DEBUG"
<appender class="org.apache.log4j.RollingFileAppender" name="SAS_FILE">
<param name="Threshold" value="WARN"/>
Modify the value of Threshold to "DEBUG"
3. Change the di server logging level from WARN to DEBUG to get the DEBUG logs
<!-- SAS: DI Solutions -->
<logger name="com.sas.solutions.di.server" additivity="false">
<level value="WARN" />
Modify the value of level in <level value="DEBUG"
4. Save the file
5. Then Stop and Start the SASServer8
/install/SASInstall/SASConfig/Lev1/Web/WebAppServer/SASServer8_1/bin/tcruntime-ctl.sh <stop / status / start>
Mid-tier logs get generated in DEBUG level.
B3U009 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.41
NONE
B3Z006 updates SAS Merchandise Intelligence Server 5.41
This Hot fix contains changes to the existing database schema.
The last Release/Hotfix containing database schema alters was Release 5.4.
Running the Update Data Mart Script
Required to be run as this hot fix contains changes to the existing database schema.
This script updates the existing data mart schema to the latest.
Note: When you run the update_datamart 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 July 07, 2017, at 05:50 a.m.:
       update_datamart_20170707_0550.log
B3S009 updates SAS Merchandise Intelligence Workbench Server 5.41
NONE
B3T009 updates SAS Merchandise Solutions Configuration Workbench 5.41
NONE
B3X003 updates SAS Revenue Optimization Server 5.4
This Hot fix contains changes to the existing database schema.
Running the Update Data Mart Script
Required to be run as this hot fix contains changes to the existing database schema.
This script updates the existing data mart schema to the latest.
Note: When you run the update_datamart 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 July 07, 2017, at 05:50 a.m.:
       update_datamart_20170707_0550.log
This completes the installation of hot fix B3R006 on Windows for x64.
Copyright 2019 SAS Institute Inc. All Rights Reserved.