Installation instructions for hot fix W19023 on Linux for x64

Installation Instructions for Hot Fix W19023

Linux for x64

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

https://tshf.sas.com/techsup/download/hotfix/HF2/W19.html#W19023

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

W23018 updates SAS Merchandise Intelligence Client 5.4
W24018 updates SAS Merchandise Intelligence Mid-Tier 5.4
W22018 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.4
Z33014 updates SAS Merchandise Intelligence Server 5.4
W20018 updates SAS Merchandise Intelligence Workbench Server 5.4
W21018 updates SAS Merchandise Solutions Configuration Workbench 5.4
Z35008 updates SAS Pack Optimization Mid-Tier LASR Configuration 3.4
A9K005 updates SAS Pack Optimization Server 3.4
Z36008 updates SAS Size Profiling Mid-Tier LASR Configuration 3.4
Y07015 updates SAS Size Profiling Server 3.4

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

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

IMPORTANT NOTES

Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
CONFIGURATION: No automatic configuration scripting is required for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.
You must deploy the hot fix in the following timeframe
- after your weekly activity has completed
- before the weekly ETL and back-end job

INSTALLATION

Hot Fix W19023 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.4 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 W19023pt.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.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.

W23018 updates SAS Merchandise Intelligence Client 5.4
W24018 updates SAS Merchandise Intelligence Mid-Tier 5.4
W22018 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.4
Z33014 updates SAS Merchandise Intelligence Server 5.4
W20018 updates SAS Merchandise Intelligence Workbench Server 5.4
W21018 updates SAS Merchandise Solutions Configuration Workbench 5.4
Z35008 updates SAS Pack Optimization Mid-Tier LASR Configuration 3.4
A9K005 updates SAS Pack Optimization Server 3.4
Z36008 updates SAS Size Profiling Mid-Tier LASR Configuration 3.4
Y07015 updates SAS Size Profiling Server 3.4

W23018 updates SAS Merchandise Intelligence Client 5.4
W21018 updates SAS Merchandise Solutions Configuration Workbench 5.4

Security Update for SAS Merchandise Intelligence Client 5.4 and SAS Merchandise Solutions Configuration Workbench 5.4

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.

W24018 updates SAS Merchandise Intelligence Mid-Tier 5.4

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
a. From the SASDeploymentManager directory sasdm.exe.
b. 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 the Product Configuration Merchandise Intell 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
a. This process will update the sas.miserver5.4.ear file in
<SASCONFIGDIR>>/Lev1/Web/Staging
b. A backup of the original ear file will be placed in the directory
<SASCONFIGDIR>>/Lev1/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
a.From the SASDeploymentManager directory launch sasdm.sh.
b.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 the Product Configuration Merchandise Intell 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

Update DAV Content

These steps were introduced by Hot Fix W19007 and are only required to be done once. If you have previously applied Hot Fix W19007 please skip this section.

Note: You can use DAVTree on UNIX/Windows, For Unix you must have a graphical interface.
DAVTree can be found in <SASCONFIGDIR>>/Lev1/Web/Utilities./DAVTree.sh

If you do not have a graphical interface, use a UNIX command line tool that supports upload to WebDAV. For example, use DAVExplorer instead of DAVTree to perform the following steps.

WebDAV URL - - http://server-name:port/SASContentServer/repository/default/sasdav/
server-name is your MidTier hostname.
Port – is the port on which Webserver is configured to use

Update file prf-table.properties
(location - http://server-name:port/SASContentServer/repository/default/sasdav/Products/SAS Merchandise Intelligence Server/Configuration Documents/Property Files/prf-table.properties)

Add the following lines:-

ColumnHeading.ProfilingProject_ReportId.txt=Report ID
ColumnHeading.ProfilingProject_ReportStatus.txt=Report Status
ColumnHeading.ProfilingProject_LoadedBy.txt=Loaded By
ColumnHeading.ProfilingProject_ReportSchedule.txt=Report Scheduled
ColumnHeading.ProfilingProject_ExtractTime.txt=Last Report Generated

Update file pko-table.properties
(location - http://server-name:port/SASContentServer/repository/default/sasdav/Products/SAS Merchandise Intelligence Server/Configuration Documents/Property Files/pko-table.properties)

Add the following lines:-

ColumnHeading.ReportId.txt=Report ID
ColumnHeading.ReportStatus.txt=Report Status
ColumnHeading.LoadedBy.txt=Loaded By
ColumnHeading.ReportSchedule.txt=Report Scheduled
ColumnHeading.ExtractTime.txt=Last Report Generated

Update file prf-views.xml
(location - http://server-name:port/SASContentServer/repository/default/sasdav/Products/SAS Merchandise Intelligence Server/Configuration Documents/prf-views.xml)

In the tag <elements id="ProfilingProjectsColumnsElements" add the following lines:

<element id="ProfilingProject_ReportId" width="150" required="false" visible="true" />
<element id="ProfilingProject_ReportStatus" width="150" required="false" visible="true" />
<element id="ProfilingProject_LoadedBy" width="150" required="false" visible="false" />
<element id="ProfilingProject_ReportSchedule" width="70" required="false" visible="false" />
<element id="ProfilingProject_ExtractTime" width="124" required="false" visible="false" />

Update file pko-views.xml
(location http://server-name:port/SASContentServer/repository/default/sasdav/Products/SAS Merchandise Intelligence Server/Configuration Documents/pko-views.xml)

In the tag <elements id="PurchaseOrderPlan" add the following lines:

<element id="ReportId" width="150" visible="true" />
<element id="ReportStatus" width="150" visible="true" />
<element id="LoadedBy" width="150" visible="false" />
<element id="ReportSchedule" width="70" visible="false" />
<element id="ExtractTime" width="124" visible="false" />

Importing .SPK File:
This change was introduced by Hot Fix W19013 and is only required to be done once. If you have previously applied Hot Fix W19013 please skip this section.

Copy Size_Profiling.spk from <SASHome>/SASSizeProfilingMidTierLASRConfiguration/3.4/Config/Deployment/SASPackages/ to a folder on MI client machine.

Take a backup of the existing metadata.

Use SAS Management console to import the delivered SPK files.

1. Log on to SAS Management Console as the Administrator (sasadm) user.
2. Select the Folders tab.
3. Right-click SAS Folders and select Import SAS Package.
4. On the Import SAS Package page, browse to the location where the spk files were kept on the client machine and select the Size_Profiling.spk file.
5. Select All Object and click Next.
On the Select Objects to Import page, make sure that the following are available:
In the SAS Folders > Products > SAS Merchandise Intelligence LASR > Size Optimization > Reports folder,
- Butterfly chart
- Triple Axis Chart
- Sample - SAS Size Profiling Analysis of Results
In the SAS Folders > Products > SAS Merchandise Intelligence LASR > Size Optimization > Reports Metadata folder:
- Size Optimization LASR
- SIZE_PROFILING_REPORT
6. Click Next.
7. On the About Metadata Connections page, the metadata properties are displayed. Click Next.
8. On the SAS Application Servers page, select Application server of VA as the target application server and click Next.
9. On the Other Servers page, select LASR Analytics Server and click Next.
10. Review the Summary information and click Next, if the details are correct. Otherwise, click Back to make necessary corrections in the earlier steps.
The next screen displays that the import was completed. Click View Log and scan the log for any errors. If the import was successful, the message "The import process completed successfully" appears in the log.
11. Click Finish.

Modify the “Sample – SAS Size Profiling Analysis of Results” report in report designer with below changes.

Note : these steps should be implemented after completing the data mart updates & manual steps

1. After all the other Hotfix steps have been executed, start the LASR server, login into the MIClient as a SASMI user.
2. Select a small project, and create a VAAR extract, and load it into VA. Note the extract name in REPORT ID column in Project listing page.
3. Launch Visual Analytics from the link in the Size Profiling UI's Welcome Page.
4. Open the Report Designer. Click File --> Open.
5. Drill to Products --> SAS Merchandise Intelligence --> Size Optimization --> Reports
6. Select --> Sample – SAS Size Profiling Analysis of Results and click open.
7. If you get a message to change the data source or the data source is blank, select the newly loaded SZPF_EXTRACT_xxxxx file (noted down in step 2 above).
8. Click the Data tab.
9. Click on the Column "Size Name"
10. In the Sort Options Property, select the Value of "Unformatted"
11. From the File menu, select Save as.
12. In the same folder, save the report as SO_Profiling_Analysis and click save.
13. Exit.

Importing .SPK File:
This change is introduced by this Hot Fix W19014 and is only required to be done once. You will not be required to repeat these steps for future hot fixes.

Copy Pack_Optimization.spk from <SASHome>/SASPackOptimizationMidTierLASRConfiguration/3.4/Config/Deployment/SASPackages/ to a folder on MI client machine.

Take a backup of the existing metadata.

Use SAS Management console to import the delivered SPK files.

1. Log on to SAS Management Console as the Administrator (sasadm) user.
2. Select the Folders tab.
3. Right-click SAS Folders and select Import SAS Package.
4. On the Import SAS Package page, ensure the box marked "Preserve source path information for objects in this package" is checked, browse to the location where the spk files were kept on the client machine and select the Pack_Optimization.spk file.
5. Select All Object and click Next.
6. On the About Metadata Connections page, the metadata properties are displayed. Click Next.
7. On the SAS Application Servers page, select Application server of VA as the target application server and clickNext.
8. On the Other Servers page, select LASR Analytics Server and click Next.
9. Review the Summary information and click Next, if the details are correct. Otherwise, click Back to make necessary corrections in the earlier steps.
10. The next screen displays that the import was completed. Click View Log and scan the log for any errors. If the import was successful, the message "The import process completed successfully" appears in the log.
11. Click Finish.

Modify the “Sample –SAS Pack Optimization Scorecard” report in report designer with below changes:

1. After all the other Hotfix steps have been executed, start the LASR server,
2. Launch Visual Analytics from the link in the Pack Optimization UI's Welcome Page.
3. Open the Report Designer. Click File -> Open.
4. Drill to Products -> SAS Merchandise Intelligence -> Size Optimization -> Reports
5. Select -> Sample – Sample - SAS Pack Optimization Scorecard and click open.
6. From the File menu, select Save as.
7. In the same folder, save the report as SO_Pack_Analysis and click save.
8. Exit.

W22018 updates SAS Merchandise Intelligence Plug-in for SAS Management Console 5.4

NONE

Z33014 updates SAS Merchandise Intelligence Server 5.4

Run the Update Data Mart Script

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

1. Log on as MI ETL User (sasmi).
2. From the SASMI HOME directory, run the update_datamart script.
/install/SASInstall_SO34/SASConfig/Lev1/Applications/SASMerchIntellServer5.4/sas/update_datamart.sh
3. Check the log file (update_datamart_YYYYMMDD_HHMM.log) in the same directory for output and any errors.

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 May 8, 2012, at 9:44 a.m.:
update_datamart_20120508_0944.log

Note: This hot fix makes ALL of the following schema changes detailed below. For details, see the Administrator's Guide.

RDBMS changes:

Two new columns are added to the table DI_TRANS.PRF_PROFILE
ALTER TABLE PRF_PROFILE ADD PROFILE_STATUS_CD INTEGER;
ALTER TABLE PRF_PROFILE ADD PROFILE_UPDATED_DTTM DATE;

SAS changes:

1. The stage table 'STG_PROFILE' is modified to apply datetime informat to STG_PROFILE.PUBLISHED_DT column.

2. Columns dropped from the table - SO_VAAR_REPORTS:
a. PARTITION_FLG
b. PROD_PARTITION_LEVEL
c. SUB_START_DT
d. NO_OF_WEEKS_FRM_SUB_START_DT

3. Column added in the table - SO_VAAR_REPORTS:
PROJECT_SKS

4. The following parameters are added in the DI_MON library's JOB_PARAM table -
a. ETLP_UPDATE_CLOSING_DT_WITH_NULL
b. FORMAT_LOCATION

5. The following global parameters are added in GLOBAL_SETTINGS table –
a. PLAN_MAXIMUM_ORDER_THRESHOLD
b. PLAN_MINIMUM_ORDER_THRESHOLD

These new Global setting parameters have been added to control the default values that appear in the Purchase Order Plan Properties/General Settings screens in the user interface.

They should be used in tandem with your existing global settings MAXIMUM_ORDER_THRESHOLD and MINIMUM_ORDER_THRESHOLD where those existing parameters control the default values that appear in the “Request Settings' tab in the BUY/DELIVERY properties pages.

6. A new Global Setting with a default value of 0 is added to adjust the DC Split logic.
proc sql noprint;
insert into di_dm.global_setting values ('IGNORE_DC_IN_REPAIR', 'ALL', '0', null);
quit;

REQUIRED MANUAL STEPS

This change was introduced by Hot Fix W19013 and is only required to be done once. If you have previously applied Hot Fix W19013 please skip this section.

To be done after running the update_datamart.sh:

1. Job_Param table changes (in library DI_MON):

PARAM_VALUE needs to be updated with the full path name of the SASFormats folder where the PARAM_NAME is equal to FORMAT_LOCATION.
Example - : /install/SASConfig/Lev1/MIMain/SASEnvironment/SASFormats
proc sql noprint;
delete * from di_mon.job_param where jobname = 'DI_UTIL_CUSTOM_SORT_FORMAT';
insert into di_mon.job_param
(jobname, param_name, param_value, default_func)
values("DI_UTIL_CUSTOM_SORT_FORMAT", "FORMAT_LOCATION", "/sas/config/Lev1/MIMain/SASEnvironment/SASFormats", '""' );
quit;

Please change the value "/sas/config/Lev1/MIMain/SASEnvironment/SASFormats" to the location specific to the customer.

2. Folder permission of SASFormats folder table should be changed to 775 for user SASMI

3. Delete all the old extracts generated
a. Go to the location <DI_DM>/so_reports
b. Execute the command
– rm SZPF_EXTRACT_*
This should delete all the extracts generated before the hotfix. User should regenerate the reports after installing the new hotfix.

W20018 updates SAS Merchandise Intelligence Workbench Server 5.4

NONE

Z35008 updates SAS Pack Optimization Mid-Tier LASR Configuration 3.4

NONE

A9K005 updates SAS Pack Optimization Server 3.4

NONE

Z36008 updates SAS Size Profiling Mid-Tier LASR Configuration 3.4

NONE

Y07015 updates SAS Size Profiling Server 3.4

The Hotfix adds below mentioned Global_settings:

PROFILE_SELECTION_FLG
PARENTDIFFSALES
PERSIZESATISFYFSTTHR
CHILD_PREFERENCE