Movatterモバイル変換

ホーム

Jump to main content

HCL Domino 14.5 Documentation
Welcome to the HCL Domino® 14.5 documentation.
What's new in Domino 14.5?
Learn about all of the new features for administrators in HCL Domino® 14.5.
Overview
Welcome to HCL Domino® Administrator Help.
Installing
Use this documentation to install theHCL Domino® server and subsequently deploy theHCL Notes®client.
Planning
Use this topic as an overview of planning task.
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successfulHCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.
  - Understanding the Server document
    The Server document is set up when you register a server. It contains many of the settings that define how your server operates.
  - Policies
    Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
  - Domino IQ
    Domino 14.5 adds support for running an AI inference engine in the Domino backend.
  - Defining default settings for Notes® user registration
    Before you register new Notes® users, you can specify default settings that apply to all users. Default settings simplify user registration and ensure user settings consistency. You can define many default settings, such as what mail server users have or what certifier ID to use for user registration. You can also specify a default workstation execution control list (ECL) to protect data from unauthorized workstation access.
  - Using groups
    Groups are lists of users, groups, and servers that have common traits. They are useful for mailing lists and access control lists. Using groups can simplify administration tasks.
  - Replicas
    You can make a database available to users in different locations, on different networks, or in different time zones, by creating replicas of the database.
    - How replication works
      For server-to-server or server to/from client replication, the Replicator on one computer calls another Domino® server at scheduled times. By default, the Replicator is loaded at startup. To schedule replication between servers, the servers must be able to connect to each other in order to update replicas. You may need to create Connection documents to enable server connections, depending on your server topology.
    - Guidelines for setting server access to databases
      For replication to occur properly, you must assign servers the appropriate access in the database ACL. Follow these guidelines when you set server access to databases.
    - Setting up a database ACL for server-to-server replication
      You add the names of servers to a database ACL in the same way that you add the names of people. The access level given to a server in an ACL determines what, if any, changes that server can replicate to the replica.
    - Creating replicas using the Administration Process
      Through theHCL Domino® Administrator you can use the Administration Process to initiate the creation of one or more replicas. You can create replicas on servers in the same domain or in another domain (across domains, using a cross domain administration request).
    - Table of replication settings
      By default, two replicas exchange all edits, additions, and deletions if the servers the replicas are on have the necessary access. However, you can customize replication. For example, to save disk space, you can prevent the transfer of documents that are not pertinent to your site.
    - Scheduling times for replication
      Whenever possible, schedule replication for times when there is less activity on the network -- before or after work or at lunch time.
    - Scheduling server-to-server replication
      For replication to occur between two servers, you create a Connection document that specifies how and when the information exchange occurs. Connection documents are stored in the Domino® Directory. Use only one Connection document at a time to handle all replication between each pair of servers. Creating unnecessary Connection documents increases network traffic and congestion.
    - Customizing server-to-server replication
      You can customize replication in several ways.
    - Database.nsf.replicate statistics
      Domino® maintains statistics about replication status.
    - Configuring managed replicas
      An administrator can use the Managed Replicas tab in the Desktop Settings document to set a policy that, for users affected by the policy, marks any existing local mail replica as a managed replica, and, if desired, creates a new managed replica if no local replica exists.
  - Calendars and scheduling
    The calendar and scheduling features allow users to check the free time of other users, schedule meetings with them, and reserve resources, such as conference rooms and equipment.
  - Editing the notes.ini file
    The Domino and Notes notes.ini files contain the settings required for the server and client to operate correctly. If you modify or add settings in a notes.ini file, do so cautiously and never edit the file directly with a text editor.
  - Configuring directory services
    This section describes how to plan, set up, and useHCL Domino® directory services.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
  - Configuring Verse
    HCL Verse providesHCL Notes® users with browser-based access toNotes mail and toNotes calendar and scheduling features. Administrators specify mail policy and security policy settings as well asnotes.ini file settings to complete the full implementation of HCL Verse.
  - Configuring Web servers
    This section describes how to set up theHCL Domino® Web server, and the Domino Web Navigator.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
  - Configuring Widgets and Live Text
    Widgets and Live Text enables end users to see and act on Live Text in supported documents, includingHCL Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Domain Search
    Notes® client and Web users can use Domain Search to search an entire Domino® domain for database documents, files, and attachments that match a search query.
Securing
This section describes security features, including execution control lists, IDs, and TLS.
Administering
This documentation provides information about the administration tools for HCL Domino.
Tuning
Use this information to improveHCL Domino® server,Domino Web server, and messaging performance through the use of resource balancing and activity trends, advanced database properties, cluster statistics, and the Server Health Monitor.
Troubleshooting
This section describes how to find and solve problems withHCL Domino® server and Administrator client.
Notices

Replicas

You can make a database available to users in differentlocations, on different networks, or in different time zones, by creatingreplicas of the database.

All replicas share a replica ID which is assigned when the databaseis first created. The file names of two replicas can be different,and each replica can contain different documents or have a differentdatabase design; however, if their replica IDs are identical, replicationcan occur between them.

As users add, edit, and delete documents in different replicasof a database, the content in the replicas is no longer identical.To ensure that the content in all replicas remains synchronized, youuse Connection documents to schedule replication between the serversthat store the replicas. Then multiple sites, teams, and users canmake changes to a database and share those changes with everyone elsewho has access to that database. In addition, using replicas and schedulingreplication reduces network traffic. Users never need to connect toa single central server that stores the only replica of a particulardatabase. Instead, they can access a replica of that database on oneor more local servers.

These distributed replicas can also be Web sites that are hostedon differentDomino® servers.Then users aren't dependent on one server when they attempt to accesscritical applications over the Internet. If one server is unavailable,users can access another replica of the database on another server.You can also use replicas to help manage ongoing Web site design.On one server, you can set up a Web staging area where you designand test new pages. When the design changes are tested and ready tobe released, you can replicate this server with the server storingthe replica of the Web site that is available to users. By using replicasand replication this way, you prevent Web users from seeing your "work-in-progress."

A replica of a database isn't the same as a copy of a databasethat you make by choosingFile >Application >New Copy. Although a copy of a database may look the same asthe original database, a copy doesn't share a replica ID with theoriginal database and so it can't replicate with it.

Decidingwhen to create a replica

Plan your replica strategy carefully,and create replicas on servers only when necessary. The more replicas,the greater the demand on server and network resources and the greaterthe need for additional maintenance. To prevent unnecessary proliferationof replicas, assign Create Replica server access to only a few administrators.Then tell users and application developers to send their requestsfor new replicas to these administrators.

Create a replicaof a database to:

Improve performance of a heavily used database.
Distribute network traffic.
Keep a database that you're redesigning separate from a productionversion of the database.
Keep a database available even if one server goes down.
Make a database available to users in remote locations.
Provide a replica containing only a subset of information thatis relevant to a particular workgroup.
Set upDomino® systemadministration -- for example, you must create replicas of theDomino® Directory, the AdministrationRequests database, and other critical system databases.
Place a replica of a master template on each server that storesa database that inherits from the master template.
Create a backup database from which you can restore informationif data becomes corrupted; since corrupted data often replicates,use this only as a secondary backup method.

Keep in mind that two replicas will contain slightly differentcontent between replications. If users need access to the most up-to-dateinformation in a database, you can create replicas on clustered serversand then set up replication in clusters. In a cluster, all replicasare always identical because each change immediately replicates toother servers in the cluster.

ページ先頭