Connector for Lotus Notes Architecture

  • Article

 

Connector for Lotus Notes can connect an Exchange organization to a Lotus Notes and Lotus Domino network. Lotus Notes releases 3 and 4 and Lotus Domino releases 4.5, 4.6, 5, and 6 are supported with Exchange Server 2003 Service Pack 1 (SP1). This MAPI-based connector uses the Lotus Notes Client API to communicate with a Lotus Notes or Lotus Domino server. This requires a Lotus Notes client on the connector server. A license from Lotus Development is required to use the client software. For information about how to install and configure Connector for Lotus Notes, see the Exchange Server 2003 Interoperability and Migration Guide.

Note

Because Connector for Lotus Notes uses the Lotus Notes Client API to communicate with a Lotus Notes or Lotus Domino server, the connector requires a dedicated Notes ID that has permissions to access Lotus Notes databases.

The following table lists the important components of Connector for Lotus Notes.

Connector for Lotus Notes components

Component Description

Connector mailbox

As a MAPI-based connector, Connector for Lotus Notes locates its message queues in a connector mailbox in the default mailbox store on the bridgehead server. The mailbox name is Connector for Lotus Notes (<server name>), such as Connector for Lotus Notes (SERVER01).

Connector service

The main executable of the Connector for Lotus Notes service is called Dispatch.exe. This is a process controller that is started using the parameters -cexchconn.ini -nLME-NOTES -pCONTROL-SERVICE -l"C:\Program Files\Exchsrvr\bin" -vLME-NOTES to dispatch the various tasks of message transfer and directory synchronization to other processes, based on the settings from an Exchconn.ini file. Exchconn.ini is created automatically, as part of the connector installation and configuration.

The following components are involved in information handling:

  • Dxanotes.dll   This component checks the Lotus Domino Directory for recipient updates. This component also transfers Exchange address information changes to the Lotus Domino/Notes address book.

  • Dxamex.dll   This component checks Active Directory for recipient updates. This component also transfers Lotus Domino/Notes address information changes to Active Directory.

  • Lsdxa.exe   This is the directory exchange manager that controls both Dxanotes.dll and Dxamex.dll.

  • Lsmexin.exe   This component obtains converted messages from the READYIN folder in the connector mailbox, verifies the validity of the recipients, and places the messages in the MTS-IN queue.

  • Lsmexnts.exe   This component obtains messages from the READYOUT folder in the connector mailbox, converts them from MAPI to Lotus Notes format, and writes them to the mail.box database on the Domino server.

  • Lsmexout.exe   This component obtains outbound messages from the MTS-OUT queue, checks Active Directory to replace target recipient information with corresponding Lotus Notes addresses, and places the messages in the READYOUT folder in the connector mailbox.

  • Lsntsmex.exe   This component downloads messages from the Lotus Notes exchange.box database, converts them to MAPI format, and places them into the READYIN folder in the connector mailbox.

In addition to the processes, Connector for Lotus Notes also includes a Microsoft Exchange Connectivity Controller helper service (Lscntrl.exe), which can be used to stop the individual connector processes.

All files reside in the \Program Files\Exchsrvr\Bin directory.

Lotus Notes databases

Connector for Lotus Notes uses the following databases on the Lotus Notes and Domino bridgehead server:

  • Exchange.box   This is the connector mailbox in Lotus Notes and Domino that stores messages being routed from Lotus Domino to Exchange. You must create a foreign domain document to register the Exchange organization as an external domain in the Lotus Domino Directory and specify the name of the connector mailbox in this document. All mail routed from Lotus Domino to Exchange Server 2003 is then sent to the connector mailbox, from which it is retrieved by Connector for Lotus Notes. The connector needs Manager permissions with Delete rights to pick up mail from this database and to run database maintenance operations.

  • Exchange.bad   This is the connector mailbox for badmail that Connector for Lotus Notes uses to store any messages that fail to transfer to Exchange Server 2003. The connector needs Manager permissions with Delete rights to move badmail to this database and to run database maintenance operations.

  • Mail.box   This is the server mailbox of the Lotus Domino server. Connector for Lotus Notes uses this mailbox to deposit all messages from Exchange Server 2003 that are bound for Lotus Domino mailboxes. The connector needs Depositor permissions to drop mail messages and to perform database maintenance operations.

  • Names.nsf   This is the default Lotus Domino directory file that Connector for Lotus Notes uses for directory synchronization. It is possible to specify different or additional address books for Lotus Domino domains. The connector needs Editor permissions with Delete rights to perform directory synchronization.

In addition, Connector for Lotus Notes might require Reader access to regular Lotus Notes databases to convert Notes doclinks to rich-text attachments or OLE documents.

Connector store

Connector for Lotus Notes uses a folder structure on the file system to maintain control files used during directory synchronization. Control files are schema definition files and mapping rule files, which determine how attributes in one directory are mapped to the other directory. The connector store is located in the \Program Files\Exchrvr\Conndata directory.

You can edit the following schema definition files and mapping rule files in Notepad to determine how attributes in one directory are mapped to the other directory:

  • AMAP.TBL in the \Dxamex subdirectory   Defines the Exchange mailbox attributes to be synchronized.

  • AMAP.TBL in the \Dxanotes subdirectory   Defines the Lotus Notes attributes to be synchronized.

  • MAPMEX.TBL in the \Dxanotes subdirectory   Determines the attribute mapping from Exchange Server 2003 to Lotus Notes.

  • MAPNOTES.TBL in the \Dxamex subdirectory   Determines the attribute mapping from Lotus Notes to Exchange Server 2003.

For detailed information about customizing the directory synchronization between Lotus Domino and Exchange Server 2003, see Microsoft Knowledge Base article 180517, "XFOR: Customizing Directory Synchronization Between Exchange and Notes."

Registry settings

In the Registry, settings for Connector for Lotus Notes are stored in the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LME-NOTES.

Proxy address generation DLL

The proxy address generation DLL of Connector for Lotus Notes is named Ntspxgen.dll and resides in the \Program Files\Exchsrvr\address\notes\i386 directory.

addrType object

The common name of the addrType object of Connector for Lotus Notes in Active Directory is NOTES:i386.

msExchConnector object

The msExchConnector object of Connector for Lotus Notes in the configuration directory partition of Active Directory stores most of the connector configuration settings. The following attributes are specific to the msExchNotesConnector object class that is derived from the msExchConnector and mailGateway object classes:

  • exportCustomRecipients   Specifies whether mail-enabled contacts are propagated to Lotus Notes through directory synchronization.

  • msExchServer1AlwaysCreateAs   Specifies how X.500 objects are synchronized.

  • msExchDeliveryOrder   Specifies the processing order of messages in the connector's queue. The options are FIFO, Priority (default), and Size.

  • msExchExportDLs   Specifies whether mail-enabled distribution groups are propagated to Lotus Notes through directory synchronization.

  • msExchPartnerLanguage   Specifies the language (code page) of the connected Lotus Notes and Domino server.

  • msExchDirsyncSchedule   Specifies the times at which directory synchronization is performed automatically.

  • msExchDirsyncStyle   Specifies whether full or incremental directory synchronization is performed.

  • msExchNotesNotesServer   Specifies the name of the Lotus Notes and Domino server (in Notes format) that the connector uses as the non-Exchange bridgehead server.

  • msExchNotesForeignDomain   Specifies the name of the Lotus Notes non-Exchange domain that represents the Exchange organization.

  • msExchNotesRtrMailbox   Specifies the name of the Lotus Notes and Domino server mailbox that is used by the Lotus Notes mail router where Connector for Lotus Notes places outbound messages to Lotus Notes. This is usually mail.box.

  • msExchNotesConnectorMailbox   Specifies the name of the Lotus Notes mailbox where Connector for Lotus Notes retrieves from Lotus Notes for delivery to Exchange. This is usually exchange.box.

  • msExchNotesLetterhead   Specifies the name of the Lotus Notes letterhead style used for messages delivered from Exchange to Lotus Notes. The default is plain text.

  • msExchNotesNotesLinks   Specifies how Lotus Notes doclinks are converted in messages to Exchange. The options are RTF, OLE, or URL. The default is RTF.

  • msExchNotesNotesINI   Specifies the full path and file name of the Lotus Notes client .ini file that is used by the connector to log on to the Lotus Notes and Domino server.

  • msExchNotesTargetBook   Specifies the name of the default Lotus Notes Name and Address Book to which Exchange users are imported.

  • msExchNotesSourceBooks   Specifies the list of the Lotus Notes Name and Address Books exported to Exchange for directory synchronization.

  • msExchNotesExportGroups   Specifies whether Lotus Notes groups are exported to Exchange during directory synchronization. The default is TRUE.

  • msExchNotesExcludeGroups   Specifies a list of Lotus Notes groups to exclude from directory synchronization. The default is OtherDomainServers and LocalDomainServers.

  • msExchExportContainersLinked   Specifies the distinguished names of the organizational units in Active Directory that Connector for Lotus Notes uses as export containers for directory synchronization.

  • msExchImportContainerLinked   Specifies the distinguished name of the organizational unit in Active Directory that Connector for Lotus Notes uses as the import container for directory synchronization.

  • msExchMaintenanceStyle   Specifies the maintenance style for this connector.

  • msExchConnectorType   Specifies the type of Exchange connector. The value is NOTES.

Administrative snap-in

The extension snap-in for Connector for Lotus Notes is named Exchange Notes Connector. This snap-in extends the node for the connector, which you can find in Exchange System Manager, under <Organization Name>/Administrative Groups/<Administrative Group Name>/Routing Groups/<Routing Group Name>/Connectors.

Message Transfer

The following figure illustrates the process for sending messages from Exchange Server 2003 to Lotus Domino.

Sending messages from Exchange Server 2003 to Lotus Domino

10ef053b-5a91-46b6-8eda-d862c90d0537

The process for message transfer between Exchange Server 2003 and Lotus Domino is made up of the following three steps:

  1. Exchange 2003 determines that the recipient is a Lotus Domino user (based on the target address of the user) and sends the message to the message transfer agent (MTA).

  2. The MTA delivers the message to the MTS-OUT directory, from which the LSMEXOUT process retrieves it, converts the address from an X.400-based address to a Lotus Domino address, and then delivers it to the READYOUT directory.

  3. The LSMEXNTS process converts the message to Lotus Domino format and delivers it for routing to the mail.box file on the Lotus Domino server.

The following figure illustrates the process for sending messages from Lotus Domino to Exchange Server 2003.

Sending messages from Lotus Domino to Exchange Server 2003

42e00ea4-4184-4c77-905a-25c13f08d4e1

The process for message transfer between Lotus Domino and Exchange Server 2003 is made up of the following three steps:

  1. Lotus Domino receives a message sent to an Exchange Server 2003 user from a Lotus Notes user and places it in the mail router's mail.box database. The mail router identifies the message sent to Exchange Server 2003 and then deposits it in the exchange.box file.

  2. Connector for Lotus Notes retrieves the message from the exchange.box database, converts the message to Exchange Server 2003 format using the LSNTSMEX process, and then delivers it to the READYIN folder on the server running Exchange Server 2003.

  3. The LSMEXIN process receives the message, converts the address from a Lotus Domino address to an X.400 address, and places it in the MTS-IN folder. The Exchange MTA then processes the message from the MTS-IN folder and places it in the Simple Mail Transfer Protocol (SMTP) service's MTS-OUT folder, from which it is then routed.

Message Conversion

Exchange Server 2003 and Lotus Domino support several message types, including meeting requests, tasks, task requests, and e-mail. Connector for Lotus Notes supports the mapping of different message types between Exchange Server 2003 and Lotus Domino. However, the conversion from one format to another might cause some changes in message characteristics. For example, certain features of a Lotus Domino message, such as the expiration date, are lost when the message is converted to the Exchange format. Messages that cannot be mapped to a corresponding message type in the target domain are converted to e-mail messages.

Note

Connector for Lotus Notes is not designed to convert HTML-formatted messages. If you plan to route messages in HTML format between Exchange Server 2003 and Lotus Notes (for example, because you want to route all messages to and from Internet recipients through Exchange Server 2003), consider deploying an SMTP connector instead of Connector for Lotus Notes.

The following table illustrates how different message types are converted between Exchange Server 2003 and Lotus Domino.

Message conversion between Lotus Domino and Exchange Server 2003

Exchange Server 2003 feature Lotus Domino feature Lotus Domino to Exchange Server 2003 Exchange Server 2003 to Lotus Domino

E-mail messages

E-mail messages

Yes

Yes

E-mail delivered receipt

E-mail delivered receipt

Yes

Yes

E-mail read receipt

E-mail read receipt

Yes

Yes

Non-delivery report

Non-delivery report

Yes

Yes

Importance

Importance

Yes

Yes

Voting buttons

No feature

No

No

Embedded OLE object

Embedded OLE object

Yes

Yes

Embedded file attachment

Embedded file attachment

Yes

Yes

Message expiry date

Message expiry date

No

No

No feature

Reply By

No

No

Web URL

Web URL

Yes

Yes

No feature

URL hotspot

No

No

Meeting requests

Appointments

Yes

Yes

Meeting accepted

Meeting accepted

Yes

Yes

Meeting declined

Meeting declined

Yes

Yes

Meeting tentatively accepted

Meeting accepted

Appears as accepted

Appears as accepted

Meeting request read

Meeting request read

Yes

Yes

Meeting request delivery

Meeting request delivery

Yes

Yes

Meeting updates

Meeting updates

Appear as new meeting requests containing the word "Updated" in the subject line

Appear as new meeting requests containing the word "Updated" in the subject line

Meeting cancellation

Meeting cancellation

Yes

Yes

Task requests

Tasks

Task requests appear as e-mail messages or tasks

Task requests appear as e-mail messages

All day meeting requests

No feature

No

Appear as meetings with midnight as the start and end time

No feature

Phone messages

Appear as e-mail messages

No

Other messages

Other messages

Default to e-mail messages

Default to e-mail messages

Note

Connector for Lotus Notes does not support signed or encrypted messages.

E-Mail Message Type Conversion

E-mail messages that originate in either Exchange or Lotus Domino are converted to the format of the target messaging system. Connector for Lotus Notes also tracks message delivery by using delivery confirmation reports, read receipts, and non-delivery reports.

Connector for Lotus Notes handles meeting requests and phone messages as follows:

  • Meeting Requests and Appointments   Connector for Lotus Notes synchronizes Exchange meeting requests and Lotus Domino appointments. Updated meeting requests are identified as Updated in their subject lines. Because of a limitation of the Lotus Domino API, meeting requests that Exchange Server 2003 users send to Lotus Domino users are not automatically updated in Lotus Domino. The user must manually update them.

  • All Day Meeting Requests   All-day meeting requests generated in Exchange Server 2003 appear with a start and end time of midnight.

  • **Phone Messages   **Lotus Notes phone messages appear as e-mail messages in Exchange Server 2003.

E-Mail Message Property Mapping

Objects embedded in messages that are sent by the Exchange Server 2003 client (Outlook) to the Lotus Domino client (Lotus Notes) are converted to attachments. Embedded objects always appear as attachments to the primary message, regardless of where they appear in the original thread.

The following table illustrates which Lotus Notes e-mail message features convert correctly to Microsoft Outlook.

E-mail message conversion between Lotus Notes and Microsoft Outlook

Lotus Notes Microsoft Outlook

Size

Converts correctly.

Color

Converts correctly.

Bold

Converts correctly.

Underline

Converts correctly.

Italic

Converts correctly.

Strikethrough

Converts correctly.

Tables

Convert correctly if Microsoft Word is used as the primary e-mail editor in Outlook, but formatting is lost. Do not convert correctly if Outlook is the e-mail editor.

Embedded OLE objects, including graphics

Convert correctly and can be edited.

Double strikethrough

Ignored.

Superscript

Ignored.

Subscript

Ignored.

Shadow

Ignored.

Outline

Converts to italic.

Emboss

Ignored.

Engrave

Ignored.

Small caps

Ignored.

All caps

Ignored.

Drop caps

Ignored.

Hidden

Ignored; text is visible.

Underline other than single

Ignored.

Bitmaps not embedded as OLE objects

Not migrated; formatting is lost.

Bullets

Ignored.

Directory Synchronization

The following figure depicts the directory connection between Exchange Server 2003 and Lotus Domino. As mentioned in the table above, the Lsdxa.exe process is responsible for controlling the actual directory synchronization processes Dxamex.dll and Dxanotes.dll. Lsdxa.exe is started automatically when the Microsoft Exchange Connector for Lotus Notes service starts. For more information about how to configure directory synchronization, see the Exchange Server 2003 Interoperability and Migration Guide.

Note

Connector for Lotus Notes creates mail-enabled contacts in Active Directory for recipients in the Lotus Notes messaging system. The legacyExchangeDN address (that is, the X.500 address of the Exchange user in Exchange 5.5 format) matches in its first part the legacyExchangeDN of the connector. The first part is that portion of the X.500 address that identifies the connector's administrative group (that is, /O=<name of organization>/OU=<name of administrative group>).

Directory synchronization between Lotus Domino and Exchange Server 2003

dac52e80-6ef3-4221-ac02-2f500ddc8198

On the Exchange side, Dxamex.dll communicates with Active Directory through ADSI to extract the recipient information from the export containers specified in the connector configuration. Dxamex.dll maps the recipient attributes as defined in Amap.tbl and Mapmex.tbl, and places the results in a temporary file named Dxanotes.text in message interchange format (MIF) in the \Program Files\Exchsrvr\Conndata\Temp directory. Dxanotes.dll then parses the Dxanotes.txt file, processes the addresses, and places them in the target directory on the Lotus Domino server. To communicate with Lotus Domino, Dxanotes.dll uses the Lotus Notes Client API.

The following listing is an example of a Dxanotes.txt file:

Load
A
FULLNAME:Administrator
MAILDOMAIN:Exchange
COMPANY:
DEPARTMENT:
FIRSTNAME:
LASTNAME:Administrator
LOCATION:
SHORTNAME:Administrator
UNID:DBC07527-91C1F649-8427525F-902428E2
DN:CN=Administrator,CN=Users,DC=contoso,DC=com
USNCreated:8194
Initials:
Title:
Phone:
MobilePhn:
Fax:
Resource:
CALDOM:Exchange
MAILSRV:

EndOfBuffer

Dxanotes.dll also performs directory synchronization from Lotus Notes to Active Directory. The process uses the Lotus Notes Client API to read the Lotus Domino directory. Dxanotes.dll maps the recipient attributes as defined in Amap.tbl and Mapnotes.tbl, and writes the recipient information to the Dxamex.txt file in the \Program Files\Exchsrvr\Conndata\Temp directory. Dxamex.dll processes the Dxamex.txt file and places the recipient information in the import container specified in the connector configuration.

The following listing is an example of a Dxamex.txt file:

Load
U
DN:admin
TA:NOTES:admin@Notes
ALIAS:admin
NAME:admin
FULLNAME:admin
FIRSTNAME:
Initials:
LASTNAME:admin
NOTESADDR:admin@Notes
UNID:4a12766d-8684ea55-3e551cde-3bac7ae9
COMPANY:
DEPARTMENT:
TITLE:
OFFICE:
PHONE:
FAX:
MOBILEPHN:
USNCREATED:

EndOfBuffer