Oracle Financial Services Financial Crime and Compliance Management 6.2 Patch/Hotfix Readme File This document provides late-breaking or other information that supplements the Oracle Financial Services Financial Crime and Compliance Management 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.0UI Applicable Releases: Oracle Financial Services Financial Crime and Compliance Management 6.2 --------------------------------------------------------------- --------------------------------------------------------------- 1.0 Resolved Issues/Enhancements in Patch 6.2.2.0.0UI --------------------------------------------------------------- 18098023 - Financial Crime and Compliance Management 6.2 INTERIM RELEASE #2 (6.2.2.0.0) This Interim Release of FCCM is cumulative and includes all the enhancements and bug fixes done since v6.2 GA release. 17648534 - LOG FILE AND LOG PATH SHOULD BE MENTIONED IN INSTALLATION GUIDE - STAGE 3 17177792 - TASK 85 SHOULD BE DETAILED MORE IN THE INSTALLATION GUIDE. 17464914 - Unable to override the score on reopened KYC cases. 16462476 - SCENARIO MIGRATION UTILITY NOT MIGRATING SCORING CORRECTLY 17464933 - Clarification added to User Guides on the character counter feature on comment boxes on the UI 14116275 - Add KYC Related RISK ASSESSMENT AND CASE REPORTS 17029508 - TWO NEW Account PARAMETERS ADDED FOR ALOGRITHM BASED MODEL 16904132 - ENABLING AND DISABLING OF ALERT/CASE NARRATIVE BASED ON ALERT/CASE STATUS so that narratives cannot be edited on closed alerts/cases. 16786661 - Corrected some errors with availability of Related to Alert and Related to Focus options on some alert management business tabs. 16813055 - Improve case details to better display reason for accelerated review for KYC Cases. 16951567 - Additional KYC Role created to support 4 eyes approval process for KYC Cases 16974551 - Update ADDING EXISTING ENTITIES ON BUSINESS TABS to consider both real time business data and existing case entities. 13659372 - ADMIN TOOLS SHOULD ALLOW for inputting NEGATIVE SCORE INCREMENTS ACROSS Rules 17230705 - When the UseTaxidForUnrelatedPartyCode variable in BDF.xml is set to Y, then the BACK_OFFICE_TRXN. UNRLTD_PARTY_CD is set to NULL (which indicates both the accounts are related) though the ACCT. ACCT_TAX_ID of the Accounts involved in Back Office Transaction or CUST.TAX_ID for the Primary Customer of the Accounts 17454671 - When you search through Domain field in the Advance Search page of Alert/Case Management UI, the following error message is displayed "Invalid request/Error while processing request". 17456093 - The Email address and Phone numbers added through tabs in Case Management UI is not getting saved. --------------------------------------------------------------- 1.1 Known Issues/Enhancements in Patch 6.2.2.0.0UI --------------------------------------------------------------- 17482228: KYC ASSESSMENT AND CASE ASSESSMENT LIST SHOW SCORES HAVE 2 DECIMAL PLACES 18034781 - Print to PDF (Print Details or Print Summary) for a KYC Case is missing some details for KYC Risk Assessment Details for Rule Based Assessments. 18033721 - Clicking a linked case on the Involved Person tab's Linked Cases grid does not always take the user to the selected case. 18027700 - Selecting to include the Trade tab when Print to PDF (Print Details) from an alert results in a popup with a script error message. 18027695 - The Customer tab information is not included when selected during Print to PDF action (Print Details). 18026869 - For some alerts portions of the PDF resulting from the Print Details action may contain the label name along with the actual associated value in the value field. 18022256 - For some alerts portions of the PDF resulting from the Print Details action may contain the label name along with the actual associated value in the value field. 18021835 - Some grids displayed in the PDF resulting from the Print Details action may have column headers switched and not be reflective of the associated value. 17946696 - The KYC High Risk Customer report does not consider Risk Assessments with Risk score as 0 if the score filter is set Risk >= 0. 17654094 -Clicking ONLINE HELP ON PRINT DETAILS POP UP DISPLAYS ERROR MESSAGE 17653395 - Export to Excel for grids with stacked headers does not export the top level header. 17647180 - This will need to come from dev/test if rewrite or if include. Not sure of impact on client 17269066 - In the KYC Case List, if a user selects to sort on a column that does not contain unique values (such as score) and navigates to multiple pages in the list one after the other using the pagination function, the list page will cease to refresh to display the additional cases. 16953774 - Export to Excel for grids with stacked headers does not export the top level header. 13666884 - In the Manage Trusted Pair UI selecting and unselecting a record in the Trusted Pair List removes the near due/overdue indicator color formatting of the expiration date. 17407533 - INVALID REQUEST/ERROR WHILE PROCESSING REQUEST" message received when click online help. 17977409 - Linking a case to another case as a duplicate and then linking the same cases using the link and merge action will result in duplicate financial information being copied. 16743359 - The Scoring Rule Editor does not always successfully modify rule set scoring rules. Workaround: This issue is isolated to some instances of machines using Internet Explorer version 9. No workaround is available. This issue will be addressed in a future release. 13667214 - The Alert Details Matched Information row does not always display the scenario name for posted alerts. Workaround: Expand the Alert Context section to see the scenario name. 13667316 - The Sort option is not sorting correctly on columns with an amount value. Amount fields are sorted based on string sorted instead of numeric sorting 16542846 - When changing the view to other than 100% in Internet Explorer the UI may experience alignment and scrolling issues. 16604886 - If a user ignores the UI warning that the allowed number of characters entered for Financial tab Loss and Recovery has been exceeded the application does not prevent them from saving with that value. However, entered records are not being created in the database and are not available when viewing financial records. Workaround: This works as designed. Loss and Recovery columns have a length limit of 20 real integers and 8 decimal values in the database. User should adhere to the warning message and ensure meet the limits before saving. Prevention of save will be addressed in a future release. 16605941 - The display of user name versus user identifier throughout the UI in such areas as alert and case context and alert and case lists, as well as in audit records, is inconsistent and does not always reflect the installation configuration for display of user name versus user identifier in the UI. 16765828 - When attempting to close a KYC Case as a duplicate case, the user is incorrectly given the option to transfer financial information. 17420981 - INTERESTED_PARTY_EMP table is not getting populated after running the BDF Ingestion. 17269066 - If KYC cases listed in KYC case list page have same values in any of the column across different pages then the pagination will show same data as previous page. 17407533 - When FCCM UI is deployed in Weblogic server, then the Online Help icon displays the following error "Invalid request/error while processing request". 16831236 - There are performance issues related to retrieving alerts through the Alert Entity Search feature. 18069427 - Clients upgrading from ECM 6.1 to FCCM 6.2 will face issue while saving security attributes for any user in the Weblogic environment. Workaround: Remove 'xalan-2.7.1.jar' from the "/ficweb/webroot/WEB-INF/lib" path before performing step no. 3.3.A.10 of 'Steps to Apply' section related to creation and deployment of OFSAAI WAR/EAR. NOTE: This hotfix includes updates to the following files: 2.0 Pre-requisites: ------------------ 2.1 This hotfix requires the prior installation of OFSFCCM 6.2, Patch Installer 1.0.1.0.0, 6.2.2.0.0BD patch and Oracle Financial Services Analytical Applications Infrastructure 7.3.3.1.0 2.2 Before applying patch 6.2.2.0.0UI, verify that the KYC Information Domain creation and data model upload was done while installing FCCM 6.2 or 6.2.1 even if you are not using KYC feature (which is part of FCCM 6.2 and FCCM 6.2.1 installers). If not, then it is mandatorily requires to do the same to avoid issues with this patch or any other future patch releases. Please refer "Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) User Guide Release 7.3" for more details on how to perform the same manually. The KYC data model would be available in the FCCM 6.2 or 6.2.1 installer kits. 2.3 Before applying patch 6.2.2.0.0UI, if you are using KYC 2.0 then truncate all the records from the table 'fct_ra_accounts_prcng' of KYC atomic schema. 3.0 PATCH CONTENTS ------------------ The following files are included with this patch/hotfix: 6.2.2.0.0UI.tar.gz readme6.2.2.0.0UI.txt (this readme file) 3.1 The following subsystems are affected by this patch/hotfix: ficdb ficweb ftpshare AM 3.2 UPGRADE INSTRUCTIONS The upgrade instructions refer to the following directories: Name Description --------------------------- -------------------------------- Directory containing installed FCCM components Directory containing the patch tar.gz file Directory containing patch installer components 3.3 Steps to apply: ------------------- Cross Site Scripting Fix Instructions ------------------------------------- 1. Open ##OFSAA INSTALL DIR##/ficweb/webroot/conf/excludeURLList.cfg file and manually remove below entries and redeploy the war/ear /solution/cc/adminToolsRenderer.jsp /solution/cc/netVizRender.jsp /solution/cc/reportsForAlrt.jsp /solution/cc/reportsForCase.jsp /solution/cc/xmlExportForAlrt.jsp /solution/cc/xmlExportForCase.jsp /solution/cc/Aml_thrs_scr.jsp /solution/cc/viewNodeAndAlertDetails.jsp /solution/cc/RegRepSup.jsp /formsFramework/formsrenderer/MapRenderer.jsp /formsFramework/formsrenderer/UploadFileFrame.jsp /formsFramework/formsrenderer/tabRenderer.jsp /ExcelUpload/AMEUIndex.jsp /solution/am/Alert_List_New.jsp /solution/am/AM_Acc_Det.jsp /solution/am/AM_AlertSummary.jsp /solution/am/AM_Asyn_Buss_Trans.jsp /solution/am/AM_Audit.jsp /solution/am/AM_CB_Det.jsp /solution/am/AM_CNA.jsp /solution/am/AM_Corel_Det.jsp /solution/am/AM_Cust_Det.jsp /solution/am/AM_Detail.jsp /solution/am/AM_Disposition_tab.jsp /solution/am/AM_EE_Det.jsp /solution/am/AM_Emp_Det.jsp /solution/am/AM_Evidence.jsp /solution/am/AM_Financial_Det.jsp /solution/am/AM_help.html /solution/am/AM_HH_Det.jsp /solution/am/AM_IA_Det.jsp /solution/am/AM_Limit_to_Focus.jsp /solution/am/AM_MSR.jsp /solution/am/AM_MTP.jsp /solution/am/AM_Narrative.jsp /solution/am/AM_PromotCaseUtil.jsp /solution/am/AM_Relship_Det.jsp /solution/am/AM_StatusCheck.jsp /solution/am/AM_Tab_Button.jsp /solution/am/AM_UsrAtt.jsp /solution/am/AMEUIndex.jsp /solution/am/Aml_Det.jsp /solution/am/Aml_KeyMap.jsp /solution/am/Aml_Sup_Land.jsp /solution/am/Aml_thrs_scr.jsp /solution/am/Aml_TP_Updt.jsp /solution/am/amMessagesConstant.jsp /solution/am/AMUAIndex.jsp /solution/cm/caseSummary.jsp /solution/cm/CMG_AccountDetails.jsp /solution/cm/CMG_AuditDetails.jsp /solution/cm/CMG_CaseDetails.jsp /solution/cm/CMG_CaseSearchNList.jsp /solution/cm/CMG_CorrelationDetails.jsp /solution/cm/CMG_CorresBankDetails.jsp /solution/cm/CMG_CustomerDetails.jsp /solution/cm/CMG_EmployeeDetails.jsp /solution/cm/CMG_EvidenceDetails.jsp /solution/cm/CMG_ExtEntityDetails.jsp /solution/cm/CMG_FinancialDetails.jsp /solution/cm/CMG_HouseHoldDetails.jsp /solution/cm/CMG_InvestmentAdvisorDetails.jsp /solution/cm/CMG_LandingPage.jsp /solution/cm/CMG_NarrativeDetails.jsp /solution/cm/CMG_RelationshipDetails.jsp /solution/cm/CMG_SetSeession.jsp /solution/cm/CMG_TransactionDetails.jsp /solution/cm/cmMessagesConstant.jsp /solution/cm/MAN_SecurityAttributes.jsp /solution/cm/newCase.jsp /solution/cm/TabButton.jsp /solution/am/AM_AssociatedAlert.jsp /solution/am/AM_ERG_INST_DET.jsp /solution/am/AM_ERG_TRD_DET.jsp /solution/am/AM_EXECUTION_DET.jsp /solution/am/AM_HISTORY_DET.jsp /solution/am/AM_MKT_PRT_DET.jsp /solution/am/AM_NTRL_GAS_FLW_DET.jsp /solution/am/AM_ORDER_DET.jsp /solution/am/AM_PRTFO_MNG_DET.jsp /solution/am/AM_REGREP_DET.jsp /solution/am/AM_SECURITY_DET.jsp /solution/am/AM_TB_DET.jsp /solution/am/AM_TB_LIST.jsp /solution/am/AM_TR_DET.jsp /solution/am/AM_TRADE_DET.jsp /solution/am/AM_TRD_BLOTTER.jsp /solution/am/CC_AlertCaseList.jsp /solution/am/CC_CaseList.jsp /solution/am/CC_LandingPage.jsp /solution/am/User_Preference.jsp /solution/cm/CMG_AssociatedCase.jsp /solution/cm/CMG_AssociatedCases.jsp /solution/cm/CMG_InvolvedPartyDetails.jsp /solution/am/AM_Replay_Tab.jsp /solution/am/CC_AlertList.jsp /solution/cc/adminToolsRenderer.jsp /solution/cc/netVizRender.jsp /solution/cc/reportsForAlrt.jsp /solution/cc/reportsForCase.jsp /solution/cc/xmlExportForAlrt.jsp /solution/cc/xmlExportForCase.jsp /solution/cc/Aml_thrs_scr.jsp /solution/cc/viewNodeAndAlertDetails.jsp /solution/cc/RegRepSup.jsp /formsFramework/formsrenderer/MapRenderer.jsp /formsFramework/formsrenderer/UploadFileFrame.jsp /formsFramework/formsrenderer/tabRenderer.jsp /ExcelUpload/AMEUIndex.jsp /solution/am/Alert_List_New.jsp /solution/am/AM_Acc_Det.jsp /solution/am/AM_AlertSummary.jsp /solution/am/AM_Asyn_Buss_Trans.jsp /solution/am/AM_Audit.jsp /solution/am/AM_CB_Det.jsp /solution/am/AM_CNA.jsp /solution/am/AM_Corel_Det.jsp /solution/am/AM_Cust_Det.jsp /solution/am/AM_Detail.jsp /solution/am/AM_Disposition_tab.jsp /solution/am/AM_EE_Det.jsp /solution/am/AM_Emp_Det.jsp /solution/am/AM_Evidence.jsp /solution/am/AM_Financial_Det.jsp /solution/am/AM_help.html /solution/am/AM_HH_Det.jsp /solution/am/AM_IA_Det.jsp /solution/am/AM_Limit_to_Focus.jsp /solution/am/AM_MSR.jsp /solution/am/AM_MTP.jsp /solution/am/AM_Narrative.jsp /solution/am/AM_PromotCaseUtil.jsp /solution/am/AM_Relship_Det.jsp /solution/am/AM_StatusCheck.jsp /solution/am/AM_Tab_Button.jsp /solution/am/AM_UsrAtt.jsp /solution/am/AMEUIndex.jsp /solution/am/Aml_Det.jsp /solution/am/Aml_KeyMap.jsp /solution/am/Aml_Sup_Land.jsp /solution/am/Aml_thrs_scr.jsp /solution/am/Aml_TP_Updt.jsp /solution/am/amMessagesConstant.jsp /solution/am/AMUAIndex.jsp /solution/cm/caseSummary.jsp /solution/cm/CMG_AccountDetails.jsp /solution/cm/CMG_AuditDetails.jsp /solution/cm/CMG_CaseDetails.jsp /solution/cm/CMG_CaseSearchNList.jsp /solution/cm/CMG_CorrelationDetails.jsp /solution/cm/CMG_CorresBankDetails.jsp /solution/cm/CMG_CustomerDetails.jsp /solution/cm/CMG_EmployeeDetails.jsp /solution/cm/CMG_EvidenceDetails.jsp /solution/cm/CMG_ExtEntityDetails.jsp /solution/cm/CMG_FinancialDetails.jsp /solution/cm/CMG_HouseHoldDetails.jsp /solution/cm/CMG_InvestmentAdvisorDetails.jsp /solution/cm/CMG_LandingPage.jsp /solution/cm/CMG_NarrativeDetails.jsp /solution/cm/CMG_RelationshipDetails.jsp /solution/cm/CMG_SetSeession.jsp /solution/cm/CMG_TransactionDetails.jsp /solution/cm/cmMessagesConstant.jsp /solution/cm/MAN_SecurityAttributes.jsp /solution/cm/newCase.jsp /solution/cm/TabButton.jsp /solution/am/AM_AssociatedAlert.jsp /solution/am/AM_ERG_INST_DET.jsp /solution/am/AM_ERG_TRD_DET.jsp /solution/am/AM_EXECUTION_DET.jsp /solution/am/AM_HISTORY_DET.jsp /solution/am/AM_MKT_PRT_DET.jsp /solution/am/AM_NTRL_GAS_FLW_DET.jsp /solution/am/AM_ORDER_DET.jsp /solution/am/AM_PRTFO_MNG_DET.jsp /solution/am/AM_REGREP_DET.jsp /solution/am/AM_SECURITY_DET.jsp /solution/am/AM_TB_DET.jsp /solution/am/AM_TB_LIST.jsp /solution/am/AM_TR_DET.jsp /solution/am/AM_TRADE_DET.jsp /solution/am/AM_TRD_BLOTTER.jsp /solution/am/CC_AlertCaseList.jsp /solution/am/CC_CaseList.jsp /solution/am/CC_LandingPage.jsp /solution/am/User_Preference.jsp /solution/cm/CMG_AssociatedCase.jsp /solution/cm/CMG_AssociatedCases.jsp /solution/cm/CMG_InvolvedPartyDetails.jsp /solution/am/AM_Replay_Tab.jsp /solution/am/CC_AlertList.jsp Stylesheet Changing Instructions --------------------------------- 1. Shutdown the Application and Web Servers. 2. Open CustomLHSMenu.xml from /ficapp/common/FICServer/conf 3. Add below tag after >/> for menu item FCCM (Search for FCCM for finding out menu item) 4. Restart the Servers. A. Alert management/Case Management/Common Components Instructions --------------------------------------------------------------- 1. Shutdown the Web Server. Keep the Reveleus Application Server up and running as that is needed for Data Model upload activities. 2. Login to putty and make sure the logged in user has read/write permission to ficweb, ficdb and ftpshare folders. 3. Navigate to the path /patch_installer directory. 4. Execute "patchUtil.sh install" to install the patch. 5. When prompted for Patch Archive name, provide the complete file path (including file name as below) where the hotfix tar.gz file is located: /6.2.2.0.0UI.tar.gz 6. Navigate to the path /patch_installer/logs and check PatchUtil.log for any error while installing patch. If any error occurs during patch installation contact oracle support . 7. a.Edit the install.cfg file located in the /ficweb/AM/admin_tools/WEB-INF/classes/conf/mantas_cfg directory. Locate and comment the following lines: # sql.pool.analyst_pool.url=jdbc:apache:commons:dbcp:analyst_pool # sql.pool.analyst_pool.conn.url=@SQL_ANALYST_POOL_URL@ # sql.pool.analyst_pool.conn.driver=@SQL_ANALYST_POOL_DRIVER@ # sql.pool.analyst_pool.conn.user=@SQL_ANALYST_POOL_USER@ # sql.pool.analyst_pool.conn.password= # sql.pool.analyst_pool.dbcp.initialSize=10 # sql.pool.analyst_pool.dbcp.maxActive=50 # sql.pool.analyst_pool.dbcp.maxWait=3000 # sql.pool.miner_pool.url=jdbc:apache:commons:dbcp:miner_pool # sql.pool.miner_pool.conn.url=@SQL_MINER_POOL_URL@ # sql.pool.miner_pool.conn.driver=@SQL_MINER_POOL_DRIVER@ # sql.pool.miner_pool.conn.user=@SQL_MINER_POOL_USER@ # sql.pool.miner_pool.conn.password= # sql.pool.miner_pool.dbcp.initialSize=10 # sql.pool.miner_pool.dbcp.maxActive=50 # sql.pool.miner_pool.dbcp.maxWait=3000 Add the following lines on top: sql.pool.analyst_pool.url=java:comp/env/jdbc/@analyst@ sql.pool.miner_pool.url=java:comp/env/jdbc/@miner@ Replace the @analyst@ , @miner@ names with your respective data source names. The following two tokens are the data source names that need to be created in the web application console(Websphere/Weblogic or Tomcat) for the KDD_WEB and KDD_MNR schema. @analyst@ = your analyst data source name @miner@ = your miner data source name # config schema name for adminTools config.schema=@config_user@ @config_user@ Config user for the OFSAAI database instance. b. Edit the web.xml file located in the /ficweb/AM/admin_tools/WEB-INF directory and Locate the below two resource reference Tags under the . @analyst_pool_description@ jdbc/@analyst@ javax.sql.DataSource Container @miner_pool_description@ jdbc/@miner@ javax.sql.DataSource Container Replace the following names with your respective data source names. @analyst_pool_description@ = description for admintool analyst @analyst@ = your analyst data source name @miner_pool_description@ = description for admintool miner @miner@ = your miner data source name 8. Execute the create_at_war.sh script located at /ficweb/AM folder and redeploy the admin_tools.war file on the web application server. 9. If you have upgraded from ECM 6.1 to FCCM 6.2, remove 'xalan-2.7.1.jar' from the "/ficweb/webroot/WEB-INF/lib" path before performing the below step related to creation and deployment of OFSAAI WAR/EAR. Refer 18069427 in the known issues section for more details. 10. Once the above steps are done, create the OFSAAI EAR/WAR file and redeploy this new war on the web application server and Delete the contents of Temp folders of web application server. For example: for Websphere navigate to "profiles//temp" folder, For Tomcat, navigate to "work" folder and For Weblogic navigate to domains//servers/AdminServer/tmp folder C. Scenario Wizard Instructions ----------------------------- 1.Navigate to /ficweb/scenario wizard folder. 2.Verify whether swizard.war file is replaced or not in the path. 3.Take a back up of SMLiteWeb.war. 4.Start Web Server. 5.Run install.sh to create a new SMLiteWeb.war file and deploy the new SMLiteWeb.war 6. Stop Web Server. Note : For detailed steps how to Generate and deploy new SMLiteWeb.war ,please refer to Installation Guide - Stage 3, Chapter 3.Post Installation. D. KYC Instructions: ----------------- Steps to Replace the place holders for KYCINFODOM in xml files: 1. Start Application and Web Servers. Take a back up of OFSAAI EAR and undeploy the OFSAAI EAR. 2. Deploy the OFSAAI EAR after following the above steps. 3. Start Application and Web Servers. 4. Replace in the mentioned path /formsFramework/formsrenderer/clearcache.jsp and run the URL in Windows Explorer. 5. Excel Upload The DIM_ACCOUNT_TYPE Excel Upload definitions is modified. After the ECM 6.2.2 ML is applied, take backup of the DIM_ACCOUNT_TYPE table and also the data. Delete the data in the DIM_ACCOUNT_TYPE table and upload the data from the DIM_ACCOUNT_TYPE.xls sheet. Also the user can verify and update the data in the DIM_ACCOUNT_TYPE.xls sheet before the data is uploaded through excel upload. The DIM_ACCT_OPENING_MTHDS, MAP_ACCT_OPENG_METHODS and MAP_ACCOUNT_TYPE excel definitons are newly created. The user can verify and modify the data in the DIM_ACCOUNT_OPENING_METHODS.xls, MAP_ACCT_OPENG_METHODS.xls and MAP_ACCOUNT_TYPE.xls if required before the excel upload is done. Some new records are added into the below mentioned excel upload data files, the data should be uploaded from this sheets into the respective tables. After the data is loaded, make sure the score per model per customer type should be equal to 100. APPLN_RISK_RATING_PARAMS.xls VW_APPLN_RISK_RATING_PARAMS.xls 6. Replacement of the Place holders Take backup of the below mentioned files. The files will be present in the //ficdb/bin/ AccountOpenDoc.sh Case_Assignment.sh IDV.sh KYC_File_Rename.sh NNS.sh WLS_FuzzyMatch.sh Make sure the below mentioned place holders are replaced in the above mentioned files, ##FICDB_HOME## --> Should be replaced with the path upto ficdb folder in the AAI installed area. for eg., /home/gsh/OFSAAI/ficdb/ ##JAVA_HOME## --> Should be replaced with the actual java home of your setup ##WEB_SERVICE_URL## --> Should be replaced with the url which is used to access the application. Note: For instructions on undeploying and deploying the EAR file, refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7.3. OBIEE Instructions: ----------------- A. Proceed with ECM6.2.2.rpd if you do not have any configuration done in ECM6.2.rpd. 1.Copy the ANALYTICS_REPORT.zip from following path /OBIEE. Place it under /instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalog 2. If there is a file name with "ANALYTICS_REPORT", Rename it (Ex: ANALYTICS_REPORT_OLD) 3.Unzip the file ANALYTICS_REPORT.zip by executing below command. unzip ANALYTICS_REPORT.zip 4.Copy the ECM_6.2.2.rpd from following path /OBIEE/repository and place it in local machine. 5.Open the EM (Ex : http://hostnmae : 7001/em) , then select Business Intelligence -> coreapplication from left panel and Click on Deployment -> Repository from right panel. 6.Click on Lock and Edit configuration , then choose the RPD by clicking the browse button, Enter password "Mantas61". 7.Click on Activate Changes. 8.Restart the opmn by executing below command from /instances/instance1/bin ./opmnctl restartproc B. Proceed to upgrade RPD from ECM6.2 to ECM6.2.2 by following given below steps: Important: 1. If there are no customizations on ECM 6.2 RPD then deploy the FCCM 6.2.2 RPD available with the FCCM 622 /OBIEE/repository. If there are customizations on ECM 6.2 RPD, follow these steps. 2. The Oracle BI Administration Tool version 11.1.1.6.7 should be installed before performing these steps. Step1 : Open the DEV RPD (6.2 RPD) with the Admin tool while offline. 1. Expand UIC_73 then expand CASEMNG. 2. Select KDD_REVIEW_OWNER and KDD_REVIEW_OWNER_CASE_TYPE simultaneously with the help of ctrl key and right click and go to the Physical Diagram . Selected Ojects Only. 3. Select the arrow and delete the arrow using delete key. 4. Go to the Diagram.New Join. 5. Press Left click on KDD_REVIEW_OWNER of mouse and drag up to KDD_REVIEW_OWNER_CASE_TYPE. 6. It will open one popup window, select the OWNER_SEQ_ID in column section from both the side. 7. Select OK button. 8. Close the Physical Diagram window. 9. Click the save button and then yes and then close. 10. Go to File. Close. Step2 : To generate the patch.xml file, follow these steps: 1. Open the DEV RPD (6.2.2 RPD) with the Admin tool while offline. 2. Go to File -> Compare. 3. Select the PROD RPD ( 6.2 RPD) as Original Repository. 4. Click No. The system will start comparing. 5. Click Create patch and choose the name and path to save the xml file. 6. Click OK . The file is saved Step3: 1: In the Administration Tool, PROD RPD ( 6.2 RPD) in offline mode. In other words, open the repository on which you want to apply the patch. 2: Select File, then select Merge. The Merge Repository Wizard appears. For Merge Type, select Patch Repository Merge. 3. Select the PROD RPD ( 6.2 RPD) repository by clicking Select next to Original Master Repository. Select Repository from the submenu to select a binary repository file in RPD format. 4: Enter the repository password for the original repository. 5: Click Select next to Patch File. Browse to select the patch file you want to apply, then click Open. The patch file must be in XML format. Patch password should be blank. 6: Below the Save Merged Repository as , give the repository password should be Mantas61 7: Click on the Next button. 8: After some time another window will open. 9: In conflict section, go to Decision column . 10: In Decision column , for each row one drop down box will be appear on click of Row Cell of Decision column. 11: Select only "Modified (A)" or "By Property". 12: After selecting all the rows Finish button will be enabled. 13: Select the check box on check consistency of merged rpd. 14: Then click on finish(Error should not come).It will create rpd with name of PROD RPD(1).rpd. Rename the file and deploy. ================================================================================================================================================================================================================================================================================================================================================== (c) 2014 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.