9.7 Merging a Domain into Your GroupWise System

In order to merge an external domain into the local GroupWise system as a new secondary domain, the external domain must be the only domain in the other GroupWise system. For more information see Section 9.6, Releasing a Domain from Your GroupWise System.

This task requires direct file access to both domain databases. For that reason, it is not available in the GroupWise Admin console, which provides direct file access to one domain database through the Admin Service for that domain. Instead, you use the GroupWise Administration Utility (GWAdminUtil) to perform the task.

  1. Stop the GroupWise agents and the GroupWise Admin Service for both domains.

  2. On your local machine, provide folder access to both the primary domain database and the secondary domain database.

  3. Use one of the following commands to merge the external GroupWise domain into the local GroupWise system:

    gwadminutil merge -p /path_to_local_primary_domain 
                      -db /path_to_external_primary_domain
    
    gwadminutil merge -mergesync -p /path_to_local_primary_domain 
                      -db /path_to_external_primary_domain
    

    The -mergesync option establishes external system synchronization between the local GroupWise system and any other external systems that were syncing with the external primary domain.

  4. On the new secondary domain server, install a new server certificate so that the local Admin Service can communicate with the primary domain Admin Service:

    gwadminutil certinst -db /path_to_secondary_domain 
                         -ca ip_address_of_primary_domain_server:9710 
                                                 -a admin_user_name -p
    
  5. Wait for replication of the domain information to the post office.

    On each post office server, you can use the following command to view the owning domain name in the post office database:

    gwadminutil dbinfo /path_to_post_office
    
  6. On each post office server, install a new server certificate so that the local Admin Service can communicate with the primary domain Admin Service:

    gwadminutil certinst -db /path_to_post_office 
                         -ca ip_address_of_primary_domain_server:9710 
                         -a admin_user_name -p
    
  7. Start the GroupWise agents and the GroupWise Admin Service for both domains.

NOTE:The principles for merging GroupWise systems are the same for GroupWise 2014 R2 as they are for GroupWise 2012. For additional information on this topic, see “Merging GroupWise Systems” in the GroupWise 2012 Multi-System Administration Guide.