Agent Settings

Use the Agent Settings page to configure the POA and store the configuration settings in Novell^® eDirectory^TM.

Message File Processing
Select the amount of message file processing for this POA. All incoming e-mail messages arrive in the form of message files, which the POA processes to deliver to users' mailboxes. All service requests for the POA to perform other types of post office data processing also arrive as message files.

All
Enables processing of message files for all message queues.

Low Priority Only
Enables processing of message files only for lower priority message files (priority queues 2 through 7). This includes user e-mail messages of high, normal, and low priority, as well as administrative messages for database updates.

High Priority Only
Enables processing of message files only for higher priority message files (priority queues 0 and 1). This includes live service requests that demand an immediate response from the POA, such as Busy Search requests and user requests for downloads from Remote mailboxes.

Off
Disables message file processing, meaning that this POA does not deliver messages to users' mailboxes but is specialized to perform other functions in the post office.

Message Handler Threads
Specify the total number of message handler threads to allocate to this POA. Message handler threads process message files. The default is 6; valid values range from 1 to 20. The default value of 6 is appropriate for a multipurpose POA. The maximum value of 20 is appropriate for a POA that has been customized to process only message files.

The more message handler threads the POA uses, the more incoming messages it can process simultaneously. However, the more threads the POA uses, the fewer threads are available to other processes running on the same server.

Enable Client/Server
Select this option to enable this POA for client/server access mode. In addition, you must specify an IP address and TCP port for the POA on the Network Address page.

Client/Server Handler Threads
Specify the maximum number of TCP/IP threads this POA can create. TCP/IP threads service client/server requests from GroupWise^® users. The default is 10; valid values range from 1 to 50.

Max Physical Connections
Specify the maximum number of physical TCP/IP connections allowed between this POA and the GroupWise clients run by GroupWise users. Each GroupWise user could have zero or multiple active physical connections. One physical connection can accommodate multiple application connections. Inactive physical connections periodically time out and are then closed by the clients and the POA.

The default maximum number of physical connections is 1024.

Max App Connections
Specify the maximum number of application ("virtual") TCP/IP connections allowed between this POA and the GroupWise clients run by GroupWise users. Each GroupWise user uses one application connection when he or she starts GroupWise. Depending on what activities the user is doing in the GroupWise client, additional application connections are used. For example, the GroupWise Address Book and GroupWise Notify use individual application connections.

The default maximum number of application connections is 2048. This is an appropriate setting for a post office of about 500 users, so that each user is assured of having at least four application connections available while using the GroupWise client.

Enable Caching
Select this option to enable database caching. Deselect this option if your backup system cannot back up open files, or if your LAN file server is not stable.

CPU Utilization (NetWare)
Specify the CPU utilization threshold for a NetWare^® POA. The default is 85 percent. When the CPU utilization threshold is exceeded by more than 5 percent, idle POA threads sleep so that no additional POA processing starts.

Delay Time (NetWare)
Specify how long idle NetWare POA threads sleep when the CPU utilization threshold has been exceeded by 5 percent. The default is 100 milliseconds. Following the delay time, sleeping POA threads can start additional POA processing if needed.

Max Thread Usage for Priming and Moves
Specify the thread usage threshold for priming users' Caching mailboxes and for moving users' GroupWise accounts. The default is 30 percent. You can increase the threshold so that priming and moving proceed more rapidly, but this may impact GroupWise client responsiveness.

Enable IMAP
Select this option to enable this POA to communicate with Internet Message Application Protocol (IMAP) clients.

Max IMAP Threads
Specify the maximum number of IMAP threads that this POA can create. By default, the POA starts 1 IMAP thread and automatically creates additional IMAP threads as needed until the specified maximum is reached. The default maximum is 40 threads and cannot be increased, but you can specify a lower maximum so that the POA allocates fewer threads to IMAP connections. Each IMAP thread can service multiple IMAP e-mail clients.

Enable SOAP
Select this option to enable this POA to communicate with Simple Object Access Protocol (SOAP) clients.

Max SOAP Threads
Specify the maximum number of SOAP threads that this POA can create. By default, the POA starts 4 SOAP threads and automatically creates additional SOAP threads as needed until the specified maximum is reached. The default maximum is 20 threads and cannot be increased, but you can specify a lower maximum so that the POA allocates fewer threads to SOAP connections. Each SOAP thread can service multiple SOAP clients.

Enable Calendar Publishing
Select this option to enable this POA to provide users' Calendar information to the Publishing Host so that the users' Calendars can be viewed on the Internet.

Max Calendar Publishing Threads
Specify the maximum number of calendar publishing threads that this POA can create. By default, the POA starts 2 calendar publishing threads and automatically creates additional threads as needed until the specified maximum is reached. The default maximum is 4 threads and cannot be increased, but you can specify a lower maximum so that the POA allocates fewer threads for calendar publishing.

Disable Administration Task Processing
Select this option to disable the POA admin thread that updates the post office database (wphost.db) when users and/or user information are added, modified, or removed, and repairs it when damage is detected. The POA admin thread must run for at least one POA for each post office. However, it can be disabled for POAs with specialized functioning where the database update and repair activities of the POA admin thread could interfere with other, more urgent processing.

Enable SNMP
Select this option to enable SNMP for a NetWare POA.

SNMP Community "Get" String
Provide the "get" community string for the server where this POA runs. Community strings are case-sensitive. If access to POA information is unrestricted, the "get" community string is typically PUBLIC.

By providing the "get" community string, you enable this POA to receive SNMP requests. The community string information is stored in the domain database and can be discovered by network management and monitoring programs such as GroupWise Monitor.

Enable HTTP
Select this option to enable HTTP and the POA Web console, so that this POA can be monitored by GroupWise Monitor.

HTTP Monitor Settings

HTTP User Name
To limit access to the POA Web console, provide a unique user name.

Unless you are using SSL, do not use an eDirectory user name because the information passes over the non-secure connection between your Web browser and the POA. If you are using SSL, the user name is encrypted and therefore secure.

HTTP Password
Click Set Password, provide a unique password for the HTTP user name, then click Set Password.

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.