| Oracle® Retail Integration Bus Installation Guide Release 13.0.1 Patch |
|
 Previous |
 Next |
This manual details the installation of the Retail Integration Bus (RIB). Generally, a RIB installation contains the following components:
An installation of RIB's Java EE applications (rib-<app>.ear) on Java EE 5 compliant application server.
An installation of the Retail Integration RIB Hospital administration (RIHA) tool.
An installation of the RIB Diagnostics and Monitoring tools.
It is imperative to also follow all installation steps of the Oracle Retail Applications that are being connected to the RIB. Failure to follow these may result in a faulty RIB installation. See the install guides of the relevant Retail applications for more information.
This covers all of the sequential steps required to perform a full install of the RIB, using either the GUI RIB Installer (strongly recommended) or a command line installation.
Table 1-1
| Task | Notes |
|---|---|
|
Prepare the Oracle Application Servers for installation of the RIB Components. |
Prerequisite |
|
Prepare the Oracle Database Schemas that the RIB will use. |
Prerequisite |
|
Prepare the JMS. |
Prerequisite |
|
Verify the Applications the RIB will be integrating to are configured appropriately. |
|
|
"Information to Gather for the Install" |
During the prerequisites steps, there is information that should be noted that will be used to configure the RIB during the installation process. |
|
Install the RIB using one of these methods:Installation using the RIB Installer GUIOrInstallation using the RIB App Builder Command Line Tools. |
It is strongly recommended that the RIB Installer GUI method be used. |
|
Verify Application URL settings match RIB install. |
RIB Functional Artifact URLJNDI URL |
|
Complete the setup of RDMT using the same "Information to Gather for the Install" |
During either of the Install methods, one of the manual steps will have extracted the RDMT tools to the appropriate directory. |
|
Verify the RIB installation using the RDMT tools. |
|
|
Install RIHA. |
The RIB Hospital maintenance tool |
|
Note: See Appendix C, "RIB Installation Check Lists", while performing the install, in order to minimize the chance of a faulty RIB installation. |
The RIB has several dependencies on Oracle Retail Application installations as well a the Oracle Application Servers. This section covers these requirements.
General Requirements for a RIB compatible database server include:
UNIX based OS certified with Oracle RDBMS 10g Enterprise Edition Oracle RDBMS 10g Release 2 Enterprise Edition (minimum 10.2.0.3.0 patch set required).
XA support installed and grants made (see database section).
|
Note: See also Oracle® Database Administrator's Guide 10g Release 2 (10.2) and Oracle® Application Developer's Guide - Fundamentals 10g Release 2 (10.2). |
Oracle AQ Streams requires an Oracle database server:
UNIX like OS certified with Oracle RDBMS 10g Enterprise Edition Oracle RDBMS 10g Release 2 Enterprise Edition (minimum 10.2.0.3.0 patch set required)
General requirements for an application server capable of running RIB 13 include:
UNIX based OS certified with Oracle Application Server 10g version 10.1.3.3 with the following patches:
Patch 5398506
Patch 5632264
|
Note: See RIB Release 13.0.1 Patch Release Notes for the compatibility matrix. |
The RIB supports the following platforms in this release:
| Platforms | Versions |
|---|---|
|
HP UX |
11.23 Itanium |
|
IBM AIX |
5.3 |
|
Sun Solaris |
10 |
|
Enterprise Linux |
Enterprise Linux AS Release 4 (October Update 5) |
|
WARNING: For AIX, the IBM JDK located at ORACLE_HOME/jdk is not supported by the RIB. Make sure that IBM Java SDK 1.5.0 build pap32dev-20080315 (SR7) or newer is installed on the RIB system and configured as the JAVA_HOME for the RIB OC4J instances. |
The information in this table reflects the most recently tested compatibility of the RIB with other Oracle Retail software products.
Oracle Retail Store Inventory Management (SIM) Release 13.0.1 Patch
Oracle Retail Advanced Inventory Planning (AIP) Release 13.0.1 Patch
Oracle Retail Price Management (RPM) Release 13.0.1 Patch
Oracle Retail Merchandising System (RMS) Release 13.0.1 Patch
Oracle Retail Warehouse Management System (RWMS) Release 13.0.1 Patch
In this release, rib-<app> uses Oracle Streams AQ as the JMS provider. Oracle Streams AQ is built on top of Oracle database system. Since AQ is hosted by Oracle database system the RIB can take advantage of database RAC capability for its JMS provider. By using RAC AQ as the RIB's JMS provider you can scale RIB's JMS server vertically and horizontally to meet any retailer's scalability and high availability need.
At runtime, rib-<app> uses the database for keeping track of its RIB Hospital records. These RIB Hospital tables can be hosted by an Oracle RAC database providing high availability and scalability for these RIB Hospital records.
All rib-<app>s use the Oracle type 4 Java Database Connectivity (JDBC) driver to connect to the RIB Hospital database and the AQ JMS server. When the RIB Hospital database and the AQ JMS servers are hosted by a Oracle RAC database, the only configuration change required in rib-<app> is the RAC JDBC connection URL.
The RIB uses JMS server for message transportation between the integrating retail applications. Since the RIB must preserve the message publication and subscription ordering, rib-<app>s deployed in Oracle Application Server cannot be configured in an active-active cluster mode. In active-active cluster mode, multiple subscribers and publishers will process messages simultaneously and there will be no way to preserve message ordering.
The rib-<app> can be deployed to a "single" oc4j instance of an Oracle Application Server that is clustered (active-passive). In this configuration, even though rib-<app> is deployed in an OAS cluster, multiple instance of same rib-<app> is not running at the same time as there is only one oc4j instance where the rib-<app> is deployed and so RIB can still preserve message ordering. The maximum number of JVM (Java Virtual Machine) hosting a rib-<app> oc4j instance must always be configured to be 1 for the same reason of preserving message ordering.
To truly configure rib-<app>s for high availability, the only option is to configure it in active-passive mode.
