Last updated on JUNE 10, 2013
Applies to:Oracle Argus Interchange - Version 5.1.3 and later
Information in this document applies to any platform.
We have a testing with a new partner and they use a different Routing ID for sending and receiving E2B Messages/ACKs
We have set up Argus to send with their receiving ID and have been able to configure Cyclone to route the receiving ID to the appropriate ESM folder.
Can you inform us how we should be configuring Argus to cope with the alternate routing ID they transmit their ACK's with.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms