5. Data Replication
5.1 Introduction
Savings is an interface provider for processing cash transactions. Business logic is not built in branch and hence, some of the crucial maintenances have to be replicated from the host (Oracle FLEXCUBE) at regular intervals. The ‘Push’ based replication methodology is used for reproducing host data in branch. This ensures that only necessary and critical information is available in the branch. This is achieved by a job invoked at host which sends the data to the branch in the form of an XML file. The branch then updates its internal tables with this data. This ensures that all branches have the most up to date data at all times. Note that not all data in host is replicated. Certain tables like static masters, user information and customer/accounts information are replicated.
The method of replication depends upon the mode of Oracle FLEXCUBE deployment. There are three modes of deployment viz:
- Centralized FCUBS deployment - In ‘Centralized’ deployment, replication is a seamless process. During authorization process of any host function id whose data has to be replicated, that data is immediately moved to corresponding branch tables. There is no need for manual or automated process to initiate such replication.
- De-Centralized FCUBS deployment – In a ‘De-centralized’ deployment, data can be replicated on an ad-hoc basis or in bulk. You can query on the data to be replicated and initiate replication onto branch tables.
- Hybrid FCUBS deployment – In ‘Hybrid’ deployment, certain branches may have a centralized deployment while some others may have a decentralized deployment. In this mode, you can replicate data in bulk.
This chapter contains the following sections:
- Section 5.2, "Maintain Replication Parameters"
- Section 5.3, "Querying on replicated records"
- Section 5.4, "Steps to follow during Setup"
5.2 Maintain Replication Parameters
This section contains the following topics:
- Section 5.2.1, "Maintaining Replication Parameters"
- Section 5.2.2, "Data Replication Process"
- Section 5.2.3, "Replicating data from Host – Automatic Refresh"
- Section 5.2.4, "Replicating Data Using Script "
- Section 5.2.5, "Replicating data from Branch - Ad-hoc basis"
5.2.1 Maintaining Replication Parameters
You need to maintain the following tables for all branches where data needs to be replicated.
STTM_FLEXBRANCH_LOC
| BRANCH_CODE | LOC_CODE | BRANCH_URL | ||||
|---|---|---|---|---|---|---|
| <Branch Code> | <Branch Code> | URL of the deployed web branch | Eg: https://10.10.10.10:1001/FCUBSApp/ReplicationBranchServlet |
STTM_BRANCHLOC_MAP
| BRANCH_CODE | LOC_CODE | MAIN_BRANCH | GEN_SCR | ||||
|---|---|---|---|---|---|---|---|
| <Branch Code> | Refer below | Refer below | Refer below |
Entry in STTM_BRANCHLOC_MAP and STTM_FLEXBRANCH_LOC is required only for de-centralized branches.Y
You need to maintain the following values for de-centralized branch:
- MAIN_BRANCH - If multiple branches use the same schema, then for one branch set this to ‘Y’ for the rest, set this to ‘N’. Decentralised branch entity is can be a standalone branch or a sub branch. If set to ‘Y’, it indicates a standalone branch. If set to ‘N’, it indicates a sub branch. If multiple branches use the same schema, then, for one branch set the ‘MAIN_BRANCH’ as ‘Y’ and for rest under that branch, set to ‘N’.
- LOC_CODE - Location code of the branch. All sub branch location codes will be same as that of their parent standalone branch location code.
- GEN_SCR - Y (If you require the Installer to generate the script for insertion of basic maintenance data into the respective decentralised schema, then you need to set this to ‘Y’. This is set to ‘Y’ for all main and sub branches at the decentralised schema. If a branch is being added to an existing set up, then for the earlier branches ‘GEN_SCR’ has to be set to ‘N’.
- You have to maintain WBPURGE batch at PBOD stage to purge the processed records of STTB_BRANCH_REPL.
CSTB_PARAM
| BRANCH_INSTALLED | DEPLOYMENT_MODE | ||
|---|---|---|---|
| Refer below | Refer below |
You need to maintain the following values for centralized set-up:
- BRANCH_INSTALLED - Y
- DEPLOYMENT_MODE - C (Here, C indicates Centralized, H indicates Hybrid and D indicates Decentralized)
You need to maintain the following values for de-centralized and hybrid set-up:
- BRANCH_INSTALLED - Y
- DEPLOYMENT_MODE - D or H (Here, C indicates Centralized, H indicates Hybrid and D indicates Decentralized)
STTB_BRN_REFRESH_FUNC
Here function id wise replication is enabled ‘Y’ or disabled ‘N’.
For decentralized setup, replication has to be enabled for all functions in STTB_BRN_REFRESH_FUNC.
| Function | Replication Required | ||
|---|---|---|---|
| STDSTAFN | Y | ||
| CADCHBOO | Y | ||
| UPDPRDMN | Y | ||
| CLDFNPRD | Y | ||
| CSDDEMAN | Y | ||
| CADSPMNT | Y | ||
| STDWFDEF | Y | ||
| CYDCDEFN | Y | ||
| DEDRTPRM | Y | ||
| DEDTVSET | Y | ||
| IFDATMMN | Y | ||
| IVDCONFR | Y | ||
| SMDFNDSC | Y | ||
| SMDROLDF | Y | ||
| SMDUSHOL | Y | ||
| SMDUSRDF | Y | ||
| STDBRANC | Y | ||
| STDBRFUN | Y | ||
| STDCIF | Y | ||
| STDCUSAC | Y | ||
| STDDEFAU | Y | ||
| STDFNGRP | Y | ||
| STDIMAGE | Y | ||
| STDTBRAN | Y | ||
| DEDBNKCD | Y | ||
| CSDISSCD | Y | ||
| STDACLGP | Y | ||
| GLDCHACC | Y | ||
| STDENDMT | Y | ||
| STDLOCHL | Y |
5.2.2 Data Replication Process
Data replication takes place only if the parameter ‘BRANCH_INSTALLED’ is set to ‘Y’. Replication takes place in the following stages upon successful authorization of any maintenance in host.
The system constructs the list of data (based on the impacted function IDs) for each Savings table that needs to be updated with data from host. The following information is captured on authorization of a maintenance in host.
- The Function ID that caused the need for replication
- The branch from which the change was made
- Comma separated list of the Primary Key values for the functions ID
- The modification number
- The Savings table into which the record is to be stored
- A running sequence number
The system calls a replication process based on the deployment mode. If the deployment mode is centralized, the system will call the replication process to trigger data replication as and when there is an authorization in host for replicable data. The Savings tables will be automatically updated. If the deployment mode is decentralized, it will call the replication servlet.
5.2.3 Replicating data from Host – Automatic Refresh
In Oracle FLEXCUBE (host), you can submit the records as a job for replication in the branch database through the ‘Jobs Browser’ screen. You can invoke this screen by typing ‘SMSJOBBR'’ in the field at the top right corner of the Application Browser and clicking the adjoining arrow button. Branch replication job definition will be created as part of the Oracle FCUBS basic setup with the job name as ‘BRNRPLI’ and startup mode as ‘Manual’. The screen shows ‘n’ number of branch replication jobs where ‘n’ is the number of branches that require replication. The job name (BRNRPLI) will be prefixed with the unique LOC code. .
Specify the search parameters and click ‘Search’ button. The job, which is created with the branch code in its name, runs for the respective branch. Select a particular branch job and click ‘Pause’ button to pause the job. You can resume the job by selecting the job and clicking the ‘Resume’ button.
Note
If a new branch is created in for branch replication, then you need to restart the application to view the newly created branch job in this screen.
5.2.4 Replicating Data Using Script
Initial replication for decentralized web branch happens during setup in the installer. The Installer automatically generates the data and compiles them into decentralized branch. In order to manually replicate using script generation, you need to follow the steps given below..
- You need to compile the Branch Installation Package in Host schema.
The package specification and body names are:
- MAIN\Branch\SQL\DIPKS_BRANCH_INSTALLATION.spc
- MAIN\Branch\SQL\DIPKS_BRANCH_INSTALLATION.sql from shipment media
- After compiling dipks_branch_installation package, you have to execute the procedure pr_start on the same package.
- On successful execution of the procedure will create the branch installation script in work area folder as defined in cstb param.
- Finally you need to run the Installation scripts in required branch schema.
5.2.5 Replicating data from Branch - Ad-hoc basis
You can replicate records from branch manually on an ad-hoc basis using the ‘Manual Refresh’ screen. This screen displays all maintenances pending replication. You can invoke this screen by typing ‘STDBRREF’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Specify the following details:
Branch Code
Specify the branch code to which data should be replicated. The adjoining option list displays all valid branch codes maintained in the system. You can select the appropriate one. You can select the value ‘ALL’ to indicate that data needs to be replicated in all branches.
Branch Name
Based on the branch code specified, the system displays the name of the branch.
Function ID
Specify the function ID for which a record has been maintained or modified, that should be replicated. The adjoining option list displays all valid function IDs maintained in the system. You can select the appropriate one. You can select the value ‘ALL’ to indicate that data from all function IDs needs to be replicated.
Description
Based on the function ID specified, the system displays a brief description of the function ID.
You can fetch replicable records for the given branch and function ID combination by striking <F8> or by clicking ‘Query’ button.
Function Block
Based on the branch and function ID combination, the system displays the following details for replicable function IDs:
- Branch Code
- Branch Name
- Function ID
- Function Description
Check the box adjoining the desired branch and click ‘Fetch Records’ button. Based on the function ID specified, the system identifies matching records for replication and displays them in the ‘Record Block’ frame. Note that you cannot click ‘Fetch Records’ button if you have selected multiple records.
Select the required record and click ‘Replicate Functions’ button to replicate data of all listed functions.
Record Block
You can view the following details.
Key Description
The Primary Key data to be replicated for the function Id and branch code is listed here.
Host Key
The system displays the primary keys separated by a pipe ‘I’.
Check the box adjoining the desired record and click ‘Fetch Versions’ button. Based on the record, the system identifies all details of data that needs to be replicated and displays them in the ‘Version Block’ frame. Note that you cannot click ‘Fetch Records’ button if you have selected multiple records.
Select the required record and click ‘Replicate Records’ button to replicate data of all listed records.
Version Block
You can view the following details.
Mod No
The system displays all available versions of the record selected as per the modification number of every record’s audit trail.
You can view the changes done in a mod number by selecting the particular mod number and clicking on ‘View’ button, thereby launching the corresponding Function Id screen with the particular modified data displayed in a different colour.
Time In
The system displays the time at which the version was available for replication.
Time Out
The system displays the time at which the version was replicated.
Replication Status
The system indicates the status of replication. It could be any one of the following:
- U - Unprocessed
- S - Replication Success
- F - Replication Success
- W - WIP
- C - Completed
Select the required record and click ‘Replicate Versions’ button to replicate data of all listed versions. If multiple rows are selected then only the latest mod number will be replicated. You can also select any of the modifications and initiate replication. On successful replication, the status for any un-replicated older modifications for that key combination will be marked as ‘C’.
All records in this frame need to be replicated for a successful replication. Even if one record fails, the system will treat it as a failure for the whole set of records.
You can clear the current query criteria by clicking ‘Reset’ button.
Replicate Common Data Button
Click ‘Replicate Common Data’ button to replicate the common data such as workflow, role definition, static data. This button is applicable only to centralized set branches. The branch tables are as follows.
| Host Table | Branch Table | ||
|---|---|---|---|
| STTM_BRANCH_WF_DEF_MASTER | FBTB_WF_DEF_MASTER | ||
| STTM_BRANCH_WF_DEF_DETAIL | FBTB_WF_DEF_DETAIL | ||
| STTB_BRANCH_WF_MASTER | FBTB_WF_MASTER | ||
| STTB_BRANCH_WF_DETAIL | FBTB_WF_DETAIL | ||
| CSTM_BRANCH_FUNC_DEFN | FBTB_FUNC_DEFN | ||
| CSTM_BRN_STAT_FUNC_DEFN | FBTB_STAT_FUNC_DEFN | ||
| CSTB_LOV_INFO | FBTB_LOV_INFO | ||
| SMTB_FUNC_GROUP | FBTB_FUNC_GROUP | ||
| SMTB_FUNCTION_DESCRIPTION | FBTB_FUNCTION_DESCRIPTION | ||
| SMTB_MENU | FBTB_MENU | ||
| CSTM_BRANCH_LOC_PARAMS | FBTB_PARAMS |
5.3 Querying on replicated records
You can view all successfully replicated records using the ‘Successful Replication Query’ screen. You can invoke this screen by typing ‘STSREPQY’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
Here you can query based on the following details.
Function Id
Specify the function ID for which you want to view the successfully replicated records. The adjoining option list displays all valid function IDs maintained in the system. You can select the appropriate one. You can select the value ‘ALL’ to indicate that data from all function IDs needs to be displayed.
Branch
Specify the branch code for which you want to view the successfully replicated records. The adjoining option list displays all valid branch codes maintained in the system. You can select the appropriate one. You can select the value ‘ALL’ to indicate that data from all branches needs to be displayed.
You can specify any one or both of the aforementioned criteria. Click ‘Search’ button.
The system identifies all records satisfying the specified criteria and displays the following details for each one of them:
- Function Id
- Branch
- Host Primary Key
- Mod No
- Status
- Time In
- Time Out
5.4 Steps to follow during Setup
Centralized Branch Setup
For centralized branch setup, you need to follow the steps given below:
- During setup, you need to select the Branch plug-in in the Installer. Select the mode of deployment as ‘Centralized’.
- For further details on this point, refer to the installation manuals ‘Setting up Database’ and ‘Setting up Property File’.
- Replicate the common static data using the option ‘Host Data Replication’ in the Installer.
- Once the set up is complete, for common static data replication, you get one more option with ‘STDBRREF’ screen, by clicking the button ‘Replicate Common Data’. When you subsequently click this button, the Installer replicates only the incremental common static data. Specific steps are not required when new centralized branches are created using ‘STDBRANC’.
- During setup, if you have not selected Branch plug-in, then you need to replicate the data using scripts.
- For further details on replicating data using scripts, refer to the section ‘Replicating data Using Script’ in this chapter.
Decentralized Branch Setup
For decentralized branch setup, you need to follow the steps given below:
- During setup, you need to select the Branch plug-in in the Installer. Select the mode of deployment as ‘De-centralized’.
- For further details on this point, refer to the installation manuals ‘Setting up Database’ and ‘Setting up Property File’.
- Replicate the data to branch schema using the option ‘Host Data Replication’ in the Installer.
- During setup, if you have not selected Branch plug-in, then you need to replicate the data using scripts.
- For further details on replicating data using scripts, refer to the section ‘Replicating data Using Script’ in this chapter.