Oracle® Retail Service Backbone Integration Console User Guide Release 19.0 F22955-02 |
|
![]() Previous |
![]() Next |
This chapter provides an overview of RIC modes and provides instructions for configuring and installing RIC. The RIC installation steps differ for different RIC modes. RIC can be deployed in three modes in this release, the following table shows RIC modes:
Supported Models | Description | When to use? | Settings in the deployment file |
---|---|---|---|
RIB ONLY | RIC is configured to collect and display only RIB data. | If RIB is in-scope and RSB is out-of-scope for your integration. | "ribEnable":"true",
"rsbEnable":"false", "bdiEnable":"true", |
RSB ONLY | RIC is configured to collect and display only RSB data. | If RSB is in-scope and RIB is out-of-scope for your integration | "ribEnable":"false",
"rsbEnable":"true", "bdiEnable":"true", |
DUAL (RIB+RSB) | RIC is configured to collect and display both RIB and RSB data. | If both RIB and RSB are in-scope for your integration. | "ribEnable":"true",
"rsbEnable":"true", "bdiEnable":"true", |
How do you decide the mode in which you should run RIC?
Retailer's site -specific integration topology must drive this decision. Customers that use both RIB and RSB must configure the RIC to run with Dual (RIB + RSB) mode. This configuration yields maximum visibility of integration system and is the recommended mode. Customers that use only messaging infrastructure for integration (RIB) must configure RIC with RIB_ONLY mode. Lastly, when only service oriented integration (RSB) is used then, you must configure RIC with RSB_ONLY mode.
BDI is disabled by default in all RIC modes, and is out of scope for this release. The value of the properties ribEnable and rsbEnable in the ric configuration file ric-deployment-env-info.json inside ric-home/conf/ folder decides RIC mode.
Take the following steps to configure RIC:
Edit the ric-deployment-env-info.json as follows:
cd ric-home/conf/
vi ric-deployment-env-info.json
The following is an example configuration:
{ "RicDeploymentEnvInfo":{ "DataSourceDef":{ "RicDataSource":{ "dataSourceName":"RicDataSource", "dataSourceClass":"oracle.jdbc.pool.OracleDataSource", "dataSourceJndiName":"jdbc/RicDataSource", "jdbcUrl":"jdbc:oracle:thin:@//richost.com:1521/orcl", "jdbcUserAlias":"ricDataSourceUserAlias", "jdbcUser":"GET_FROM_WALLET", "jdbcPassword":"GET_FROM_WALLET" } }, "MiddlewareServerDef":{ "RicAppServer":{ "weblogicDomainName":"TOOLS_Domain", "weblogicDomainHome":"/scratch/u00/webadmin/WLS12.2.1.3/user_projects/domains/TOOLS_Domain/", "weblogicDomainAdminServerUrl":"t3://richost.com:24001", "weblogicDomainAdminServerProtocol":"t3", "weblogicDomainAdminServerHost":"richost.com", "weblogicDomainAdminServerPort":"24001", "weblogicDomainAdminServerUserAlias":"ricAppServerAdminServerUserAlias", "weblogicDomainTargetManagedServerName":"ric-server", "ricUiUrl":"http://richost.com:24012/rsb-admin", "ricUiUserGroup":"RicAdminGroup", "ricUiUserAlias":"ricAdminUiUserAlias", "ricUiUser":"GET_FROM_WALLET", "ricUiPassword":"GET_FROM_WALLET", "secureCookie":"false" } }, "IntegrationProduct":{ "ribEnable":"true", "rsbEnable":"true", "bdiEnable":"true", "ribHome":"../../../RIB/rib-home/", "rsbHome":"../../../RSB/rsb-home/", "bdiHome":"../../ric-home" }, "RicApplication":{ "ricAppUses":[ "RicDataSource", "RicAppServer" ] }, "BdiBatchJobAdminInfo":{ "BdiRmsAdmin":{ "batchJobAdminUrl": "http://bdihost:8080/bdi-rms-batch-job-admin", "optional":"true" }, "BdiSimAdmin":{ "batchJobAdminUrl": "http://bdihost:8080/bdi-sim-batch-job-admin", "optional":"true" }, "BdiOcdsAdmin":{ "batchJobAdminUrl": "http://bdihost:8080/bdi-ocds-batch-job-admin", "optional":"true" } }, "BdiProcessFlowAdminInfo":{ "processFlowAdminUiUrl":"http://bdihost:7001/bdi-batch-process-flow-admin", "optional":"true" }, "BdiSchedulerAdminInfo":{ "schedulerAdminUiUrl":"http://bdihost:7001/bdi-batch-scheduler-admin", "optional":"true" } } }
Modify the DataSourceDef, the MiddlewareServerDef, and the IntegrationProduct with information that is specific to your environment.
In order to hide host and port wherever exposed in RIC, set the below java option to TRUE in the Weblogic instance startup.
JAVA_OPTIONS="${JAVA_OPTIONS} -DMaskServerInfo.appServerHostPort=true"
For the masking of the jdbc url in RIC, set the below java option to TRUE in the Weblogic instance startup.
JAVA_OPTIONS="${JAVA_OPTIONS} -DMaskServerInfo.db=true"
After configuring the RIC, follow the installation steps according to the selected RIC mode.
Install the RIC in the RIB only mode to provide visibility into the RIB. The following pre-requisites must be met:
RIB must be deployed.
JMS Console must be deployed from the rib-home/tools-home/.
rib-home must be accessible to ric-home, that is both must reside in the same file system.
The rib-deployment-env-info.xml must have a correct notification configuration for every rib-app in scope. RIC will use this email address to send notifications related to RIB.
Configure a new mail session as below on the Weblogic server where you deploy RIC. This is for RIC to send notification emails on exceeding the error thresholds.
Login to the Weblogic admin console.
Navigate to Admin Console > Services > Mail Sessions.
Create a new mail session with the JNDI Name as "mail/RicMailSession".
Add the below JavaMail properties:
mail.smtp.ssl.enable=true
mail.smtp.auth=true
mail.smtp.ssl.trust=example.com
mail.smtp.port=465
mail.transport.protocol=smtps
mail.smtp.host=example.com
mail.from=admin@example.com
Take the following steps to deploy the RIC in RIB only mode:
Download RicKernel19.0.0ForAll19.x.xApps_eng_ga.zip to a location (for example, RIC-APP-BUILDER) on the computer which has your rib-home.
Edit the ric-deployment-env-info.json configuration file located in the ric-home/conf/ folder.
Modify MiddlewareServerDef and IntegrationProduct with information that is specific to your environment.
Set the value of the ribEnable property in the configuration file to True.
Set the value of the ribHome property in the configuration file to point to rib-home.
Set the value of secureCookie to true if the cookies has to be secure.
Set the value of the RicAppServer fields to point to the environment where you want to deploy RIC.
Go to the ric-home/bin/ folder and run the compiler to update the RIC ear as follows: $ sh ric-app-compiler.sh -setup-credentials.
When prompted by the compiler, enter the user name and password for WebLogic server and RIC admin user. The RIC admin user is used to log in to the RIC.
From the same folder, run the deployer script to create the user and group and deploy RIC on the WebLogic server as follows: $ sh ric-app-deployer.sh –deploy-ric-app.
Restrict access to the $RIC-HOME folder:
cd $RIC-HOME
chmod -R 700 .
Install the RIC in the RSB only mode to provide visibility into the RSB. The following pre-requisites must be met:
RSB must be deployed.
Cross-domain security should be enabled to establish communication trust between the RSB domain and the Tools domain where RIC app is deployed.
Refer to "Appendix: Enabling Cross Domain Security Trust between Weblogic Servers Domains" for steps to enable cross domain security
rsb-home must be accessible to ric-home, in other words both reside in the same file system.
Note: If the RIB is already installed, we recommend configuring the RIC in a DUAL mode which provides visibility into the RIB and RSB systems. For more information, see DUAL Mode (RIB and RSB). |
Take the following steps to deploy the RIC in a RSB only mode:
Download RicKernel119.0.0ForAll19x.xApps_eng_ga.zip to a location (for example, RIC-APP-BUILDER) on your computer which has your rsb-home.
Edit the ric-deployment-env-info.json configuration file located in the ric-home/conf/ folder.
Modify the DataSourceDef, MiddlewareServerDef, and the IntegrationProduct with information that is specific to your environment.
Set the value of the rsbEnable property in the configuration file to True.
Set the value of the rsbHome property in the configuration file to point to rsb-home.
Set the value of the RicDataSource : jdbcUrl property to the same as that of the service-infrastructure-db.jdbc-url property in rsb-home/deployment-home/conf/rsb-deployment-env-info.properties.
Set the value of the RicAppServer fields to point to the environment where you want to deploy the RIC.
Set the value of secureCookie to true if the cookies has to be secure.
Note: Make sure RicDataSource and RsbDataSource point to the same database schema. |
Go to the ric-home/bin/ folder and run the compiler to update the RIC ear as follows: $ sh ric-app-compiler.sh -setup-credentials.
When prompted by the compiler, enter the user name and password for WebLogic server, RicDataSource, and the RIC admin user. The RIC admin user is used to log in to the RIC.
From the same folder, run the deployer script to create the user and group and deploy the RIC on the WebLogic server as follows: $ sh ric-app-deployer.sh –deploy-ric-app.
Restrict access to the $RIC-HOME folder:
cd $RIC-HOME
chmod -R 700 .
Install the RIC in the DUAL mode to provide visibility into both RIB and RSB. The following pre-requisites must be met:
RIB must be deployed.
JMS Console must be deployed from the rib-home/tools-home/.
RSB must be deployed.
rib-home and rsb-home must be accessible to ric-home, in other words both must reside in the same file system.
Cross-domain security should be enabled to establish communication trust between RSB domain and Tools domain where RIC app is deployed.
Refer to "Appendix: Enabling Cross Domain Security Trust between Weblogic Servers Domains" for steps to enable cross domain security
Take the following steps to deploy RIC in DUAL mode:
Download RicKernel19.0.0ForAll19.x.xApps_eng_ga.zip to a location (for example, RIC-APP-BUILDER) on the computer which contains the rib-home and rsb-home.
Edit the ric-deployment-env-info.json configuration file located in the ric-home/conf/ folder.
Modify the DataSourceDef, MiddlewareServerDef, and the IntegrationProduct with information that is specific to your environment.
Set the value of ribEnable and rsbEnable property in the configuration file to True.
Set the value of ribHome property in the configuration file to point to rib-home.
Set the value of rsbHome property in the configuration file to point to rsb-home.
Set the value of bdiHome property in the configuration file to point to rsb-home.
Set the value of RicDataSource : jdbcUrl property to the same as that of the service-infrastructure-db.jdbc-url property in rsb-home/deployment-home/conf/rsb-deployment-env-info.properties.
Set the value of the RicAppServer fields to point to the environment where you want to deploy the RIC.
Set the value of secureCookie to true if the cookies has to be secure.
Note: make sure RicDataSource and RsbDataSource point to the same database schema. |
Go to the ric-home/bin/ folder and run the compiler to update the RIC ear as follows: $ sh ric-app-compiler.sh -setup-credentials.
When prompted by the compiler, enter the user name and password for WebLogic server, RicDataSource, and RIC admin user. The RIC admin user is used to log in to the RIC.
From the same folder, run the deployer script to create the user and group and deploy the RIC on the WebLogic server as follows: $ sh ric-app-deployer.sh –deploy-ric-app.
Restrict access to the $RIC-HOME folder:
cd $RIC-HOME
chmod -R 700 .