View
15
Download
0
Category
Preview:
Citation preview
Oracle Banking Virtual Account Management
Installer Guide
Release 14.3.0.0.0
Part No. F18410-01
May 2019
Oracle Banking Virtual Account Management Installer Guide May 2019 Version 14.3.0.0.0 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon (East) Mumbai, Maharashtra 400 063 India Worldwide Inquiries: Phone: +91 22 6718 3000 Fax:+91 22 6718 3001 https://www.oracle.com/industries/financial-services/index.html Copyright © 2018-2019, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Contents 1. PREFACE ........................................................................................................................................................ 1-1
1.1 PURPOSE ..................................................................................................................................................... 1-1 1.2 AUDIENCE .................................................................................................................................................. 1-1 1.3 SCOPE ......................................................................................................................................................... 1-1
2. INSTALLER PRODUCT ............................................................................................................................... 2-1
2.1 PREREQUISITES ........................................................................................................................................... 2-1 2.2 DATABASE INSTALLATION ....................................................................................................................... 2-10 2.3 WEBLOGIC INSTALLATION ....................................................................................................................... 2-11
3. BATCH PROCESS .......................................................................................................................................... 3-1
3.1 CONFIGURATION AND RUNNING BATCH ..................................................................................................... 3-1 3.2 OBVAM-AMOUNT-BLOCK-EXPIRY-TASK ...................................................................................................... 3-2 3.3 OBVAM-ACCOUNT-INACTIVE-TASK ............................................................................................................. 3-2 3.4 OBVAM-FORGET-ACCOUNT-TASK ............................................................................................................... 3-3 3.5 OBVAM-FORGET-ENTITY-TASK ................................................................................................................... 3-3 3.6 CMC-FORGET-ACCOUNT-TASK .................................................................................................................... 3-3 3.7 CMC-FORGET-CUSTOMER-TASK .................................................................................................................. 3-4 3.8 OBVAM-UNTANKING-TASK ......................................................................................................................... 3-4 3.9 OBVAM-ACCOUNT-STATEMENT-TASK ......................................................................................................... 3-4 3.10 OBVAM-ACCOUNT-VALUEDATE-TASK ........................................................................................................ 3-5 3.11 OBVAM-ACCOUNT-TURNOVER-BALANCE-TASK .......................................................................................... 3-5 3.12 OBVAM-CREDITLIMIT-UTIL-REVAL-TASK .................................................................................................... 3-5
4. BIP CONFIGURATION ................................................................................................................................. 4-1
4.1 CONFIGURING DATA MODEL ...................................................................................................................... 4-1 4.2 CONFIGURING THE REPORT ABSOLUTE PATH ............................................................................................. 4-1
5. LOGGING AREA ........................................................................................................................................... 5-1
5.1 LOGGING AREA .......................................................................................................................................... 5-1
1-1
1. Preface
1.1 Purpose
This document provides the procedure to use the installer product.
1.2 Audience
This guide is primarily intended for Developers for Oracle Banking products. Some information may be relevant to IT decision makers and users of the application are also included. Readers are assumed to possess basic operating system, network, and system administration skills with awareness of vendor/third-party software’s and knowledge of Oracle Banking products.
1.3 Scope
1.3.1 Read Sections Completely
Each section should be read and understood completely. Instructions should never be blindly applied. Relevant discussion may occur immediately after instructions for an action, so be sure to read whole sections before beginning implementation.
1.3.2 Understand the Purpose of this Guidance
The purpose of the guidance is to provide procedure to use Oracle Banking Installer Product.
1.3.3 Limitations
This guide is limited in its scope to provide procedure to use Oracle Banking Installer Product.
2-1
2. Installer Product
The following sections require to be completed in a sequence to finish the installation.
2.1 Prerequisites
A list of prerequisites that are required to use Oracle Banking Installer:
1. Oracle Database Enterprise Edition.
2. Oracle WebLogic Server Standard Edition.
3. Node machines must have Oracle Linux 7 installed with Java version 1.8.0 patch 181.
4. Install the Chef Client on the node machines to use the Oracle Banking Installer. Refer Installation of Chef Client section for detailed instructions to install chef client.
5. Ensure that the PDB with applicable DB schemas for the product are available.
6. Install the Oracle SQL Client must be installed on the node machine to use the Oracle Banking Installer for the DB SQL execution.
7. Ensure that the required number of WebLogic (12.2.1.3) managed servers and clusters for the product are up and running on SSL with Custom Trust Key Store (jks).
8. Create the data bags required for the product installation. Refer Data bag Creation section for detailed instructions to create the data bags.
9. Set bash shell on node machines to run the Oracle Banking Installer.
10. Configure the proxy on each node machine. Set up the proxy with the following commands. (Proxy setup is required only to update the yum package)
$ export http_proxy=http://USERNAME:PASSWORD@proxy-
server.mycorp.com:port/
$ export
https_proxy=https://USERNAME:PASSWORD@proxyserver.mycorp.com:port/
11. Update yum using the following command.
$ yum update yum
12. Ensure that the system date and time is valid and latest.
13. FQDN should be set properly. You can check the current FQDN using this command.
$ hostname -f
14. LDAP server
15. Rabbit MQ Server 3.7.7
16. Ensure 18 managed servers/clusters are created (11 for OBVAM, 1 for COMMONCORE, 1 for SMS, 1 for OBVAM UI and 4 for PLATO). To create and configure weblogic managed servers/clusters refer section named “creating domain and cluster configuration“ from Oracle Banking Virtual Account Management Annexure.
To enable ssl in the created server, refer Oracle Banking Virtual Account Management SSL Setup.
2.1.1 Installing of Chef Client
To install the chef client:
1. Login to node machine as root user.
2-2
2. Copy the product OSDC bundle to the /scratch folder of the Oracle Linux Server i.e. node machine.
3. Extract the product OSDC bundle and navigate to /scratch/<extracted OSDC bundle>/ oracle_banking_installer_pack/softwares/chef-client/14.8.12.
$ cd /scratch/<<extracted OSDC
bundle>>/oracle_banking_installer_pack/softwares/chef-client/14.8.12
4. Execute the below command to install the chef-client
$ rpm -ivh chef-14.8.12+20190122094824-1.el7.x86_64.rpm
5. Verify chef 14.8.12 is installed in the machine using this command.
$ chef-client --version
Chef: 14.8.12
2.1.2 Data bag Creation
The data bag contains the encrypted passwords for the WebLogic, DB and SSL. These passwords will be used by the Oracle Banking Installer during the product installation.
Chef requires a secret key to encrypt and decrypt the data bag items. Install the openssl in the node machine and use the following command to generate a secret key:
$ openssl rand -base64 512 > /scratch/<extracted OSDC
bundle>/oracle_banking_installer_pack/chef-repo/secrets/secret_key
Note: Open ssl is one of the option to generate the secret key.
2.1.2.1 WebLogic
1. Navigate to /scratch/<extracted OSDC bundle>/oracle_banking_installer_pack/chef-repo/data_bags/fsgbu_weblogic_deploy/ folder.
2. Edit the json file “datasource_credentials.json”. This json file will contain the data source passwords.
$ cd fsgbu_weblogic_deploy
$ vi datasource_credentials.json
3. Update plain data source passwords against the corresponding data source name in the json file.
{
"id": "datasource_credentials",
"PLATO": "<password>",
"PLATO_SECURITY": "<password>" ,
"PLATO_UI":"<password>" ,
"SMS": "<password>",
"COMMONCORE": "<password>",
"OBVAMACCTSVCS": "<password>",
"OBVAMCORESVCS": "<password>",
"OBVAMECASVCS": "<password>",
"OBVAMENTYSVCS": "<password>",
"OBVAMEXTDDASVCS": "<password>" ,
"OBVAMIDSVCS": "<password>" ,
"OBVAMINTTRANSSVCS": "<password>",
"OBVAMSTMTSVCS": "<password>",
"OBVAMTXNJOURNALSVCS": "<password>",
"EIESVCS": "<password>" ,
"ELMSVCS": "<password>"
}
2-3
4. For reference, see the below example datasource_credentials.json with sample content.
{
"id": "datasource_credentials",
"PLATO": "welcome1",
"PLATO_SECURITY": "welcome2" ,
"PLATO_UI":"welcome3" ,
"SMS": "welcome4",
"COMMONCORE": "welcome5",
"OBVAMACCTSVCS": "welcome6",
"OBVAMCORESVCS": "welcome7",
"OBVAMECASVCS": "welcome8",
"OBVAMENTYSVCS": "welcome9",
"OBVAMEXTDDASVCS": "welcome10" ,
"OBVAMIDSVCS": "welcome11" ,
"OBVAMINTTRANSSVCS": "welcome12",
"OBVAMSTMTSVCS": "welcome13",
"OBVAMTXNJOURNALSVCS": "welcome14",
"EIESVCS": "welcome15" ,
"ELMSVCS": "welcome16"
}
5. Execute the below knife command from chef-repo directory to encrypt the passwords.
knife data bag from file fsgbu_weblogic_deploy
datasource_credentials.json --secret-file /scratch/<extracted OSDC
bundle>/oracle_banking_installer_pack/chef-repo/secrets/secret_key --
local-mode
6. Encrypted data bag file look like below (for reference).
{
"id": "datasource_credentials",
"PLATO": {
"encrypted_data": "fI68A3KOFbVwRnDT9n5RslBZHqez892D\n",
"iv": "F7fcJLnD8640mP+A\n",
"auth_tag": "0cDJLh85dbbcEBc7sffe5w==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"PLATO_SECURITY": {
"encrypted_data": "uS9/5zalW7omMw6LLKxjog2urtMCryBC\n",
"iv": "M9p8yKG3u4vi9m3i\n",
"auth_tag": "IN3BFf+5YpRfPS1t7zuJqA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"PLATO_UI": {
"encrypted_data": "mEHKFUj52LSaaNGaonS4jnGAwm/Zywnv\n",
"iv": "o+ABlU34aJ+/ZY6k\n",
"auth_tag": "ZCUqQavqdBEdr6rGVJ7IOg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"SMS": {
"encrypted_data": "swSPnbLQwr7XB2SqehYWmKO0B4IumwI/\n",
"iv": "OR3mwV14WKlOiFfd\n",
"auth_tag": "Yr91S3NPrgtOpy2ay4QCww==\n",
"version": 3,
"cipher": "aes-256-gcm"
2-4
},
"COMMONCORE": {
"encrypted_data": "9EQ0I9zPI1gKF1V91EiqAeEGKHw/NxKC\n",
"iv": "pA3+vAn+X1v/ExmT\n",
"auth_tag": "khdGumRQRV/V3ZVjnmCRBg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMACCTSVCS": {
"encrypted_data": "NRR6cY8XwS36W9t5qyf1eeGF21XRen0J\n",
"iv": "j2XZDCzmpZE/S/21\n",
"auth_tag": "/AA6IXGEvQJvNQzHnmNrrg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMCORESVCS": {
"encrypted_data": "0AbhGENlm3r5ySUiqVmEl5UZd3Vnz/AH\n",
"iv": "MBFX+Br0VHfTfJu1\n",
"auth_tag": "qDYxcdxLg/iiYNmELt8RRw==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMECASVCS": {
"encrypted_data": "imEZLPWVyb8ULBZfFFmPjq3UcbVUWOQN\n",
"iv": "MgPlIgbAYIajofiP\n",
"auth_tag": "s+uQBWebbPgr5iM4NRTCqw==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMENTYSVCS": {
"encrypted_data": "6hxB+8FwH51rUr1NkHgG6D+0XEvMkqkX\n",
"iv": "9DGsDXEgJWGL8YoD\n",
"auth_tag": "nwTqEF6YEiW6EtB85GzDbA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMEXTDDASVCS": {
"encrypted_data": "2ZJTOcg43CsY0lS1gY3rKoPFjbmNws+F\n",
"iv": "u+Q09V6w9dH3Nlp6\n",
"auth_tag": "cWI9QX1qyWb8HVxucr828A==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMIDSVCS": {
"encrypted_data": "NbIMXcPaTcnCxLidGa+d4CTGPszaINyb\n",
"iv": "zx3RsCFOYx9X8K+w\n",
"auth_tag": "ZkXygyk0iRlClYLU1OpJ4w==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMINTTRANSSVCS": {
"encrypted_data": "7VkwNVFTZaBNCGLuvjPBfuTyXIdHoTO+\n",
"iv": "caqb8ScmuF8OyLpk\n",
"auth_tag": "tqM4KaxcMiTabkx4RZPLpA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
2-5
"OBVAMSTMTSVCS": {
"encrypted_data": "8zujZk2OOaQzdh3eI8JTD0elWbzXEibg\n",
"iv": "LNEDf6nQnmISPrR8\n",
"auth_tag": "wfi5XTfjfcoRCUPECtf/Sw==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"OBVAMTXNJOURNALSVCS": {
"encrypted_data": "jZwuPgEdrr649Q093g8MRn4uAweXH0WT\n",
"iv": "swFvnvmIpQxM8y2A\n",
"auth_tag": "jGM8JQHadevt2P2LgmFzew==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"EIESVCS": {
"encrypted_data": "4KLGrhGvEVTJ5JbIiqM431HhKC1/q9Ns\n",
"iv": "5bsD8b2H5mszb3Ak\n",
"auth_tag": "/JUKjxOHXT/3lZ9baP8euw==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"ELMSVCS": {
"encrypted_data": "QAV3UPl7Gl0jP6if/f3Itmb7Nz3QkYny\n",
"iv": "s1ew03VF7QlRMepF\n",
"auth_tag": "qltz5G/UnS/nzqrzqjLO2g==\n",
"version": 3,
"cipher": "aes-256-gcm"
}
}
7. Edit the json file “ssl_credentials.json”. This json file will contain the Custom TrustKeyStore
Passphrase.
$ cd fsgbu_weblogic_deploy
$ vi ssl_credentials.json
8. Update plain Custom TrustKeyStore Passphrase against “ssl_password” key in the json file.
{
"id": "ssl_credentials_",
"password": "<Custom TrustKeyStore Passphrase>"
}
9. For reference, see the below example ssl_credentials.json with sample content.
{
"id": "ssl_credentials",
"password": "welcome1"
}
10. Execute the below knife command from chef-repo directory.
knife data bag from file fsgbu_weblogic_deploy ssl_credentials.json --
secret-file /scratch/<extracted OSDC
bundle>/oracle_banking_installer_pack/chef-repo/secrets/secret_key --
local-mode
11. Encrypted data bag file look like below (for reference).
{
"id": "ssl",
"password": {
"encrypted_data": "1V8PHifoq4mD6HcdCSFh5ViczOFYs5hOQBL1\n",
2-6
"iv": "01lmFs8TScYdWiOU\n",
"auth_tag": "piaTCwUIljlYzA/zg66hbQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
}
}
12. Edit the json file “weblogic_credentials.json”.This json file will contain the WebLogic admin
username and password.
$ cd fsgbu_weblogic_deploy
$ vi weblogic_credentials.json
13. Update plain text WebLogic admin username and password against “wl_admin_username” and
“wl_admin_password” keys respectively in the json file.
{
"id": " weblogic_credentials",
"wl_admin_password": "<weblogic admin user password>",
"wl_admin_username": "<weblogic admin user name>"
}
14. For reference, see the below example weblogic_credentials.json with sample content.
{
"id": " weblogic_credentials",
"wl_admin_password": "welcome1",
"wl_admin_username": "weblogic"
}
15. Execute the below knife command from chef-repo directory.
knife data bag from file fsgbu_weblogic_deploy
weblogic_credentials.json --secret-file /scratch/<extracted OSDC
bundle>/oracle_banking_installer_pack/chef-repo/secrets/secret_key --
local-mode
16. Encrypted data bag file look like below (for reference)
{
"id": "weblogic_credentials",
"wl_admin_password": {
"encrypted_data": "VcvEoFJuGpQTHkNfNycdWmZ2dZEOecgLAxYpgVHH\n",
"iv": "EQfnKTtGmY9QD7zB\n",
"auth_tag": "db/XjXWY5eSeiLupMqGVGA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"wl_admin_username": {
"encrypted_data": "HRjvx8IIJ6ij01wcbiANbxCpNZHHrbyES7aL\n",
"iv": "FrTOd8zxHLW/dOPN\n",
"auth_tag": "fOGTGlcC4uoPDuKToN9MrQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
}
}
17. Ensure all json files are on 755 permission.
2.1.2.2 Database
1. Navigate to /scratch/<extracted OSDC bundle>/
oracle_banking_installer_pack/chef-repo/data_bags/fsgbu_db_deploy folder.
2-7
2. Edit the json file “schema_credentials.json”. This json file contains the db login passwords.
$ cd fsgbu_db_deploy
$ vi schema_credentials.json
3. Update the database passwords against their respective place holders in the json file. Schema
Passwords should be updated against their respective schema names.
{
"id": "passwords",
"PLATO_SCHEMA_PASSWORD": “<password>”,
"PLATO_SECURITY_SCHEMA_PASSWORD":“<password>”,
"PLATO_UI_SCHEMA_PASSWORD":“<password>”,
"SMS_SCHEMA_PASSWORD": “<password>”,
"COMMONCORE_SCHEMA_PASSWORD": “<password>”,
"VAM_SCHEMA_PASSWORD":“<password>”,
"VAC_SCHEMA_PASSWORD":“<password>”,
"VAB_SCHEMA_PASSWORD":“<password>”,
"VAE_SCHEMA_PASSWORD":“<password>”,
"EDA_SCHEMA_PASSWORD":“<password>”,
"VAI_SCHEMA_PASSWORD":“<password>”,
"VAN_SCHEMA_PASSWORD":“<password>”,
"VAS_SCHEMA_PASSWORD":“<password>”,
"VAT_SCHEMA_PASSWORD":“<password>”,
"EIE_SCHEMA_PASSWORD":“<password>”,
"ELM_SCHEMA_PASSWORD":“<password>”
}
4. For reference, see the below example schema_credentials.json with sample content.
{ "id": "passwords",
"PLATO_SCHEMA_PASSWORD": "welcome",
"PLATO_SECURITY_SCHEMA_PASSWORD": "welcome",
"PLATO_UI_SCHEMA_PASSWORD": "welcome1",
"SMS_SCHEMA_PASSWORD": "welcome2",
"COMMONCORE_SCHEMA_PASSWORD": "welcome3",
"VAM_SCHEMA_PASSWORD": "welcome4",
"VAC_SCHEMA_PASSWORD": "welcome5",
"VAB_SCHEMA_PASSWORD": "welcome6",
"VAE_SCHEMA_PASSWORD": "welcome7",
"EDA_SCHEMA_PASSWORD": "welcome8",
"VAI_SCHEMA_PASSWORD": "welcome9",
"VAN_SCHEMA_PASSWORD": "welcome10",
"VAS_SCHEMA_PASSWORD": "welcome11",
"VAT_SCHEMA_PASSWORD": "welcome12",
"EIE_SCHEMA_PASSWORD": "welcome13",
"ELM_SCHEMA_PASSWORD": "welcome14"
}
5. Execute the below knife command from chef-repo directory.
knife data bag from file fsgbu_db_deploy schema_credentials.json --
secret-file /scratch/<extracted OSDC
bundle>/oracle_banking_installer_pack/chef-repo/secrets/secret_key --
local-mode
6. Encrypted data bag file look like below (for reference).
{
"id": "passwords",
"PLATO_SCHEMA_PASSWORD": {
2-8
"encrypted_data": "UtFoSAW1FLMw7fCFTP2xhkJUmARTVIeXQBk=\n",
"iv": "DWTMxu8a5yUhPDfU\n",
"auth_tag": "1QsWAXNzH+ojNGI4TkYBWA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"PLATO_SECURITY_SCHEMA_PASSWORD": {
"encrypted_data": "yETI4M/zIAigq/FaVbsxzm9yDKE2pPG5UjI=\n",
"iv": "eFzigWLXjahH48Sr\n",
"auth_tag": "NnDKXOyz/6VxF429q98pDQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"PLATO_UI_SCHEMA_PASSWORD": {
"encrypted_data": "gfKSufpiVz+nnG6B7woI7BbKsK7oZNe6bm4R\n",
"iv": "7XYCIAGZN1B+gqUk\n",
"auth_tag": "NSTZ328TIW3XDq05SO+NAQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"SMS_SCHEMA_PASSWORD": {
"encrypted_data": "I9vkW37WYTQ/dXCQ1yCj/A+Eyy2LmQ350RPa\n",
"iv": "Roeg1i1hanKTAZAP\n",
"auth_tag": "85i0zKkwp7crm9ZlVHslgg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"COMMONCORE_SCHEMA_PASSWORD": {
"encrypted_data": "VhLDWTQWNntjZKWWK/AdvOcgA9DYlrDHX0D4\n",
"iv": "2M+AJsDdj8PvkVQf\n",
"auth_tag": "hb6C2AquVeJRk5L60rTiZA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAM_SCHEMA_PASSWORD": {
"encrypted_data": "+04SjwADFX1CXYuRvkDa8v4b8AxDvUagWvum\n",
"iv": "+5hLqdsnsi5GKFX0\n",
"auth_tag": "jrLTp1uXFVMhwPNzcmFG6Q==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAC_SCHEMA_PASSWORD": {
"encrypted_data": "i1KG/qgm57VWiBEphjA0YlztdZvZQ9YuGtJj\n",
"iv": "ERufOupomjLGlEFi\n",
"auth_tag": "Skp5cwW7e5L6o54zIX59Ag==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAB_SCHEMA_PASSWORD": {
"encrypted_data": "40IbIFq9c/omvcZ6rFwc2D0cKDaL+El91XgL\n",
"iv": "ell71qcI9jxioTBy\n",
"auth_tag": "etNjWnz1nVp/OuAzX2ivQw==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAE_SCHEMA_PASSWORD": {
"encrypted_data": "vlmP9gSSqmVw7MWkb5HR6prBmj53PYLURzd9\n",
2-9
"iv": "4Zgz1+osxNxhO3bv\n",
"auth_tag": "U2jzMvusJgYjJPWZNBIndA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"EDA_SCHEMA_PASSWORD": {
"encrypted_data": "XL4ieKbdB5PLyLHp9R0oZZerzNPTTISxuEdT\n",
"iv": "5bQ0Dqk2CLMhFSB6\n",
"auth_tag": "acLF+7j6Jd5x4vYaUH8pEQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAI_SCHEMA_PASSWORD": {
"encrypted_data": "cQv7lno46AXLC3tJR4VhGiEb4sgDsV0Qc5mg\n",
"iv": "Yr7GHyLh60vH+Q13\n",
"auth_tag": "m3jJ22NTjNDQdDuiYn30wA==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAN_SCHEMA_PASSWORD": {
"encrypted_data": "PG74/2KjeJtOvtg133vJDxlTWxlesw+MBKuD4w==\n",
"iv": "FQ6347RIKCpETo04\n",
"auth_tag": "NKNjWHBYPCtPaldte6RNSg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAS_SCHEMA_PASSWORD": {
"encrypted_data": "W7OWonBCuxr+IQ69/T2+svajJZ3lOSgDFNyf+A==\n",
"iv": "DhXIM87m+ptS/g3s\n",
"auth_tag": "uFUHS0virgLtETxEafKNmg==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"VAT_SCHEMA_PASSWORD": {
"encrypted_data": "JUQxuABctNzaIoc7f1fck/R4ktnL/OIqEHKr/A==\n",
"iv": "LyfKUQGo9bTmcyVb\n",
"auth_tag": "hm7EfhgHGwmcGow8kmI6QQ==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"EIE_SCHEMA_PASSWORD": {
"encrypted_data": "XBkoM6sfBxHksTr+laQtcpnSZ0moi35LzXLTWQ==\n",
"iv": "SfEhG7P/99OpnL4K\n",
"auth_tag": "ANcjNmr+Vy1N8lxuD16R7g==\n",
"version": 3,
"cipher": "aes-256-gcm"
},
"ELM_SCHEMA_PASSWORD": {
"encrypted_data": "jaLv8QSpmi3LsN5G4y3nwZldS4mZL8v6qm0O4g==\n",
"iv": "zbnaZUo+CDvKDXf8\n",
"auth_tag": "Kh3vqGoSZavE7dzn1S5liA==\n",
"version": 3,
"cipher": "aes-256-gcm"
}
}
7. Ensure all json files are on 755 permission.
2-10
2.2 Database Installation
Note: Ensure that all the DB schemas which are required for the product are available before installation.
1. Login to Linux server as root user
2. Go to /scratch/<extracted OSDC bundle>/oracle_banking_installer_pack/chef-repo folder.
3. Update Parameter file “db_deploy_properties.rb” with relevant values as described in below
table.
Attribute Description
ORACLE_SERVER_HOSTNAME Oracle Database Server Hostname
ORACLE_CLIENT_INSTALL_USER User that owns the Oracle home directory.
ORACLE_CLIENT_HOME Path to Oracle database Client home
PDB_SID PDB SID
PDB_PORT PDB Port
PRODUCT_CUSTOM_SCRIPTS_HOME Path to the product directory inside the OSDC
folder.
For example: /scratch/OSDC/<product
directory>
PLATO_SCHEMA_USERNAME Plato schema username
PLATO_SECURITY_SCHEMA_USERNAME Plato security schema username
PLATO_UI_SCHEMA_USERNAME Plato ui config schema username
SMS_SCHEMA_USERNAME SMS schema username
COMMONCORE_SCHEMA_USERNAME Common core schema username
VAM_SCHEMA_USERNAME VAM schema username
VAC_SCHEMA_USERNAME VAC schema username
VAB_SCHEMA_USERNAME VAB schema username
VAE_SCHEMA_USERNAME VAE schema username
2-11
EDA_SCHEMA_USERNAME EDA schema username
VAI_SCHEMA_USERNAME VAI schema username
VAN_SCHEMA_USERNAME VAN schema username
VAS_SCHEMA_USERNAME VAS schema username
VAT_SCHEMA_USERNAME VAT schema username
EIE_SCHEMA_USERNAME EIE schema username
ELM_SCHEMA_USERNAME ELM schema username
4. Execute the shell script db_deploy_installer.sh under /oracle_banking_installer_pack/chef-repo 5. Tail the log file to see the progress
$ tail -f nohup.out
2.3 WebLogic Installation
Note: Ensure that all the DB schemas which are required for the product are available and ensure that the required number of WebLogic managed servers and clusters for the product are up and running on configured SSL before installation.
1. Login to Linux server as root user
2. Go to /scratch/<extracted OSDC bundle>/oracle_banking_installer_pack/chef-repo folder. 3. Ensure that the Weblogic install user (user that owns weblogic home directory) has write
permission on the extracted OSDC bundle.
4. Update Parameter file “pre_installation_properties.rb” with relevant values as described in below table
Attribute Description
PRODUCT_BUNDLE_HOME Path to the product directory inside the OSDC folder.
For Example: /scratch/OSDC/<product directory>.
APP_STARTERS_PATH_URL Path to the destination folder inside which App starters
files should be copied.
TASKS_PATH_URL Path to the destination folder inside which Task files
should be copied.
5. Execute the shell script pre_installation_package_mw_deploy.sh under /oracle_banking_installer_pack/chef-repo
6. Tail the log file to see the progress $ tail -f nohup.out
2-12
7. Update Parameter file “mw_deploy_properties.rb” with relevant values as described in below
table.
Attribute Description
JAVA_HOME Path to the directory where java is installed.
WLS_HOME Path to the WebLogic home directory.
WLS_INSTALL_USER User who owns the WebLogic home directory
WLS_INSTALL_USER_GROUP Group that owns the WebLogic home directory.
WLS_DOMAIN_NAME Name of the WebLogic domain
IS_TARGET_CLUSTER Whether the targets to which the deployment is to
be done are clusters (true/false)
WLS_SSL_CUSTOM_TRUST_FILE Location of the SSL custom trust file
WLS_SSL_CUSTOM_TRUST_KEYSTO
RE_TYPE
SSL Trust KeyStore Type(JCEKS or JKS)
WEBLOGIC_ADMIN_HOST Weblogic Admin Host
WEBLOGIC_ADMIN_LISTEN_PORT WebLogic Admin listen port
WEBLOGIC_ADMIN_SSL_PORT WebLogic Admin SSL port
ORACLE_PDB_SID Oracle PDB SID for data source configuration
ORACLE_PDB_HOSTNAME Oracle PDB hostname for data source
configuration
ORACLE_PDB_PORT Oracle PDB port for data source configuration
PRODUCT_BUNDLE_HOME Path to the product directory inside the OSDC
folder.
For Example: /scratch/OSDC/<product directory>
DISCOVERY_SVCS_TARGET Target (managed server /cluster) for plato-
2-13
discovery-service
CONFIG_SVCS_TARGET Target(managed server /cluster) for plato-config-
service
API_GATEWAY_TARGET Target(managed server /cluster) for plato-api-
gateway
UI_CONFIG_TARGET Target(managed server /cluster) for plato-ui-
config-service
SMS_CORE_SVCS_TARGET Target(managed server /cluster) for sms-core-
services
CMN_CORE_SVCS_TARGET Target(managed server /cluster) for all
commoncore services
VAM_SVCS_TARGET Target(managed server /cluster) for obvam-
account-services
VAC_SVCS_TARGET Target(managed server /cluster) for obvam-core-
services
VAB_SVCS_TARGET Target(managed server/cluser) for obvam-eca-
services
VAE_SVCS_TARGET Target(managed server/cluser) for obvam-entity-
services
EDA_SVCS_TARGET Target(managed server/cluser) for obvam-
external-dda-services
VAI_SVCS_TARGET Target(managed server/cluser) for obvam-
identifier-services
VAN_SVCS_TARGET Target(managed server/cluser) for obvam-
internal-transfer-services
VAS_SVCS_TARGET Target(managed server/cluser) for obvam-
statement-services
VAT_SVCS_TARGET Target(managed server/cluser) for obvam-
2-14
transaction-journal-services
EIE_SVCS_TARGET Target(managed server/cluser) for external-
interest-engine-service
ELM_SVCS_TARGET Target(managed server/cluser) for external-
liquidity-management-service
UI_APPSHELL_TARGET Target(managed server/cluser) for obvam-app-
shell-14.3.0.0.0
PLATO_DS_USERNAME Plato datasource username
PLATO_SECURITY_DS_USERNAME Plato security datasource username
PLATO_UI_CONFIG_DS_USERNAME Plato UI Config datasource username
PLATO_UI_CONFIG_DS_USERNAME Plato UI Config datasource username
SMS_DS_USERNAME SMS datasource username
VAM_DS_USERNAME VAM datasource username
VAC_DS_USERNAME VAC datasource username
VAB_DS_USERNAME VAB datasource username
VAE_DS_USERNAME VAE datasource username
EDA_DS_USERNAME EDA datasource username
VAI_DS_USERNAME VAI datasource username
VAN_DS_USERNAME VAN datasource username
VAS_DS_USERNAME VAS datasource username
VAT_DS_USERNAME VAT datasource username
EIE_DS_USERNAME EIE datasource username
2-15
ELM_DS_USERNAME ELM datasource username
PLATO_DS_TARGET List of target clusters/managed servers for PLATO
datasource
PLATO_SECURITY_DS_TARGET List of target clusters/managed servers for
PLATO_SECURITY datasource
PLATO_UI_CONFIG_DS_TARGET List of target clusters/managed servers for
PLATO_UI_CONFIG datasource
SMS_DS_TARGET List of target clusters/managed servers for
SMSdatasource
CMN_CORE_DS_TARGET List of target clusters/managed servers for
COMMONCORE datasource
VAM_DS_TARGET List of target clusters/managed servers for VAM
datasource
VAC_DS_TARGET List of target clusters/managed servers for VAC
datasource
VAB_DS_TARGET List of target clusters/managed servers for VAB
datasource
VAE_DS_TARGET List of target clusters/managed servers for VAE
datasource
EDA_DS_TARGET List of target clusters/managed servers for EDA
datasource
VAI_DS_TARGET List of target clusters/managed servers for VAI
datasource
VAN_DS_TARGET List of target clusters/managed servers for VAN
datasource
VAS_DS_TARGET List of target clusters/managed servers for VAS
datasource
VAT_DS_TARGET List of target clusters/managed servers for VAT
2-16
datasource
EIE_DS_TARGET List of target clusters/managed servers for EIE
datasource
ELM_DS_TARGET List of target clusters/managed servers for ELM
datasource
8. Execute the shell scripts under /oracle_banking_installer_pack/chef-repo in the following order
plato_mw_deploy_installer.sh
sms_mw_deploy_installer.sh
commoncore_mw_deploy_installer.sh
domain_services_mw_deploy_installer.sh
Note: Before running each shell script, update the properties in “mw_deploy_properties.rb” as described in the above table.
9. Tail the log file to see the progress $ tail -f nohup.out
3-1
3. Batch Process
Batches are introduced to complete the some of the end of the day related task. Below are the batches need to configure as part of the installation process.
Batch Name Archive name OSDC path
Forget Core account Task
cmc-forget-account-task-1.0.0.jar
{unzip the file} COMMON_CORE\cmc-account-services\TASK
Forget Core Customer Task
cmc-forget-customer-task-1.0.0.jar
{unzip the file}COMMON_CORE\cmc-customer-services\TASK
Forget Virtual Accounts
obvam-forget-account-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Forget Virtual Customers
obvam-forget-entity-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-entity-services\TASK
Virtual Inactive Task obvam-account-inactive-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Account Statement Generation Task
obvam-account-statement-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Un Tanking Task obvam-untanking-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Turnover Balance Task
obvam-account-turnover-balance-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Value Date Task obvam-account-valuedate-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
Credit Limit Re Valuation Task
obvam-creditlimit-util-reval-task-1.0.0.jar
{unzip the file} OBVAM_SERVICES\obvam-account-services\TASK
3.1 Configuration and Running Batch
Batches can be triggered independently using command prompt. Based on the EOD or requirement, scheduling the batches are the recommended way to trigger the batches.
3-2
Before running the batches ensure required JDK is installed. Separate Schema is recommended to have for the batches.
Ensure you provide the database Connections and Eureka URL specific to the Environment.
--spring.datasource.url
--spring.datasource.username
--spring.datasource.password
--plato.services.eureka.uri
A list of all batches are explained.
3.2 obvam-amount-block-expiry-task
System to release the amount block for the Virtual accounts during EOD Date based on the configured expiry date. Provide the job Parameters such as Branch Code, User Id and EOD Date to which EOD Date amount blocks must be released.
3.2.1 Running obvam-amount-block-expiry-task
Batch Command:
java -jar obvam-amount-block-expiry-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXX:XXX/XXXX --
spring.datasource.username=XXX --spring.datasource.password=XXX --
plato.services.eureka.uri=http://XXXX:XXX/plato-discovery-
service/eureka branchCode=XXX userId=XXXX
3.3 obvam-account-inactive-task
System automatically marks the virtual accounts as inactive if there are no transactions getting posted on it for more number of days than that is configured at the account code level. Provide the job Parameters such as Branch Code, User Id and EOD Date.
3.3.1 Running obvam-account-inactive-task
Batch Command:
java -jar obvam-account-inactive-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXX:XXX/XXXX --
spring.datasource.username=XXX --spring.datasource.password=XXX --
plato.services.eureka.uri=http://XXXX:XXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX
3-3
3.4 obvam-forget-account-task
PII data access can be controlled based on the user role. We can configure details of an account who wants to be forgotten, if the customer does not withdraws/avail for virtual account facility. Provide the job Parameters such as Branch Code, User Id, EOD Date and retention Period.
If Account is in closed state for x no. of days (x time period) then after that those records should be removed (purged) or data should be anonymized. That time period is called retention period. And this will be property of a bank not branch/customer/account.
3.4.1 Running obvam-forget-account-task
Batch Command:
java -jar obvam-forget-account-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXXX:XXXX/XXXX --
spring.datasource.username=XXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXX userId=XXXXX
3.5 obvam-forget-entity-task
PII data access can be controlled based on the user role and we can configure details of an entity, who wants to be forgotten if the Entity does not withdraws/avail for the virtual account facility. Provide the job Parameters such as Branch Code, User Id, EOD Date and retention Period.
If Entity is in closed state for x no. of days(x time period) then after that those records should be removed (purged) or data should be anonymized. That time period is called retention period. And this will be property of a bank not branch/customer/account.
3.5.1 Running obvam-forget-entity-task
Batch Command:
java -jar obvam-forget-entity-task-1.0.0.jar --spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXX:XXXX/XXXX --
spring.datasource.username=XXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX
3.6 cmc-forget-account-task
PII data access can be controlled based on the user role. We can configure details of a core accounts who wants to be forgotten.
As a bank OPS user, I want to forget the core accounts present in common core during End Of Day which are configured in the forget core account screen.
If Account is in closed state for x no. of days(x time period) then after that those records should be removed (purged) or data should be anonymized. That time period is called retention period. And this will be property of a bank not branch/customer/account.
3-4
3.6.1 Running cmc-forget-account-task
Batch Command:
java -jar cmc-forget-account-task-1.0.0.jar --spring.datasource.driver-
class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXX:XXXXX/XXXXX --
spring.datasource.username=XXXXX --spring.datasource.password=XXXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX
3.7 cmc-forget-customer-task
PII data access can be controlled based on the user role. We can configure details of core customers who want to be forgotten.
As a bank OPS user, I want to forget the core customers present in common core during End Of Day which are configured in the forget core customers screen.
If Customer is in closed state for x no. of days(x time period) then after that those records should be removed (purged) or data should be anonymized. That time period is called retention period. And this will be property of a bank not branch/customer/account.
3.7.1 Running cmc-forget-customer-task
Batch Command:
java -jar cmc-forget-customer-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXXX:XXXX/OBVAMTESTPDB --
spring.datasource.username=XXXXX --spring.datasource.password=XXXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXXX
3.8 obvam-untanking-task
System automatically un tanks all the transactions that are tanked during the EOD, after date change has been completed successfully.
3.8.1 Running obvam-untanking-task
Batch Command:
java -jar obvam-untanking-task-1.0.0.jar --spring.datasource.driver-
class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXX:XXXX/XXXXX --
spring.datasource.username=XXXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXX:XXXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXXX tankedTxnCount=1
3.9 obvam-account-statement-task
System to generate the account statement (PDF file format is generated) during EOD for the virtual entities based on the statement preference configured.
3-5
3.9.1 Running obvam-account-statement-task
Batch Command:
java -jar obvam-account-statement-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXX:XXXX/XXXX --
spring.datasource.username=XXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX outputPath=C:\
3.10 obvam-account-valuedate-task
System to update the transaction amount according to the value date for each transactions.
3.10.1 Running obvam-account-valuedate-task
Batch Command:
java -jar obvam-account-valuedate-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXXX:XXXXX/XXXX --
spring.datasource.username=XXXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX
3.11 obvam-account-turnover-balance-task
During EOD, calculate the total debit turnover balance and credit turnover balance for the virtual accounts and update specific to Virtual accounts.
3.11.1 Running obvam-account-turnover-balance-task
Batch Command:
java -jar obvam-account-turnover-balance-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
spring.datasource.url=jdbc:oracle:thin:@//XXXXXX:XXXX/XXXXX --
spring.datasource.username=XXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXXX:XXXX/plato-discovery-
service/eureka branchCode=XXXX userId=XXXX
3.12 obvam-creditlimit-util-reval-task
As the exchange rate can vary over time, there should be a daily batch to do revaluation for the line currency equivalent for the 'utilized amount in account currency' and make the required updates in utilization, whenever the utilization currency and line currency are different. This task performs the required action-
3.12.1 Running obvam-creditlimit-util-reval-task
Batch Command:
java -jar obvam-creditlimit-util-reval-task-1.0.0.jar --
spring.datasource.driver-class-name=oracle.jdbc.OracleDriver --
3-6
spring.datasource.url=jdbc:oracle:thin:@//XXXXX:XXXX/XXXXX --
spring.datasource.username=XXXX --spring.datasource.password=XXXX --
plato.services.eureka.uri=http://XXXXX:XXXXX/plato-discovery-
service/eureka branchCode=XXXXX userId=XXXX
4-1
4. BIP Configuration
This documentation is focused on the configuration of BIP for the generation of reports. The procedure includes two steps:
Configuring the Data Model
Configuring the Report Absolute Path
4.1 Configuring Data Model
The data model designed for the report is to be uploaded to the BIP server.
1. Open the BIP console. Sign in with BIP credentials.
2. Click Catalog and select the folder on which the data model file needs to be uploaded.
3. Click Upload icon to upload a file.
4. Choose the data model file from OBVAM_SERVICES\obvam-statement-services\BIP\DataModels path (.xdmz) and click Upload.
4.2 Configuring the Report Absolute Path
The report absolute path file created for the report is to be uploaded to the BIP server.
1. Click Catalog and select the folder on which the file must be uploaded.
4-2
2. Click Upload icon to upload a file.
3. Choose the report absolute path file from OBVAM_SERVICES\obvam-statement-services\BIP\Reports\AccountStatement\ AccountStatement_en.xdoz (.xdoz) and click Upload.
5-1
5. Logging Area
This part of the document will talk about the logging area of OBVAM applications in server.
5.1 Logging Area
Logging area is configurable, you can configure any path within the server, where you want OBVAM application to write logs. OBVAM applications will wright logs in the configured path with below name:
<Application name>.logs
Example: if application name is obvam-account-services, then logs file name would be obvam-account-servies.logs
To configure logging path, refer Annexure-1 Post Domain Creation Section.
Recommended