How Do I Configure a GWIA on My Reload Server?

I have one domain and one post office and I want to set up a GWIA on my Reload server in case a disaster happens, and I want my GroupWise system to function as it did on the production server, being able to send and receive messages to and from the Internet.

The Reload server can host a GroupWise Internet Agent (GWIA). The GWIA can be installed and associated with a new Secondary Domain that will be installed on the Reload server.  Configuring any needed GroupWise components before a disaster happens will allow Reload to be a push-button Disaster Recovery solution.

Assumptions:

• Customer understands that adding a GWIA to the Reload server is just an option when it is not possible to have a GWIA loaded on any other server.

• Customer has set up, configured, and tested Disaster Recovery prior to a disaster.

• This article recommends installing GroupWise agents, installing ConsoleOne, and making changes in ConsoleOne.  GroupWise and ConsoleOne are not supported by GWAVA.  Issues with either GroupWise or ConsoleOne may be outside of a GWAVA support engineer's expertise.

• It is recommended placing the GWIA on its own domain somewhere in the production system.  The POA and/or MTA loaded on the Reload server can then communicate with the GWIA's domain.

• The reader is possesses a strong knowledge of installing and configuring GroupWise and managing it within ConsoleOne.

Prerequisites:

1. ConsoleOne (C1) will need to be installed on the Reload server, including the GroupWise snap-ins.  C1 is needed on the initial setup to create the domain and gateway as part of the production server's domain.  Authenticate against the server with the Groupwise primary domain on the production server when logging into the Reload C1.  This will allow all changes to be made to the primary domain.  Add all GroupWise domains, post offices, and the Reload server in DNS.

2. When an IP address is changed in C1 for a domain or post office, a request is sent to the changed agent and a response is sent back before the change actually takes effect.  If the network address is configured with the DNS name, then C1 just excepts the change.  If the IP addresses were used for all domains and post offices and a disaster happens, the IP addresses would have to be reconfigured to point to the Reload server for the domain and post office.  Because the GroupWise system is configured with DNS names, no additional changes will need to be made once the domain and gateway have been created.     

3. Set up a Software Distribution Directory (SDD) for GroupWise, on the Reload server.  The SDD can be placed in the new domain directory that will be installed on the Reload server.

4. eDirectory is not needed or required on the Reload server. 

Required Steps:

1.  In ConsoleOne, configure all MTAs and POAs with DNS names instead of IP addresses.

2.  Install and configure a new GroupWise secondary domain on the Reload server.  This domain will be a participating domain in the production GroupWise system. 

3. Install and configure a GWIA on the Reload server and specify the "Message Transfer Port" for all GWIAs on which to listen. 

This is important because the alternate GWIA (on the Reload server) can't be accessed without this configured. The message transfer port is configured in C1 | Properties of the GWIA | GroupWise tab | Network Address | Message Transfer: Port.  The GWIA will be associated with the secondary domain that was just created on the Reload server.

4. Configure the GroupWise primary domain to use an "Alternate Internet Agent for Outbound SMTP/MIME Messages". 

The "alternate GWIA" will be the one installed on the Reload server.  The alternate GWIA is configured in C1 |  Domain | Properties | GroupWise | Internet Addressing.  At the bottom of the screen is Alternate Internet Agent for outbound SMTP/MIME messages.  When the MTA can't communicate over the primary GWIA's MTP port, then the Alternate GWIA's MTP port will be used.

More details about the alternate GWIA is referenced in a Cool Solutions article.  This article covers additional steps that won't be needed for the Reload server but will help in understanding the purpose: Alternate GWIA.

5. The MX record will need to be modified to include the GWIA on the Reload server. 

The Reload GWIA can be given a higher number so that mail won't be sent to it unless the main GWIA with the lower number (which is a higher priority) can't be reached.  Don't configure the GWIA to load automatically - just have it installed and ready to load.

6. Reload has the ability to load scripts before and/or after the Disaster Recovery MTA/POA are loaded.  A script can be created that will load the GWIA when the Disaster Recovery MTA is loaded.

 

This article was originally published in the GWAVA knowledgebase as article ID 1519.