Oracle® Retail Service Backbone Cloud Service Oracle® Retail Service Backbone Cloud Service Implementation Guide Release 19.0.000 F25617-01 |
|
Previous |
Next |
RSB implements a synchronous request-reply based integration pattern while RIB implements near real time asynchronous fire and forget integration pattern. RSB is implemented using Web Services while RIB uses JMS. RSB and RIB can exist independently. However, they are different types of integration and in many cases they complement each other. They can co-exist in an enterprise. Both implementations can be bridged using IGS for RIB bound transactions and Injector service for RSB bound transactions.
In RSB integration errors have to be handled by the consumer. RSB does not offer any retry mechanism like RIB. RIB and RSB are not mutually exclusive. Both can be implemented together and both RIB and RSB can communicate with each other. RSB does not replace RIB. It complements RIB with the request reply type of integration. RSB can be clustered in active - active mode. RSB does not need sequencing of messages.
RIC is designed as a consolidated view of both RSB and RIB, if each exists. The current version of RIC shows RIB configuration and transaction data, in addition to RSB configuration and transaction data.
Note: See also the Oracle Retail Integration Console Guide. |
Table 9-1 RIB Vs RSB
RIB | RSB |
---|---|
JMS Publish - Subscribe |
Web Services on OSB |
Guaranteed Delivery |
Consumer gets error on failure |
Failed Message Recovery |
Consumer has to manage errors |
Fire-and-Forget |
Request Response |
XSD Schema |
XSD, XSLT, WSDL |
Remote Invocation |
|
Only active-passive cluster supported |
Active-active cluster supported |
Near real-time response |
Real-time response |