Register a server ID for the staging server

Register a server ID, and optionally an administrator ID, for the staging server. Give mail servers access to the staging server.

About this task

The staging server requires access to your mail servers. To avoid the need for cross-certification, register the server ID under a certifier that your mail servers trust.

If access to mail servers in your environment is granted through a server-specific organizational unit (OU) wildcard, register the staging server under that OU. Then, the staging server has access to the mail servers automatically. For example, if your mail servers are registered under /SERVER/RENOVATIONS and access to them is controlled through the wildcard entry */SERVER/RENOVATIONS, you might register the staging server ID as SCNSTAGING1/SERVER/RENOVATIONS.

For more information, see the topic on registering a server in the Domino® documentation.

The staging server also requires at least Author access to each mail file to be transferred.

Procedure

  1. Register the server ID with a common name of your choice, for example, SCNSTAGING1.
  2. Optional: To use a dedicated ID to administer the staging server rather than one used in your production environment, register a new ID file within the trust hierarchy of the staging server ID.
  3. Open the Server document of each mail server in the Domino directory in which the mail server is registered. Click the Security tab.
    • Make sure that the Access server field allows the staging server at least Reader access.
    • Add the staging server to the Trusted servers field. This access allows the scheduled agents in the onboarding tools to access the mail servers.
  4. Delete the Server document for the newly created staging server from the directory. The new server will be set up in its own domain.
  5. Make sure that the staging server has Author access to each mail file to be transferred.

    Server access to mail files is often controlled through a wildcard ACL entry, for example, */SERVER/RENOVATIONS, or a group, for example, LocalDomainServers.