10 BDI Application Installation Tasks

This chapter includes:

Hybrid Cloud

As part of hybrid cloud integration between retail apps and EBS, the retail applications are on cloud setup and EBS is on-premise. The Oracle Retail Financial Integration (RFI) layer serves as an intermediate thin layer of application between the financial application (EBS) and Oracle Retail. This integration remains synchronized with the new releases of the edge applications.

The integration mainly depends on the participating application whether it's an on-prem or cloud solution that decides which deployment topology to be followed.

There are two different types' of integration deployment topologies.

On-Premise Deployment Topology
Hybrid Cloud Deployment Topology

This section mainly talks about Hybrid cloud architecture and its implementation in detail.

On-Premises Deployment Topology

On-premises solutions (on-prem) are deployed in the traditional manner. Servers are acquired, operating systems are installed, other hardware may be involved, but all of that lives within the walls of datacenter.

Both Retail Applications and Financial Applications (EBS/PeopleSoft) should be on premise solutions.
Data flow is bidirectional.
Both Service-based integration and ETL-based integration works fine

Hybrid Cloud Deployment Topology

Hybrid cloud deployment provides computing environment which uses a mix of on- premises and cloud services with orchestration between the two platforms. By allowing workloads to move between two platforms as computing needs and costs change, hybrid cloud gives businesses greater flexibility and more data deployment options.

Retail Applications (i.e. RMS/ReIM) are on cloud and Financial Applications (EBS/PeopleSoft) are on premise.
Only Service-based integration works fine and there is a little modification in existing ETL-based integration to work in hybrid cloud.

Figure 10-1 RFI EBS Hybrid Cloud Architecture

Applications to be installed	Hybrid Topology	On-Premise Topology
RMS-EDGE, REIM-EDGE	Required	N/A
BDI-RMS, BDI-REIM	Required	N/A
BDI-RFI	Required	N/A
BDI-PROCESSFLOW	Required	N/A
BDI-SCHEDULER	Optional	N/A
ODI	Required	Required
RFI	Required	Required
EBS	Required	Required
RIB, RIB-RMS	Required	Required

Rms-edge, reim-edge, bdi-rms and bdi-reim are sender side apps to be installed in the retail cloud. Bdi-rfi is the receiver side app to be installed on premise environment like RFI and EBS.

Prerequisites

Assuming that edge applications installation instructions are provided by RMS and ReIM application teams.

Rms-Edge-App: Please refer to RMS 16.0.023 install guide and create a RMS environment that includes BdiEdgeAppJobAdminPakForRms. Before you begin installing RMS Batch Job Admin, make sure you have the database schema created for RMS Batch Job Admin.

The app can be deployed in any domain but it is recommended to deploy it in the existing RMS domain with separate managed server.

Reim-Edge-App: Please refer to ReIM 16.0.023 install guide and create a ReIM environment that includes BdiEdgeAppJobAdminPakForReim. Before you begin installing ReIM Batch Job Admin, make sure you have the database schema created for ReIM Batch Job Admin.

The application can be deployed in any domain but it is recommended to deploy it in the existing ReIM domain with separate managed server.

Note:

The edge applications edge- reim, edge-rms schema need write permission to integration schema in order to write the data to the corresponding outbound tables.

For complete installation instructions follow the BDI Installation Guide.

Deploying BDI Batch Job Administration Applications

Before starting the installation procedure, identify the retail applications that are in-scope for this installation. BDI requires at least 2 applications in-scope, a sender app and a receiver app. Each bdi-app must be deployed on its own WebLogic managed server. Depending on the site specific deployment topology, create separate WebLogic domains OR managed servers to host the BDI apps in-scope.

Note:

Repeat the procedures in this chapter for installing other applications that are in-scope.

Below are the instructions to deploy bdi integration applications (bdi-rms, bdi-reim, bdi-process-flow and bdi-scheduler) in the cloud and bdi-rfi on premise where EBS installed.

Deploying BDI RMS Batch Job Admin

This section describes the installation process for a sender app with the BDI-RMS app as an example.

Preparing the Database for BDI Batch Job Admin for RMS Installation

Before you begin installing BDI RMS Batch Job Admin, make sure you have the database schema created for BDI RMS Batch Job Admin.

Please follow the below naming convention during schema creation for BDI RMS.

Example, BDI_RMS_INT_SCHEMA

Preparing the WebLogic Domain for BDI Batch Job Admin for RMS

Use the instructions provided in the document BDI Installation Guide to install WebLogic 12.2.1.2 and create a domain.
Start the Admin and managed servers.

Deploying BDI RMS Batch Job Admin on the WebLogic

To deploy the BDI RMS Batch Job Admin war, perform the following steps.

Download BdiIntJobAdminPak16.0.023ForRms16.0.023_eng_ga.zip to $BDI_HOME.
Unzip the downloaded archive. The Bdi Job home directory will be created under the current directory.
```
unzip BdiIntJobAdminPak16.0.023ForRms16.0.023_eng_ga.zip
```
Edit the rms job configuration file to point to deployment environment (conf/bdi-job-admin-deployment-env-info.json) as follows:
```
cd bdi-int-rms-job-home/conf
vi bdi-job-admin-deployment-env-info.json
```

Provide the following values in the JSON file.

Configuration Property	Description
BdiRmsJobAdminDataSource -> jdbcUrl	The JDBC URL for the Oracle database where the RMS integration schema resides. Suggested schema user BDI_RMS_INT_SCHEMA
BdiRmsReceiverServiceDataSource -> jdbcUrl	The JDBC URL for the Oracle database where the RMS integration schema resides. BdiRmsJobAdminDataSource and BdiRmsReceiverServiceDataSource can use the same jdbcUrl.
BatchInfraDataSource -> jdbcUrl	The JDBC URL for the schema created using RCU. The schema user is <prefix>_wls (e.g. INT_WLS). The value of prefix that you provided in schema creation using RCU.
JobAdminAppServer -> weblogicDomainName	The domain name where BDI RMS Admin app is deployed.
JobAdminAppServer->weblogicD omainHome	The domain path where BDIRMS Adminapp is deployed
JobAdminAppServer -> weblogicDomainAdminServerUrl	Admin Server URL of the BDI RMS Admin App - http://<Admin host>:<Admin port>
JobAdminAppServer->weblogicD omainAdminServerProtocol	AdminServer protocol which is by default t3, For SSL deployment update to t3s.
JobAdminAppServer -> weblogicDomainAdminServerHost	Host Name of the BDI RMS Admin Server
JobAdminAppServer -> weblogicDomainAdminServerPort	BDI RMS Admin Server Port
JobAdminAppServer -> weblogicDomainTargetManagedS erverName	Managed Server Name where BDI RMS Admin App is installed (e.g. bdi-rms-server)
JobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI RMS http://<host>:<managed server port>/bdi-rms-batch-job-admin
RfiJobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI RFI http://<host>:<rfi managed server port>/bdi-rfi-batch-job-admin

Note:

The alias names in the configuration files should not be changed.

Run the deployer script to create the data sources and deploy BDI RMS Batch Job Admin.

cd bdi-int-rms-job-home/bin
bdi-job-admin-deployer.sh -setup-credentials -deploy-job-admin-app

Enter the values prompted by the script for following credentials aliases. JobAdmin user has more privileges (e.g. change configuration and run jobs from JobAdmin UI) than JobOperator user. JobOperator can run batch jobs where as JobMonitor has just read privileges.

Alias	Description
bdiAppServerAdminServerUserAlias	WebLogic admin server credentials
bdiJobAdminUiUserAlias	Credentials for Admin Role user for Job Admin app
bdiJobOperatorUiUserAlias	Credentials for Operator Role user for Job Admin app
bdiJobMonitorUiUserAlias	Credentials for Monitor Role user for Job Admin app
bdiJobAdminDataSourceUserAlias	Credentials for the Data Source of the Job Admin Schema
bdiRmsReceiverServiceDataSourceUserAlias	Credentials for the Data Source of the Job Receiver Schema
batchInfraDataSourceUserAlias	Credentials for the Data Source of the Batch Infra Schema
rxmJobAdminBaseUrlUserAlias	BDI RXM job admin app credentials
simJobAdminBaseUrlUserAlias	BDI SIM job admin app credentials
rfiJobAdminBaseUrlUserAlias	BDI RFI job admin app credentials

Deployer script deploys BDI RMS Batch Job Admin to the managed server.
Restrict access to the bdi-int-rms-job-home folder:
```
cd bdi-int-rms-job-home 
chmod -R 700 .
```

Creating Outbound Interface tables for BDI RMS

Go to the $BDI_HOME/bdi-int-rms-job-home/setup-data/ddl folder.
Run the sql script bdi_rms_ddl.sql provided in this folder in the BDI RMS database schema.
DDL generates the necessary interface tables and PL/SQL packages.

Deploying BDI REIM Batch Job Admin

This section describes the installation process for a sender app with the BDI-REIM app as an example.

Preparing the Database for BDI Batch Job Admin for REIM Installation

Before you begin installing BDI REIM Batch Job Admin, make sure you have the database schema created for BDI REIM Batch Job Admin.

Please follow the below naming convention during schema creation for BDI REIM.

Example, BDI_REIM_INT_SCHEMA

Preparing the WebLogic Domain for BDI Batch Job Admin for REIM

Use the instructions provided in the document BDI Installation Guide to install WebLogic 12.2.1.2 and create a domain.
Start the Admin and managed servers.

Deploying BDI REIM Batch Job Admin on the WebLogic

To deploy the BDI REIM Batch Job Admin war, perform the following steps.

Download BdiIntJobAdminPak16.0.0231ForReim16.0.023_eng_ga.zip to $BDI_HOME.
Unzip the downloaded archive. The Bdi Job home directory will be created under the current directory.
```
unzip BdiIntJobAdminPak16.0.023ForReim16.0.023_eng_ga.zip
```
Edit the reim job configuration file to point to deployment environment (conf/bdi-job-admin-deployment-env-info.json) as follows:
```
cd bdi-int-reim-job-home/conf
vi bdi-job-admin-deployment-env-info.json
```

Provide the following values in the JSON file.

Configuration Property	Description
BdiReimJobAdminDataSource -> jdbcUrl	The JDBC URL for the Oracle database where the REIM integration schema resides. Suggested schema user BDI_REIM_INT_SCHEMA
BdReimReceiverServiceDataSource -> jdbcUrl	The JDBC URL for the Oracle database where the REIM integration schema resides. BdiReimJobAdminDataSource and BdiReimReceiverServiceDataSource can use the same jdbcUrl.
BatchInfraDataSource -> jdbcUrl	The JDBC URL for the schema created using RCU. The schema user is <prefix>_wls (e.g. INT_WLS). The value of prefix that you provided in schema creation using RCU.
JobAdminAppServer -> weblogicDomainName	The domain name where BDI REIM Admin app is deployed.
JobAdminAppServer->weblogicD omainHome	The domain path where BDIREIM Adminapp is deployed
JobAdminAppServer -> weblogicDomainAdminServerUrl	Admin Server URL of the BDI REIM Admin App - http://<Admin host>:<Admin port>
JobAdminAppServer->weblogicD omainAdminServerProtocol	AdminServer protocol which is by default t3, For SSL deployment update to t3s.
JobAdminAppServer -> weblogicDomainAdminServerHost	Host Name of the BDI REIM Admin Server
JobAdminAppServer -> weblogicDomainAdminServerPort	BDI REIM Admin Server Port
JobAdminAppServer -> weblogicDomainTargetManagedS erverName	Managed Server Name where BDI REIM Admin App is installed (e.g. bdi-rms-server)
JobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI REIM http://<host>:<managed server port>/bdi-rms-batch-job-admin
RfiJobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI RFI http://<host>:<rfi managed server port>/bdi-rfi-batch-job-admin

Note:

The alias names in the configuration files should not be changed.

Run the deployer script to create the data sources and deploy BDI REIM Batch Job Admin.

cd bdi-int-reim-job-home/bin
bdi-job-admin-deployer.sh -setup-credentials -deploy-job-admin-app

Alias	Description
bdiAppServerAdminServerUserAlias	WebLogic admin server credentials
bdiJobAdminUiUserAlias	Credentials for Admin Role user for Job Admin app
bdiJobOperatorUiUserAlias	Credentials for Operator Role user for Job Admin app
bdiJobMonitorUiUserAlias	Credentials for Monitor Role user for Job Admin app
bdiJobAdminDataSourceUserAlias	Credentials for the Data Source of the Job Admin Schema
bdiRmsReceiverServiceDataSourceUserAli as	Credentials for the Data Source of the Job Receiver Schema
batchInfraDataSourceUserAlias	Credentials for the Data Source of the Batch Infra Schema
rfiJobAdminBaseUrlUserAlias	BDI RFI job admin app credentials

The deployer script deploys BDI REIM Batch Job Admin to the managed server.
Restrict access to the bdi-int-reim-job-home folder:
```
cd bdi-int-reim-job-home
chmod -R 700 .
```

Creating Outbound Interface tables for BDI ReIM

Go to the $BDI_HOME/bdi-int-reim-job-home/setup-data/ddl folder.
Run the sql script bdi_reim_ddl.sql provided in this folder in the BDI REIM database schema.
DDL generates interface tables and PL/SQL packages.

Deploying BDI RFI Batch Job Admin

Preparing the Database for BDI RFI Batch Job Admin Installation

Before you begin installing BDI RFI Batch Job Admin, make sure you have the database schema created for BDI RFI Batch Job Admin.

Please follow the below naming convention during schema creation for BDI RFI.

Example, BDI_RFI_INT_SCHEMA

Preparing the WebLogic Domain for BDI Batch Job Admin for RFI

Assuming that WebLogic 12.2.1.2 and JRF domain are installed as part of ORFI installation.

Deploying BDI RFI Batch Job Admin on the WebLogic

To deploy the BDI RFI Batch Job Admin war, take the following steps.

Download BdiIntJobAdminPak16.0.023ForRfi16.0.023_eng_ga.zip to $BDI_HOME.
Unzip the downloaded archive. The BDI Job home directory will be created under the current directory.
```
Unzip BdiIntJobAdminPak16.0.023ForRfi16.0.023_eng_ga.zip.
```

Edit bdi-job-admin-deployment-env-info.json as follows:

cd bdi-int-rfi-job-home/conf
vi bdi-job-admin-deployment-env-info.json

Provide the following values in the JSON file.

Configuration Property	Description
BdiRfiJobAdminDataSource ->jdbcUrl	The JDBC URL for the Oracle database where the RFI Retail Proxy schema resides. Suggested schema user BDI_RFI_INT_SCHEMA
BdiRfiReceiverServiceDataSource -> jdbcUrl	The JDBC URL for the Oracle database where the RFI Retail Proxy schema resides.
BatchInfraDataSource -> jdbcUrl	The JDBC URL for the schema created using RCU. The schema user is <prefix>_ WLS (e.g. INT_WLS). The value of prefix that you provided in schema creation using RCU.
JobAdminAppServer -> weblogicDomainName	The domain name where BDI RFI Admin app is deployed
JobAdminAppServer -> weblogicDomainHome	The domain home directory of WebLogic where BDI RFI Admin app is deployed
JobAdminAppServer -> weblogicDomainAdminServerUrl	Admin Server URL of the BDI RFI Admin App - http://<Admin host>:<Admin port>
JobAdminAppServer->weblogicDomainA dminServerProtocol	AdminServer protocol which is by default t3, For SSL deployment update to t3s.
JobAdminAppServer -> weblogicDomainAdminServerHost	Host Name of the BDI RFI Admin Server
JobAdminAppServer -> weblogicDomainAdminServerPort	BDI RFI Admin Server Port
JobAdminAppServer -> weblogicDomainTargetManagedServerNa me	Managed Server Name where BDI RFI Admin App is installed (e.g.bdi-rfi-server)
JobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI RFI http://<host>:<bdi rfi managed server port>/bdi-rfi-batch-job-admin
RmsJobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI RMS http://<host>:<bdi rms managed server port>/bdi-rms-batch-job-admin
ReimJobAdminAppServer -> jobAdminUiUrl	Job Admin URL of BDI REIM http://<host>:<bdi reim managed server port>/bdi-reim-batch-job-admin

Run the deployer script to create the data sources and deploy BDI RFI Batch Job Admin.

cd bdi-int-rfi-job-home/bin
bdi-job-admin-deployer.sh -setup-credentials -deploy-job-admin-app

Enter the values prompted by the script for the following credential aliases. JobAdmin user has more privileges (e.g. change configuration and run jobs from JobAdmin UI) than JobOperator user. JobOperator can run batch jobs where as JobMonitor has just read privileges.

Alias	Description
bdiAppServerAdminServerUserAlias	WebLogic admin server credentials
bdiJobAdminUiUserAlias	Credentials for Admin Role user for Job Admin app
bdiJobOperatorUiUserAlias	Credentials for Operator Role user for Job Admin app
bdiJobMonitorUiUserAlias	Credentials for Monitor Role user for Job Admin app
bdiJobAdminDataSourceUserAlias	Credentials for the Data Source of the Job Admin Schema
bdiRfiReceiverServiceDataSourceUserAlias	Credentials for the Data Source of the Job Receiver Schema
batchInfraDataSourceUserAlias	Credentials for the Data Source of the Batch Infra Schema
rmsJobAdminBaseUrlUserAlias	BDI RMS job admin app credentials
reimJobAdminBaseUrlUserAlias	BDI REIM job admin app credentials

Note:

The alias names in the configuration files should not be changed.

Deployer script deploys BDI RFI Batch Job Admin to the server.
Restrict access to the bdi-int-rfi-job-home folder:
```
cd bdi-int-rfi-job-home 
chmod -R 700 .
```

Creating Inbound Interface tables for BDI RFI

Go to $BDI_HOME/bdi-int-rfi-job-home/setup-data/ddl folder.
Run the sql script bdi_rfi_ddl.sql provided in this folder in the BDI RFI database schema.
DDL generates the necessary retail and inbound interface tables along with the database packages for RFI.

Deploying BDI Process Flow

Preparing the Database for Process Flow Installation

Before you begin installing Process Flow App, make sure you have the database schema created for Process Flow.

Please follow the below naming convention during schema creation for process flow.

Example, BDI_PROCESS_INT_SCHEMA

Install the Process Flow Application

Perform the following procedure to install the Process Flow application:

Download the process flow archive BdiProcessFlow16.0.023ForAll16.x.xApps_eng_ ga.zip
Unzip the downloaded archive. The Process Home directory will be created under the current directory.
```
unzip BdiProcessFlow16.0.023ForAll16.x.xApps_eng_ga.zip
```

Modify process flow configuration file (conf/bdi-process-flow-admin-deployment-env-info.json) to match the deployment environment. While you can change many values to match your requirements, here is a table of a minimum set of configuration values that you need to modify for process flow application.

Note:

The alias names in the configuration files should not be changed.

Configuration Field	Description
ProcessFlowAdminDataSource ->jdbcUrl	JDBC URL for the process flow schema. Change this value to match the environment. Suggested schema user BDI_PROCESS_INT_SCHEMA
ProcessFlowAdminAppServer->weblogicDomainName	Name of the WebLogic domain where the process flow application is deployed
ProcessFlowAdminAppServer->weblogicDomainHome	WebLogic Domain home directory
ProcessFlowAdminAppServer- > weblogicDomainProtocol	WebLogic admin server protocol is by default t3, if SSL configured then update to t3s.
ProcessFlowAdminAppServer ->weblogicDomainAdminServerUrl	WebLogic Admin server URL
ProcessFlowAdminAppServer ->weblogicDomainAdminServerHost	Host name of WebLogic Admin Server
ProcessFlowAdminAppServer ->weblogicDomainAdminServerPort	WebLogic admin server port
ProcessFlowAdminAppServer ->weblogicDomainTargetManagedServerName	Managed Server name where Process Flow is hosted
ProcessFlowAdminAppServer->processFlowAdminUiUrl	Process Flow admin app URL. Update only the host and port
RmsJobAdminAppServer-->jobAdminUiUrl	BDI RMS job admin URL
ReimJobAdminAppServer-->jobAdminUiUrl	BDI REIM job admin URL
RfiJobAdminAppServer-->jobAdminUiUrl	BDI RFI job admin URL
RmsAppJobAdminAppServer -> jobAdminUiUrl	RMS APP job admin URL
ReimAppJobAdminAppServer -> jobAdminUiUrl	REIM APP job admin URL
RfiAppJobAdminAppServer -> jobAdminUiUrl	RFI APP job admin URL

Determine which flows are in scope for your deployment. Copy the flows from bdi-process-home/setup-data/dsl/available_process_flow_options to bdi-process-home/setup-data/dsl/flows-in-scope.

For example, for integration between RMS, REIM and RFI, the rms_rfi-no_split_ flows, reim_rfi-no_split_flows files would be copied:
```
cp bdi-process-home/setup-data/dsl/available_process_flow_options/rms_rfi-no-split-flows/* bdi-process-home/setup-data/dsl/flows-in-scope/.
cp bdi-process-home/setup-data/dsl/available_process_flow_options/reim_rfi-no-split-flows/* bdi-process-home/setup-data/dsl/flows-in-scope/.
```

Run the deployer. Make sure that the WebLogic server is running before issuing the following command.

cd bin
bdi-process-flow-admin-deployer.sh -setup-credentials
-deploy-process-flow-admin-app

The process flow deployer will prompt for username and password for the following credential aliases:

Alias	Description
bdiAppServerAdminServerUserAlias	WebLogic admin server credentials
processFlowAdminBaseUrlUserAlias	Credentials for Admin Role user for Process Flow Admin app
processFlowOperatorBaseUrlUserAlias	Credentials for Operator Role user for Process Flow Admin app
processFlowMonitorBaseUrlUserAlias	Credentials for Monitor Role user for Process Flow Admin app
bdiProcessFlowAdminDataSourceUserAlias	Credentials for the Data Source of the Process Flow Schema
rmsJobAdminBaseUrlUserAlias	BDI RMS job admin app credentials
reimJobAdminBaseUrlUserAlias	BDI REIM job admin app credentials
rfiJobAdminBaseUrlUserAlias	BDI RFI job admin app credentials
rmsappJobAdminBaseUrlUserAlias	RMS APP job admin credentials
reimappJobAdminBaseUrlUserAlias	REIM APP job admin credentials
rfiappJobAdminBaseUrlUserAlias	RFI APP job admin credentials

Make sure the deployment step shows deployment success message at the end.
Restrict access to the bdi-process-home folder:
```
cd bdi-process-home 
chmod -R 700 .
```

See the Oracle Retail Bulk Data Integration Implementation Guide for the operation details of the Process Flow application.

Enabling Email Notification Alerts

Process Flow can send email alerts upon success or failure of process executions as specified in the process definitions.

Follow the instructions in the BDI Installation Guide to configure email notification alerts.

Deploying BDI Batch Scheduler

BDI Batch Scheduler Installation

Use the instructions provided in the document BDI Installation Guide to install bdi batch scheduler.

Synonyms and Grant Privileges

Synonyms in reim-edge app

Check if the below synonyms are present. If the synonyms are not present, create them.

For example, if rms app schema given for JobXmlDataSource of reim-edge app is rms01app rms owner schema is rms01 reim bdi int app JobAdminDataSource schema is BDI_REIM_INT_SCHEMA

create or replace synonym rms01.INVCMTCHAP_TX_OUT_DATACTL for BDI_REIM_INT_SCHEMA.INVCMTCHAP_TX_OUT_DATACTL;

create or replace synonym rms01.INVCMTCHFIN_TX_OUT_DATACTL for BDI_REIM_INT_SCHEMA.INVCMTCHFIN_TX_OUT_DATACTL;

create or replace synonym rms01.IM_AP_HEAD_OUT for BDI_REIM_INT_SCHEMA.IM_AP_HEAD_OUT;

create or replace synonym rms01.IM_AP_DETAIL_OUT for BDI_REIM_INT_SCHEMA.IM_AP_DETAIL_OUT;

create or replace synonym rms01.IM_FINANCIALS_OUT for BDI_REIM_INT_SCHEMA.IM_FINANCIALS_OUT;

In addition, create synonyms in the rms01app schema for the same synonyms present in rms01.

create synonym INVCMTCHAP_TX_OUT_DATACTL for rms01.INVCMTCHAP_TX_OUT_DATACTL;

create synonym INVCMTCHFIN_TX_OUT_DATACTL for rms01.INVCMTCHFIN_TX_OUT_DATACTL;

create synonym IM_AP_HEAD_OUT for rms01.IM_AP_HEAD_OUT;

create synonym IM_AP_DETAIL_OUT for rms01.IM_AP_DETAIL_OUT;

create synonym IM_FINANCIALS_OUT for rms01.IM_FINANCIALS_OUT;

Synonyms in rms-edge app

Check if the below synonyms are present. If the synonyms are not present, create them.

For example, if rms app schema given for JobXmlDataSource of reim-edge app is rms01app rms owner schema is rms01 rms bdi int app JobAdminDataSource schema is BDI_RMS_INT_SCHEMA

create or replace synonym rms01.FINGENLDGR_TX_OUT_DATACTL for BDI_RMS_INT_SCHEMA.FINGENLDGR_TX_OUT_DATACTL;

create or replace synonym rms01.FIF_GL_DATA_OUT for BDI_RMS_INT_SCHEMA.FIF_GL_DATA_OUT;

In addition, create synonyms in the rms01app schema for the same synonyms present in rms01.

create synonym FINGENLDGR_TX_OUT_DATACTL for rms01.FINGENLDGR_TX_OUT_DATACTL; create synonym FIF_GL_DATA_OUT for rms01.FIF_GL_DATA_OUT;

Grant Privileges for Bdi--Reim--Int App

Grant SELECT, INSERT privileges to *_OUT tables and EXECUTE privilege to PACKAGES from BDI_REIM_INT_SCHEMA (bdi reim JobAdminDataSource schema) to rms01 (rms owner schema).

Execute the grant_privildges_bdi_to_reim_for_ebs.sql (present under $BDI_HOME/bdi-int-rfi-job-home/setup-data/ddl folder) from BDI_REIM_INT_SCHEMA schema.

Note:

Please provide rms owner schema as input while executing the grant script.

Grant Privileges for Bdi--Rms--Int App

Grant SELECT, INSERT privileges to *_OUT tables and EXECUTE privilege to PACKAGES from BDI_RMS_INT_SCHEMA (bdi rms JobAdminDataSource schema) to rms01 (rms owner schema).

Execute the grant_privildges_bdi_to_rms_for_ebs.sql (present under $BDI_HOME/bdi-int-rfi-job-home/setup-data/ddl folder) from BDI_REIM_INT_SCHEMA schema

Note:

Please provide rms owner schema as input while executing the grant script.