Routing mail between Lotus Domino and IBM Workplace users
Many Notes/Domino shops are now adding IBM Workplace messaging for new or existing users. This tip provides an overview of the key issues involved in successfully routing mail between Lotus Domino and IBM Workplace.
Many Notes/Domino shops are now adding IBM Workplace messaging for new or existing users. Courtesy of IBM's new Redbook, Lotus Workplace release 2.0.1 Products and Lotus Domino 6.5.x Together: Integration Handbook, this tip provides an overview of the key issues involved in successfully routing mail between Lotus Domino and IBM Workplace users.
Workplace messaging and mail cells
The Lotus Workplace Messaging application, which provides both a rich client and a Web-based interface, uses the same type of mail cell as WebSphere Application Server, which consists of mail, calendar and other required messaging portlets, as well as basic SMTP inbound and outbound services, POP3 and IMAP services.
To configure a Workplace Messaging cell for domains, postmaster addresses and the like, you use the WebSphere Administrative Console.
In order for mail to be routed between the mail cells, all must be registered in the Lotus Workplace Directory settings. Each cell should have a name, the SMTP server settings, and how users are to be found in the cell.
Selecting the smart host
As IBM's related Redbook notes, Workplace Messaging will route mail to Lotus Notes or Microsoft Outlook users who are in the same Internet domain. To do this, you have to select a "smart host" to make routing decisions. Either mail system can be a smart host, but you must select one and set it up using the Lotus Workplace Mail Cell-Wide Settings, under SMTP Outbound/Local Delivery settings.
Workplace/Domino messaging scenarios
Depending upon your specific network, you're likely to use one of three messaging integration scenarios:
- Everything separate: In this scenario, Workplace Messaging and Domino are deployed with their own Internet domains and LDAP directories; routing between the two is done via DNS lookups. This configuration is often done when existing users are on Domino, and Workplace is being deployed to serve new users. In this case, it may be easiest to deploy Workplace on its own server.
- Shared domain, separate directory: Here, Workplace Messaging and Domino share a single Internet domain, but have separate LDAP directories. In this situation, a designated smart host will need to route mail between the two systems.
The advantage here is that you can manage Domino users and Workplace Messaging users differently. The disadvantage is that you have to manage each set of users separately, which is obviously an extra administrative burden. For this scenario, IBM recommends adding Notes/Domino users to Workplace's LDAP directory.
- Everything shared: Workplace Messaging and Domino share the domain and Domino LDAP directory. Here, everything is centrally controlled, with Domino acting as the LDAP server for all users. In this instance, the Workplace Messaging server should be the smart host for itself and the Domino server. Also, you'll need to define separate mail cells for both.
For more information on how to configure and integrate Lotus Domino and Workplace Messaging, download the IBM Redbook in PDF or HTML.
About the author: Sue Hildreth is a Waltham, MA-based freelance writer specializing in enterprise software. She can be reached at Sue.Hildreth@Comcast.net.
Do you have comments on this tip? Let us know.
Related information from SearchDomino.com:
Please let others know how useful this tip is via the rating scale at the end of it. Do you have a useful Lotus Notes, Domino, Workplace or WebSphere tip or code snippet to share? Submit it to our tip contest and you could win a prize.
Start the conversation
0 comments