For detailed instructions on configuring GroupWise to work with Micro Focus Cluster Services, see Novell Cluster Services on Linux
in the GroupWise 2012 Interoperability Guide. The procedure for installing GroupWise 2014 differs from the GroupWise 2014 procedure in the following ways:
The GroupWise 2014 Installation Wizard is completely different from the GroupWise 2014 Installation program. Therefore, the specific installation instructions in Setting Up a New GroupWise System in a Linux Cluster
in the GroupWise 2012 Interoperability Guide no longer apply. There is no longer a Configure GroupWise for Clustering option for taking care of certain clustering configuration tasks. Those tasks are taken care of in other ways in GroupWise 2014.
Install the GroupWise Server component on each cluster node where a GroupWise agent will run for a domain or a post office.
Follow the instructions in Step 1 through Step 9 in Linux: Installing the GroupWise Server Software
in the GroupWise 2014 R2 Installation Guide.
IMPORTANT:Install the GroupWise Server component on all cluster nodes before setting up any domains or post offices. Do not start the GroupWise Installation Console at the end of the installation process.
In GroupWise 2014, the GroupWise Admin console replaces ConsoleOne as the GroupWise administration tool. The instructions that include ConsoleOne in the GroupWise 2012 Interoperability Guide can easily be adapted to apply to the GroupWise Admin console in GroupWise 2014. For more information, see Working with the GroupWise Administration Console
in GroupWise 2014 R2 Installation Guide and GroupWise Administration Console
in the GroupWise 2014 R2 Administration Guide.
You must configure the GroupWise Admin Service to function in a cluster, so that it keeps track of which cluster resources are available to it at each point in time. Configuring the GroupWise Admin Service for clustering ensures that files associated with domains and post offices are created on cluster volumes, rather than on individual cluster nodes.
|
File |
Standard Location |
Clustered location |
|---|---|---|
|
Domain SSL Certificate, MTA SSL Certificate, GWIA SSL Certificate |
/opt/novell/groupwise/certificates |
/groupwise/certificates (a peer to the domain folder) |
|
Post Office SSL Certificate, POA SSL Certificate |
/opt/novell/groupwise/certificates |
/groupwise/certificates (a peer to the post office folder) |
|
MTA Log Files |
/var/log/novell/groupwise/
domain.mta |
/groupwise/agents/logs (a peer to the domain folder) |
|
GWIA Log Files |
/var/log/novell/groupwise/
gwia.domain |
/groupwise/agents/logs (a peer to the domain folder) |
|
POA Log Files |
/var/log/novell/groupwise/
post_office.poa |
/groupwise/agents/logs (a peer to the post office folder) |
On each cluster node:
Run the following command to enable the GroupWise Admin Service to run in a clustering environment:
gwadminutil config -cluster enable
You should receive the following response:
Cluster: enabled Default Port: 9710
Use the following command to restart the GroupWise Admin Service.
rcgrpwise restart gwadminservice
Your GroupWise system is now ready to function in a cluster.
In the Installation console, when you are creating domains and post offices in a cluster, a few fields require cluster-specific information.
When you follow the instructions in Creating the Primary Domain
in the GroupWise 2014 R2 Installation Guide, pay special attention to the following fields:
In the Host field, specify the secondary IP address of the shared resource where you want to create the domain.
In the Domain Folder field, specify a folder on the shared resource where you want to create the domain.
When you follow the instructions in Step 2 through Step 8 in Adding a Post Office
in the GroupWise 2014 R2 Installation Guide, pay special attention to the following fields:
In the Owning Domain Host field, specify the secondary IP address of the shared resource where the owning domain is located.
In the Owning Domain Admin Port field, specify the port on the shared resource for the domain.
In the Host field, specify the secondary IP address of the shared resource where you want to create the post office.
In the Post Office Folder field, specify a folder on the shared resource where you want to create the post office.
The sample load and unload scripts that are provided in the following sections of Novell Cluster Services on Linux
in the GroupWise 2012 Interoperability Guide should not be used with GroupWise 2014:
Use the following scripts instead:
This sample cluster load script performs the following actions:
Establishes what to do for certain error conditions.
Creates the GroupWise agent services (if they do not already exist).
Starts the GroupWise Admin Service listeners with clustering enabled for the MTA and POA.
Starts the POA, MTA, and GWIA (in that order if all are present)
#!/bin/bash ./opt/novell/ncs/lib/ncsfuncs exit_on_error nss /poolact=DOM exit_on_error ncpcon mount DOM=254 exit_on_error add_secondary_ipaddress 151.155.136.248 exit_on_error ncpcon bind --ncpservername=DOM --ipaddress=151.155.136.248 exit_on_error novcifs --add '--vserver=".cn=DOM.ou=servers.o=novell.t=GW14-TREE."' --ip-addr=151.155.136.248
# Start gwadmin service exit_on_error /etc/init.d/grpwise start gwadminservice #create agent services exit_on_error /opt/novell/groupwise/admin/gwadminutil services -i /media/nss/DOM/utah exit_on_error /opt/novell/groupwise/admin/gwadminutil services -i /media/nss/DOM/utah/wpgate/gwia exit_on_error /opt/novell/groupwise/admin/gwadminutil services -i /media/nss/DOM/provo
#start admin service listeners exit_on_error /opt/novell/groupwise/admin/gwadmin-ipc start utah cluster exit_on_error /opt/novell/groupwise/admin/gwadmin-ipc start provo.utah cluster
#start GroupWise agents exit_on_error /etc/init.d/grpwise start utah exit_on_error /etc/init.d/grpwise start gwia.utah exit_on_error /etc/init.d/grpwise start provo.utah exit 0
This sample cluster unload script performs the following actions:
Stops the GroupWise Admin Service listeners for the MTA and POA
Stops the MTA, GWIA, and POA (in that order if all are present)
Lists error conditions that can be ignored
#!/bin/bash . /opt/novell/ncs/lib/ncsfuncs # Stop admin service listeners ignore_error /opt/novell/groupwise/admin/gwadmin-ipc stop utah ignore_error /opt/novell/groupwise/admin/gwadmin-ipc stop provo.utah
# Stop GroupWise agents ignore_error /etc/init.d/grpwise stop utah ignore_error /etc/init.d/grpwise stop gwia.utah ignore_error /etc/init.d/grpwise stop provo.utah
ignore_error novcifs --remove '--vserver=".cn=DOM.ou=servers.o=novell.t=GW14-TREE."' --ip-addr=151.155.136.248 ignore_error ncpcon unbind --ncpservername=DOM --ipaddress=151.155.136.248 ignore_error del_secondary_ipaddress 151.155.136.248 ignore_error nss /pooldeact=DOM exit 0
Follow the instructions in Testing Your Clustered GroupWise System on Linux
to verify that the GroupWise Admin console keeps track of the cluster resources that are currently available to it.