Creating a policy document

When you create a policy, you use a Policy document to specify which policy settings documents to include. You can create policy settings documents before you create the policy document, or you can create them while you create the Policy document.

If you are creating an exception policy, include only the policy settings documents that have settings whose values you do not want to enforce. For each setting you do not want to enforce, change the value as required. Exceptions are made at the policy setting level. When the effective policy settings are resolved, any settings you specify in the exception policy apply.

Policy document names

The names of Policy documents must be in one of the formats below. However, when you create a Policy document, you do not have to include the asterisk (*) or slash (/) when you enter a policy name. Domino adds them for you depending on the type of policy you specify.

*/organization -- an organizational policy that is automatically applied at the organization level

*/organizational unit/organization -- an organizational policy that is automatically applied to an organizational unit

*/hosted organization -- an organizational policy that is automatically applied to a hosted organization

* -- an organizational policy that is automatically applied to everyone in the Domino Directory

/policyname -- an explicit policy that must be assigned manually, but can be assigned at any organizational level

To create a policy document

1. Make sure that you have Editor access to the Domino Directory and one of these roles:

• PolicyCreator role to create a policy document
• PolicyModifier role to modify a policy document

2. From the Domino Administrator, click the People & Groups tab, and then open the Policies view.

3. Click Add Policy.

4. Under Basics, complete these fields:

Field	Action
Policy name	Enter one: A unique name, for an explicit policy. The name of the organization or organizational unit, such as Acme or Sales/Acme The name of the hosted organization Note To create a policy for all hosted organizations in the Domino Directory, do not enter a policy name. By default Domino will enter the asterisk for you.
Policy type	Choose one: Explicit -- to create a policy to assign to specific users and groups. Organizational -- to create a policy that is automatically assigned to all users in the part of the organization specified in the Policy name field.
Description	Enter a description of the policy.

5. (Optional) Click Create Child to create a child policy document that includes the name of the parent policy. You can save the child policy document and return to it at a later time. When you close this document you return to the parent policy document.

6. To specify the policy settings documents to include in this policy, for each type of settings do one:

• Select a policy settings document from the list.
• Click "New" to create a new policy settings document. Then, after you create the policy settings document, select it from the list.
Note If the name of the new policy settings document does not appear as a selection, you may need to refresh. Press F9)

7. (Optional) To create an exception policy, click the Administration tab and enable “Exception Policy."

Caution Be cautious when creating an exception policy. An exception policy allows a user to override enforced policy settings.

8. Save the document.

Databases created with Domino

The information in this topic is unique to the IBM Lotus Domino with IBM DB2 Universal Database™ Enterprise Server Edition configuration. For information about creating IBM Lotus Notes databases, see the Domino Administrator printed or online documentation.

For information about creating databases in IBM DB2 Universal Database™, go to the DB2 Information Center at http://publib.boulder.ibm.com/infocenter/db2help/index.jsp

Database storage

When you run the DB2 Server Enablement Tool from the Domino Administrator or the Domino Web Administrator, you specify a number of parameters. One of these is the default database storage type of either DB2 or NSF that is assigned to all databases that you create. By default, the database storage type is DB2, but you can change that to NSF on the DB2 tab of the Server document. When NSF is the default database storage type, new databases are created as files in the Domino server's disk space. When DB2 is the default database storage type, the databases are stored in a DB2 database managed by the DB2 server. "Classic" Domino databases are referred to as NSF databases, and NSFs stored in a DB2 database and managed by a DB2 server are referred to as DB2 enabled Notes databases.

Only databases stored in DB2 can be accessed in DB2 using SQL. Databases created with an NSF are not visible to DB2. NSFs and DB2 enabled Notes databases are visible to the Domino server.

Each DB2 enabled Notes database can be identified by the following icon in the Files panel of the Domino Administrator:

Databases not supported as DB2 enabled Notes databases

The Domino tasks listed in the following table create databases in NSF format on DB2 enabled Domino servers.

Note Do not create replicas for these .NSF files on a DB2 enabled Domino server:

Task	Command to run task	Description	Database
Activity Trends Collector	trends	Runs the Activity Trends Collector which performs historical and trended analysis on Domino Activity data.	activity.nsf
Administration Process	AdminP	Automates a variety of administrative tasks.	admin4.nsf
Billing	Billing	Collects all generated billing information.	billing.nsf
Cataloger	Catalog	Updates the database catalog.	catalog.nsf
Cluster Database Directory Manager	Cldbdir	Updates the cluster database directory and manages databases with cluster-specific attributes.	cldbdir.nsf
Event Monitor	Event	Monitors events on a server.	events4.nsf
HTTP Server	HTTP	Enables a Domino server to act as a Web server so browser clients can access databases on the server.	webadmin.nsf
IMAP Server	IMAP	Enables a Domino server to act as a maildrop for IMAP clients.	mail files for IMAP users/mail#.ntf
LDAP Server	LDAP	Enables a Domino server to provide LDAP directory services to LDAP clients.	schema.nsf
MTC	MTC	Reads log files produced by the router and writes summary data about message traffic to a database for message tracking purposes.	mtstore.nsf
Router	Router	Routes mail to other servers.	mail.box
Rooms & Resource Manager	RnRMgr	Processes all Rooms and Resources activities, such as meeting invitations, reschedules or cancellations, and updates the Busytime database accordingly.	clubusy.nsf or busytime.nsf
Schedule manager	Sched	Processes all user calendar activities and updates the Busytime database accordingly.	clubusy.nsf or busytime.nsf
SMTP listener	SMTP	Listens for incoming SMTP connections, enabling Domino to receive mail from other SMTP hosts.	mail*.box

The databases in the following table are not supported as DB2 enabled Notes databases in Domino and DB2.

Note Do not create replicas for these .NSF files on a DB2 enabled Domino server:

Database	Usage	Description	From template
DA.NSF	Directory Assistance	The Domino server uses directory assistance to look up information in a directory other than a local primary Domino Directory (NAMES.NSF).	DA50.NTF
DBDIRMAN.NSF	Domino Server	Keeps information about all Notes databases on the Server.	DBDIRMAN.NTF
DDM.NSF	Admin Client, Domino Server	Domino Domain Monitoring provides one location in the Domino Administrator client that you can use to view the overall status of multiple servers across one or more domains.	DDM.NTF
DIRCAT.NSF	Domino server, Notes Client	Directory catalog is an optional directory database that typically contains information aggregated from multiple Domino Directories.	DIRCAT5.NTF
DOMCHANGE.NSF	RunJava task	The Domino Change Control database is used by the Domino Change Manager process to manage and execute change control plans. It includes an approval cycle workflow and tight integration with the Administration Process.	domchange.ntf
INETLOCKOUT.NSF	Domino server	The first time the lockout database needs to be looked at or written to, it is created using the template inetlockout.ntf. The template is included in server installation and is run during runtime. By default, the ACL allows access to Administrators only. The Default access setting is No Access.	inetlockout.ntf
ISPY50.NSF	ISPY server task	This database is created automatically by the ISpy server task for its mail probing activities.	mail#.ntf
LOG.NSF	Domino Server, Notes Client	Notes Log created at Domino server startup. Records and stores information about all types of Domino server activities and remote workstation communication activities.	LOG.NTF
NAMES.NSF	Domino Server, Notes Client	Domino Directory	PUBNAMES.NTF
RESRC8.NSF	Admin Client, Notes Client	Resource Reservation Database	RESRC8.NTF
STATREP.NSF	Statistic Collector Task	Monitoring Results Database (formerly Statistics Reporting) contains statistics for one or more servers in a domain (gathered by the Statistic Collector Task).	STATREP5.NTF
WEB.NSF	Averaging agent	The Averaging Agent collects ratings that the users assign to Web pages and calculates the rating of pages in the Web Navigator database.

Domino server console command abbreviationsDomino server console command abbreviations

Command/Abbreviation

Broadcast (b)
Dbcache Flush (db f)
Dbcache Show (db s)
Drop (dr)
Exit (e)
Help (he)
Load (l)
Pull (pul)
Push (pus)
Quit (q)
Replicate (rep)
Restart Port (res po)
Restart Server (res se)
Route (ro)
Set Configuration (se c)
Set Secure (se se)
Set Statistics (se st)
Show Allports (sh a)
Show Cluster (sh cl)
Show Configuration (sh co)
Show Directory (sh dir)
Show Diskspace (sh dis)
Show Memory (sh me)
Show Performance (sh pe)
Show Port (sh po)
Show Schedule (sh sc)
Show Server (sh se)
Show Stat (sh st)
Show Tasks (sh ta)
Show Users (sh u)
Show Transactions (sh tr)
Show xDir (sh x)
Show xDir reload (sh x r)
Start Port (sta po)
Stop Port (sto po)
Tell (t)
Trace (tr)