T04017 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
T10018 updates SAS Enterprise GRC Administrative Tools 6.1
T11017 updates SAS Enterprise GRC Mid-Tier 6.1
Y02004 updates SAS Enterprise GRC Server 6.1
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, T04017pt.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 T04017pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of T04017pt.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 T04017pt.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.
T10018 updates SAS Enterprise GRC Administrative Tools 6.1
T11017 updates SAS Enterprise GRC Mid-Tier 6.1
Y02004 updates SAS Enterprise GRC Server 6.1
T10018 updates SAS Enterprise GRC Administrative Tools 6.1
Perform the following steps to ensure the administrative tools are running with the latest updates.
to
<SASCONFIGDIR>/Lev1/Applications/ SASEnterpriseGRCAdminTools/6.1/dbscripts/picklist
and overwrite the current contents.
T11017 updates SAS Enterprise GRC Mid-Tier 6.1
This hot fix requires that the WebApp be rebuilt and redeployed. Use the following steps to perform this post-installation task:
Step 1: Re-build Web ApplicationClean up the Application Server cache. Please contact your Administrator for detail steps specific to your application server.In order for this step to execute correctly, the Metadata Server must be running.
1.1 Invoke the SAS Deployment Manager 9.4
From the SASDeploymentManager directory launch sasdm.sh.
SAS Deployment Manager is installed in the following default location: <SASHOME>/SASDeploymentManager/9.41.2 Select a language in the Choose Language box
1.3 Select Rebuild Web Applications
1.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated
1.5 Specify Connection Information, including the sasadm User ID and Password
1.6 Select Enterprise GRC MidTier 6.1 as the Web Application to Rebuild
1.7 Verify the information on the Summary screen and select Start
1.8 Select Finish when the deployment is complete
This process will update the Enterprise GRC MidTier 6.1 ear in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear file will be placed in the directory below:
<SASCONFIGDIR>/Web/Staging/Backup
Step 2: Re-deploy Web ApplicationsRe-deploy the web applications based on the instructions for the web application server you are using.
#{0}nodename
dataload.data.moveself.fmt.txt=Attempting to move an existing node {0} so that it will be a child of itself.
monitor.validation.modifyDataWithValidation=trueThe following behavior changes would happen only when this option is set to "true".
monitor.kri.canDeleteValidatedObservations.enabled=trueWhen this option is set to "true", customer can unload a fully validated observation, or delete an observation request with fully validated observation, so they can add a new observation request for the same period.
<field type="component" component-name="LinkedControlTable" name="linkedControl" required="true">There are 3 acceptable values for the new globalTester parameter: "ADDALL", "FORCE" and "EMPTYONLY". Once this parameter is set in TestDefinition.xml, and the configdata.properies option: "monitor.controlTesting.newTestsLocation" is set to "useTestDef", a new User chooser is available on the Controls table in Test Definition to select a Tester for all associated Controls to the current Test Definition.
<param name="statusFilter">APPROVED</param>
<param name="globalTester" value="'ADDALL'" />
</field>
# List of acceptable embedded urls.IMPORTANT: This option is enabled by default with the values shown above, even though it may not be shown in configdata.properties. After installing the HF, you must check your menu XML for any menu items with embed="true", append them to the default property values. For example:
# If urls start with / the context root is prefixed before checking
# Otherwise an exact match is used.
monitor.embed.whitelist=/CPBDocumentation?docType=COMPONENTS&topLevel=true,/CPBDocumentation?docType=FUNCTIONS&topLevel=true,/CPBDocumentation?docType=DIRECTIVES&topLevel=true,/CPBDocumentation?docType=PROPERTIES&topLevel=true
monitor.embed.whitelist=/CPBDocumentation?docType=COMPONENTS&topLevel=true, /CPBDocumentation?docType=FUNCTIONS&topLevel=true,/CPBDocumentation?docType=DIRECTIVES&topLevel=true, /CPBDocumentation?docType=PROPERTIES&topLevel=true,<menu-option1>,<menu-option2>Although not recommended, this option may be disabled altogether by setting monitor.embed.whitelist=OFF
monitor.query.canQueryOptimizationEnabled=true
By default, the optimization is off (false).
monitor.query.optimizeRecentTestsQuery=true
By default, the optimization is off (false).
monitor.query.optimizeRecentTestResultsQuery=true
By default, the optimization is off (false).
Y02004 updates SAS Enterprise GRC Server 6.1
The post install instructions in this document are needed if you want to
install and configure the new GRC sample Visual Analytics report. If
you do not wish to install
the new Visual Analytics report, you may skip Section 2 of the post
install instructions.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Section 1: Installation and Configuration of the GRC_Dashboards SAS Visual Analytics report
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
NOTE: If you are using SAS Visual Analytics reports as part of your EGRC reporting toolset, please proceed with this
section in order to get the new sample report for your environment.
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_apply_dim_path.sasTO:
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_db_connect.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_db_libname.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_filter_link_inst_tbl.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_actionplan_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_audit_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_cause_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_control_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_event_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_issue_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_kri_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_load_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_policy_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_reload_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_risk_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_risk_dash_scores.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_load_lasr_tbls.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_load_link_inst_tbl.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_lasr_perm_filter.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_get_cust_field_labels.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_pivot_datatype.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_prep_actionplan_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_prep_control_data.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_cert_progress.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_progress.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_results.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_status.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_key_risk_indicators.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_loss_matrix.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_risk_heatmap.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_apply_dim_path.sasNOTE: Once all files have been copied, rename all of the existing files in the “To” list from “.sas” to “.sas.old” and allfile extensions from ".sas.orig" to ".sas" by dropping the ".orig" file extension.If the file already exist, overwrite it.
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_connect.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_libname.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_filter_link_inst_tbl.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_actionplan_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_audit_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_cause_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_control_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_event_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_issue_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_kri_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_load_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_policy_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_reload_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_dash_scores.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_lasr_perm_filter.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_lasr_tbls.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_link_inst_tbl.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_get_cust_field_labels.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_pivot_datatype.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_actionplan_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_control_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_cert_progress.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_progress.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_results.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_status.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_key_risk_indicators.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_loss_matrix.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_risk_heatmap.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_libname.sasToken:
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_actionplan_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_audit_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_cause_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_control_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_event_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_issue_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_kri_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_load_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_policy_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_reload_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_link_inst_tbl.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_actionplan_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_control_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_cert_progress.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_progress.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_results.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_status.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_key_risk_indicators.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_loss_matrix.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_risk_heatmap.sas
%let orm_dbserver=%upcase(@ORMONCONFIG_DBMS_TYPE@);
%let orm_dbengine=%upcase(@ORMONITOR_DBENGINE@);
%let orm_dbName=@ORMONITOR_DBIDENTIFIER@;
%let orm_dbAuth=@ORMONCONFIG_DBMS_AUTH@;
%let orm_dbServerNm=@ORMONCONFIG_DBMS_SERVER@;
%let orm_dbport=@ORMONCONFIG_DBMS_PORT@;
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/reporting_parameters.txtTO:
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/features.txt
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/reporting_parameters.txt.bk
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/features.txt.bk
<SASHOME>/SASFoundation/9.4/misc/ormonitormva/control/reporting_parameters.txt
<SASHOME>/SASFoundation/9.4/misc/ormonitormva/control/features.txtTO:
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/reporting_parameters.txt
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/misc/control/features.txt
RISK,Numeric Assessment Measures,"'SEV','RES_RSK','DEMOEXPVAL','DEMOSEV'",The value column for this parameter should contain the numeric assessment measures required for reporting.B) features.txt changes (Line# 30):
RISK,Dropdown Assessment Measures,"'IND_1','LIKE_RSK','SEV_RSK','EXP_RSK','DEMOCUST','DEMOEMP','DEMOEXPSCALE','DEMOOVERALL','DEMOREG','DEMOSUPP','DEMOREP'",The value column for this parameter should contain the drop-down assessment measures required for reporting.
CONTROL,Dropdown Assessment Measures,"'ADE', 'EFF', 'EFFECTIVE_CNTL','DEMOCONTROL_DESIGN','DEMOCONTROL_EFFECTIVE'",The value column for this parameter should contain the drop-down assessment measures required for reporting.
# Issue Custom Field for GRC_Dashboard reportIn order to access and modify this file in your environment, see the following instructions for accessing the file:
issue.field.x_issue_days_pastdue.displayName.txt=# of Days Pastdue
issue.field.x_issue_type_cd.displayName.txt=Issue Category
A) Users.xls
B) Dimensions.xls
C) Positions.xls
D) CustFieldDefns.xls
E) NamedLists.xls
F) NamedListMappings.xls
G) NamedListTranslations.xls
H) Issues.xls
I) ActionPlans.xls
J) Measures.xls
K) ResponseScales.xls
L) Reference_Data.xls
M) KRIs.xls
N) ControlInstances.xls
O) TestDefinition.xls
P) TestPlans.xls
Q) TestResults.xls
R) Instances.xls
S) ObjectiveInstances.xls
T) OpRiskEvent.xls
U) FinancialImpact.xls
V) ImpactDetails.xls
W) FBA_Assessments.xls
X) IssueMappings.xls
Y) Policies.xls
Z) Audits.xls
AA) LinkInstances.xls
A) Open the SAS Management Console as a user account that is in the SAS Administrators Group.
B) Click on the Folders tab on the left side of the screen.
C) Right click on the "SAS Folders" Folder on the left side of the screen.
D) Click on "Import SAS Package".
E) For the "Enter the location of the input SAS Package file:", click on the browse button and navigate to the following directory and import the following file:
<SASHOME>/SASFoundation/9.4/misc/ormonitormva/Config/Deployment/Packages/EGRC_Load_Reload_Jobs.spk
F) Leave the "Import Options" and "Select objects to import" to their default values. Click on the Next button.
G) On the "Select Objects to Import" screen, click the Next button.
H) On the "About Metadata Connections" screen, click on the Next button.
I) On the "SAS Application Servers" screen, validate the SAS Application Servers "Target" value is set to "SASApp". If it is not, please change it to "SASApp" by using the drop down to change the value. Click Next.
J) On the "Scheduling Servers" screen, validate the "Target Server Name" is set to your "Operating System Services" server. If it is not set, click the drop down and select the server. Click Next.
K) On the "Deployment Directories" screen, validate the "Target" is set to "Ucmacros Directory". If it is not, click the drop down and select the "Ucmacros Directory".
L) On the "File Paths" screen, validate the "Target" names map to the "Original" names. If the Original and Targets do not match, change the "Target" to the correct path. The files should be located in <SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros. Click Next.
M) On the "Summary" screen, review your selections to ensure you have made the correct selections. If not, you can use the "Back" button to make changes. If your selections appear to be correct, click the Next button to update metadata with your selections.
N) Once complete, click the Finish button to close the window.
A) Open the SAS Management Console as a user account that is in the SAS Administrators Group.
B) Click on the Folders tab on the left side of the screen.
C) Right click on the "SAS Folders" Folder on the left side of the screen.
D) Click on "Import SAS Package".
E) For the "Enter the location of the input SAS Package file:", click on the browse button and navigate to the following directory and import the following file:
<SASHOME>/SASEnterpriseGRCMidTier/6.1/Config/Deployment/Packages/EGRC_VA_Dashboards.spk
F) Leave the "Import Options" and "Select objects to import" to their default values. Click on the Next button.
G) On the "Select Objects to Import" screen, click the Next button.
H) On the "About Metadata Connections" screen, click on the Next button.
I) On the "Tables" screen, validate the "Original" and "Target" values match. If not, click "Cancel" to exit the import screen and go back to step #14 in order to run the "Load All Data" job in order to create the LASR data sources. If the two match, click Next.
J) On the "Summary" screen, review your selections to ensure you have made the correct selections. If not, you can use the "Back" button to make changes. If your selections appear to be correct, click the Next button to update metadata with your selections.
K) Once complete, click the Finish button to close the window.
A) Logon to SAS EGRC.
B) Navigate to the Reports menu.
C) Under the reports menu, drill down into the Dashboards folder.
D) In the Dashboards folder, you should see a report called GRC_Dashboards.
E) Double click on this report to open it in the right pane in order to see the report.
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_apply_dim_path.sasTO:
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_db_connect.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_db_libname.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_filter_link_inst_tbl.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_actionplan_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_audit_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_cause_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_control_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_event_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_issue_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_kri_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_load_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_policy_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_reload_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_risk_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_job_risk_dash_scores.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_load_lasr_tbls.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_load_link_inst_tbl.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_lasr_perm_filter.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_get_cust_field_labels.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_pivot_datatype.sas
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_prep_actionplan_data.sas.orig
<SASHOME>/SASFoundation/9.4/ucmacros/ormonitormva/orm_prep_control_data.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_cert_progress.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_progress.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_results.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_ctltest_test_status.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_key_risk_indicators.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_loss_matrix.sas.orig
<SASHOME>/SASFoundation/9.4/sasstp/ormonitormva/orm_rpt_risk_heatmap.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_apply_dim_path.sasNOTE: Once all files have been copied, rename all of the existing files in the “To” list from “.sas” to “.sas.old” and all file extensions from ".sas.orig" to ".sas" by dropping the ".orig" file extension. If the file already exist, overwrite it.
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_connect.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_libname.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_filter_link_inst_tbl.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_actionplan_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_audit_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_cause_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_control_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_event_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_issue_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_kri_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_load_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_policy_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_dash_scores.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_lasr_perm_filter.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_lasr_tbls.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_link_inst_tbl.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_pivot_datatype.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_actionplan_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_control_data.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_cert_progress.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_progress.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_results.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_status.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_key_risk_indicators.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_loss_matrix.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_risk_heatmap.sas.orig
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_db_libname.sasToken:
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_actionplan_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_audit_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_cause_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_control_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_event_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_issue_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_kri_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_policy_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_load_link_inst_tbl.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_actionplan_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_prep_control_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_cert_progress.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_progress.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_results.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_ctltest_test_status.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_key_risk_indicators.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_loss_matrix.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/sasstp/orm_rpt_risk_heatmap.sas
%let orm_dbserver=%upcase(@ORMONCONFIG_DBMS_TYPE@);
%let orm_dbengine=%upcase(@ORMONITOR_DBENGINE@);
%let orm_dbName=@ORMONITOR_DBIDENTIFIER@;
%let orm_dbAuth=@ORMONCONFIG_DBMS_AUTH@;
%let orm_dbServerNm=@ORMONCONFIG_DBMS_SERVER@;
%let orm_dbport=@ORMONCONFIG_DBMS_PORT@;
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_actionplan_data.sasThe section of code that would need to comment out to turn off the import of the data into SAS Visual Analytics would look like the following in the files listed above:
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_audit_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_cause_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_control_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_event_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_issue_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_kri_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_policy_data.sas
<SASCONFIGDIR>/Lev1/Applications/SASEnterpriseGRCServerCfg/6.1/Source/ucmacros/orm_job_risk_data.sas
This completes the installation of hot fix T04017 on 64-bit Enabled AIX.
Copyright 2019 SAS Institute Inc. All Rights Reserved.