Rolling out a database
As you roll out your application, you need to work closely with your Domino® server administrator to organize your application on a server and perform a set of administrative tasks. The following tables list the mandatory and optional tasks that the Domino® administrator performs to put 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 you copy a new database or database replica to a production server.
For more information on the following tasks, as well as information about replication, see Domino® Administrator Help.
| Task |
Considerations |
|---|---|
| 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. Make sure that the Group document replicates before you copy the 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 Database dialog box |
While designing a database, the database designer often removes the database title from the list that appears in the Open Database dialog box. This deters the user from opening the database. After the database is completed, make sure that the database title appears in the Open Database 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 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 setting. |
| 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 needed. |
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.
For more information on the following tasks, as well as information about replication, see Domino® Administrator Help.
| Task |
Considerations |
|---|---|
| Create "About this database" and "Using this database" documents |
Provide the name, phone number, and e-mail address of database managers in the "About this database" document. Provide information about the application in the "Using this database" document. |
| Create an index for the database For information, see Full-text indexes for single databases if you have installed Domino® Administrator Help. Or, go to http://www.lotus.com/ldd/doc to download or view Domino® Administrator Help. |
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. |
| If the database design includes encrypted fields, distribute encryption keys to users. |
|
| 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. For information, see The database catalog if you have installed Domino® Administrator Help. Or, go to http://www.lotus.com/ldd/doc to download or view Domino® Administrator Help. |
By default, all databases are listed in the database catalog. If you wish, add categories to control how the database appears in the catalog views. |
| Publish the database in a database library. For information, see The database library if you have installed Domino® Administrator Help. Or, go to http://www.lotus.com/ldd/doc to download or view Domino® Administrator Help. |
Create a library of selected databases on one server or several servers for your users. |
| Notify users that the database is available. |
Provide the database title, file name, and server location. |