| Oracle® Retail Integration Bus Cloud Service Installation Guide Release 19.1.000 F31805-01 |
|
 Previous |
 Next |
| Oracle® Retail Integration Bus Cloud Service Installation Guide Release 19.1.000 F31805-01 |
|
Previous |
Next |
This chapter provides instructions for running the RIB Application Builder Tools.
|
Note: If there is an existing WebLogic installation on the server, you must upgrade to WebLogic 12.2.1.4.0. All middleware components associated with WebLogic server should be upgraded to 12.2.1.4.0.Back up the weblogic.policy file ($WLS_HOME/wlserver/server/lib) before upgrading your WebLogic server, because this file could be overwritten. Copy over the weblogic.policy backup file after the WebLogic upgrade is finished and the post patching installation steps are completed. |
The RIB application builder can be used to perform any of the tasks below. For a new installation, all tasks are recommended.
Run the Preparation Phase to unpack files, prepare the workspace, and perform preinstallation verifications.
Run the Assembly Phase to build the EAR and WAR files for the rib-<app> applications.
Configure the Advanced Queuing JMS topics for RIB.
Run the Deployment Phase to deploy the EAR and WAR files to the application servers.
Restart the WebLogic server.
For more information about the Preparation, Assembly and Deployment Phases, see the Oracle Retail Integration Bus Operations Guide.
To start the RIB application installation, do the following.
Undeploy all old rib-apps and completely remove them from the AdminServer upload directory as follows.
Shut down all the rib-* servers.
Delete all rib-* apps from the deployments menu in WebLogic.
|
Note: Be sure to remove ONLY the rib-* apps and no others. If other applications are removed, their deployments will break. |
Remove them from the upload directory if they exist:
cd [RIB_DOMAIN]/servers/AdminServer/uploadrm -rf rib-*
Start the rib-servers up again before starting the installation.
Expand the RIB Kernel distribution as described in Expand the RIB Kernel Distribution.
Download the RIB Functional Artifacts distribution (RibFuncArtifact19.1.000ForAll19.1.000Apps_eng_ga.tar), and copy it into the <RIB_HOME>/download-home/rib-func-artifacts directory. Do not untar the file.
Download the tar file distributions for each rib-<app> application (RibPak19.1.000For<app>19.1.000_eng_ga.tar) that you will install. Copy the files into the <RIB_HOME>/download-home/all-rib-apps directory. Do not untar the files.
Download the RIB Diagnostic and Monitoring Tools (RDMT) package (Rdmt19.1.000ForAll19.x.xApps_eng_ga.tar) and untar it into the <RIB_HOME>/tools-home directory. Several files will be placed under the rdmt directory when you untar the package. Run the <RIB_HOME>/tools-home/rdmt/configbuilder.sh script after the RIB installation.
For multiple JMS servers only: If your RIB installation includes more than one JMS server, you must complete the additional preinstallation steps in the section, Preinstallation Steps for Multiple JMS Server Setup.
Set the JAVA_HOME environment variable. The JAVA_HOME must be set to a JDK 1.8.0+ 64 bit with latest security updates, within the 1.8 code line. 64 bit. For Linux and Solaris OS only.
Make sure that all WebLogic instances that you intend to deploy to are currently running.
Give execute permissions to rib-home:
For example, chmod -R 700 rib-home.
Change directories to the <RIB_HOME>/download-home/bin directory and run check-version-and-unpack script to extract all the tarball contents.
Change directories to the <RIB_HOME>/application-assembly-home/bin directory and rRun the rib-app-compiler.sh script. Provide the needed inputs , compilation prompts for.
Change directories to the <RIB_HOME>/deployment-home/bin directory and run the rib-app-deployer.sh script.
Restart the rib-<app>-server. During the installation process a shared library is created that contains the JDBC Driver update. For PL/SQL applications, it is necessary to bounce the WebLogic managed server instance.
Manually run the RDMT at this time to verify the installation.
To check log files, do the following.
Check the log files in <RIB_HOME>/deployment-home/log to ensure that all RIB applications deployed successfully.
If errors are encountered, verify that the installer inputs were correct.
If all installer inputs were correct, it may be necessary to rerun the rib app builder with the existing <RIB_HOME>/deployment-home/conf/rib-deployment-env-info.xml file. Running the tools multiple times usually resolves any extraneous errors.
|
Note: Using multiple JMS servers allows for the isolation of flows for performance and operational QoS. For more information, see "JMS Provider Management" section in the Oracle Retail Integration Bus Operations Guide. |
If your RIB installation will include multiple JMS servers, additional steps are required before you can run the rib application builder.
|
Note: Do not follow these steps if you are using only one JMS server. |
Determine the family that must be configured for multiple JMS.
Locate the rib-integration-flows.xml inside the rib-func-artifacts.war.
Examine the rib-integration-flows.xml to identify all the RIB applications participating in the integration flows that must be configured with multiple JMS.
Ensure that a new AQ JMS database server (not a schema) is set up. For information see "Prepare Oracle AQ JMS Provider" in this guide.
Ensure that any additional AQ JMS are not in the same database server. Each new AQ JMS requires a new database server.
Add JMS servers by updating rib-deployment-env-info.xml.
In the rib-home, modify the appropriate files for each of the rib-<apps> that participate in the integration flow. Point the adapters to the right JMS server. The following applies to this step:
rib-<app>-adapters.xml
rib-<app>-adapter-resources.properties
|
Note: For more information on this step, see the Oracle Retail Integration Bus Operations Guide. |
Once Step 6 is finished, do the following to complete preinstallation activities:
Compiles all rib apps
($RIB_HOME/application-assembly-home/bin/rib-app-compiler.sh).
Runs prepare-jms for the newly-created JMS server
($RIB_HOME/deployment-home/bin/rib-app-deployer.sh -prepare-jms<jms2>). This step configures additional JMS servers.
Deploys ($RIB_HOME/deployment-home/bin/rib-app-deployer.sh rib-<app>).
Restart the WebLogic managed servers.
Rib-Ext is a new component added for external apps/3rd party integration with RIB. The RIB-EXT app organizes all publishers and subscribers adapters required by an external system and makes it easy to integrate from thirdparty systems. The list of publisher and subscriber adapters are defined by the customer's implementation team.
Following are the steps required to enable customer's specific integration flows:
The install tarball(RibPak19.1.000ForExt19.1.000_eng_ga) includes a version of the configuration file with all adapters enable as well as a copy of the file based on the customer's configuration..
rib-ext-adapters.xml (undesired flows can be commented out)
rib-ext-adapters_gap.xml (flows have been pre-determined)
If required, copy rib-ext-adapters_gap.xml to rib-ext-adapters.xml.
Proceed with rib installation.
This is new feature introduced in this release wherein user can pick a set of adapters at runtime from list of all available adapters for rib-<app>. This feature is enabled by default for rib-ext as it has a big list of adapters.
The following steps are required for enabling the dynamic adapter selection feature in all other rib-<app>:
The install tarball(RibPak19.1.000For<app>19.1.000_eng_ga) includes a properties file.
rib-<app>.properties (eg- rib-sim.properties)
Edit rib-<app>.properties file to add below flag
enableDynamicAdapterInstanceSelection=true
Proceed with RIB installation.
