After you have set up the primary domain and initial post office, as described in Section 3.2, Setting Up a New GroupWise System in a Cluster, you can create additional secondary domains as needed.
To create a new secondary domain in a clustering environment:
Map a drive to the GroupWise volume for the domain (System Clustering Worksheet item 7) where the new secondary domain will be created.
The GroupWise volume name will be cluster_volume. For assistance with mapping a drive to a cluster-enabled volume, see Configuring Short Name Resolution.
Manually create the domain directory (System Clustering Worksheet item 10).
This step is not required, but in a clustered environment, Step 5 is easier if the domain directory already exists.
If you selected vol:\system on GroupWise volume as the agent installation location (under Agent Clustering Worksheet item 1), create the vol:\system directory on the GroupWise volume accessed in Step 1.
or
If you selected sys:\system on each node, decide which node you will install the agents to first.
In ConsoleOne, connect to the primary domain in your GroupWise system, as described in Connecting to a Domain
in Domains
in the GroupWise 8 Administration Guide.
Create the new domain, following the steps provided in Creating the New Domain
in Domains
in the GroupWise 8 Administration Guide. Keep in mind the following cluster-specific details:
Use the Domain Worksheet you filled out in Section 2.3, Planning a New Clustered Domain to fill in the fields in the Create GroupWise Domain dialog box.
In the field, be sure to browse through the drive you mapped in Step 1 to the domain directory you created in Step 2 above.
In the field, link the new domain to the primary domain of your GroupWise system.
The option is selected by default. Select . Refer to the Agent Clustering Worksheet that you filled out in Planning Secondary IP Addresses and Cluster-Unique Port Numbers for Agents in the Cluster for the secondary IP address and cluster-unique port numbers that you need to specify in order to configure the link.
Use the Link Configuration tool to change the links from the new domain to all other domains in the cluster to direct TCP/IP links, following the steps provided in Changing the Link Protocol between Domains to TCP/IP
in Message Transfer Agent
in the GroupWise 8 Administration Guide.
Although a complete mesh link configuration is the most efficient, it might not be feasible in all situations. Set up as many direct TCP/IP links as possible for best MTA performance in the cluster.
Make sure you are still connected to the primary domain.
Rebuild the domain database for the new domain, following the steps provided in Rebuilding Domain or Post Office Databases
in Databases
in the GroupWise 8 Administration Guide. Be sure to browse to the database location (under System Clustering Worksheet item 10) through the virtual server that was created when you cluster-enabled the GroupWise volume.
The database rebuild is necessary in order to transfer the MTA configuration information and the domain link information into the secondary domain database, because the MTA for the new domain is not yet running.
Continue with Creating a New Post Office in a Cluster.