Modifying the Domino server

You must make the following modifications to the Domino server before you can run the adapter:

  1. Configure the server to run the Domino Internet Interoperability Protocol (IIOP) and HTTP server (for Web Applications), and configure the server to allow remote calls from an application. These changes are made with the Domino Administrator.
  2. Modify the NOTES.INI file on the Domino server.
  3. Copy the event table and associated files and the event listener to the required directories on the Domino server.
  4. Configure the event table.
  5. Make the NCSO.jar file accessible to the adapter.

Configuring changes with Domino Administrator

The Domino server must be configured to accept remote calls from an application for the adapter to operate. Configuration is done with the Domino Administrator (refer to your Lotus Domino administration documentation for details). The following sections describe what must be configured. Make sure that the server is restarted after these changes are made so that they will take effect.

HTTP

The HTTP server (for Web Applications) must be enabled on the Domino server. Refer to your Lotus Domino administration documentation for more information on how to set this up.

IIOP

The Domino Internet Interoperability Protocol (IIOP, sometimes called DIIOP) must be enabled. Make sure that a TCP/IP port number is configured and enabled for IIOP.

Java/COM

You must configure the username that is configured for the adapter, as well as the username(s) that will be specified in any incoming business objects, (if applicable) to run restricted and unrestricted Java agents (and methods, for R6).

Note:
The user name configured for the adapter is the value for ApplicationUserName as configured with Connector Configurator. Refer to Application-specific configuration properties for more information.

Configure these as follows:

In R5:

  1. Select the Security tab.
  2. In the Java/COM Restrictions section, in the "Who can -" column under both "Run unrestricted Java/Javascript/COM" and "Run restricted Java/Javascript/COM," enter the ApplicationUserName that is configured in the Connector Configurator file, as well as the username(s) that will be specified in any incoming business objects, if applicable.

In R6:

  1. Select the Security tab.
  2. In the Programmability Restrictions section, in the "Who can -" column, enter the ApplicationUserName that is configured in the Connector Configurator file, as well as the username(s) that will be specified in any incoming business objects, if applicable, for the following item:

Modifying NOTES.INI

Add one of the following lines to the NOTES.INI file on the Domino server, depending on the operating system:

On Windows: EXTMGR_ADDINS=nbiald.dll

On AIX: EXTMGR_ADDINS=libbiald.a

On Solaris: EXTMGR_ADDINS=libbiald.so

This enables the Domino server to call the event listener at startup.

Note:
The event listener is a Domino Extension Manager library; therefore, the line should be entered on the same line in the NOTES.INI file as any other Domino Extension Manager libraries, separated from other entries by commas.

Copying files to the Domino server

You must copy the event table files and the event listener from the ProductDir/connectors/Domino/dependencies directory on the adapter host computer to the required directories on the Domino server. The following table lists the files and where they must be copied:

Table 2. Files to copy into Domino server directories
Directory to copy to File Description
Domino data directory
BIALD_EventTable.nsf
Event table
Domino data directory
BIALD_emptytrash.gif
BIALD_movetotrash.gif
BIALD_newconfig.gif

Event table bitmaps
(appear if event table is
viewed through
Lotus Notes Client).
Copy one of the following:
Domino server root libbiald.a
Event listener for AIX
systems. Copy this only if
your Domino server runs
on AIX.
Domino server root libbiald.so
Event listener for Solaris
systems. Copy this only if
your Domino server runs
on Solaris.
Domino server root nbiald.dll
Event listener for Windows
systems. Copy this only if
your Domino server runs
on Windows.

Copying event table files

Copy the following files from their installation directory to the Domino data directory. (On Windows, the default for this data directory is c:\Lotus\Domino\Data; on UNIX there is no default so the directory name will vary.)

BIALD_EventTable.nsf

BIALD_emptytrash.gif

BIALD_movetotrash.gif

BIALD_newconfig.gif

Copying the event listener

Copy the event listener from the installation directory (ProductDir/connectors/Domino/dependencies) to the Domino server root directory.

This will be one of the following files, depending on the operating system on which the Domino server will be run:

For AIX systems: libbiald.a

For Solaris systems: libbiald.so

For Windows systems: nbiald.dll

Note:
The event listener is not supported on the Linux Domino server.

Typically, the root directory to which you will install is as follows, depending on your operating system: /opt/lotus/notes/latest/ibmpow for AIX, /opt/lotus/notes/latest/sunspa for Solaris, and c:\lotus\domino for Windows.

Configuring the event table

To allow the adapter's event listener to monitor events that occur on the Domino server, you must configure the adapter's event table. The event table is a Lotus Domino database file which you can open from a Lotus Notes client.

To configure the event table:

  1. From a Lotus Notes client, select File > Database > Open and select the Domino server name to be supported by this adapter.
  2. Select the BIALD_EventTable database. If it does not appear in the list, enter or browse for BIALD_EventTable.nsf in the Filename field. The window should appear similar to the following:
    Shows Open Database field with targeted database selected.
  3. Click Open. The following window is displayed:
    Shows window with Event Table views (EventArchiveView, EventConfiguration View, and EventTableView displayed in left panel; EventConfigurationView selected. Related buttons to select across top of window are Empty Trash, Move to Trash, and New Configuration
  4. Select EventConfigurationView from the navigation view in the left panel.
  5. Select New Configuration from the menu bar. The following table will appear:
    Shows WebSphere Business Integration Adapter for Lotus Domino Configuration Table. Left column is "Event Info," right column is "Value." Under Event Info there are two rows, each with a label: Database Path and below it Event Type. Enter the Database path in the right column in the first row;  using checkbox, select whether to Create, Delete or Update event s(in that order) from the second row.
  6. In the Database Path field, enter the path of the database that you want the adapter to monitor. The path should be relative to your Domino server root directory/Data. For example, if the database is called Buyer and the path is Domino server root/Data/BusApp/Buyer.nsf, enter BusApp/Buyer in the Database Path field.
  7. In the Event Type row, select the verb types or verb type combination that will enable the adapter to monitor the desired event types, as follows:
    For the adapter to monitor: Select:
    Create events Create and Update
    Delete events Delete
    Update events Update
    For example, the following selections enable the adapter to monitor create, update and delete events:
    Shows WebSphere Business Integration Adapter for Lotus Domino Configuration Table with Create, Delete, and Update all selected.
    Note:
    It is not possible for the adapter to monitor Create events without also monitoring Update events. For monitoring Create events you must select Create and Update as shown in the following example:
    Shows WebSphere Business Integration Adapter for Lotus Domino Configuration Table with Create and Update selected. These settings both required for monitoring Create events.
  8. Select File > Save to save the configuration, then close the event table database.

Making NCSO.jar accessible

The file NCSO.jar is part of the Lotus Domino Toolkit for Java/CORBA, which should have come with your Lotus Domino server. (The file should be available on the Domino server and on Notes clients.) NCSO.jar contains the Lotus Domino API (known as Domino Objects for Java). You must update the adapter startup script to point to this file.

Location of NCSO.jar

Typically, NSCO.jar resides in the following directory on the Domino server:

DirectoryName\Data\domino\java

where DirectoryName is the name of the Domino server directory or the Notes client directory.

Note:
For UNIX, substitute slashes (/) for backslashes in the pathname shown above.

Modifying the startup script

Change the following line in the adapter startup script to point to NCSO.jar.

On UNIX: Change

DOMINOJAVACLASSES=/server1/domino/java CON_SPEC_JAR_ONE=${DOMINOJAVACLASSES}/NCSO.jar

to

DOMINOJAVACLASSES=directoryname CON_SPEC_JAR_ONE=${DOMINOJAVACLASSES}/NCSO.jar

where

directoryname is the name of the directory containing NCSO.jar.

On Windows: Change

set DOMINOCLASSES=C:\Notes\Data\domino\java\NCSO.jar

to

set DOMINOCLASSES=directoryname\NCSO.jar

where

directoryname is the name of the directory containing NCSO.jar.

Copyright IBM Corporation 1997, 2004. All Rights Reserved.