Installation Instructions for Hot Fix M2Q003

Windows for x64

Hot fix M2Q003 addresses the issue(s) in SAS Infrastructure for Risk Management 3.7 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/M2Q.html#M2Q003

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

M2P003  updates  SAS Infrastructure for Risk Management Mid-Tier 3.7
M2M001  updates  SAS Infrastructure for Risk Management Server 3.7
M2N003  updates  SAS Infrastructure for Risk Management Server Configuration 3.7

Before applying this hot fix, follow the instructions in SAS KB0036131 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, M2Q003pt.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 M2Q003pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of M2Q003pt.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.

PRE-INSTALLATION INSTRUCTIONS

1. On the Midtier machine - open the file
   <SASConfig>\Lev1\Web\WebAppServer\SASServer8_1\sas_webapps\sas.insuranceriskmanagementserver.war\WEB-INF\picklist
   and search the file for the line:
   

   name=sas.solutions.risk.irm.server
   

   Below this line you will find the version number of sas.solutions.risk.irm.server jar file. For example:
   

   version=307001.8.0.20240809091900_f0irm37p

2. Go to the folder <SASHome>\SASVersionedJarRepository\eclipse\plugins and search for the sas.solutions.risk.irm.server jar that matches the version number.
   For example:
   

   sas.solutions.risk.irm.server_307001.8.0.20240809091900_f0irm37p

   Remove this file from the folder or move it to a different archive folder.

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

1. Run the SAS Infrastructure for Risk Management post-installation task automation tool.
   For detailed instructions, go to the SAS Infrastructure for Risk Management 3.7 Administrator's Guide.
   
   
   1. Ensure that all servers are stopped except the Web Infrastructure Platform Data Server.
      
   2. Ensure you are logged in to the SAS Infrastructure for Risk Management server machine as the SAS Installer account.
      
   3. Execute the following command (updated for your deployment) to complete the post-installation tasks:
   
   <SASHome>\SASPrivateJavaRuntimeEnvironment\9.4\jre\bin\java -cp <SASHome>\SASVersionedJarRepository\eclipse\plugins\sas.solutions.risk.irm.server_307001.8.0.20240809091900_f0irm37p.jar com.sas.solutions.risk.irm.server.utils.IRMHFHelper -home <SASHome> -config <SASConfig> -dbuser <IRM_db_user > -dbpassword <IRM_db_user_pw>
   
   Values in angle brackets <> above denote user-replaced values.
   
   Other optional parameters may be required if your install differs from the default install values in the SAS Deployment Wizard®. The SAS Infrastructure for Risk Management 3.7 Administrator's Guide provides more details.

2. Update and merge the IRM logging configuration file.
   
   This fixes an issue with the log file size and logging entry formatting.
   
   
   1. Make a backup of the existing configuration files.
      1. cd <SASConfig>\Lev1\Web\Common\LogConfig
         
      2. copy SASIRM-log4j2.xml SASIRM-log4j2.xml.bak
         
      3. copy SASIRMServer-log4j2.xml SASIRMServer-log4j2.xml.bak
      
      
   2. Copy the new configuration files installed by the hot fix.
      
      
      1. cd <SASConfig>\Lev1\Web\Common\LogConfig
      2. copy <SASHome>\SASInfrastructureforRiskManagementMidTier\3.7\Configurable\logging\SASIRM-log4j2.xml.orig SASIRM-log4j2.xml
      3. copy <SASHome>\SASInfrastructureforRiskManagementMidTier\3.7\Configurable\logging\SASIRMServer-log4j2.xml.orig SASIRMServer-log4j2.xml
      
      
   3. This will reset the logging configuration to its defaults. If different settings are desired, you can merge the changes into the configuration files using the backup files as a reference.
      
      
   4. Delete the unused log configuration files.
      1. cd <SASConfig>\Lev1\Web\Common\LogConfig
      2. del SASIRM-log4j.xml
      3. del SASIRMServer-log4j.xml

3. Hot Fix Post Installation steps to Rebuild and Redeploy Web Applications

   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.

      Select the appropriate product as the Web Application to Rebuild

   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 updated wars to the web application server.

4. Apply Python changes to the platform federated area
   
   1. Copy file irm_exec_pytask.py
      from
          <SASHome directory>\SASFoundation\9.4\rmifirmmva\sasmisc\fa.0.3.7\source\python\nodes
      to
      the SAS Infrastructure for Risk Management platform FA replacing the old file.
          <SAS Config directory>\Lev1\AppData\SASIRM\fa.0.3.7\source\python\nodes\
      

   2. Copy "irm-3.7-py2.py3-none-any.whl" (with md5 checksum 411f18be509546992c6a97a129f6b3db)
      from
          <SASHome directory>\SASFoundation\9.4\rmifirmmva\sasmisc\fa.0.3.7\client_packages
      to
      the SAS Infrastructure for Risk Management platform federated area folder
         <SAS Config directory>\Lev1\AppData\SASIRM\fa.0.3.7\client_packages.

   3. Restart the SAS Infrastructure for Risk Management midtier

5. All Python developers will need to update the wheel package on their local machine:
   
   1. Uninstall the SAS Infrastructure for Risk Management wheel package in the local machine by using pip: pip uninstall irm

   2. Reinstall the SAS Infrastructure for Risk Management wheel package by following the instructions in
      Download the SAS Infrastructure for Risk Management Wheel Package

6. After applying the hot fix customers running a large number of parallel cycles might still encounter issues. Hence, the following configuration parameters need to be set, depending on the site hardware.
   1. Increase the JVM heap size and http connections in the JVM_OPTS parameter list in the wrapper.conf file for SASServer8_1. After implementing the JVM parameter perform a restart of the SASServer8_1 for the changes to be in effect.

             -Dsas.svcs.http.max.total.connections=1024
             -Dsas.svcs.http.max.connections=1024
             -Xss should be set to 256k
             - Increase JVM heap -Xmx and -Xms value to 12G or 12288M
      

   2. Add the following parameters in SAS IRM Mid-Tier Server. Go to

      SAS Management Console -> Expand Application Management -> Expand Configuration Manager -> Expand SAS Application Infrastructure ->

             com.sas.solutions.risk.irm.gemfire.lock-lease=600
             com.sas.solutions.risk.irm.gemfire.lock-timeout=240
             com.sas.solutions.risk.irm.gemfire.search-timeout=1200
      

   3. Increase max_connections to 2000 in the following Postgres Database Server configuration section as mentioned below. Find the postgres configuration file in the following path on the machine where Postgres Database services are running.

      <SASConfig>\Lev1\RiskGovernanceFrameworkDataServer\data\postgresql.conf
      <SASConfig>\Lev1\WebInfrastructurePlatformDataServer\data\postgresql.conf
      

             ## postgresql.conf ##
             #------------------------------------------------------------------------------
             # CUSTOMIZED OPTIONS
             #------------------------------------------------------------------------------
             # Add settings for extensions here
             max_connections = 2000
      

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


Copyright SAS Institute Inc. All Rights Reserved.