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:
- Event was processed successfully
- Event was not processed successfully
- Event was not subscribed to
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.
To configure event and archive processing, you must use configuration
properties to specify the following information:
- The interval frequency
- The number of events for each polling interval
- Whether the connector archives unsubscribed and unprocessed events
- The unique ID of the connector, which is important when multiple
connectors poll the same table
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:
- Ensure that all current projects have been checked in, including:
- Siebel Sales Enterprise project
- Projects that include objects that you want to modify, such as the Account
project
- Note:
- Ensure that the projects are locked on both the local and development
servers.
- Apply the six patch files in the following order to your local
database:
- ibmtable.sif
- ibmview.sif
- ibmapplet.sif
- ibmbo.sif
- ibmbc.sif
- ibmcreen.sif
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.
- When you are prompted, lock the IBM Audit project on your local
database.
- Ensure that the following have been created:
- Two new tables, CX_IBM_Archive_Q and CX_IBM_Event_Q
- One new business object, IBM Events
- One new business object, Schema version
- Two new business components, IBM Archive and IBM
Events
- One new view, IBM Event List View
- Two new applets, IBM Archive List Applet and IBM Event
List Applet
- One new screen IBM Events and one new screen view, IBM
Event List view
- Create a page tab as follows:
- Access the Application > Siebel Sales Enterprise > Page tab.
- Right-click and select New Record from the menu.
- Enter IBM Events as the screen name and IBM Events
as the text name.
- 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.
- Leave the inactive field unchecked.
- 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.
- Create a screen menu item as follows:
- Access the Application > Siebel Sales Enterprise > Screen Menu
Item.
- Right-click and select New Record.
- Enter IBM Events as the screen and IBM Events as the
text name.
- 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.
- Leave the inactive field unchecked.
- 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.
- 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.
- If you want to sort events by priority, edit the priority values in the
business objects VB scripts before compiling them.
- If you are installing multiple connectors, set and activate the Connector
Id in the VB scripts.
- 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.
- Activate the new schema using the activate button.
- Compile the updated and locked projects on your local database to create a
new Siebel repository (.srf) file.
- Open Siebel Sales Enterprise on your local database. You must have
administrative privileges to perform the following:
- .Create a new view called IBM Event List View.
Tip: Copy the view name from tools and paste it into the View Name
field.
- .Create a new responsibility called IBM Responsibility
for IBM Event List View.
- .Add the employees or teams who are responsible for reviewing
events to the newly created IBM Responsibility.
- .Create the CWCONN user and add it to IBM
Responsibility and Administrative Responsibility.
- 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.
- Check in the following updated and locked projects to your development
server.
- IBM Audit
- Siebel Sales Enterprise
- The project for the business objects that you want to use
- Note:
- You should check in your locked projects only through the query.
- 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.
- Activate the queried tables in the development database.
- Move to test and production environments accordingly.
- 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:
- Select, Site Map->Server Admin-> Components (Sales Object
Manager).
- 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.
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:
- Ensure that all current projects have been checked in.
- On your local database, check out and lock the following files:
- New Table Project
- Siebel Sales Enterprise project
- Projects that include objects that you want to modify, such as the Account
project
- Dock project
- Note:
- Ensure that the projects are locked on both the local and development
servers.
- Apply the seven patch files in the following order to your local
database:
- cwtable.sif
- cwview.sif
- cwapplet.sif
- cwbo.sif
- cwbc.sif
- cwdo.sif
- cwscreen.sif
- schemabo.sif
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.
- When you are prompted, lock the CW Audit project on your local
database.
- Ensure that the following have been created:
- Two new tables, CX_CW_Archive_Q and CX_CW_Event_Q
- One new business object, Events
- One new business object, schema version
- Two new business components, Archive and Events
- One new view, Event List View
- Two new applets, Archive List Applet and Event List
Applet
- One new screen Events and one new screen view, Event
List view
- Two new dock objects, CX_CWArchive and CX_CWEvent
- Create a page tab as follows:
- Access the Application > Siebel Sales Enterprise > Page tab.
- Right-click and select New Record from the menu.
- Enter CW Events as the screen name and IBM
Events as the text name.
- 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.
- Leave the inactive field unchecked.
- If you are using Siebel 6, proceed to Step 7.
- If you are using Siebel 7, go to the Page tab locale and create a new
record for CW Events. Add ENU for the
Language Code and IBMEvents for text, if it does not exists.
- Create a screen menu item as follows:
- Access the Application > Siebel Sales Enterprise > Screen Menu
Item.
- Right-click and select New Record.
- Enter Events as the screen and IBM Events as the
text name.
- 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.
- Leave the inactive field unchecked.
- If you are using Siebel 6, proceed to Step 8.
- If you are using Siebel 7, go to the screen menu item locale and create a
new record for CWEvents. Add ENU for language and
IBMEvents for text, if it does not exist.
- 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.
- 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.
- Activate the new schema using the activate button.
- Compile the updated and locked projects on your local database to create a
new Siebel repository (.srf) file.
- Open Siebel Sales Enterprise on your local database. You must have
administrative privileges to perform the following:
- .Create a new view called Event List View.
Tip: Copy the view name from tools and paste it into the View Name
field.
- .Create a new responsibility called CW Responsibility
for Event List View.
- .Add the employees or teams who are responsible for reviewing
events to the newly created CW Responsibility.
- .Create the CWCONN user and add it to CW
Responsibility and Administrative Responsibility.
- 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.
- Check in the following updated and locked projects to your development
server.
- New Table
- CW Audit
- Dock
- Siebel Sales Enterprise
- The project for the business objects that you want to use
- Note:
- You should check in your locked projects only through the query.
- 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.
- Activate the queried tables in the development database.
- Move to test and production environments accordingly.
- 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:
- Select, Site Map->Server Admin-> Components (Sales Object
Manager).
- 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.
