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:
After installing the Siebel connector, use the information in Table 7 for copying the Siebel files to the correct location.
Table 7. 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
|
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. See the Siebel Tools Guide, Chapter 5, for information on
locking projects.
- Apply the seven IBM WebSphere Business Integration Adapter patch files in
the following order to your local database:
- cwtable.spf
- cwview.spf
- cwapplet.spf
- cwbo.spf
- cwbc.spf
- cwdo.spf
- cwscreen.spf
- 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.
- 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.
- Ensure that the following have been created:
- Two new tables, CX_CW_Archive_Q and CX_CW_Event_Q
- One new business object, CW Events
- Two new business components, CW Archive and CW
Events
- One new view, CW Event List View
- Two new applets, CW Archive List Applet and CW Event List
Applet
- One new screen CW Events and one new screen view, CW 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 and 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.
See the Siebel Tools Guide, Chapter 5, for more information on page
tabs.
- Create a screen menu item as follows:
- Access the Application>Siebel Sales Enterprise>Screen Menu
Item.
- Right-click and select New Record.
- Enter CW Events as the screen and 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.
- 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.
- 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.
- Activate the new schema using the activate button. See the Siebel
Tools Guide, Chapter 11, for instructions.
- 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.
- Open Siebel Sales Enterprise on your local database. You must have
administrative privileges to perform the following:
- Create a new view called CW 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
CW 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.
See the Siebel Applications Administration Guide, Chapter 2, for more
information on responsibilities.
- 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.
- 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. See
the Siebel Tools Guide, Chapter 5, for more information.
- 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. See the
Siebel Tools Guide, Chapter 8, for more information.
- Move to test and production environments accordingly. See the
Siebel Tools Guide, Chapter 5, for information on migrating the Siebel
repository between databases.
- Distribute the new repository file to remote users via diskette or
e-mail. This file replaces the existing.srf file in
the Siebel object directory. The new repository file was created on
your local database when you compiled your projects.
- When configuring the production environment, change the data source in the
configuration file from local to server. This specifies that the
connector should obtain data from the server instead of from each remote
user. Under connector properties, determine which Siebel configuration
file is in use and change the DataSource property in that file from
Local to Server.
- Remote users must synchronize in order to update their systems with the
event and archive tables.
You may need to change one or more of the configuration file settings
described in this section.
In the siebeljpn.cfg configuration file on the same
machine as the connector, set the value of the DataSource
configuration property to Server.
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.
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:
- If you are not running a Siebel client application on the same machine
where the connector is running, open the siebeljpn.cfg file
on the machine where the connector is running, and change the
EnableBasic property to false.
- If you are running the Siebel client application on the same machine where
the connector is running, you can create a second configuration file named
cwsiebeljpn.cfg by copying and renaming the
siebeljpn.cfg file in the same directory, and then changing
the EnableBasic property in the new file to
false. Make sure both configuration files point to the same
siebel.srf repository file. Make sure that you change
the SiebelConfigFile property in the System Manager so that it
points to the renamed configuration file. This allows the Siebel
client, connector, and Microsoft Applications to co-exist and function
normally on the same machine.
