WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Connecting to a clustered Siebel environment

To connect to a Siebel server in a clustered environment, use a siebel.properties file.

Before you start:

Ensure the external software dependencies for Siebel have been set up, as described in Adding external software dependencies for Siebel.

To connect to a Siebel server in a clustered environment, use the siebel.conmgr.virtualhosts property in the siebel.properties file to list the Siebel servers in the cluster.

The siebel.conmgr.virtualhosts property is used to list groups of servers with the same function. An incoming call attempts to connect to each server in a group in turn.

The only property in the siebel.properties file that WebSphere Message Broker supports is siebel.conmgr.virtualhosts. Information message BIP3427 indicates if a siebel.properties file is being used, and error message BIP3428 indicates if a problem occurs when attempting to access the siebel.properties file.

When the list of servers has been set up in the siebel.properties file, you specify the location of the file by using a configurable service, as described in the following steps.

  1. If you do not already have a siebel.properties file, create one with a siebel.conmgr.virtualhosts property that lists the Siebel servers in the cluster. Servers are listed by using a comma separated list in the format hostname:port.
  2. Set the location of the siebel.properties file by using the mqsichangeproperties command; for example:
    mqsichangeproperties MYBROKER -c EISProviders -o Siebel -n siebelPropertiesURL 
    -v C:\siebel.properties
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:50


Task topicTask topic | Version 8.0.0.7 | bc22720_