Connector Guides › Connectors Guide › Connecting to Endpoints › Lotus Domino Connector › LND Installation › LND Java Implementation Considerations

LND Java Implementation Considerations

The Java version of the LND Connector (installed with JCS) provides the same functionality as the previous (eTrust Admin r8.1) C++ version of the LND Connector with the added benefit of DJX support, but there are a few things to consider when switching from the C++ version.

• To add the Java LND connector to an existing system:
  1. Run the Provisioning Server install to reconfigure and add the LND connector.
  2. Run Java CS installer and select Register with the Provisioning Server.

     Doing this routes requests from the Provisioning Server to JCS for the LND endpoint type. See "Install the LND Connector" for more information.

• For this release it is no longer required to have Lotus Notes Client software installed, or a Notes.ini file available on the computer where the Provisioning Manager is running. The same is true for the computer where Java CS hosting the LND connector is run.
• Connector operation, as well as migration requires the Lotus Notes Domino remote Corba interface jar (NCSO.jar) to be copied to

  <jcs-home>/extlib/ 
  

  from the server installation directory

  (Windows) <lotus-home>\Data\domino\java

  (UNIX) /local/notesdata/domino/java

  and im_jcs restarted.

• If existing Regarc and Regcert databases are used, these encryption Keys must be imported from the Admin ID used previously, to the Server ID, or all documents in the database created using the old encryption keys will show an error.
• ID file paths should be specified local to the endpoint or use a UNC style path.
• Organization names and organizational unit names no longer appear prefixed by "O:" and "OU:".
• There are new choices for mail systems that correspond to the available choices in Domino R6 and R7
  • Lotus Notes
  • POP
  • IMAP
  • Domino Web Access
  • Other Internet
  • Other
  • None
• The mapping information for the custom attributes is now contained in

  <jcs-home>/conf/override/lnd/lnd_custom_metatdata.xml 
  

  Two sample files with the prefix of "SAMPLE" are provided including one covering DJX mappings. the override connector.xml file of the Java LND Connector. For existing LND endpoints, the credential information currently stored in the registry is no longer required.

• The following settings must be made to the Domino server's notes.ini file:
  • $Reg_TempDir variable representing the temp directory on the Domino server, must be added to the notes.ini file. If you add or change the variable, the Domino server must be restarted.

    Note: The directory specified must already exist. The LND Connector will not create the directory. An example of this setting:

    (Windows) $Reg_TempDir=c:\lotus\domino\data\temp

    (Windows) $Reg_TempDir=\\user01w2k3\c$\lotus\domino\data\temp

    (UNIX) $Reg_TempDir=/local/notesdata/temp

    The value is necessary for the temporary placement of ID files during ID password changes. For ID password changes to be successful, the ID must be located on the server at the time of the change. The value is also necessary for the temporary placement of ID files during account and certifier creation if another location is not specified for the ID.

• Two new fields are required when acquiring an LND Endpoint:
  • DIIOP Port

    The LND connector uses the remote access support provided in the Lotus Domino Toolkit for Java/CORBA 2.1 to communicate with the endpoint.

  • Use SSL/TLS
• The connector is now case insensitive. Objects existence is checked ignoring case. If duplicate objects already exist during an explore operation, only one is managed (silently) by the Provisioning Manager.
• If connection to the endpoint is temporarily lost, the default retry settings of six retries 10 seconds apart are enforced. As for all Java CS connectors, these settings can be adjusted using the exceptionRetryMap settings in the connector.xml file located in:

  <jcs-home>/conf/override/lnd/.
  

• Search results are streamed so the connector passes search results on to the Provisioning Server immediately rather than buffering all results before passing any on. This keeps the memory usage of the Connector Server to a minimum, regardless of the number of objects in an LND endpoint.
• Custom delete of an account in a secondary directory is not supported by the Administration Process (adminp) JAVA API used by the connector so the connector explicitly deletes only the person document itself. You must manually clean up any references to the person's name in group members/ACL's and so forth, where they exist.

  Note: Account operations are not supported on accounts that are in a secondary directory and require the intervention or spawning of requests from the Domino administration process ‘adminp’.