Oracle® Retail Financial Integration for Oracle Retail Merchandise Operations Management and Oracle Financials Installation Guide Installation Guide Release 16.0.2 E99801-02 |
|
![]() Previous |
![]() Next |
This chapter includes:
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.
Table 10-1 Hybrid Cloud Topology Applications
Applications to be installed | Hybrid Topology | On-Premise Topology |
---|---|---|
RMS-EDGE |
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 is a sender side app to be installed in the retail cloud. Bdi-rfi is the receiver side app to be installed on premise environment like RFI and EBS.
Assuming that edge applications installation instructions are provided by RMS and application teams.
Rms-Edge-App: Please refer to RMS 16.0.2 install guide and create a RMS environment that includes BdiEdgeAppJobAdminPakForRms.
The app can be deployed in any domain but it is recommended to deploy it in the existing RMS domain with separate managed server.
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
Assuming that WebLogic 12.2.1.3.0 and JRF domain are installed as part of ORFI installation.
To deploy the BDI RFI Batch Job Admin war, take the following steps.
Download BdiIntJobAdminPak16.0.2ForRfi16.0.2_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.2ForRfi16.0.2_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.
Table 10-2 JSON File Configuration Properties
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>:<rms edge managed server port>/rms-batch-job-admin |
SystemOptions->Name |
Name of the odi domain home SystemOptions ->Value Replace with local odi_domain_home directory |
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.
Table 10-3 Credential Aliases
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 |
RMS edge 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 .
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.
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
Perform the following procedure to install the Process Flow application:
Download the process flow archive BdiProcessFlow16.0.2ForAll16.x.xApps_eng_ ga.zip
Unzip the downloaded archive. The Process Home directory will be created under the current directory.
unzip BdiProcessFlow16.0.2ForAll16.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. |
Table 10-4 Aliases Configuration Fields
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 |
SimJobAdminAppServer ->jobAdminUiUrl |
BDI SIM app job admin URL |
SimAppJobAdminAppServer->jobAdminUiUrl |
BDI SIM job admin URL |
OcdsAppJobAdminAppServer->jobAdminUiUrl |
BDI Ocds job admin URL |
RpasAppJobAdminAppServer->jobAdminUiUrl |
BDI Rpas job admin URL |
RfiJobAdminAppServer-->jobAdminUiUrl |
BDI RFI job admin URL |
ExternalAppJobAdminServer->jobAdminUiUrl |
BDI External job admin URL |
RmsAppJobAdminAppServer -> jobAdminUiUrl |
RMS 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 and RFI, the rms_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/.
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:
Table 10-5 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 |
rfiJobAdminBaseUrlUserAlias |
BDI RFI job admin app credentials |
rmsappJobAdminBaseUrlUserAlias |
RMS APP job admin credentials |
simJobAdminBaseUrlUserAlias |
SIM job admin app credentials |
simAppJobAdminBaseUrlUserAlias |
SIM app job admin app credentials |
ocdsAppJobAdminBaseUrlUserAlias |
OCDS app job admin app credentials |
externalAppJobAdminBaseUrlUserAlias |
EXTERNAL app job admin app credentials |
rpasAppJobAdminBaseUrlUserAlias |
RPAS 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.