Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - POST OFFICE AGENT
  6. Manual

Novell GROUPWISE 7 - POST OFFICE AGENT Manual

Hide thumbs

Advertisement

Quick Links

Download this manual
Post Office Agent
I X
Chapter 35, "Understanding Message Delivery and Storage in the Post Office," on page 463
Chapter 36, "Configuring the POA," on page 475
Chapter 37, "Monitoring the POA," on page 515
Chapter 38, "Optimizing the POA," on page 547
Chapter 39, "Using POA Startup Switches," on page 565
IX
Post Office Agent
461

Advertisement

loading

Related Manuals for Novell GROUPWISE 7 - POST OFFICE AGENT

Summary of Contents for Novell GROUPWISE 7 - POST OFFICE AGENT

  • Page 1 Post Office Agent Chapter 35, “Understanding Message Delivery and Storage in the Post Office,” on page 463 Chapter 36, “Configuring the POA,” on page 475 Chapter 37, “Monitoring the POA,” on page 515 Chapter 38, “Optimizing the POA,” on page 547 Chapter 39, “Using POA Startup Switches,”...
  • Page 2 462 GroupWise 7 Administration Guide...
  • Page 3 Understanding Message Delivery and Storage in the Post Office ® A post office is a collection of user mailboxes and GroupWise objects. Messages are delivered into mailboxes by the Post Office Agent (POA). The following topics help you understand the post office and the functions of the POA: Section 35.1, “Post Office Representation in ConsoleOne,”...
  • Page 4 GroupWise View Showing Post Offices in Relationship to Domains Figure 35-2 35.2 Post Office Directory Structure Physically, a post office consists of a set of directories that house all the information stored in the post office. See “Post Office Directory” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
  • Page 5 Message Body: The message body contains the message text in an encrypted format and a distribution list containing user IDs of the sender and recipients. File Attachments (optional): File attachments can be any type of file that is attached to the message.
  • Page 6 Outgoing messages from local senders are stored in the message database assigned to each sender. Incoming messages from users in other post offices are stored in the message database that corresponds to the message database assigned to the sender in his or her own post office. In each case, only one copy of the message is stored in the post office, no matter how many members of the post office it is addressed to.
  • Page 7 MTA Output Queue in the Post Office The MTA output queue in each post office is the directory. post_office\wpcsout If the MTA has a mapped or UNC link to the post office, the MTA writes user messages directly into its output queue, which requires write access to the post office. If the MTA has a TCP/IP link to the post office, the MTA transfers user messages to the POA by way of TCP/IP.
  • Page 8 Library Databases The databases for managing libraries are stored in the directory and its subdirectories in the gwdms post office. file is a database shared by all libraries in the post office. It contains information dmsh.db about where each library in the post office is located. Each library has its own subdirectory in the gwdms directory.
  • Page 9 the user that option. However, you can force the GroupWise 6.x and later client to use direct access by starting it with the /ph switch and providing the path to the post office directory. 35.5 Role of the Post Office Agent The GroupWise Post Office Agent (POA) delivers messages to users’...
  • Page 10 35.5.2 Message File Processing Messages from users in other post offices arrive in the local post office in the form of message files deposited in the POA input queue. See Section 35.3.4, “Agent Input/Output Queues in the Post Office,” on page 466.
  • Page 11 NetWare Windows Server Linux The GroupWise agents can run on the following platforms: Novell NetWare Windows Server Linux In general, GroupWise is most efficient if you match the agent platform with the network operating system, so the POA and the post office should be on the same platform, and the client should be on a compatible platform.
  • Page 12 Section 35.7.2, “Client/Post Office Platform Independence through Client/Server Mode,” on page 472 Section 35.7.3, “POA/Post Office Platform Dependencies Because of Direct Access Requirements,” on page 472 35.7.1 Client/Post Office Platform Independence through Browser Technology If your GroupWise users want to access their mailboxes through POP3, IMAP4, or SOAP clients, it makes no difference what platform their post offices are located on.
  • Page 13 The NetWare POA cannot service a post office on a Windows server because Windows does not support the required cross-platform connection. Post offices cannot be created on Macintosh computers. Understanding Message Delivery and Storage in the Post Office 473...
  • Page 14 474 GroupWise 7 Administration Guide...
  • Page 15 Configuring the POA For detailed instructions about installing and starting the POA for the first time, see “Installing GroupWise Agents” in the GroupWise 7 Installation Guide. ® As your GroupWise system grows and evolves, you might need to modify POA configuration to meet the changing needs of the post office it services.
  • Page 16 POAs for an existing post office if message traffic in the post office is heavy. To accomplish this, you must create additional POA objects as well. ® To create a new POA object in Novell eDirectory: 1 In ConsoleOne, browse to and right-click the Post Office object for which you want to create a new POA object, then click New >...
  • Page 17 7 In the Description field, type one or more lines of text describing the POA. This description displays on the POA server console as the POA runs. When you run multiple POAs on the same server, the description should uniquely identify each one. If multiple administrators work at the server where the POA runs, the description could include a note about who to contact before stopping the POA.
  • Page 18 ConsoleOne Properties Pages Corresponding Tasks and Startup Switches and Settings Domain.PO Section 36.1.1, “Creating a POA Object in eDirectory,” on page 476. Distinguished Name Name Agent Type Description Platform POA Agent Settings Page Message File Processing Section 38.2.2, “Configuring a Dedicated Message File Processing POA,”...
  • Page 19 ConsoleOne Properties Pages Corresponding Tasks and Startup Switches and Settings TCP/IP Address Section 36.2.1, “Using Client/Server Access to the Post Office,” on page 486 Section , “Using TCP/IP Links between the Post Office IPX/SPX Address and the Domain,” on page 481.
  • Page 20 ConsoleOne Properties Pages Corresponding Tasks and Startup Switches and Settings Log File Path Section 37.3, “Using POA Log Files,” on page 538. See also /log, /logdays, /logdiskoff, /loglevel, and /logmax. Logging Level Max Log File Age Max Log Disk Space POA Scheduled Events Page Disk Check Event...
  • Page 21 36.1.3 Changing the Link Protocol between the Post Office and the Domain How messages are transferred between the POA and the MTA is determined by the link protocol in use between the post office and the domain. For a review of link protocols, see Section 10.1.3, “Link Protocols for Direct Links,”...
  • Page 22 5 In the Message Transfer field, specify the TCP port on which the POA will listen for incoming messages from the MTA. The default message transfer port for the POA to listen on is 7101. 6 Click OK to save the TCP/IP information and return to the main ConsoleOne window. Corresponding Startup Switches You can also use the /mtpinipaddr...
  • Page 23 ConsoleOne then notifies the POA and MTA to restart using the new link protocol. For a sample message flow for this configuration, see “TCP/IP Link Open: Transfer between Post Offices Successful” in “Message Delivery to a Different Post Office” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
  • Page 24 3 Select Bind Exclusively to TCP/IP Address, then click OK to save your change. Corresponding Startup Switches You can also use the /mtpoutport startup switch in the POA startup file to establish an exclusive bind to the specified IP address. 36.1.5 Moving the POA to a Different Server As your GroupWise system grows and evolves, you might need to move a POA from one server to another.
  • Page 25 The full post office name is used in the filename. However, all letters are lowercase and any spaces in the post office name are removed. The startup file is located in the /opt/novell/groupwise/agents/share directory. 3 Adjust the setting of the /home switch to point to the new location of the post office directory.
  • Page 26 For more information about log settings and log files, see Section 37.3, “Using POA Log Files,” on page 538. Corresponding Startup Switches You can also use the /log, /loglevel, /logdays, /logmax, and /logdiskoff switches in the POA startup file to configure logging. POA Web Console You can view and search POA log files on the Log Files...
  • Page 27 4 Make sure that Enable TCP/IP (for Client/Server) is selected. The default numbers of physical connections and application connections are appropriate for a post office with as many as 500 users. If you are configuring the POA to service more than 500 users, see Section 38.1.2, “Adjusting the Number of Connections for Client/Server Processing,”...

  • Page 28: Name Server

    7 Select IP Address, then specify the IP address, in dotted decimal format, of the server where the POA is running. Select DNS Host Name, then provide the DNS hostname of the server where the POA is running. IMPORTANT: The POA must run on a server that has a static IP address. DHCP cannot be used to dynamically assign an IP address for it.
  • Page 29 provide any IP address information. However, some GroupWise users might be on platforms where eDirectory is not in use. To fill the same function for non-eDirectory users, you can set up a GroupWise name server. A GroupWise name server redirects each GroupWise client user to the IP address and port number of the POA that services the user’s post office.
  • Page 30 6 Create an entry for the IP address of the first POA and give it the hostname ngwnameserver. 7 If you want a backup name server, create an entry for the IP address of the second POA and give it the hostname ngwnameserver2. You must use the hostnames ngwnameserver and ngwnameserver2.
  • Page 31 For additional instructions about using SSL connections, see Chapter 71, “Encryption and Certificates,” on page 1117. 5 Click OK to save the IMAP settings and return to the main ConsoleOne window. ConsoleOne then notifies the POA to restart with IMAP enabled. Corresponding Startup Switches You can also use the /imap, /imapmaxthreads, /imapport, /imapssl, /imapsslport, and /imapreadlimit...
  • Page 32 5 To secure SOAP connections to the post office, click GroupWise > Network Address, then select Enabled in the SSL drop-down list. The default SOAP port is 7191 and must be unique on the server. You can change the port number if necessary.
  • Page 33 3 Specify the approved GroupWise release version, if any. Only 6.x and later versions of the client are supported for lockout. 4 Specify the approved GroupWise release date, if any You can specify the minimum version, the minimum date, or both. If you specify both minimums, any user for which both minimums are not true is identified as running an older GroupWise client.
  • Page 34 36.2.7 Supporting Forced Mailbox Caching GroupWise client users have the option to download their GroupWise mailboxes to their workstations so they can work without being continuously connected to the network. This is called Caching mode. For more information, see Section 64.1.2, “Caching Mode,” on page 1035.
  • Page 35 Corresponding Startup Switches You can also use the /primingmax switch in the POA startup file to configure the POA to handle multiple requests to prime mailboxes. POA Web Console You can change the POA’s ability to respond to caching requests for the current POA session on the Configuration page.
  • Page 36 4 In the Maximum Send Message Size field, specify in megabytes the size of the largest message you want users to be able to send outside the post office, then click OK. 5 To exit the Link Configuration tool and save your changes, click File > Exit > Yes. ConsoleOne then notifies the POA to restart using the new maximum message size limit.
  • Page 37 2 Click GroupWise > Network Address to display the POA Network Address page. 3 Make sure the POA is already configured for client/server processing as explained in Section 36.2.1, “Using Client/Server Access to the Post Office,” on page 486. 4 Click the pencil icon for the Proxy Server Address field to display the Edit Network Address dialog box.
  • Page 38 36.3.2 Controlling Client Redirection Inside and Outside Your Firewall When a user tries to access his or her mailbox without providing the IP address of the POA for his or her post office, any POA or a GroupWise name server POA can redirect the request to the POA for the user’s post office.
  • Page 39 1 In ConsoleOne, browse to and right-click the POA object, then click Properties. 2 Click GroupWise > Network Address to display the Network Address page. 3 To use SSL connections between the POA and GroupWise clients located inside your firewall, select Enabled in the Local Intranet Client/Server SSL drop-down list to let the GroupWise client determine whether an SSL connection or non-SSL connection is used.
  • Page 40 6 To use SSL connections between the POA and SOAP clients, select Enabled in the SOAP SSL drop-down list to let the SOAP client determine whether an SSL connection or non-SSL connection is used. 7 To use SSL connections between the POA and its MTA, select Enabled in the Message Transfer SSL drop-down list.
  • Page 41 “Configuring a Pool of LDAP Servers” on page 504 “Specifying Failover LDAP Servers (Non-SSL Only)” on page 505 NOTE: If multiple eDirectory trees are involved, refer to TID 10067272 in the Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) for additional instructions. Providing LDAP Server Configuration Information Information about your available LDAP servers must be provided in ConsoleOne before you can enable LDAP authentication for users.
  • Page 42 If you do not specify a full path, the POA looks in the following locations for the trusted root certificate: NetWare: POA installation directory Linux: /opt/novell/groupwise/agents/lib/nldap Windows: POA installation directory For more information about the trusted root certificate, see Section 71.3, “Trusted Root Certificates and LDAP Authentication,”...
  • Page 43 Select DNS Host Name, then provide the DNS hostname of the LDAP server. The default LDAP port is 389 for non-SSL connections and 636 for SSL connections. 8 If the default port number is already in use, specify a unique LDAP port number. 9 Click OK to save the LDAP server address and port information.
  • Page 44 If you are using a Novell LDAP server, you can browse for an eDirectory User object. The information returned from eDirectory uses the following format: cn=username,ou=orgunit,o=organization If you are using another LDAP server, you must type the information in the format used by that LDAP server.
  • Page 45 pool is contacted equally often by the POA. The LDAP server pool can include as many as five servers. 1 Make sure you have enabled LDAP Authentication as described in “Enabling LDAP Authentication for a Post Office” on page 503. 2 In the LDAP Pool Server Reset Timeout field, specify the number of minutes the POA should wait before trying to contact an LDAP server in the pool that failed to respond to the previous contact.
  • Page 46 For more information about the POA startup file, see Chapter 39, “Using POA Startup Switches,” on page 565. 3 Use the /ldapipaddr startup switch to list addresses for multiple LDAP servers. Use a space between addresses. For example: /ldapipaddr-172.16.5.18 172.16.15.19 172.16.5.20 IMPORTANT: Do not include any LDAP servers that require an SSL connection.
  • Page 47 The default is 30; the minimum setting is 15. 7 Click OK to save the intruder detection settings. ConsoleOne then notifies the POA to restart so the new settings can be put into effect. If a user gets locked out by intruder detection, his or her GroupWise account is disabled. To restore access for the user in ConsoleOne, right-click the User object, click GroupWise >...
  • Page 48 The Scheduled Events page lists a pool of POA events available to all POAs in your GroupWise system. 3 To modify the default database maintenance event, which affects all POAs that have this database maintenance event enabled, select Default POA Mailbox/Library Maintenance Event, then click Edit.
  • Page 49 4 In the Trigger box, specify when you want the database maintenance event to take place. You can have the database maintenance event take place once a week, once a day, or at any other regular interval, at whatever time you choose. Below the Trigger box is listed the pool of POA database maintenance actions that are available for inclusion in all POA database maintenance events in your GroupWise system.
  • Page 50 36.4.2 Scheduling Disk Space Management By default, the POA performs one recurring disk space management 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.
  • Page 51 The Scheduled Events page lists a pool of POA events available to all POAs in your GroupWise system. 7 To modify the default disk space management event, which affects all POAs that have this disk space management event enabled, select Default POA Disk Check Event, then click Edit. To create a new disk space management event, which is added to the pool of POA events that can be enabled for any POA in your GroupWise system, click Create, then type a name for the new disk space management event.
  • Page 52 9 In the Trigger Actions At field, specify the minimum amount of available disk space you want to have in the post office. When the minimum amount is reached, the Disk Check actions are triggered 10 In the Stop Mail Processing At field, specify the minimum amount of available disk space at which you want the POA to stop receiving and processing messages.
  • Page 53 For some specific suggestions on implementing disk space management, see Section 12.3, “Managing Disk Space Usage in the Post Office,” on page 182. POA Web Console You can view the currently scheduled disk check events on the Scheduled Events page. 36.4.3 Performing Nightly User Upkeep To keep GroupWise users’...
  • Page 54 6 Specify the number of hours after midnight for the POA to generate the daily copy of the system Address Book for Remote and Caching users. The default is 0 hours (that is, at midnight). If you want to generate the system Address Book for download more often than once a day, you can delete the existing file from the \wpcsout\ofs subdirectory of the post wprof50.db...
  • Page 55 Section 37.3, “Using POA Log Files,” on page 538 Section 37.4, “Using GroupWise Monitor,” on page 539 Section 37.5, “Using Novell Remote Manager,” on page 540 Section 37.6, “Using an SNMP Management Console,” on page 540 Section 37.7, “Notifying the GroupWise Administrator,” on page 544 Section 37.8, “Using the POA Error Message Documentation,”...
  • Page 56 ® NetWare The POA server console always displays on the NetWare server console. Linux: You must use the --show startup switch in order to display the Linux POA server console. “Starting the Linux Agents with a User Interface” in “Installing GroupWise Agents”...
  • Page 57 POA Status Box The POA Status box displays the current status of the POA and its backlog. The information displayed varies depending on whether the POA is processing client/server connections, message files, both, or neither. Processing: Displays a rotating bar when the POA is running. If the bar is not rotating, the POA has stopped.
  • Page 58 POA Statistics Box The POA Statistics box displays statistics showing the current workload of the POA. The information displayed varies depending on whether the POA is processing client/server connections, message files, both, or neither. C/S Requests (for client/server processing): Displays the number of active client/server requests between GroupWise clients and the POA.
  • Page 59 POA Web Console You can view and search POA log files on the Log Files page. Informational Messages When you first start the POA, you typically see informational messages that list current agent settings, current number of threads, TCP/IP options (client/server), and scheduled events. As the POA runs, it continues to provide status and delivery information in the POA Log Message box.
  • Page 60 37.1.2 Controlling the POA from the POA Server Console You can perform the following tasks to monitor and control the POA from the POA server console at the server where the POA is running: “Stopping the POA” on page 520 “Suspending/Resuming the POA Admin Thread”...
  • Page 61 Linux: If the Linux POA does not respond to Exit, you can kill the POA process, as described below, but include the -9 option. Windows: If the Windows POA does not respond to Exit, you can close the POA server console to stop the POA or use the Task Manager to terminate the POA task.
  • Page 62 1 At the POA server console, click Configuration > Admin Status. 2 Click Suspend. NetWare Note: Use Options (F10) > Admin Status > Suspend. The POA admin thread no longer accesses the post office database until you resume processing. To resume the POA admin thread: 1 At the POA server console, click Configuration >...
  • Page 63 Displaying Detailed Statistics about POA Functioning The POA server console displays essential information about the functioning of the POA. More detailed information is also available. 1 At the server where the POA is running, display the POA server console. 2 Click Statistics > Misc. Statistics. NetWare Note: This feature is not available in the NetWare POA.
  • Page 64 Application Connections: Lists the currently active application connections. Every user that starts GroupWise has an application connection for as long as GroupWise is running, even if GroupWise is not actively in use at the moment. By listing the application connections, you can see what users have started GroupWise and how much throughput each user is generating.
  • Page 65 Hold Directory: Displays the path to the directory where the POA stores messages if the TCP/ IP link to the MTA is closed. Current Status: Lists the current status of the TCP/IP link. Open: The POA and the MTA are successfully communicating by way of TCP/IP. Closed: The POA is unable to contact the MTA by way of TCP/IP Unavailable: The POA is not yet configured for TCP/IP communication with the MTA.
  • Page 66 Send Admin Mail: Select this options to send a message to the administrator whenever a critical error occurs. See Section 37.7, “Notifying the GroupWise Administrator,” on page 544. Admin Database Box The Admin Database box provides the following information about the post office database (wphost.db): Status: Displays one of the following statuses: Normal: The POA admin thread is able to access the post office database normally.
  • Page 67 1 At the server where the POA is running, display the POA server console. 2 Click Configuration > Admin Status > Perform DB Recovery. NetWare Note: Use Options (F10) > Admin Status > Perform DB Recovery. For additional database repair procedures, see Chapter 26, “Maintaining Domain and Post Office Databases,”...
  • Page 68 You can set up indexing to occur at regular intervals. See Section 38.3.1, “Regulating Indexing,” on page 555. If the indexing load on the POA is heavy, you can set up a separate POA just for indexing. See Section 38.3.2, “Configuring a Dedicated Indexing POA,” on page 556.
  • Page 69 2 Click Log > Auto Scroll to toggle automatic scrolling on or off. NetWare Note: Use View Log File (F9). For explanations of messages in the POA log file, see “Post Office Agent Error Messages” in GroupWise 7 Troubleshooting 1: Error Messages.
  • Page 70 Adjusting POA Log Settings Default log settings are established when you start the POA. However, you can adjust the POA log settings for the current session from the POA server console. This overrides any settings provided in ConsoleOne or in the POA startup file. The modified settings remain in effect until you restart the POA, at which time the log settings specified in ConsoleOne or the startup file take effect again.
  • Page 71 37.2.1 Setting Up the POA Web Console The default HTTP port for the POA Web console is established during POA installation. You can change the port number and increase security after installation in ConsoleOne. 1 In ConsoleOne, browse to and right-click the POA object, then click Properties. 2 Click GroupWise >...
  • Page 72 9b Click Set Password. 9c Type the password twice for verification. 9d Click Set Password. ® Unless you are using an SSL connection, do not use a Novell eDirectory username and password because the information passes over the insecure connection between your Web browser and the POA.
  • Page 73 POA Web Console Figure 37-3 37.2.3 Monitoring the POA from the POA Web Console The POA Web console provides several pages of information to help you monitor the performance of the POA. The bar at the top of the POA Web console displays the name of the POA and its post office.
  • Page 74 POA Web Console with the Status Page Displayed Figure 37-4 Click any hyperlinked status items for additional details. The status information is much the same as that provided at the POA server console, as described in Section 37.1.1, “Monitoring the POA from the POA Server Console,”...
  • Page 75 On a Windows server, the following information is displayed: POA Web Console Environment Page for a Windows Server Figure 37-7 Viewing and Searching POA Log Files On the POA Web console menu, click Log Files to display and search POA log files. POA Web Console with the Log Files Page Displayed Figure 37-8 To view a particular log file, select the log file, then click View Events.
  • Page 76 POA Web Console with the Scheduled Events Page Displayed Figure 37-9 QuickFinder indexing and remote downloadable Address Book generation can be controlled using links from the Configuration page. The Configuration page also displays information about disk check events and database maintenance events. However, scheduled events must be created and modified using ConsoleOne.
  • Page 77 Changing POA Configuration Settings On the POA Web console menu, click Configuration. Online help on the Configuration page helps you interpret the configuration information being displayed. POA Web Console with the Configuration Page Displayed Figure 37-11 Click any hyperlinked configuration items to change settings for the current agent session. The settings that can be modified are much the same as those that can be changed at the POA server console, as described in Section 37.1.2, “Controlling the POA from the POA Server Console,”...
  • Page 78 Modify the functioning of the POA admin thread as needed, then click Submit. The changes remain in effect for the current POA session. Controlling the POA MTP Threads On the Configuration page, click Message Transfer Protocol. POA Web Console with the Message Transfer Protocol Settings Page Displayed Figure 37-13 On this page, you can restart MTA processing between the POA and the MTA.
  • Page 79 Using startup switches to override ConsoleOne settings (see Section 39, “Using POA Startup Switches,” on page 565) Using the POA server console to override log settings for the current POA session (see Section , “Adjusting POA Log Settings,” on page 530) Using the POA Web console to override other settings for the current POA session (see Section 37.2.4, “Controlling the POA from the POA Web Console,”...
  • Page 80 963. 37.5 Using Novell Remote Manager If the POA is running on NetWare 6.5 or on Novell Open Enterprise Server (OES), you can use the IP Address Management feature in Novell Remote Manager (Manage Server > IP Address Management) to view the IP address and port configuration for the POA. This is also true for other GroupWise agents (MTA, Internet Agent, and WebAccess Agent) running on NetWare 6.5/OES...
  • Page 81 Section 37.6.3, “Configuring the POA for SNMP Monitoring,” on page 544 37.6.1 Setting Up SNMP Services for the POA Select the instructions for the platform where the POA runs: “Setting Up SNMP Services for the NetWare POA” on page 541 “Setting Up SNMP Services for the Linux POA”...
  • Page 82 3 Locate the snmpd.conf file on your Linux server. 4 In a text editor, open the snmpd.conf file and add the following line: dlmod Gwsnmp /opt/novell/groupwise/agents/lib/libgwsnmp.so 5 Save the snmpd.conf file and exit the text editor. 6 Restart the SNMP daemon (snmpd) to put the changes into effect.
  • Page 83 option was not available. Now that you have set up SNMP, you can install GroupWise agent SNMP support. At the Windows server where you want to install the GroupWise agent SNMP support: 1 Run setup.exe at the root of the GroupWise 7 Administrator for NetWare/Windows CD. Click Install Products >...
  • Page 84 2e Make sure that the server where the POA is running is configured to send SNMP traps to the ZENworks Server Management Site Server. NetWare: Add the IP address or hostname of the ZENworks Server Management Site Server to the traptarg.cfg file in the sys:\etc directory. Windows: Add the IP address or hostname of the ZENworks Server Management Site Server to the list of trap destinations.
  • Page 85 2 In the Administrator field, browse to and select your GroupWise user ID. A domain can have a single administrator, or you can create a group of users to function as administrators. 3 Click OK to save the administrator information. The selected user or group then begins receiving e-mail messages whenever POAs servicing post offices in the domain encounter critical errors.
  • Page 86 37.10 Using Platform-Specific POA Monitoring Tools Each operating system where the GroupWise POA runs provides tools for monitoring programs. NetWare: You can use the NetWare Monitor NLM to monitor the effects of the POA on the NetWare server. NetWare 6.x/OES provides monitoring tools that you can use from your Web browser.
  • Page 87 Optimizing the POA You can adjust how the POA functions to optimize its performance. Before attempting optimization, you should run the POA long enough to observe its efficiency and its impact on other network applications running on the same server. See Chapter 37, “Monitoring the POA,”...
  • Page 88 2 Click GroupWise > Agent Settings to display the Agent Settings page. 3 Increase the number in the TCP Handler Threads field to increase the maximum number of threads the POA can create for client/server processing. The optimum number of threads for a POA is affected by many factors, including available system resources, number of users in Caching mode, number of users priming Caching mailboxes, and so on.
  • Page 89 38.1.2 Adjusting the Number of Connections for Client/Server Processing Connections are the number of “sockets” through which client/server requests are communicated from the GroupWise client to the POA. Application connections: Each GroupWise user uses one application connection when he or she starts GroupWise.
  • Page 90 ConsoleOne then notifies the POA to restart so the new connection settings can be put into effect. Corresponding Startup Switches You can also use the /maxappconns /maxphysconns switches in the POA startup file to adjust the POA client/server processing. POA Web Console Status page helps you assess whether the POA is currently meeting the client/server needs of the post office.
  • Page 91 5 Increase the number in the TCP Handler Threads field as needed to increase the maximum number of threads the POA can create. The optimum number of threads for a POA is affected by many factors, including available system resources, number of users in Caching mode, number of users priming Caching mailboxes, and so on.
  • Page 92 38.2 Optimizing Message File Processing If you run only one POA for the post office, you can adjust the number of POA threads for message file processing. If message file processing needs are extremely heavy for a post office, you can set up a dedicated message file processing POA to meet those needs.
  • Page 93 Corresponding Startup Switches You can also use the /threads switch in the POA startup file to adjust the number of message handler threads. POA Web Console Status page helps you assess whether the POA is currently meeting the message file processing needs of the post office.
  • Page 94 6 Deselect Enable TCP/IP (for Client/Server). Make sure another POA handles client/server processing. 7 Select Disable Administration Task Processing, so that this POA does not run an admin thread. Make sure that another POA handles administration tasks. 8 Click Apply to save the updated information on the Agent Settings page. 9 Click GroupWise >...
  • Page 95 38.3.1 Regulating Indexing By default, the POA indexes messages and documents in the post office every 24 hours at 8:00 p.m. You can modify this interval if users need messages and documents indexed more quickly. To start indexing immediately, see “Updating QuickFinder Indexes”...
  • Page 96 Corresponding Startup Switches You can also use the /qfinterval, /qfintervalinminute, /qfbaseoffset, and /qfbaseoffsetinminute switches in the POA startup file to regulate indexing. POA Web Console You can control indexing for the current POA session on the Configuration page. Under the General Settings heading, click QuickFinder Indexing.
  • Page 97 regularly, you should configure the POA with very frequent indexing cycles in order to get all messages indexed in a timely manner. For continuous QuickFinder indexing, set QuickFinder Update Interval to 0 (zero). 7 Click Apply to save the updated QuickFinder settings. 8 Click GroupWise >...
  • Page 98 GroupWise client. In Online mode, the FID is displayed after the username. In Caching or Remote mode, the FID is the last three characters of the Caching or Remote directory (for example, c:\novell\groupwise\gwstr7bh). Determining Indexing Priority The POA carries on many processes at once. If you are not using a dedicated indexing POA, you can configure the POA to make indexing a higher or lower priority task than responding to users’...
  • Page 99 Priority Level Description Index constantly until all databases have been indexed, then wait until the next indexing cycle set on the QuickFinder property page of the POA object before starting to index again. If you have users who consistently receive more items than are processed during your current daily indexing cycle, you could implement an appropriate /qflevel setting for permanent use.
  • Page 100 3 Increase the number in the Maintenance Handler Threads field. 4 Click OK to save the new thread setting. ConsoleOne then notifies the POA to restart so the new setting can be put into effect. Corresponding Startup Switches You can also use the /gwchkthreads switch in the POA startup file to increase the number of POA threads started for database maintenance activities.
  • Page 101 4 Make sure Enable Automatic Database Recovery is selected. 5 Set Maintenance Handler Threads as needed. The maximum number of threads you can start for database maintenance is 8. 6 Deselect Perform User Upkeep and deselect Generate Address Book for Remote. Make sure another POA handles these tasks.
  • Page 102 38.5 Optimizing CPU Utilization for the NetWare To ensure that it does not dominate the NetWare server CPU, the NetWare POA has a CPU utilization threshold. The default CPU utilization threshold for the NetWare POA is 85 percent. You can change this threshold using the CPU Utilization option. If CPU utilization exceeds the threshold by 5 percent, any idle NetWare POA threads remain idle for the number of milliseconds set by the Delay Time option.
  • Page 103 4 Decrease the number in the Delay Time field to allow NetWare POA threads to take on new tasks more quickly. Increase the number in the Delay Time field to force NetWare POA threads to pause before taking on new tasks. 5 Click OK to save the new CPU utilization settings.
  • Page 104 564 GroupWise 7 Administration Guide...
  • Page 105 Using POA Startup Switches ® You can override settings provided in ConsoleOne by using startup switches in the POA startup file. When you run the Agent Installation program, an initial POA startup file is created in the agent installation directory. It is named using the first 8 characters of the post office name with a .poa extension.
  • Page 106 NetWare POA Linux POA Windows POA ConsoleOne Settings /home --home /home /httppassword --httppassword /httppassword HTTP Password /httpport --httpport /httpport HTTP Port /httprefresh --httprefresh /httprefresh /httpssl --httpssl /httpssl HTTP SSL /httpuser --httpuser /httpuser HTTP User Name /imap --imap /imap IMAP /imapmaxthreads --imapmaxthreads /imapmaxthreads Max IMAP Threads...
  • Page 107 NetWare POA Linux POA Windows POA ConsoleOne Settings /ldapuser --ldapuser /ldapuser LDAP User Name /ldapuserauthmethod --ldapuserauthmethod /ldapuserauthmethod User Authentication Method /lockoutresetinterval --lockoutresetinterval /lockoutresetinterval Lockout Reset Time /log --log /log Log File Path /logdays --logdays /logdays Max Log File Age /logdiskoff --logdiskoff /logdiskoff Logging Level...
  • Page 108 NetWare POA Linux POA Windows POA ConsoleOne Settings /norecover --norecover /norecover Enable Auto DB Recovery /nosnmp --nosnmp /nosnmp Enable SNMP /notcpip --notcpip /notcpip Enable TCP/IP (for C/S) /nuuoffset --nuuoffset /nuuoffset Start User Upkeep /password --password /password Remote Password /port --port /port Client/Server Port /primingmax...
  • Page 109 The full path must be included if the file does not reside in the same directory with the POA program. Linux: The startup file always resides in the /opt/novell/groupwise/agents/share directory. Windows: The full path must be included if the file does not reside in the same directory with the POA program.
  • Page 110 39.4 /capmaxthreads Specifies the maximum number of CAP threads the POA can create to service CAP clients. The default is 50. This setting is appropriate for most systems. See Section 36.2.5, “Supporting CAP Clients,” on page 492. NetWare POA Linux POA Windows POA Syntax: /capmaxthreads-number...
  • Page 111 For information about clustering the POA, see the GroupWise 7 Interoperability Guide. If you are running the NetWare POA on the latest version of NetWare 6.x and Novell Cluster Services , the POA can detect the cluster automatically. NetWare POA...
  • Page 112 39.11 /enforceclientversion Enforces the minimum client release version and/or date so that users of older clients are forced to ® update in order to access their GroupWise mailboxes. Valid settings are version, date, both, and disabled. See Section 36.2.6, “Checking What GroupWise Clients Are in Use,” on page 492.
  • Page 113 NetWare POA Linux POA Windows POA Example: /externalclientssl-enabled --externalclientssl disabled /externalclientssl-required See also /certfile, /keyfile, /keypassword, and /port. 39.14 /gwchkthreads Specifies the number of threads the POA starts for Mailbox/Library Maintenance activities. The default is 4; valid values range from 1 to 8. See Section 38.4.1, “Adjusting the Number of POA Threads for Database Maintenance,”...
  • Page 114 39.17 /help Displays the POA startup switch Help information. When this switch is used, the POA does not start. NetWare POA Linux POA Windows POA Syntax: /help or /? --help /help or /? Example: load gwpoa /help ./gwpoa --help gwpoa.exe /help 39.18 /home Specifies the post office directory, where the POA can find the message and user databases to service.
  • Page 115 NetWare POA Linux POA Windows POA Example: /httpport-7182 --httpport 7183 /httpport-7184 See also /httpuser, /httppassword, /httprefresh, and /httpssl. 39.21 /httprefresh Specifies the rate at which the POA refreshes the status information in your Web browser. The default is 60 seconds. See Section 37.2, “Using the POA Web Console,”...
  • Page 116 39.24 /imap Enables IMAP so that the POA can communicate with IMAP clients. Valid settings are enabled and disabled. See Section 36.2.3, “Supporting IMAP Clients,” on page 490. NetWare POA Linux POA Windows POA Syntax: /imap-enabled or disabled --imap enabled or disabled /imap-enabled or disabled Example: /imap-enabled...
  • Page 117 See also /imap, /imapmaxthreads, /imapssl, /imapsslport, and /imapreadlimit. 39.28 /imapssl Sets the availability of secure SSL communication between the POA and IMAP clients. Valid settings are enable and disable. See Section 36.3.3, “Securing the Post Office with SSL Connections to the POA,” on page 498.
  • Page 118 IP addresses. See Section 36.1.4, “Binding the POA to a Specific IP Address,” on page 483. See also “Editing Clustered Agent Startup Files” in “Novell Cluster Services on NetWare” in the GroupWise 7 Interoperability Guide. NetWare POA Linux POA Windows POA...
  • Page 119 Linux POA Windows POA Syntax: /language-code --language code /language-code Example: /language-de --language de /language-fr The table below lists the valid language codes. Contact your local Novell sales office for information about language availability. Language Language Language Language Code Code Arabic Hungarian...
  • Page 120 Language Language Language Language Code Code English-United States Portuguese-Brazil Finnish Russian French-France Spanish German-Germany Swedish Hebrew For more information, see Chapter 7, “Multilingual GroupWise Systems,” on page 105. 39.37 /ldapdisablepwdchg Prevents GroupWise users from changing their LDAP passwords by using the Password dialog box in the GroupWise client.
  • Page 121 39.39 /ldapippooln Specifies a pooled LDAP server’s network address as either an IP address or a DNS hostname. As many as five LDAP servers can participate together as a pool; therefore, n ranges from 1 to 5. See “Configuring a Pool of LDAP Servers” on page 504.
  • Page 122 NetWare POA Linux POA Windows POA Syntax: /ldapportpooln-port --ldapportpooln port /ldapportpooln-port Example: /ldapportpool2-390 --ldapportpool3 391 /ldapportpool4-392 See also /ldapippooln, /ldappoolresettime, /ldapsslpooln, and /ldapsslkeypooln. 39.43 /ldappwd Provides the password for the LDAP user that the POA uses to log in to the LDAP server. See Section 36.3.4, “Providing LDAP Authentication for GroupWise Users,”...
  • Page 123 39.46 /ldapsslkey Specifies the full path to the SSL key file used with LDAP authentication. See Section 36.3.4, “Providing LDAP Authentication for GroupWise Users,” on page 501. NetWare POA Linux POA Windows POA Syntax: /ldapsslkey-[svr\][vol:]\dir\file --ldapsslkey /dir/file /ldapsslkey-[drive:]\dir\file /ldapsslkey-\\svr\vol\dir\file /ldapsslkey- \\svr\sharename\dir\file Example /ldapsslkey-\ldap\gwkey.der...
  • Page 124 See also /ldapipaddr, /ldapport, /ldapuser, /ldappwd, /ldapuserauthmethod, /ldapdisablepwdchg, ldapssl, and /ldapsslkey. 39.49 /ldapuser Specifies the username that the POA can use to log in to the LDAP server in order to authenticate GroupWise client users. See Section 36.3.4, “Providing LDAP Authentication for GroupWise Users,”...
  • Page 125 39.52 /log Specifies the directory where the POA stores its log files. The default location varies by platform. NetWare: post_office\wpcsout\ofs Linux: /var/log/novell/groupwise/post_office_name.poa Windows: post_office\wpcsout\ofs For more information, see Section 37.3, “Using POA Log Files,” on page 538. NetWare POA Linux POA...
  • Page 126 See also /loglevel. 39.55 /loglevel Controls the amount of information logged by the POA. Logged information is displayed in the log message box and written to the POA log file during the current agent session. The default is Normal, which displays only the essential information suitable for a smoothly running POA. Use Verbose to display the essential information, plus additional information helpful for troubleshooting.
  • Page 127 39.58 /maxphysconns Sets the maximum number of physical TCP/IP connections allowed between the POA and the GroupWise clients run by GroupWise users. The default maximum number of physical connections is 1024. See Section 38.1.2, “Adjusting the Number of Connections for Client/Server Processing,” on page 549.
  • Page 128 NetWare POA Linux POA Windows POA Syntax: /mtpoutipaddr- --mtpoutipaddr /mtpoutipaddr- network_address network_address network_address Exampl /mtpoutipaddr-172.16.5.18 --mtpoutipaddr 172.16.5.19 /mtpoutipaddr-172.16.5.19 /mtpoutipaddr-server2 --mtpoutipaddr server3 /mtpoutipaddr-server4 See also /mtpinipaddr, /mtpinport, /mtpoutport, /mtpsendmax, and /nomtp. 39.62 /mtpoutport Specifies the message transfer port number the MTA listens on for messages from the POA. The default is 7100.
  • Page 129 See also /certfile, /keyfile and /keypassword. 39.65 /name Specifies the object name of the POA object in the post office. If you have multiple POAs configured for the same post office, you must use this switch to specify which POA configuration to use when the POA starts.
  • Page 130 39.68 /noconfig Ignores any configuration information provided for the POA in ConsoleOne and uses only settings from the POA startup file. The default is for the POA to use the information provided in ConsoleOne, overridden as needed by settings provided in the startup file or on the command line. NetWare POA Linux POA Windows POA...
  • Page 131 39.72 /nomf Turns off all message file processing for the POA. The default is for the POA to process all message files. Two specialized configurations that require turning off message files are described in Section 38.1.3, “Configuring a Dedicated Client/Server POA,” on page 550 Section 38.3.2, “Configuring a Dedicated Indexing POA,”...
  • Page 132 39.76 /nonuu Disables nightly user upkeep. See Section 36.4.3, “Performing Nightly User Upkeep,” on page 513. NetWare POA Linux POA Windows POA Syntax: /nonuu --nonuu /nonuu See also /nuuoffset. 39.77 /noqf Disables the periodic QuickFinder indexing done by the POA. The default is for periodic indexing to be turned on.
  • Page 133 39.80 /nosnmp Disables SNMP for the POA. The default is to have SNMP enabled. See Section 37.6, “Using an SNMP Management Console,” on page 540. NetWare POA Linux POA Windows POA Syntax: /nosnmp --nosnmp /nosnmp 39.81 /notcpip Disables TCP/IP communication for the POA. The default is to have TCP/IP communication enabled.
  • Page 134 See also /user and /dn. 39.84 /port Sets the TCP port number used for the POA to communicate with GroupWise clients in client/server access mode. The default is 1677. See Section 36.2.1, “Using Client/Server Access to the Post Office,” on page 486.
  • Page 135 NetWare POA Linux POA Windows POA Syntax: /qfbaseoffsetinminute- --qfbaseoffsetinminute minutes /qfbaseoffsetinminute-minutes minutes Exampl /qfbaseoffset-30 --qfbaseoffset 45 /qfbaseoffset-90 See also /qfbaseoffset, /qfinterval, /qfintervalinminute, and /noqf. 39.88 /qfdeleteold Deletes previous versions of QuickFinder .idx and .inc files to conserve disk space during periods of heavy indexing.
  • Page 136 39.91 /qflevel Customizes the way the POA performs indexing. Valid levels are 0 through 3 and 999. See “Determining Indexing Priority” on page 558 NetWare POA Linux POA Windows POA Syntax: /qflevel-level --qflevel level /qflevel-level Example: /qflevel-1 --qflevel 3 /qflevel-999 The following table describes the functionality of each level: QuickFinder Indexing Priority Levels Table 39-2...
  • Page 137 39.93 /qfnopreproc Suppresses generation of document word lists that are normally written to user databases when libraries are indexed. Use with /qfnolibs. See “Determining What to Index” on page 558. NetWare POA Linux POA Windows POA Syntax: /qfnopreproc --qfnopreproc /qfnopreproc See also /qfdeleteold, /qflevel, /qfnolibs, /qfnousers, /qfusefidbeg, and /qfuserfidend.
  • Page 138 In Online mode, the FID is displayed after the username. In Caching or Remote mode, the FID is the last three characters of the Caching or Remote directory (for example, c:\novell\groupwise\gwstr7bh). See also /qfdeleteold, /qflevel, /qfnolibs, /qfnopreproc, /qfnousers, and /qfuserfidbeg.
  • Page 139 39.100 /sleep Sets how long NetWare POA threads remain dormant when the CPU utilization threshold has been exceeded. The default is 100 milliseconds. See Section 38.5, “Optimizing CPU Utilization for the NetWare POA,” on page 562. NetWare POA Linux POA Windows POA Syntax: /sleep-milliseconds...
  • Page 140 See also /soap, /soapmaxthreads, /soapsizelimit, soapssl, and /soapthreads. 39.104 /soapsizelimit Sets the maximum amount of data that the POA can return in a single request from a SOAP client. The default is 1024 KB (1 MB), which is the recommended setting. NetWare POA Linux POA Windows POA...
  • Page 141 NetWare POA Linux POA Windows POA Syntax: /tcpthreads-number --tcpthreads number /tcpthreads-number Example: /tcpthreads-10 --tcpthreads 20 /tcpthreads-20 See also /primingmax. 39.108 /threads Specifies the maximum number of message handler threads the POA can create. The default is 8; valid values range from 1 to 30. See Section 38.2.1, “Adjusting the Number of POA Threads for Message File Processing,”...
  • Page 142 the Post Office Settings page in ConsoleOne. However, it is preferable to use the same user ID and password on all servers where the POA needs access. 602 GroupWise 7 Administration Guide...

This manual is also suitable for:

Groupwise 7 post office agent