Configuration

The Configuration page lists detailed configuration settings for the POA and provides links that enable you to change some configuration settings for the current POA session.

Settings that have been changed at the POA Web console or in the POA startup file, thus overriding the ConsoleOne® settings, are displayed in bold green text.

General Settings

Post Office Directory

Displays the UNC path or mapped drive for the post office directory serviced by the POA.

Post Office Access Mode

Displays the post office access mode. GroupWise® 6.x and later clients always communicate with the post office in client/server mode. However, older GroupWise clients can still run against a 6.x and later post office in direct mode.

You can change the post office access mode in ConsoleOne (Post Office object > GroupWise tab > Post Office Settings page).

Post Office Configuration Instance

Displays the name of the POA object in Novell® eDirectory™. POA configuration settings are stored as properties of the POA object.

Read Configuration from Database

Indicates whether or not the POA is retrieving its configuration settings from eDirectory. By default, it does, but you can turn this off by using the /noconfig startup switch in the POA startup file. This starts the POA using default settings plus startup switch settings.

Error Mail to Administrator

Indicates whether or not the POA will notify a GroupWise administrator when agent errors occur.

To turn error mail on and off for the current POA session, click Admin Task Processing.

IP Addresses Redirection Table

Click IP Addresses Redirection Table to list all the POAs in your GroupWise system, along with their IP addresses, and where applicable, the IP addresses of their proxy servers.

IPV6 Protocol

Indicates whether or not the IPV6 protocol is available on the server. If it is available, the POA detects it and supports IPV6 by default, along with IPV4.

QuickFinder Indexing

Indicates whether or not QuickFinder™ indexing is turned on.

Click QuickFinder Indexing to control indexing for the current POA session.

QuickFinder Indexing Base Offset

Displays the number of hours and minutes after midnight for the POA to start its indexing cycle. The default is 20, meaning at 8:00 p.m.

QuickFinder Indexing Interval

Displays in hours and minutes the time interval between POA QuickFinder indexing cycles. The default is 24 hours. If the value is set to 0 (zero), QuickFinder indexes continuously.

Simple Network Management Protocol (SNMP)

Indicates whether or not the POA is configured for SNMP so that it can be monitored by SNMP manager programs such as the Management and Monitoring Services component of Novell ZENworks® for Servers.

For the Windows POA, this is an installation option. If necessary, you can rerun the Agent Installation program to add SNMP support to the Windows POA.

Admin Task Processing

Indicates whether or not the POA admin thread is currently running. The POA admin thread updates the post office database (wphost.db) when users and user information are added, modified, or removed. The POA admin thread also repairs the database when damage is detected.

Click Admin Task Processing to change admin thread settings for the current POA session.

Intruder Detection

Indicates whether or not intruder detection is enabled for the post office. Intruder detection enables the POA to detect system break-in attempts in the form of repeated unsuccessful logins. This feature can be especially helpful when allowing Remote client users to establish client/server connections to MTAs in your system.

If intruder detection is enabled, the intruder detection configuration settings are listed.

Click Intruder Detection to change intruder detection settings for the current POA session.

GWCheck Processing

Indicates whether or not GWCheck processing (mailbox/library maintenance) is enabled for the POA.

By default, the POA performs mailbox/library maintenance tasks requested from ConsoleOne and configured as POA scheduled events. You can use the /nogwchk startup switch in the POA startup file to disable all mailbox/library maintenance processing for the POA.

NetWare Clustering Enabled (NetWare Only)

Indicates whether or not the NetWare POA is configured for use in a clustered environment.

With the latest version of Novell Cluster Services, the POA can detect when it is running in a cluster.

With versions of Novell Cluster Services™ that date earlier than GroupWise 6.5, this is an installation option. If necessary, you can rerun the Agent Installation program to enable the POA for clustering. The Agent Installation program edits the POA startup file so that the /home startup switch does not include the server name.

Running in Protected Address Space (NetWare Only)

Indicates whether or not the NetWare POA is running in a protected address space on a NetWare server. The POA detects when it is running in a protected address space and displays the name of the address space in the Up Time heading on the Status page.

This is an installation option. It can be changed by editing the autoexec.ncf file to start the agents with the protect grpwise.ncf command.

Post Office Security Requires Password

Indicates whether or not the post office serviced by the POA is configured to require users to log into GroupWise by providing passwords. High security requires passwords; low security does not.

Post office security is established in ConsoleOne (Post Office object > GroupWise tab > Security page).

LDAP Authentication

Indicates whether or not LDAP authentication is enabled for the post office serviced by the POA.

If passwords are required, the POA authenticates users to GroupWise through eDirectory. The POA obtains a user's GroupWise password from the user's User object in order to grant mailbox access. With LDAP authentication enabled, user password information can be retrieved from any network directory that supports LDAP.

Click LDAP Authentication to display LDAP configuration information and to change some LDAP settings for the current POA session.

Move User (Live) via TCP/IP

Indicates whether or not the POA is enabled for live moves.

A live move uses a TCP/IP connection between POAs to move a user from one post office to another. In general, a live move is significantly faster (approximately 5 to 10 times) than a file transfer move. However, it does require that both POAs are version 6 or later and that TCP/IP is functioning efficiently between the two POAs.

The alternative, a file transfer move, uses the transfer of message files (using POAs and MTAs) rather than a TCP/IP connection between POAs. A file transfer move is required if you are moving a user to a post office that is not using a GroupWise 6 or later POA or if you are moving a user across a WAN link where TCP/IP may not be efficient.

Click Move User (Live) via TCP/IP to enable or disable live moves for the current POA session.

Internet Protocol Agent Settings

IMAP Agent

Indicates whether or not the POA is configured to communicate with IMAP e-mail clients.

When IMAP is enabled, subsequent IMAP fields display IMAP configuration information such as the port for incoming IMAP requests and whether SSL is in use.

You can configure the POA to listen for requests from IMAP e-mail clients in ConsoleOne (POA object > GroupWise tab > Agent Settings page and Network Address page).

CAP Agent

Indicates whether or not the POA is configured to communicate with CAP clients.

When CAP is enabled, subsequent CAP fields display CAP configuration information such as the port for incoming CAP requests and whether SSL is in use.

You can configure the POA to listen for requests from CAP clients by using switches in the POA startup file (/cap, /capport, /capssl, and so on).

SOAP Agent

Indicates whether or not the POA is configured to communicate with SOAP clients.

When SOAP is enabled, subsequent SOAP fields display SOAP configuration information such as the port for incoming SOAP requests, whether SSL is in use, and the number of active SOAP threads.

You can configure the POA to listen for requests from SOAP clients in ConsoleOne (POA object > GroupWise tab > Agent Settings page and Network Address page).

Log Settings

Click Log Settings to change the logging functionality for the current POA session.

Log Level

Displays the amount of data displayed on the POA agent console and written to the POA log file.

Normal (Default)

Displays only the essential information suitable for a smoothly running POA.

Verbose

Displays the essential information, plus routing information and file names helpful for troubleshooting.

Diagnostic

Displays the above types of information plus additional detail.

Disk Logging

Indicates whether or not logging information is being saved on disk.

If logging information is not being saved, the default amount of logging information is still displayed on the POA agent console.

Log Directory

Displays the full path where the POA stores its log files. The default is the POA input queue (post_office_directory\wpcsout\ofs), as displayed in the Post Office Directory field at the top of this page.

Maximum Log File Age

Displays the number of days the POA's log files remain on disk before being automatically deleted. The default log file age is 7 days.

Maximum Log Disk Space

Displays the amount of disk space in kilobytes for all POA log files. When the specified disk space is full, the POA overwrites existing POA log files, starting with the oldest one. The default is 65536 KB of disk space for all POA log files.

Performance Settings

Message Worker Threads

Displays the total number of message worker threads to allocate for the POA. Message worker threads deliver messages to users' mailboxes.

Click Message Worker Threads to increase the number of message worker threads for the current POA session.

You can assess whether or not current message file processing is meeting the needs of your GroupWise system on the Status page. Use the Priority Queues and Message Queues links to view the current contents of the POA input queue. Use the Message Worker Threads link to list the message worker threads that the POA is currently running.

Maximum GWCheck Worker Threads

Displays the maximum number of GWCheck worker threads the POA can start. GWCheck worker threads perform mailbox/library maintenance.

Click Maximum GWCheck Worker Threads to increase the number of GWCheck worker threads for the current POA session.

You can assess whether or not the current GWCheck processing configuration is meeting the needs of your GroupWise system on the Status page. Use the GWCheck Auto Queues and GWCheck Scheduled Queues links to view the current contents of the POA GWCheck queue. Use the GWCheck Worker Threads link to list the GWCheck worker threads that the POA is currently running.

Client/Server Handler Threads

Displays the maximum number of client/server handler threads the POA can start. Client/server handler threads service client/server requests from GroupWise users.

Click Client/Server Handler Threads to increase the number of client/server handler threads for the current POA session.

You can use the Status page to assess whether or not current client/server processing is meeting the needs of your GroupWise system. Use the C/S Handler Threads link to list the client/server handler threads that the POA is currently running. Use the C/S Requests Pending link to list periods of time during the last 24 hours when the POA has been unable to respond to all of the client/server requests that it has received from GroupWise client users. These could be Windows clients or Cross-Platform clients.

Database Recovery

Indicates whether or not the POA is configured to perform automatic database recovery.

By default, the POA recovers user databases (userxxx.db) and message databases (msgnnn.db) automatically when it detects a problem.

Database recovery is established in ConsoleOne (POA object > GroupWise tab > Maintenance page).

Database Caching

Indicates whether or not the POA caches user databases (userxxx.db) and message databases (msgnnn.db) in order to deliver messages faster.

By default, the POA caches databases. You can turn off database caching by using the /nocache startup switch in the POA startup file.

When caching is in use, subsequent fields on the Configuration page provide caching statistics.

Nightly User Upkeep

Indicates whether or not the POA performs nightly user upkeep.

By default, the POA performs nightly user upkeep, which consists of the following POA actions performed once per day:

Nightly user upkeep is enabled and configured in ConsoleOne (POA object > GroupWise tab > Maintenance page).

Nightly User Upkeep Offset

Displays the number of hours after midnight for the POA to start performing nightly user upkeep. The default is 1 hour.

Nightly Remote Downloadable Address Book Generation

Indicates whether or not the POA generates a daily copy of the system Address Book for GroupWise Remote client users to download.

By default, the POA does generate a daily copy of the system Address Book. If this option is disabled, the POA generates a copy of the system Address Book whenever a Remote client user requests one and the existing copy is more than 24 hours old.

Click Nightly Remote Downloadable Address Book Generation to change the settings or generate a copy of the system Address Book immediately.

Nightly Remote Address Book Offset

Displays the number of hours after midnight for the POA to generate the daily copy of the system Address Book for Remote client users. The default is 0 (zero), meaning at midnight.

Client/Server Settings

Client/Server

Indicates whether or not the POA is enabled for client/server access mode to the post office.

Client/server access is enabled and configured in ConsoleOne (Post Office object > GroupWise tab > Post Office Settings page, POA object > GroupWise tab > Agent Settings page and Network Address page).

Client/Server over SSL

Indicates whether or not the POA is configured to use SSL connections with GroupWise clients.

By default, SSL is not enabled. You can enable SSL in ConsoleOne (POA object > GroupWise tab > Network Address page).

IP Address

Displays the IP address of the server where the POA is running.

eDirectory Object Name

Displays the fully distinguished eDirectory name of the POA object.

TCP Port for Incoming Connections

Displays the port number where the POA listens for requests from GroupWise clients (Windows or Cross-Platform). The default is 1677.

Maximum Application Connections

Displays the maximum number of application ("virtual") TCP/IP connections that the POA can start with GroupWise clients. Each GroupWise client user creates one application connection when he or she starts GroupWise. The default maximum number of application connections is 2048.

The maximum number of application connections is established in ConsoleOne (POA object > GroupWise tab > Agent Settings page > Max App Connections field).

Maximum Physical Connections

Displays the maximum number of physical TCP/IP connections that the POA can start with GroupWise clients. Each GroupWise client user could have zero or multiple physical connections, depending on what activities he or she is doing in the GroupWise client. For example, the GroupWise client, GroupWise Address Book, and GroupWise Notify will all register as individual application connections. The default maximum number of physical connections is 1024.

The maximum number of physical connections is established in ConsoleOne (POA object > GroupWise tab > Agent Settings page > Max Physical Connections field).

Maximum Thread Usage for Priming and Live Moves

Displays the maximum percentage of POA client/server threads that the POA can use for priming Caching mailboxes and moving users.

By default, the POA can use as much as 20% of its client/server threads for these activities. If many users are starting to use Caching mode or are being moved, you can increase the amount of POA resources devoted to priming and moving.

Click Maximum Thread Usage for Priming and Live Moves to change the percentage.

You can assess whether or not the current percentage is meeting the needs of your GroupWise system by using the Rejected Caching Primings link on the Status page.

HTTP

Indicates whether or not the POA is enabled to listen for requests for status information from the POA Web console.

HTTP over SSL

Indicates whether or not the POA is configured to use an SSL connection with the POA Web console.

By default, SSL is not enabled. You can enable SSL in ConsoleOne (POA object > GroupWise tab > Network Address page).

HTTP Port

Displays the port number where the POA listens for requests for status information from the POA Web console. The default is 7181.

HTTP Refresh Rate

Displays the time interval when the POA refreshes the status information in the POA Web console. The default is 60 seconds.

You can change the refresh rate by using the /httprefresh startup switch in the POA startup file.

Enforce Lockout on Older GroupWise Clients

Indicates whether or not the POA locks out GroupWise clients that do not meet specified date and/or version requirements. By default, the POA allows multiple versions of the GroupWise client to access it.

If lockout is enforced, lockout requirements are listed.

Click Enforce Lockout on Older GroupWise Clients to change the date and/or version requirements for the current POA session.

Message Transfer Protocol

Click Message Transfer Protocol to change the displayed configuration for the current POA session and restart the MTP thread.

Inbound MF Traffic

Displays the TCP/IP address and port where the POA listens to receive message files from the MTA. The default port is 7101.

Outbound MF Traffic

Displays the TCP/IP address and port where the POA sends message files to the MTA. The default port is 7100.

Message Transfer over SSL

Indicates whether or not the POA is configured to use an SSL connection with the MTA.

By default, SSL is not enabled. You can enable SSL in ConsoleOne (POA object > GroupWise tab > Network Address page).

MTP File Transfer Size Limit

Displays the maximum size in megabytes for message files the POA can send to the MTA.

If a message file exceeds the maximum allowed size, the sender and the administrator receive a "delivery disallowed" message specifying the size of the rejected message file and the size limitation.

A message file includes all text associated with a message: the message body, the distribution list, and attachments if any. Because message files are compressed, attachments that would exceed the maximum size in their uncompressed state can still be processed successfully.

Message File Processing Settings

By default, the POA performs message file processing of all message queues to deliver messages to mailboxes. You would only need to change these settings if you are running multiple, specialized POAs for a post office.

Message file processing is configured in ConsoleOne (POA object > GroupWise tab > Agent Settings page).

Directory Scanning for Message Files

Indicates whether or not the POA is enabled to process message files.

High Priority Directory Scanning

Indicates whether or not the POA processes high priority message files (specifically, Busy Searches and requests from Remote client users).

Low Priority Directory Scanning

Indicates whether or not the POA processes lower priority message files (that is, regular messages of high, normal, or low priority).

Disk Check Events

Lists all disk check events that the POA is scheduled for, along with descriptions of the conditions to check for and the actions to perform based on the conditions.

By default, the POA performs one recurring disk check event. Every 5 minutes, the POA checks to make sure there is at least 100 MB of free disk space in the post office directory. If there is ever less than 100 MB of free disk space, the POA performs a Reduce operation on the user and message databases in the post office.

You can modify the default disk check event, or create additional disk check events in ConsoleOne (POA object > GroupWise tab > Scheduled Events page).

Database Maintenance Events

Lists all database maintenance events that the POA is scheduled for, along with the event schedules and the actions to perform.

By default, the POA performs one recurring database maintenance event. At 12:00 a.m. each Friday, the POA performs a structural check of all user, message, and document databases in the post office.

You can modify this default database maintenance event, or create additional database maintenance events in ConsoleOne (POA object > GroupWise tab > Scheduled Events page).


GroupWise Documentation

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