IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Siebel Business Applications > Configure the module for deployment

Configure the Siebel application to work with the adapter

Configure the Siebel application to work with the adapter by creating an event table and a Siebel business object.

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

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

You must open Siebel Sales Enterprise (or the Siebel application you are using) on your local database with the administrative privileges.

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


Procedure

  1. Create a project called IBM , and lock the project with Siebel tools.

  2. Using the object wizard, create an event table called CX_IBM_EVENT to store the events.

    1. In the event table, create the columns shown in the following table.

      Event table details
      Column Name Type Length Data Type Required Nullable Status
      CONNECTOR_ID Data (public) 255 Varchar No Yes Active
      DESCRIPTION Data (public) 255 Varchar No Yes Active
      EVENT_ID Data (public) 30 Varchar Yes No Active
      EVENT_TYPE Data (public) 20 Varchar Yes No Active
      OBJECT_KEY Data (public) 255 Varchar Yes No Active
      OBJECT_NAME Data (public) 255 Varchar Yes No Active
      PRIORITY Data (public) 10 Varchar No Yes Active
      STATUS Data (public) 20 Varchar Yes No Active
      XID Data (public) 255 Varchar Yes No Active

      If ConnectorId is specified in the AdapterInstanceEvent
      Filter property, the adapter adds the column to the event query. If ConnectorId is not specified in the AdapterInstanceEvent
      Filter property, the adapter ignores the column in the event query.

    2. Create a business component called IBM Event.

    3. Create a time stamp called Field Event, and map it to the CREATED column from CX_IBM_EVENT. Make the Type of this field DTYPE_UTCDATETIME.

    4. Create a business object called IBM Event.

    5. Associate the IBM event business component to the IBM Event business object.

    6. Create an applet called IBM Event List Applet, and base it on the IBM Event business component you created earlier.

    7. Create a view called IBM Event List View, and base it on the IBM Event business object you created earlier.

    8. Create a screen called IBM Event Screen, and associate it to the IBM Event List View in the Siebel tools.

  3. Create a page tab.

    1. Click Start Application > Siebel Sales Enterprise > Page tab.
    2. Right-click and select New Record.

    3. Specify IBM Event as the screen name and IBM Event for the Text - String Override field.
    4. Leave the Inactive field clear.

  4. Create a business object called Schema Version for your IBM project and associate it to the Schema Version business component.

    1. Apply the physical schema for the new tables to your local database. You can do this by querying for the new table, 'CX_IBM_EVENT' and selecting the current query to create a physical schema. Leave the table space and index space blank.

    2. Click Activate to activate the new schema.

  5. Add or modify the Siebel VB or e-scripts for the business component that corresponds to the business objects used at your site. Siebel scripts trigger event notification for business objects. Samples are located in the Samples Folder in your adapter installation.

  6. Create a Siebel repository file by compiling the updated and locked projects on your local database. The new repository file will have an extension of .srf.
  7. Open Siebel Sales Enterprise on your local database.

    1. Create a responsibility called IBM Responsibility for IBM Event List View.

    2. Add the employees or teams who are responsible for reviewing events to the newly created IBM Responsibility.

    3. Create a user name called IBMCONN (or some other user name to be used by the adapter later). Add the user name to the newly created IBM Responsibility and also to the Administrative Responsibility.
  8. Test the application in your local environment to ensure that you have visibility to the IBM Event List View. An event is generated in the view after you create a record in the supported object. As part of the test, create a Account business component instance in Siebel. Confirm that a new Account event appears in the IBM Event List View. (This is assuming that you have added the e-script trigger to the Account business component). If a new Account event does not appear in the view, check for an error and fix it. For more information about the errors that might be generated, check either the Siebel support site or Siebel documentation.

  9. When the test performed in Step 8 is successful, add your new and updated projects to your development server.

  10. Activate the new table in the development server.
  11. Compile a new Siebel repository (.srf) file on the server.
  12. Back up the original repository file on the server.
  13. Stop the Siebel Business Applications server, and replace the original repository file with the newly created one.
  14. Restart the Siebel Business Applications server.

Configure the module for deployment


Related concepts:

Event store