IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Lotus Domino > Overview of WebSphere Adapter for Lotus Domino > Technical overview > Inbound processing

Inbound extension manager

During inbound processing, WebSphere Adapter for Lotus Domino (WALD) inbound extension manager monitors the operations on the Lotus Domino server. Whenever you create, update, or delete a document from the Domino database, the inbound extension manager generates corresponding events containing the operation information.

The WALD inbound extension manager is a dynamic linked library that monitors the create, update, and delete events on the Lotus Domino server. The extension manager is deployed on the Lotus Domino server.

You configure the extension manager according to the operating system on which the Lotus Domino server is run. You require the waldinbound.nsf (event table and configuration table database) and the operating system-specific library files in the Domino database to configure the extension manager.

The WALD Inbound Event Table in the waldinbound.nsf database contains the configuration parameters for the inbound extension manager. The following views are available for configuring the inbound event table.

• ConfigurationView: The view was used to configure the inbound event table. This view is now deprecated.
• EventTriggerConfigurationView: This view is used to create or edit event trigger rules for a monitored Form.
• SystemConfigurationView: This view is used to edit the existing logging configuration of the inbound event table.

The adapter supports configuring of multiple documents with either the same or with different Connector IDs in the EventTriggerConfigurationView view.

Same Connector ID

The multiple documents with a same Connector ID are merged to create a single trigger rule. The following examples show the configuration for using a same Connector ID in two documents.

• Configuration document 1: Connector1; Create, Update; DB1a, DB1b
• Configuration document 2: Connector1; Create, Update; DB1a, DB1c

Here, Connector1 is the Connector ID, Create and Update are the event types, and DB1a, DB1b, and DB1c are the databases.

The following sample scenarios show the event logging behavior for a same Connector ID.

• When a document is created or updated in DB1a database, one event is logged for Connector1.

• When either a document is created in DB1b or DB1c database, only one event is logged for Connector1 because both the databases have the same Connector ID.

Different Connector IDs

The adapter supports multiple configuration documents in the Event Trigger Configuration view of Extension Manager. The following examples show the configuration for using different Connector IDs in two documents.

• Configuration document 1: Connector1; Create, Update; DB1a, DB1b
• Configuration document 2: Connector2; Create, Update; DB1a, DB1c

Here, Connector1 and Connector2 are the Connector IDs, Create and Update are the event types, and DB1a, DB1b, and DB1c are the databases.

The following sample scenarios show the event logging behavior for different Connector IDs.

• When a document is created or updated in DB1b database, one event is logged for Connector1.

• When a document is created or updated in DB1a database, two events are logged; one for Connector1 and the other for Connector2.

• When a document is created or updated in DB1c database, one event is logged for Connector2.

The dynamic linked library file monitors the create, update, and delete events in the event directory. The following table lists the dynamic linked library file required for the different operating systems.

Operating system-specific dynamic linked library file

Dynamic linked library file name	Operating system
waldinbound.dll	Windows
libwaldinbound_r.a	AIX
libwaldinbound.so	Linux
libwaldinbound.so	Solaris

Operating systems supported by WALD inbound extension manager

The extension manager libraries required to support 32-bit Lotus Domino server on specific operating systems are shown in Table 2.

WALD inbound extension manager libraries for 32-bit Domino on supported operating systems.

Lotus Domino server	Library directory after installation	Library file name
32-bit Domino on Microsoft Windows	dependencies/win32	waldinbound.dll
32-bit Domino on IBM AIX	dependencies/aix32	libwaldinbound_r.a
32-bit Domino on Novell SUSE Linux Enterprise Server	dependencies/suse32	libwaldinbound.so
32-bit Domino on Red Hat Enterprise Linux	dependencies/redhat32	libwaldinbound.so
32-bit Domino on Solaris Operating System	dependencies/solaris32	libwaldinbound.so

The current version of WALD inbound extension manager does not support the 64-bit Lotus Domino server.

For detailed information about the deployment and configuration information of the WALD inbound extension manager, see the topic Deployment and configuration of the WALD inbound extension manager. After you configure the inbound extension manager, see the topic View and verify the deployment of the WALD inbound extension manager to verify the extension manager configuration.

Inbound processing

Related reference:

Deployment and configuration of the WALD inbound extension manager

View and verify the deployment of the WALD inbound extension manager