You must make the following modifications to the Domino server before you can run the adapter:
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.
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.
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.
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).
Configure these as follows:
In R5:
In R6:
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.
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. |
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
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
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.
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:
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:
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.
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.
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.