Hot fix D4Z024 addresses the issue(s) in SAS Risk Governance Framework 7.4 as documented
in the Issue(s) Addressed section of the hot fix download page:
https://tshf.sas.com/techsup/download/hotfix/HF2/D4Z.html#D4Z024
D4Z024 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
D6X023 updates SAS Risk Governance Framework Administrative Tools 7.4
D5B023 updates SAS Risk Governance Framework Mid-Tier 7.4
D5A011 updates SAS Risk Governance Framework Server 7.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, D4Z024pt.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 D4Z024pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of D4Z024pt.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 D4Z024pt.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 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.
D6X023 updates SAS Risk Governance Framework Administrative Tools 7.4
D5B023 updates SAS Risk Governance Framework Mid-Tier 7.4
D5A011 updates SAS Risk Governance Framework Server 7.4
D6X023 updates SAS Risk Governance Framework Administrative Tools 7.4
a. extractContent.cmd
b. extractContent.config
c. removeWorkflowInstances.cmd
d. removeWorkflowInstances.config
e. unregistercontent.cmd
f. unregistercontent.config
h. migrateWorkflowInstances.cmd
a. Workflows.csv
b. Workflows.mappings.config
c. NamedListOptions.csv
d. NamedListOptions.mappings.config
a. Change directories to <SASCONFIGDIR>\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\dbscripts\<db_vendor>
where <db_vendor> is the vendor used for the RGF database, either “PostgreSQL”, “Oracle”, or “MSSQLServer”.
b. Make a backup of DropViews.sql, InitDBVersion.sql and CreateTables.sql
i. copy DropViews.sql DropViews.sql.bak
c. Copy the updated files from <SASHOME>\SASRiskGovernanceFrameworkAdministrativeTools\7.4\dbscripts\<db_vendor>
ii. copy InitDBVersion.sql InitDBVersion.sql.bak
iii.copy CreateTables.sql CreateTables.sql.bak
where <db_vendor> matches the path from step (a). The other vendor directories can be ignored.
i. copy <SASHOME>\SASRiskGovernanceFrameworkAdministrativeTools\7.4\dbscripts\<db_vendor>\DropViews.sql
ii. copy <SASHOME>\SASRiskGovernanceFrameworkAdministrativeTools\7.4\dbscripts\<db_vendor>\InitDBVersion.sql
iii. copy <SASHOME>\SASRiskGovernanceFrameworkAdministrativeTools\7.4\dbscripts\<db_vendor>\CreateTables.sql.orig
iv. rename CreateTables.sql.orig CreateTables.sql
a. removeWorklfowInstances.cmd
b. migrateWorklfowInstances.cmd
D5B023 updates SAS Risk Governance Framework Mid-Tier 7.4
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.
a. Make a backup of the “picklist” file for the SAS Risk Governance Framework web application in
<SASHOME>\SASRiskGovernanceFrameworkMidTier\7.4\Picklists\wars\sas.riskgovernanceframework. Name it picklist.bak.
b. Edit the “picklist” file in that directory. Do not edit “picklist.full”.
c. Remove the following entry. Note that the version number might differ in your environment. Leave two blank lines between the surrounding entries.name=Log4J2d. Save the picklist file.
version=2.17.1.0_SAS_20220104134706
a. cd <SASHOME>\SASRiskGovernanceFrameworkMidTier\7.4\Static\wars\sas.riskgovernanceframework\resources
b. move ckeditor ..\..\..\ckeditor.bak
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
Redeploy the updated wars to the web application server.
To satisfy updates delivered in this hotfix you must specify the following JVM option in the setenv.bat or sasenv.sh file.
These files are found in the directory below:
SAS-configuration-directory/Levn/Web/WebAppServer/SASServer1_1/binUpdate the file to include the JVM option:
-Dcom.sas.workflow.shortTextMaxLength=1000
After the web application servers are restarted, complete the following steps
a. listCustomFields.groovy
b. list_enums.groovy
c. groovyEditor.groovy
d. migrateattachments.groovy
e. purgeObjects.groovy
org.apache.struts.util.LabelValueBean -> com.sas.oprisk.framework.server.util.LabelValueBean
org.apache.struts.action.ActionMessage -> com.sas.oprisk.framework.server.util.ActionMessage
org.apache.struts.action.ActionMessages -> com.sas.oprisk.framework.server.util.ActionMessages
a. Locate the file SaveRefreshBEPData.groovy file on the SAS Content Server, under the folder
/SASContentServer/repository/default/sasdav/Products/SASRiskGovernanceFramework/RiskGovFrwkMid-Tier/rmc/Scripts/customfunctions/html5Ui/
b. Edit the file, and change the method setDefaults on line 216, so that it has two arguments, where the first one is “IContext context”:
From:
def setDefaults = {JSONObject bepData ->
To:
def setDefaults = { IContext context, JSONObject bepData ->
c. Change the calls to setDefaults on lines 85 and 126 so that they passes the additional argument:
From:
setDefaults(bepData);
To:
setDefaults(context,bepData);
d. Save the groovy file to the content server.
a. Change directories to <SASCONFIGDIR>\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\dbscripts
b. Run the patchdb utility for each installed content package (mrm, gcm, rmc, etc.), using the following command, and apply the patch:
PostgreSQL, MSSQL: patchdb.cmd -c <content_id>
Oracle: patchdb.cmd -c <content_id> <index_tablespace>
where <index_tablespace> is the tablespace containing the RGF database indexes,
for example RGFIDX_1
a. Change directories to <SOLRHOME>\bin and run the following command to stop SOLR.
solr stop -p 8983
b. Change directories to <SOLRHOME>\server\solr\rgf\conf and run the following to command to backup managed-schema
copy managed-schema managed-schema.bak
c. Copy the new managed-schema from <SASHOME> directory to the SOLR configuration directory.
copy <SASHOME>\SASRiskGovernanceFrameworkMidTier\7.4\Config\Samples\Solr\managed-schema <SOLRHOME>\server\solr\rgf\conf
d. Change directories to <SOLRHOME>\bin and run the following command to start SOLR.
solr start -p 8983 -m <mem_size>
e. Change directories to <SASCONFIGDIR>\Lev1\Applications\SASRiskGovernanceFrameworkAdministrativeTools\dbscripts and update the SOLR search index for each installed content package, where content_id is “mrm”, “gcm”, “rmc”, etc.
updateindex.cmd -c <content_id>
D5A011 updates SAS Risk Governance Framework Server 7.4
%SMD2DS(DIR=<SASHOME>\SASFoundation\9.4\rskmgtsvr\smd, BASENAME=rskmgtsvr, LOCALE=en, lib=SASHELP);*NOTE: Be sure to run the above SAS code in the same SAS session encoding that was used when the product was installed and configured.
<SASHOME>\SASFoundation\9.4\rskmgtsvr\ucmacros\rgf_post_init.sas.orig
<SASHOME>\SASFoundation\9.4\rskmgtsvr\sasmisc\control\grid_host.map
<SASHOME>\SASFoundation\9.4\rskmgtsvr\ucmacros\rgf_job_load_audit_data.sas
<SASHOME>\SASFoundation\9.4\rskmgtsvr\ucmacros\rgf_job_reload_audit_data.sas
<SASHOME>\SASFoundation\9.4\rskmgtsvr\ucmacros\rgf_job_reload_data.sas
to
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas.orig
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\sasmisc\control\grid_host.map
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_job_load_audit_data.sas
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_job_reload_audit_data.sas
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_job_reload_data.sas
From: rgf_post_init.sas
To: rgf_post_init.sas.old
A) Using a text editor, replace the tokens in the files with the paths listed below:
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas.orig
Token: @CNTLFILEDIR@
Path: <SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\sasmisc\control
B) Copy the lines below in "<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas.old"
Example:
%let rskmgt_dbserver=%upcase(PostgreSQL);
%let rskmgt_dbengine=%upcase(POSTGRES);
%let rskmgt_dbName=rgfdbname;
%let rskmgt_dbAuth=RGF_db_auth;
%let rskmgt_dbServerNm=xxx.abc.com;
%let rskmgt_dbport=1001;
and overwrite the following lines in "<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas.orig"
%let rskmgt_dbserver=%upcase(@DBMS_TYPE@);
%let rskmgt_dbengine=%upcase(@DBENGINE@);
%let rskmgt_dbName=@DBIDENTIFIER@;
%let rskmgt_dbAuth=@DBMS_AUTH@;
%let rskmgt_dbServerNm=@DBMS_SERVER@;
%let rskmgt_dbport=@DBMS_PORT@;
C) Save the changes to the file.
D) Rename
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas.orig
to
<SASCONFIGDIR>\Lev1\AppData\SASRiskGovernanceFramework\Source\ucmacros\rgf_post_init.sas
to remove the ".orig" file suffix.
This completes the installation of hot fix D4Z024 on Windows for x64.
Copyright 2023 SAS Institute Inc. All Rights Reserved.