14.2 Manually Migrating the WebAccess and WebPublisher Applications to Linux

NOTE:GroupWise 2012 does not include WebPublisher.

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

  2. Make sure that the Linux server already has Apache and Tomcat configured and running successfully and that you know the full path to the Apache and Tomcat root directories.

  3. (Conditional) If your Linux environment includes the X Window System, run the GUI GroupWise Installation program to install and configure the Linux WebAccess Application, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

  4. (Conditional) If the X Window System is not available, run the text-based GroupWise Installation program instead, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

    IMPORTANT:On the WebAccess Objects page, specify a new context for the WebAccess Application objects, so that the old objects are retained.

    If you need to perform the installation from a remote location, you can use ssh to access the remote Linux server. Copy the GroupWise DVD or software distribution directory to the server where you have migrated the domain, then run the text-based Installation program to install the WebAccess Application on the Linux server.

  5. (Conditional) If you want to use WebPublisher on Linux, perform the manual configuration described in the following section of the GroupWise Installation Guide for your version of GroupWise:

  6. In ConsoleOne, review the property pages for the old WebAccess Application objects:

    • GroupWise WebAccess

    • Novell Speller

    • LDAP Provider

    • GroupWise Provider

    • GroupWise Document Provider

  7. Transfer any settings that you have customized on the old WebAccess Application objects to the new WebAccess Application objects.

  8. (Conditional) If you installed WebPublisher, review the property pages of the old GroupWise WebPublisher object, then transfer any settings that you have customized on the old GroupWise WebPublisher object to the new GroupWise WebPublisher object.

  9. (Conditional) If you have customized any WebAccess or WebPublisher template files, copy the customized template files from the old Web server to the following directories on the Linux Web server:

    /var/opt/novell/gw/WEB-INF/classes/com/novell/webaccess/templates
/var/opt/novell/gw/WEB-INF/classes/com/novell/webpublisher/templates

  10. Stop and then start Apache and Tomcat, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:

  11. Verify that the new WebAccess Application is communicating successfully with the existing WebAccess Agent by accessing your GroupWise mailbox through the WebAccess client:

    http://new_web_server_address/gw/webacc

  12. To keep users’ existing browser bookmarks from being broken, redirect the old WebAccess and WebPublisher URLs to the new WebAccess and WebPublisher URLs:

    1. (Conditional) If your old Web server was Apache on NetWare:

      1. Change to the conf subdirectory of the Apache root directory (for example, \apache2\conf).

      2. Edit the Apache configuration file for GroupWise.

        On NetWare 6, the Apache configuration file is gwapache.conf. On NetWare 6.5, the Apache configuration file is gwapache2.conf.

      3. Add the following line:

        redirect permanent /servlet/webacc 
                        http://web_server_address/gw/webacc

      4. If you use WebPublisher, add the following additional line:

        redirect permanent /servlet/webpub 
                        http://web_server_address/gw/webpub

      5. Save the file, then exit the editor.

      6. Restart Apache to put the redirections into effect.

    2. (Conditional) If your old Web server was Internet Information Server (IIS) on Windows:

      1. Change to the netpub\wwwroot subdirectory of the IIS root directory (for example, c:\inetpub\wwwroot).

      2. Create a subdirectory named servlet.

      3. Under the servlet subdirectory, create a subdirectory named webacc.

      4. If you use WebPublisher, create a second subdirectory named webpub.

      5. In IIS Manager, expand the tree in the left pane to display Default Web Site under Web Sites.

        Under Default Web Sites, you should see the servlet subdirectory you created in Step 12.b.b

      6. Expand the servlet subdirectory to display the webacc subdirectory (and optionally, the webpub subdirectory) that you created in Step 12.b.c.

      7. Right-click the webacc subdirectory, then click Properties.

      8. Click Directory, select A Redirection to a URL, then type /gw/webacc in the associated field.

      9. Select A Permanent Redirection for This Resource, then click OK to save your changes.

      10. If you use WebPublisher, repeat Step 12.b.g through Step 12.b.i, using webpub in place of webacc.

      11. Restart the IIS Web server to put the redirections into effect.

  13. Notify users of the new WebAccess and WebPublisher URLs so that users can update their browser bookmarks if they want to.

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

    See Section 9.0, What’s Next.