IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Creating the event store manually

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

Configuring the Siebel application to work with the adapter describes how to use the samples that are supplied with WebSphere® IBM® Integration to configure the Siebel application. This topic describes how to create the event store manually.

The following steps describe how to create the event store to be used for inbound operations in the Siebel application. You can substitute all references to Siebel Sales Enterprise with the name of the Siebel application that you are using.

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

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

In the event table, create the columns that are shown in the following table.

Column Name	Type	Length	Data Type	Required	Nullable	Status
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

Create a new business component called IBM Event.
Create a new time stamp called Field Event, and map it to the CREATED column from CX_IBM_EVENT. Make the Type of this field DTYPE_UTCDATETIME.
Create a new business object called IBM Event.
Associate the IBM event business component to the IBM Event business object.
Create an applet called IBM Event List Applet, and base it on the IBM Event business component that you have created.
Create a view called IBM Event List View, and base it on the IBM Event business object that you have created.
Create a screen called IBM Event Screen, and associate it with the IBM Event List View in the Siebel tools.

Create a page tab.
1. Click Start Application > Siebel Sales Enterprise.
2. Right-click the Page tab, and click New Record.
3. Specify IBM Event as the screen name, and IBM Event for the Text - String Override field.
4. Leave the Inactive field blank.
Create a new business object called Schema Version for your IBM project and associate it with the Schema Version business component.
1. Apply the physical schema for the new tables to your local database by querying for the new table, CX_IBM_EVENT_Q 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.
Add or modify the Siebel VB or e-scripts for the business component that corresponds to the business objects that are used at your site. Siebel scripts trigger event notification for business objects. Samples are located in the Samples folder in your adapter installation.
Create a new Siebel repository file by compiling the updated and locked projects on your local database. The new repository file has an extension of .srf.
Create and populate a new responsibility.
1. Open Siebel Sales Enterprise on your local database.
2. Create a new responsibility called IBM Responsibility for IBM Event List View.
3. Add the employees or teams who are responsible for reviewing events to the newly created IBM Responsibility.
4. Create a user name called IBMCONN (or another 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.
Test the application in your local environment to ensure that you can see 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 new Account business component instance in Siebel. Confirm that a new Account event is shown in the IBM Event List View (assuming that you have added the e-script trigger to the Account business component). If a new Account event is not displayed in the view, check for an error and fix it. For more information on the errors that might be generated, check either the Siebel support site or Siebel documentation.
When the test that you perform in Step 8 is successful, add your new and updated projects to your development server.
Activate the new table in the development server.
Compile a new Siebel repository (.srf) file on the server.
Back up the original repository file on the server.
Stop the Siebel server and replace the original repository file with the newly created one.
Restart the Siebel server.

stsba_configeis.htm |

Last updated Friday, 21 July 2017