GroupWise Agent Overview
Each time you create a new post office, you must set up at least one Post Office Agent (POA) for it. Some of the POA's tasks in the post office include:
- Connecting GroupWise clients to mailboxes through network connections (TCP/IP, POP, IMAP)
- Sending messages to other users and delivering incoming messages into mailboxes
- Indexing messages and documents to support the Find feature in the GroupWise clients
- Managing disk space usage in the post office and controlling the size of messages that users are allowed to send and receive
Each time you create a new domain, you must set up a Message Transfer Agent (MTA) for it. Some of the MTA's tasks in the domain include:
- Routing user messages between post offices and domains
- Routing administration messages throughout the GroupWise system so that databases are kept in sync
- Synchronizing GroupWise user information with Novell eDirectoryTM user information
The POA requires direct access to the post office directory. The MTA requires direct access to the domain directory. The preferred way to fulfil this requirement is to install each agent on the same server with its directory. Running an agent locally on the same server where its directory and database are located simplifies network connections, because no remote login is required. In addition, it reduces network traffic and protects database integrity. The following diagram illustrates direct access:
However, if necessary, you can install the agent on a different server from its directory. This requires the agent to have a direct link (mapped drive, UNC path, or file system mount) to its directory on the remote server in order to function. The following diagram illustrates the direct links:
To route user and administration messages to the post office, the MTA requires a direct link (or direct access) to the post office directory, or a TCP/IP link to the POA for the post office. The following diagram illustrates the alternatives:
