22.0 Manually Migrating the Internet Agent to Linux

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

As an alternative, you can use the GroupWise® Server Migration Utility to perform some of the steps for you. For more information, see GroupWise Server Migration Utility Installation and Migration Guide.

  1. Migrate the Internet Agent’s domain to Linux, as described in Section 21.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 (filename.crt) and a new key file (filename.key) for the Linux server and placing them in the /opt/novell/groupwise/agents/bin directory, as described in Step 9 in Section 21.2, 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 Internet Agent configuration process. For Linux server configurations to accomplish this, see Section 19.1.1, Making a Linux Server Visible from Windows.

  4. Install and configure the Linux Internet Agent, as described in Linux: Installing the Internet Agent Software.

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

    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 directory path in the Log File Path field, delete the NetWare® or Windows path, then click Apply.

      On Linux, Internet Agent 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 Internet Agent looks in the /opt/novell/groupwise/agents/bin directory 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 Internet Agent.

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

  7. From Windows, copy the queued Internet messages in the Internet Agent SMTP queues directory 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, as described in Section 19.2.1, Making a NetWare or Windows Server Visible from Linux.

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

    If you have used the SMTP Queues Directory field on the Server Directories property page of the Internet Agent object in ConsoleOne or the /dhome switch in the gwia.cfg file to place the queue directories outside the domain directory structure, then DBCopy did not copy the queue directories. Copy the queue directories from the NetWare or Windows server to their default location in the domain directory 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 directory.

  8. If Sendmail, Postfix, or any other SMTP daemon is enabled on your Linux server, disable it before starting the Internet Agent.

    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 Internet Agent to bind exclusively to the server IP address, as described in Binding the Internet Agent to a Specific IP Address, so that the Internet Agent IP address does not conflict with the default Postfix IP address of 127.0.0.1 (the loopback address).

  9. If you want to use the Internet Agent for POP3 and IMAP4 mail, make sure no POP3 or IMAP4 daemons are running on your Linux server.

  10. Make sure that the MTA for the domain is running.

  11. Start the Linux Internet Agent with or without a user interface, as described in Linux: Starting the Internet Agent.

    If the Internet Agent server console does not appear, or the Internet Agent Web console is not available in your Web browser, review the preceding steps to verify that all steps have been followed. For additional assistance, see Internet Agent Problems in Strategies for Agent Problems in the GroupWise 7 Troubleshooting 2: Solutions to Common Problems.

  12. When the Linux Internet Agent 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 directory structure from the NetWare or Windows server.

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

  14. If desired, uninstall the Internet Agent software to reclaim disk space on the NetWare or Windows server. See Uninstalling the NetWare GroupWise Agents or Uninstalling the Windows GroupWise Agents.