13.3 Understanding Domain and Post Office Database Updates

Functionality enhancements in GroupWise 7 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.

You must update the primary domain first so that correct replication of GroupWise 7 information can take place as you update post offices and secondary domains. After you update the primary domain, you can update the primary domain’s post offices or you can update a secondary domain and its post offices. The following diagram illustrates this update sequence.

Figure 13-1 Update Must Occur in the Following Order: 1) Primary Domain, 2) Primary Domain’s Post Offices or Secondary Domain, 3) Secondary Domain’s Post Offices

To update a domain database, you run the GroupWise 7 Message Transfer Agent (MTA) against it. The first time the GroupWise 7 MTA runs against a domain, it rebuilds the domain database (wpdomain.db) so the database includes the records required for new GroupWise 7 information. The MTA uses a new domain dictionary file (gwdom.dc) to rebuild the database for use with GroupWise 7.

Likewise, to update a post office database, you run the GroupWise 7 Post Office Agent (POA) against it. The first time the GroupWise 7 POA runs against the post office, it rebuilds the post office database (wphost.db) so the database includes the new records required for GroupWise 7 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 7. A user cannot run a GroupWise 7 client until his or her post office has been updated.