6.3 Upgrading from OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

This section describes how to upgrade from OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0.

Standalone Upgrade of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

Perform the Standalone Upgrade of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0 via, In-Place Upgrade and Cloning Upgrade.

Note:

  • Ensure to take the backup of File System (FIC_HOME and FTPSHARE), Atomic schema, and Config schema before performing the upgrade.
  • Ensure that you end all the batches before you start the upgrade process.
  • For enabling the unlimited Cryptographic Policy for Java, see Enabling Unlimited Cryptographic Policy for Java.
  • ORACLE_HOME AND JAVA_HOME have to be updated under FIC_HOME SUB DIRECTORIES while performing Inplace upgrade.
  • If CTR is not enabled in 8.1.1.0.0, 8.1.1.1.0 patch is applied. The below error can be ignored if it is observed.
    Query: 
    insert into CSSMS_ROLE_FUNCTION_MAP (V_ROLE_CODE, V_FUNCTION_CODE) values ('CTRADMN', 'AMPASENCYT')
    Error: ORA-02291: integrity constraint (AK7_811CONF.FK_CSSMS_ROLE_FUNCTION_MAP_2) violated - parent key not found.

In-Place Upgrade of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

Perform the In-Place upgrade of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0.

Prerequisites: For Inplace Upgrade, a minimum patch set level is required for performing OFS BD 8.1.1.0 to OFS BD 8.1.2.0.0.

For more information, see Oracle Financial Services Analytical Applications 8.1.2.0.0 Technology Matrix.

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • If user has different schema for FSDF, see the Configuring FSDF in Different Infodom (Pack on Pack Installation) section in Configuring FSDF before upgrading.
  • Before upgrade take backup of all STGSTG tables. Use the list of the STG tables (BD FSDF_OIDF Merged 81210 Staging Tables) and create SQL truncate script for truncating STG tables from BD atomic schema.
  • When truncating, ignore ORA errors for table not found.
  • The minimum BD patch level must be bug 33767914.

To upgrade:

  1. Download and unzip the OFS BD 8.1.2.0.0 Installer from My Oracle Support by using the bug 33940349 - OFS BD APPLICATION PACK - 8.1.2.0.0.
  2. Navigate to OFS_BD_PACK and grant execute (755) permission for all executables $ chmod 755 *.
  3. Navigate to installer/OFS_BD_PACK/ conf and update OFS_BD_PACK.xml. Select applications to enable. For more information, see Configuring OFS_BD_PACK.xml File.

    Note:

    Enter YES in ENABLE tag to enable applications which has been installed and Enter NO in the remaining applications.
  4. Modify PatchConfig.xml parameters under OFS_BD_PACK/OFS_AML/conf/PatchConfig.xml with appropriate values as described in the following table.

    Table 6-5 Modify PatchConfig.xml Parameters

    Placeholder Name Significance and Expected Value Mandatory
    ##OFS_AML_SW_RMIPORT## The Scenario Wizard uses this attribute. It must consist of a proper port number and not be used by any other application.

    For example, 7623 or 8204.

    		 Yes
    ##OFS_AML_SAVE_METADATA# The installer to decide whether to execute hierarchy. Resave uses this attribute. The applicable value is ALL. Yes
    ##EXECUTE_PRE_AND_POST_SCRIPTS## This flag indicates if certain scripts need to be executed just before and just after the data model upload Applicable value is 1. Yes (Value = 0)
    ##SCHEMA_OUT_ XML_PATH## This attribute refers to the path, which needs to be pointed to OFS_BD_ SCHEMA_OUTPUT.xml, which was generated at the time of installation.

    For example, /scratch/ofsaaapp/Installer/OFS_BD_PACK/schema_creator/OFS_BD_SCHEMA_OUTPUT.xml

    		 Yes
    ##OFS_FCCM_ LOADER_ROLE## This attribute role is used when OFS BD 8.0.1.0.0/8.0.4.0.0 is installed. The value will be available in OFS_BD_SCHEMA_ OUTPUT.xml and is generated at the time of 8.1.1.1.0 Installation. Yes
    ##OFS_AML_ANALYST_DATA_SOURCE## Name of the Analyst Data source used for Admin Tools Configurations.

    For example: Create a data source with name ANALYST.

    		 Yes
    ##OFS_AML_MINER_DATA_SOURCE## Name of the Miner Data source used for Admin Tools Configurations.

    For example: Create a data source with name MINER.

    		 Yes
    ##BASE_COUNTRY## ISO country code to use during data ingestion to record Institution-derived geography risk on parties on transactions that are internal to the OFSBD client.

    For example: base_country=US base_country=US.

    		 Yes
    ##DEFAULT_ JURISDICTION## Jurisdiction to assign the derived entities and derived addresses.

    For example: default_jurisdiction=AMEA.

    		 Yes
    ##TNS_ADMIN## This attribute refers to the path where TNSNAMES.ORA is placed.

    For example: /scratch/ofsaaapp.

    		 Yes
    ##BIG_DATA_ ENABLE## Placeholder to enable Big Data. Enter FALSE. Yes
    ##OFS_AML_SQOOP_WORKING_DIR## Placeholder to provide SQOOP working directory for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_AUTH_ ALIAS## Placeholder to provide SSH authorization alias for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_HOST_ NAME## Placeholder to provide SSH host name for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_ PORT## Placeholder to provide SSH port name for AML. Mandatory only if big data is enabled.
    ##FSDF_UPLOAD_MODEL# # This flag indicates whether the FSDF data model has to be executed or not. If the user wants to upload FSDF data model, the user must enter the value as 1 or enter the value as 0. No
    - Note:
    KYC Onboarding requires additional deployments of the following:
    • Initiate Onboarding Service (InitiateOnboardingService.war)
    • Table To JSON Service (TabletoJSONService.war)
    • JSON To Table Service (JSONToTablePersistenceUtility.war)
    • Common Gateway Service (CommonGatewayService.war)
    • Generate Case Input Service (GenerateCaseInputService.war)
    • Create JSON Service (createJSONService.war)
    The above .war files are available in the FIC_HOME path post-installation. For information on deploying the .war files, see Post Installation Configuration

    These deployments are in addition to the Application Pack deployment , that is, OFSBD, Watch list Service deployment and RAOR deployments which are mandatory for KYC onboarding.

    For information on the services, see Know Your Customer Service Guide.

    The following parameters are applicable for KYC Onboarding:

    		 -
    ##OBDATASRCNAME# # This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be OBDATASRCNAME.
    ##COMN_GATWAY_ DS## This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be COMN_GATWAY_DS.
    ##AAI_AUTH_URL## This is the URL of the BD application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be AAI_URL.
    ##TABLE_TO_JSON_PROTOCOL_SERVER_PORT## This is the URL of Table To JSON Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be T2J_URL.
    ##JSON_TO_TABLE_PROTOCOL_SERVER_PORT## This is the URL of JSON To Table Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be J2T_URL.
    ##OB_PROTOCOL_ SERVER_PORT## This is the URL of Initiate onboarding service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OB_URL.
    ##ECM_APP_URL## This is the URL of the ECM application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be ECM_ CASE_URL.
    ##CASE_INPUT_PROTOCOL_SERVER_PORT## This is the URL of the Generate Case Input Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be GCI_URL.
    ##COMMON_GATEWAY_PROTOCOL_SERVER_ PORT## This is the URL of the Common Gateway Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CMNGTWYURL.
    ##SCORING_ PROTOCOL_SERVER_ PORT## This is the URL of the RAOR Application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be SCORING_URL.
    ##OFSS_WLS_PROTOCOL_SERVER_PORT## This is the URL of the OFS Watch list application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OFSS_ WLS_URL.
    ##CS_PROTOCOL_ SERVER_PORT## This is the URL of the OFS Customer Screening Application till the port number.

    For example: <PROTOCOL:/HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CS_URL.
    ##COMM_LOG_PATH## This is the path of the KYC onboarding log file.

    For example: /scratch/ofsaaapp/KYC808DEV/apache-tomcat-8.0.47/logs.

    		 Mandatory only if KYC onboarding is used.
    Placeholder Name Significance and Expected Value Mandatory
    ##QTNR_RESP_URL## This is the URL of the OFS KYC onboarding service.

    The URL is <PROTOCOL:/HOSTNAME:PORT/CONTEXT_NAME>/questionnaire_api/questionnaires/ resume/<INFODOM>/en_US?appCode=OFS_KYC.

    		 Mandatory only if KYC onboarding is used. If not, value must be ##QTNR_ RESP_URL##.
    ##OFS_COMM_DATA_ TBSP## This is the table space for the common gateway. The value is COMM_DATA_TBSP. Mandatory only if KYC onboarding is used. If not, value must be ##OFS_COMM_DATA_TBSP##.
  5. Navigate to the OFS_BD_PACK/bin folder and execute setup.sh file using the following command: 
    $./setup.sh SILENT
  6. After Installation is successful, apply AAI patch by downloading the bug 33738222 from My Oracle Support.
  7. After the patch installation is successful, execute BD_Duplicate_Jar_Removal.sh script from $FIC_HOME.
  8. Entry (DBNAME of Atomic Schema) must be added in the tnsnames.ora file on the OFSAA server.

    Note:

    • After Upgrade Run below scripts manually as post upgrade steps: $FIC_HOME/database/db_tools/bin.
      • ./run_dbbuilder_utility.sh $FIC_HOME/database/mantas_schema/delta/oracle/8.0/mantas8.1.2.0.0_delta.cfg
      • ./run_dbbuilder_utility.sh$FIC_HOME/database/bus_mkt_schema/delta/oracle/8.0/delta_plat8.1.2.0.0.cfg

      During installation, the PR_8.1.2.0.0_33645879.miner.sql script can fail with error code ORA-02303. This issue can be resolved by adding keyword FORCE to following string:

      CREATE OR REPLACE TYPE DEPWD_SAMT_EN_ROW FORCE AS OBJECT (

      This issue is to be fixed in release 8.1.2.1 ML.

    • To enable newly licensed app from OFSA BD pack, see How to Enable Newly Licensed App after Upgrade to BD 8.1.2.0.0.
    • Load the following scenarios manually using the sm_load utility available in the $FIC_HOME/database/db_tools/bin path.

      For details on running the sm_load utility, see Loading Scenario Metadata section in OFS BD Administration Guide 8.1.2.0.0.

      List of scenarios to be loaded:

      • ML-CIBPreviousAverageActivity.116000083.xml
      • ML-CashTransPossibleCTR.116000037.xml
      • ML-DepWDSameAmts.118860020.xml
      • ML-LargeReportableTrans.116000099.xml
      • ML-RapidMvmtFundsAllActivity.116000079.xml
      • ML-StructuringAvoidReportThreshold.116000046.xml
      • ML-StructuringAvoidReportThreshold.116000062.xml

Cloning Upgrades of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

Perform the Cloning upgrade of OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0.

Note:

  • Ensure to take the backup of File System (FIC_HOME and FTPSHARE), Atomic schema, and Config schema before performing the upgrade.
  • Ensure that you end all the batches before you start the upgrade process.
  • For enabling the unlimited Cryptographic Policy for Java, see Enabling Unlimited Cryptographic Policy for Java.
  • ORACLE_HOME AND JAVA_HOME have to be updated under FIC_HOME SUB DIRECTORIES while performing cloning upgrade.
  • If CTR is not enabled in 8.1.1.0.0, 8.1.1.1.0 patch is applied. The below error can be ignored if it is observed.
    Query: 
    insert into CSSMS_ROLE_FUNCTION_MAP (V_ROLE_CODE, V_FUNCTION_CODE) values ('CTRADMN', 'AMPASENCYT')
    Error: ORA-02291: integrity constraint (AK7_811CONF.FK_CSSMS_ROLE_FUNCTION_MAP_2) violated - parent key not found.
Prerequisites:

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • If user has different schema for FSDF, see the Configuring FSDF in Different Infodom (Pack on Pack Installation) section in Configuring FSDF before upgrading.
  • Before upgrade take backup of all STGSTG tables. Use the list of the STG tables (BD FSDF_OIDF Merged 81210 Staging Tables) and create SQL truncate script for truncating STG tables from BD atomic schema.
  • The minimum BD patch level must be bug 33767914.

To clone upgrade:

  1. Download and unzip the OFS BD 8.1.2.0.0 Installer from My Oracle Support by using the bug 33940349 - OFS BD APPLICATION PACK - 8.1.2.0.0.
  2. Navigate to OFS_BD_PACK and grant execute (755) permission for all executables $ chmod 755 *.
  3. Navigate to installer/OFS_BD_PACK/conf and update OFS_BD_PACK.xml. Select applications to enable. For more information, see Configuring OFS_BD_PACK.xml File.

    Note:

    Enter YES in ENABLE tag to enable applications which has been installed and Enter NO in the remaining applications.
  4. Modify PatchConfig.xml parameters under OFS_BD_PACK/OFS_AML/conf/PatchConfig.xml with appropriate values as described in the following table.

    Table 6-6 Modify PatchConfig.xml Parameters

    Placeholder Name Significance and Expected Value Mandatory
    ##OFS_AML_SW_RMIPORT## The Scenario Wizard uses this attribute. It must consist of a proper port number and not be used by any other application.

    For example, 7623 or 8204.

    		 Yes
    ##OFS_AML_SAVE_METADATA# The installer to decide whether to execute hierarchy. Resave uses this attribute. The applicable value is ALL. Yes
    ##EXECUTE_PRE_AND_POST_SCRIPTS## This flag indicates if certain scripts need to be executed just before and just after the data model upload Applicable value is 1. Yes (Value = 0)
    ##SCHEMA_OUT_ XML_PATH## This attribute refers to the path, which needs to be pointed to OFS_BD_ SCHEMA_OUTPUT.xml, which was generated at the time of installation.

    For example, /scratch/ofsaaapp/Installer/OFS_BD_PACK/schema_creator/OFS_BD_SCHEMA_OUTPUT.xml

    		 Yes
    ##OFS_FCCM_ LOADER_ROLE## This attribute role is used when OFS BD 8.0.1.0.0/8.0.4.0.0 is installed. The value will be available in OFS_BD_SCHEMA_ OUTPUT.xml and is generated at the time of 8.1.1.1.0 Installation. Yes
    ##OFS_AML_ANALYST_DATA_SOURCE## Name of the Analyst Data source used for Admin Tools Configurations.

    For example: Create a data source with name ANALYST.

    		 Yes
    ##OFS_AML_MINER_DATA_SOURCE## Name of the Miner Data source used for Admin Tools Configurations.

    For example: Create a data source with name MINER.

    		 Yes
    ##BASE_COUNTRY## ISO country code to use during data ingestion to record Institution-derived geography risk on parties on transactions that are internal to the OFSBD client.

    For example: base_country=US base_country=US.

    		 Yes
    ##DEFAULT_ JURISDICTION## Jurisdiction to assign the derived entities and derived addresses.

    For example: default_jurisdiction=AMEA.

    		 Yes
    ##TNS_ADMIN## This attribute refers to the path where TNSNAMES.ORA is placed.

    For example: /scratch/ofsaaapp.

    		 Yes
    ##BIG_DATA_ ENABLE## Placeholder to enable Big Data. Enter FALSE. Yes
    ##OFS_AML_SQOOP_WORKING_DIR## Placeholder to provide SQOOP working directory for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_AUTH_ ALIAS## Placeholder to provide SSH authorization alias for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_HOST_ NAME## Placeholder to provide SSH host name for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_ PORT## Placeholder to provide SSH port name for AML. Mandatory only if big data is enabled.
    ##FSDF_UPLOAD_MODEL# # This flag indicates whether the FSDF data model has to be executed or not. If the user wants to upload FSDF data model, the user must enter the value as 1 or enter the value as 0. No
    - Note:
    KYC Onboarding requires additional deployments of the following:
    • Initiate Onboarding Service (InitiateOnboardingService.war)
    • Table To JSON Service (TabletoJSONService.war)
    • JSON To Table Service (JSONToTablePersistenceUtility.war)
    • Common Gateway Service (CommonGatewayService.war)
    • Generate Case Input Service (GenerateCaseInputService.war)
    • Create JSON Service (createJSONService.war)
    The above .war files are available in the FIC_HOME path post-installation. For information on deploying the .war files, see Post Installation Configuration

    These deployments are in addition to the Application Pack deployment , that is, OFSBD, Watch list Service deployment and RAOR deployments which are mandatory for KYC onboarding.

    For information on the services, see Know Your Customer Service Guide.

    The following parameters are applicable for KYC Onboarding:

    		 -
    ##OBDATASRCNAME# # This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be OBDATASRCNAME.
    ##COMN_GATWAY_ DS## This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be COMN_GATWAY_DS.
    ##AAI_AUTH_URL## This is the URL of the BD application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be AAI_URL.
    ##TABLE_TO_JSON_PROTOCOL_SERVER_PORT## This is the URL of Table To JSON Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be T2J_URL.
    ##JSON_TO_TABLE_PROTOCOL_SERVER_PORT## This is the URL of JSON To Table Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be J2T_URL.
    ##OB_PROTOCOL_ SERVER_PORT## This is the URL of Initiate onboarding service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OB_URL.
    ##ECM_APP_URL## This is the URL of the ECM application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be ECM_ CASE_URL.
    ##CASE_INPUT_PROTOCOL_SERVER_PORT## This is the URL of the Generate Case Input Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be GCI_URL.
    ##COMMON_GATEWAY_PROTOCOL_SERVER_ PORT## This is the URL of the Common Gateway Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CMNGTWYURL.
    ##SCORING_ PROTOCOL_SERVER_ PORT## This is the URL of the RAOR Application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be SCORING_URL.
    ##OFSS_WLS_PROTOCOL_SERVER_PORT## This is the URL of the OFS Watch list application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OFSS_ WLS_URL.
    ##CS_PROTOCOL_ SERVER_PORT## This is the URL of the OFS Customer Screening Application till the port number.

    For example: <PROTOCOL:/HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CS_URL.
    ##COMM_LOG_PATH## This is the path of the KYC onboarding log file.

    For example: /scratch/ofsaaapp/KYC808DEV/apache-tomcat-8.0.47/logs.

    		 Mandatory only if KYC onboarding is used.
    Placeholder Name Significance and Expected Value Mandatory
    ##QTNR_RESP_URL## This is the URL of the OFS KYC onboarding service.

    The URL is <PROTOCOL:/HOSTNAME:PORT/CONTEXT_NAME>/questionnaire_api/questionnaires/ resume/<INFODOM>/en_US?appCode=OFS_KYC.

    		 Mandatory only if KYC onboarding is used. If not, value must be ##QTNR_ RESP_URL##.
    ##OFS_COMM_DATA_ TBSP## This is the table space for the common gateway. The value is COMM_DATA_TBSP. Mandatory only if KYC onboarding is used. If not, value must be ##OFS_COMM_DATA_TBSP##.
  5. Navigate to the OFS_BD_PACK/bin folder and execute setup.sh file using the following command: 
    $./setup.sh SILENT
  6. After Installation is successful, apply AAI patch by downloading the bug 33738222 from My Oracle Support.
  7. After the patch installation is successful, execute BD_Duplicate_Jar_Removal.sh script from $FIC_HOME.
  8. Entry (DBNAME of Atomic Schema) must be added in the tnsnames.ora file on the OFSAA server.

    Note:

    • After Upgrade Run below scripts manually as post upgrade steps: $FIC_HOME/database/db_tools/bin.
      • ./run_dbbuilder_utility.sh $FIC_HOME/database/mantas_schema/delta/oracle/8.0/mantas8.1.2.0.0_delta.cfg
      • ./run_dbbuilder_utility.sh$FIC_HOME/database/bus_mkt_schema/delta/oracle/8.0/delta_plat8.1.2.0.0.cfg

      During installation, the PR_8.1.2.0.0_33645879.miner.sql script can fail with error code ORA-02303. This issue can be resolved by adding keyword FORCE to following string:

      CREATE OR REPLACE TYPE DEPWD_SAMT_EN_ROW FORCE AS OBJECT (

      This issue is to be fixed in release 8.1.2.1 ML.

    • To enable newly licensed app from OFSA BD pack, see How to Enable Newly Licensed App after Upgrade to BD 8.1.2.0.0.
    • Load the following scenarios manually using the sm_load utility available in the $FIC_HOME/database/db_tools/bin path.

      List of scenarios to be loaded:

      • ML-CIBPreviousAverageActivity.116000083.xml
      • ML-CashTransPossibleCTR.116000037.xml
      • ML-DepWDSameAmts.118860020.xml
      • ML-LargeReportableTrans.116000099.xml
      • ML-RapidMvmtFundsAllActivity.116000079.xml
      • ML-StructuringAvoidReportThreshold.116000046.xml
      • ML-StructuringAvoidReportThreshold.116000062.xml

Pack on Pack Inplace Upgrade from OFS BD 8.1.1.1.0, OFS ECM 8.1.1.1.0 and OFS CRR 8.1.1.1.0 to OFS BD 8.1.2.0.0, OFS ECM 8.1.2.0.0 and OFS CRR 8.1.2.0.0

Performing Pack on Pack Inplace Upgrade from OFS BD 8.1.1.1.0, OFS ECM 8.1.1.1.0 and OFS CRR 8.1.1.1.0 to OFS BD 8.1.2.0.0, OFS ECM 8.1.2.0.0 and OFS CRR 8.1.2.0.0.

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • Ensure to take the backup of File System (FIC_HOME and FTPSHARE), Atomic schema, and Config schema before performing the upgrade.
  • Ensure that the dispatcher is not running. If the dispatcher is running, stop and then start the upgrading process.
  • Ensure that you end all the batches before you start the upgrade process.
  • Ensure that you run the END_MANTAS_BATCH before starting the upgrade.
  • For enabling the unlimited Cryptographic Policy for Java, see Enabling Unlimited Cryptographic Policy for Java.
  • ORACLE_HOME AND JAVA_HOME have to be updated under FIC_HOME SUB DIRECTORIES while performing Inplace upgrade.
  • If CTR is not enabled in 8.1.1.0.0, 8.1.1.1.0 patch is applied. The below error can be ignored if it is observed.
    Query: 
    insert into CSSMS_ROLE_FUNCTION_MAP (V_ROLE_CODE, V_FUNCTION_CODE) values ('CTRADMN', 'AMPASENCYT')
    Error: ORA-02291: integrity constraint (AK7_811CONF.FK_CSSMS_ROLE_FUNCTION_MAP_2) violated - parent key not found.
  • If the OFS Sanctions 8.0.8.0.0 is installed:
    • create table KDD_BUS_DMN_SANC as (select * from DD_BUS_DMN);
    • UPDATE KDD_BUS_DMN SET TF_BUS_DMN_NM=NULL; commit

Pack on Pack Upgrade Sequence

Use the following pack upgrade sequence:
  • OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0
  • OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0
  • OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0

OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

Follow these steps for OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0.

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • If user has different schema for FSDF, see the Configuring FSDF in Different Infodom (Pack on Pack Installation) section in Configuring FSDF before upgrading.
  • Before upgrade take backup of all STGSTG tables. Use the list of the STG tables (BD FSDF_OIDF Merged 81210 Staging Tables) and create SQL truncate script for truncating STG tables from BD atomic schema.
  • The minimum BD patch level must be bug 33767914.

To upgrade:

  1. Download and unzip the OFS BD 8.1.2.0.0 Installer from My Oracle Support by using the bug 33940349 - OFS BD APPLICATION PACK - 8.1.2.0.0. Refer to the following instructions to download, extract, install, and configure this release:
  2. Shut down all the OFSAAI Services. For more information, see the Start/Stop Infrastructure Services section in Starting/Stopping Infrastructure Services.
  3. Execute the command: 
    chmod -R 755 $FIC_HOME.
  4. If you have Unzip utility, skip to the next step. Download the Unzip utility (OS specific) and copy it in Binary mode to the directory that is included in your PATH variable, typically $HOME path or directory in which you have copied the 8.1.2.0.0 installer.
  5. Uncompress the unzip installer file using the command: 
    uncompressunzip_<os>.Z

    Note:

    In case you notice an error message “uncompress: not found [No such file or directory]” when the package is not installed, contact your UNIX administrator.
  6. Extract the contents of the Oracle Financial Services Behavior Detection Applications Pack 8.1.2.0.0 installer archive file using the command: 
    unzip_<os> <name of the file to be unzipped>
  7. Assign EXECUTE permission to the archive file OFS_BD_PACK as in the following sample command: 
    chmod -R 750 OFS_BD_PACK
  8. Navigate to installer/OFS_BD_PACK/OFS_AML/conf and update patchconfig.xml and grant permission to the .sh files as described in the following table.

    Table 6-7 Update PatchConfig.xml Parameters

    Placeholder Name Significance and Expected Value Mandatory
    ##OFS_AML_SW_RMIPORT## The Scenario Wizard uses this attribute. It must consist of a proper port number and not be used by any other application.

    For example, 7623 or 8204.

    		 Yes
    ##OFS_AML_SAVE_METADATA# The installer to decide whether to execute hierarchy. Resave uses this attribute. The applicable value is ALL. Yes
    ##EXECUTE_PRE_AND_POST_SCRIPTS## This flag indicates if certain scripts need to be executed just before and just after the data model upload Applicable value is 1. Yes (Value = 0)
    ##SCHEMA_OUT_ XML_PATH## This attribute refers to the path, which needs to be pointed to OFS_BD_ SCHEMA_OUTPUT.xml, which was generated at the time of installation.

    For example: /scratch/ofsaaapp/Installer/OFS_BD_PACK/schema_creator/OFS_BD_SCHEMA_OUTPUT.xml

    		 Yes
    ##OFS_FCCM_ LOADER_ROLE## This attribute role is used when OFS BD 8.0.1.0.0/8.0.4.0.0 is installed. The value will be available in OFS_BD_SCHEMA_ OUTPUT.xml and is generated at the time of 8.1.1.1.0 Installation. Yes
    ##OFS_AML_ANALYST_DATA_SOURCE## Name of the Analyst Data source used for Admin Tools Configurations.

    For example: Create a data source with name ANALYST.

    		 Yes
    ##OFS_AML_MINER_DATA_SOURCE## Name of the Miner Data source used for Admin Tools Configurations.

    For example: Create a data source with name MINER.

    		 Yes
    ##BASE_COUNTRY## ISO country code to use during data ingestion to record Institution-derived geography risk on parties on transactions that are internal to the OFSBD client.

    For example: base_country=US base_country=US.

    		 Yes
    ##DEFAULT_ JURISDICTION## Jurisdiction to assign the derived entities and derived addresses.

    For example: default_jurisdiction=AMEA.

    		 Yes
    ##TNS_ADMIN## This attribute refers to the path where TNSNAMES.ORA is placed.

    For example: /scratch/ofsaaapp.

    		 Yes
    ##BIG_DATA_ ENABLE## Placeholder to enable Big Data. Enter FALSE. Yes
    ##OFS_AML_SQOOP_WORKING_DIR## Placeholder to provide SQOOP working directory for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_AUTH_ ALIAS## Placeholder to provide SSH authorization alias for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_HOST_ NAME## Placeholder to provide SSH host name for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_ PORT## Placeholder to provide SSH port name for AML. Mandatory only if big data is enabled.
    ##FSDF_UPLOAD_MODEL# # This flag indicates whether the FSDF data model has to be executed or not. If the user wants to upload FSDF data model, the user must enter the value as 1 or enter the value as 0. No
    - Note:
    KYC Onboarding requires additional deployments of the following:
    • Initiate Onboarding Service (InitiateOnboardingService.war)
    • Table To JSON Service (TabletoJSONService.war)
    • JSON To Table Service (JSONToTablePersistenceUtility.war)
    • Common Gateway Service (CommonGatewayService.war)
    • Generate Case Input Service (GenerateCaseInputService.war)
    • Create JSON Service (createJSONService.war)
    The above .war files are available in the FIC_HOME path post-installation. For information on deploying the .war files, see Post Installation Configuration

    These deployments are in addition to the Application Pack deployment , that is, OFSBD, Watch list Service deployment and RAOR deployments which are mandatory for KYC onboarding.

    For information on the services, see Know Your Customer Service Guide.

    The following parameters are applicable for KYC Onboarding:

    		 -
    ##OBDATASRCNAME# # This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be OBDATASRCNAME.
    ##COMN_GATWAY_ DS## This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be COMN_GATWAY_DS.
    ##AAI_AUTH_URL## This is the URL of the BD application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be AAI_URL.
    ##TABLE_TO_JSON_PROTOCOL_SERVER_PORT## This is the URL of Table To JSON Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be T2J_URL.
    ##JSON_TO_TABLE_PROTOCOL_SERVER_PORT## This is the URL of JSON To Table Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be J2T_URL.
    ##OB_PROTOCOL_ SERVER_PORT## This is the URL of Initiate onboarding service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OB_URL.
    ##ECM_APP_URL## This is the URL of the ECM application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be ECM_ CASE_URL.
    ##CASE_INPUT_PROTOCOL_SERVER_PORT## This is the URL of the Generate Case Input Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be GCI_URL.
    ##COMMON_GATEWAY_PROTOCOL_SERVER_ PORT## This is the URL of the Common Gateway Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CMNGTWYURL.
    ##SCORING_ PROTOCOL_SERVER_ PORT## This is the URL of the RAOR Application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be SCORING_URL.
    ##OFSS_WLS_PROTOCOL_SERVER_PORT## This is the URL of the OFS Watch list application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OFSS_ WLS_URL.
    ##CS_PROTOCOL_ SERVER_PORT## This is the URL of the OFS Customer Screening Application till the port number.

    For example: <PROTOCOL:/HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CS_URL.
    ##COMM_LOG_PATH## This is the path of the KYC onboarding log file.

    For example: /scratch/ofsaaapp/KYC808DEV/apache-tomcat-8.0.47/logs.

    		 Mandatory only if KYC onboarding is used.
    Placeholder Name Significance and Expected Value Mandatory
    ##QTNR_RESP_URL## This is the URL of the OFS KYC onboarding service.

    The URL is <PROTOCOL:/HOSTNAME:PORT/CONTEXT_NAME>/questionnaire_api/questionnaires/ resume/<INFODOM>/en_US?appCode=OFS_KYC.

    		 Mandatory only if KYC onboarding is used. If not, value must be ##QTNR_ RESP_URL##.
    ##OFS_COMM_DATA_ TBSP## This is the table space for the common gateway. The value is COMM_DATA_TBSP. Mandatory only if KYC onboarding is used. If not, value must be ##OFS_COMM_DATA_TBSP##.
  9. Navigate to the OFS_BD_PACK/bin folder and execute setup.sh file using the following command: 
    $./setup.sh SILENT
  10. After Installation is successful, apply AAI patch by downloading the bug 33738222 from My Oracle Support.
  11. After the patch installation is successful, execute BD_Duplicate_Jar_Removal.sh script from $FIC_HOME.
  12. Entry (DBNAME of Atomic Schema) must be added in the tnsnames.ora file on the OFSAA server.

    Note:

    • After Upgrade Run below scripts manually as post upgrade steps: $FIC_HOME/database/db_tools/bin.
      • ./run_dbbuilder_utility.sh $FIC_HOME/database/mantas_schema/delta/oracle/8.0/mantas8.1.2.0.0_delta.cfg
      • ./run_dbbuilder_utility.sh$FIC_HOME/database/bus_mkt_schema/delta/oracle/8.0/delta_plat8.1.2.0.0.cfg

      During installation, the PR_8.1.2.0.0_33645879.miner.sql script can fail with error code ORA-02303. This issue can be resolved by adding keyword FORCE to following string:

      CREATE OR REPLACE TYPE DEPWD_SAMT_EN_ROW FORCE AS OBJECT (

      This issue is to be fixed in release 8.1.2.1 ML.

    • Load the following scenarios manually using the sm_load utility available in the $FIC_HOME/database/db_tools/bin path.

      List of scenarios to be loaded:

      • ML-CIBPreviousAverageActivity.116000083.xml
      • ML-CashTransPossibleCTR.116000037.xml
      • ML-DepWDSameAmts.118860020.xml
      • ML-LargeReportableTrans.116000099.xml
      • ML-RapidMvmtFundsAllActivity.116000079.xml
      • ML-StructuringAvoidReportThreshold.116000046.xml
      • ML-StructuringAvoidReportThreshold.116000062.xml
  13. Verify if the release is applied successfully by checking the log file generated in the installation folder. You can ignore ORA-00001, ORA-00955, ORA-02260, and ORA-01430 errors in the log file. In case of any other errors, contact My Oracle Support.

    Note:

    • The DMT migration utility is executed during BD installation to migrate the DMT metadata (PLC/Data Source/Data Mapping/Data File Mapping) to be persisted in tables instead of XML. You may be required to re-run the DMT migration utility in some scenarios. To identify whether to run the utility, how to run, and how to handle migration issues, see OFSAA DMT Metadata Migration Guide.
    • Ignore the below fatal error in the putty console while upgrading:

      Summary will be written to: ../log/ DMTMigrationUtilityReport.log

      Detailed logs can be found in: ../log/ DMTMigrationUtility.log FIC_HOME:/scratch/ofsaadb/BDECM811OCT/

      [Fatal Error] ETLLoader.properties:2:1: Premature end of file.

  14. For more information on securing your OFSAA Infrastructure, see the Security Guide in OHC Library.
  15. Add umask 0027 in the .profile of the UNIX account, which manages the WEB server to ensure restricted access permissions.
  16. Restart all the OFSAAI services. For more information, see the Start/Stop Infrastructure Services section in Starting/Stopping Infrastructure Services.
  17. Generate the application EAR/WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying EAR/WAR file, see Creating and Deploying EAR/WAR File.
  18. Deploy the RPD and Catalog ORACLE ANALYTIC SERVER (OAS) 5.9 files available under $FIC_HOME/ORACLE ANALYTIC SERVER (OAS) 5.9 folder.
  19. For enabling TDE in case of a new installation, see the Configuring TDE in case of Upgradesection in Configuring TDE and Data Redaction in OFSAA.
  20. For enabling Data Redaction in case of a new installation, see the Enabling Data Redaction in case of Upgrade section in Configuring TDE and Data Redaction in OFSAA.

    Note:

    To enable newly licensed app from OFSA BD pack, see How to Enable Newly Licensed App after Upgrade to BD 8.1.2.0.0.

OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0

See the OFS ECM Installation Guide 8.1.2.0.0 for Pack on Pack Inplace Upgrade steps from OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0.

OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0

See the OFS CRR Installation Guide 8.1.2.0.0 for Pack on Pack Inplace Upgrade steps from OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0.

Pack on Pack Cloning Upgrade from OFS BD 8.1.1.1.0, OFS ECM 8.1.1.1.0 and OFS CRR 8.1.1.1.0 to OFS BD 8.1.2.0.0, OFS ECM 8.1.2.0.0 and OFS CRR 8.1.2.0.0

Performing Pack on Pack Cloning Upgrade from OFS BD 8.1.1.1.0, OFS ECM 8.1.1.1.0 and OFS CRR 8.1.1.1.0 to OFS BD 8.1.2.0.0, OFS ECM 8.1.2.0.0 and OFS CRR 8.1.2.0.0.

Pre-requisites:

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • Ensure to take the backup of File System (FIC_HOME and FTPSHARE), Atomic schema, and Config schema before performing the upgrade.
  • Ensure that the dispatcher is not running. If the dispatcher is running, stop and then start the upgrading process.
  • Ensure that you end all the batches before you start the upgrade process.
  • Ensure that you run the END_MANTAS_BATCH before starting the upgrade.
  • For enabling the unlimited Cryptographic Policy for Java, see Enabling Unlimited Cryptographic Policy for Java.
  • ORACLE_HOME AND JAVA_HOME have to be updated under FIC_HOME SUB DIRECTORIES while performing cloning upgrade.
  • If CTR is not enabled in 8.1.1.0.0, 8.1.1.1.0 patch is applied. The below error can be ignored if it is observed.
    Query: 
    insert into CSSMS_ROLE_FUNCTION_MAP (V_ROLE_CODE, V_FUNCTION_CODE) values ('CTRADMN', 'AMPASENCYT')
    Error: ORA-02291: integrity constraint (AK7_811CONF.FK_CSSMS_ROLE_FUNCTION_MAP_2) violated - parent key not found.
  • If the OFS Sanctions 8.0.8.0.0 is installed:
    • create table KDD_BUS_DMN_SANC as (select * from DD_BUS_DMN);
    • UPDATE KDD_BUS_DMN SET TF_BUS_DMN_NM=NULL; commit

Pack on Pack Upgrade Sequence

Use the following pack upgrade sequence:
  • OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0
  • OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0
  • OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0

OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0

Follow these steps for OFS BD 8.1.1.1.0 to OFS BD 8.1.2.0.0.

Note:

  • The archive files are different for every operating system like Solaris Sparc and RHEL/Oracle Linux.
  • If user has different schema for FSDF, see the Configuring FSDF in Different Infodom (Pack on Pack Installation) section in Configuring FSDF before upgrading.
  • Before upgrade take backup of all STGSTG tables. Use the list of the STG tables (BD FSDF_OIDF Merged 81210 Staging Tables) and create SQL truncate script for truncating STG tables from BD atomic schema.
  • The minimum BD patch level must be bug 33767914.

To clone upgrade:

  1. Download and unzip the OFS BD 8.1.2.0.0 Installer from My Oracle Support by using the bug 33940349 - OFS BD APPLICATION PACK - 8.1.2.0.0. Refer to the following instructions to download, extract, install, and configure this release.
  2. Login to the OFSAA Server with user credentials used to install OFSAA.
  3. Shut down all the OFSAAI Services. For more information, see the Start/Stop Infrastructure Services section in Starting/Stopping Infrastructure Services.
  4. Execute the command: 
    chmod -R 755 $FIC_HOME.
  5. If you have Unzip utility, skip to the next step. Download the Unzip utility (OS specific) and copy it in Binary mode to the directory that is included in your PATH variable, typically $HOME path or directory in which you have copied the 8.1.2.0.0 installer.
  6. Uncompress the unzip installer file using the command: 
    uncompressunzip_<os>.Z

    Note:

    In case you notice an error message “uncompress: not found [No such file or directory]” contact your UNIX administrator if the package is not installed.
  7. Extract the contents of the Oracle Financial Services Behavior Detection Applications Pack 8.1.2.0.0 installer archive file using the command: 
    unzip_<os> <name of the file to be unzipped>
  8. Assign EXECUTE permission to the archive file OFS_BD_PACK as in the following sample command: 
    chmod -R 750 OFS_BD_PACK
  9. Navigate to installer/OFS_BD_PACK/OFS_AML/conf and update patchconfig.xml and grant permission to the .sh files as described in the following table.

    Table 6-8 PatchConfig.xml Parameters

    Placeholder Name Significance and Expected Value Mandatory
    ##OFS_AML_SW_RMIPORT## The Scenario Wizard uses this attribute. It must consist of a proper port number and not be used by any other application.

    For example, 7623 or 8204.

    		 Yes
    ##OFS_AML_SAVE_METADATA# The installer to decide whether to execute hierarchy. Resave uses this attribute. The applicable value is ALL. Yes
    ##EXECUTE_PRE_AND_POST_SCRIPTS## This flag indicates if certain scripts need to be executed just before and just after the data model upload Applicable value is 1. Yes (Value = 0)
    ##SCHEMA_OUT_ XML_PATH## This attribute refers to the path, which needs to be pointed to OFS_BD_ SCHEMA_OUTPUT.xml, which was generated at the time of installation.

    For example, /scratch/ofsaaapp/Installer/OFS_BD_PACK/schema_creator/OFS_BD_SCHEMA_OUTPUT.xml

    		 Yes
    ##OFS_FCCM_ LOADER_ROLE## This attribute role is used when OFS BD 8.0.1.0.0/8.0.4.0.0 is installed. The value will be available in OFS_BD_SCHEMA_ OUTPUT.xml and is generated at the time of 8.1.1.1.0 Installation. Yes
    ##OFS_AML_ANALYST_DATA_SOURCE## Name of the Analyst Data source used for Admin Tools Configurations.

    For example: Create a data source with name ANALYST.

    		 Yes
    ##OFS_AML_MINER_DATA_SOURCE## Name of the Miner Data source used for Admin Tools Configurations.

    For example: Create a data source with name MINER.

    		 Yes
    ##BASE_COUNTRY## ISO country code to use during data ingestion to record Institution-derived geography risk on parties on transactions that are internal to the OFSBD client.

    For example: base_country=US base_country=US.

    		 Yes
    ##DEFAULT_ JURISDICTION## Jurisdiction to assign the derived entities and derived addresses.

    For example: default_jurisdiction=AMEA.

    		 Yes
    ##TNS_ADMIN## This attribute refers to the path where TNSNAMES.ORA is placed.

    For example: /scratch/ofsaaapp.

    		 Yes
    ##BIG_DATA_ ENABLE## Placeholder to enable Big Data. Enter FALSE. Yes
    ##OFS_AML_SQOOP_WORKING_DIR## Placeholder to provide SQOOP working directory for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_AUTH_ ALIAS## Placeholder to provide SSH authorization alias for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_HOST_ NAME## Placeholder to provide SSH host name for AML. Mandatory only if big data is enabled.
    ##OFS_AML_SSH_ PORT## Placeholder to provide SSH port name for AML. Mandatory only if big data is enabled.
    ##FSDF_UPLOAD_MODEL# # This flag indicates whether the FSDF data model has to be executed or not. If the user wants to upload FSDF data model, the user must enter the value as 1 or enter the value as 0. No
    - Note:
    KYC Onboarding requires additional deployments of the following:
    • Initiate Onboarding Service (InitiateOnboardingService.war)
    • Table To JSON Service (TabletoJSONService.war)
    • JSON To Table Service (JSONToTablePersistenceUtility.war)
    • Common Gateway Service (CommonGatewayService.war)
    • Generate Case Input Service (GenerateCaseInputService.war)
    • Create JSON Service (createJSONService.war)
    The above .war files are available in the FIC_HOME path post-installation. For information on deploying the .war files, see Post Installation Configuration

    These deployments are in addition to the Application Pack deployment , that is, OFSBD, Watch list Service deployment and RAOR deployments which are mandatory for KYC onboarding.

    For information on the services, see Know Your Customer Service Guide.

    The following parameters are applicable for KYC Onboarding:

    		 -
    ##OBDATASRCNAME# # This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be OBDATASRCNAME.
    ##COMN_GATWAY_ DS## This is the name of the datasource pointing to the atomic schema. Mandatory only if KYC onboarding is used. If not, value must be COMN_GATWAY_DS.
    ##AAI_AUTH_URL## This is the URL of the BD application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be AAI_URL.
    ##TABLE_TO_JSON_PROTOCOL_SERVER_PORT## This is the URL of Table To JSON Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be T2J_URL.
    ##JSON_TO_TABLE_PROTOCOL_SERVER_PORT## This is the URL of JSON To Table Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be J2T_URL.
    ##OB_PROTOCOL_ SERVER_PORT## This is the URL of Initiate onboarding service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OB_URL.
    ##ECM_APP_URL## This is the URL of the ECM application till the context name.

    For example: <PROTOCOL:/HOSTNAME:PORT/ CONTEXT_NAME>.

    		 Mandatory only if KYC onboarding is used. If not, value must be ECM_ CASE_URL.
    ##CASE_INPUT_PROTOCOL_SERVER_PORT## This is the URL of the Generate Case Input Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be GCI_URL.
    ##COMMON_GATEWAY_PROTOCOL_SERVER_ PORT## This is the URL of the Common Gateway Service till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CMNGTWYURL.
    ##SCORING_ PROTOCOL_SERVER_ PORT## This is the URL of the RAOR Application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be SCORING_URL.
    ##OFSS_WLS_PROTOCOL_SERVER_PORT## This is the URL of the OFS Watch list application till the port number.

    For example: <PROTOCOL:/ HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be OFSS_ WLS_URL.
    ##CS_PROTOCOL_ SERVER_PORT## This is the URL of the OFS Customer Screening Application till the port number.

    For example: <PROTOCOL:/HOSTNAME:PORT>.

    		 Mandatory only if KYC onboarding is used. If not, value must be CS_URL.
    ##COMM_LOG_PATH## This is the path of the KYC onboarding log file.

    For example: /scratch/ofsaaapp/KYC808DEV/apache-tomcat-8.0.47/logs.

    		 Mandatory only if KYC onboarding is used.
    Placeholder Name Significance and Expected Value Mandatory
    ##QTNR_RESP_URL## This is the URL of the OFS KYC onboarding service.

    The URL is <PROTOCOL:/HOSTNAME:PORT/CONTEXT_NAME>/questionnaire_api/questionnaires/ resume/<INFODOM>/en_US?appCode=OFS_KYC.

    		 Mandatory only if KYC onboarding is used. If not, value must be ##QTNR_ RESP_URL##.
    ##OFS_COMM_DATA_ TBSP## This is the table space for the common gateway. The value is COMM_DATA_TBSP. Mandatory only if KYC onboarding is used. If not, value must be ##OFS_COMM_DATA_TBSP##.
  10. Navigate to the OFS_BD_PACK/bin folder and execute setup.sh file using the following command: 
    $./setup.sh SILENT
  11. After Installation is successful, apply AAI patch by downloading the bug 33738222 from My Oracle Support.
  12. After the patch installation is successful, execute BD_Duplicate_Jar_Removal.sh script from $FIC_HOME.
  13. If the release is applied successfully, check the log file generated by verifying in the installation folder. Ignore ORA-00001, ORA-00955, ORA-02260, and ORA-01430 errors in the log file. In case of any other errors, contact My Oracle Support.

    Note:

    • The DMT migration utility is executed during BD installation to migrate the DMT metadata (PLC/Data Source/Data Mapping/Data File Mapping) to be persisted in tables instead of XML. You may be required to re-run the DMT migration utility in some scenarios. To identify whether to run the utility, how to run, and how to handle migration issues, see OFSAA DMT Metadata Migration Guide.
    • Ignore the below fatal error in the putty console while upgrading:

      Summary will be written to: ../log/ DMTMigrationUtilityReport.log

      Detailed logs can be found in: ../log/ DMTMigrationUtility.log FIC_HOME:/scratch/ofsaadb/BDECM811OCT/

      [Fatal Error] ETLLoader.properties:2:1: Premature end of file.

  14. Entry (DBNAME of Atomic Schema) must be added in the tnsnames.ora file on the OFSAA server.

    Note:

    • After Upgrade Run below scripts manually as post upgrade steps: $FIC_HOME/database/db_tools/bin.
      • ./run_dbbuilder_utility.sh $FIC_HOME/database/mantas_schema/delta/oracle/8.0/mantas8.1.2.0.0_delta.cfg
      • ./run_dbbuilder_utility.sh$FIC_HOME/database/bus_mkt_schema/delta/oracle/8.0/delta_plat8.1.2.0.0.cfg

      During installation, the PR_8.1.2.0.0_33645879.miner.sql script can fail with error code ORA-02303. This issue can be resolved by adding keyword FORCE to following string:

      CREATE OR REPLACE TYPE DEPWD_SAMT_EN_ROW FORCE AS OBJECT (

      This issue is to be fixed in release 8.1.2.1 ML.

    • Load the following scenarios manually using the sm_load utility available in the $FIC_HOME/database/db_tools/bin path.

      List of scenarios to be loaded:

      • ML-CIBPreviousAverageActivity.116000083.xml
      • ML-CashTransPossibleCTR.116000037.xml
      • ML-DepWDSameAmts.118860020.xml
      • ML-LargeReportableTrans.116000099.xml
      • ML-RapidMvmtFundsAllActivity.116000079.xml
      • ML-StructuringAvoidReportThreshold.116000046.xml
      • ML-StructuringAvoidReportThreshold.116000062.xml
      • ML-RoutingMultiLocations.118860012.xml (Before loading and executing the scenario, add it to the scnro.cfg file)
  15. For more information on securing your OFSAA Infrastructure, see the Security Guide in OHC Library.
  16. Add umask 0027 in the .profile of the UNIX account, which manages the WEB server to ensure restricted access permissions.
  17. Restart all the OFSAAI services. For more information, see the Start/Stop Infrastructure Services section in Starting/Stopping Infrastructure Services.
  18. Generate the application EAR/WAR file and redeploy the application onto your configured web application server. For more information on generating and deploying EAR/WAR file, see Creating and Deploying EAR/WAR File.
  19. Deploy the RPD and Catalog ORACLE ANALYTIC SERVER (OAS) 5.9 files available under $FIC_HOME/ORACLE ANALYTIC SERVER (OAS) 5.9 folder.
  20. For enabling TDE in case of a new installation, see the Configuring TDE in case of Upgradesection in Configuring TDE and Data Redaction in OFSAA.
  21. For enabling Data Redaction in case of a new installation, see the Enabling Data Redaction in case of Upgrade section in Configuring TDE and Data Redaction in OFSAA.

    Note:

    To enable newly licensed app from OFSA BD pack, see How to Enable Newly Licensed App after Upgrade to BD 8.1.2.0.0.

OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0

See the OFS ECM Installation Guide 8.1.2.0.0 for Pack on Pack Inplace Upgrade steps from OFS ECM 8.1.1.1.0 to OFS ECM 8.1.2.0.0.

OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0

See the OFS CRR Installation Guide 8.1.2.0.0 for Pack on Pack Inplace Upgrade steps from OFS CRR 8.1.1.1.0 to OFS CRR 8.1.2.0.0.