Event notification

Event Notification in the connector is handled through the adapter-delivered Gateway Server. An event is triggered when a task is initiated in "Waiting" status. The MetaSolv Client sends the event to the Gateway Server or the PSR Billing Gateway Server depending on the type of event. The Gateway Server reads the event details from the Event Notification object and places the event in the business-integration system's event table. This table can be created in any Oracle database.

Gateway server

Gateway Servers are responsible for extracting event information from the MetaSolv Client event notification and creating an event in the event table. There are two adapter-delivered Gateway Servers:

These servers should run on the same machine as the MetaSolv Application Server is running.

An event is triggered when a MetaSolv task gets initiated. The MetaSolv Client then sends the Service Request and/or Customer Gateway Event to the appropriate Gateway Server. When the event is successfully populated in the event table, a status of completed is returned to the MetaSolv Client via the MetaSolv Application Server.

If the event does not get populated, a status of error is be returned to the MetaSolv Client. If the error is related to the WebSphere business-integration system's database, a notification e-mail is sent. The e-mail address must be specified as a parameter in the CwGatewayServer.bat and CwPSRBillingGatewayServer.bat files.

If the MetaSolv Application Server is down, the status of the gateway events is Waiting until the MetaSolv Application Server is brought up.

The MetaSolv Client must be restarted Whenever the Gateway Servers are restarted. MetaSolv Client gets a handle to the Gateway Server when it first sends the Gateway event. When a Gateway Server is restarted, the old handle is no longer valid.

Note:
Any change to the WebSphere business-integration system's event table definition affect the Gateway servers.

Processing application events

Event retrieval

The connector polls the event table at configurable intervals. The connector picks up all unprocessed events in the event table, processes them, and then archives them. The number of events a connector can process at any time is determined by the PollQuantity connector property. The connector builds a query to extract events from the event table.

Each time the connector is started, it updates the InProgress events to ReadyForPoll and sets their priority to 0. This ensures that the status is updated for InProgress events in case the connector is abnormally shut down.

Create notification

When the connector encounters a Create event in the event table, it instantiates an object of the type specified by the event, sets the doc number for the object, and retrieves it through the MetaSolv Application Server APIs. When it is retrieved, the object is sent to the integration broker.

Update notification

When the connector encounters an Update event in the event table, it instantiates an object of the specified type, sets the doc number for the object, and retrieves it by using the MetaSolv APIs. When it is retrieved, the object is sent to the integration broker.

Archiving

When an event is deleted from the event table it is placed in the archive table. The archive table provides a means of recovering events that are not successfully processed, and a history of events that can be used to audit event processing.

To enable archiving, the ArchiveProcessed must be set to true. If the ArchiveProcessed property is set to false:

The ArchiveProcessed property defines whether unsubscribed or unprocessed events are archived. The archive table is specified through the configuration property ArchiveTableName.

Copyright IBM Corp. 1997, 2003