Configuring the Siebel application to work with the adapter

To configure the Siebel application, create an event table and a Siebel business object.

Before you begin

  1. Before you configure the Siebel application to work with WebSphere® Adapter for Siebel Business Applications, you must create a user name and password so that the Adapter Connection wizard can connect to Siebel Business Applications to perform outbound operations, and retrieve Siebel business objects and services.

    You perform this task on the Siebel server, therefore ensure that you are familiar with the Siebel tools that are required to complete it. For information about using Siebel tools, refer to the Siebel tools documentation.

    To open Siebel Sales Enterprise on your local database, you must have administrative privileges.

About this task

To configure the Siebel application, you must create an event table and a Siebel business object. IBM® App Connect Enterprise contains resources that help you to create the event components and triggers. This topic describes how to use those resources. You can also create the event table and Siebel business object manually; for more information, see Creating the event store manually.

Procedure

  1. Locate the Scripts folder at install_dir/tools/ResourceAdapters/Siebel_version/Scripts.

    The Scripts folder contains two folders: Siebel7.x.x and Siebel8.0. Each version has an Event_pkg folder, which contains a .sif file and a number of .js scripts. You use the .sif file to create the event components; it can add business objects, views, and all other Siebel objects to the Siebel repository. The .js scripts help you to create Siebel triggers.

  2. To use the .sif file:
    1. Open Siebel tools and click Tools > Import.
    2. Import the .sif file.
    3. Merge the differences between the .sif file and the Siebel repository.
    4. Recompile the repository into a Siebel repository file (.srf file).
  3. Use the .js scripts to create Siebel triggers.
    The provided samples show how to create entries in the inbound table when new Account objects are created.