Siebel setup with MQ Queue managers in CLUSTER
(Doc ID 759972.1)
Last updated on MARCH 01, 2018
Applies to:Siebel Financial Services CRM - Version 188.8.131.52 SIA  and later
Siebel CRM - Version 8.0 SIA  and later
Information in this document applies to any platform.
Customer wanted to know suitable inputs for the below architecture to work:
The requirement is to have multiple Siebel Application Servers to be running on one Enterprise.The current EAI setup requires running multple MQ Queue managers with each server.The standard setup suggested by middleware group is to use middleware Queue managers and siebel Q managers in cluster.
Inside a cluster each siebel Q managers needs to have a unique name which poses the problem of providing the connection parameters to the Integration workflow.
An Enterprise profile for connection subsystem was created but with clustering in effect,a single connection subsystem does not work.
Different connection subsytems can be created but the integration workflow which need to send the outbound message needs to be aware of which of them to be used. Currently the workflow can be executed on any of the multiple Appserver and only the Q manager details of that server will work to send the details. The workflow has no means of knowing which server its running on and hence no means to get the correct Connection parameters.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|