Installation Instructions for Hot Fix B5C009

Linux for x64

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

B5A008  updates  SAS Infrastructure for Risk Management Mid-Tier 3.4
B5B002  updates  SAS Infrastructure for Risk Management Server 3.4
B5D008  updates  SAS Infrastructure for Risk Management Server Configuration 3.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, B5C009pt.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 B5C009pt.zip on each machine or save it in a network location that is accessible to all machines.

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

IMPORTANT NOTES

1. 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.

2. You must have Administrator Privileges on your CLIENT or SERVER machine.

3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

4. This hot fix should be installed using the same userid who performed the initial software installation.

5. CONFIGURATION: No automatic configuration scripting is included 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.

INSTALLATION

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 B5C009pt.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

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.

B5A008  updates  SAS Infrastructure for Risk Management Mid-Tier 3.4
B5B002  updates  SAS Infrastructure for Risk Management Server 3.4
B5D008  updates  SAS Infrastructure for Risk Management Server Configuration 3.4

B5B002  updates  SAS Infrastructure for Risk Management Server 3.4

1. Navigate to the <SASHome>/SASFoundation/9.4/misc/rmifirmmva/fa.0.3.4/source/sas/ucmacros directory

2. Copy the following files

   irm_filter_data_by_flow.sas
   irm_get_child_parent_entity.sas

   to

   <SASConfig>/LevX/AppData/SASIRM/fa.0.3.4/source/sas/ucmacros

3. Navigate to the <SASHome>/SASFoundation/9.4/misc/rmifirmmva/fa.0.3.4/source/sas/smd directory

4. Copy irmplatmsg.smd to

   <SASConfig>/LevX/AppData/SASIRM/fa.0.3.4/source/sas/smd directory

   
   

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.

1. Rebuild Web Applications

   NOTE: In order for this step to execute correctly, the Metadata Server must be running.

   Rebuild the SAS Infrastructure for Risk Management Mid-Tier 3.4 web application

2. Re-start all SAS sessions, daemons, spawners and servers.
   For more information on the proper order for starting servers, go to SAS® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition and review the section entitled "Starting, Stopping and Checking the Status of Servers".

3. Redeploy Web Applications

   Redeploy the SAS Infrastructure for Risk Management Mid-Tier 3.4 web application to the web application server.

4. Using pgAdmin, execute the following SQL statements to update the SAS Infrastructure for Risk Management Postgres database:

   alter table DATA_OBJ add column MV_NAMES character varying(255);
   alter table DATA_OBJ add column MV_VALUES character varying(255);

   
   The database user is listed in the IRM Database Users group in SAS Management Console.

5. Copy updated jar and files to Federated Area
   1. Navigate to the <SASHome>/SASVersionedJarRepository/eclipse/plugins/ directory

   2. Copy the following jars

      sas.solutions.risk.irm.server_304001.18.0.20190219121000_f0irm34.jar
      sas.solutions.risk.irm.mid.nls_304001.1.0.20180919081800_f0irm34.jar
      sas.solutions.risk.irm.mid_304001.1.0.20180919081800_f0irm34.jar
      sas.solutions.risk.irm.server.nls_304001.1.0.20180116090300_f0irm34.jar
      to
      <SASConfig>/LevX/AppData/SASIRM/fa.0.3.4/source/java/lib

6. Clean up configuration area by deleting old jars

   1. Navigate to the <SASConfig>/LevX/AppData/SASIRM/fa.0.3.4/source/java/lib directory

   2. Delete any of the following files that exist:

      sas.solutions.risk.irm.server_304000.3.0.20170906190000_d4irm34.jar
      sas.solutions.risk.irm.server.nls_304000.1.0.20170823190000_d4irm34.jar
      sas.solutions.risk.irm.server_304001.3.0.20171012094400_f0irm34.jar
      sas.solutions.risk.irm.server_304001.8.0.20180108091300_f0irm34.jar
      sas.solutions.risk.irm.server_304001.11.0.20180117135600_f0irm34.jar
      sas.solutions.risk.irm.server_304001.13.0.20180523123500_f0irm34.jar
      sas.solutions.risk.irm.server_304001.15.0.20180713104500_f0irm34.jar
      sas.solutions.risk.irm.server_304001.16.0.20180814142500_f0irm34.jar
      

7. Copy IOJavaLauncher.class
   from:
   <SASConfig>/Lev1/AppData/SASIRM/fa.0.3.4/source/java/lib/sas.solutions.risk.irm.server_304001.18.0.20190219121000_f0irm34.jar/com/sas/solutions/risk/irm/server/io/remote
   to:
   <SASConfig>/LevX/AppData/SASIRM/fa.0.3.4/source/java/bin/com/sas/solutions/risk/irm/server/io/remote
   
   Note:
   You can use an unzip tool to view the contents of sas.solutions.risk.irm.server_304001.18.0.20190219121000_f0irm34.jar and copy the IOJavaLauncher.class.

8. Restart the SAS Infrastructure for Risk Management Web Application Server

B5D008  updates  SAS Infrastructure for Risk Management Server Configuration 3.4

NONE

This completes the installation of hot fix B5C009 on Linux for x64.


Copyright 2019 SAS Institute Inc. All Rights Reserved.