Home
Administering
This documentation provides information about the administration tools for HCL Domino.
Administering with Domino Administrator
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Managing databases
Topics in this section describe how to set up and manage Domino® databases.
Database design, management, and administration
The tasks involved with application design, database design, database management, and Domino® system administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino system administration.
About composite applications
Composite applications incorporate components from multiple applications into a single, role-based work environment. A composite application has one or more pages, each of which contains one or more components. Components can support communication interaction, where one or more components are programmed to respond to user-initiated action in another component.

Administering
This documentation provides information about the administration tools for HCL Domino.
- Administering with AdminCentral
  The AdminCentral application (admincentral.nsf) is automatically created by adminP on the Domino administration server. You can open AdminCentral directly from your Notes Standard or Nomad web client, without the need to start Domino Administrator. This application provides a simplified and easy-to-use way of managing fully functional Notes users and groups in a Domino deployment.
- Administering with Domino Administrator
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
  - Administration tools
    Topics in this section describe the tools you can use to administer a Domino® server.
  - Managing users
    The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
  - Monitoring servers
    This section describes how to use the tools and features that help you monitor a Domino® system.
  - Managing servers
    Manage Domino® servers by performing any of these tasks.
  - Managing databases
    Topics in this section describe how to set up and manage Domino® databases.
    - Database design, management, and administration
      The tasks involved with application design, database design, database management, and Domino® system administration may overlap, depending on the size of your organization and the structure of job responsibilities. In some organizations, an application developer may be responsible for both application and database design, while in others, a database manager may handle all database design and management tasks. In addition, database management overlaps with Domino system administration.
      - Creating a database
        Use the Domino® Administrator to create a database. You can use one of Domino's templates to create a database or you can choose Blank to use a "blank" template.
      - Rolling out a database
        There are several mandatory and optional tasks that a Domino® administrator must complete before putting a database into production.
      - Copying a new database to a server
        Plan the deployment of new databases before copying them to a server.
      - Creating a Mail-In Database document for a new database
        The mail-in database is designed to allow mail to be received by a database that is set up to receive mail, without the mail being added to a person's mail file. The mail-in database can then be accessed by one person, or by multiple people, who have access to read the database. For example, if you want multiple users on a mailing list to read specific mail, that mail can be sent to a mail-in database instead of sending it to numerous individual users. Those users can then open the database and review the mail that has been sent to that database.
      - Signing a database or template
        You can sign a template or database to vouch for its integrity. You might want to do this, for example, to sign an agent so that the Agent Manager on a server can verify that the signer has the rights to execute the agent. Or you might sign a database or template so an ECL on a Notes® client can evaluate which database actions to carry out.
      - About composite applications
        Composite applications incorporate components from multiple applications into a single, role-based work environment. A composite application has one or more pages, each of which contains one or more components. Components can support communication interaction, where one or more components are programmed to respond to user-initiated action in another component.
      - Deleting databases
        To keep a server performing efficiently and to free disk space, delete databases that are no longer active. To delete databases from a cluster server, you use the Cluster database tool in the I Domino® Administrator. To delete databases on non-cluster servers, select the databases and delete them manually, or use the Delete database tool in the Domino Administrator to have the Administration Process deletes replicas of the database.
    - Domino on-disk structure (ODS)
      Domino on-disk structure (ODS) refers to the file format of a database. Each release of HCL Domino® and Notes has a default ODS version for databases. A new release may offer a new ODS version that provides database enhancements not available with earlier ODS versions.
    - Increase the document summary data limit to 16 MB
      Starting with Domino 9.0.1 FP8, you can increase the document summary data limit on databases to 16 MB. Databases must be at ODS 52 or higher.
    - Organizing databases on a server
      You can organize databases in folders.
    - Backup and restore
      As of Domino 12, functionality to back up and restore Notes databases and their associated transaction logs is provided with Domino servers.
    - Attachment consolidation
      The Domino® server employs the Domino Attachment and Object Service (DAOS) to save significant space at the file level by sharing data identified as identical between databases (applications) on the same server.
    - Full-text indexes for single databases
      You can create full-text indexes to allow users to quickly search for information in databases. To search in a database, users enter a word or phrase in the search bar of the database to locate all documents containing the word or phrase.
    - Controlling attachment indexing on servers
      Use the notes.ini setting FT_INDEX_ATTACHMENTS on a server to control full-text indexing of attachments for all databases on a server.
    - Database libraries
      You can create a database library that contains databases that pertain to a specific collection of users or to a specific topic. For example, a corporate database library might include all databases that deal with corporate policies and procedures, and a marketing database library might include databases that are useful to the marketing staff.
    - Database catalogs
      A database catalog provides a list of all databases on a server. You use the server Catalog task to create a database catalog. The Catalog task bases the catalog file (CATALOG.NSF) on the CATALOG.NTF template and adds the appropriate entries to the catalog's ACL.
    - The Files tab in the Domino® Administrator
      The Files tab in the Domino® Administrator provides an easy way for you to manage files in the Domino data folder.
    - Replicating unread marks
      Unread marks can be replicated for selected databases, most notably mail databases, by using the advanced database properties from the Domino® Administrator or from the database properties box. When you enable the replication of unread marks on mail databases, users can read their mail from a workstation on ServerA, and after replication, can read their mail from a workstation on ServerB, with unread mail clearly delineated from mail that has previously been read.
    - Using indirect files to run database maintenance tasks
      You can use indirect files to run the same maintenance task multiple times, resulting in significant time savings. The fixup, compact, updall, design, convert, and replicate tasks support using indirect files. You can also create batch files or scripts that run several maintenance tasks serially against different indirect files to help complete them quickly. If you have multiple CPUs, you can run the same maintenance tasks against multiple indirect files so they run concurrently. It is recommended you only run as many concurrent maintenance tasks as you have CPUs, otherwise they will start competing for CPU resources and can take longer to complete.
    - Updating database indexes and views
      A view index is an internal filing system that Notes® uses to build the list of documents to display in a database view or folder.
    - Synchronizing databases with master templates
      To use a consistent design for multiple databases, database designers can associate databases or elements within databases with a master template.
    - Fixing corrupted databases
      Corrupted databases don't occur frequently when you use transaction logging. When you use transaction logging to log changes to databases, a server automatically uses the transaction log to restore and recover databases after a system failure -- for example, after server failures or power failures. If a disk failure occurs, you use the transaction log along with a certified backup utility to restore and recover the databases.
    - Moving databases
      It may be necessary to move a database from one server to another -- for example, to distribute databases evenly among servers. If there are replicas of the database, the server to which you move the database should have the appropriate Connection documents to replicate the database to other servers that store replicas. If you're moving a database to a server in a cluster, replication between the server and other servers in the cluster that have replicas of the database occurs without Connection documents.
    - Using load convert to convert non-mail databases
      You can use the server's mail convert utility to convert non-mail databases to another type of non-mail database. Non-mail databases are all databases that do not have a $Inbox folder.
    - Redirecting client references to databases
      You can redirect Notes® client references from deleted or moved databases to a database replica that you specify.
    - Running a database analysis
      A database analysis reveals changes in documents, user activity, and other details such as replication data.

About composite applications

Composite applications incorporate components from multiple applications into a single, role-based work environment. A composite application has one or more pages, each of which contains one or more components. Components can support communication interaction, where one or more components are programmed to respond to user-initiated action in another component.

A Notes® component is a link to a specific view, frameset, document, or other design component contained in a Notes® database. The same Notes® database can contain multiple components, and those components can be used in multiple composite applications.

Composite applications can be hosted on Domino® servers running Domino® 8 or greater, or HCL Digital Experience servers running WebSphere® Portal 6.0 or greater. Composite applications can also be run locally.

Composite applications can be used by the Notes® standard configuration, but not the Notes® basic configuration.

To work with composite applications in Notes®, use the Composite Applications Editor, which is optionally installed during Notes® client installation and upgrade.

Composite applications can be used online or offline, and bookmarked like any Notes® application or Web site.

Note: NSF-based composite application support is available only for Notes® applications, accessed from a Notes® client, and not for Domino® Web applications that are accessed from a Web browser.

To be used in a composite application, Domino® Web applications must be rendered by DAP (Domino® Application Portlet) and embedded in a composite application on WebSphere® Portal.

NSF-based composite applications are stored on the Domino® server in .nsf databases. The database contains the definition of a composite application, and access rights to the composite application database itself are managed through a Notes® database access control list (ACL). Security for each component is managed using the same Domino® Designer security controls that are applied to views, framesets, and other design components used in a Notes® database.

Notes® applications can be extended by adding either custom or packaged functions developed on HCL Expeditor, combined with other technologies, for a composite application. Components are assembled into composite applications using the Composite Application Editor.