What is the RIB?

The Retail Integration Bus (RIB) is Oracle's real-time messaging infrastructure that connects all Oracle Retail applications. When something changes in one system, the RIB ensures every other system that cares about that change receives a notification.

Without the RIB, each Oracle Retail module (RMS, Xstore, RPCS, ReIM, SIOCS) would need point-to-point integrations with every other module — an N×N integration nightmare. The RIB provides a centralized hub:

RIB Architecture & Components

┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
│   RMS    │   │  RPCS    │   │  Xstore  │   │  SIOCS   │   │  ReIM    │
│          │   │          │   │          │   │          │   │          │
│ Publisher│   │ Publisher │   │ Publisher│   │ Publisher│   │ Publisher│
│ +        │   │ +        │   │ +        │   │ +        │   │ +        │
│ Subscriber│  │ Subscriber│  │ Subscriber│  │ Subscriber│  │ Subscriber│
└────┬─────┘   └────┬─────┘   └────┬─────┘   └────┬─────┘   └────┬─────┘
     │              │              │              │              │
     └──────────────┼──────────────┼──────────────┼──────────────┘
                    │              │              │
              ┌─────▼──────────────▼──────────────▼─────┐
              │                                          │
              │        WEBLOGIC JMS SERVER               │
              │                                          │
              │   ┌────────────┐  ┌────────────┐        │
              │   │ Topic:     │  │ Topic:     │  ...   │
              │   │ ItemDesc   │  │ PrcChgDesc │        │
              │   └────────────┘  └────────────┘        │
              │                                          │
              │   ┌────────────┐  ┌────────────┐        │
              │   │ Topic:     │  │ Topic:     │        │
              │   │ ASNDesc    │  │ InvAdjDesc │        │
              │   └────────────┘  └────────────┘        │
              │                                          │
              └──────────────────────────────────────────┘

Key Components

• WebLogic JMS Server: The message broker that hosts JMS topics and manages message delivery
• JMS Topics: Named message channels. Each topic carries a specific type of business event (ItemDesc, PrcChgDesc, etc.)
• RIB Adapters: Application-specific connectors that publish messages to and subscribe to messages from JMS topics
• Message Payloads: XML documents conforming to the Oracle Retail Integration XML schema (RIB XML)

The Pub/Sub Messaging Model

RIB uses the Publish/Subscribe (Pub/Sub) pattern:

• Publisher: The system that generates the event. When RMS creates an item, the RMS RIB adapter publishes an ItemDesc message.
• Topic: The logical channel. The ItemDesc topic carries all item-related events.
• Subscriber: Systems that need the event. Xstore subscribes to ItemDesc to update its local item database. RPCS subscribes to ItemDesc to set up pricing for new items.

Key Advantages

1. Loose Coupling: RMS doesn't know (or care) how many systems subscribe to its messages. It just publishes to the topic.
2. Guaranteed Delivery: JMS persists messages to disk. If Xstore is temporarily offline, messages queue up and are delivered when it reconnects.
3. Independent Processing: Each subscriber processes messages at its own pace. A slow subscriber doesn't block other subscribers.
4. Event Replay: Messages can be replayed from the JMS store if a subscriber needs to reprocess historical events.

Message Families & Types

RIB organizes messages into families based on business domain:

Message Types Within a Family

Each message family supports multiple operation types:

• Create: A new entity was created (new item, new PO)
• Modify: An existing entity was changed (item description updated, PO quantity changed)
• Delete: An entity was removed or inactivated
• Detail Create/Modify: Child records were added (PO line items, item-location records)

RIB Adapters

Each Oracle Retail application has a dedicated RIB adapter — a Java application deployed on WebLogic that handles message publishing and subscribing:

Message Flow: Item Creation Example

When a buyer creates a new item in RMS, here's the complete RIB message flow:

1. Buyer creates item 100400012345 in RMS
   └── RMS commits to ITEM_MASTER
   
2. RMS triggers publish to RIB
   └── rib-rms publishes ItemDesc(CREATE) to ItemDesc topic
   
3. JMS persists the message and delivers to all subscribers:
   
   ├── rib-rpcs receives ItemDesc(CREATE)
   │   └── RPCS creates pricing placeholder for new item
   │
   ├── rib-rxm receives ItemDesc(CREATE)  
   │   └── Xcenter routes to relevant stores
   │       └── Xstore updates local Derby DB with new item
   │
   ├── rib-sim receives ItemDesc(CREATE)
   │   └── SIOCS updates local item master for inventory ops
   │
   └── rib-reim receives ItemDesc(CREATE)
       └── ReIM creates item reference for invoice matching

All of this happens within seconds of the buyer clicking "Save" in RMS.

The Error Hospital

When a subscriber cannot process a message (e.g., RPCS can't create pricing because the item's department doesn't exist in RPCS), the message enters the Error Hospital — a holding area for failed messages.

Error Hospital Workflow

1. Message fails processing — the subscriber's adapter logs the error
2. Message moves to error queue — it's removed from the main processing queue to prevent blocking subsequent messages
3. Operations investigates — reviews the error message and root cause
4. Fix the data issue — correct the underlying data problem (e.g., create the missing department in RPCS)
5. Retry the message — the operator marks the errored message for reprocessing
6. Message processes successfully — removed from the error hospital

Common Error Hospital Scenarios

RIHA Monitoring Console

RIHA (Retail Integration Hub Application) is the web-based monitoring console for the RIB:

• Dashboard: Real-time view of message throughput, error counts, and adapter status across all topics
• Error Hospital Manager: Browse, search, and retry errored messages
• Adapter Control: Start, stop, and restart individual RIB adapters
• Message Tracking: Trace a specific message's journey from publisher through topic to all subscribers
• Performance Metrics: Message processing rates, queue depths, and latency measurements

Integration Best Practices