Description:
The Siebel architecture is composed of resonate Siebel Servers, each with it's own physical IP Address. In front of these machines we have a virtual IP Address which does the load balance between Siebel Servers.

When using the Siebel Server with resonate configuration, the Siebel Adapter might fail to connect to the Siebel Server if the value for "Siebel Server" parameter is "not"  blank (Not even space).

As recommended by Siebel, we should not specify any value for "Siebel Server" parameter if Resonate is being used. This is because the Resonate Server dynamically chooses the Siebel Server with the lowest utilization.

- For connection parameter "Host", provide the name/IP and port number of the computer on which the gateway server is installed. e.g.: acctibinfo20:2320
- Enter correct values for "Object Manager" and "Enterprise Server" parameters.
- Do not enter any value for parameter "Siebel Server" (Not even a space).

However, there is a known issue with Siebel Adapter 5.1.0 ( LBN1-4O35UG ) design time, where the design time (in both design-time and run-time connection tabs) will not allow you to leave the Siebel Server field blank. This has been fixed in 5.2.0 version of the adapter. A simple workaround for this issue is,
    - define a custom global variable, say "SiebelServerName" in the Global Variable tab with value as blank (empty string).
    - use this global variable in the "Siebel Server" field in design-time/run-time connection tab.
    - Do "not" provide any value for this global variable while starting the adapter.

If this does not work, please make sure that Connection Broker or Resonate Scheduler does not reside on any server that is part of the cluster. In other words, if Name Server is clustered, then the same server cannot run Resonate scheduler. Also Load-balanced Siebel Server should not reside on the same server as a clustered server. For more information on the same, refer to section Planning Your Siebel Deployment  in Siebel bookshelf.