Functionality enhancements in GroupWise 8 require the GroupWise domain and post office databases to be updated with new records and fields, similar to the schema extensions that are required for eDirectory. The following diagram illustrates the required update sequence.
Figure 15-1 Required Software Update Sequence
Update the primary domain first, so that correct replication of GroupWise 8 information can take place as you update post offices and secondary domains.
Update the post offices in the primary domain.
Update secondary domains
Update the post offices in the updated secondary domains.
To update a domain database, you run the GroupWise 8 Message Transfer Agent (MTA) against it. The first time the GroupWise 8 MTA runs against a domain, it rebuilds the domain database (wpdomain.db) so the database includes the records required for new GroupWise 8 information. The MTA uses a new domain dictionary file (gwdom.dc) to rebuild the database for use with GroupWise 8.
Likewise, to update a post office database, you run the GroupWise 8 Post Office Agent (POA) against it. The first time the GroupWise 8 POA runs against the post office, it rebuilds the post office database (wphost.db) so the database includes the new records required for GroupWise 8 information. The POA uses a new post office dictionary file (gwpo.dc), which it requests from the MTA, to rebuild the database for use with GroupWise 8. A user cannot run a GroupWise 8 client until his or her post office has been updated.
IMPORTANT:Before you update a secondary domain, you must wait until the update to the primary domain has run to completion. Before you update a post office, you must wait until the update to its domain has run to completion. Updating a large domain database can take 20 minutes or more. If you do not wait until the update runs to completion, you might encounter database versioning discrepancies. If such discrepancies occur, see GroupWise 8 Troubleshooting 2: Solutions to Common Problems.