OIC Publisher/Subscriber Pattern Works Incorrectly
(Doc ID 2600376.1)
Last updated on OCTOBER 17, 2019
Applies to:Oracle Integration-OIC - Version 18.2.5 and later
Information in this document applies to any platform.
When researching the OIC Publisher/Subscriber pattern, an integration (name is XOR) was created, that receives message by REST (POST) and using FTP adapter writes a file adding new records are received.
Then a Subscriber integration was created that receives messages from Messaging Service and transfers them to the first integration (XOR).
The Publisher integration was created and receives messages from REST (POST) interface, and transfers them to the Messaging Service.
The path is Publisher -> MS -> Subscriber -> XOR.
It works fine.
In order to imitate a network issue by deactivating XOR integration, continue to send messages to the publisher and all messages are received and stored in a queue.
After that, activate XOR integration again and expect all not delivered messages will be saved in a file at the XOR side.
All messages sent while XOR being was deactivated were lost.
Any message queue must deliver all messages, even if an endpoint is in unreachable state within any period of time.
Of course they must be delivered after an endpoint has became reachable.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document