Installation Instructions for Hot Fix S63001

HP-UX IPF


Hot fix S63001 addresses the issue(s) in SAS Compliance Solutions 6.2_M1 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/S63.html#S63001


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

S62001  updates  SAS Compliance Solutions Mid-Tier 6.2_M1
R77003  updates  SAS Compliance Solutions Server 6.2_M1

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

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


INSTALLATION

Hot Fix S63001 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 Compliance Solutions 6.2_M1 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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 S63001pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.


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.

S62001  updates  SAS Compliance Solutions Mid-Tier 6.2_M1
R77003  updates  SAS Compliance Solutions Server 6.2_M1


S62001  updates  SAS Compliance Solutions Mid-Tier 6.2_M1

Important Note: For ease of completion of post-installation tasks, you can export the following:

export SASHOME=/install/SASHome This should be the path that SAS was installed to.
export SASCONFIG=/install/config/Lev1 This should be the path that SAS was deployed/configured to.
export FCFMIDROOT=$SASCONFIG/Web/Applications/SASComplianceSolutions6.2
Copy the following files from $SASHOME/SASComplianceSolutionsMidTier/6.2 to $FCFMIDROOT/install/uidef, removing the '.orig' extension:
deploy/uidef/aml-alert-details-01.xml.orig
deploy/uidef/aml-available-alerts-01.xml.orig
deploy/uidef/aml-closed-alerts-01.xml.orig
deploy/uidef/aml-fin-rr-01.xml.orig
deploy/uidef/aml-my-alerts-01.xml.orig
deploy/uidef/aml-risk-assessment-details-01.xml.orig
deploy/uidef/aml-suppressed-alerts-01.xml.orig
deploy/uidef/cdd-case-details-01.xml.orig
deploy/uidef/fcf-customer-details-01.xml.orig
Make the following token substitutions in the same files:
@fcf.software.component.name@=Compliance Solutions Mid 6.2
@war.context.name@=SASComplianceSolutionsMid
Edit the aml-available-alerts-01.xml file and find this section of code that relates to all available alerts:

<set name="TEMP.GRID_DATA_EXPR"
value="'C_GetSASDataAsMapList( \'fcf_get_ecm_entities_sp\',
\'INCIDENT\',
\'query_type=AA_ALERTS\',
\'incident_types="AMLALT"\',
Concat( \'user_id=\', getUserId() ),
Concat( \'user_groups=\', C_GetCurrentUserGroups() ),
Concat( \'party_rk=\', C_GetSelectedDataGridItem( \'CUST_GRID\', \'PARTY.PARTY_RK\' ) ),
\'number_of_records=999\' )'"/>

Remove this line:
Concat( \'party_rk=\', C_GetSelectedDataGridItem( \'CUST_GRID\', \'PARTY.PARTY_RK\' ) ),

This hot fix requires that the WebApps be rebuilt and redeployed. Use the following steps to perform this post-installation task:

Step 1: Re-build Web Applications

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

1.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 the following WebApps:

SAS Compliance Solutions Mid 6.2

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 ear files in <SASCONFIGDIR>/Web/Staging.
A backup of the original ear files will be placed in the directory below:

<SASCONFIGDIR>/Web/Staging/Backup

Step 2: Re-deploy Web Applications

Re-deploy the web applications based on the instructions for the web application server you are using.

2.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.4
2.2 Select a language in the Choose Language box

2.3 Select Deploy Web Applications

2.4 Select Configuration Directory or Enter the Configuration Directory and Level that needs to be updated

2.5 Specify Connection Information, including the sasadm User ID and Password

2.6 Select the following WebApps:

SAS Compliance Solutions Mid 6.2
2.7 Verify the information on the Summary screen and select Start

2.8 Select Finish when the deployment is complete

Upload UI Definitions:

After rebuilding the web applications, start all servers. Wait until they are running, then complete the following steps:

  1. Log into the SAS Enterprise Case Management application as an administrator user

  2. Open the Administration->UI Definitions menu.

  3. Upload the following files:
    $FCFMIDROOT/install/uidef/aml-alert-details-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-available-alerts-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-closed-alerts-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-fin-rr-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-my-alerts-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-risk-assessment-details-01.xml.orig
    $FCFMIDROOT/install/uidef/aml-suppressed-alerts-01.xml.orig
    $FCFMIDROOT/install/uidef/cdd-case-details-01.xml.orig
    $FCFMIDROOT/install/uidef/fcf-customer-details-01.xml.orig
  4. Choose the Administration->Clear Cache menu item.

  5. Log out of the application and reconnect.


R77003  updates  SAS Compliance Solutions Server 6.2_M1

Important Note:

For ease of completion of post-installation tasks, you can export the following:

export SASHOME=/install/SASHome This should be the path that SAS was installed to.
export SASCONFIG=/install/config/Lev1 This should be the path that SAS was deployed/configured to.
export FCFROOT=$SASCONFIG/Applications/SASComplianceSolutions6.2
Copy the following file from $SASHOME/SASFoundation/9.4 to $FCFROOT/custom/config:
misc/antimnycmn/deploy/fcf_autoexec.sas
Make the following token substitutions in the file above. You should merge it with a backup of your previous fcf_autoexec.sas, because there are a lot of settings that need to be the same as before. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@iomsrv.metadatasrv.host@={metadata tier host name}
@iomsrv.metadatasrv.port@={metadata port, usually 8561}" />
@oma.repository.foundation.name@={metadata repository name, usually “Foundation”}
@install.cmacros.dir@=$SASCONFIG/SASFoundation/9.4/cmacros/antimnycmn
@custsrc@=$FCFROOT/custom/source
@fcfroot@=$FCFROOT
@cmnroot@=$FCFROOT
@fcfdata@=$FCFROOT/data
@fcfland@=$FCFROOT/landing
@sysadmin.email@=%LET sysadmin=sysadmin@mycompany.com;
@agp.mlrisk@=1000
@agp.tfrisk@=1000
@agp.scoring.duration@=31
@agp.replicate.suppressed.alerts@=N
@agp.autoroute@=Y
@authdomain@=DefaultAuth
@dbms.engine"@={database engine, which can be oracle, odbc, db2, or teradata}
@dbms.mode@={remove this token, replacing it with nothing, unless your configuration had it before}
@dbms.kc.schema@=FCFKC
@dbms.kc.userid@=FCFKC
@dbms.kc.connopts@={database connection options, for example "path=dbserver"}
@dbms.libopts@={remove this token, replacing it with nothing, unless your configuration had it before}
@dbms.segkc.schema@=FCFBU1
@dbms.segkc.userid@=FCFBU1
@dbms.segkc.connopts={database connection options, for example "path=localdb"}
@dbms.core.schema@=FCFCORE
@dbms.core.userid@=FCFCORE
@dbms.core.connopts@={database connection options, for example "path=localdb"}
@default.locale@=en
@ecm.db.conopts@=%str({database connection options, for example "path=localdb"}
@custfmt@=$FCFROOT/custom/fmts
@jobstat@=$FCFROOT/jobstats
@cmndata@=$FCFROOT/data
@fcf.software.component.name@="Compliance Solutions Mid 6.2"
@fcf.install.ucmacros.dir@=$SASHOME/SASFoundation/9.4/ucmacros/antimnycmn
@install.xml.map@=$SASHOME/SASFoundation/9.4/misc/antimnycmn/xml/map
@source_system_cd@=FCFBU1;
Copy the following files from $SASHOME/SASFoundation/9.4 to $FCFROOT/install:
misc/antimnycmnc/deploy/xml/aml_sa_create_request_ar.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_es.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_fr.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_it.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_ja.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_ko.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_nl.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_ru.xml
misc/antimnycmnc/deploy/xml/aml_sa_create_request_zh_CN.xml
In the files, replace the token @segment_id@ with 'FCFBU1' or the Business Unit schema name, if different.

Copy the following files from /SASFoundation/9.4 to $FCFROOT/sasstp, removing the '.orig' extension from each:

sasstp/antimnycmn/cdd_attribute_score.sas.orig
sasstp/antimnycmn/cdd_case_details.sas.orig
sasstp/antimnycmn/cdd_category_score.sas.orig
sasstp/antimnycmn/cdd_overall_score.sas.orig
sasstp/antimnycmn/cdd_scoring_trend.sas.orig
sasstp/antimnycmn/fcf_get_ecm_entities_sp.sas.orig
sasstp/antimnycmn/fcf_init.sas.orig
sasstp/antimnycmn/fcf_list_cases.sas.orig
Make the following token substitutions in those files. Be sure to fully expand any environment variables like SASHOME and SASCONFIG:
@ecm.autoexec.path@=$SASCONFIG/Applications/SASEnterpriseCaseManagement/6.2/Source/control/ecm_autoexec.sas
@aml.autoexec.path@=$SASCONFIG/Applications/SASComplianceSolutions6.2/custom/config/aml_autoexec.sas
@nefs@=/ (should be a forward slash for UNIX; a backslash for Windows)
@fcf.stp@=$SASCONFIG/Applications/SASComplianceSolutions/sasstp
@fcf.software.component.name@=Compliance Solutions Mid 6.2
@fcf.autoexec.path@=$SASCONFIG/Applications/SASComplianceSolutions6.2/custom/config/fcf_autoexec.sas


Copy the following files from from $SASHOME/SASFoundation/9.4/samples/antimnycmn to $SASCONFIG/Applications/SASComplianceSolutions6.2/custom/source

fcf_sa_ecm_ui_data.sas
fcf_stp_ecm_ui_response.sas
fcf_write_ecm_ui_xml_data.sas

Leveraging the Compliance Solutions 6.2 S63001 update

In order to leverage the updates provided by this hot fix, please read the following document:

Additional Documentation

This completes the installation of hot fix S63001 on HP-UX IPF.