Description:
Symptoms
========
If the Siebel Server architecture is composed of resonate Siebel Servers, the server does not expect a value for the parameter ‘Siebel Server’ and since the value of this field cannot be left blank in TIBCO Designer, the adapter fails to connect to the Siebel server and will give an error saying invalid connection string.


Impact
======
Loss of Functionality


Workaround
==========
- Create a new custom global variable with empty (blank) value.
- Use this global variable in the "Siebel Server" parameter in run-time/design-time connection tab
- Do "not" substitute any value for this global variable while connecting to Design-time Adapter or starting the Adapter

Cause
=====
If the Siebel Server architecture is composed of resonate Siebel Servers, each with it's own physical IP address, they will have a single virtual IP Address which does the load balance between Siebel Servers. In this case the parameter ‘Siebel Server’ has to be left blank in the Siebel adapter configuration, as recommended by Siebel. This is because the Resonate Server dynamically chooses the Siebel Server with the lowest utilization.
Since the value of this field cannot be left blank in TIBCO Designer, the adapter fails to connect to the Siebel server and will give an error saying invalid connection string.

If this does not work, please make sure that the 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, please refer to the section ‘Planning Your Siebel Deployment’ in Siebel bookshelf.

Resolution
==========
This issue is fixed in 5.2.0 version of the Siebel Adapter
Symptoms:

Cause:

TIBCO Adapter for Siebel fails to connect to Siebel Server with Resonate configuration