13.0 Manually Migrating the Internet Agent to Linux

Manually migrating the Internet Agent (GWIA) to Linux includes migrating its domain to Linux, then installing the GWIA software on Linux, updating GWIA configuration information in ConsoleOne, and copying queued Internet messages from the NetWare or Windows server to the Linux server.

  1. Migrate the GWIA’s domain to Linux. See Section 12.0, Manually Migrating a Domain and Its MTA to Linux.

    If you are using SSL, migrating the domain and its MTA includes creating a new certificate file (file_name.crt) and a new key file (file_name.key) for the Linux server and placing them in the /opt/novell/groupwise/agents/bin folder, as described in Step 11 in Performing the Domain Migration.

  2. On the Linux server, become root in a terminal window.

  3. Make the Linux server visible from Windows.

    This is necessary in order to perform administration tasks from Windows ConsoleOne during the GWIA configuration process. For Linux server configurations to accomplish this, see Making a Linux Server Visible from Windows.

  4. Install and configure the Linux GWIA, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

  5. In ConsoleOne, update the GWIA property pages for the new location of the GWIA:

    1. On the Identification property page of the GroupWise tab, set Platform to Linux, then click Apply.

    2. On the Network Address property page of the GroupWise tab, specify the IP address or DNS hostname of the Linux server, then click Apply.

    3. On the Log Settings property page of the GroupWise tab, if you have specified a folder path in the Log File Path field, delete the NetWare or Windows path, then click Apply.

      On Linux, GWIA log files are stored in the /var/log/novell/groupwise/domain.gwia.

    4. On the SSL Settings property page of the GroupWise tab, if you have specified full paths in the Certificate File and SSL Key File fields, delete the NetWare or Windows path, then click Apply.

      On Linux, the GWIA looks in the /opt/novell/groupwise/agents/bin folder for certificate and key files by default.

    5. On the Server Directories tab, update the Conversion Directory and SMTP Queues Directory fields with corresponding Linux locations.

  6. On the NetWare or Windows server, stop the GWIA.

    Internet messages cannot be received into your GroupWise system while the GWIA is stopped.

  7. From Windows, copy the queued Internet messages in the GWIA SMTP queues folder on the NetWare or Windows server to the Linux server.

    NOTE:Because of Step 3 above, the Linux server is already visible from Windows. If you prefer to perform the copy operation from Linux, you must first make the NetWare or Windows server visible from Linux. See Making a NetWare or Windows Server Visible from Linux.

    The default GWIA SMTP queues folder is domain/wpgate/gwia. In this folder, four queue subfolders are used for SMTP processing: send, receive, result, and defer. When you migrated the domain to Linux, DBCopy copied these queue folders and their contents to the Linux server along with the rest of the domain folder structure, but additional Internet messages might have arrived since that time. Therefore, you need to copy these queue folders again now that the GWIA has been stopped.

    If you used the SMTP Queues Directory field on the Server Directories property page of the GWIA object in ConsoleOne or the /dhome switch in the gwia.cfg file to place the queue folders outside the domain folder structure, then DBCopy did not copy the queue folders. Copy the queue folders from the NetWare or Windows server to their default location in the domain folder structure or to another location of your choice on the Linux server. If you do not copy them to their default location, update the SMTP Queues Directory setting with the full path to the SMTP queues folder.

  8. (Conditional) If Sendmail, Postfix, or any other SMTP daemon is enabled on your Linux server, disable it before starting the GWIA.

    For example, use the following commands to stop and disable Postfix:

    /etc/init.d/postfix stop
    chkconfig postfix off

    As an alternative, you can configure the GWIA to bind exclusively to the server IP address, so that the GWIA IP address does not conflict with the default Postfix IP address of 127.0.0.1 (the loopback address).

    For instructions, see the following section in the GroupWise Administration Guide for your version of GroupWise:

  9. (Conditional) If you want to use the GWIA for POP3 and IMAP4 mail, ensure no POP3 or IMAP4 daemons are running on your Linux server.

  10. Ensure that the MTA for the domain is running.

  11. Start the Linux GWIA with or without a user interface, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

    If the GWIA server console does not appear, or the GWIA console is not available in your web browser, 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:

  12. When the Linux GWIA is running smoothly for the new domain location, and other GroupWise agents belonging to the domain have been migrated to Linux as needed, delete the old domain folder structure from the NetWare or Windows server.

  13. (Conditional) If the SMTP queue folder was located outside the domain folder structure, delete this folder and its contents from the NetWare or Windows server.

  14. (Optional) Uninstall the old GWIA software to reclaim disk space on the NetWare or Windows server.

    See Section 9.0, What’s Next.