Installing the Lotus Domino server

To enable your users to export Lotus Notes® content or to view content by using Lotus Notes, you must install the Lotus® Domino® server on the IBM® eDiscovery Manager system. eDiscovery Manager requires only the Lotus Domino APIs, but these APIs are bundled with the Lotus Domino server; the APIs are not bundled separately. For this reason, you must install a Lotus Domino server on the eDiscovery Manager system or logical partition (LPAR), even though you do not start the server itself.

1. Install the Lotus Domino server on the eDiscovery Manager system. If you are installing Lotus Domino Version 8, you can find more information in the Guidepost for deploying Domino topic.

   You do not need to configure this local Lotus Domino server if you are installing it only for the purpose of obtaining the Lotus Domino APIs, as recommended.

2. Verify that the Lotus Domino installation directory was added to the PATH system environment variable, for example, C:\Program Files\IBM\Lotus\Domino.
3. Log out and log back in to the eDiscovery Manager system as the root user to check the I/O completion port (IOCP):
   1. Enter the following command to ensure that the IOCP module is installed on the eDiscovery Manager system:

      $lslpp -l bos.iocp.rte

      The output from the lslpp command should be similar to the following example:

      Fileset					Level				State			Description
      -----------------------------------------------------
      Path: /usr/lib/objrepos			5.2.0.10		COMMITTED	I/O Completion Ports API
      bos.iocp.rte
      Path: /etc/objrepos			5.2.0.10		COMMITTED	I/O Completion Ports API
      bos.iocp.rte

   2. If the IOCP module (bos.iocp.rte) is not installed, install it from the AIX product CD, then enter the lslpp -l bos.iocp.rte command again to confirm that it is installed.
   3. Enter the following command to ensure that the status of the IOCP port is Available:

      $ lsdev -Cc iocp

      The output from the lsdev command should be similar to the following example:

      iocp0 Available I/O Completion Ports

   4. If the IOCP port status is Defined, change the status to Available:
      1. Enter the following command:

         # smit iocp

      2. Select Change / Show Characteristics of I/O Completion Ports and change STATE to be configured at system restart from Defined to Available.
      3. Reboot the eDiscovery Manager system and log in as the root user.
      4. Enter the lsdev -Cc iocp command again to confirm that the status of the IOCP port changed to Available.
4. Set up the environment for the AIX non-root user ID that starts the eDiscovery Manager application server.
   You created this user ID as a prerequisite.
   1. Log out of the eDiscovery Manager system and log back in by using the user ID that starts the eDiscovery Manager application server.
   2. In the $HOME directory, create a notesdata subdirectory.
   3. Copy the Lotus Notes user ID file for the user ID that starts the eDiscovery Manager application server from the remote Lotus Domino server to the $HOME/notesdata subdirectory on the eDiscovery Manager system.

      You created this user ID as a prerequisite. eDiscovery Manager uses this ID file to connect to the remote Lotus Domino server, create databases, and export Lotus Notes content.

   4. Create a notes.ini file in the $HOME/notesdata subdirectory that contains the following lines, as well as a blank line at the end of the file:

      [Notes]
      Directory=$HOME/notesdata
      KeyFileName=Lotus_Notes_user_ID_for_eDM_appServer_starter.id
      Ports=TCPIP
      TCPIP=TCP,0,15,0

      Important: If the Lotus Domino installation directory already contains a notes.ini file, then the notesConnect utility will always use it. This is true even if the notes.ini file that you created when installing the Lotus Domino server is first in the system path. For this reason, it is necessary to rename the notes.ini file in the Lotus Domino installation directory, if one exists.
   5. Edit the .profile file for the user ID that starts the eDiscovery Manager application server.

      Remember that the .profile file for this user ID exists in the $HOME/AIX_non_root_user_ID subdirectory.

      Add the following lines to the .profile file:

      # LIBPATH: Add the path to the ibmpow directory in the Lotus Domino 
      # installation directory:
      LIBPATH=$LIBPATH:/opt/ibm/lotus64/lotus/notes/latest/ibmpow
      
      # PATH: Add the paths to the notesdata directory, 
      # ibmpow and bin directories in the Lotus Domino installation directory,
      # and resource subdirectory of the Lotus Domino installation directory.
      # For example, in English locales, the path of the resource subdirectory is
      # /opt/ibm/lotus/notes/latest/ibmpow/res/C
      PATH=$PATH:$HOME/notesdata:/opt/ibm/lotus/notes/latest/ibmpow:
         /opt/ibm/lotus/bin:/opt/ibm/lotus/notes/latest/ibmpow/res/C
      
      Notes_ExecDirectory=/opt/ibm/lotus/notes/latest/ibmpow
      
      LOTUS=/opt/ibm/lotus
      
      NOTES_DATA_DIR=$HOME/notesdata
      
      export LIBPATH PATH Notes_ExecDirectory LOTUS NOTES_DATA_DIR

   6. Copy the names.nsf file from the data directory ($HOME/notesdata) of the Lotus Domino server (typically a remote server) to the $HOME/notesdata directory on the eDiscovery Manager system.
   7. Log out of the eDiscovery Manager system and log back in by using the user ID that starts the eDiscovery Manager application server.

      The changes that you made to the .profile file for this user ID are now in effect. You can run the env command to verify the changes.

5. Set up the environment for the user ID that starts the eDiscovery Manager application server.
   1. Create a notesdata directory in a convenient location of your choice, for example \your_dir\notesdata.
   2. Copy into the notesdata directory the names.nsf file from the Lotus Domino server that your eDiscovery Manager server will connect to for viewing and exporting Lotus Notes content, typically a remote Lotus Domino server.
   3. Create a new user ID on the Lotus Domino server, for example, eDMNotesUser.
      Make sure that this user has read and write access to the eDMMail.nsf database, which is used for viewing Lotus Notes content. This database is created at the Lotus Domino Settings pane of the Administration page in the eDiscovery Manager web client. Also make sure that this user has the ability to create new databases on the Lotus Domino server.
   4. An ID file is created for this new user ID. Copy this ID file (for example, eDMNotesUser.id) into the \your_dir\notesdata directory that you just created.
   5. In the \your_dir\notesdata directory create a new file called notes.ini with the following contents:

      [Notes]
      Directory=\your_dir\notesdata
      KeyFileName=Notes_user_ID_for_eDM.id
      Ports=TCPIP
      TCPIP=TCP,0,15,0

      Substitute \your_dir with the absolute path to your notesdata directory and Notes_user_ID_for_eDM.id with the new Lotus Notes user ID you created (for example, eDMNotesUser.id).
   6. Edit the system Path environment variable so that the \your_dir\notesdata directory is the first directory listed and that the notes.ini file is picked from this location.
6. Rename the notes.ini file in the Lotus Domino installation directory, if it exists.
7. Verify that the environment for the ID that starts the eDiscovery Manager application server is working by running the eDiscovery Manager notesConnect utility.
   Remember that on AIX systems this ID is a non-root user.

   The notesConnect utility connects to the remote Lotus Domino server and returns the title from the names database. Run the notesConnect utility on a single line from the bin subdirectory of the eDiscovery Manager installation directory. For example:

   AIX

   /opt/IBM/eDM/bin/notesConnect names.nsf [remote_Lotus_Domino_server]

   Windows

   C:\Program Files\IBM\eDM\bin\notesConnect names.nsf
    [remote_Lotus_Domino_server]

   where remote_Lotus_Domino_server is the IP address or IP name of the remote Lotus Domino server.

   The notesConnect utility uses the Lotus Notes user ID that is configured for the KeyFileName setting in the $HOME/notesdata/notes.ini file if on AIX or in the \your_dir\notesdata\notes.ini file if on Windows.

   If the environment is configured properly, the title of the names database is returned. You might be prompted for a password.