Event and archive tables

The connector uses the event table to queue events for pickup. If you have set the ArchiveProcessed property to true or to no value, the connector uses the archive table to store events after updating their status in the event table.

For each event, the connector gets the business object's name, verb, and key from the Event business component. The connector uses this information to retrieve the entire entity from the application. If the entity was changed after the event was first logged, the connector gets the initial event and all subsequent changes. In other words, if an entity is created and updated before the connector gets it from the event table, the connector gets both data changes in the single retrieval.

The following three outcomes are possible for each event processed by a connector:

If events are not deleted from the event table after the connector picks them up, they occupy unnecessary space there. However, if they are deleted, all events that are not processed are lost and you cannot audit the event processing. Therefore, you should also create an archive table and keep the ArchiveProcessed property set to true. Whenever an event is deleted from the event table, the connector inserts it into the archive table.

Configuring event and archive processing

To configure event and archive processing, you must use configuration properties to specify the following information:

Creating the event and archive tables in Siebel, version 7.5

This procedure uses the Siebel Sales Enterprise application as an example. Substitute all references to Siebel Sales Enterprise with the name of the Siebel application in use.

To create the event and archive tables and to trigger the business objects, perform the following procedure:

  1. Ensure that all current projects have been checked in, including:
    Note:
    Ensure that the projects are locked on both the local and development servers.
  2. Apply the six patch files in the following order to your local database:

    When you apply WebSphere business integration system patch files in a Japanese environment, edit all the patch files as follows:

    Edit the first line of each file from:

    <xml version="1.0" encoding="windows-1252"?>

    to:

    <xml version="1.0" encoding="Shift_JPN"?>

    Replace all instances of the "ENU" language setting with "JPN." If you use the search and replace function of your text editor, make sure you use quotation marks around the language setting to make sure no similar words (for example, MENU) are replaced.

  3. When you are prompted, lock the IBM Audit project on your local database.
  4. Ensure that the following have been created:
  5. 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 as the text name.
    4. For the sequence, enter a number greater than the rest of the sequence numbers. This selection determines where the tab is displayed in the application.
    5. Leave the inactive field unchecked.
    6. Go to the Page tab locale and create a new record for IBM Events. Add ENU for the Language Code and IBMEvents for text, if it does not exists.
  6. 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 and IBM Events as the text name.
    4. For the sequence, enter a number greater than the rest of the sequence numbers. This selection determines where the tab is displayed in the screen pull-down menu.
    5. Leave the inactive field unchecked.
    6. Go to the screen menu item locale and create a new record for IBMEvents. Add ENU for language and IBMEvents for text, if it does not exist.
  7. Add or modify the Siebel VB scripts for the business components that correspond to the business objects used at your site. The Siebel VB scripts trigger event notification for business objects.
  8. Apply the physical schema for the new tables to your local database. You can do this by querying for the two new tables, CX_IBM_ARCHIVE_Q and CX_IBM_EVENT_Q, and selecting the current query to create a physical schema. Make sure that you leave the table space and index space blank.
  9. Activate the new schema using the activate button.
  10. Compile the updated and locked projects on your local database to create a new Siebel repository (.srf) file.
  11. Open Siebel Sales Enterprise on your local database. You must have administrative privileges to perform the following:
    1. .Create a new view called IBM Event List View. Tip: Copy the view name from tools and paste it into the View Name field.
    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 the CWCONN user and add it to IBM Responsibility and Administrative Responsibility.
  12. Test the application in your local environment. Ensure that you have visibility to IBM Event List View and that an event is generated in the view after you create a supported object. For example, create a new account in Siebel and check that a new account event appears in the IBM Event List View.
  13. Check in the following updated and locked projects to your development server.
    Note:
    You should check in your locked projects only through the query.
  14. Apply the physical schema to your development database. You can do this by querying for the two new tables, CX_IBM_ARCHIVE_Q and CX_IBM_EVENT_Q, and select the current query to create a physical schema. Make sure that you leave the table space and index space blank.
  15. Activate the queried tables in the development database.
  16. Move to test and production environments accordingly.
  17. Move your newly compiled Siebel.srf file to the server.
Note:
Enable Enterprise Application Integration by going to:
Sitemap > Server Administration > Component Group and selecting Enable.

To set Siebel JAVABean:

  1. Select, Site Map->Server Admin-> Components (Sales Object Manager).
  2. In the lower applet, go to Component Parameter and enter a timeout value.
    Note:
    The Request Timeout current value is set to 600. This means that the connector will die after ten minutes. Based on Siebel, you can change this value to be as large as you want.

Creating the event and archive tables in Siebel, versions below 7.5

This procedure uses the Siebel Sales Enterprise application as an example. Substitute all references to Siebel Sales Enterprise with the name of the Siebel application in use.

To create the event and archive tables and to trigger the business objects, perform the following procedure:

  1. Ensure that all current projects have been checked in.
  2. On your local database, check out and lock the following files:
    Note:
    Ensure that the projects are locked on both the local and development servers.
  3. Apply the seven patch files in the following order to your local database:

    When you apply WebSphere business integration system patch files in a Japanese environment, edit all the patch files as follows:

    Edit the first line of each file from:

    <xml version="1.0" encoding="windows-1252"?>

    to:

    <xml version="1.0" encoding="Shift_JPN"?>

    Replace all instances of the "ENU" language setting with "JPN." If you use the search and replace function of your text editor, make sure you use quotation marks around the language setting to make sure no similar words (for example, MENU) are replaced.

  4. When you are prompted, lock the CW Audit project on your local database.
  5. Ensure that the following have been created:
  6. 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 CW Events as the screen name and IBM Events as the text name.
    4. For the sequence, enter a number greater than the rest of the sequence numbers. This selection determines where the tab is displayed in the application.
    5. Leave the inactive field unchecked.
  7. 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 Events as the screen and IBM Events as the text name.
    4. For the sequence, enter a number greater than the rest of the sequence numbers. This selection determines where the tab is displayed in the screen pull-down menu.
    5. Leave the inactive field unchecked.
  8. Add or modify the Siebel VB scripts for the business components that correspond to the business objects used at your site. The Siebel VB scripts trigger event notification for business objects.
  9. Apply the physical schema for the new tables to your local database. You can do this by querying for the two new tables, CX_CW_ARCHIVE_Q and CX_CW_EVENT_Q, and selecting the current query to create a physical schema. Make sure that you leave the table space and index space blank.
  10. Activate the new schema using the activate button.
  11. Compile the updated and locked projects on your local database to create a new Siebel repository (.srf) file.
  12. Open Siebel Sales Enterprise on your local database. You must have administrative privileges to perform the following:
    1. .Create a new view called Event List View. Tip: Copy the view name from tools and paste it into the View Name field.
    2. .Create a new responsibility called CW Responsibility for Event List View.
    3. .Add the employees or teams who are responsible for reviewing events to the newly created CW Responsibility.
    4. .Create the CWCONN user and add it to CW Responsibility and Administrative Responsibility.
  13. Test the application in your local environment. Ensure that you have visibility to Event List View and that an event is generated in the view after you create a supported object. For example, create a new account in Siebel and check that a new account event appears in the Event List View.
  14. Check in the following updated and locked projects to your development server.
    Note:
    You should check in your locked projects only through the query.
  15. Apply the physical schema to your development database. You can do this by querying for the two new tables, CX_CW_ARCHIVE_Q and CX_CW_EVENT_Q, and select the current query to create a physical schema. Make sure that you leave the table space and index space blank.
  16. Activate the queried tables in the development database.
  17. Move to test and production environments accordingly.
  18. Move your newly compiled Siebel.srf file to the server.
Note:
Enable Enterprise Application Integration by going to:
Sitemap > Server Administration > Component Group and selecting Enable.

To set Siebel JAVABean:

  1. Select, Site Map->Server Admin-> Components (Sales Object Manager).
  2. In the lower applet, go to Component Parameter and enter a timeout value.
    Note:
    The Request Timeout current value is set to 600. This means that the connector will die after ten minutes. Based on Siebel, you can change this value to be as large as you want.

Copyright IBM Corp. 1997, 2004