Planning for collaborative servers and portlets
Setting up a site with Lotus Domino Integration requires decisions about user directories, security, authentication, and performance for your suite of Domino and Extended Products servers and software. View some use cases that may help you make decisions leading to a successful Lotus Domino integration.
Performance
When integrating Lotus Domino into the portal environment, consider performance when deciding how many and which servers you need.
For example, to use a Lotus Domino LDAP server as the user directory (repository) for the portal, install portal on a separate machine from the Lotus Domino LDAP server configured to support collaborative features in the portlets. The Lotus Domino LDAP server for the portal user directory should reside on a machine that is dedicated to serving the portal environment and all its users.
i5/OS:
IBM recommends that a specific Lotus Domino server be created to run the collaborative components, and that it should reside on the same i5/OS server as WebSphere Portal.
- Plan names for servers and users in a Lotus Domino site
While installing and integrating Domino and Extended Products, decide on a naming scheme for your servers, plan for and create several important administrative users, and create passwords for those users. Learn about server naming and a table of identities you can use while configuring servers, with recommendations for which names need to match for better performance.
- Determining the needs of the portal site
The following general use cases are intended only to provide some recommendations for your decisions about directories when integrating the Domino and Extended Products Portlets.
- Platform and user directory
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.
- Security and user authentication
Correctly configuring authentication and security includes configuring single sign-on and setting up SSL.
- Automatic detection of mail files
Messaging portlets are configured by default to detect a user's source mail file (a Notes database) based on the identity with which the user signs into the portal. The LDAP server for Lotus Collaborative Services, and Single Sign-On configuration for the portal site, are requirements to support this feature.
Parent topic:
Integrate with collaboration software
Related reference
Member Manager and People Finder
Related information
WebSphere Portal detailed system requirements
Sametime product page