Merging Two External GroupWise Systems

This walkthrough takes you through the process of merging two GroupWise systems. The primary domain in System 2 will become subordinate to the primary domain in System 1, which means it will eventually be converted to a secondary domain.

Note

Only primary domains can be merged with an existing system, and they can be merged only if they do not own any secondary domains. If you need to merge a multidomain system with yours, you must first have that system release all of its domains. Refer to the section "Releasing a Secondary Domain to Create a New GroupWise System," earlier in this chapter.

The Merge Scenario

The WorldWide Widgets Corporation wants to acquire the ACME Corporation. (Forget, for just a moment, that you released the ACME system in an earlier walkthrough. Or perhaps you could assume that this is a real-life example of a confused corporate reorganization.)

They both have GroupWise systems. It is natural for them to merge their two systems. This will cause the MFG domain to be a GroupWise secondary domain to the CORP primary domain. WorldWide Widgets and ACME will still keep separate trees, however. Remember that System 1 is WorldWide Widgets' system, and System 2 is ACME's system.

Creating System Definitions for Merged Systems

From System 1, follow the steps to create a definition for System 2. From System 2, follow the steps to create a definition for System 1. All the steps are in previous sections of this chapter. Follow all the steps in the sections "Creating System Definitions for Synchronizing," "Creating MTA Connectivity," and "Testing System Connectivity."

On System 2 (the system that will be merged), follow all the steps necessary to release its secondary domains. The steps for doing this are described in the section "Releasing a Secondary Domain to Create a New GroupWise System."

Tip

The reason for releasing domains is that you cannot merge another GroupWise system when it contains multiple domains. You must pare it down to a single primary domain to merge it into a different GroupWise system.

Now, connect to System 1's primary domain (the domain that will assimilate System 2). Log in to the eDirectory tree that houses the primary domain for System 2. In this scenario it's the ACME_INC TRee, and the domain is the MFG domain.

Highlight the external domain that represents the primary domain that you are assimilating to become a new secondary domain. Select Tools, GroupWise Utilities, System Maintenance. Choose the option Merge External Domain and then click the Run button. Follow the prompts of the Merge External Domain Wizard. When you get the prompt Update eDirectory Objects, choose No, at least in this scenario in which the MFG domain will still be contained in the ACME_INC tree.

When prompted to do so, bring down the MTA for both of the primary domains. Proceed through the wizard, and merge the two systems.

Tip

If you get the Merge Domain Error, there is an MTA or a gateway still up that is accessing the WPDOMAIN.DB, or ConsoleOne is tripping over its own shoelaces (this is often the case in scenarios such as this). The solution is simple. Make sure that you are connected to System 1's primary domain, and then exit ConsoleOne. Load ConsoleOne, and then attempt the merge again. If the problem persists, someone else is accessing the WPDOMAIN.DB for the primary domain for either System 1 or System 2. You can use Monitor on NetWare and check for File, Open Lock activity, and then browse to the WPDOMAIN.DB file to determine who is accessing the database.

Synchronizing Objects

Merging two systems is rather easy. However, the merge does not broadcast the new objects brought in from System 2 to the rest of System 1. Also, the domains and post offices originally associated with System 2 don't have a clue about the objects in their new system.

To get all domains and post offices acquainted with the new, larger system, you must perform a top-down rebuild. This can be a big task. A top-down rebuild requires that all GroupWise domains and post offices be rebuilt. Here are some important pointers for top-down rebuilds:

• Before rebuilding a secondary domain, synchronize it with the primary domain. See the beginning of this walkthrough for instructions on how to do this.

• Rebuilding a GroupWise domain or GroupWise post office database requires exclusive access to that database.

• For more information about rebuilding domain and post office databases, refer to Chapter 22, "Troubleshooting the GroupWise Directory."

After the top-down rebuild, all GroupWise domains and post offices should be aware of the new domains and post offices.