Home

Installation Guide - Oracle Documentation

Contents

1. INGEST SCHEMA US This variable is used to identify the Ingest Schema name ER INGEST SCHEMA Replace the placeholder with Ingest Schema Name _USER For example lt Variable name INGEST_SCHEMA_USER gt INGEST_USER lt Variable gt Refer to the Installation Checklist point 4 for the schema name FSDF_SCHEMA_USER This variable is used to identify the FSDF Schema name FSDF_SCHEMA_USE Rit Replace the placeholder with FSDF Schema Name For example lt Variable name FSDF_SCHEMA_USER gt FSDF_USER lt Variable gt Refer to the Installation Checklist point 4 for the schema name KDD_ALGORITHM KDD_ALG_ROLE This variable is used to identify the Algorithm Role name Replace the placeholder with Algorithm Role Name For example lt Variable name KDD_ALGORITHM gt KDD_ALGORITHM lt Variable gt Refer to the Installation Checklist point 4 for the role name Installation Guide Stage 3 Release 6 2 1 27 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 6 Placeholders in Layer DATABASE Continued KDD ANALYST KDD_ANALYST_R This variable is used to identify the Analyst Role name OLE Replace the placeholder with Analyst Role Name For example lt Variable name KDD_ANALYST gt KDD_ANALYST lt Variable gt Refer to the Installat
2. OBIEE REPORTS OBLEE F This variable is used to identify whether Oracle Business Intelligence Enterprise Edition OBIEE needs to be integrated in the setup Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 0 if OBIEE reports related files are not be installed e 1 if OBIEE reports related files are to be installed For example Variable name OBIEE_REPORTS gt 1 lt Variable gt 32 Installation Guide Stage 3 Release 6 2 1 CHAPTER 2 Installation Activities This chapter covers the following topics e Installing OFSFCCM Solution in Silent Mode e Verification of Installation Logs Installing OFSFCCM Solution in Silent Mode OFSFCCM comprises the components that are installed in the OFSAAI Database Application and Web layers If OFSAAT is installed in multi tier architecture then the OFSFCCM installer must be invoked on each machine that hosts different tiers This chapter describes the installation process in which OFSAAT is installed using single tier option Por single tier installation the installer must be invoked only once on the machine that hosts all the OFSAAI platform tiers Note For multi tier installation the installation must be done in the following order e Application Layer e Database Layer The Database layer installation must be performed after Application Layer e Web Layer The Web Layer installation
3. Subsequently the installation process starts After successful installation the following message is displayed Installation Complete Verification of Installation Logs Once you complete the installation process check the installation logs for any errors 1 SolutionSetup_InstallLog 1og which is created in OFSFCCM installed directory FIC HOME Ww 2 SolutionsLOG 1og which is created in OFSFCCM installed directory FIC HOME 3 FCCM62_LOG 1og which is created at the path from where installation is triggered Note If you observe any warnings non fatal errors fatal errors exceptions ORA error reported in either of the logs notify the OFSECM support personnel Do not proceed with the installation process until all the issues ate addressed Upon successful installation proceed to post installation steps as explained in the following chapters Ignore the following warning message coming in SolutionSetup InstallLog log where the placeholders lt ftpshare gt in the message is replaced with the actual ftpshare area path Additional Notes WARNING Source lt ftpshare gt STAGE ExcelUpload INFODOM does not exist Note For RAC DB JDBC url is required in the format jdbc oracle thin DESCRIPTIO ADDRESS PROTOCOL TCP HOST Server Host Name PORT 1521 CONNECT DATA SERVER DEDICATED SERVICE NAME Database Name 34 Installation Guide Stage 3 Rel
4. The OFSECM Home page is displayed Click FCCM and then click the Administration Menu and select the Manage Parameters and click Manage Common Parameters Choose Parameter Category as UI and Parameter Name as OBIEE Set Attribute 2 Value PROTOCOL OBIEE SERVER NAME PORT Note PROTOCOL is the web page access PROTOCOL http or https and OBIEE SERVER NAME is the FQN fully qualified name host name of the of the server where OBIEE is installed PORT is the PORT number used in OBIEE installation It may change based on the OBIEE version Enter the correct PORT number if it is not 9704 Placeholder variables are mentioned between angle brackets Update the placeholders with actual value Verify Attribute 4 Value It must be the OFSECM application URL If the same OFSECM application is deployed on different machines then modify the OFSECM Application URL in Attribute 4 Value appropriately Installation Guide Stage 3 Release 6 2 1 51 Accessing Reports through OFSFCCM Application Chapter 5 Deploying Analytic Reports and Threshold Analyzer Accessing Reports through OFSFCCM Application For more information on Accessing Reports refer to the Aert Management User Guide Note For Bug 13713131 An error displays when a user clicks on the pie chart or tries to access the Threshold Analyzer reports This is an issue with Solaris OS Apply Solaris patch 130558
5. 2 Navigate to FIC HOME Uninstall FCCM62 directory and execute the following command Uninstall App sh 3 Input the Configuration Schema Password when prompted 4 After running Uninstaller on all the layers follow these steps a Uninstall the OFSAAI ear file deployed on the Web Application Server b Navigate to FIC HOME ficweb on server hosting WEB Layer and execute the following command to recreate the ear file ant sh c Deploy the new ear file on Web Server Note For more information on deploying the EAR file refer to the Oracle Financial Services Analytical Applica tions Infrastructure Installation and Configuration Release 7 3 5 The OFSFCCM Uninstaller does not perform the following activities a It does not delete Infodom and Segment created as part of OFSFCCM installation b It does not revert DataModel Upload done as part of OFSFCCM installation c It does not delete ETL Applications and Sources created as part of OFSFCCM installation 6 If you are re installing OFSFCCM after running the un installer keep the same InfoDom and Segment Names for all the atomic schemas For consecutive installation replace the following parameters in GRC InstallConfig xml with 0 before starting installation next time since they already exist in the database Mark the following parameters as 0 in GRC InstallConfig xml file for next time installation after successful uninstallation Installation Guide Stage 3 Release
6. 3 Post Installation a Navigate to Network Settings and change the Network Proxy Settings to Direct Connection b Navigate to Settings under Temporary Internet Files and perform the following steps i Check the option to Keep temporary files on my computer ii Click Delete Files to clear the Java cache Restarting Web Application server Once all the above steps are completed restart the Web Application Server Creating Users to Access OFSFCCM Solution Create users to access OFSFCCM application For more information refer to sections About OFSECM User Authentication and About User Setup in the Administration Guide Perform Administrative activities for OFSECM Access the OFSFCCM UI as ECM Administrator and perform all the steps given in the following sections of Administration Guide e About Configuring Access Control Metadata e Mapping Users To Access Control Metadata e About Scenario Manager Login Accounts e About Changing Passwords for System Accounts e About Configuring File Type Extensions e About Configuring File Size e About Configuring Status To User Role Table Note Once Security Attributes mapping is completed for the ECM Administrator user restart OFSAAI and Web Application servers before accessing the Admin Tools application Perform Configurations for OFSECM Access the OFSFCCM UI as ECM Administrator and perform all the steps given in the following sections of Configuration Guide m Configuring the Ba
7. 53 OFSAAI APP Layer on Machine A OFSAAI DB Layer on Machine B and OFSAAI WEB Layer on Machine e 53 APPENDIX B ETL Source CrealloD nois hotte a aient 55 APPENDIX C Configuration for the KYC File Rename sh eene 57 Steps for Creating the Access Permission for Copying the File from One Machine to Another eent 57 Calling the Shell Script for Copying the Files from One Path to Another een 58 APPENDIX D Watchlist FuzzyMatCch csssscscsssscssssccecsevcssssnveaseocessrenssaneecsaneenssaes 59 Calling the Shell Script for Copying the Files from One Path to Another eene 60 vi Installation Guide Stage 3 Release 6 2 1 List of Figures Fisute 1 Deployment Atchitectultes ii asiscissstesscscssesssotesnosaasevenovecsesensovocasvosssvasesusestsovasusustonbessovensosasesus onbesstbasanbesabeduoeiederitoas 2 Figure 2 Multi tiet Configutatlofi iet EES 58 Figure 3 Single ter Configutati n 3 5 is ete ee RR EE Ee 58 Figure 4 Multisti jConfiguratlOTius cde hos iens met edite eene 60 Figure 5 5inglestier ConfIpufatiOn nb ebd menit iva ii e Du e etie eerte ree eb eed 60 Installation Guide Stage 3 Release 6 2 1 vii List of Figures viii Installation Guide Stage 1 Release 6 2 1 List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Conventions Dsed in this EmteeSA xiii Enyitonment RUE 3 Installation Checklist 1e e
8. 5KYC Variable VariableGroup Refer to the nstallation Checklist point 4 for the schema name VariableGroup name FSDF DB DETAILS ATOMIC SCH R NAME EMA USE E SDF_USER This variable is used to identify the fourt Atomic Schema For FCCM the fourth Atomic schema is FSDF Schema Replace the placeholder with FSDF Schema Name For example lt VariableGroup name FSDF_DB_DETAILS gt lt Variable name ATOMIC SCHEMA USER NAME FSDF Variable VariableGroup Refer to the nstallation Checklist point 4 for the schema name 16 Installation Guide Stage 3 Release 6 2 1 Populating the GRC_InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued VariableGroup name DATABASE SCHEMA DETAILS BUSINESS SCHEMA U BUSINESS_USER This variable is used to identify the Business Schema name SER tt Replace the placeholder with Business Schema Name For example lt Variable name BUSIN ER gt BUSINESS lt Variable gt ESS SCHEMA US Refer to the nstallation Checklist point 4 for the schema name VariableGroup name LOG DETAILS APP LAYER LOG PAT H APP_LOG_PATH This variable is used to identify Application Layer log path to store logs for all front end
9. 6 2 1 43 Chapter 4 Uninstalling OFSFCCM Table 8 Placeholders in GRC InstallConfig xml Variable Preferred Value Description VariableGroup name PRE INSTALLATION PRE INSTALL 0 This variable is used to identify whether the installer will perform the following pre Installation activities 1 Infodom and Segment Creation for all atomic schemas Data Model Upload for KYC and FSDF atomic schema ETL Application Source creation for KYC atomic schema Replace this placeholder with 0 For example VariableGroup name PRE INSTALLATION Variable name PRE_INSTALL gt 0 lt Variable gt VariableGroup Note In case OFSFCOM is being installed second time after successfully un installing then keep this parameter as O since it is a onetime activity TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 1 ActionGroup 0 This variable is used to identify the Alert Management name CREATE INFOD Information Domain to be created by the installer OM Replace this placeholder with 0 For example lt ActionGroup name CREATE_INFODOM flag 0 gt Note In case OFSFCOM is being installed second time after successfully un installing then keep this parameter as 0 since it is a onetime activity TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 2 ActionGroup 0 This variable is used to identify the Case Management name CREATE INFOD
10. 740 permissions The Data model folder contains the following folders FSDF DataModel KYC DataModel These folders contain the rescpective XMLs All other files must be copied in binary mode Setup sh and GRC_InstallConfig xml must be copied in text mode 17 Create a copy of GRC InstallConfig xml as GRC InstallConfig xml bak in the L same directory and add values as in GRC_InstallConfig xml System specific details 18 Populate GRC InstallConfig xml O For more information refer to section Populating the GRC_InstallConfig xml File on page 8 19 Install OFSFCCM solution For more information refer to section Installing OFSFCCM L1 Solution in Silent Mode on page 33 20 Verify Installation logs for any error For more information refer section Verification of O Installation Logs on page 34 OFSFCCM Post Installation 21 Perform post installation steps For more information refer to Chapter 3 Post Installation on page 37 22 Create users to access OFSFCCM solution and other administrative activities For more information refer to Administration Guide 23 Ensure to access OFSFCCM URL with server s Fully Qualified Domain Name FQDN O while opening OFSFCCM UI Installation Guide Stage 3 Release 6 2 1 7 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Populating the GRC InstallConfig xml File This section explains the steps
11. Customer KYC and Financial Services Data Framework FSDF schema The Alert and Case Management data models are created during the Stage 1 installation while the KYC and FSDF schema data models are created during Stage 3 installation e Stage 2 OFSAAI Installation For this installation we can either use the user created during Stage1 installation config user or any other manually created user In case you ate using a manually created user then Stage1 and Stage2 installations can be done in parallel There is no dependency for Stage 1 and Stage 2 except that both the installations must use the same database instance e Stage 3 OFSFCCM Installation This guide talks about OFSFCCM product installation which requires Stage 1 and Stage 2 installations to be completed successfully Who Should Use this Guide The Installation Guide Stage 2 is designed for use by the OFSFCCM Installers and OFSFCCM Administrators Their roles and responsibilities include the following e OFSFCCM Installer This user installs and configures the OFSFCCM product at the deployment site e OFSFCCM Administrator This user performs OFSFCCM related administrative activities maintains user accounts and performs mapping of User Groups internally mapped with roles to users Installation Guide Stage 3 Release 6 2 1 xi About this Guide How this Guide is Organized Thelnstallation Guide Stage includes the following chapters Chapter 1 Prepa
12. File names and extensions Process names Code sample including keywords and variables within text and as separate paragraphs and user defined program elements within text lt Variable gt Substitute input value Installation Guide Stage 3 Release 6 2 1 xiii About this Guide xiv Installation Guide Stage 3 Release 6 2 1 CHAPTER 1 Pr epar ing to Install This chapter provides information about system hardware and software requirements and pre installation activities This chapter includes the following topics e Deployment Architecture e Environment Details e Installation Checklist e Populating the GRC InstallConfig xml File Installation Guide Stage 3 Release 6 2 1 1 Deployment Architecture Chapter 1 Preparing to Install Deployment Architecture Figure 1 shows the flow of data through the components of the Oracle Financial Services Financial Crime and Compliance Management solution Web Browser Interface OFSAAI SG Workstation S 1 Application Server Socket connection Web Server JDBC amp Vendor Web Application Database Data Ingestion Behavior Server Server Detection Server Figure 1 Deployment Architecture 2 Installation Guide Stage 3 Release 6 2 1 Environment Details Chapter 1 Preparing to Install Environment Details The OFSFCCM solution will be installed using the hardware and software environments as described in following tab
13. GRC InstallConfig xml File Chapter 1 Preparing to Install Table 4 Placeholders in Layer GENERAL Continued VariableGroup name INFODOM 2 INFODOM NAME INFODOM_2 This variable is used to specify the Case Management Information Domain Infodom name Replace this placeholder with Case Management Infodom name in either of the following cases e f already created from OFSAAI front end Or To be created by Installer Make sure to follow these conventions Consider the following while giving a new Information Domain Name e The Information Domain name specified is of minimum 6 characters long e The Information Domain name does not contain any special characters or extra spaces e The maximum length of Information Domain must be less than or equal to 20 characters For example Variable name INFODOM_NAME gt CMINFO lt Variable gt SEGMENT CODE SEGMENT_2 This variable is used to specify the Case Management Segment Code Replace this placeholder with the Case Management Segment Code in either of the following cases e f already created from OFSAAI front end Or To be created by the Installer Make sure to follow these conventions Consider the following while giving a new Segment Code e The segment code is unique e There are no special characters and extra spaces in the code entered e The Segment Code must be less than or equal to 10 characters For exampl
14. Installation Guide Stage 3 Release 6 2 1 Post Installation Steps Chapter 5 Deploying Analytic Reports and Threshold Analyzer 15 16 17 lt This Configuration setting is managed by Oracle Enterprise Manager Fusion Middle ware Control lt ClientSessionExpireMinutes gt 210 lt ClientSessionExpireMinutes gt lt InIFrameRenderingMode gt allow lt InIFrameRenderingMode gt lt Security gt Restart OBIEE server Modify Instanceconfig xml available at FMW HOME instances instancel config OracleBIPresentationServicesComponent coreappli cation obipsl instanceconfig xml location Add the tag under the Security Section in Instance Config xml lt InIFrameRenderingMode gt allow lt InIFrameRenderingMode gt So that it looks like below after adding above tag lt Security gt lt This Configuration setting is managed by Oracle Enterprise Manager Fusion Middle ware Control lt ClientSessionExpireMinutes gt 210 lt ClientSessionExpireMinutes gt lt InIFrameRenderingMode gt allow lt InIFrameRenderingMode gt lt Security gt Start the Oracle Process Manager and Notification Server OPMN services by executing the following command from lt OBIEE Installed Directory gt instances instancel bin opmnctl startall Post Installation Steps After installing the OBIEE server follow these steps d 2 Log in as OFSECM Admin User with valid username and password
15. OBIEE Analytics port gt analytics From LHS menu click Get Started and select Download BI Desktop Tools Installation Guide Stage 3 Release 6 2 1 47 Disabling the Cache Feature in OBIEE Server Chapter 5 Deploying Analytic Reports and Threshold Analyzer Disabling the Cache Feature in OBIEE Server Login to the Enterprise Manager and perform the following steps 1 Click Business Intelligence folder from the left hand side menu and select coreapplicaiton For more information refer Figure 1 Click Capacity Management and then select the Performance tab Click Lock and Edit Configuration tab To disable the Cache uncheck the Cache Enabled Option Click Apply and Activate Changes nn KR o H Click Restart to apply recent changes Change Default Repository Password Copy ECH 6 2 rpd from FIC HOME OBIEE Repository to the Windows machine where the OBIEE Windows administration client is installed Change the default password for the repository by following these steps 1 Open the Repository using the OBIEE Windows administration client from Windows machine From the File menu select Open and click Offline Browse to the Repository on Windows machine The Oracle BI Administration Tool ECM 6 2 rpd windows is displayed 2 Enter default Repository password Mantas61 To change the default password follow these steps 1 From File menu choose Change Password 2 E
16. and back end components that will be created by OFSAAI For example Information Domain Replace this placeholder with an absolute path For example lt Variable name APP_LAYER_LOG_PATH gt home ftpshare APP_logs lt Variable gt DB_LAYER_LOG_PATH DB_LOG_PATH This variable is used to identify the Database Layer log path to store logs for all front end and back end components that will be created by OFSAAI For example lt Variable name DB_LAYER_LOG_PATH gt home ftpshare DB_logs lt Va riable gt TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 1 ActionGroup name CREATE INFO DOM INFODOM_FLAG_ 144 This variable is used to identify the Alert Management Information Domain to be created by the installer Allowable values for this placeholder are 0 and 1 Replace this placeholder with 1 If Infodom for Alert Management is to be created 0 If Infodom for Alert Management is already created For example lt ActionGroup name CRE AT E INFODOM flag 1 gt Installation Guide Stage 3 Release 6 2 1 17 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued INFODOM DESCRIPTI ON INFODOM DESC 1 This variable is used to identify the Alert Management Information Domain description This value is required only
17. if INFODOM_FLAG_1 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a description for Alert Management Information Domain by following these conventions e Ensure that the description field is not empty e Ensure that the description field should not exceed 100 characters For example Variable name INFODOM DESCRIPTION Alert Management Infodom lt Variable gt DATABASE NAME H4 DB NAME 144 This variable is used to identify the Database Name for Alert Management Information Domain This value is required only if INFODOM_FLAG_1 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a name for the Alert Management Database by following these conventions e There are no special characters and extra spaces in the name e The length of database Name must not exceed 20 characters For example Variable name DATABASE NAME gt AMDB lt Variable gt TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 2 ActionGroup name CREATE INFO DOM INFODOM_FLAG_ 2H This variable is used to identify the Case Management Information Domain to be created by the installer Allowable values for this placeholder are 0 and 1 Replace this placeholder with 1 if Infodom for Case Management is to be created 0 if Infodom for Case Management is already created For example ActionGroup name
18. in as the INGEST_USER Replace the KYC_USER place holder with name of the KYC ATOMIC schema CREATE SYNONYM DIM_CUSTOMER_TYPE for KYC_USER DIM_CUSTOMER_TYPE CREATE SYNONYM DIM_JURISDICTION for KYC_USER DIM_JURISDICTION CREATE SYNONYM FCT_TP_WLS_REQUESTS_PRCNG for KYC_USER FCT_TP_WLS_REQUESTS_PRCNG CREATE SYNONYM FCT_WLS_RESULT_STG for KYC_USER FCT_WLS_RESULT_STG Installation Guide Stage 3 Release 6 2 1 59 Calling the Shell Script for Copying the Files from One Path to Another Appendix C Configuration for the KYC File Rename sh Calling the Shell Script for Copying the Files from One Path to Another 6 Open the KYC_File_Rename sh which is present in the path lt OFSAAI Installed Area gt ficdb bin of DB layer and configure the paths and details as mentioned in the following screenshots After the changes are done move the file to the ficdb bin area Provide executable permissions to the file 7 Execute the task through the batch execution screen of the OFSAAI application and check if the files are moved to the destination path Modify the below mentioned SHARE PATH az per your setup provide the path upto fipshare SMARE PATH home gsh ftpshare STAGE KYCsource e Modify the path according to your setup export SHARE PATH 5 echo 55HABE PATH Creating o Mew
19. must be performed after Database Layer installation Note For more information refer to Appendix A Installation Order for Multi Tier Installation of OFSFCCM for installation order of OFSFCCM solution To install OFSFCCM in silent mode follow these steps 1 Execute profile to set the environment variables using the following command ksh profile 2 Navigate to the OFSFCCM installer kit directory 3 Execute the following command Setup sh SILENT Note Installation for Solaris Box displays an incorrect message lt Stage3 Installer Kit Setup bin not found The file is present The installation continues and ends successfully Ignore this message Installation Guide Stage 3 Release 6 2 1 33 Verification of Installation Logs Chapter 2 Installation Activities 4 Enter the following passwords raised by the installer LOG Starting up Enter Config Schema Password Enter BUSINESS Schema Password Enter MARKET Schema Password Enter Alert Management Schema Password Enter KDD WEB Schema Password Enter KDD Schema Password Enter KDD MNR Schema Password Enter DB UTIL Schema Password Enter KDD ALGORITHM Schema Password Enter INGEST Schema Password Enter FSDF Schema Password Enter OFSBDP User Password Enter Case Management Schema Password Enter KYC Atomic Schema Password Note In case of single tier installation the installer will not prompt for the Config Schema Password
20. no special characters and extra spaces in the code entered e The maximum length of Segment Code must be less than or equal to 10 characters For example Variable name SEGMENT_CODE gt KYCSEG lt Variable gt 12 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 4 Placeholders in Layer GENERAL Continued VariableGroup name INFODOM 4 INFODOM NAME INFODOM_4 This variable is used to specify the FSDF Information Domain Infodom name Replace this placeholder with FSDF Infodom name in either of the following cases e If already created from OFSAAI front end Or To be created by the Installer Make sure to follow these convention while giving a new Information Domain Name e The Information Domain name specified is of minimum 6 characters long e The Information Domain name does not contain any special characters or extra spaces e The maximum length of Information Domain name must be less than or equal to 20 characters For example Variable name INFODOM_NAME gt FSDFINFO lt Variable gt SEGMENT CODE SE GM ENT_4 This variable is used to specify the FSDF Segment Code Replace this placeholder with FSDF Segment Code in either of the following cases e lif already created from OFSAAI front end Or To be created by t
21. 0 gt Report Schema refer report user in OFSBDP Installed Directory database db tools mantas cfg db variables cfg file For more details refer to the Installation Guide Stage 1 c KYC1 1DEV 179 gt Alert Management Schema d MNTS583 gt Alert Management Schema e UIC 73 gt CaseMng connection pool gt Case Management Schema f UIC 73 gt Security connection pool gt Alert Management Schema Select Save option from the File menu The following message is displayed Do you want to check global consistency Click Yes The following message is displayed Consistency check didn t find any errors warning or best practices violations Click OK Installation Guide Stage 3 Release 6 2 1 49 Deploying OFSFCCM Report Analytics Chapter 5 Deploying Analytic Reports and Threshold Analyzer Deploying OFSFCCM Report Analytics To deploy Analytic Reports follow these steps I 11 12 13 14 S E En COX cem Stop Oracle Process Manager and Notification Server OPMN services by executing the following command from OBIEE Installed Directory instances instancel bin opmnctl stopall Change the value in Nqscon ig ini file located at lt FMW_HOME gt instances instancel config OracleBIServerComponent coreapplication_obis1 directory From EVALUATE SUPPORT LEVEL 0 To EVALUATE SUPPORT LEVEL 2 Copy AN
22. 19 to solve this issue 52 Installation Guide Stage 3 Release 6 2 1 APPENDIX A Installation Order for Multi Tier Installation of OFSFCCM If OFSAAT is installed in a multi tier architecture then installation order of OFSFCCM on different machines hosting OFSAAI Layer s will depend on the OFSAAI Installation architecture as mentioned below OFSAAI APP DB Layer on Machine A and OFSAAI WEB Layer on Machine B 1 Execute installer on Machine A with APP_LAYER and DB_LAYER flags as 1 WEB_LAYER flag as 0 2 Execute installer on Machine B with APP_LAYER and DB_LAYER flags as 0 HWEB_ LAYER flag as 1 OFSAAI APP Layer on Machine A and OFSAAI DB WEB Layer on Machine B 1 Execute installer on Machine A with APP_LAYER flag as 1 DB_LAYER and WEB_LAYER flags as 0 2 Execute installer on Machine B with APP_LAYER flag as 0 DB_LAYER and WEB_LAYER flags as 1 OFSAAI APP WEB Layer on Machine A and OFSAAI DB Layer on Machine B 1 Execute installer on Machine A with APP_LAYER flagas 1 DB_LAYER and WEB_LAYER flags as 0 2 Execute installer on Machine B with DB_LAYER flag as 1 APP_LAYER and WEB_LAYER flags as 0 3 Execute installer on Machine A with WEB_LAYER flag as 1 APP_LAYER and DB_LAYER flags as 0 OFSAAI APP Layer on Machine A OFSAAI
23. ALYTICS REPORT folder from FIC_HOME OBIEE and place under lt OBIEE Installed Directory instances instancel bifoundation OracleBIPresentationServicesComponent core application obipsl catalog Login into Enterprise Manager click the Business Intelligence folder at left hand side and select coreapplication then click on Deployment tab Click the Repository tab Click on Lock and Edit Configuration tab Click Close on the Confirmation pop up window In the Upload BI Server Repository Section browse the repository file from the Windows machine Enter the new repository password in the Repository Password and Confirm Password text boxes In BI Presentation Catalog section provide the Catalog Location as OBIEE Installed Directory instances instancel bifoundation OracleBIPresentationServicesComponent core application obipsl catalog ANALYTICS REPORT Click Apply Click Activate Changes and close the activate changes pop up window Click Close on the Confirmation pop up window Modify OBIEE Installer Directory instances instancel config OracleBIPresentationServicesComponent coreapplication obip sl instanceconfig xml as below From Security lt This Configuration setting is managed by Oracle Enterprise Manager Fusion Middle ware Control lt ClientSessionExpireMinutes gt 210 lt ClientSessionExpireMinutes gt lt Security gt To lt Security gt 50
24. CREATE INFODOM flag 1 gt 18 Installation Guide Stage 3 Release 6 2 1 Populating the GRC_InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued INFODOM DESCRIPTI INFODOM_DESC_ This variable is used to identify the Case Management Information ON 248 Domain description This value is required only if amp TNFODOM FLAG 2 4 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a description for Case Management Information Domain by following these conventions e Ensure the description field is not empty e Ensure the description field should not exceed 100 characters For example Variable name INFODOM DESCRIPTION Case Management Infodom lt Variable gt DATABASE NAME T4DB NAME 24 This variable is used to identify the Database Name for Case Management Information Domain This value is required only if TNFODOM FLAG 2 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a name for the Case Management Database by following these conventions e There are no special characters and extra spaces in the name e The length of database name must not exceed 20 characters For example Variable name DATABASE NAME CMDB Variable TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 3 ActionGroup INFODOM_F
25. CRIPTION ADDRESS LIST ADDR ESS PROTOCOL TCP HOST DBSERVER1 ORACLE COM port 1521 ADDRESS PROTOCOL TCP HOST 1 DBSER VER2 ORACLE COM gt PORT 1521 LOAD BALANCE no FA ILOVER yes CONNECT DATA SERVICE NAME dbname Note In RAC DB ETL application and sources are not created by the installer perform Appendix B to create the same FICMASTER_DRIVER DB_DRIVER Replace this placeholder with the OFSAAI Configuration Schema Database Driver for the connection purpose For example lt Variable name FICMASTER_DRIVER gt oracle jdbc driver Oracle Driver lt Variable gt Note Refer to the value of DEFAULT_DRIVER parameter in the file DbynamicServices xml under FIC APP HOME conf for value of this parameter FICMASTER USER CONFIGURATION Replace this placeholder with the value of OFSAAI Configuration _USER Schema user For example lt Variable name FICMASTER_USER gt REVELEUS lt Variable gt Refer to the nstallation Checklist point 10 for the schema name VariableGroup name DATABASE SCHEMA DETAILS Installation Guide Stage 3 Release 6 2 1 25 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 6 Placeholders in Layer DATABASE Continued BUSINESS SCHE
26. DB Layer on Machine B and OFSAAI WEB Layer on Machine C 1 Execute installer on Machine A with APP_LAYER flag as 1 DB_LAYER and WEB_LAYER flags as 0 2 Execute installer on Machine B with DB_LAYER flap as 1 APP_LAYER and WEB_LAYER flags as 0 3 Execute installer on Machine C with WEB_LAYER flag as 1 APP_LAYER and DB_LAYER flags as 0 Installation Guide Stage 3 Release 6 2 1 53 Appendix E Installation Order for Multi Tier Installation of OFSFCCM 54 Installation Guide Stage 3 Release 6 2 1 APPENDIX B ETL Source Creation Create the following applications File2Table_Load FicMaster KYCApplication BusinessSchema OracleSchema NOTE The Application Name and Data Source names are case sensitive and should be created as specified Ensure that folders are created with the Data Source Name in the ftpshare STAGE area in the application and database layer Create the following data sources FileTable A Flat File Source pointing to the source database to hold the F2T Definitions The date format should be set as mm dd yyyy ConfigSource An RDBMS Soutce pointing to the Configuration database to hold the configuration information The date format should be set as mm dd yyyy KYCsource An RDBMS Source pointing to the KYC Atomic Schema to hold the T2T Definitions The date format should be set as mm dd yyyy Busin
27. DF Database by following below conventions e There are no special characters and extra spaces in the name e The length of database Name should not exceed 20 characters For example Variable name DATABASE NAME FSDF DB lt Variable gt 22 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued ActionGroup T4MODEL UPLOAD This variable is used to identify whether Data Model Upload for FSDF name DATA MODEL FLAG 2144 is to be done through the Installer UPLOAD Allowable values for this placeholder are 0 and 1 Replace this placeholder with 1 if Data Model Upload for FSDF is to be done through the Installer 0 if Data Model Upload for FSDF is already completed For example ActionGroup name DATA MODEL UPLOAD flag 1 gt DATAMODEL TYPE T4DM TYPE 24 This variable is used to identify the type of Data Model Upload for FSDF that is to be done through the Installer This value is required only if 4 MODEL UPLOAD FLAG 2 and PRE_INSTALL has been replaced by 1 Replace this placeholder with the type of DataModel upload to be performed Allowable values are 0 O SLICED Model Upload For example Variable name DATAMODEL TYPE 0 Variable LOGICAL UPLOAD LOGICAL_UPLOA This variable is used to identify if the Data Mo
28. D_SCHEMA_USER KDD_USER This variable is used to identify the KDD Schema name Replace the placeholder with KDD Schema Name For example Variable name KDD_SCHEMA_USER gt KDD lt Variable gt Refer to the nstallation Checklist point 4 for the schema name 26 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 6 Placeholders in Layer DATABASE Continued KDD MNR SCHEMA U KDD_MNR_USER This variable is used to identify the KDD MNR Schema name SER Replace the placeholder with MNR Schema Name For example lt Variable name KDD_MNR_SCHEMA_USER gt KDD_MNR lt Variable gt Refer to the Installation Checklist point 4 for the schema name DB_UTIL_USER DB_UTIL_USER This variable is used to identify the DB UTIL Schema name Replace the placeholder with DB UTIL Schema Name For example lt Variable name DB_UTIL_USER gt DB_UTIL_USER lt Variable gt Refer to the Installation Checklist point 4 for the schema name A DD ALG SCHEMA U KDD_ALG_USER This variable is used to identify the Algorithm Schema name SER 3 Replace the placeholder with Algorithm Schema Name For example lt Variable name KDD_ALG_SCHEMA_USER gt KDD_ALG lt Variable gt Refer to the nstallation Checklist point 4 for the schema name
29. Information Domain to be created by the installer OM Replace this placeholder with 0 For example lt ActionGroup name CREATE_INFODOM flag 0 gt Note In case OFSFCCM is being installed a second time after successfully un installing then keep this parameter as 0 since it is a onetime activity 44 Installation Guide Stage 3 Release 6 2 1 Chapter 4 Uninstalling OFSFCCM Table 8 Placeholders in GRC InstallConfig xml Continued TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 3 ActionGroup 0 This variable is used to identify the KYC Information Domain to name CREATE INFOD be created by the installer OM Replace this placeholder with 0 For example lt ActionGroup name CREATE INFODOM flag 0 gt Note In case OFSFCOM is being installed a second time after successfully un installing then keep this parameter as 0 since it is a onetime activity ActionGroup 0 This variable is used to identify whether the Data Model Upload name DATA MODEL U for KYC is to be done through the Installer PLOAD Replace this placeholder with 0 For example lt ActionGroup name DATA MODEL UPLOAD flag 0 gt Note In case OFSFCOM is being installed a second time after successfully un installing then replace this placeholder with 0 ActionGroup 0 This variable is used to identify whether the ETL application and name ETI CREATION sourc
30. LAG_ This variable is used to identify the KYC Information Domain to be name CREATE_INFO 3 created by the installer DOM Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 if Infodom for KYC is to be created e 0 if Infodom for KYC is already created For example ActionGroup name CREATE INFODOM flag 1 gt INFODOM DESCRIPTI INFODOM_DESC_ This variable is used to identify the KYC Information Domain ON 34H description This value is required only if INFODOM_FLAG_3 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a description for KYC Information Domain by following these conventions e Ensure that the description field is not empty e Ensure that the description field should not exceed 100 characters For example Variable name INFODOM_DESCRIPTION gt KYC Infodom lt Variable gt Installation Guide Stage 3 Release 6 2 1 19 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued DATABASE NAME DB_NAME_3 This variable is used to identify the Database Name for KYC Information Domain This value is required only if INFODOM_FLAG_3 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a name for the KYC Database by following these conventions e There are no special charac
31. MA BUSINESS_USER This variable is used to identify the Business Schema name USER tt Replace the placeholder with BUSINESS Schema Name For example lt Variable name BUSINESS_SCHEMA_USER gt BUSINESS lt Variable gt Refer to the nstallation Checklist point 4 for the schema name ARKET_SCHEMA_US MARKET_USER This variable is used to identify the Market Schema name Replace the placeholder with Market Schema Name For example lt Variable name MARKET_SCHEMA_USER gt MARKET lt Variable gt Refer to the nstallation Checklist point 4 for the schema name ALERT_MANAGEMENT ALERT_MANAGEM This variable is used to identify the Alert Management Schema _SCHEMA_USER ENT_USER name Replace the placeholder with the Alert Management Schema name For example lt Variable name ALERT_MANAGEMENT_SCHEMA_USER gt AM lt Variable gt Refer to the nstallation Checklist point 4 for the schema name KDD_WEB_SCHEMA_U KDD_WEB_USER This variable is used to identify the WEB Schema name Replace the placeholder with WEB Schema Name For example lt Variable name KDD_WEB_SCHEMA_USER gt KDD_WEB lt Variable gt Refer to the nstallation Checklist point 4 for the schema name KD
32. ORACLE Installation Guide Stage 3 Oracle Financial Services Anti Money Laundering Fraud Trading Compliance Broker Compliance Energy and Commodity Trading Compliance Enterprise Case Management Know Your Customer FATCA Management Release 6 2 1 September 2013 ORACLE FINANCIAL SERVICES Installation Guide Stage 3 Oracle Financial Services Anti Money Laundering Fraud Trading Compliance Broker Compliance Energy and Commodity Trading Compliance Enterprise Case Management Know Your Customer Release 6 2 1 September 2013 Document Control Number 9MN12 62110009 Document Number IGST3 13 FCCM 0009 6 2 1 01 Oracle Financial Services Software Inc 1900 Oracle Way Reston VA 20190 Document Number IGST3 13 FCCM 0009 6 2 1 01 First Edition September 2013 Copyright 1996 2013 Oracle and or its affiliates All rights reserved Printed in U S A 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 Trademarks Oracle is a registered trademark of Oracle Corporation and or its affiliates Other names may be trademarks of their respective owners Oracle Financial Services Software Inc 1900 Oracle Way Reston VA 20190 Phone 703 478 9000 Fax 703 318 6340 Internet www oracle com financialservices Contents LiS
33. SAAI is installed is RAC 0 if Database on which OFSAAI is installed is not RAC For example lt Variable name IS_RAC gt 0 lt Variable gt TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 4 ActionGroup name CREATE INFO DOM INFODOM_FLAG_ 4 This variable is used to identify the FSDF Information Domain to be created by the installer Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 fInfodom for FSDF is to be created e 0 if Infodom for FSDF is already created For example ActionGroup name CREATE INFODOM flag 1 gt INFODOM DESCRIPTI ON INFODOM DESC A3 This variable is used to identify the FSDF Information Domain description This value is required only if INFODOM_FLAG_4 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a description for FSDF Information Domain by following these conventions e Ensure the description field is not empty e Ensure the description field should not exceed 100 characters For example Variable name INFODOM_DESCRIPTION gt FSDE Infodom lt Variable gt DATABASE_NAME DB_ NAME 4 This variable is used to identify the Database Name for FSDF Information Domain This value is required only if INFODOM_FLAG_4 and PRE_INSTALL has been replaced by 1 Replace this placeholder with a name for the FS
34. TER USER CONFIGURATIO Replace this placeholder with the value of OFSAAI Configuration Schema N_USER user For example lt Variable name FICMASTER_USER gt REVELEUS lt Variable gt Refer to the Installation Checklist point 10 for the schema name VariableGroup name DATABASE SCHEMA DETAILS BUSINESS SCHEMA BUSINESS_USE This variable is used to identify the Business Schema name USER REH Replace the placeholder with BUSINESS Schema Name For example lt Variable name BUSINESS_SCHEMA_USER gt BUSINESS lt Variable gt Refer to the Installation Checklist point 4 for the schema name 30 Installation Guide Stage 3 Release 6 2 1 Populating the GRC_InstallConfig xml File Chapter 1 Preparing to Install Table 7 Placeholders in layer WEB Continued MARKET SCHEMA U MARKET_USER This variable is used to identify the Market Schema name SER Replace the placeholder with Market Schema Name For example Variable name MARKET SCHEMA USER 2MARKET Variable Refer to the nstallation Checklist point 4 for the schema name ALERT MANAGEMEN ALERT_MANAGE This variable is used to identify the Alert Management Schema name T SCHEMA USER ENT_USER IS Replace the placeh
35. allation and Configuration Release 7 3 Note The backup must be kept until the successful installation of the solution OFSFCCM Pre Installation 12 Prior to installation ensure that sufficient free temp space minimum 1 GB free is available in tmp directory of unix server hosting OFSAAI 6 Installation Guide Stage 3 Release 6 2 1 Installation Checklist Chapter 1 Preparing to Install Table 3 Installation Checklist Continued 13 Ensure that the Oracle database instance is up and running O 14 Ensure that the database instance parameter processes is set to a minimum value of 1000 For more information refer to the Installation Guide Stage 1 OFSFCCM Installation 15 Once you have downloaded the Installer from e delivery or support oracle com refer to the following instructions to unzip the downloaded contents 1 Copy the downloaded Installer zip file contents to your server in Binary mode 2 Provide execute permissions to Installer zip file For example chmod 751 lt Installer zip file gt 3 To unzip Installer zip file using this utility run the following command For example unzip a Installer zip file gt 16 Navigate to Unzipped Installer Directory OFSFCCM v6 2 1folderandcopy Setup bin Setup sh validateXMLinputs jar log4j xml GRCInstall_Config xml and Data Model folder containing DataModel files to the machine that hosts OFSAAI and provide
36. as per the OFSAAI Installation option or multi tier followed while installing the OFSAAI platform Allowable values for this placeholder are 0 and 1 Replace this e 1 if DATABASE Layer component is to be installed e 0 if DATABASE Layer component is not to be installed Replace the place holder with 1 in case OFSAAI was installed as In case OFSAAI was installed as multi tier mode this value needs to be set according to the OFSAAI DATABASE layer installed on e Replace the placeholder with 1 for the machine hosting OFSAAI DATABASE layer e Replace the placeholder with 0 for the machine NOT hosting OFSAAI DATABASE layer Layer name DATABASI p flag 1 VariableGroup name DATABASE DETAILS 24 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 6 Placeholders in Layer DATABASE Continued DATABASE URL DB_URL Replace this placeholder with OFSAAI Configuration Schema Database URL for the connection purpose For example lt Variable name DATABASE_URL gt jdbc oracle thin DBSERVER OR ACLE COM 1521 0RCL Variable Refer to the value of DEFAULT CONNECTION URL parameter in the file DynamicServices xml under FIC App HOME conf for value of this parameter If you are using RAC database then provide the URL in below format jdbc oracle thin DES
37. b SCENARIO WIZARD and follow these steps 1 Execute install sh When prompted for password enter the KDD MNR Schema password Note Refer to the Installation Checklist point 4 for more information 2 Deploy the context name war file for example SMLiteWeb war available at FIC HOME ficweb SCENARIO WIZARD as an application on your Web Application Server While deploying war file keep context name as SMLiteWeb Note At a moment of time only one instance of Scenario Wizard will run on one Application server While launching the Scenario Wizard if you find any exception pop up saying java rmi bind exception or java rmi unknownhost exception follow these Steps a Stop the SMLiteWeb war b Navigate to deployed area gt SMLiteWeb WEB INF classes conf mantas_cfg install cfg c In install cfg change the token to some other port which is not occupied d Define rmiPort By default keep it 1099 rmiPort 1099 e Restart the server Note Por instructions on deploying the EAR file refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 Por Front end access the following settings must be changed on the client side for the Scenario Wizard to work on Windows XP Windows 7 1 Navigate to Java Control Panel 2 Under the General tab ensure the following two settings 40 Installation Guide Stage 3 Release 6 2 1 Restarting Web Application server Chapter
38. ctory gt bdf scripts lt Variable gt VariableGroup name TABLESPACE_1 28 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 6 Placeholders in Layer DATABASE Continued DATA TABLE SPACE DATA_TABLESPA Replace this placeholder with KYC Data Tablespace Name CE 144 For example Variable name DATA TABLE SPACE 2KYC DATA Variable Note It should be the same as the value of KYC Data Tablespace name created during the OFSBDF installation For more details refer to APPENDIX D OFSBDF Data Model Variables of Installation Guide Stage 1 INDEX TABLE SPAC INDEX_TABLESP Replace this placeholder with KYC INDEX Tablespace Name ACE 1d t For example Variable name INDEX TABLE SPACE 2KYC INDEX Variable Note It should be the same as the value of KYC Index Tablespace name created during the OFSBDF installation For more details refer to APPENDIX D OFSBDF Data Model Variables of Installation Guide Stage 1 VariableGroup name ADMIN TOOLS CONTEXT NAME ADMIN CONTEXT NA ADMIN_TOOLS_C Replace this placeholder with a string to be used as context name ME ONTEXT for Admin Tools for deployment purpose For example lt Variable name ADMIN_CONTEXT_NAME gt admin_tools lt Va
39. del Upload for FSDF is D_2 to be Logical This value is required only if MODEL_UPLOAD_FLAG_2 and PRE_INSTALL has been replaced by 1 Replace this placeholder with the type of DataModel upload to be performed Allowable values are 0 For example Variable name LOGICAL_UPLOAD gt 0 lt Variable gt DATAMODEL_FILE_PA DM_FILE_PATH_ This variable is used to identify the type of Data Model file path used TH 21H for FSDF data model upload This value is required only if amp MODEL UPLOAD FLAG 244 and PRE_INSTALL has been replaced by 1 Replace this placeholder with the absolute path of DataModel file For example Variable name DATAMODEL FILE PATH home FCCMkit Data Model FSDF DataModel FCCM Staging Release62 xml Va riable gt Installation Guide Stage 3 Release 6 2 1 23 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Layer DATABASE The Layer DATABASE Layer name DATABASE gt contains the following placeholders which must be configured for installation of Database Layer as one of its component Table 6 Placeholders in Layer DATABASE Variable name PLACEHOLDERS DESCRIPTION name DATABASE placeholder with single tier mode this machine For example Layer DB_LAYER This variable is used to Identify FCCM Database Layer component to be installed on this machine
40. e Variable name SEGMENT CODE CMSEG Variable Installation Guide Stage 3 Release 6 2 1 11 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 4 Placeholders in Layer GENERAL Continued VariableGroup name INFODOM 3 INFODOM NAME INFODOM_3 This variable is used to specify the KYC Information Domain Infodom name Replace this placeholder with KYC Infodom name in either of the following cases e If already created from OFSAAI front end Or To be created by the Installer Make sure to follow these conventions Consider the following while giving a new Information Domain Name e The Information Domain name specified is of minimum 6 characters long e The Information Domain name does not contain any special characters or extra spaces e The maximum length of Information Domain name must be less than or equal to 20 characters For example Variable name INFODOM_NAME gt KYCINFO lt Variable gt SEGMENT CODE SEGMENT_3 This variable is used to specify the KYC Segment Code Replace this placeholder with KYC Segment Code in either of the following cases e If already created from OFSAAI front end Or To be created by the Installer Make sure to follow these conventions Consider the following while giving a new Segment Code e Enter a unique segment code There are
41. e Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 While configuring OFSAAI do not perform the following configuration since FCCM 6 2 1 installer will perform it during installation Chapter 4 Post Installation Configuration e Section 4 1 Configure Resource Reference m Sub Section 4 1 1 Configure Resource Reference in Infrastructure Web Application gt 4 1 1 1 Configure web xml e Section 4 5 Additional Configurations m Sub Section 4 5 7 Configure Information Domain schema privileges While configuring OFSAAI do perform additional configurations since FCCM 6 2 1 requires it Chapter 4 Post Installation Configuration e Section 4 5 Additional Configurations m Sub Section 4 5 1 Configure FTP SFTP e Section 4 5 4 SFTP Configuration for Excel Document Upload m Sub Section 4 5 18 Configure HTPs Certificate information 9 Ensure that OFSAAI application server is up and running before installing the OFSFCCM O Application Layer 10 Note down the OFSAAI configuration schema User ID and Password L1 For more details refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 11 Take the back up of the following L1 OFSAAI Configuration Schema Config schema OFSAAI Installed directory S FIC HOME For more details refer to the Oracle Financial Services Analytical Applications Infrastructure Inst
42. e not required for a single tier configuration follow steps from 4 to 5 only for single tier 1 Execute the command ssh keygen t rsa in the machine from where the files are to be copied machine where the ficdb layer of OFSAAI is installed ssh keygen t rsa Generating public private rsa key pair Enter file in which to save the key home gsh ssh id rsa just press Enter Enter passphrase empty for no passphrase just press Enter Enter same passphrase again just press Enter Your identification has been saved in home gsh ssh id_rsa Your public key has been saved in home gsh ssh id rsa pub The key fingerprint is 23 b1 27 c8 23 a3 73 ea a8 3 7a 71 85 61 59 59 gsh ofsaa 2 Copy this id rsa pub file which is created in the path home gsh ssh into the Destination machine in the path home gsh ssh id rsa pub This file has to be moved manually from one machine to another machine 3 Navigate to the path home gsh ssh in the machine where the files are to be copied and execute the below commands cat id rsa pub home gsh ssh authotized keys chmod 700 home gsh ssh authotized keys Note The paths are according to our setup when the ssh keygen t rsa is executed the paths of your setup will be displayed below the command Installation Guide Stage 3 Release 6 2 1 57 Calling the Shell Script for Copying the Files from One Path to Another Appendix C Configuration for the KYC File Rename s
43. e unix user ID and O password used for OFSBDF 6 2 1 installation Note Make sure that F IC_HOME should not be the same as lt OFSBDF_Installed Directory gt For more information refer to the Installation Guide Stage 1 4 Note down the following OFSBDF schemas with a valid User ID and Password and Role L1 Names Business schema business schema owner Market schema market schema owner Alert Management Schema mantas schema owner Web Schema web user KDD Schema kdd schema owner KDD MNR Schema tools user DB UTIL Schema db util user Algorithm Schema server user Ingest Schema Ingest schema Owner FSDF Schema sdf schema owner KYC Schema kyc schema owner Case Management Schema case schema owner Note Refer to OFSBDF Installed Directory database db tools mantas cfg db variables cfg file for schema names written against the variables provided in brackets of respective schema e Algorithm Role dd algorithm role e Analyst Role ad analyst role e Data Loader Role data loader role 4 Installation Guide Stage 3 Release 6 2 1 Installation Checklist Chapter 1 Preparing to Install Table 3 Installation Checklist Continued 5 Take a back up of the following atomic schemas O e Alert Management Schema e Case Management Schema For more details refer to the Installation Guide Stage 1 Note The backup must be kept until the successful ins
44. ease 6 2 1 Verification of Installation Logs Chapter 2 Installation Activities Note For Installations on RAC databases ETL Application and Source creation is not supported by installer Therefore perform ETL Application and Source creation from OFSAAI UI for KYC after installation Once done proceed with next chapter For more details refer to the Appendix B Installation Guide Stage 3 Release 6 2 1 35 Verification of Installation Logs Chapter 2 Installation Activities 36 Installation Guide Stage 3 Release 6 2 1 CHAPTER 3 Post Installation This chapter explains the post installation activities and includes the following topics e Restart Application servers e Web Layer Configuration e OFSAAI Redeployment e Admin Tools Deployment e Scenario Wizard Configuration and Deployment e Restarting Web Application server e Creating Users to Access OFSFCCM Solution e Setting OFSFCCM UI as Home Page of OFSAAI for a Particular User Restart Application servers After successful installation of OFSFCCM restart the OFSAAI Application Server and ICC Server Note For more information on starting Application servers Infrastructure Server and ICC server refer to Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 During the restart of OFSAAI Application server ignore the following message appearing on the console of OFSAAI application server and proceed further ja
45. eholder with the type of DataModel upload to be performed Allowable values are 0 0 SLICED Model Upload For example Variable name DATAMODEL TYPE gt 0 lt Variable gt 20 Installation Guide Stage 3 Release 6 2 1 Populating the GRC_InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued LOGICAL UPLOAD LOGICAL_UPLOA This variable is used to identify if Data Model Upload for KYC is to be D_1 Logical This value is required only if MODEL_UPLOAD_FLAG_1 and PRE_INSTALL has been replaced by 1 Replace this placeholder with the type of DataModel upload to be performed Allowable values are 0 For example Variable name LOGICAL_UPLOAD gt 0 lt Variable gt DATAMODEL_FILE_PA DM_FILE_PATH_ This variable is used to identify the type of Data Model file path used TH 1 for KYC data Model Upload This value is required only if MODEL_UPLOAD_FLAG_1 and PRE_INSTALL has been replaced by 1 Replace this placeholder with the absolute path of DataModel file For example lt Variable name DATAMODEL FILE PATH home FCCMkit DataModel KYC DataModel Data Model KYC Release 2 0 Oracle xml lt Variable gt ActionGroup ETL_FLAG 1 This variable is used to identify whether ETL Application and Sources name ETL_CREATIO creation for KYC is to be done through t
46. ent Schema Name For example VariableGroup name ALERT MANAGEMENT DB DETAILS Variable name ATOMIC SCHEMA USER NAME 2AM Variable VariableGroup Refer to the nstallation Checklist point 4 for the schema name Installation Guide Stage 3 Release 6 2 1 15 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued VariableGroup name CASE MANAGEMENT DB DETAILS ATOMIC SCH R NAME EMA USE CASE_MANAGEME NT_USER This variable is used to identify the second Atomic Schema For FCCM the second Atomic schema is Case Management Schema Replace the placeholder with Case Management Schema Name For example lt VariableGroup name CASE_MANAGEMENT_DB_DETAILS gt lt Variable name ATOMIC_SCHEMA_USER_NAME gt CM lt Variable gt lt VariableGroup gt Refer to the Installation Checklist point 4 for the schema name VariableGroup name KYC DB DETAILS ATOMIC SCH R NAME EMA USFE KYC_USER This variable is used to identify the third Atomic Schema For FCCM the third Atomic schema is KYC Schema Replace the placeholder with KYC Schema Name For example lt VariableGroup name KYC_DB_DETAILS gt lt Variable name ATOMIC SCHEMA USER NAME
47. erform Configurations fot OFPSECM cscsiscssscnaiescssisveioseissssaiesosoasensasssoenssoeiossssonodedvanseiosedessdaiovedssnoaiebedssvoaiesedeanies 41 Installation Guide Stage 3 Release 6 2 1 V Contents Perform Administrative activities for KYQC NENNEN 42 Setting OFSFCCM UI as Home Page of OFSAAI for a Particular User 42 CHAPTER 4 Uninstalling OFSFCCM sss 43 CHAPTER 5 Deploying Analytic Reports and Threshold Analyzer 47 Instaling OBIBEB Setyet x aes decederet AE 47 Installing OBIEE Windows Administration Client ENNEN 47 Disabling the Cache Feature in OBIEB Servet csssssssesesssssssesesssssecssovesosnsnsosecnsnonsosssnsnodesvseasiesetessansodetesnanvedetesvaniovesesnans 48 Change Default Repository Passwotd tette tetto tt tekst tirisin sisisi eaa eco eate ea ree ea eee ani 48 Configuring OBIEB Gonnecttort Poole etre te rine eot e HO HABERE I EEE AE 49 Deploying OFSECCM Report Analytics cise sentiet ERR o RS E aware exi deese EE 50 Post Installation Steps ett tette tinet este ren t take ine FIR ENEE 51 Accessing Reports through OFSFCCM Application tette 52 APPENDIX A Installation Order for Multi Tier Installation of OFSFCCM 53 OFSAAI APP DB Layer on Machine A and OFSAAI WEB Layer on Machine B eeeeeeeeees 53 OFSAAI APP Layer on Machine A and OFSAAI DB WEB Layer on Machine B A 53 OFSAAI APP WEB Layer on Machine A and OFSAAI DB Layer on Machine B s
48. ers in Layer APPLICATION Variable name PLACEHOLDERS DESCRIPTION Layer name APPLICATION APP_LAYER This variable is used to identify FCCM Application Layer component to be installed on this machine as per the OFSAAI Installation option or Multi tier followed while installing OFSAAI platform Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 if Application Layer component is to be installed e 0 if Application Layer component is not to be installed e Incase OFSAAI was installed as single tier mode replace the place holder with 1 e Incase OFSAAI was installed as multi tier mode this value needs to be set according to OFSAAI application layer installed on this machine m Replace the placeholder with 1 for the machine hosting OFSAAI application layer m Replace the placeholder with 0 for the machine not hosting OFSAAI application layer Note For installing FCCM the application layer must be installed first followed by Database and Web layer installation For example Layer name APPLICATION flag 1 gt VariableGroup name ALERT MANAGEMENT DB DETAILS ATOMIC SCHEMA USE ALERT_MANAGEM R_NAME ENT_USER This variable is used to identify the first Atomic Schema For FCCM the first Atomic schema is Alert Management Schema Replace the placeholder with Alert Managem
49. es creation for KYC is to be done through the Installer Replace this placeholder with 0 For example lt ActionGroup name ETL CREATION flag 0 gt Note In case OFSFCOM is being installed a second time after successfully un installing then replace this placeholder with 0 Installation Guide Stage 3 Release 6 2 1 45 Chapter 4 Uninstalling OFSFCCM Table 8 Placeholders in GRC InstallConfig xml Continued TaskGroup name PRE INSTALLATION CONFIGURATION SUB SOL 4 ActionGroup 0 This variable is used to identify the FSDF Information Domain to name CREATE INFOD be created by the installer OM Replace this placeholder with 0 0 if Infodom for FSDF is already created For example lt ActionGroup name CREATE INFODOM flag 0 gt Note In case OFS FCOM installation is performed second time after successful un installation then keep this parameter as 0 since it is a onetime activity ActionGroup 0 This variable is used to identify whether Data Model Upload for name DATA MODEL U FSDF is to be done through the Installer PLOAD Replace this placeholder with 0 e 1 lif Data Model Upload for FSDF is to be done through the installer e 0 If Data Model Upload for FSDF is already completed For example lt ActionGroup name DATA MODEL UPLOAD flag 0 gt Note In case OFS FCOM installation is performed second time after successful un i
50. essSchema An RDBMS Source pointing to the Business database to hold the Business schema information The date format should be set as mm dd yyyy OracleSchema An RDBMS Source pointing to the Alert Management database to hold the Alert Management schema information The date format should be set as mm dd yyyy Map the Source to the respective application Data Source FileTable to Application File2Table Load Data Source ConfigSource to Application FicMaster Data Source KYCsource to Application KYC Data Source BusinessSchema to Application BusinessSchema Data Source OracleSchema to Application OracleSchema Generate the Source Model for the Sources FicMaster KYCsource Business and Mantas Schema NOTE For more details refer to the Oracle Financial Services Analytical Applications Infrastructure User Manual Release 7 3 to perform the steps mentioned above Installation Guide Stage 3 Release 6 2 1 55 Appendix B ETL Source Creation 56 Installation Guide Stage 3 Release 6 2 1 APPENDIX C Configuration for the KYC File Rename sh Below is the configuration which must be done for KYC_File_Rename sh file found in ficdb bin path The script will work fine for both Multitier and Single tier configuration Steps for Creating the Access Permission for Copying the File from One Machine to Another The below steps from 1 to 3 for providing the access must be done only for the Multi tier environment These steps ar
51. et ee eed E NU IRE re te eod eco uo AREARE ren BN eee cedes 4 Placeholders an Layer GENERAL iiie ietetet dte tette ded ee e he aH eH he dede 9 Placeholdets in Layer APPLICATION vsciissssscisssisssbssseasecsssasviessiassiseadeavsuavesstossdvavsvnsabapbessiensdvasstacdosassaniusssvandenndes 15 Placeholders in Layer DATABAS EB isscscsesssstsisssentevasnvstussssusticrssstesvasscnsssvsvessvovouscussdpuvsvandavacoasssesaenadiuavanecniscuastbinepial 24 Placeholders an layer WEB 22cm eret eter ete ke re XR EEE bae eR rer eive teta ped 30 Placeholders n GRC Install Com Deel Aeren dE 44 Installation Guide Stage 3 Release 6 2 1 ix List of Tables x Installation Guide Stage 3 Release 6 2 1 About This Guide This guide provides comprehensive instructions for installing and configuring the Oracle Financial Services Financial Crime and Compliance Management OFSFCCM Release 6 2 1 product that includes Enterprise Case Management OFSECM and Oracle Financial Services Know Your Customer OFSKYC This chapter focuses on the following topics e Who Should Use this Guide e How this Guide is Organized e Where to Find More Information e Conventions Used in this Guide Introduction The Oracle Financial Services Financial Crime and Compliance Management product installation happens in three stages e Stage1 OFSBDF Installation This stage creates four Atomic schemas namely Alert Management AM Case Management CM Know Your
52. f iles PATH SA RenamedF i les Custome t into the folder 9 tre renamed fi ke tAodity the File names according to the need of the AML solution Lat PATH S4 BistoryFiles PATH 4 Renawedr A les AccountSupplementalAttribute DLY 1 dad d files into the Token PATH SS BistoryFiles PATH SA RensmedFiles HatchListFeedback DLY 2 dat SSHABR PATM SS RenamedF11es Loving the files info the machine where the AMAL ts nstelled scp K l 104 5 69 f hose gsh fccm ingest ton_manager inbox aoe mez Path where the files need to be copied in the machine where the AML is installed IP Address of Hostname of the machine where the AML is installed User login name for the machine where the AML is installed cd SSE FATH S4 RenamedF i1es Suen She filet into the another machine where fhe AMI scp gsh 10 194 228 60 home gsh fccm ingestion manager inbox l Rep hom ai toen tion morae r inbox i This command is for Single Tier configuration uncomment this command and comment the above if nop below command if the Dot Layer and AML layer are on different machine the fiodh Layer and AML layer are on the same machine Figure 3 Single tier Configuration This command is used for the Multi tier configuration comment this command and uncomment the 58 Installation Guide Stage 3 Release 6 2 1 APPENDIX D Watchlist_FuzzyMatch Execute the below mentioned create synonym queries by logging
53. ficweb directory Note For instructions on deploying the EAR file refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 Admin Tools Deployment To deploy Admin Tools follow these steps 1 Go to FIC_HOME ficweb AM installed directory and run the script file changePasswords sh It will ask for the following passwords Enter password for Web Application User Installation Guide Stage 3 Release 6 2 1 39 Scenario Wizard Configuration and Deployment Chapter 3 Post Installation Enter password for Data Miner User Note Enter passwords corresponding to the following user names respectively Web Schema web user KDD MNR Schema tools user Refer to the Installation Checklist point 4 for more details 2 Go to FIC_HOME ficweb AM installed directory and run the script file create at war sh 3 Deploy the admin tool context name war fot example admin tools war available at FIC HOME AM directory as an application on your Web Application Server While deploying wat file keep same context name as given against variable ADMIN CONTEXT NAME in GRC InstallConfig xml File Note For instructions on deploying the EAR file refer to Oracle Financial Services Analytical Applications Infra structure Installation and Configuration Release 7 3 Scenario Wizard Configuration and Deployment Navigate to FIC HOME ficwe
54. folder under the ftpahore 5 ca SMARK PATM SA mkdir HistoryFiles chmod R 775 HistoryFiles B reofing a row fokfer under the ftpshore cd 5MARE FATW SA mkdir RenamedfFiles chmod R 775 RenwwedFiles ped BENI S thee actual Customer files onto the History Folder and movig the renamed files into the ep GenCustDetails ED 5i dat SSMARE VATM SI MistoryFiles ep GenCustbeteils ED 4 dat 3MARE PATH S4 RenamedF 11e Fustome lement ut dat Mihai the ac tue tomer files onto the History Folder and moves the rercemed files into Se fokter Modify the File names according to the need of the AMi solution ep GenAcctDetails ED zi dar mr PATW S1 HistoryFiles 1 ep GenAcctDetails ED i dat SSMARE PATM SI RenemedFiles AccountSupplementalAttribute DLY_2 dad Saken the actual Customer files unto the Hitory l okfer and movi the renamed files into the folder GenVLSFeedback ED 4 dat mr PATH SI1 HistoryTFiles cp GenMLSFeedback ED 4 dat mr PATW Si1 RensmmedFiles SatchListFeedback DLY 2 dat SSHABR PATM SS RenamedF11es ving the files into the machine where the AMA is motolled scp s tz 164 228 6d nome gsh tecm ingest ion_manager inbox 9 3 e Path where the files need to be copied in the machine where the AML is installed IP Address of Hostname of the machine where the AML is installed User login name for the machine where the AML is installed cd SSE FPATH S4 RenamedF iles Md the filer into fe another mochone where f
55. gt lt Variable name CUSTID gt OFSAAICUSTID lt Variable gt lt VariableGroup gt VariableGroup name PRE_INSTALLATION PRE_INSTALL PRE_INSTALL This variable is used to identify whether installer will perform the following pre installation activities e Infodom and Segment Creation for all atomic schemas e Data Model Upload for KYC and FSDF atomic schema e ETL Application Source creation for KYC atomic schema Replace this placeholder with either of the following values Allowable values are 0 and 1 e 1 If the user wants one or more of the above pre installation steps to be performed by the installer e 0 If the user has performed all the above steps through OFSAAI front end or the installer or in case running the installation for second time For example VariableGroup name PRE INSTALLATION Variable name PRE_INSTALL gt 1 lt Variable gt lt VariableGroup gt Note Oracle recommends that the installer to perform all these steps In case OFSFCCM installation has been performed second time after successful un installation then this parameter will be kept as 0 since it is a one time activity For more information refer to Chapter 4 Uninstalling OFSPCCM Installation Guide Stage 3 Release 6 2 1 9 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 4 Placeholders in Layer GENERAL Continued VariableGroup
56. h Calling the Shell Script for Copying the Files from One Path to Another 4 Open the KYC_File_Rename sh which is present in the path lt OFSAAI Installed Area gt ficdb bin of DB layer and configure the paths and details as mentioned in the following screenshots After the changes are done move the file to the ficdb bin area Provide executable permissions to the file 5 Execute the task through the batch execution screen of the OFSAAI application and check if the files are moved to the destination path Sech fy the below menticeed SHARE PATH az per your setup provide the path upto fipshare STAG SMARE PATH home gsh ftpshare STAGE KYCsource e Modifythe path according to your setup export SHARE PATH echo 55MARE PATH nC reating cd 5MARK PATM SA mkdir MistoryFiles chmod R New folder under the ftpshare 5 5 MistoryFiles croot mg cd 5MARE FATW SA mkdir RenamedfFiles chmod R 775 Mow fokfer under She ftpshare Peragseafi len pwa sese e e e cp etsare e g the actual Customer files into the GenCustDetails ED_ 4 dat Scien GenCustbetails ED 4 dat 3 ing the actual Customer files ito the History F GendcctDetails ED z3 dar mr GenAcctDetails ED i det SSMARE A the actual Customer files into the History P GenVLSFeedback ED 4 dat SSMARE GenWLSFeedback ED 4 det mz history Fol Wer and moveg the Mer ond mes kde e ard mos Pe rer renamed files ir PATH S4 Nistory
57. he AMI scp gsh 10 194 228 60 home gsh fccm ingestion manager inbox This command is used for the Multi tier configuration comment this command and uncomment the Rp homa ab f eom ingestion _manaye r inbox below command if the flog layer and AML layer are on different machine This command is for Single Tier configuration uncomment this command and comment the above if the fiodh Layer and AML layer are on the same machine Figure 5 Single tier Configuration 60 Installation Guide Stage 3 Release 6 2 1 ORACLE
58. he Installer Make sure to follow these conventions while giving a new Segment Code e The segment code must be unique There are no special characters and extra spaces in the code entered e The maximum length of Segment Code must be less than or equal to 10 characters For example Variable name SEGMENT_CODE gt FSDFSEG lt Variable gt Installation Guide Stage 3 Release 6 2 1 13 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 4 Placeholders in Layer GENERAL Continued VariableGroup name LOCAL FTPSHARE PATH FTPSHARE PATH FTPSHARE_PATH This variable is used to identify the common share area path Replace this placeholder with the same path as configured during OFSAAI Installation For example lt VariableGroup name LOCAL FTPSHARE PATH Variable name FTPSHARE_PATH gt home ftpshare lt Variable gt lt VariableGroup gt Note If having multiple installation of FCCM products on same server then keep different ftpshare path for this installation 14 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Layer APPLICATION The Layer APPLICATION Layer name APPLICATION gt consist of the following placeholders which must be replaced for installation of Application Layer as one of its component Table 5 Placehold
59. he installer N S Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 if ETL Application and Sources creation for KYC is to be done through the Installer e 0 if ETL Application and Sources for KYC is already completed For example ActionGroup name ETL CREATION flag 1 gt Note For Installations on RAC databases ETL Application and Source creation is not supported by installer Therefore keep this flag as 0 Once installation completes perform ETL Application and Source creation from OFSAAI UI for KYC ETL CODE ETL_CODE_1 This variable is used to identify the Atomic Schema for which ETL Application and Sources creation is to be done through the installer This value is required only if ETL_FLAG_1 and PRE_INSTALL has been replaced by 1 Replace this placeholder with 3 for KYC For example lt Variable name ETL_CODE gt 3 lt Variable gt Installation Guide Stage 3 Release 6 2 1 21 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 5 Placeholders in Layer APPLICATION Continued IS RAC IS_RAC_l This variable is used to identify whether the database is RAC This value is required only if ETL_FLAG_1 and PRE_INSTALL has been replaced by 1 Allowable Values are 0 and 1 Replace this placeholder with 1 if Database on which OF
60. ion Checklist point 4 for the role name DATA_LOADER_ROLF DATA_LOADER_R This variable is used to identify the Data Loader Role name OLE Replace the placeholder with Data Loader Role Name For example Variable name DATA_LOADER_ROLE gt DATA LOADER lt Variable gt Refer to the Installation Checklist point 4 for the role name VariableGroup name OFSBDP_DETAILS SINGLE_TIER_FLAG This variable is used to identify that OFSBDF is on same machine SINGLE TIER FLA asin which the OFSAAI DB layer is installed Gif e 0 if installed on same machine e 1 if installed on different machine For example Variable name SINGLE TIER FLAG 0 Variable OFSBDP USER ID OFSBDP_USER_I This variable takes the direct login unix user input of the machine DEH where OFSBDF is installed For Example Variable name OFSBDP_USER_ID gt ofsaa lt Variable gt OFSBDP_SERVER_HO This variable takes the input of the hostname or IP address of the ST OFSBDP_SERVER_H machine where OFSBDF is installed OST For example lt Variable name OFSBDP SERVER HOST unix oracle com Variab le OF SBDP_HOME LE This attribute holds the path where the execute sh file is present OF SBDP_HOME in the OFSBDF installed System For example lt Variable name OFSBDP_HOME gt lt OFSBDF Installed Dire
61. le Table 2 Environment Details Back End Environment Hardware Software OEL 5 5 or RHEL 5 3 5 5 or Sun Solaris 10 64 Bit or AIX 6 1 64 bit x 86 architecture Oracle 11g R2 11 2 0 2 0 64 bit e Java 1 6 0 latest update 64 bit e Websphere 7 0 0 latest update 64 bit or Weblogic 10 3 latest update 64 bit e OFSBDF 62 1 e OFSAAI 7 3 e OBIEE 11 1 1 6 7 Front End Client Access Software Windows XP Service Pack 3 Windows 7 e Java Plug in 1 6 0 latest update e Microsoft Internet Explorer 8 0 9 0 e Microsoft Office 2007 e Adobe Reader 8 0 or later Installation Guide Stage 3 Release 6 2 1 Installation Checklist Chapter 1 Preparing to Install Installation Checklist Table 3 lists the Installation Checklist to be completed for installing the OFSFCCM solution Follow the checklist in the sequence mentioned below and perform the listed activities Table 3 Installation Checklist Step No Task Done General 1 Check the OFSFCCM 6 2 1 Release Notes and Read Me document for any additional jr steps to be performed on OFSBDF or OFSAAI Note For more details contact Oracle support 2 Ensure that the required hardware and software are installed and configured O For more information on environment details refer Environment Details on page 3 OFSBDF 6 2 1 3 Ensure that the OFSBDF 6 2 1 is installed and configured Obtain th
62. le then perform the follow ing settings Maximum connections 0 to remove the upper cap of allocated Minimum connections 0 Aged timeout 660 Follow these steps depending on the type of Web Application server Websphere Weblogic used For Websphere a Login to the Websphere admin console b Click on Resources select JDBC and then select JDBC Providers c Click on data sources applicable for OFSFCCM apply the following setting for AM CM KYC and FSDF data sources i Click Data Sources in additional properties Click the data source name again Click Connection Pool Properties in additional properties If the value for maximum connection is less than 100 then make it 100 For Weblogic a Login to the Weblogic admin console b Click Setvices select JDBC and then select Data Sources c Click on data sources applicable for OFSFCCM 6 2 1 apply the following setting for AM CM KYC and FSDF data sources i Click the Connection Pool tab If the value for the maximum Capacity is less than 100 then make it 100 3 Verify the memory settings for the Web Application Server Set the minimum heap size as 512 MB and the maximum heap size as 3072 MB Note For more information refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 38 Installation Guide Stage 3 Release 6 2 1 OFSAAI Redeployment Chapter 3 Post Installation Workaround f
63. name INFODOM 1 INFODOM NAME INFODOM_1 This variable is used to specify the Alert Management Information Domain Infodom name Replace this placeholder with the Alert Management Infodom name in either of the following cases e f already created from OFSAAI front end Or To be created by the Installer Make sure to follow these conventions while creating a new infodom Consider the following e Information Domain name specified must be at least 6 characters long e Information Domain name must not contain any special characters or extra spaces e Information Domain name must be less than or equal to 20 characters For example Variable name INFODOM_NAME gt AMINFO lt Variable gt SEGMENT CODE SEGMENT_1 This variable is used to specify the Alert Management Segment Code Replace this placeholder with Alert Management Segment Code in either of the following cases e f already created from OFSAAI front end Or To be created by the Installer Make sure to follow these conventions Consider the following while giving a new Segment Code e The segment code must be unique e There must be no special characters and extra spaces in the code entered e The maximum length of Segment Code must be less than or equal to of 10 characters For example Variable name SEGMENT CODE AMSEG Variable 10 Installation Guide Stage 3 Release 6 2 1 Populating the
64. nstallation then replace this placeholder with O 46 Installation Guide Stage 3 Release 6 2 1 CHAPTER 5 Deploying Analytic Reports and Threshold Analyzer This chapter explains how to deploy Analytics on Oracle Business Intelligence Enterprise Edition OBIEE and integrate Analytic Reports and Threshold Analyzer in the OFSECM UI This chapter includes the following topics e Installing OBIEE Server e Installing OBIEE Windows Administration Client e Disabling the Cache Feature in OBIEE Server e Change Default Repository Password e Configuring OBIEE Connection Pool e Deploying OFSFCCM Report Analytics e Post Installation Steps Accessing Reports through OFSFCCM Application Installing OBIEE Server To install the Oracle Business Intelligence Enterprise Edition OBIEE server refer to Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence 1g Release 1 11 1 1 6 7 After installation get the Enterprise Manager URL Username Password and OBIEE installed directory from the system administrator Installing OBIEE Windows Administration Client To install the OBIEE repository administration client for Windows machine refer to Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence 1g Release 1 11 1 1 6 7 The OBIEE repository administration client can be downloaded from running OBIEE setup from the following URL lt protocol gt lt OBIEE Server Name gt lt
65. nter the new password and click OK 48 Installation Guide Stage 3 Release 6 2 1 Configuring OBIEE Connection Pool Chapter 5 Deploying Analytic Reports and Threshold Analyzer Configuring OBIEE Connection Pool To configure the Connection Pool of the repository follow these steps 1 10 lk 12 v OND u Open the same Repository as in the previous step on the Windows machine The Oracle BI Administration Tool ECM 6 2 rpd windows is displayed Expand the D4010S10 folder in the Physical section Double click Connection Pool to open the Connection Pool Properties window Enter the following in the Data Source Name text box of the Connection Pool Properties window after modifying Database Server Host Name and Database Name Data Source Name DESCRIPTION ADDRESS PROTOCOL TCP HOST Database Server Host Name PORT 1521 CONNECT DATA SERVER DEDICATED SERVICE NAME Database Name gt Enter the Alert Management schema user in the User name text box Enter the Alert Management schema user password in the Password text box Click OK Expand the folder and test connection for any one table name by Right Click gt view data Perform similar changes in the Connection Pools for all remaining folders in the Physical Layer by providing the following schema details for all Connection Pools a D4010810 gt Alert Management Schema b D5011S1
66. older with Alert Management Schema Name For example lt Variable name ALERT_MANAGEMENT_SCHEMA_USER gt AM lt Variable gt Refer to the Installation Checklist point 4 for the schema name KDD_WEB_SCHEMA_ KDD_WEB_USER This variable is used to identify the WEB Schema name USER Ht Replace the placeholder with WEB Schema Name For example lt Variable name KDD_WEB_SCHEMA_USER gt KDD_WEB lt Variable gt Refer to the nstallation Checklist point 4 for the schema name KDD_SCHEMA_USER KDD_USER This variable is used to identify the KDD Schema name Replace the placeholder with KDD Schema Name For example Variable name KDD_SCHEMA_USER gt KDD lt Variable gt Refer to the Installation Checklist point 4 for the schema name KDD_MNR_SCHEMA_ KDD_MNR_USER This variable is used to identify the KDD MNR Schema name USER tt Replace the placeholder with MNR Schema Name For example lt Variable name KDD_MNR_SCHEMA_USER gt KDD_MNR lt Variable gt Refer to the Installation Checklist point 4 for the schema name Installation Guide Stage 3 Release 6 2 1 31 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Table 7 Placeholders in layer WEB Continued VariableGroup name OBIEE REPORTS INSTALLATION
67. or AIX 6 1 Perform the following step for Bug 16830426 if using ATX 6 1 box the Stage 3 Installer adds an additional FICMASTER entry Follow these steps 1 Navigate to SFIC WEB HOME webroot WEB INF web xml 2 Open web xml and remove one set of the following tags if duplicate entries present lt resource ref gt res ref name jdbc FICMASTER res ref name lt res type gt javax sql DataSource lt res type gt res auth Container res auth resource ref 3 Save file 4 Recteate OFSAAI eat file Workaround for WebLogic as Web Application Server Update the file startWebLogic sh in WebLogic Instance Home bin directory as follows Locate the following line in the shell script echo starting weblogic with Java version Edit the Weblogic startup script which starts up the Oracle Financial Services application server and add the following three parameters above echo starting weblogic with Java version Add the following lines in the shell script JAVA OPTIONS S JAVA OPTIONS Djavax xml soap SOAPConnectionFactory org apache axis soap SOAPConnectionFactoryImpl JAVA OPTIONS S JAVA OPTIONS Djavax xml soap MessageFactory org apache axis soap MessageFactoryImpl JAVA OPTIONS S JAVA OPTIONS Djavax xml soap SOAPFactory org apache axis soap SOAPFactoryImpl OFSAAI Redeployment Deploy the Context name ear for example OFSAAI ear available at FIC HOME
68. or installing and configuring OFSAAI For more information about OFSFCCM refer to the following documents Configuration Guide Provides instruction to configure OFSFCCM solution Administration Guide Provides instruction to perform administrative activities for the OFSFCCM solution Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 This Installation and Configuration Guide provides instructions for installing and configuring OFSAAT Oracle Financial Services Analytical Applications Infrastructure User Manual Release 7 3 This manual provides instructions for System Administration components of Infrastructure and assists the administrator in configuring the system managing users and performing administrative tasks effectively To find more information about Oracle Financial Services application and our complete product line visit our website at www oracle com financial services xii Installation Guide Stage 3 Release 6 2 1 About this Guide Conventions Used in this Guide Table 1 lists the conventions used in this guide Table 1 Conventions Used in this Guide Convention Meaning Italics Names of books chapters and sections as references Emphasis Bold Object of an action menu names field names options button names in a step by step procedure Commands typed at a prompt User input Monospace Directories and subdirectories
69. riable gt Installation Guide Stage 3 Release 6 2 1 29 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Layer WEB The Layer WEB Layer name WEB gt contains the following placeholders which must be configured for installation of WEB layer as one of its component Table 7 Placeholders in layer WEB Variable PLACEHOLDERS DESCRIPTION Layer WEB_LAYER This variable is used to identify OFSFCCM Web Layer component to be name WEB installed on this machine as per the OFSAAI installation option or multi tier followed while installing OFSAAI platform Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 if WEB Layer component is to be installed e 0 if WEB Layer component is not to be installed In case OFSAAI was installed as single tier mode replace the place holder with 1 In case OFSAAI was installed as multi tier mode this value needs to be set according to the OFSAAI Web layer installed on this machine e Replace the placeholder with 1 for the machine hosting OFSAAI Web layer e Replace the placeholder with 0 for the machine not hosting OFSAAI Web layer Note For installing OFSFCCM APP layer installation happens first and then followed by Database and Web layer For example Layer name WEB flag 1 gt VariableGroup name DATABASE DETAILS FICMAS
70. ring to Install details the activities that occur prior to the installation of OFSFCCM and identifies all the third party software s necessary to run the OFSFCCM solution Chapter 2 Installation Activities provides step by step installation activities for installing the OFSFCCM solution Chapter 3 Post Installation details the steps that must be followed after successful installation of OFSFCCM solution Chapter 4 Uninstalling OFSFCCM details the steps that must be followed for un installation of OFSFCCM solution Chapter 5 Deploying Analytic Reports and Threshold Analyzer explains how to integrate Analytic Reports and Threshold Analyzer with OFSFCCM solution Appendix A Installation Order for Multi Tier Installation of OFSFCCM explains the installation order of OFSFCCM on different machines hosting OFSAAI Layet s Appendix B ETL Source Creation explains steps for creation of ETL Where to Find More Information The OFSFCCM installation is done in three stages The three installation guides are as follows Installation Guide Stage 1 This Installation Guide provides instructions for installing Oracle Financial Services Behavior Detection Framework OFSBDF Scenarios and Data Ingestion and Detection Algorithms to support Behavior Detection Stage 2 Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 This installation and configuration guide provides instructions f
71. se Time Zone m Configuring the Default Currency Code Configuring E mail Configuring XML Export Configuring Organization Relationships for Trade Blotter IN Configuring Search Criteria Population Options for Trade Blotter Installation Guide Stage 3 Release 6 2 1 41 Setting OFSFCCM UI as Home Page of OFSAAI for a Particular User Chapter 3 Post Installation Configuring Case Correlation Owner Configuring Default Case Owner E Configuring Default Alert Owner m Configuring the Alert Case Auto Assignment Web Service Perform Administrative activities for KYC Access the OFSFCCM UI as a KYC Administrator and perform all the steps given in the KYCAdministration Guide Note Appendix C and D should be performed for successful KYC installation Setting OFSFCCM UI as Home Page of OFSAAI for a Particular User To set OFSFCCM UI as home page of OFSAAI follow these steps 1 Log in as an ECM Administrator Supervisor user 2 Navigate to Home page 3 Select Enterprise Case Management as your default page and click Save 42 Installation Guide Stage 3 Release 6 2 1 CHAPTER 4 Uninstalling OFSFCCM To uninstall the OFSFCCM in a particular OFSAAI Layer follow these steps For multi tier architecture OFSFCCM Uninstaller must be run on all servers hosting an OFSAAI Layer 1 Before uninstalling the OFSFCCM execute profile to set the environment variables using the following command ksh profile
72. t OL e vii List f Tables wiveiteserictiause casera suatsecssasciiatbaiserheasssansusttedsenuaiuaensuavidtrfemtunsiosuciyveriPniudnenauierd ix About R M xi ett xi Who Should Use this Gif P n xi How this Guides Organized a teorici a ac eH EHE HB OH REUS HAEC HE HEU EUREN xii Where to Find More ee xii Conventions Used in this Guide iiie tertiis riii esie tores ae oae NEEN xiii CHAPTER 1 Preparing to Install roten 1 Deployment ArchiteGt te ciet be RR E qaando disini oti A ris bee ees e Fueron 2 Environment BI e S P M 3 e E P 4 Populating the GRC Install Config wink leeden eco 8 secuela EE 9 SEET 15 Layer DATABASE EE 24 Layers WEB EE 30 CHAPTER 2 Installation Activities 33 Installing OFSFCCM Solution in Silent Mode ENNEN 33 Verification of Installation Les ihr ERR tpe e eee ie ilo E de Raph Seed o EE 34 CHAPTER 3 la e ccr VI 37 Restart Application adc M SOR 37 avisar M RR 38 Workaround fot AIX EE 39 Workaround for WebLogic as Web Application Bereer ENEE 39 ORSAAT Red eployiment HY 39 Admin Tools ee 39 Scenario Wizard Configuration and Deployment ENEE 40 Restarting Web Application setVet eee eerie Eddie 41 Creating Users to Access OFSECCM Sehugemg sesch ee 41 Perform Administrative activities for OPSPBCN ENEE 41 P
73. tallation of the solution OFSAAI 7 3 6 Ensure that the OFSAAI 7 3 is installed and configured O For more details refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 Note Make sure that 5F1C HOME should not be the same as lt OFSBDF_Installed Directory gt Contact Oracle Support for installing any additional patches on top of OFSAAI if required Before installing OFSFCCM 6 2 1 make sure to install the 7 3 3 patch on top of Oracle Financial Services Analytical Applications Infrastructure 7 3 OFSAAI in the following order OFSAAI Bug IDs 7 3 3 0 0 OFSAAI 7 3 3 0 0 Interim Release 7 Ensure that the ftpshare path of the OFSAAI Application Layer APP Data Base Layer L DB and Web Application Layer WEB layers are configured and have recursive read write execute permission for the user installing OFSFCCM For more details refer to the Oracle Financial Services Analytical Applications Infrastructure Installation and Configuration Release 7 3 Note If having multiple installation of FCCM products then keep different ftpshare path for each installation Installation Guide Stage 3 Release 6 2 1 5 Installation Checklist Chapter 1 Preparing to Install Table 3 Installation Checklist Continued 8 Ensure to configure OFSAAI WEB APP DB server as part of OFSAAI Installation L For more information refer to Oracl
74. ters and extra spaces in the name e The length of database name must not exceed 20 characters For example Variable name DATABASE_NAME gt KYCDB oracle com lt Variable gt Note A TNS entry must be made in tnsnames ora with tnsname same as the value provided for KYC Database Name If sqinet ora is configured with a vaue in NAMES DEFAULT_DOMAIN then make sure to use same domain while defining Database Name It is required for KYC Batch processing Or OFSAAI recommends for the Oracle database the DB_NAME_3 must be same as the TNS Transparent Network Substrate Database Name In case the TNS Database Name is not yet used as Database_Name for any other Atomic Schema ActionGroup MODEL_UPLOAD_ This variable is used to identify whether Data Model Upload for KYC name DATA MODEL FLAG_l is to be done through the Installer UPLOAD Allowable values for this placeholder are 0 and 1 Replace this placeholder with e 1 if Data Model Upload for KYC is to be done through Installer e 0 if Data Model Upload for KYC is already completed For example ActionGroup name DATA MODEL UPLOAD flag 1 gt DATAMODEL TYPE T4DM TYPE 14H This variable is used to identify the type of Data Model Upload for KYC that is to be done through the Installer This value is required only if 4 MODEL UPLOAD FLAG L t and PRE_INSTALL has been replaced by 1 Replace this plac
75. to populate the GRC InstallConfig xml file Open the GRC InstallConfig xml under the OFSFCCM installer kit directory and enter the required input parameters as per the instructions This file contains the following four sections e Layer GENERAL e Layer APPLICATION e Layer DATABASE e Layer WEB The GRC_InstallConfig xml contains placeholders in the format lt PLACEHOLDER Name gt wherever user input is required Replace these placeholders with the corresponding values as mentioned against each one of these placeholders Note 1 In single tier installation all layers sections are mandatory 2 In multi tier installation while performing individual tier installation GENERAL layer section information is mandatory for all layers 8 Installation Guide Stage 3 Release 6 2 1 Populating the GRC InstallConfig xml File Chapter 1 Preparing to Install Layer GENERAL The Layer GENERAL Layer name GENERAL gt contains the following placeholders to provide parameter values specific to the users system Table 4 Placeholders in Layer GENERAL Variable name PLACEHOLDERS DESCRIPTION VariableGroup name OFSAA INFRASTRUCTURE CUSTOMER CODE CUSTID CUST_ID This variable is used to store the Customer ID Replace this placeholder with Customer Code used during OFSAAI Installation For example lt VariableGroup name OFSAA_INFRASTRUCTURE_CUSTOMER_CODE
76. va io FileNotFoundException lt ftpshare path gt lt AMINFODOM gt erwin fipxml lt AMINFODOM gt _DATABASE XML No such file or directory java io FileNotFoundException lt ftpshare path CMINFODOM erwin fipxml CMINFODOM DATABASE XML No such file or directory Note The placeholders lt AMINFODOM gt and lt CMINFODOM gt in the message are replaced with the Alert Management Infodom values Installation Guide Stage 3 Release 6 2 1 37 Web Layer Configuration Chapter 3 Post Installation Web Layer Configuration 1 Login to the Web Application server console for creating Java Data Base Connectivity JDBC resources for AM CM KYC and FSDF schemas by providing AM CM KYC and FSDF infodom names and respective Atomic Schema DB usernames and passwords respectively Por more information refer to Oracle Financial Services Analytical Applications Infrastructure Installation and Configu ration Release 7 3 Note In Web Logic while creating Data Source do not select any driver for Thin XA Always choose data base driver as Oracles driver Thin for service connection Version 2 Verify the connection pool settings for AM CM KYC and FSDF Data Sources It must be 100 Note Web Sphere has its own tunable Connection pool settings FCCM recommends to keep Max Connection 100 but it depends on the number of users specific to Admin Tools In case while accessing Admin Tools if you get no connection pool availab

Download Pdf Manuals

Related Search

Related Contents

Hometronic Manager HCM 200  Benutzerhandbuch  取扱説明書 保証書 UHF卓上アンテナ  越 JーTEC - ジャパン・ティッシュ・エンジニアリング  Instrucciones ovalada - Portugues  

Copyright © All rights reserved.

• https://telegra.ph/Calculate-Wire-Resistor-from-Voltage-Drop-2e0f9197-11-16
• https://telegra.ph/Calculate-Length-from-Voltage-Drop-d8298556-11-16
• https://telegra.ph/Concrete-Mix-Calculator-c0b6a640-11-16
• https://telegra.ph/Footer-Concrete-Volume-Calculator-188748b6-11-17
• https://telegra.ph/Round-Slab-Concrete-Volume-Calculator-3515330f-11-17
• https://telegra.ph/Wall-Concrete-Volume-Calculator-3a454ed8-11-13
• https://telegra.ph/DC-Voltage-Drop-Calculator-245f9403-11-17
• https://telegra.ph/Wire-Size-Calculator-From-Voltage-Drop-07bbf472-11-17
• https://telegra.ph/Calculat-Wire-Area-From-Voltage-Drop-4e79d7a5-11-18
• https://telegra.ph/AC-Single-phase-Voltage-Drop-Calculator-1e3d99e8-11-18