Platform and user directory considerations
There are unique considerations for operating systems that you should be aware of before you proceed with integrating collaboration software with WebSphere Portal. Also, in the context of collaboration integration, there are two types of user directories, Lotus Domino directory and then all other supported user directories.
Platform considerations
Depending upon platform, Lotus Domino servers in your environment have slightly different task and/or registry requirements:
Lotus Domino IIOP is used to pre-populate drop-down lists shown when users personalize the collaborative portlets.
Any Lotus Domino data source servers must have HTTP, LDAP, and Lotus Domino IIOP enabled.
User directory considerations
Directory considerations for Lotus Domino LDAP:
From the portal perspective, there are two types of Lotus Domino servers: the Lotus Domino server as a user repository (Lotus Domino Directory server as an LDAP server), and any Lotus Domino server that acts as a Lotus Domino data source for portlets: such a server is called a messaging/application server.
Because WebSphere Portal supports the use of Lotus Domino Directory as an LDAP server, we can set up the portal to use a Lotus Domino server as the user repository for users who access both the portal and any portlets that access Lotus Domino and collaboration products.
We can use a Lotus Domino server with LDAP enabled both as the user repository for the portal and for auto-detection of users' mail files, unless the portal user repository is so largto use separate machines for performance reasons (see Performance considerations).
Directory considerations for Sametime :
If you will be using portlets for Lotus Domino and Sametime, the Sametime user directory can be any supported LDAP (including Lotus Domino) directory, or a native Lotus Domino directory. But IBM recommends that Sametime use the same directory as the one configured for the portal, to avoid the additional configuration necessary to support both directories.