Oracle Behavior Detection Platform 6.2 Patch/Hotfix Readme File This document provides late-breaking or other information that supplements the Oracle Behavior Detection Platform 6.2 documentation. For information about Oracle Financial Services Software, Inc., visit http://www.oracle.com/industries/financial_services/index.html. ------------------------------------------------- Patch 6.2.2.0.0BD Applicable Releases: Behavior Detection Platform 6.2 ------------------------------------------------- 1.0 Resolved Issues in Patch 6.2.2.0.0BD 1.1 Issue 18098034- Behavior Detection Platform INTERIM RELEASE #2 (6.2.2.0.0) This Interim Release of FCCM BDP is cumulative and includes all the enhancements and bug fixes done since v6.2 GA release. 1.2 Issue 17502029: Watchlist task fails with an ORA-00942: table or view does not exist error. 1.3 Issue 17499761: The Scenario loading utility (sm_load.sh) deletes any custom jobs which have job_id more than the product.id.range.min=113000000 as set in the install.cfg file. 1.4 Issue 17444163: HDC jobs should use dbms_gather_stats in the P_ANALYZE procedure. 1.5 Issue 17385429: HDC job has been updated for better performance. 1.6 Issue 16674424: For attestation, Outside Business Activity/ Private Security Transaction datamap files has been added for ingestion. 1.7 Issue 17230705: The UNRLTD_PARTY_CD flag derivation should use the UseTaxIDForUnrelatedParty configuration for back office transactions. NOTE: This hotfix includes updates to the following files: kddcore.jar preprocessor.jar OutsideBusinessActivity.xml PrivateteSecurityTransaction.xml dbtools.jar CR_6.2.2_pta.ingest.sql PR_6.2.2_17528469.miner.sql delta_plat6.2.2.cfg CR_6.2.2_16674068.business.sql CR_6.2.2_pta.business.sql PR_6.2.2_17080868.miner.sql mantas6.2.2_delta.cfg CR_6.2.2_metadata.mantas.sql CR_6.2.2_pta.mantas.sql PR_6.2.2_17339364.case.sql HDC_DataBags.xml KeysByTableName.xml BackOfficeTransaction_UnrelatedPartyCodeUpd.xml actionframework.jara common.jar message.dat NOTE: This patch requires the prior installation of Behavior Detection Framework 6.2. 2.0 Upgrade Instructions -------------------------- PATCH CONTENTS The following files are included with this patch/hotfix: 6.2.2.0.0BD.tar.gz (this readme file) The following subsystem is affected by this patch/hotfix: Ingestion Manager Database Behavior Detection Framework Services UPGRADE INSTRUCTIONS The upgrade instructions refer to the following directories: Name Description --------------------------- -------------------------------- Directory containing installed Oracle Behavior Detection Framework components Directory containing the patch tar.gz file To apply this patch/hotfix, follow these instructions: On the Behavior Detection Framework server: 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.2.2.0.0BD.tar.gz 4. For the token replacements, the following needs to be replaced in fuzzy_match.sh: @KDD_FUZZY_PRODUCT_HOME@ with $USER_INSTALL_DIR$/bdf/fuzzy_match (where $USER_INSTALL_DIR$ is the root installation directory) @JVM_PATH@ with $jdk_home$/jre/lib/amd64:$jdk_home$/jre/lib/amd64/server (where $jdk_home$ is the path to the JDK) The following needs to be replaced in install.cfg: @STOPWORD_PATH@ with $USER_INSTALL_DIR$/bdf/fuzzy_match/share (where $USER_INSTALL_DIR$ is the root installation directory) @LOG_DIR@ with $fuzzy_log_dir$ (where $fuzzy_log_dir$ is the desired path for the fuzzy matcher log files) @FUZZY_TEMP_DIR@ with $USER_INSTALL_DIR$/bdf/data/temp (where $USER_INSTALL_DIR$ is the root installation directory) 4 b. Change the permissions for the $USER_INSTALL_DIR$/bdf/fuzzy_match/bin/fuzzy_match.sh as follows: chmod +x fuzzy_match.sh 5. Edit the env.sh file located at /bdf/scripts and append $BDF_ROOT/fuzzy_match/bin this has been included in the PATH variable. So the PATH vriable should be: PATH=$ORACLE_HOME/bin:$BDF_ROOT/fuzzy_match/bin:$PATH 6. Edit the BDF.xml file located at /bdf/config/install and ensure the following tokens are replaced correctly with the corresponding values. @DB_URL@ - Database URL for JDBC connections made by BDF components. The content and format of this value is specific to the database vendor and the vendor database driver. Example: jdbc:oracle:thin:@solitaire.mantas.com:1521:D1O9L2 @DB_INSTANCE@ - Database instance to connect to on the database servers. Typically, the instance name matches the database name portion of the DB.Connection.URL. Example: D1O9L2 @DB_USER@ - Database User that Java Ingestion components use when connecting with the database. Example : INGEST_USER @ALG_DB_USER@ - Database user for running Behavior Detection post-processing jobs. Example: KDD_ALG @MANTAS_SCHEMA@ - Schema name for the Oracle Mantas database schema. Typically, an Oracle client uses the default name of "MANTAS." BDF accesses the MANTAS schema when allocating sequence IDs to ingested records. Example: Mantas @MARKET_SCHEMA@ - Schema name for the MARKET database schema. Typically, an Oracle client uses the default name of "MARKET." Data Ingestion stores market data related records in the MARKET schema. Example: MARKET @FIRM_SCHEMA@ - Business Schema user Schema name for the BUSINESS database schema. Typically, an Oracle client uses the default name of "BUSINESS." Data Ingestion stores business data related records in the BUSINESS schema. Example: BUSINESS @CONFIG_SCHEMA@ - Account that the OFSAAI uses to connect to the database. Example:config_user=REVELEUS. In case for OFSAAI has already been installed using separate user then provide SAME user id for this parameter @CASE_SCHEMA@ - Account that the Web Application uses to connect to the databasefor Cases . Example:case_schema_owner=CMREVMAN This is the case Management database user which is one of the four atomic schemas of Financial crime and compliance management stage3 @ACCT_TRUST_FROM_CUST@ - Flag that tells the Data Ingestion process whether the account risk should be exempt or trusted based on the exempt or trusted status of the customers risk. The value Y indicates that the BDF process will consider the customer exempt and trust risk in calculating the account risk. The value N will not consider the customer exempt and trusted risk in calculating the account risk. Valid Values are Y and N. @JURISDICTION@ - Default Jurisdiction Jurisdiction to assign the derived entities and derived addresses. Example:AMEA @USETAXID@ - Instruction to Ingestion Manager when to use tax identifiers(both account and customer) in determining unrelated journals.If a substitute tax identifier is used when the accounts or customers tax identifier is unknown,then unrelated accounts may appear to be related when tax identifiers are considered.This variable enables the Ingestion Manager to ignore substitute tax identifiers. Y Ingestion Manager is to use tax identifiers N Ingestion Manager is not to use tax identifiers @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 OFSBDF client. Example:base_country=US @PROCESS_FOREIGN_FL@ - Flag that tells the Data Ingestion process whether it should populate the Foreign field in the front office transaction table or if it should leave it blank for the firm to populate. Y Run the OFSBDFmappings. N Use the provided Value. @PROCESS_BANK_TO_BANK@ - Flag that tells the Data Ingestion process whether it should populate the bank to bank transfer field in the front office transaction table or if it should leave it blank for the firm to populate. Y Run the OFSBDFmappings. N Use the provided Value. @PROCESS_TRXN_XREF@ - Flag that tells the Data Ingestion process whether it should populate BUSINESS.TRXN_PARTY_XREF TABLE or leave it blank Y Populate the BUSINESS.TRXN_PARTY_XREF TABLE N Do not populate the BUSINESS.TRXN_PARTY_XREF TABLE @TP_RISK_REVIEW_FLAG@ - If the flag is set to .N., the datamaps for trusted pair risk review is not executed. If the value is set to Y datamaps for trusted pair risk review is also executed. This variable should not be set to Y when trusted pairs are loaded through the DIS file. Example: N 7. Keep a record of the builds and patches applied to each Oracle Behavior Detection Platform server, and the date/time they were applied. 8. Send an email message to mantas_support_us@oracle.com indicating that the patch/hotfix has been applied. On the Ingestion Manager server: -------------------------------- 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.2.2.0.0BD.tar.gz 4. Keep a record of the builds and patches applied to each Oracle Behavior Detection Platform server, and the date/time they were applied. 5. Send an email message to mantas_support_us@oracle.com indicating that the patch/hotfix has been applied. On the Database Server: ----------------------- 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.2.2.0.0BD.tar.gz 4a. Edit the install.cfg file located at database/db_tools/mantas_cfg directory and locate the following section: # Specify product version purge_product_verion= Update the above to : # Specify product version purge_product_version= 4b. Edit the install.cfg file located at database/db_tools/mantas_cfg directory and locate the "LOAD" sub section under "GENERAL SCENARIO MIGRATION SETTINGS" section. a. Add the below line: load.score.update=N The above flag should be set to N if a scenario should be loaded without wiping out the existing scoring rules. It should be set to Y if the scoring rules should be updated. b. Replace the following line: dbscript.execution.users=(system|business|mantas|market|miner|ingest|report|kdd|algorithms|case|config|fatca|ctr|kyc) with the following line: dbscript.execution.users=(system|business|mantas|market|miner|ingest|report|kdd|algorithms|case|config|fatca|ctr|kyc|fsdf) 5. Keep a record of the builds and patches applied to each Oracle Behavior Detection Platform server, and the date/time they were applied. 6. Send an email message to mantas_support_us@oracle.com indicating that the patch/hotfix has been applied. On the Services subsystem ------------------------- 1. Change to the /patch_installer directory. 2. Type "patchUtil.sh install" to install the patch. 3. When prompted, provide the complete directory path where the hotfix tar.gz file is located: /6.2.2.0.0BD.tar.gz 4. Edit the env.sh file located at /services/scripts directory and ensure the following tokens are replaced correctly with the corresponding values. @SERVICES_ROOT@ - Absolute path upto the services directory (e.g., /mnt/devops_0/dba/ECM622CYCLE2/BDP622CYCLE2/services) @MANTAS_EXT_DIR@ - Absolute path for the stage 1 install directory (e.g., /mnt/devops_0/dba/ECM622CYCLE2/BDP622CYCLE2) @TNS_ADMIN@ - absolute path to the location of tnsnames.ora file (e.g., /scratch/oracle/app/oracle/product/11.2.0/dbhome_2/network/admin) @ORACLE_HOME@ - Path to the Oracle Home Directory @JRE_HOME@ - path to the jdk root directory (e.g., /scratch/oracle/jdk1.6.0_37) 5. Keep a record of the builds and patches applied to each Oracle Behavior Detection Platform server, and the date/time they were applied. 6. Send an email message to mantas_support_us@oracle.com indicating that the patch/hotfix has been applied. =============================== (c) 2013 by Oracle Financial Services Software, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission of Oracle Financial Services Software, Inc.