On the NetWare or Windows server, stop the MTA for the domain.
(Conditional) If the domain has gateways, stop the gateways.
In the /opt/novell/groupwise/agents/bin folder, use DBCopy to copy the domain folder from the NetWare or Windows server to the new folder on the Linux server.
./dbcopy -m -d /domain_folder /destination_folder
The -m switch indicates that DBCopy is being used for migration to Linux. This ensures that all folder names and file names are in lower case.
The -d switch indicates that you are migrating a domain.
The domain_folder variable includes the Linux mount location (for example, /mnt), the mount point folder, and the full path to the domain folder on the NetWare or Windows server.
The destination_folder variable is the folder you created on the Linux server in Step 5 in Preparing for the Domain Migration.
DBCopy creates a log file named mmddgwbk.nnn. The first four characters represent the date. A three-digit extension allows for multiple log files created on the same day. The log file is created at the root of the destination domain folder. Include the -v switch in the dbcopy command to enable verbose logging for the domain migration.
DBCopy is typically used for backing up your GroupWise system, but when you use the -m switch to migrate a domain, it changes folder names to lowercase as required on Linux and copies the message queue folders as well as the GroupWise databases in the domain.
(Conditional) If you are using the /work startup switch to place the MTA working folder (mslocal) outside the domain folder structure, relocate the folder and rename files:
Copy the mslocal folder to the Linux server so that no messages en route between users are lost.
In the mslocal folder structure, rename files and folders that contain uppercase letters to all lowercase.
(Conditional) If your Linux environment includes the X Window System, run the GroupWise Installation program to install the Linux MTA for the domain, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:
GroupWise 2012: Installing the Linux GroupWise Agents
GroupWise 8: Installing the GroupWise Agents on Linux
(Conditional) If the X Window System is not available, run the text-based GroupWise Installation program, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:
If you need to perform the installation from a remote location, you can use ssh to access the remote Linux server. Copy the GroupWise software image or software distribution directory to the server where you have migrated the domain, then run the text-based Installation program to install the MTA on the Linux server.
Change to the /opt/novell/groupwise/agents/bin folder.
(Conditional) If the X Window System is available, enter the following command to start the Linux MTA to verify that it runs for the domain in the new location:
./gwmta --show --home /domain_folder
The --show switch starts the MTA with a user interface. The --home switch provides the location of the domain.
You should see the MTA server console described in the following section of the GroupWise Installation Guide for your version of GroupWise:
GroupWise 2012: Installing GroupWise Components Using the Text-Based Installation Program
GroupWise 8: Starting the Linux Agents with a User Interface
If the MTA server console does not appear, review the preceding steps to verify that all steps have been followed. For additional assistance, see the following section of GroupWise Troubleshooting 2: Solutions to Common Problems for your version of GroupWise:
GroupWise 2012: Message Transfer Agent Problems
GroupWise 8: Message Transfer Agent Problems
(Conditional) If the X Window system is not available:
Enter the following command to start the Linux MTA to verify that it runs for the domain in the new location:
./gwmta --home /domain_folder --ip mta_server_ip_address --httpport 7180
The --home switch provides the location of the domain. The --ip switch provides the IP address of the server where the MTA is running. The -httpport switch enables the MTA console and provides the port number.
To simplify this test, do not use an SSL connection.
In an appropriate environment, open a web browser and display the following URL:
http://mta_server_ip_address:7180
You should see the MTA console described in the following section of the GroupWise Installation Guide for your version of GroupWise:
GroupWise 2012: Monitoring the Linux GroupWise Agents from Your Web Browser
GroupWise 8: Monitoring the Linux GroupWise Agents from Your Web Browser
If the MTA console does not appear, review the preceding steps to verify that all steps have been followed. For additional assistance, see the following section of GroupWise Troubleshooting 2: Solutions to Common Problems for your version of GroupWise:
GroupWise 2012: Message Transfer Agent Problems
GroupWise 8: Message Transfer Agent Problems
After verifying that the MTA starts successfully for the domain in the new location on Linux, stop the MTA, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:
GroupWise 2012: Stopping the Linux GroupWise Agents
GroupWise 8: Stopping the Linux GroupWise Agents
(Conditional) If you plan to use SSL on Linux, create new certificate and key files for the Linux server and place them in the /opt/novell/groupwise/agents/bin folder, the default location where the MTA looks for certificate and key files.
For instructions on creating certificate and key files, see the following section of the GroupWise Administration Guide for your version of GroupWise:
GroupWise 2012: Server Certificates and SSL Encryption
GroupWise 8: Server Certificates and SSL Encryption
Continue with Reconfiguring the Domain in ConsoleOne.