Description:
Please verify below in case of adapter not able to connect to Siebel Server:

1) Siebel Application server and back end Data Base is up and running
2) There is no networ issue between adapter and server machin and server machine is accessible
3) If the Siebel Java Data Bean jar files are of correct Siebel version, it should be exactly from the Siebel server to be connected
4) If the connection parameters provide to the adapter is correct while trying to connect to the target Siebel application.

To confirm the connection parameter, Compile the attached java program and run it. Check if the java program is able to establish connections, if so use same parameter with adapter to establish connection.

*************************************************************
Below is quick information on the Sample program
*************************************************************

Sample program connects to Siebel outside TIBCO environment, using mechanism similar to the way adapter connects to Siebel. You would need to add the Siebel JDB path to the system classpath before compiling the program.  

Eg:- set CLASSPATH=C:\siebjars\sieb78\SiebelJI_enu.jar;C:\siebjars\sieb78\Siebel.jar

NOTE: There has been a change in the name of the JAR files provided by Siebel in Siebel application version 7.7. V7.7 installation will not have SiebelJI_Common.jar and SiebelJI.jar files. A Siebel 7.7 tools installation should have 3 jar files under %Siebel_Tools_ROOT%\CLASSES folder - SiebelJI_&ltlanguage>.jar, Siebel.jar and Siebel_JavaDoc.jar. Please note that SiebelJI.jar and SiebelJI_common.jar in v7.5.3 were combined in Siebel 7.7 into Siebel.jar file.


Also specify the following parameters for connection string in the java program
connectString = "siebel.&lttransport>.&ltencryption>.&ltcompression>://&ltgtwysrvr>/&ltenterpriseServer>/&ltObjectmanager>/&ltSiebel Server>" ;

Below is the description for each field:

Transport: Choose one of the following values: tcpip or http. By default it would be tcpip.
Encryption: Possible values are ‘none’ and RSA. By default in most cases of Siebel implementation it is ‘none’.
Compression: The type of compression for network communications (Possible values are none, zlib, or pkware). If compression is required on both the client and server side when using Resonate, it must be specified for both sides. Each side compresses communications as defined. When Resonate is not used, the server side drives the compression and any client side settings are ignored.
Gtwysrvr: Name of the machine running the gateway server along with the port number.
EnterproseServer: Name of the Siebel enterprise server.
Objectmanager: Name of the object manager being connected to.
Siebel Server: Name of the Siebel Server.
E.g:  connectString = "siebel.tcpip.none.zlib://kangchenjunga/sieb78/SCCObjMgr_enu/”;

************************************************************************

IMPORTANT NOTE: This java program works outside TIBCO's environment and is made available on an AS-IS basis, and is NOT supported by TIBCO Software. Please do not use it for any other purpose, especially during production runs.

What should I do if TIBCO Adapter for Siebel 5.x is unable to connect to the target the Siebel application.