36.1 Performing Basic POA Configuration

POA configuration information is stored as properties of its POA object in eDirectory™. The following topics help you modify the POA object in ConsoleOne® and change POA configuration to meet changing system configurations:

36.1.1 Creating a POA Object in eDirectory

When you create a new post office, one POA object is automatically created for it. You can set up additional 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 > Object.

  2. Double-click GroupWise Agent to display the Create GroupWise Agent dialog box.

    GroupWise agent dialog box

  3. Type a unique name for the new POA. The name can include as many as 8 characters. Do not use any of the following invalid characters in the name:

    ASCII characters 0-13

    Comma ,

    Asterisk *

    Double quote "

    At sign @

    Extended ASCII characters that are graphical or typographical symbols; accented characters in the extended range can be used

    Braces { }

    Parentheses ( )

    Colon :

    Period .

    You use this name with the /name startup switch when you start the new POA.

    The Type field is automatically set to Post Office.

  4. Select Define Additional Properties.

  5. Click OK.

    The POA object is automatically placed within the Post Office object.

  6. Review the information displayed for the first four fields on the Identification page to ensure that you are creating the correct type of Agent object in the correct location.

    POA Identification property page

  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.

  8. In the Platform field, select the platform (NetWare, Linux, or Windows) where the POA will run.

  9. Continue with Section 36.1.2, Configuring the POA in ConsoleOne.

36.1.2 Configuring the POA in ConsoleOne

The advantage to configuring the POA in ConsoleOne, as opposed to using startup switches in a POA startup file, is that the POA configuration settings are stored in eDirectory.

  1. In ConsoleOne, expand the eDirectory container where the Post Office object is located.

  2. Expand the Post Office object.

  3. Right-click the POA object, then click Properties.

The table below summarizes the POA configuration settings in the POA object properties pages and how they correspond to POA startup switches (as described in Section 39.0, Using POA Startup Switches). The table also includes settings on the Post Office object that correspond to POA startup switches.

Table 36-2 POA Configuration Settings

ConsoleOne Properties Pages and Settings

Corresponding Tasks and Startup Switches

POA Identification Page

 
  • Domain.PO
  • Distinguished Name
  • Name
  • Agent Type
  • Description
  • Platform

See Section 36.1.1, Creating a POA Object in eDirectory.

POA Agent Settings Page

 
  • Message File Processing

See Section 38.2.2, Configuring a Dedicated Message File Processing POA. See also /nomf, /nomfhigh, and /nomflow.
  • Message Handler Threads

See Section 38.2.1, Adjusting the Number of POA Threads for Message File Processing. See also /threads.
  • Enable TCP/IP (for C/S)

See Section 36.2.1, Using Client/Server Access to the Post Office and Section 38.1.3, Configuring a Dedicated Client/Server POA. See also /notcpip.
  • TCP Handler Threads

See Section 38.1.2, Adjusting the Number of Connections for Client/Server Processing. See also /tcpthreads.
  • Max Physical Connections
  • Max Application Connections

See Section 38.1.2, Adjusting the Number of Connections for Client/Server Processing. See also /maxphysconns and /maxappconns.
  • Enable Caching

See /nocache.
  • CPU Utilization (NLM)
  • Delay Time (NLM)

See Section 38.5, Optimizing CPU Utilization for the NetWare POA. See also /cpu and /sleep.
  • Max Thread Usage for Priming and Moves

See Section 36.2.7, Supporting Forced Mailbox Caching. See also /primingmax.
  • Enable IMAP
  • Max IMAP Threads

See Section 36.2.3, Supporting IMAP Clients. See also /imap and /imapmaxthreads.
  • Enable SOAP
  • Max SOAP Threads

See Section 36.2.4, Supporting SOAP Clients. See also /soap and /soapmaxthreads.
  • Enable SNMP
  • SNMP Community "Get" String

See Section 37.6, Using an SNMP Management Console. See also /nosnmp.
  • Disable Administration Task Processing

See /noada.
  • HTTP User Name
  • HTTP Password

See Section 37.2.1, Setting Up the POA Web Console. See also /httpuser and /httppassword.

Network Address Page

 
  • TCP/IP Address
  • IPX/SPX Address

See Section 36.2.1, Using Client/Server Access to the Post Office and Using TCP/IP Links between the Post Office and the Domain. See also /ip.
  • Proxy Server Address

See Section 36.3.1, Securing Client/Server Access through a Proxy Server.
  • Bind Exclusively to TCP/IP Address

See Section 36.1.4, Binding the POA to a Specific IP Address See also /ip.
  • Message Transfer

See Using TCP/IP Links between the Post Office and the Domain. See also /mtpinipaddr, /mtpinport, /mtpoutipaddr, /mtpoutport, /mtpsendmax, and /mtpssl.
  • HTTP

See Section 37.2.1, Setting Up the POA Web Console. See also /httpport and /httpssl.
  • Local Intranet Client/Server
  • Internet Proxy Client/Server

See Section 36.2.1, Using Client/Server Access to the Post Office and Using TCP/IP Links between the Post Office and the Domain. See also /port, /internalclientssl, and /externalclientssl.
  • IMAP

See Section 36.2.3, Supporting IMAP Clients. See also /imapport, /imapssl, and /imapsslport.
  • SOAP

See Section 36.2.4, Supporting SOAP Clients. See also /soapport and /soapssl.

QuickFinder Page

 
  • Enable QuickFinder Indexing
  • Start QuickFinder Indexing
  • QuickFinder Interval

See Section 38.3.1, Regulating Indexing and Section 38.3.2, Configuring a Dedicated Indexing POA. See also /qfbaseoffset, /qfbaseoffsetinminute, /qfinterval, /qfintervalinminute, and /noqf.

Maintenance Page

 
  • Enable Auto DB Recovery

See /norecover.
  • Maintenance Handler Threads

See Section 38.4.1, Adjusting the Number of POA Threads for Database Maintenance. See also /gwchkthreads and /nogwchk.
  • Perform User Upkeep
  • Start User Upkeep
  • Generate Address Book for Remote
  • Start Address Book Generation

See Section 36.4.3, Performing Nightly User Upkeep. See also /nuuoffset, /nonuu, /rdaboffset, and /nordab.
  • Disk Check Interval
  • Disk Check Delay

See Section 36.4.2, Scheduling Disk Space Management.

POA Log Settings Page

 
  • Log File Path
  • Logging Level
  • Max Log File Age
  • Max Log Disk Space

See Section 37.3, Using POA Log Files. See also /log, /logdays, /logdiskoff, /loglevel, and /logmax.

POA Scheduled Events Page

 
  • Disk Check Event

See Section 36.4.2, Scheduling Disk Space Management.
  • Mailbox/Library Maintenance Event

See Section 36.4.1, Scheduling Database Maintenance.

POA SSL Settings Page

 
  • Certificate File
  • SSL Key File
  • Password

See Section 36.3.3, Securing the Post Office with SSL Connections to the POA. See also /certfile, /keyfile, /keypassword.

Post Office Settings Page

 
  • Remote User Name
  • Remote Password

See /user and /password.

Post Office Client Access Settings Page

 
  • Lock Out Older GroupWise Clients
  • Minimum Client Release Version
  • Minimum Client Release Date

See Section 36.2.6, Checking What GroupWise Clients Are in Use. See also /gwclientreleasedate, /gwclientreleaseversion, and /enforceclientversion.
  • Enable Intruder Detection
  • Incorrect Logins Allowed
  • Incorrect Login Reset Time
  • Lockout Reset Time

See Section 36.3.5, Enabling Intruder Detection. See also /intruderlockout, /incorrectloginattempts, /attemptsresetinterval, and /lockoutresetinterval.

Post Office Security Page

 
  • LDAP Authentication

See Section 36.3.4, Providing LDAP Authentication for GroupWise Users. See also /ldapipaddr, /ldapport, /ldapuser, /ldappwd, /ldapuserauthmethod, /ldapdisablepwdchg, /ldapssl, /ldapsslkey,/ldaptimeout, and /noldapx. See also /ldapippooln, /ldappoolresettime, /ldapportpooln, /ldapsslpooln, and /ldapsslkeypooln

After you install the POA software, you can further configure the POA using a startup file. See Section 39.0, Using POA Startup Switches to survey the many ways the POA can be configured.

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.

If you need to change from one link protocol to another, some reconfiguration of the POA and its link to the domain is necessary.

NOTE:The Linux POA requires TCP/IP links between the post office and the domain.

Using TCP/IP Links between the Post Office and the Domain

To change from a mapped or UNC link to a TCP/IP link between a post office and its domain, you must perform the following two tasks:

Configuring the Agents for TCP/IP

  1. If the MTA in the domain is not yet set up for TCP/IP communication, follow the instructions in Configuring the MTA for TCP/IP.

  2. To make sure the POA is properly set up for TCP/IP communication, follow the instructions in Section 36.2.1, Using Client/Server Access to the Post Office.

    Only one POA per post office needs to communicate with the MTA. If the post office has multiple POAs, have a POA that performs message file processing communicate with the MTA for best performance. For information about message file processing, see Section 35.5, Role of the Post Office Agent.

  3. In ConsoleOne, browse to and right-click the POA object, then click Properties.

  4. Click GroupWise > Network Address to display the Network Address page.

    POA Network Address property page

  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 and /mtpinport startup switches in the POA startup file to set the incoming IP address and port.

Changing the Link between the Post Office and the Domain to TCP/IP

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

  2. In the drop-down list, select the domain where the post office resides.

  3. Click Post Office Links, then double-click the post office for which you want to change the link protocol.

  4. In the Protocol field, select TCP/IP.

    Edit Post Office Link dialog box

  5. Make sure the information displayed in the Edit Post Office Link dialog box matches the information on the Network Address page for the POA.

  6. Click OK.

  7. To exit the Link Configuration tool and save your changes, click File > Exit > Yes.

    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.

Corresponding Startup Switches You can also use the /mtpoutipaddr and /mtpoutport startup switches in the POA startup file to set the outgoing IP address and port.

Using Mapped or UNC Links between the Post Office and the Domain

To change from a TCP/IP link to a mapped or UNC link between a post office and its domain:

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

  2. In the drop-down list, select the domain where the post office resides.

  3. Click Post Office Links, then double-click the post office for which you want to change the link protocol.

  4. In the Protocol field, select Mapped or UNC.

  5. Provide the location of the post office in the format appropriate to the selected protocol.

  6. Click OK.

  7. To exit the Link Configuration tool and save your changes, click File > Exit > Yes.

    ConsoleOne then notifies the POA and MTA to restart using the new link protocol.

36.1.4 Binding the POA to a Specific IP Address

You can now cause the POA to bind to a specified IP address when the server where it runs uses multiple IP addresses. The specified IP address is associated with all ports used by the agent. Without an exclusive bind, the POA binds to all IP addresses available on the server.

  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.

    POA Network Address property page

  3. Select Bind Exclusively to TCP/IP Address, then click OK to save your change.

Corresponding Startup Switches You can also use the /ip and /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. For example, you might decide to run the POA on a different platform, or perhaps you want to move it to a server that has more memory.

  1. When moving the POA, pay special attention to the following details:

    • For a POA configured for client/server processing, reconfigure the POA object with the new IP address and port number for the POA to use on the new server. See Section 36.2.1, Using Client/Server Access to the Post Office.

    • For the NetWare POA, if it was originally on the same server where the post office is located and you are moving it to a different server, add the /dn switch or the /user and /password switches to the POA startup file to give the NetWare POA access to the server where the post office is located. You can also provide user and password information on the Post Office Settings page.

  2. Install the POA on the new server, as described in Installing GroupWise Agents in the GroupWise 7 Installation Guide.

  3. Start the new POA, as described in the following sections in the GroupWise 7 Installation Guide:

  4. Observe the new POA to see that it is running smoothly, as described in Section 37.0, Monitoring the POA.

  5. Stop the old POA.

  6. If you are no longer using the old server for any GroupWise agents, you can remove them to reclaim the disk space, as described in the following sections in the GroupWise 7 Installation Guide:

36.1.6 Adjusting the POA for a New Post Office Location

If you move a post office from one server to another, you also need to edit the POA startup file to provide the new location of the post office directory.

  1. Stop the POA for the old post office location if it is still running.

  2. Use an ASCII text editor to edit the POA startup file.

    The POA startup file is named after the post office name, plus a .poa extension.

    NetWare and Windows:

    Only the first 8 characters of the post office name are used in the filename. The startup file is typically located in the directory where the POA software is installed.

    Linux:

    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.

  4. Save the POA startup file.

  5. Start the POA for the new post office location, as described in the following sections in the GroupWise 7 Installation Guide:

  6. Adjust the link between the post office and the domain. See Section 41.1.7, Adjusting the MTA for a New Location of a Domain or Post Office.

36.1.7 Adjusting the POA Logging Level and Other Log Settings

When installing or troubleshooting the POA, a logging level of Verbose can be useful. However, when the POA is running smoothly, you can set the logging level down to Normal to conserve disk space occupied by log files.

  1. In ConsoleOne, browse to and right-click the POA object, then click Properties.

  2. Click GroupWise > Log Settings to display the Log Settings page.

    Log Settings property page

  3. Set the desired settings for logging.

    For more information about log settings and log files, see Section 37.3, Using POA Log Files.

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.