2.3 Copying Ndsrep and Notes.jar to the Required Locations

After the Lotus Notes driver files are installed, you need to copy ndsrep (and its support files) to the Lotus Notes directory and copy the Lotus Notes JAR file to the driver directory.

For information about ndsrep, see Publisher Channel.

2.3.1 Windows Domino Server

  1. Manually copy the following files:

    Filename

    Copy from

    Copy to

    ndsrep.exe

    The installed location:

    \novell\NDS

    or

    \Novell\RemoteLoader

    The Domino Server executable folder:

    \Lotus\Domino

    dsrepcfg.ntf

    The installed location:

    \novell\NDS

    or

    \Novell\RemoteLoader

    The Domino Server data folder:

    \Lotus\Domino\Data

    Notes.jar

    The Domino Server executable folder:

    \Lotus\Domino

    The Remote Loader:

    \Novell\RemoteLoader\lib

    or

    The Metadirectory server (without a Remote Loader):

    \Novell\NDS\lib

  2. Make sure that the Domino shared libraries directory (for example, c:\lotus\domino) is in the Windows system path, and reboot the computer to make sure this step becomes effective.

    Without this directory in the Windows system path, the JVM might have difficulty locating the Domino shared libraries required by Notes.jar, such as nlsxbe.dll.

  3. If the Domino server requires databases to be signed, use a Notes client or Domino Administrator to sign dsrepcfg.ntf with your Domino server’s server ID.

2.3.2 Notes Client Workstation

  1. Manually copy the following files:

    Filename

    Copy from

    Copy to

    ndsrep.exe

    The installed location:

    \novell\NDS

    or

    \Novell\RemoteLoader

    The Domino Server executable folder:

    \Lotus\Domino

    dsrepcfg.ntf

    The installed location:

    \novell\NDS

    or

    \Novell\RemoteLoader

    The Domino Server data folder:

    \Lotus\Domino\Data

    Notes.jar

    The Notes Client workstation:

    \Lotus\Domino

    or

    \Lotus\Domino\jvm\lib\ext

    The Remote Loader:

    \Novell\RemoteLoader\lib

    or

    The Metadirectory server (without a Remote Loader):

    \Novell\NDS\lib

  2. Make sure that the Notes client library .dll directory (for example, c:\lotus\notes) is in the Windows system path, and reboot the computer to make sure this step becomes effective.

    Without this directory in the Windows system path, the JVM might have difficulty locating the Notes client libraries required by Notes.jar, such as nlsxbe.dll.

  3. Make sure the necessary user.id and cert.id files are available to the Notes Client and NotesDriverShim.jar so that the Notes driver can properly authenticate to the Domino server and register new Notes users.

2.3.3 Linux, AIX, or Solaris

  1. Make sure that the Notes.jar file is linked to the correct directory for your environment.

    If your Domino server is V7 or later, enter the following:

    ls -l /opt/novell/eDirectory/lib/dirxml/classes/Notes.jar

    The link should be something like the following:

    /opt/novell/eDirectory/lib/dirxml/classes/Notes.jar linked to /opt/ibm/lotus/notes/latest/linux/jvm/lib/ext/Notes.jar

    If your Domino server is prior to V7, the link should be something like the following:

    /opt/novell/eDirectory/lib/dirxml/classes/Notes.jar linked to /opt/lotus/notes/latest/linux/Notes.jar

  2. Use a Notes client or Domino Administrator to sign dsrepcfg.ntf with your Domino server’s server ID.

  3. Copy the following files from where they are installed (/opt/novell/eDirectory/lib/dirxml/rules) to the location where you intend to launch your driver on the Domino server, such as /local/notesdata. You might want this location to be in your execution search path. You might also need appropriate rights when copying these files to other directories.

    Filename

    Description

    rdxml.startnotes

    This script calls the findDomino script, which sets up appropriate Domino operating system environment variables for the Notes driver. Then the rdxml.startnotes script launches the Remote Loader with the Notes driver parameters specified in the rdxml.confignotes file.

    If the location where the scripts are placed is not in a current search path, you might need to do one of the following:

    • Modify rdxml.startnotes to include a specific path to the findDomino script.

    • Create a symbolic link for findDomino in /usr/bin.

    rdxml.stopnotes

    This script stops the Remote Loader that is running the Notes driver.

    findDomino

    This script is called from the rdxml.startnotes script. When you launch rdxml.startnotes, this script sets up operating system environment variables that indicate the location of a UNIX type of installation of Domino.

    rdxml.confignotes (or wherever your configuration is stored)

    This configuration is referenced by rdxml.startnotes and rdxml.stopnotes scripts.

    You might need to modify the rdxml.startnotes script to fit your environment. For example, if you change the name of the configuration file to a name other than rdxml.confignotes, you must revise the last line in the script.

    You might need to change the configuration ports that are referenced in this file.

    These three sample scripts and the sample configuration file are provided to demonstrate how to launch the driver. You can start the Remote Loader for the driver using rdxml.startnotes, and stop the Remote Loader for the driver using rdxml.stopnotes.

    The sample scripts work in a variety of situations. If they do not work in your environment, you might need to edit them appropriately. The sample scripts produce a Remote Loader trace log for the driver that can be used for troubleshooting.

  4. Modify the scripts and configuration file to fit to your environment, as described in the table in Step 3.

  5. Make sure that the three scripts noted in Step 3 have file access for execution (for example, rwxr-xr-x).

For troubleshooting tips, see Troubleshooting Installation Problems.