1
Introduction to Oracle Application Server Integration Adapter for Siebel 2000

Oracle Application Server ProcessConnect connects to a Siebel system through the Oracle Application Server Integration Adapter for Siebel 2000. The Oracle Application Server Integration Adapter for Siebel 2000 provides connectivity and executes interactions on a Siebel system.

This chapter discusses the following topics:

• Architecture: Oracle Application Server Integration Adapter for Siebel 2000

• Software Requirements

• Supported Platforms

• Postinstallation

• Siebel Configuration

Architecture: Oracle Application Server Integration Adapter for Siebel 2000

Oracle Application Server Integration Adapter for Siebel 2000 is a JCA-based component that plugs in to Oracle Application Server ProcessConnect. Using the Oracle Application Server Integration Adapter for Siebel 2000, you can access Siebel Business Components and Business Services. The Oracle Application Server Integration Adapter for Siebel 2000 uses configuration options from its associated Oracle Application Server ProcessConnect Delivery Channel definition to determine how to connect to and log on to the Siebel system. The Oracle Application Server Integration Adapter for Siebel 2000 uses Siebel Java Data Bean classes to communicate to the Siebel system. As shown in Figure 1-1, the Oracle Application Server Integration Adapter for Siebel 2000 runs on the machine running Oracle Application Server ProcessConnect and uses the SISNAPI (Siebel Internet SessioN API) protocol, which is a session-based RPC to communicate with the Siebel system.

Figure 1-1 Architecture

Text description of the illustration xipsi001.gif

For Business Components, the Oracle Application Server Integration Adapter for Siebel 2000 supports Insert, Query, QueryWithViewMode, Update and Delete operations.

The Oracle Application Server Integration Adapter for Siebel 2000 supports outbound interactions. The interactions have both request and reply records. Each record has one record element associated with it. The following naming convention is used for the records:

• Request records

  AEProtocolName_interactionGroupName_interactionName_Request 
  
  

• Reply records

  AEProtocolName_interactionGroupName_interactionName_Reply 
  

  See Also: Chapter 3, "Defining an Interaction"

Software Requirements

The Oracle Application Server Integration Adapter for Siebel 2000 connects to Siebel, Version 6.2.1 with patch 110 or higher.

The following jar files must be accessible:

• SiebelTcOM.jar

• SiebelTcCommon.jar

• SiebelTC_enu.jar

• SiebelDataBean.jar

These jar files comprise the Siebel Java Data Bean provided on the Siebel installation CD.

Supported Platforms

Oracle Application Server Integration Adapter for Siebel 2000 is supported on:

• Solaris 8 (2.8)

• HP-UX 11.0

Postinstallation

Verify you are connecting to Siebel, Version 6.2.1 with patch 110 or higher.

Copy the following jar files from your Siebel installation and place them in ORACLE_install/ip/adapters/lib:

• SiebelTcOM.jar

• SiebelTcCommon.jar

• SiebelTC_enu.jar

• SiebelDataBean.jar

The following discussion refers to the Oracle database that is the back-end to the Siebel system. Siebel may require many open database cursors if you are running any kind of remote client--Siebel tools, Siebel client, or Oracle Application Server ProcessConnect. Although the default setting in the ora*.ini file is 100 open cursors maximum, Siebel recommends 1500 when using remote clients. You can edit ora*.ini (your file name may vary) using a text editor. The Oracle installation determines the name of the ora*.ini file.

Siebel Configuration

Siebel requires that you enable the Siebel Thin Client Enterprise Component to allow any thin clients to communicate remotely with the Siebel Application Server. Ensure that the Siebel Thin Client Enterprise component is enabled.

1. Log on using the Siebel Client (with Server Administration enabled).

   The user ID must have sufficient authorization to make server management changes.

2. Select Screens > Server Administration > Enterprise Configuration > Enterprise Component Groups.

3. Ensure that the Thin Client component is enabled.

   If it is not enabled, select the component in the list and click Enable.

   

   Text description of the illustration comp_ent.gif

4. Restart Siebel to ensure that the settings are registered and the component started.