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 > Reference

Deployment and configuration of the WALD inbound extension manager

The adapter provides for deployment and configuration of the WALD inbound extension manager on the Lotus Domino server. When you deploy the extension manager, the adapter is able to monitor the create, update, and delete events in the Domino database.


Deployment of the inbound extension manager

You can deploy the inbound extension manager on Windows, AIX , Linux, and Solaris systems. After you deploy the required files, you can monitor the events in the specified databases in the Lotus Domino server.

The following steps describe how to deploy the required files for extension manager on the different operating systems.

  1. Copy the required library file into the Lotus Domino server installation directory. See Table 1 to know the operating system-specific library file name.

    Operating system-specific library file
    Library file name Supported operating systems
    waldinbound.dll Windows
    libwaldinbound_r.a AIX

    libwaldinbound.so

    Linux
    Solaris

  2. Edit the notes.ini file in your Domino directory and add the required line as given in Table 2.

    Add the extension manager line as per the operating system
    Extension manager lines Supported operating systems
    EXTMGR_ADDINS=waldinbound Windows
    EXTMGR_ADDINS=libwaldinbound_r.a AIX

    EXTMGR_ADDINS=libwaldinbound.so

    Linux
    Solaris

  3. Copy the waldinbound.nsf file into your Domino data directory.
  4. Restart the Lotus Domino server.

    You must restart the Lotus Domino server each time you update these files:

    • waldinbound.dll
    • libwaldinbound_r.a
    • libwaldinbound.so
    • waldinbound.nsf

  5. Click Configuration for WALD Inbound in the left pane to configure the databases that are to be monitored.

  6. Click EventView in the left pane to see the generated events.


Configuration of the inbound extension manager

You can configure the inbound extension manager by setting up different configuration parameters. The steps here describe the process of setting up the configuration parameters.

  1. Open the waldinbound.nsf database in the Lotus Domino server through Lotus If s .

  2. Click EventTriggerConfigurationView.

    You can create or edit an event trigger configuration view to configure a monitored Form.

    Figure 1. Editing the WALD inbound event trigger configuration

  3. Click Edit Document to edit the existing event trigger configuration of the WALD inbound extension manager. The parameters available for configuration are described in Table 3.

    The event trigger configuration overwrites the Connector ID, Database Paths, and Event Types fields of configuration document.

    Event trigger configuration parameters for WALD inbound extension manager
    Configuration parameter Description
    Connector ID The connector ID item that is used as the value of Connector ID field of the generated event.
    Database Paths The database paths and forms that are monitored by the WALD inbound extension manager. The semicolon ; is used as a separator between different configuration values. You can use either comma or semicolon as a separator to add another configuration value. The colon: is used as a separator between a database path and a form.

    For example, SampleDatabase.nsf:Employee;PlanDatabase.nsf implies that the form Employee in the database, SampleDatabase.nsf, and the whole database PlanDatabase.nsf are monitored.

    Event Types The event types that are monitored by the WALD inbound extension manager. The event types can be:

    • Create
    • Update
    • Delete

    You can configure the event monitoring by selecting the required events types.

  4. Click SystemConfigurationView to edit the existing logging configuration.

    Figure 2. Editing the WALD inbound logging configuration

  5. Click Edit Document to edit the existing system configuration of the WALD inbound extension manager. The parameters available for configuration are described in Table 4.

    The values set in the system configuration overwrite the Log Level field of configuration document.

    Log configuration parameters for WALD inbound extension manager
    Configuration parameter Description
    Log level The type of information that is logged during the WALD inbound processing. The log level can be:

    • NONE
    • ERROR
    • INFO
    • DEBUG

    Log outputs The targets where you can log the information. The log can be logged to the following targets:

    • Console
    • log.nsf

  6. Click ConfigurationView.

    When both event trigger configuration documents and configuration document are available, the adapter uses the event trigger configuration document to trigger the events.

    Figure 3. Editing the WALD inbound event configuration

  7. Click Edit Document to edit the existing configuration of the WALD inbound extension manager. The parameters available for configuration are described in Table 5.

    The configuration done using the ConfigurationView is a configuration document used only for WALD version 7.0. When either EventTriggerConfigurationView or SystemConfigurationView is configured, the existing configuration values of configuration document are overwritten.

    Configuration parameters for WALD inbound extension manager
    Configuration parameter Description
    Connector ID The connector ID item that is used as the value of Connector ID field of the generated event.
    Database Paths The database paths and forms that are monitored by the WALD inbound extension manager. The semicolon ; is used as a separator between different configuration values. You can use either comma or semicolon as a separator to add another configuration value. The colon: is used as a separator between a database path and a form.

    For example, SampleDatabase.nsf:Employee;PlanDatabase.nsf implies that the form Employee in the database, SampleDatabase.nsf and the whole database PlanDatabase.nsf are monitored.

    Event Types The event types that are monitored by the WALD inbound extension manager. The event types can be:

    • Create
    • Update
    • Delete

    You can configure the event monitoring by selecting the required events types.

    Log level The type of information that is logged during the WALD inbound processing. The log level can be:

    • NONE
    • ERROR
    • INFO
    • DEBUG

  8. Click Configuration for WALD Inbound to view all the configuration documents.

    The event trigger configuration and system configuration overwrite the configuration document of WALD version 7.0.

    Figure 4. Viewing the WALD inbound configuration tables

  9. Save the document. The configuration settings take effect immediately after you save the configuration document.

Reference


Related concepts:

Inbound extension manager


Related reference:

View and verify the deployment of the WALD inbound extension manager