The application-specific component of the connector polls the
event table event view for events. If it finds an applicable event
(sometimes called a subscribed-to event), it retrieves information
about the event from the Domino server and builds an
application-specific business object. The connector populates the
business object with data obtained with an API call to the Domino
server. It then sends this business object through the connector
framework to the integration broker.
For incoming business objects (business objects sent to the
adapter from the integration broker), the connector receives a
business object from the integration broker, processes that
business object based on its active verb, and then sends a request
for operation to Lotus Domino.
The following sections explain how events that originate on the
Lotus Domino server are passed to the broker, and how requests from
another application are forwarded to the Lotus Domino server.
Events that occur on the Lotus Domino server are passed to the
integration broker as follows:
- At startup, the event listener reads the event table
configuration view to obtain the name of the database and determine
which events should be monitored.
- The event listener detects events from the database and filters
them according to information in the event table configuration
view. If the event is of a type listed in the event table
configuration view, the information about the event is
retained.
- The event listener stores information (key data) about the
event in the event table event view.
- The connector (application-specific component) polls the event
table event view to obtain key data about the event.
- The application-specific component of the connector uses the
event key data to retrieve all of the relevant event-related data
from the Domino server.
- The application-specific component of the connector creates a
business object and sends it to the connector framework, which then
sends it to the integration broker.
- If there is another application requesting Lotus Domino event
information from the broker, the broker passes the event
information to the other application. (Details of this process vary
depending upon which integration broker is being used. Refer to
your integration broker documentation for more information.)
Figure 1 shows how an event
is processed by the Lotus Domino adapter.
Figure 1. Event processing for Lotus Domino
adapter
For events originating from the integration broker:
- The broker sends a business object to the connector.
- The connector establishes a session with the Domino
server.
- An action occurs on the Lotus Domino server corresponding to
the request passed to it by the broker. (For example, if the
request is to update a field in a Notes document, the value is
updated in the Domino database.)
- The adapter sends the status of the requested action (whether
successful or whether a problem occurred) to the integration
broker, which sends it back to the requesting application.
Figure 2 shows how a
request is processed by the Lotus Domino adapter.
Figure 2. Request processing for Lotus
Domino adapter
