2
Defining a Delivery Channel

This chapter describes how to use Oracle Application Server ProcessConnect to define a delivery channel to connect to a Siebel 2000 system.

This chapter discusses the following topics:

• Adding and Configuring a Delivery Channel

• Verifying Your Siebel Information

• Troubleshooting Siebel Settings

Adding and Configuring a Delivery Channel

Part of the application definition includes adding a delivery channel for the adapter. Setting up the delivery channel in Oracle Application Server ProcessConnect requires information which is specific to the adapter.

See Also: Oracle Application Server ProcessConnect User's Guide for details about adding an application delivery channel in Oracle Application Server ProcessConnect

1. Select the Profiles > Applications tabs.

2. Click Create.

   

   Text description of the illustration create.gif

3. Type an application name in the Name field.

4. Select the Siebel application type from the Application Type box and click Apply.

5. Click Add in the Adapter Types section to add the Oracle Application Server Integration Adapter for Siebel 2000.

   The Add Adapter Type page appears.

   

   Text description of the illustration add.gif

6. Select Siebel2000 Adapter in the Type selection box in the Add Adapter Type page and click Apply.

   The Adapter Type Details: Siebel Adapter page is displayed.

   

   Text description of the illustration del_create.gif

7. Click Create in the Delivery Channels section in the Adapter Type Details page.

8. Add the following information to create a delivery channel.

   In Table 2-1 an asterisk (*) indicates a required field.

   Note: All parameters are case-sensitive.

   Table 2-1  Siebel Specific Parameters

   Field	Description
   Name*	Enter a name for the delivery channel.
   Enterprise Server*	Enter the Siebel Enterprise Server name. The default is ES_SIEBEL.
   Gateway*	Enter the name of the gateway. The default is siebel_srvr.
   Application Server*	Enter the name of the application server where you have access to all the metadata for the Siebel system. The metadata is the information regarding the Business Services and Business Objects, which is the container for Business Components. The default is SS_SIEBEL.
   Object Management Server*	Enter the name of the Siebel Object Management server. The default is SCCObjMgr.
   Repository*	Enter the name of the repository where the Siebel Repository files are located. The Siebel Repository contains Business Service methods, Business Components, and typed method arguments. The default is Siebel Repository.
   Login Timeout	This is the amount of time Oracle Application Server ProcessConnect waits when attempting to log on to a Siebel system. If the login fails within that amount of time, Oracle Application Server ProcessConnect returns an exception to the user. It can be set to any value between 1 and 300 seconds (5 minutes). The default is 10 seconds.
   Connection Timeout	This is the amount of time Oracle Application Server ProcessConnect waits for a response before the request times-out. This value must be set between 10 and 300 minutes. Networks with a higher load should have this timeout variable set to a higher limit to allow enough time for the request to process. The purpose of having Login timeout is to keep the threads from deadlocking. If there is no response within the specified time, the system stops sending packets and issues a timeout. At that point, you need to re-initiate a login. The default is 30 minutes.
   User Name*	Enter a user name to login to the Siebel system.
   Password*	Enter the password of the specified user. You must have developer rights to the areas of the Siebel system you want to access.

   

   Text description of the illustration questions.gif

   See Also: "Troubleshooting Siebel Settings" for connection error information

9. Click Apply after entering your parameters to connect to a Siebel system.

   The delivery channel Confirmation screen appears. You can modify any parameters and click Update in the confirmation page to change your parameters or click Delete to remove the channel.

   

   Text description of the illustration del_update.gif

10. Click the Return to List link to return to the Adapter Details page.

    The delivery channel is added for the adapter and you can now add interactions.

    See Also: Chapter 3, "Defining an Interaction"

Verifying Your Siebel Information

To assist in connecting to a Siebel system, the following provides a brief description of Siebel terms and where you can locate information in a Siebel system.

• An Application Server refers to the name of the Siebel system. This is the name of host machine on which the Siebel system is installed.

• A Gateway refers to the name of the host on which gateway server is running.

• An Enterprise refers to the name that was specified for the Enterprise server during a Siebel installation.

  An Enterprise Server is a logical entity. It collectively represents the Siebel application servers and Gateway server.

You can retrieve the name of the Gateway server, Application server, Enterprise, and Repository from the siebel.cfg file located in siebel-root/siebsrvr/BIN directory.

You can verify the Siebel user name and password by running Siebel Call Center. When you launch this application, you need to enter the user name and password (which has administrator privileges). If it successfully connects to the Siebel system, it means that the user name and password are correct.

Troubleshooting Siebel Settings

Error ID	Possible Cause / Error Description	Possible Correction
E-SBL0016	Siebel Java Data Bean jars are missing. Failed to instantiate Siebel Java Data Bean on thread -742484740	Verify your CLASSPATH settings. Refer to "Software Requirements".
E-SBL0030	Wrong Enterprise, app server, gateway server, Object manager. Error Message: Call to Login failed.	Verify your Siebel connection parameters. The parameters are case-sensitive. Refer to "Enterprise Server*".
	Wrong Repository - Business Services: Call to GetBusinessServices failed.	Verify your repository setting. Refer to "Repository*".
	Wrong Repository - Business Objects: Call to GetBusinessObjects failed.	Verify your repository setting. Refer to "Repository*".
	Wrong User or Password - Call to Login failed. You have entered an invalid set of logon parameters.	Reenter your logon parameters. The parameters are case-sensitive. Refer to "User Name*".
E-SBL0039	Siebel Java Data Bean jars are missing	Thread task failed while trying to do login. Refer to "Software Requirements".
	Wrong Enterprise, app server, gateway server, Object manager. Thread task failed while trying to do login. Error Message: Call to Login failed.	Verify your Siebel connection parameters. The parameters are case-sensitive. Refer to "Repository*".
	Wrong Repository - Business Services: Thread task failed while trying to retrieve business services.	Verify your repository setting. Refer to "Repository*".
	Wrong Repository - Business Objects: Thread task failed while trying to retrieve business objects.	Verify your repository setting. Refer to "Repository*".
	Wrong User or Password. Thread task failed while trying to do login.	Reenter your logon parameters. The parameters are case-sensitive. Refer to "User Name*".