Required modifications

After you have installed the connector, you must copy the Siebel files to a new location, create the event and archive tables, and modify the settings in the Siebel configuration file (siebeljpn.cfg). This section contains the following topics:

Copying Siebel files

After installing the Siebel connector, use the information in Table 1 for copying the Siebel files to the correct location.


Table 1. Where to copy Siebel files

Directory in which files are installed Directory to which files must be copied
ProductDir\connectores\Siebel\COM\ Siebel.dll ProductDir\connectores\Siebel\ Siebel.dll
ProductDir\connectores\Siebel\COM\ repository\CN_SiebelCOM.txt ProductDir\connectores\Siebel\ repository\CN_SiebelCOM.txt
ProductDir\connectores\Siebel\COM\ messages\SiebelCOMConnector.txt ProductDir\connectores\Siebel\ messages\SiebelCOMConnector.txt
ProductDir\connectores\Siebel\COM\ repository\Siebel_BO_CWArchive.txt ProductDir\connectores\Siebel\ repository\Siebel_BO_CWArchive.txt
ProductDir\connectores\Siebel\COM\ repository\Siebel_BO_CWEvent.txt ProductDir\connectores\Siebel\ repository\Siebel_BO_CWEvent.txt

Creating the event and archive tables

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. See the Siebel Tools Guide, Chapter 5, for information on locking projects.
  3. Apply the seven IBM WebSphere Business Integration Adapter patch files in the following order to your local database:
  4. The cweventmanager.spf patch adds the capability to re-queue or delete events from the CW archive table. If you require this functionality, see CW Event Manager for more information before applying the patch. If you are using VB script, apply the cweventmanagervbscript.spf patch. If you are using e-script, apply the cweventmanagerescript.spf patch.
  5. When you are prompted, lock the CW Audit project on your local database. See the Siebel Tools Guide, Chapter 5, for more information on locking projects.
  6. Ensure that the following have been created:
  7. 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 and 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.

    See the Siebel Tools Guide, Chapter 5, for more information on page tabs.

  8. 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 CW Events as the screen and 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.
  9. Add or modify the Siebel VB scripts for the business components that correspond to IBM WebSphere Business Integration Adapter business objects used at your site. The Siebel VB scripts trigger event notification for business objects.
  10. 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. See the Siebel Tools Guide, Chapter 11, for instructions on applying changes to your local database.
  11. Activate the new schema using the activate button. See the Siebel Tools Guide, Chapter 11, for instructions.
  12. Compile the updated and locked projects on your local database to create a new Siebel repository (.srf) file. See the Siebel Tools Guide, Chapter 5, for instructions on compiling projects.
  13. Open Siebel Sales Enterprise on your local database. You must have administrative privileges to perform the following:
    1. Create a new view called CW 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 CW 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.

    See the Siebel Applications Administration Guide, Chapter 2, for more information on responsibilities.

  14. Test the application in your local environment. Ensure that you have visibility to CW Event List View and that an event is generated in the view after you create an IBM WebSphere Business Integration Adapter supported object. For example, create a new account in Siebel and check that a new account event appears in the CW Event List View.
  15. Check in the following updated and locked projects to your development server.

    Note:
    You should check in your locked projects only through the query. See the Siebel Tools Guide, Chapter 5, for more information.
  16. 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.
  17. Activate the queried tables in the development database. See the Siebel Tools Guide, Chapter 8, for more information.
  18. Move to test and production environments accordingly. See the Siebel Tools Guide, Chapter 5, for information on migrating the Siebel repository between databases.

Points to remember

Changing configuration file settings

You may need to change one or more of the configuration file settings described in this section.

Setting the DataSource property

In the siebeljpn.cfg configuration file on the same machine as the connector, set the value of the DataSource configuration property to Server.

Immediate event display

To display new inbound events in Siebel as soon as they occur, set the MaxCachedCursors and MaxCachedDataSets properties in the siebeljpn.cfg file to 0.

Microsoft application conflicts

When the connector is running on the same machine with Microsoft applications, the Microsoft applications might hang. Also, if you have existing Visual Basic code for your business components in Siebel, the connector may fail to process an event. To avoid these situations you can do one of the following:

Copyright IBM Corp. 1997, 2004