How to configure multiple APIX engines connecting to the same EMS Server?
Article ID: KB0077873
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | ALL |
Description
When APIX is configured with Target Operations using ESB or SOAPJMS transport,
- the request queues are configured on the Target Operation
- and the response queues are set in the asg.properties files
for e.g.:
If your Target Operation is using ESB0 channel, then the default replyQueue it uses is:
--------
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue=asg.out.request.reply.0.0
--------
One can also check the "replyTo" property set on the Request Message(using Gems or such tool).
If both the APIX engines are connected to the same EMS queue, they will both have listeners on the same reply queue and pick up messages meant for the other engine.
Environment
All Supported Platforms
Resolution
To resolve this please configure unique replyQueues for each engine.
for e.g.:
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue=asg.out.request.reply.APIX1
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue=asg.out.request.reply.APIX2
for e.g.:
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue=asg.out.request.reply.APIX1
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue=asg.out.request.reply.APIX2
Issue/Introduction
This article provides inputs on setting up multiple APIX engines connecting to the same EMS Server
Feedback
Yes
No
Powered by
