The following sections describe how to configure the connector:
This section contains some general points to consider to ensure a successful implementation.
Since the connector is single threaded, you must set the -t option in the connector shortcut before running the connector.
In order for the connector to insert data into the Siebel database, the Row_Id attribute must be in the CW_Siebel business object. Also, in order to perform an update or delete you must do one of the following:
Before attempting to access Siebel with the connector, ensure that all multi-value links, multi-value fields, multi-value groups and picklists exist in Siebel as defined in the CW_Siebel business objects.
A multi-value link exists between two Siebel business components that have a one-to-many or many-to-many relationship and reside in the same screen or applet. However, the connector assumes that a multi-value link exists between any two business components that have a one-to-many or a many-to-many relationship, regardless of whether they reside in the same screen or applet.
If the connector must process 5000 or more multiple events, use the RefreshLogonCycle connector property. This enables the connector to disconnect and reconnect to the client after processing a specified number of events. For more information, see Connector configuration properties
The connector is dependent on the Siebel.srf file in the objects directory. Therefore, when changes are made in the Siebel application, the Siebel.srf file must be replaced with the updated version.
CW Event Manager is a view in the CWEvents screen. It is used to re-queue events from the CW archive table to the CW event table for reprocessing by the connector. CW Event Manager can also be used to delete processed events from the CW archive table. Events that have been re-queued will have "Requeued Event" added to their description in the CW archive and CW event tables. This makes it easier to identify and delete duplicate events from the CW archive table.
This view provides two options. After entering the event criteria in the appropriate fields, you can either delete or re-queue the selected events. If you are using the start time and end time fields to select events, use the format: mm/dd/yy hh:mm:ss AM/PM. For example 3/28/01 9:45:32 PM. CW Event Manager converts this to military time.
CW Event Manager is script-dependent. You must apply the appropriate CW Event Manager patch depending on whether you are using VB or e-script. After applying the patch, perform the following:
The Siebel dll avoids performance overhead in retrieving and comparing the application image with the sent business object. The child verb must be set manually when SkipRetrieve is set to true, otherwise the children will inherit the parent verb; because there is no retrieve, that might not be the result needed.
SkipRetrieve is an ASI, which can have values of true or false. This new ASI can be used only at the BC Parent level, which is immediately inside the parent business object. When this ASI is being used, the name of the business object must be set after nm= and must be separated from SkipRetrieve ASI by a semicolon.
For example, in Siebel_BCAccount the ASI will be nm=Account;SkipRetrieve=true.
You can configure the following behaviors of the event delivery mechanism:
The connector can be configured to retrieve a specified number of Siebel_BC_CWEvent business objects and process them in a single poll. Processing multiple events per poll can improve performance when the application generates large numbers of events.
The number of events per poll is specified using application-specific information on the Retrieve verb of the Siebel_BC_CWEvent business object. You can change the application-specific information for this business object using the System Manager just as you would for any application-specific business object.
To specify the number of events processed on each poll, use the attribute-value pair max=n. For example, to specify that the connector retrieve 25 event business objects per poll, use the following application-specific information on the Retrieve verb:
[Verb] Name = Retrieve AppSpecificInfo =max=25 [End]
You can assign priority values to events to specify the order in which the connector selects events to process. Event priority enables the connector poll method to handle situations where the number of events in the event store exceeds the maximum number of events the connector retrieves in a single poll.
Event priority is set in the Siebel VB script for each business component. By default, priority for all business objects is set to 1, and events are sorted by creation date.
To enable sorting by priority, first edit the VB scripts to change the priority to a value between 0 (highest) and 5 (lowest). Then, add the name-value pair sort=Priority, EventTs(ASCENDING) to the application-specific information of the Retrieve verb on the Siebel_BC_CWEvent object. This text specifies that events are sorted first by priority and then by creation date in ascending order.
Always specify a maximum number of events to retrieve per poll. If you also specify sorting by priority, the maximum events attribute-value pair precedes the priority attribute-value pair. For example, to specify sorting by priority, use the following application-specific information on the Retrieve verb of the Siebel_BC_CWEvent object:
[Verb] Name = Retrieve AppSpecificInfo =max=25;sort=Priority, EventTs(ASCENDING) [End]
If sort=Priority is not specified, sorting defaults to the creation date, and the priority is not checked.
You can set one or more attributes in a subscription delivery business object by specifying them in the Object Key field of a Siebel VB script. If the total length of the attributes is greater than the length of the Object Key field (80 characters), use the Additional Object Key field which, supports up to 250 characters. Object Key is a required value. Therefore, when using the Additional Object Key field, you must set a dummy value for the Object Key field.
To set the Additional Object Key field:
In the script, you can specify an attribute and value using a name-value pair, or using a fully qualified path beginning with a forward slash (/). The syntax of a composite key is:
/attribute/[/attribute]=value[;/attribute[/attribute]=value]
You can also specify only the attribute value; in this case, the first key of the first child business object attribute is set.
For example, a VB script that sets only a single key, such as ContactId in the Siebel_BCContact business object, might include these lines:
RowId=GetFieldValue("Id") Set EventBC = EventBO.GetBusComp("CW Events") EventBC.SetFieldValue "Object Key" , RowId
A script that sets keys for the ContactId and AccountId attributes in the Siebel_BCContact business object might include these lines:
RowId = GetFieldValue("Id") Account = GetFieldValue ("Account Id") Key = "/Siebel_BCContact/ContactId=" + RowId + ";/Siebel_BCContact/AccountId=" + Account EventBC = EventBO.GetBusComp("CW Events") EventBC.SetFieldValue "Object Key" , Key
To streamline the processing of certain types of Siebel events, you can install and configure multiple connectors on a Siebel client and configure each connector to handle specific business objects. Because multiple connectors can access the same Siebel application, each connector can process events of a given type and pass them to the integration broker. This can increase throughput and speed the transfer of data into and out of the Siebel application.
To install and set up multiple connectors, follow these steps:
Each connector picks up events that match its ConnectorId property value. If you do not assign a value to the ConnectorId property, the connector picks up all events.
.ActivateField "Connector Id" .SetFieldValue "Connector Id", "2"