Movatterモバイル変換

ホーム

Jump to main content

Welcome
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.
Improving Domino® server performance
Read the following topics for help on improving basic Domino® server performance and capacity, as well as the performance of these features: Agent Manager, databases and the Domino directory, the directory catalog, LDAP searches, mail, Web server, and UNIX™ server.
Updating the design of an enabled agent
Design update helps preserve agents in a database whose design is being updated.

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.
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.
- Using activity trends
  Domino® server resource utilization can be separated into two types, system activity and user activity. System activity, which includes the level of processor, disk, memory, and network consumption that Domino generates to keep the server running, is a fixed amount of activity, as long as systems are healthy and performing smoothly. Domino servers typically use a modest percentage of their resources to run. The remaining server capacity is used to support user activity, which varies with the usefulness of the data on the server.
- Tuning Domain Indexer performance
  Each time the Domain Indexer task runs, it looks in the Domain Catalog for new databases that have theInclude in multi database indexing property enabled. It then looks for documents and files in existing databases and file systems that are new or changed since the last time it ran, and adds them to the Domain Index.
- Improving Domino® server performance
  Read the following topics for help on improving basic Domino® server performance and capacity, as well as the performance of these features: Agent Manager, databases and the Domino directory, the directory catalog, LDAP searches, mail, Web server, and UNIX™ server.
  - Tools for measuring server performance
    Domino® offers performance tools you can use to measure and evaluate server performance.
  - Improving partitioned server performance and capacity
    You use the same set of tools to monitor partitioned servers as you use to monitor individual servers. However, remember that a partitioned server can use a large number of system resources, denying those resources to other partitioned servers on the same computer.
  - Improving Agent Manager performance
    The Agent Manager controls when agents run on a server. Every time an agent runs, it uses server resources. To control when scheduled and event-triggered agents run, you specify settings in the Server document and in the NOTES.INI file. Customizing when agents run may conserve server resources, but it may also delay when agents run.
  - Updating the design of an enabled agent
    Design update helps preserve agents in a database whose design is being updated.
  - Improving server performance using the configuration collector
    The Domino® configuration collector provides snapshots of how the Domino server is configured. You can use that configuration information to analyze recent changes made to the server's configuration that have impacted server performance.
  - Improving database and Domino® Directory performance
    By default, the Domino® Directory uses two database performance properties --Document table bitmap optimization andDon't maintain unread marks -- to improve performance. The following NOTES.INI settings can affect database and Domino Directory performance.
  - Tips for tuning mail performance
    You can modify settings on the Configuration Settings document, or change NOTES.INI settings to help improve mail performance.
  - Improving Windows™ server performance
    In general, use the default settings for your Microsoft™ Windows™ server. However, there are some measures you can take which may result in performance improvements.
  - Improving UNIX™ server performance
    Methods of improving UNIX™ server performance include adjusting disk and memory requirements and disk i/o tuning, and employing console and database logging.
- Improving Web server performance
  After you set up the Domino® Web server and make sure that it runs properly, check the server's performance and response time.
- Improving mail performance
  Domino® includes features that improve efficiency in specific environments, but these features may not be switched on by default.
- Setting advanced database properties
  Advanced database properties include performance optimization and compression features, as well as ways to manage usability features such as unread marks and soft deletions.
- Understanding cluster statistics
  Three categories of Domino® cluster statistics help you analyze clusters
- Improving the performance of the Server Health Monitor
  If the Domino® Administration client workstation performs at 100 percent CPU utilization for a long period of time, the Server Health Monitor discards server statistic data to keep up with the workload.
Troubleshooting
This section describes how to find and solve problems withHCL Domino® server and Administrator client.
Notices

Updating the design of an enabled agent

Design update helps preserve agents in a database whosedesign is being updated.

In pre-8.0 releases ofDomino® ,when a design update for enabled agents occurred, the agents weredisabled and stopped running. This occurred because there was no mechanismto update the agent's design and retain the original signature ofthe agent. InDomino® 8, designupdate can update many enabled agents without disabling the agents.

InDomino® 8 and greater,design update preserves the identify of the agent owner in the "OnBehalf" field and re-signs the agent with the server ID. The agent'senabled status is preserved only if the original agent owner has therights to run agents and if the agent is scheduled to run on the serveron which the design update is performed. The server has explicit rightsto run agents only on itself. If the agent's enabled status cannotbe preserved, the design update is performed and a warning messageis generated and sent to the server console as well as to theDomino® Domain Manager.

Note: This topic describes behavior that occurs only when using theConvert or Design tasks inDomino® Administratorto update the design of a database or databases. Selecting eitherFile >Application >ReplaceDesignorFile >Application >Refresh Design inNotes® doesnot preserve the enablement status of agents already in the design.

For more information about using the Run on behalf of setting,see theHCLDomino® DesignerHelp.

You may see the warning messages shown in the following examplesdepending on who signs the agent.

In this example, the agent was signed by the server, ServerA/DomainA,which did not have rights to run agents on the server Test/Acme. Designupdate updated the agent design, leaving the agent disabled.

Warning generated on server TEST/ACME:

Designer: Agent 'OutOfOffice' in 'mail\rooks.nsf' disabled during Design Update from template 'mail8.ntf'. Agent signer 'ServerA/DomainA.: Users without rights to sign 'On Behalf' agents can only run agents on their own behalf.

Inthis example, the agent was specified to run on -any server-; therefore,its enabled state could not be preserved because it could not be signedwith the server ID Test/DomainB ID. If the agent was signed with Test/DomainBID, the agent would not run on any server other than Test/DomainB,which was not the intention of the agent designer. Design update updatedthe design of the agent, leaving it disabled.

Warning messagegenerated on server Test/DomainB:

Designer: Agent 'LotusInboxCleanup' in 'AdminSurvey2007.nsf' disabled during Design Update from template 'mail8.ntf'. Agent signer 'Lotus Notes Template Development/Lotus Notes'.: Enabled status can be preserved only on the server where the agent is scheduled to run or, for mail agents, on the home mail server. Enabled status cannot be preserved if '-Any server-' is specified for the agent.

ページ先頭