Question & Answer
Question
Which configurations are required to connect to a clustered Siebel Server with the WebSphere Adapter for Siebel on WebSphere Message Broker runtime?
Answer
The information contained in this document has been moved to developerWorks Answers located here. This technote will be archived in 60 days. Please bookmark the new location.
The following adjustments are required when connecting to a clustered Siebel server with the WebSphere Adapter for Siebel through the siebel.properties file. The WebSphere Adapter for Siebel is set as configurable service on the WebSphere Message Broker.
1) Verify the siebel. properties modifications for a single server Siebel environment, as described in the technote below:
2) Check the information center on the configurable service set up for connection to a clustered environment:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/bc22720_.htm
3) Perform the following adjustments to prevent the properties from not getting overridden for the deployed adapter file.
a) Add "VirtualServer" to the connection string of the adapter node in the WebSphere Message Broker Toolkit: e.g. "siebel://VirtualServer/<siebel server>/<application>"
b) Add the "VirtualServer" to the siebel.properties file, together with the clustered IP addresses for the Siebel servers:
siebel.conmgr.virtualhosts=VirtualServer=1:10.20.30.170:2321,2:10.20.30.171:2321;
This allows the Java™ Data Bean API to substitute "VirtualServer" with one of the IP addresses
using Siebel native load balancing (Round Robbin).
A detailed description of the steps required can be found in the following blog entry: https://www.ibm.com/developerworks/mydeveloperworks/blogs/aimsupport/entry/connect_to_a_clustered_siebel_server_from_websphere_message_broker?lang=en
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21498460