22.2 Cleaning Up the WebAccess Server after Updating to GroupWise 2012

The GroupWise 2012 WebAccess Installation program updates the existing WebAccess installation, but it does not delete any parts of the previous version of WebAccess that are no longer necessary. To avoid confusion in the future, you should remove the obsolete parts of WebAccess from eDirectory and from the WebAccess server.

22.2.1 Exporting WebAccess Access Control Information

If you used classes of service to control user access to WebAccess in an earlier version of GroupWise, you can export your existing access control information for use with GroupWise 2012 WebAccess.

  1. In ConsoleOne with the GroupWise 2012 snap-ins installed, browse to and select the Domain object where the WebAccess eDirectory objects are located.

  2. Right-click the WebAccess Agent object, then click Properties.

  3. Click Access Control.

  4. Review your existing access control information to ensure that it is current and accurate.

  5. Click Export, then close the Access Control tab.

  6. Change to the WebAccess Gateway directory (domain/wpgate/webac80a), then list the contents of the directory.

    A gwac.xml file has been created that captures your existing WebAccess access control information in XML format for use with GroupWise 2012.

  7. Copy the gwac.xml file to the same directory where the GroupWise 2012 webacc.cfg file is located.

  8. Restart Tomcat to implement the same access control for GroupWise 2012 WebAccess that you had for your earlier version of GroupWise.

    OES 11:

    		 
    rcnovell-tomcat6 stop
rcnovell-tomcat6 start

    OES 2 Linux:

    		 
    rcnovell-tomcat5 stop
rcnovell-tomcat5 start

    SLES 11:

    		 
    rctomcat6 stop
rctomcat6 start

    SLES 10:

    		 
    rctomcat5 stop
rctomcat5 start

    Windows:

    1. At the Windows server, click Start > Administrative Tools > Services.

    2. Right-click Tomcat 6, then click Restart.

  9. For instructions on using the gwac.xml file in the future as you access control needs change, see Controlling WebAccess Usage in WebAccess in the GroupWise 2012 Administration Guide.

22.2.2 Deleting Obsolete WebAccess eDirectory Objects

Because WebAccess configuration information is no longer stored in WebAccess eDirectory objects, you should delete the WebAccess eDirectory objects from domains that you have updated go GroupWise 2012.

IMPORTANT:If you need to configure WebAccess in domains that have not yet been updated to GroupWise 2012, use the version of ConsoleOne that corresponds to the domain where the WebAccess eDirectory objects are located. The GroupWise 2012 version of ConsoleOne cannot administer WebAccess eDirectory objects.

  1. In ConsoleOne, browse to and select the Domain object for the domain where you have updated WebAccess.

  2. Review the properties of the existing WebAccess objects, and make notes about any customizations that you have made:

    • WebAccess Agent (WEBAC80A)

    • WebAccess Application (GroupWiseWebAccess)

    • WebPublisher Application (GroupWiseWebPublisher)

      NOTE:WebPublisher is not part of GroupWise 2012. To continue using WebPublisher, maintain an existing domain with the existing version of WebAccess to support your WebPublisher needs until comparable functionality becomes available.

    • GroupWise Service Provider (GroupWiseProvider)

    • LDAP Service Provider (LDAPProvider)

    • Document Service Provider (GroupWiseDocumentProvider)

  3. Delete the obsolete WebAccess objects from eDirectory.

  4. Use the webacc.cfg file to configure GroupWise 2012 WebAccess.

    Many of the customizations that could be made in the properties of the WebAccess eDirectory objects can be made in the webacc.cfg file, as described in Configuring the WebAccess Application in WebAccess in the GroupWise 2012 Administration Guide.

  5. Continue with Removing the WebAccess Agent Software.

22.2.3 Removing the WebAccess Agent Software

Because the GroupWise 2012 WebAccess Application communicates directly with the POA, the WebAccess Agent is no longer part of GroupWise. Therefore, it must be removed from the WebAccess server.

On Linux

For a listing of the software files associated with the GroupWise 8 WebAccess Agent on Linux, see Linux WebAccess Agent Installation Directory in Directory Structure Diagrams inGroupWise 8 Troubleshooting 3: Message Flow and Directory Structure.

The Linux GroupWise 2012 WebAccess Installation program automatically removes obsolete WebAccess Agent files from these directories.

On Windows

For a listing of the software files associated with the GroupWise 8 WebAccess Agent on Windows, see Windows WebAccess Agent Installation Directory in Directory Structure Diagrams inGroupWise 8 Troubleshooting 3: Message Flow and Directory Structure.

The Windows GroupWise 2012 WebAccess Installation program does not delete the obsolete WebAccess Agent service or the directory where the obsolete WebAccess Agent software is installed.

To remove the WebAccess Agent service and software from the WebAccess server:

  1. Stop the WebAccess Agent:

    net stop "WebAccess (webaccess_agent_name)"

  2. Remove the WebAccess Agent service:

    sc delete "WebAccess (webaccess_agent_name)"

  3. Delete the following directory:

    c:\Program Files\Novell\GroupWise Server\WebAccess

22.2.4 Removing Obsolete WebAccess Application Software

All GroupWise Web-based components (WebAccess, Calendar Publishing Host, and Monitor) rely on a platform-specific Web server and on Tomcat for their Web-based functionality.

GroupWise 2012 WebAccess uses Tomcat 6 instead of Tomcat 5 on OES 11, SLES 11, and Windows. If no other non-GroupWise Web services are using the old version of Tomcat, you can remove it from the Web server.

NOTE:Tomcat 5 is still used on OES 2 Linux and SLES 10, so no cleanup is required on these Linux versions.

On OES 11 and SLES 11

For earlier versions of GroupWise, Tomcat 5 is located in the following platform-specific directory:

OES:

 
/var/opt/novell/tomcat5

SLES:

 
/srv/www/tomcat5

If a Tomcat 5 directory exists on a Linux server that you have updated to GroupWise 2012, use YaST to remove Tomcat 5. This also removes the obsolete WebAccess Application from the server.

On Windows

For earlier versions of GroupWise, Tomcat 5 is located in the following directory:

c:\novell\groupwise\tomcat5.5

If a Tomcat 5 directory exists on a Windows server that you have updated to GroupWise 2012, delete the Tomcat 5 directory in order to remove the obsolete WebAccess Application from the server.

22.2.5 Accommodating Earlier GroupWise Versions

As you update your GroupWise system to GroupWise 2012, you might not be able update all post offices at one time. The GroupWise 2012 WebAccess Application cannot communicate with an earlier version of the POA. When a user whose post office is still on a earlier GroupWise version tries to log in to WebAccess, the WebAccess Application can redirect that user to an earlier version of WebAccess to match the post office where the user’s mailbox is located.

To provide a redirection URL:

  1. Open the webacc.cfg file in a text editor.

  2. Search to find the following line:

    #Redirect.url=http://gw8.novell.com/gw/webacc

  3. Remove the pound sign (#) to activate the setting.

  4. Replace the sample URL with the URL for an earlier version of GroupWise WebAccess.

  5. Save the webacc.cfg file.

  6. Restart Tomcat.

    OES 11:

    		 
    rcnovell-tomcat6 stop
rcnovell-tomcat6 start

    OES 2 Linux:

    		 
    rcnovell-tomcat5 stop
rcnovell-tomcat5 start

    SLES 11:

    		 
    rctomcat6 stop
rctomcat6 start

    SLES 10:

    		 
    rctomcat5 stop
rctomcat5 start

    Windows:

    1. At the Windows server, click Start > Administrative Tools > Services.

    2. Right-click Tomcat 6, then click Restart.