Prerequisites for starter activities in Siebel

This section contains the prerequisites to configure the Siebel inbound activities.

You must create an event store in Siebel as a prerequisite for using the starter activities.

Creating the Event Store in Siebel

This procedure uses the Siebel Sales Enterprise application as an example. For convenience, whenever we say Siebel application, it means Siebel Sales Enterprise application in the following chapter. IBM Events are used as the event store name in this example. This name can be changed based on the end user needs.

To create an ‘Event Store’ and ‘Object’ in Siebel Business Applications, perform the following procedure in Siebel tools:
  1. Using New Object Wizard, create a stand-alone table CX_IBM_EVENT.
  2. Create these columns in your new table:
    Table 1. Columns for the event table
    Column Name / User Name Type Length Physical Type Required Nullable Status
    DESCRIPTION Data (public) 255 Varchar   Active
    EVENT_ID Data (public) 30 Varchar   Active
    CONNECTOR_ID Data (public) 255 Varchar   Active
    EVENT_TYPE Data (public) 20 Varchar   Active
    OBJECT_KEY Data (public) 255 Varchar   Active
    OBJECT_NAME Data (public) 255 Varchar   Active
    PRIORITY Data (public) 10 Number   Active
    STATUS Data (public) 20 Number   Active
    XID Data (public) 255 Varchar   Active
  3. Create a new Business Component (BC) IBM Events based on your new table. All fields are single value fields.
  4. In addition to the fields in BC, create a new field Event Time Stamp and map it to CREATED column in from CX_IBM_EVENT. The Type of this field should be DTYPE_UTCDATETIME.
  5. Create a new Business Object (BO) IBM Events.
  6. Associate IBM Events BC to IBM Events BO.
  7. Create IBM Event List Applet based on IBM Events BC.
  8. Create IBM Event List View based on IBM Events BO.
  9. Create IBM Events Screen and associate it to the IBM Event List View in Screen View.
  10. Create a page tab as follows:
    1. Access the Application > Siebel Sales Enterprise > Page tab.
    2. Right-click and select New Record from the menu.
    3. Enter IBM Events as the screen name and IBM Events for the Text-String Override.
    4. Leave the inactive field unchecked
  11. Create a screen menu item as follows:
    1. Access the Application > Siebel Sales Enterprise > Screen Menu Item.
    2. Right-click and select new record.
    3. Enter IBM Events as the screen name and IBM Events for the Text–String Override.
    4. Leave the inactive field unchecked.
  12. Create a new Business Object Schema Version for IBM project and associate it to Schema Version BC.
  13. Apply the physical schema for the new tables in your local database. You can do this by querying on the new table, CX_IBM_EVENT. Select the current query to create a physical schema. Make sure that you leave the table space and index space blank.
  14. Activate the new schema using Activate.
  15. Add or modify the Siebel VB or e-scripts for the BC that corresponds to the business objects used at your site. Siebel scripts triggers event notification for the configured objects (sample scripts are in the <studio_root>/etc/Siebel folder). In the Siebel script, ensure that the event will not get created for the connector user name to prohibit the ping-pong effect.
  16. Compile the updated and locked projects in your local database to create a new Siebel repository (.srf) file.
  17. Open Siebel Sales Enterprise in your local database. You need to have administrative privileges to perform the following:
    1. Create a new view called IBM Event List View.
    2. Create a new responsibility called IBM Responsibility for IBM Event List View.
    3. Add the employees or teams who are responsible for receiving events to the newly created IBM Responsibility.
    4. Create the IBMCONN (or your connector user name) user and add it to IBM Responsibility and Administrative Responsibility.
  18. Test the application in your local environment. Ensure that you have the visibility to IBM Event List View and that an event is generated in the view after you create a record in supported object. For example, create a new account in Siebel and check if a new account event appears in the IBM Event List View.
  19. Check-in the new and updated projects into your development server.
  20. Activate the new tables in the development database.
  21. Compile a new Siebel.srf file and deploy it on the server.

You have successfully created the event store in the Siebel server.




Feedback | Notices


Timestamp icon Last updated: Wednesday, 15 June 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Siebel_prerequisites_inbound_activity.html