Oracle Banking Digital Experience Installation Guide

Oracle Banking Digital
Experience
Installation Guide
Release 18.1.0.0.0
Part No. E92727-01
January 2018
Installation Guide
January 2018
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
www.oracle.com/financialservices/
Copyright © 2018, 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.
Installation Guide ii
Table of Contents
1. Preface ................................................................................................................................................. 4
2. Introduction ......................................................................................................................................... 6
3. Prerequisites ....................................................................................................................................... 7
4. Installation ........................................................................................................................................... 9
5. Installation In Silent Mode ............................................................................................................... 22
6. Installer Verification ......................................................................................................................... 25
7. Installer Scope .................................................................................................................................. 26
8. Post Installation Steps ..................................................................................................................... 30
9. Configuring the Connector Credential Store ................................................................................. 61
10. OBDX Product Verification........................................................................................................... 62
11. Configuration for OUD/OAM ........................................................................................................ 65
12. Multi Entity ..................................................................................................................................... 78
13. Multi-entity installation In Silent Mode ....................................................................................... 84
14. OBDX Product Security ................................................................................................................ 87
15. Troubleshoot Overview ................................................................................................................ 88
Installation Guide iii

Preface
1. Preface
1.1 Intended Audience
This document is intended for the following audience:
 Customers
 Partners
1.2 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program
website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
1.3 Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information,
visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
1.4 Structure
This manual is organized into the following categories:
Preface gives information on the intended audience. It also describes the overall structure of the
User Manual.
The subsequent chapters cover following:
 Introduction
 Prerequisites
 Installation
 Post Installation Steps
 Product Verification
 Multi-Entity Installation and configuration
1.5 Related Information Sources

For more information on Oracle Banking Digital Experience Release 18.1.0.0.0, refer to the
following documents:
 Oracle Banking Digital Experience Licensing Guide
 Oracle Banking Digital Experience Installer Pre-Requisite Setup Manual
 Oracle Banking Digital Experience OBP Base Setup and Configuration
 Oracle Banking Digital Experience OBP US LZN Setup and Configuration
 Oracle Banking Digital Experience OFSLL Setup Configuration
 Oracle Banking Digital Experience Origination Social Media Integration
 Oracle Banking Digital Experience OHS User Interface Configuration
 Oracle Banking Digital Experience Chatbot Configuration
Installation Guide 4
Preface
 Oracle Banking Digital Experience Mobile Application Builder-Android

 Oracle Banking Digital Experience Mobile Application Builder-iOS
 Oracle Banking Digital Experience Security Guide
 Oracle Banking Digital Experience System Configuration
 User Manual Oracle Banking Digital Experience Core
 Oracle Banking Digital Experience File Upload Report Configuration
Introduction
2. Introduction
2.1 Purpose of the Document
The purpose of the OBDX Installation Manual is to provide a step by step overview on the
installation process of the solution.
It includes:
 Reference to prerequisites software installation required for OBDX & OBDX installer
 Setup of OBDX with Oracle’s own Core Banking and Origination Products along with Third-
party HOST system.
 Running the installation in silent mode
 Advanced Configurations (Post installation)
 Installation Verification
 Multi-Entity Installation and configuration
Home
Prerequisites
3. Prerequisites
OBDX pre-requisite software should be installed and available before proceeding.
For OBDX pre-requisite software setup refers document “Oracle Banking Digital Experience Installer Pre-
Requisite Setup Manual” mentioned in section 1.5 Related Information Sources.
Installer Pre-requisite verification

Post installation of OBDX Installer prerequisite software’s, verification can be done using below steps.
Note: Verification should be performed on Server where Oracle Weblogic is locally installed and by OS
user (which is owner for Oracle Weblogic home directory) for non-root steps. The same user will be used
to execute installer.
Oracle Instant client

Step 1: Login using root user.
Step 2 : Run below command to verify if Oracle Instant client is installed.
rpm –qa | grep oracle
Note: Above package verification command is specific to Oracle Linux and RHEL distributions only. For
other Linux distributions or OS please refer to OS specific package manager documentation.
Python
Step 1: Execute python –V command
python -V
Note: Ensure Python 2.7.5 supported version is installed. Above command should reflect the same.
cx_Oracle & Urwid
Step 1: Execute python command

python
Note: Ensure Python 2.7.5 version should be available in PATH variable. Above execution should be
done using Python 2.7.5.
Prerequisites
Step 2: Import Urwid and check version

import urwid (Press Enter)
urwid.__version__
If version is displayed, then Urwid is installed and available for use.
Note: Ensure Urwid 1.3.1 supported version is installed. Above command should reflect the same.
Step 3: Similarly import cx_Oracle and check version

import cx_Oracle (Press Enter)
cx_Oracle.version
If version is displayed, then cx_Oracle is installed and available for use.
Note: Ensure cx_Oracle 5.2.1 supported version is installed. Above command should reflect the same.
Home
Installation
4. Installation
Pre-Installation
 Install all the prerequisite software and packages mentioned above
Steps of Installation
 Download and extract the installer zip file (Base – non localization version).
 Navigate to “<OBDX INSTALLER DIR>/core/config”
 Open the “installer.properties” file to maintain key configurations for BASE ENTITY (OBDX_BU)
IMPORTANT:
 Enter the values right after the “=” sign

 DO NOT change anything to the left of the “=”
 DO NOT change any of the flag values or pre-filled values (such as DataSourceName,
DataSourceJNDI, Flag values etc) available post “Factory Shipped” section.
 Ensure there is no blank space after “=” sign
Installation
Only below parameters should be set in installer.properties file.
Component Parameter Description Example
Enter the hostname of the

database server which would host
the database schema for OBDX
DatabaseHostName and RCU ofss310759
Enter the port number of the

DatabaseHostPort database listener 1521
Enter the Oracle Service Name for

DatabaseHostSID database instance OBDXSID
Enter the username with 'sys'

DB details (for
DB_SYS_USER privileges sys
Weblogic RCU and
OBDX schema) For OBDX schema name like
"OBDX_DEV" POST FIX is 'DEV'.
SHOULD BE IN UPPERCASE
POST_FIX ONLY. DEV
DIRECTORY_NAME Enter the directory name in which

you want the OBDX schema
tablespace datafile to be created.
OPATCH_LOG_D
Enter Logical name (i.e.
IR
DIRECTORY_NAME column) from
DBA_DIRECTORIES table NOT
the physical path.
DatabaseHostNameU Enter the hostname for the UBS

BS HOST database host server ofss310759
DatabaseHostPortUB Enter the port number of the UBS

S database listener 1521
Enter the Complete OBDX-EXT

(B1A1) HostInterfaceschema
UBS DB details (to name you want installer to create
be configured only as new schema.
in-case of SCHEMA_NAME_UB SHOULD BE IN UPPERCASE
FLAVOR as UBS) S ONLY. UBSSCHEMA123
Enter the directory name in which

you want the OBDX-EXT (B1A1)
schema tablespace datafile to be
created. Enter Logical name (i.e.
DIRECTORY_NAME column) from
DIRECTORY_NAME_ DBA_DIRECTORIES table NOT
UBS the physical path. OPATCH_LOG_DIR
Installation
Enter the username with 'sys'

DB_SYS_USER_UBS privileges sys
DatabaseHostSID_UB Enter the UBS Host database

S Service Name UBSSID
Enter the EXISTING UBS Host

UBS_SCHEMA schema name OBDXUBS
Enter the Country code for UBS

UBS_CCY HOME Branch GB
UBS_HB Enter the Branch code for

code for UBS HOME Branch AT3
Middleware home path. Example

/home/obdxuser/Oracle/Middlewar
e/Oracle_Home - where you have /home/obdxuser/Or
directories like acle/Middleware/Or
MiddlewareHome wlserver,oracle_common etc. acle_Home
Path where JAVA (JDK) is /home/obdxuser/jdk1

JAVA_HOME installed 8
Path where OBDX is to be

installed. All configuration files will
be copied as a sub-directory
“config” under this directory. DO
NOT KEEP
WEBLOGIC INSTALLATION_HOM INSTALLATION_HOME AS
E MiddlewareHome. /home/obdxuser/obdx
server details
Path where OBDX Weblogic
domain should be created. Users
can now enter custom path as per /home/obdxuser/dom
DOMAIN_PATH their requirements. ains
Name of cluster; this cluster would

ClusterName have one single managed server. obdx_cluster
Host name or IP address of

managed server participating in
the cluster. Currently only single
node is supported.
ClusterMachineName
List ofss310759
Installation
AdminServer port. It is the port to

access the administrative console
of the Weblogic server. Generally 7001
HostMachinePort
port 7001 is used as the
AdminServer port.
AdminServer SSL port. It is the

port used to securely access
(https) the administrative console
of the Weblogic server. Generally
port 7002 is used as the 7002
HostMachineSSLPort AdminServer port.
Node Manager Port. It is the port

used by Node Manager to be
configured for OBDX domain.
Generally, 5556 is utilized as Node
Manager Port. Custom ports are
NodeManagerPort supported. 5556
Managed server name. This will be

the name of the managed server
created in the cluster followed by
clip
indexes. eg- If this is set as 'clip'
managed servers would be
ManagedServerName clip1etc.
Managed Server Port. Managed

server will utilize this port for
hosting OBDX components and
ManagedServerPort associated resources. 9001
DomainName Enter Weblogic Domain name. obdx_domain1
Domain user ID. The user id will be

used to access the Weblogic
DomainUserID Administrative console. weblogic
Set the paths for the persistence

stores of the FileUpload JMS
FileUploadFileStore modules. DO NOT KEEP path as
(to be configured for INSTALLATION_HOME or as
all OBDX supported sub directory inside /scratch/obdx/
HOST) INSTALLATION_HOME. FileUpload

stores of the Audit JMS modules.
AuditFileStore (to be DO NOT KEEP path as
configured for all INSTALLATION_HOME or as
OBDX supported sub directory inside
HOST) INSTALLATION_HOME. /scratch/obdx/Audit
ReportsFileStore (to Set the paths for the persistence

be configured for all stores of the Reports JMS /scratch/obdx/Repo
modules. DO NOT KEEP path as rts
OBDX supported
Installation
HOST) INSTALLATION_HOME or as
sub directory inside
INSTALLATION_HOME.

stores of the ExtSystemReceiver
ExtSystemReceiverFil JMS modules. DO NOT KEEP
eStore (to be path as INSTALLATION_HOME
configured for Third- or as sub directory inside
/scratch/obdx/Recei
party OBDX host only) INSTALLATION_HOME.
ver
stores of the ExtSystemSender
ExtSystemSenderFile JMS modules. DO NOT KEEP
Store (to be path as INSTALLATION_HOME
configured for Third- or as sub directory inside
/scratch/obdx/Send
party OBDX host only) INSTALLATION_HOME.
er
Set the IP and port for UBS
JMSForeignServerUR 10.184.135.59:786
Managed server where JMS queue
are available (Specific to OBDX – 0
L (to be configured for
UBS host only) UBS flavor)
STB schema name prefix. If schema

RCU pre-fix is 'OBDX' then 'OBDX_STB'
STBSchemaPrefix would be the STB schema name. OBDX_STB
Set username for OBDX application

Admin user. USERNAME IS CASE
SENSITIVE. In-case of OUD as
provider username should be the
User ID mentioned during user
creation steps mentioned in pre-
requisite document (refer To create
OBDXAuthenticato
User and mapping it to the Group
r Admin user DBAuthUser section) superadmin
details
Enter the Email ID for OBDX [email protected]
DBAuthMailID application admin user. om
Enter the mobile number for OBDX

application admin user. COUNTRY
DBAuthPhoneNo CODE IS MUST. +911234567890
Note: Apart from above any other property values should not be modified
Ensure ORACLE_HOME, JAVA_HOME variable are set and their binaries are available in PATH variable
before proceeding.
Login with OS user which was used to perform OBDX pre-requisite software installation (or has
ownership on Oracle Weblogic home directory)
Ensure OBDX Installation home and filestore path maintained in installer.properties exists and user
running the installer has read-write permissions.
 From your terminal navigate to <OBDX INSTALLER DIR>/
 Enter the following command
Installation
python runInstaller.py
Select the appropriate type of Installation
 OBDX Installation: This option should be used for first-time installation or for first entity only. Existing
installation should not utilize this option unless performing “Clean and Install” on already installed
environment.
 New Entity Creation: This option should be used for multi-entity installation only.
Post selection of installation type.

Select the appropriate host system for Installation
Installation
Post selection of host system below installation mode would be available
Installation
Mode of Installation - New Installation
 New installation
In-case of a fresh installation of OBDX with appropriate host system for the first run on server.
Below screens would appear with respective to host selected
Installation
Universal Banking Solution (OBDX with UBS)
Select the version of UBS HOST system from available options
Post UBS HOST version selection, enter the required credentials details
Installation
Enter below passwords:

 SYS privilege user password where OBDX schema would be created
 OBDX schema password
 OBDX STB schema password
 Weblogic console administrator user password
 SYS privilege user password where UBS host schema exists
 Existing UBS HOST schema password
 New OBDX EXT schema password
 Password for OBDX application admin user (In-case of OUD as provider, password should be
similar to one used while user creation in OUD (or User Password field))
Oracle Banking Platform (OBDX with OBP)

No additional input required. Screen is same as available in Third Party System.
Oracle Financial Services Lending and Leasing (OBDX with OFSLL)

No additional input required. Screen is same as available in Third Party System.
Installation
Third Party System (OBDX with THP)
Post Third Party System selection, enter the required credentials details
Enter below passwords:
 SYS privilege user password where OBDX schema would be created

 OBDX STB schema password
 OBDX application admin user password (In-case of OUD as provider, password should similar to
one used while user creation in OUD (or User Password field))
Installation
Mode of Installation - Clean and Install

In-case of an existing OBDX installation that you want to overwrite OR in case of a previously failed
installation user can opt for this option.
Pre-requisites
 Weblogic domain processes should be down (i.e. AdminServer, NodeManager, Managed Servers,
Derby etc)
 No open session (user should not be logged-in) with OBDX database schema (and OBDX EXT
schema in-case of OBDX UBS flavor) and RCU schema.
Key pointers
 OBDX schema (and OBDX EXT schema in-case of OBDX UBS flavor) and RCU schema would be
dropped and recreated (as per installer.properties). Tablespace would be re-used.
 Weblogic domain (as per installer.properties) would be deleted and created again.
 Installation Home would be cleaned up and all files/ sub-directories would be deleted.
Note: All input screens are similar to new installation option and as per the host system opted.
Installation
Installation Status
After selecting the mode and entering all required details, the status is displayed (as shown below) on the
terminal to indicate the progress of the installation.
When the installation completes, the below message is displayed
Home
Installation In Silent Mode
5. Installation In Silent Mode

This chapter describes how to run the OBDX installer in silent mode.
What is silent-mode installation?
During installation in silent mode, the installation program reads the details for your configuration from the
environment properties and installer.properties that you set for the session before beginning the
installation. The installation program does not display any configuration options during the installation
process.
Steps for Silent-Mode Installation
 Set the environment variables
Below parameters should be set in environment variables
Parameter Description
FLAVOUR Flavour for installation
‘UBS’ for Universal Banking Solution (Installation
with UBS)
MODE Mode of installation.
‘New’ in-case of a fresh installation of OBDX for
the first run on server
‘Clean’ in-case of an existing OBDX installation
that you want to overwrite OR in case of a
previously failed installation
Universal
Banking DB_SYS_PASSWORD Sys password of OBDX database (Existing)
Solution (OBDX SCHEMA_PASS Password for new schema on OBDX database
with UBS ) STBPassword Password for STB schema
DomainPassword Password for weblogic admin console
DB_SYS_PASSWORD_UBS Sys password of UBS database (Existing)
UBS_PASS Password of existing HOST UBS schema
(Existing)
SCHEMA_PASS_UBS Password for new B1A1 schema on UBS database
DBAuthPassword Password for new Admin user of the application
(In-case of OUD as provider, password should
similar to one used while user creation in OUD(or
User Password field))
FLAVOUR Flavour for installation
‘OBP’ for Oracle Banking Platform (OBDX with

OBP)‘
OBDX’ for Third Party System (OBDX with THP)
‘FLL’ for Oracle Financial Services Lending and

Oracle Banking Leasing (OBDX with OFSLL)
Platform (OBDX Mode Mode of installation.
with OBP)/
Oracle ‘New’ in-case of a fresh installation of OBDX for
Financial the first run on server
Services
Lending and ‘Clean’ in-case of an existing OBDX installation
Leasing (OBDX that you want to overwrite OR in case of a
with OFSLL) previously failed installation
/
Third Party DB_SYS_PASSWORD Sys password of OBDX database (Existing)
System (OBDX SCHEMA_PASS Password for new schema on OBDX database
with THP)
STBPassword Password for STB schema
DomainPassword Password for weblogic admin console
DBAuthPassword Password for new Admin user of the application
(In-case of OUD as provider, password should
similar to one used while user creation in OUD (or
User Password field))
Run the runInstaller.py file with ‘--silent ’ argument along with ‘--base’ option
Installation Status
After all passwords are entered, the status is displayed on the terminal to indicate the progress of the
installation.
Home
Installer Verification
6. Installer Verification
Each execution creates a new directory as <DDMonthHHMM> under <OBDX INSTALLER
DIR>/ExecInstances directory where output logs as describe are stored.
Log Description PATH
<OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>

Summarized Installer Activity Log /logs/obdx_installer.log

Summarized Database Logs /logs/db/DB_installation.log
Detailed OBDX DB Logs per SQL <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>

file /logs/db/OBDX/*
Detailed UBS DB Logs per SQL

file (specific to UBS host system <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>
only) /logs/db/UBS/*

RCU Logs /logs/app/obdx_stb_rcu_1600.log

Weblogic Configuration Logs /logs/app/obdx_wls_post.log
Detailed policy seeding logs per <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>

SQL Statement /logs/db/out.log
Detailed policy seeding logs if SQL

execution fails
Note: It will be created in case of <OBDX INSTALLER DIR>/ExecInstances/<DDMonthHHMM>
failure during execution of policies. /logs/db/error.log

Policy seeding jar failure Log /logs/db/seedPolicies.log
Check all the logs for any errors.
Home
Installer Scope
7. Installer Scope
OBDX Installer currently covers below activities:
Flavor: Third Party system (OBDX with THP)
New
Flavor Activity Detailed Activity List Installation Clean and Install
Create Tablespace √ NA
Create Schema and √ (drop and

Role √ create)
OBDX DB Setup
Grants √ √
Load DB object (DDL's

and DML's) √ √
Compile Schema √ √
RCU schema and √ (drop and

Create Domain √ create)
Create and Configure

AdminServer, Machine,
Managed Server and
OBDX Cluster √ √
(Installation
with Third Configure NodeManager √ √
Party System)
Configure JDBC √ √
Weblogic Setup and
Configure DB
Configuration
Authenticator, JMS
servers, Persistent
stores and JMS Modules √ √
Application Deployment √ √
JTA √ √
Enable Production Mode √ √
Start AdminServer and

NodeManager √ √
√ (Delete old
and copy new
OBDX Configuration
Copy Config files into from installer
OBDX Installation Home √ zip)
Installer Scope
Flavor: Universal Banking Solution (OBDX with UBS)
New Clean and

Flavor Activity Detailed Activity List Installation Install
√ (drop and
Create Schema and Role √ create)
OBDX DB Setup
Grants √ √

and DML's) √ √
√ (drop and
Grants √ √
OBDX
EXTSYSTEM DB
Setup
OBDX with and DML's) √ √
UBS
(Installation DB Link pointing to
with OBDX Schema √ √
Universal
Banking Compile Schema √ √
Solution)
RCU schema and Create √ (drop and
Domain √ create)
Create and Configure

AdminServer, Machine,
Managed Server and
Cluster √ √
Configure NodeManager √ √
Weblogic Setup Configure JDBC √ √

and Configuration
Configure DB
Authenticator, JMS
servers, Persistent
stores and JMS Modules √ √
JTA √ √
Installer Scope
New Clean and


NodeManager √ √
Copy Config files into

OBDX Installation Home √ (Delete old
OBDX
and configure and copy new
Configuration
Preferences.xml (set from installer
AdapterFactories) √ zip)
Flavor: Oracle Banking Platform (OBDX with OBP)
New Clean and

√ (drop and
OBDX DB
Setup Grants √ √
Load DB object (DDL's and

DML's) √ √
RCU schema and Create √ (drop and

Domain √ create)
OBDX with
OBP Create and Configure
(Installation AdminServer, Machine,
with Oracle Managed Server and Cluster √ √
Banking
Platform) Configure NodeManager √ √
Configure JDBC √ √
Weblogic
Setup and Configure DB Authenticator,
Configuration JMS servers, Persistent stores
and JMS Modules √ √
JTA √ √

NodeManager √ √
√
OBDX Copy Config files into OBDX √ (Delete old
Installer Scope
New Clean and

Configuration Installation Home and copy new
from installer
zip)
Flavor: Oracle Financial Services Lending and Leasing ( OBDX with OFSLL)
New Clean and

√ (drop and
OBDX DB
Setup Grants √ √
Load DB object (DDL's and

DML's) √ √
RCU Schema and Create √ (drop and

Domain √ create)
OBDX with
OFSLL Create and Configure
(Installation AdminServer, Machine,
with Oracle Managed Server and Cluster √ √
Financial
Services Configure NodeManager √ √
Lending
and Configure JDBC √ √
Leasing) Weblogic
Setup and Configure DB Authenticator,
Configuration JMS servers, Persistent stores
and JMS Modules √ √
JTA √ √

NodeManager √ √
Copy Config files into OBDX √ (Delete old
Installation Home and configure and copy new
OBDX Preferences.xml (set from installer
Configuration AdapterFactories) √ zip)
Home
Post Installation Steps
8. Post Installation Steps

Once Installation is successful and no errors are observed, proceed with below set of steps.
Apply JRF Template

To apply JRF template follow below steps.
 To do this, ensure that the Admin Server is running. Login to the EM (Enterprise Manager) Console
using the following URL:
http://<hostname>:<admin_port>/em
Note: EM console would be available on same hostname and port which was used for Weblogic Admin
Console for OBDX domain (created via installer), just replace the “/console” with “/em”.
 Enter Weblogic administrator username and password (same used for Weblogic administrator
console login)
Click on Sign In
 Click on the Managed Server (as highlighted below)
Note : Depending on installer.properties, Managed server will differ from above screenshot.
 Click on “Lock and Edit” option (as shown in screenshot).
You will see below screen stating the edit session confirmation
 Click on “Apply JRF Template” option (as shown in screenshot).
Is JRF successfully applied, you will get below Confirmation.
 Click on “Activates Changes” option (as shown in screenshot).
Post activation you will receive below Confirmation.
Configure User Lockout attributes in Weblogic
The User Lockout attributes in Weblogic under Home>Security Realms>myrealm need to be in sync with the
Password Policy Maintained in LDAP or DBAuthenticator.In case of DBAuthenticator it has to be in sync with
Password Policy Maintenance in OBDX.
Check for below values & change accordingly.
1]Lockout Threshold : It should be equal to Invalid attempts of Password Policy Maintenance.

2]Lockout Duration : It should be equal to property under prop_id "USER_LOCK_PERIOD" maintained in
DIGX_FW_CONFIG_ALL_B table.
In case of OUD or other LDAP it needs to be sync with the Password Policy configured in LDAP. For e.g.: Refer to
below values configured in OUD.
Once the values are available, make appropriate change in respective highlighted configuration.
Save and Activate Changes

Restart AdminServer
OBDX Application logging
To enable OBDX activation logging make below change to logging.xml present at

${domain.home}/config/fmwconfig/servers/${ManagedServer}.
Open logging.xml and make a new entry under <log_handlers> tag using below code template:
<log_handler name='obdx-handler' level='<LOGLEVEL>'

class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='<path for OBDX log>/<OBDX log filename>' />
<property name='maxFileSize' value='<The maximum size in bytes for each log file>' />
<property name='maxLogSize' value='<The maximum size in bytes for the entire log>' />
<property name='encoding' value='<encoding>' />
<property name='useThreadName' value='true' />
<property name='supplementalAttributes' value=’<supplementalAttributes>' />
</log_handler>
Below is a sample implementation for log_handlers file.
<log_handler name='obdx-handler' level='ERROR' class='oracle.core.ojdl.logging.ODLHandlerFactory'>

<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/obdx.log' />
<property name='maxFileSize' value='10485760' />
<property name='maxLogSize' value='104857600' />
<property name='encoding' value='UTF-8' />
<property name='useThreadName' value='true' />
<property name='supplementalAttributes'
value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,compos
ite_instance_id,component_instance_id,composite_name,component_name' />
</log_handler>
Add loggers under <loggers> tag using below template:
<logger name='com.ofss' level='ERROR' useParentHandlers='false'>

<handler name='obdx-handler' />
</logger>
<logger name='#BANKCODE#.com.ofss' level='ERROR' useParentHandlers='false'>
</logger>
Note: Replace the #BANKCODE# with bank code.
Below is a sample implementation for loggers file
<logger name='com.ofss' level='ERROR' useParentHandlers='false'>

</logger>
<logger name='000.com.ofss' level='ERROR' useParentHandlers='false'>
</logger>
Eclipselink logging
To modify eclipselink logging make changes in <INSTALLATION_HOME>\config\META-
INF\persistence.xml using below link :
https://wiki.eclipse.org/EclipseLink/Examples/JPA/Logging
Change logging level during runtime

To change OBDX application logging level at runtime (when OBDX application is up and running) do following steps.
To do this, ensure that the Admin Server is running. Login to the EM (Enterprise Manager) Console using the
following URL:
http://<hostname>:<admin_port>/em
Note: EM console would be available on same hostname and port which was used for Weblogic Admin
Console for OBDX domain (created via installer), just replace the “/console” with “/em”.
 Click on obdx-server
Note : Depending on installer.properties, Managed server will differ from above screenshot.
 In Weblogic Domain menu click on Logs -> Logs Configurations
 Select the logger and change the logging level and then click on apply.
Note : Logger name should be defined in logging.xml.
If during installer execution Universal Banking Solution (OBDX with UBS) is selected, then below steps
needs to be done manually.
Foreign Server
 Login into Weblogic Admin console (OBDX domain created using installer) and Browse to Summary
of JMS Modules > UBSSystemModule (as shown below)
 Click on UBSForeignServer
 Click on Lock & Edit
Set below configurations with:
JNDI Connection URL – UBS HOST Weblogic t3 URL for Managed server (where
NOTIFY_DEST_QUEUE and NOTIFY_DEST_QUEUE_FCDB are mapped)
JNDI Properties Credential – Password for username set in JNDI properties
Confirm JNDI Properties Credential – Confirm password for username set in JNDI properties
JNDI Properties – Value to be set as “java.naming.security.principal=<username>”, where

username is the login user of UBS Weblogic Admin Console (user which created the primary local
queues for UBS).
 Click on Save
 Click on Activate Changes
Deployment of notification MDB application
Before deployment of obdx.externalsystem.ubs.notification.mdb.ear application, kindly perform below

steps:
 Open the obdx.externalsystem.ubs.notification.mdb.ear (EAR file is available <OBDX INSTALLER
DIR>/installables/app/components/ubs/deploy/obdx.externalsystem.ubs.notification.mdb.ear) using
any archiving tools (i.e.: 7-zip)
 Double click on com.ofss.extsystem.ubs.notification.jar
 Open the wsconfig.properties to edit
 Change the URL for AlertProcessorService.url and FileProcessedNotifProcessorService.url (Note

the hostname and port should be of OBDX managed server created by installer)
 Save changes.
 Click OK.
 Navigate back to obdx.externalsystem.ubs.notification.mdb.ear
 Click OK
Deploy the updated obdx.externalsystem.ubs.notification.mdb.ear using below steps.
 Login into Weblogic Admin Console (OBDX domain created using installer) and navigate to
Deployments
 Click Lock & Edit
 Click on Install
 Click on Upload your file(s)
 Click on Choose File
 Navigate to customized obdx.externalsystem.ubs.notification.mdb.ear and click Open
 Click Next
 Click Next
 Select “Install this deployment as an application” and click Next
 Select Cluster as target and click Next
 Click Next
 Click Finish.
 Click Save.
 Click Activate Changes
Fileupload with UBS

Refer below document for File upload configuration with UBS
Oracle Banking Digital Experience File Upload Report Configuration
Origination with UBS

Refer below document (section 5 and 6) for enabling Origination with UBS
Oracle Banking Digital Experience UBS Origination Setup and Configuration
OBDX with OBP Base (Installation with Oracle Banking Platform)

Refer below document (section 5.2 OUD configurations in OBP) for User Authentication required for
integration with OBP
Oracle Banking Digital Experience OBP Base Setup and Configuration
OBDX US LZN with OBP US LZN (Installation with Oracle Banking Platform US LZN)
Once OBP Base setup and configuration is complete, refer below document to apply LZN Installer
required for integration with OBP 2.5.0.2 US LZN.
Oracle Banking Digital Experience OBP US LZN Setup and Configuration
OBDX with OFSLL (Installation with Oracle Services Lending and Leasing)
Refer below document for OFSLL Installer required for integration with OFSLL
Oracle Banking Digital Experience OFSLL Setup Configuration
OFSLL supports social media integration. Refer Oracle Banking Digital Experience Origination Social
Media Integration document.
OHS
OHS server needs to be configured for all FLAVOR’s as a mandatory activity.

To configure OHS server follow steps mentioned in below document before proceeding further.
Oracle Banking Digital Experience OHS User Interface Configuration
Home
Configuring the Connector Credential Store
9. Configuring the Connector Credential Store

This step is required to setup the encryption key required for encryption of certain sensitive data within
the OBDX application.
For more information, refer the Oracle Banking Digital Experience Connector Credential Store
Guide.docx
OBDX Product Verification
10. OBDX Product Verification

Start managed server and verify all deployed applications are in Active state (as shown below).
To login into application, new user needs to be created (if not already done) in OUD refer section
Creating the Attributes, Object Class, Users, Groups and Adding Optional Attributes on LDAP Server of
document “Oracle Banking Digital Experience Installer Pre-Requisite Setup Manual” mentioned in section
1.5 Related Information Sources.
To verify the installation, launch below URL
http://<OHS server ip or hostname>:<OHS port>
Check if the page loads successfully.
Day1 Configuration
Refer below document (Section 3. System Configuration) for Day1 configuration required for integration
with UBS
Oracle Banking Digital Experience System Configuration
Once day1 is completed, application is available for end-user transactions.
Note: Post Day1 restart of Managed server is mandatory
Third Party System (OBDX with THP)
Refer below document (Section 5. System Configuration – Host System as Third Party) for Day1
configuration required for integration with Third-party System
Oracle Banking Platform (OBDX with OBP)
Refer below document (Section 4 System Configuration – Host System as OBP Base and US LZN) for
Day1 configuration required for integration with OBP
Oracle Banking Platform US LZN (OBDX with OBP US LZN)
Refer below document (Section 4 System Configuration – Host System as OBP Base and US LZN) for
Day1 configuration required for integration
Oracle Financial Services Lending and Leasing ( OBDX with OFSLL)
Refer below document (section 5.1 System Configuration) for Day1 configuration required for integration
with OFSLL
Oracle Banking Digital Experience OFSLL Setup Configuration
Chat Bot Configuration:
Refer below document for Chat Bot configuration.

Oracle Banking Digital Experience Chatbot Configuration
Mobile Application Builder:
Refer below documents for Mobile Applications build and setup.

Oracle Banking Digital Experience Mobile Application Builder-Android
Oracle Banking Digital Experience Mobile Application Builder-iOS
Home
Configuration for OUD/OAM
11. Configuration for OUD/OAM

In-case installation needs to be done using OUD/ OAM provider, below steps needs to be performed
manually.
Weblogic configuration
 REST EAR deployment:

Undeploy obdx.app.rest.idm from deployments.
Deploy obdx.app.rest from Installer zip (<OBDX INSTALLER DIR>
\installables\app\components\obdx\deploy\).
 Security Realms
To configure your own Oracle LDAP to use instead of the default embedded LDAP, which comes with
Oracle Weblogic Server.
 To do this, ensure that the Admin Server is running. Login to the Weblogic Console for OBDX
domain (created by Installer) using the following URL:
http://<hostname>:<admin_port>/console
 Now, go to Security Realms > myrealm > Providers
 Now click on “Lock & Edit” in order to edit the details.

 Delete the following authenticators under providers->authenticators:
DBAuthenticator
SQLAuth
 Click on ‘DefaultAuthenticator” provider and change the Control Flag to SUFFICIENT
 Click on Save button to save the changes
 Navigate Back to Security Realms > myrealm > Providers
 Now, click on New and enter the below details and click Save.
Name : OUDAuthenticator
Type : IPlanetAuthenticator
 Click on OK Button.
Now Click on OUDAuthenticator and select Control Flag as “SUFFICIENT”
 Click on Save Button.
 Now under Provider Specific tab set the details of LDAP where the server should point. Refer to the
following table for more information:
Property Value
Host This is the LDAP Server (OUD) Hostname
Port This is the LDAP Server (OUD) Port. E.g. 1389
Principal This is the Administrator Account name. E.g.

cn=orcladmin
Credential This is the Administrator Account password.
Confirm Credential Confirm the Administrator Account password.
UserBase DN This is the OUD user search base

For e.g.: cn=Users, dc=in,dc=oracle,dc=com
GroupBase DN This is the OUD group search base

For e.g.: cn=Groups, dc=in,dc=oracle,dc=com
 Click on Save to update the changes.

 Navigate Back to Security Realms > myrealm > Providers
 Now, click on New and enter the below details and click Save.
Name : OAMIdentityAsserter
Type : OAMIdentityAsserter
 Click on Reorder Button.
 Reorder the providers so that LDAP Provider (OUDAuthenticator) gets highest priority followed by
OAMIdentityAsserter, OBDXJWT, DefaultAuthenticator, DefaultIdentityAsserter.
 Click on Activate Changes to apply the changes.
 Now go to the <DOMAIN_PATH>/<DOMAIN_NAME>/config/fmwconfig/

 Open jps-config.xml
Replace the line: <serviceInstanceRef ref="idstore.custom"/>
With <serviceInstanceRef ref="idstore.ldap"/>
 Now Shutdown the Admin server.

 Now, again start the Admin Server using the command,
<DOMAIN_PATH>/<DOMAIN_NAME>/bin/startWeblogic.sh
 Run the following script into OBDX Schema:
update DIGX_FW_CONFIG_ALL_B set

prop_value='com.ofss.digx.app.sms.adapter.impl.user.OUDUserAdapterFactory' where
PROP_ID='USER_MANAGEMENT_ADAPTER_FACTORY' and
CATEGORY_ID='adapterfactoryconfig'; commit;
 Restart Managed Server
Verification
Post Admin and Managed Servers restart, login into Admin Console and browse to Security Realms >
myrealm > Users and Groups.
Under Users tab additional LDAP users would be populated and additional LDAP groups can be seen
under Groups tab.
Home
Multi Entity
12. Multi Entity
To add entity to existing OBDX with supported host system follow below steps.
 Add entity through OBDX Web application, using User Manual Oracle Banking Digital Experience
System Configuration User Manual
 Run OBDX installer
Ensure that managed server should be down and admin server should be running.
Ensure ORACLE_HOME, JAVA_HOME variable are set and their binaries are available in PATH
variable before proceeding.
Login with OS user which was used to perform OBDX software installation (or has ownership on
Oracle Weblogic home directory)
Ensure OBDX Installation home and filestore path maintained in installer.properties exists and user
running the installer has read-write permissions.
 From your terminal navigate to <OBDX INSTALLER DIR>
 Enter the following command
python runInstaller.py
Select installation type as ‘New Entity Creation’
Multi Entity
Below screen will appear after selecting add entity
Enter below information:
 Entity code which has been added from screen

If an entity code belongs to UBS host following screen will appear:
Multi Entity
Enter below details:
 Hostname of the UBS database host server

 Port of the UBS database host server
 UBS Host database Service Name
 Oracle directory name in which you want the database datafile (dbf) to be created. Enter only the
name NOT the path.
 Username with 'sys' privileges
 SYS privilege user password where UBS schema would be created
Multi Entity
Enter below details:
 EXISTING UBS Host schema name

 Password for EXISTING UBS schema
 Complete UBS B1A1 (HostInterface) schema name you want installer to create as new schema
 Password for New UBS schema
 Country Code of entity branch
Multi Entity
Installation Status in case of UBS
After entering all required details, the status is displayed (as shown below) on the terminal to indicate the
progress of the installation.
Installation Status in case of other hosts
Multi Entity
After entering all required details (Entity code and OBDX schema password), the status is displayed (as
shown below) on the terminal to indicate the progress of the installation.
Home
Multi-entity installation In Silent Mode
13. Multi-entity installation In Silent Mode

This chapter describes how to run the OBDX installer for add entity in silent mode.
Ensure that managed server should be down and admin server should be running.
Ensure ORACLE_HOME, JAVA_HOME variable are set and their binaries are available in PATH
variable before proceeding.
Login with OS user which was used to perform OBDX software installation (or has ownership on
Oracle Weblogic home directory)
Steps for Silent-Mode Installation
 Set the environment variables
Below parameters should be set in environment variables
Parameter Description
Entity_Code Entity code which has been entered from
screen
SCHEMA_PASS Password for existing schema on OBDX
database
ENTITY_UBS_HOSTNAME Hostname of the UBS database host
server
ENTITY_UBS_PORT Port of the UBS database host server
ENTITY_UBS_SID UBS Host database SID or Service Name
ENTITY_DIRECTORY_NAME_UBS Oracle Directory name in which you want
the UBS B1A1 (HostInterface) schema
Add entity with datafile (dbf).
UBS (Installation Enter only the name and NOT the path
with Universal
ENTITY_SYS_USER username with 'sys' privileges
Banking Solution)
ENTITY_SYS_PASS
ENTITY_NEW_SCHEMA_NAME Complete UBS B1A1 (HostInterface)
schema name you want installer to create
as new schema.
ENTITY_NEW_SCHEMA_PASS Password for new B1A1 schema on UBS
database
ENTITY_UBS_SCHEMA EXISTING UBS Host schema name
ENTITY_UBS_SCHEMA_PASS Password of existing HOST UBS schema
(Existing)
ENTITY_DomainPassword Password for weblogic admin console
ENTITY_UBS_CCY Country Code for entity home branch
Entity_Code Entity code which has been entered from
Add entity with screen
other hosts
SCHEMA_PASS Password for existing schema on OBDX
database
 Run the runInstaller.py file with ‘--silent ’ argument along with ‘--addEntity’
Installation Status in case of UBS
Installation Status in case of other hosts
Home
OBDX Product Security
14. OBDX Product Security

Refer below document for OBDX product security configuration
Oracle Banking Digital Experience Security Guide
Home
Troubleshoot Overview
15. Troubleshoot Overview

This section describes how to troubleshoot OBDX setup.
Invalid database password

This topic contains troubleshooting information if you receive an error when attempting to connect to the
database server.
If you get the following error:
Try one of the following:

 Verify that the database is running.
 Check Network connectivity between Weblogic Server and Database server.
 Check the database configuration in installer.properties file
 Verify that the entered password is correct.
cx_oracle module
This topic contains troubleshooting information about problems with cx_Oracle python module.
Execute the below command:

export LD_LIBRARY_PATH=/usr/lib/oracle/12.2/client64/lib:$ LD_LIBRARY_PATH
Failed Database Scripts

This topic contains troubleshooting information in case of database script failures.
If you get the following error in DB_installation.log:
Check the detailed log of the failed SQL file at <OBDX INSTALLER
DIR>/ExecInstances/<DDMonthHHMM> /logs/db folder.
Failure of Policy Seeding

This topic contains troubleshooting information if policy seeding fails during installation.
Try one of the following:

 Check if error.log is created on following path <OBDX INSTALLER
DIR>/ExecInstances/<DDMonthHHMM>/logs/db/error.log. This log contains runtime SQL execution
errors.
 If the above mentioned file does not exist, then check the seedPolicies.log on <OBDX INSTALLER
DIR>/ExecInstances/<DDMonthHHMM>/logs/db/seedPolicies.log. This log file contains errors
generated during execution of the seed policies jar.
Fix the problem by following below steps:

 Login to OBDX installer server
 Browse to <OBDX INSTALLER DIR>\installables\policies
 Run below command manually
java -jar SeedPolicies.jar "Clip.csv,Admin.csv" "CLIP,ADMIN" "<Directory where logs needs to be
created>" "INS-oracle.jdbc.OracleDriver,<OBDX Schema name>,<OBDX Schema
password>,jdbc:oracle:thin:@<OBDX DB hostname or IP>:<OBDX DB listener port>/<OBDX Service

Name>"
for e.g.:
java -jar SeedPolicies.jar "Clip.csv,Admin.csv" "CLIP,ADMIN" "/tmp/" "INS-
oracle.jdbc.OracleDriver,OBDX_THP181,Welcome#1,jdbc:oracle:thin:@10.44.169.255:1521/OBDX"
 Post successfully execution, restart Managed server.
Home

Oracle Banking Digital Experience Installation Guide

Uploaded by

Copyright:

Available Formats

Oracle Banking Digital Experience Installation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Banking Digital Experience Installation Guide

Uploaded by

Copyright:

Available Formats

Oracle Banking Digital

Part No. E92727-01

Oracle Financial Services Software Limited

Copyright © 2018, Oracle and/or its affiliates. All rights reserved.

Installation Guide iii

1.2 Documentation Accessibility

1.3 Access to Oracle Support

1.5 Related Information Sources

 Oracle Banking Digital Experience Mobile Application Builder-Android

Installer Pre-requisite verification

Oracle Instant client

cx_Oracle & Urwid

Step 1: Execute python command

Step 2: Import Urwid and check version

If version is displayed, then Urwid is installed and available for use.

Step 3: Similarly import cx_Oracle and check version

If version is displayed, then cx_Oracle is installed and available for use.

 Enter the values right after the “=” sign

Only below parameters should be set in installer.properties file.

Component Parameter Description Example

Enter the hostname of the

Enter the port number of the

Enter the Oracle Service Name for

Enter the username with 'sys'

DIRECTORY_NAME Enter the directory name in which

Component Parameter Description Example

DatabaseHostNameU Enter the hostname for the UBS

DatabaseHostPortUB Enter the port number of the UBS

Enter the Complete OBDX-EXT

Enter the directory name in which

Enter the username with 'sys'

DatabaseHostSID_UB Enter the UBS Host database

Enter the EXISTING UBS Host

Enter the Country code for UBS

UBS_HB Enter the Branch code for

Component Parameter Description Example

Middleware home path. Example

Path where JAVA (JDK) is /home/obdxuser/jdk1

Path where OBDX is to be

Name of cluster; this cluster would

Host name or IP address of

AdminServer port. It is the port to

AdminServer SSL port. It is the

Node Manager Port. It is the port

Managed server name. This will be

Managed Server Port. Managed

DomainName Enter Weblogic Domain name. obdx_domain1

Domain user ID. The user id will be

Set the paths for the persistence

Set the paths for the persistence

ReportsFileStore (to Set the paths for the persistence

Set the paths for the persistence

STB schema name prefix. If schema

Set username for OBDX application

Enter the mobile number for OBDX

Select the appropriate type of Installation

Post selection of installation type.

Post selection of host system below installation mode would be available

Mode of Installation - New Installation

Universal Banking Solution (OBDX with UBS)