5.2 Manually Migrating the WebAccess and WebPublisher Applications to Linux

NOTE:GroupWise 2018 does not include WebPublisher.

On the Linux server, become root in a terminal window.
Ensure 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 folders.
(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:
- GroupWise 2012: Linux: Setting Up GroupWise WebAccess
- GroupWise 8: Installing and Configuring the WebAccess Application and WebPublisher Application
(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:
- GroupWise 2012: Installing GroupWise Components Using the Text-Based Installation Program
- GroupWise 8: Installing the GroupWise Agents Using the Text-Based Installation Program
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 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 WebAccess Application on the Linux server.
(Conditional) If you want to use WebPublisher on Linux, perform the manual configuration described in Configuring WebPublisher in the GroupWise 8 Installation Guide.
In ConsoleOne, review the property pages for the old WebAccess Application objects:
- GroupWise WebAccess
- Novell Speller
- LDAP Provider
- GroupWise Provider
- GroupWise Document Provider
Transfer any settings that you have customized on the old WebAccess Application objects to the new WebAccess Application objects.
(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.
(Conditional) If you have customized any WebAccess or WebPublisher template files, copy the customized template files from the old web server to the following folders 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
```
Stop and then start Apache and Tomcat, as described in the following section of the GroupWise Installation Guide for your version of GroupWise:
- GroupWise 2012: Installing the Linux WebAccess Software
- GroupWise 8: Restarting the Web Server
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
```
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 subfolder of the Apache root folder (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 subfolder of the IIS root folder (for example, c:\inetpub\wwwroot).
  2. Create a subfolder named servlet.
  3. Under the servlet subfolder, create a subfolder named webacc.
  4. If you use WebPublisher, create a second subfolder 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 subfolder you created in Step 12.b.b
  6. Expand the servlet subfolder to display the webacc subfolder (and optionally, the webpub subfolder) that you created in Step 12.b.c.
  7. Right-click the webacc subfolder, 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.
Notify users of the new WebAccess and WebPublisher URLs so that users can update their browser bookmarks if they want to.
(Optional) Uninstall the old WebAccess Application software to reclaim disk space on the NetWare or Windows server.

See Section 7.0, What’s Next.