You must satisfy the following prerequisites for creating a connection with the Oracle Siebel Adapter.
Ensure that the target Siebel server is up and running.
Know the hostname address and port number of the Siebel server.
Know the username and password for connecting to the Siebel server.
Ensure that the user called by the Oracle Siebel Adapter has access to both the Java Data Bean (JDB) and the SOAP Web service invocation roles.
Each Siebel instance has a version-specific Siebel.jar/SiebelJI_enu.jar file located at Siebel_Installation_Directory/ses/siebsrvr/CLASSES. After installing the connectivity agent, copy the JARs to Agent_Home/thirdparty/lib and restart the connectivity agent.
Siebel has access control at both design time and runtime, although this may vary functionally.
At design time, the Oracle Siebel Adapter fetches a catalog of published web services through a native Siebel business service called Web Service Publisher. The Oracle Siebel Adapter does this by internally invoking the Java data bean provided by Siebel. To access this business service through this Siebel Java data bean, the user you configure in your Oracle Siebel Adapter connection must be given access to this Siebel business service called Web Service Publisher (and specifically the methods GetWebServiceList and RetrieveWebService within this service) to get the list of published web services. Configuration is described in the Siebel documentation. See the Siebel Security Guide.
To invoke any of the Siebel web services at runtime, you need access at varying levels depending on the type of user (for example, anonymous or a named user). The Siebel documentation covers topics on access roles for these web services. See Integration Platform Technologies: Siebel Enterprise Application Integration.