Home
Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
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 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.
Server document - Traveler tab
Complete the fields on the Traveler tab when you are configuring HCL Traveler.

Welcome to the HCL Domino 11.0.1 documentation
Welcome to the HCL Domino® 11.0.1 documentation. Here administrators can find information about planning, installing, configuring, and administering Domino 11.0.1.
- Translated documentation
  The HCL Domino 11.0.1 documentation is currently available in the following languages.
- What's new in Domino® 11?
  Learn about all of the new features for administrators in HCL Domino® 11.
- Overview
  Welcome to HCL Domino® Administrator Help.
- Domino trial
  A trial version of HCL Domino® 11.0.1 is available free of charge.
- Installing
  Use this documentation to install the HCL Domino® server and subsequently deploy the HCL 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 successful HCL 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.
      - Server document - Basics tab
        This topic is an overview of the tabs and fields on the document.
      - Server document - Security tab
        This topic is an overview of the tabs and fields on the document.
      - Server document - Ports tab
        After you install and set up a Domino® server, review the list of network ports that were enabled by the Server Setup program. Unless you customize network settings during setup, Domino enables ports based on the current operating system configuration.
      - Server Tasks tab
        The Server Tasks tab contains seven sub-tabs.
      - Server document - Internet Protocols tab
        This topic is an overview of the tabs and fields on the document.
      - Server document - Miscellaneous tab
        This topic is an overview of the tabs and fields on the document.
      - Server document - Transactional Logging tab
        Use the fields on this tab to enable and configure transaction logging, or to disable transaction logging.
      - Server document - Traveler tab
        Complete the fields on the Traveler tab when you are configuring HCL Traveler.
      - Server document - Administration tab
        This topic is an overview of the tabs and fields on the document.
      - Server Properties - Advanced
        The Advanced tab shows statistics on transactions, users, and memory.
      - Server Properties - Basics
        The Basics tab provides information such as server name, operating system, hardware, and mailboxes. You can also view this information using the Show Tasks server command.
      - Server Properties - Cluster
        The Cluster tab provides information if the server is a member of a cluster.
      - Server Properties - Disks
        The Disks tab provides information about server disks, size, and free space.
    - 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.
    - 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.
    - 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.
    - 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.
    - 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.
    - 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.
    - Configuring Widgets and Live Text
      Widgets and Live Text enables end users to see and act on Live Text in supported documents, including HCL Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Editing the NOTES.INI file
    You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if Support recommends that you do so.
  - Configuring directory services
    This section describes how to plan, set up, and use HCL 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 iNotes®
    HCL iNotes® provides HCL Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of HCL iNotes.
  - Configuring Web servers
    This section describes how to set up the HCL 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.
- Securing
  This section describes security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Tuning
  Use this information to improve HCL Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with HCL Domino® server and Administrator client.
- Notices

Server document - Traveler tab

Complete the fields on the Traveler tab when you are configuring HCL Traveler.

Procedure

Complete these fields in the Basics section:

Table 1. Basics
Field	Action
Maximum memory size	Specify the maximum amount of memory that will be allocated to the Traveler server task. The default is 512 MB.
IPC Socket Port	Specify the TCP port that is used for communications between the Traveler HTTP Servlet and the Traveler server task. This communication is only on the local machine, no external firewalls will see this traffic. The default is 50125.

Complete these fields in the Log Settings section:

Table 2. Log Settings
Field	Action
Logging Level	Choose the logging level that defines the amount of detail Traveler should include in the log files. The possible values are listed in order from the least amount of logging to the most verbose. Choose one: Severe - Only the most severe messages are logged. Warning - Warnings and Severe messages are logged. Informational - Warnings, Severe and Informational messages are logged. This is the default. Fine - In addition to Severe, Warning and Informational messages, low-level tracing is logged. Finer - In addition to Severe, Warning and Informational messages, medium-level tracing is logged. Finest - In addition to Severe, Warning and Informational messages, high-level tracing is logged.
SyncML Logging	Enable SyncML Logging only if you need to troubleshoot a specific synchronization problem. The SyncML logging mechanism logs all traffic between the Traveler Client and Server, except for fields marked private (see the Fields Logged - Privacy field). By default, this setting is Off.
Package Log Filter	Do not modify this parameter unless instructed to do so by Support for troubleshooting purposes. This field allows you to enable logging for certain Traveler components. By default, this field contains the asterisk (*) wildcard which enables logging for all Traveler components.
Maximum File Size	Specify the maximum size of a single Activity Log file. Use this parameter with Maximum Number of Activity Log Files to indicate the total disk space to use for logging. The default is 50 MB.
Maximum Number of Activity Log Files	Specify the maximum number of Activity log files to keep on disk. When this number is reached, each time a new log file is created the oldest log file is removed from the file system. The default is 10.
Fields Logged - Privacy	Specify the fields to be logged for troubleshooting purposes only. Possible values are: Other - Logs all other fields not specified in this list. Body - Logs the Body field of data being synchronized. Subject - Logs the Subject field of data being synchronized. Location - Logs the Location field of data being synchronized. Address - Logs the Address field of data being synchronized. Phone Number - Logs the Phone Number field of data being synchronized.

Complete these fields in the Auto Sync Settings section:

Table 3. Auto Sync Settings
Field	Action
Monitor Polling Interval	Specify how frequently a user's mail database is checked for changes when it is actively being monitored for Auto Sync. This check is made between the Traveler server and the user's mail database. The server's polling interval in seconds. The default is 3 seconds.
Heartbeat Algorithm	Do not change this value. Algorithm to use when sending the connection keep alive message. Note that the keep alive message is only sent if there is no other Auto Sync activity. Indefinite Detection is currently the only supported option.
Heartbeat Initial Interval	Specify the initial interval to use for keep alive polling. This value should not be shorter than any network time out values nor should it be shorter than the Minimum Interval specified. The default is 30 seconds.
Heartbeat Algorithm Minimum Interval	Specify the minimum interval allowed to keep polling alive. The Heartbeat Algorithm will not be allowed to calculate a value smaller than this value. The default is 30 seconds.
Heartbeat Algorithm Maximum Interval	Specify the maximum interval allowed to keep polling alive. The Heartbeat Algorithm will not be allowed to calculate a value greater than this value. The default is 15 minutes.
Heartbeat Retry Interval	Specify the number of minutes to use the optimal keep alive interval before calculating a new optimal value. The default is 30 minutes.
Port for TCP Connections	Specify the TCP port used for Auto Sync communications between the Traveler Server and Client. This port must not be used by other applications on this server. If the Traveler server is behind a firewall this port must be open on the firewall or the Traveler client must use a VPN to tunnel through the external firewalls. The default is 8642.
Device Offline Timeout	Specify the maximum number of hours a user can be inactive before the user's mail database is no longer actively monitored. The user can still access the Traveler Server by activating the device or starting the Traveler Client. As soon as the device is detected by the server after this timeout, the server will resume active monitoring of the mail database. The default is 24 hours.
User Cleanup Timeout	Specify the maximum number of days that a user can be inactive before the user is purged from the Traveler database. The user can still connect by activating the Traveler client, but the client will be required to reregister with the Server and data will be synchronized as if this is a new user. The default is 30 days.

Click Save and Close.