To configure event and archive processing, you must use configuration
properties to specify the following information:
- The name of the event table (EventTableName). You need not specify a value for this
property if you use the connector only to process business object
requests.
- The interval frequency (PollFrequency).
- The number of events for each polling interval (PollQuantity).
- The name of the archive table (ArchiveTableName).
- Whether the connector archives unsubscribed and unprocessed events (ArchiveProcessed). For subscription information specific to your
integration broker, refer to the broker's implementation guide.
- The unique ID of the connector, which is important when multiple
connectors poll the same table (ConnectorID).
You can also specify a value for the EventOrderBy property to specify the order of events to be
processed. For information on these and other configuration properties,
see Appendix A, Standard configuration properties for connectorsand Table 4.
- Note:
- Creation of the event and archive tables is optional. However, if you
specify a value for EventTableName but do not use the connector to
poll for events and do not create an event table, the connector times
out. To prevent such time-out, leave the value of
EventTableName as null (as a string).
By default, the name of the event queue table is xworlds_events,
and the name of the archive queue table is
xworlds_archive_events.
To use the connector only for request processing, use the -fno option when
starting it and set the value of EventTableName to null
(as a string).
If the driver being used does not support Java class
DatabaseMetaData, and you want the connector to avoid the checking
for the existence of event and archive tables, disable the
CheckForEventTableInInit by setting its value to false. By
default, it is true. It is recommended that the value not be
set to false.
- Note:
- If your site will not archive events into the archive table, set the value of
ArchiveProcessed to false.
