The following types of information are stored in the domain:
No messages are stored in the domain, so GroupWise client users do not need access to the domain directory. The only person who needs file access to the domain directory is the GroupWise administrator.
The domain database (wpdomain.db) contains all administrative information for the domain, including:
Address information about all GroupWise objects (such as users, resources, post offices, and gateways in the domain)
System configuration and linking information for the domain’s MTA
Address and message routing information to other domains
The first domain you create is the primary domain. In the primary domain, the wpdomain.db file contains all administrative information for your entire GroupWise system (all its domains, post offices, users, and so on). Because the wpdomain.db file in the primary domain is so crucial, you should back it up regularly and keep it secure. See Section 31.1, Backing Up a Domain.
You can re-create your entire GroupWise system from the primary domain wpdomain.db file; however, if the primary domain wpdomain.db file becomes unusable, you can no longer make administrative updates to your GroupWise system.
Secondary domains are automatically synchronized to match the primary domain.
Each domain contains agent input/output queues where messages are deposited and picked up for processing by the MTA.
For a mapped or UNC link between domains, the MTA requires read/write access rights to its input/output queues in the other domains. For a TCP/IP link, no access rights are required because messages are communicated by way of TCP/IP.
For illustrations of the processes presented below, see Section 40.6, Message Flow between Domains and Post Offices.
The MTA input queue in the local domain (domain\wpcsin) is where MTAs for other domains deposit user messages for the local MTA to route to local post offices or to route to other domains. Thus the MTA input queue in the local domain is the output queue for the MTAs in many other domains.
The MTA does not have an output queue for user messages in the local domain. Because its primary task is routing messages, the local MTA has output queues in all post offices in the domain. See POA Input Queue in the Post Office. The local MTA also has output queues in all domains to which it is directly linked.
The MTA output queue in the local domain (domain\wpcsout\ads) is where the MTA deposits administrative messages from other domains for the MTA admin thread to pick up.
The MTA admin thread input queue (domain\wpcsout\ads) is, of course, the same as the MTA output queue in the local domain. The MTA admin thread picks up administrative messages deposited in the queue by the MTA and updates the domain database.
The MTA admin thread output queue (domain\wpcsin) is the same as the MTA input queue in the local domain. The MTA admin thread deposits administrative messages in the queue for replication to other domains.
Gateways are installed and configured at the domain level of your GroupWise system. For a list of gateways, see the GroupWise Gateways Documentation Web site.