Plan names for servers and users in a Lotus Domino site

 

+
Search Tips   |   Advanced Search

 

Overview

IBM Lotus Domino server names should be...

  • Short
  • Contain no spaces
  • Descriptive

If the Lotus Domino server name is not the same as the physical machine name, verify the name is resolvable through DNS.

It is not a requirement to make the Lotus Domino server name the same as the physical machine name, but if it is not, Server Connection documents are required in all other Lotus Domino servers and the Lotus Notes or Lotus Domino Administrator client software running on them.

 

User Identities

Identity Description Recommendation
Organization name for a Lotus Domino LDAP server Specified during the server setup procedure you perform after installing the Lotus Domino LDAP server. Example:

dom_hub/mpls/renovationscorp
Administrator of a Lotus Domino LDAP server User identity created during the server setup procedure you perform after installing the Lotus Domino LDAP server. For convenience, you could make this the same as the user name of an administrator in WebSphere Portal (PortalAdminId in the wpconfig.properties file)

Example: wpsadmin

Bind user

...or...

IBM WAS administrator

...or...

both

Identity used by IBM WebSphere Portal to access the LDAP directory. Both LDAP directory and security configuration for WebSphere Portal involve modifying values in the wpconfig.properties file. If you keep the default values for the "Bind Distinguished Name" in this properties file, the user name wpsbind will be used for this LDAP access account.

Created during the server setup of a Lotus Domino LDAP server.

Should be the same as the user ID of an administrator for the WebSphere Application Server (WasUserID in the wpconfig.properties file)

Example: wpsbind

Certifier ID User ID used to register every Lotus Domino server that you add after the first one in the portal site (including the Lotus Domino servers that run Lotus Sametime and Lotus QuickPlace ). It makes all the servers members of the same organization and ( Lotus Domino ) domain. cert.id
WebSphere Portal administrators group You should manually edit the group wpsadmins to wpsadmins/yourorgname. This edit creates a fully distinguished LDAP name of...

cn=wpsadmins/o=yourorgname

This change must made when using a Lotus Domino LDAP directory, because Lotus Domino does not store groups in the hierarchical format that WebSphere Portal expects.

Should be the same as the group name of an administrator for all administrators for the WebSphere Portal server (PortalAdminGroupId in the wpconfig.properties file)

Example: wpsadmins/renovationscorp

In the ACL of the Lotus Domino Directory this group should have Author or Editor access, and the Role Types. These settings allow the administrator group to write and edit Person documents in the Lotus Domino Directory; these are necessary tasks in a portal that uses subscriber management. For more information, see Registration, Edit My Profile and Login

Lotus Sametime server administrator This user name has administrative access to the Lotus Sametime server and can modify Web pages on the server. Example: stadmin
Lotus QuickPlace server administrator This user name has administrative access to the Lotus QuickPlace server and can modify Web pages on the server. Example: qpadmin
Lotus Sametime Web Conferencing administrator This user name is created in the Lotus Domino Directory (names.nsf) on the Lotus Sametime Web Conferencing server. It is used only for integration of Lotus Sametime and the Inline QuickPlace portlet.

In the ACL of the STConfig.nsf database, this user name is a Person/Manager, and has, at minimum, role(s) equivalent to those specified for the meeting api's servlet entry in the servlets.properties file on the Lotus Domino server.

Example: st_webconf_admin

Recommended: At least the [SametimeAdmin] role

 

Parent Topic

Planning a portal with Domino Integration