Rolling out a database

There are several mandatory and optional tasks that a Domino® administrator must complete before putting a database into production.

You must have Manager access in a database access control list (ACL) to perform these tasks.

Mandatory tasks

Perform these tasks before copying a new database or database replica to a production server.

Table 1. Tasks for rolling out a database - mandatory



Set up the database ACL for users and servers that require access

If you plan to make replicas of a database, make sure that the database ACL lists the name of each server containing a replica. If the database uses roles, assign all roles to each server.

If you assign ACL settings on the original database before copying it to a server, assign yourself Manager access on the original. Otherwise, you won't have Manager access to the new copy.

Verify that server ACLs are set up correctly

Without proper access in a server ACL, users and servers won't have access to databases on the server.

Verify that the Domino® Directory contains the necessary Group documents

Create a Group document in the Domino® Directory before adding a Group name in a database ACL. If you must create a Group, make sure that the Group document replicates before you copy the database to a server.

Copy the new database to a server

Consider server disk space, topology, and network protocols. Placing a database on a cluster requires that you consider cluster resources.

Verify that the database appears in the Open Application dialog box

While designing a database, the database designer often removes the database title from the list that appears in the Open Application the database is completed, make sure that the database title appears in the Open Application dialog box.

Decide which servers require replicas of the database and then create the replicas

To make this decision, consider the purpose and size of the database, the number and location of users who need access to the database, and the existing replication schedules between servers.

Verify that Server documents in the Domino® Directory are enabled for replication

Server documents are, by default, enabled for replication, but to avoid any problems, verify this.

Create or edit Connection documents

If several servers have a replica of the database, make sure that any necessary Connection documents are set up so that replication can occur.

Set up a replication schedule

Consider the location and time zones of users and the frequency of database updates.

Optional tasks

The following tasks are not required, but you may want to perform them after your database is in production. Whether or not you need to do these tasks depends on the type of database you are rolling out to the production server and the roles assigned to an application developer, database manager, or Domino® administrator in your organization.

Table 2. Tasks for rolling out a database - optional



Create About This Application and Using This Application documents

Provide the name, phone number, and email address of database managers in the About This Application document. Provide information about the application in the Using This Application document.

For more information, see IBM® Domino® Designer 9.0.1 Social Edition Help.

Create an index for the database

Create a full-text index for the database if users need to search the database for information. If you create the index before you copy a new copy of the database or a replica to a server, the index settings carry over to the new copy or replica.

Distribute encryption keys

If the database design includes encrypted fields, distribute encryption keys to users.

For more information, see IBM® Domino® Designer 9.0.1 Social Edition Help.

Create a Mail-In Database document

If the database is designed to receive mail, you must create a Mail-In Database document in the Domino® Directory.

List the database in the database catalog

By default, all databases except mail databases are listed in the default views of the database catalog. You can add categories to control how the database appears in the catalog views and to help users narrow the scope of a domain search.

Publish the database in a database library

Create a library of selected databases on one server or several servers for users.

Sign the database

Sign a database to provide a signature for it. Do this, for example, so that an Execution Control List (ECL) can evaluate the signature.

Add the database to the Domain Index

If an application database will be useful to a wide audience, include the database in the Domain Index.

Notify users that the database is available

Provide the database title, file name, and server location.