The GroupWise 2012 Monitor Installation program updates the existing Monitor installation, but it does not delete any parts of the previous version of Monitor that are no longer necessary. To avoid confusion in the future, you should remove the obsolete parts of Monitor from eDirectory and from the WebAccess server.
The GroupWise 2012 Monitor Installation program updates the existing Monitor installation, but it does not delete any parts of the previous version of Monitor that are no longer necessary. To avoid confusion in the future, you should remove the obsolete parts of Monitor from eDirectory and from the WebAccess server.
Because Monitor Application configuration information is no longer stored in Monitor eDirectory objects, you should delete the Monitor Application eDirectory objects from domains that you have updated to GroupWise 2012.
IMPORTANT:If you need to configure the Monitor Application in domains that have not yet been updated to GroupWise 2012, use the version of ConsoleOne that corresponds to the domain where the Monitor Application eDirectory objects are located. The GroupWise 2012 version of ConsoleOne cannot administer Monitor Application eDirectory objects.
In ConsoleOne, browse to and select the Domain object for the domain where you have updated to GroupWise 2012 and where Monitor is installed.
Review the properties of the existing Monitor Application objects, and make notes about any customizations that you have made:
GroupWise Monitor Application (GroupWiseMonitor)
GroupWise Monitor Provider (MonitorProvider)
Delete the existing Monitor Application objects.
Use the gwmonitor.cfg file to configure GroupWise 2012 Monitor, as described in Configuring the Monitor Application
in Monitor
in the GroupWise 2012 Administration Guide.
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 Monitor 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.
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 Monitor Application from the server.
For earlier versions of GroupWise, Tomcat 5 was locating 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 Monitor Application from the server.