Upgrading GroupWise Monitor

Upgrading the GroupWise Monitor is essentially installing the new GroupWise software for the monitor agent and optionally the Monitor application. If you have a GroupWise 5.5EP Monitor (where have you been???), you will need to totally reinstall your Monitor from scratch. As you know, GroupWise Monitor is similar to the GroupWise WebAccess as it existed prior to GroupWise 2012, in that it has two components, the GroupWise Monitor “Agent” and a web application that can be installed on your web server. (Of course, as we discussed earlier, beginning with GroupWise 2012, GroupWise WebAccess no longer has an “Agent” and is driven entirely by the WebAccess Application and SOAP at the POA.)

While the Monitor setup seems similar to our prior versions of WebAccess, it is quite a bit different. The Monitor Web Application is dependent upon a Monitor Agent being installed somewhere in your system. However, the Monitor Agent is not at all dependent on the Monitor Web Application, and can be used entirely “stand-alone” without the Monitor Web Application being installed at all. It is very rare that the Monitor Agent is run on a server that does not contain a domain (although it is possible by attaching to an MTA via the MTP port). We provide these steps only for reference. If your Monitor Agent is on the same server as a domain, it has already been upgraded during the GroupWise Server installation!

If you are running GroupWise Monitor Application along with GroupWise WebAccess and/or the GroupWise Calendar Publishing Host on the same server, all of these must be upgraded in the same upgrade cycle or the other applications will not work until they are upgraded.

Preparing for the Upgrade

There is very little preparation that must be made for the GroupWise Monitor upgrade. It can reside anywhere, and no database adjustments are made when it is installed. You must shut down the existing Monitor agent, or course (on Linux or Windows), and it’s best to also shut down Apache and Tomcat if you are installing the Monitor Web Application. In fact, if your Monitor Agent was on the same server as any of the domains you have previously upgraded, the new Monitor Agent Software has already been installed, and you can continue on with “Installing your Agent Software” on page 162.

GroupWise High Availability Agent Considerations

As we mentioned in “GroupWise High Availability Agent Considerations” on page 12, if you are using the High Availability Agent, the settings will not come over after the upgrade. Thus, before you install the Monitor Agent you must copy your High Availability settings so that you can re enable the GWHA afterwards.

Edit the /etc/init.d/grpwise-ma script and find your MA_OPTIONS settings. For example, ours are:

MA_OPTIONS=”–hauser gwha –hapassword gwhapassword –hapoll 120 –httpagentuser gwweb –httpagentpassword gwweb –httpmonuser gwmon –httpmonpassword gwmon”

Save this information in a text file for use in “Re-enabling the GroupWise High Availability Agent” below in this chapter.

Installing your Agent Software

This section will talk about installing just the Monitor Agent on Windows and Linux. The monitor agent is required to monitor your GroupWise system. The Monitor Application is not required, but does add some nice enhancements and functionality.

The installation for the GroupWise Monitor is pretty much the same whether you are upgrading or if you are installing from scratch. The important thing to remember is that you should make a copy of your monitor.xml file before you begin. The upgrade procedure should use the current monitor.xml file that it finds in the directory you specify in the installation (providing it is the same directory where your existing GroupWise monitor resides). However, having a backup is always nice, particularly if you have made customizations on your GroupWise Monitor.

Windows

  1. Make a copy of your monitor.xml file. This will typically be c:\gwmon.
  2. From the Windows machine where Monitor will run, go to your <installationfiles> and run setup.exe.
    1. linuxinstall167.tifInstalling GroupWise Monitor
  3. Proceed to the GroupWise Monitor: Components Screen. Uncheck “GroupWise Monitor Application”, click Next. Note however: If you do intend to have both the Monitor Agent and the Monitor Application on this same server, you must do them at the same time. Otherwise the installation attempts to uninstall the option you deselect. If you are installing both, refer to the steps in “Installing the Monitor Application Software” if you need assistance with the installation prompts.
  4. Select the local path where you wish to install the GroupWise Agent. Note that the default has changed from c:\gwmon to C:\Program Files\Novell\GroupWise Server\Monitor. This is one time when you can easily change this location without having trouble with the setup. If you choose to move your Monitor to this new location, just copy the monitor.xml from your former installation into the new directory if necessary.
    1. linuxinstall169.tifMonitor Server Information
  5. Also verify that the IP address and Port are correct. Click Next
  6. Define the path to any of your GroupWise domain databases. You can use any domain you wish. Choose the domain that the Monitor Agent machine has the easiest access to. Since all of your domains have access to information about all agents in your system, any domain can be used for the Monitor connection. The Monitor Agent will simply query the domain to find IP address, Port and HTTP user and password information for all agents in the system. Click Next.

  1. Choose Your Domain Directorylinuxinstall170.tif
  2. You will then be given a summary of the Agent install. Verify that this information is correct and Click Next.
  3. When the installation is complete, you may launch the GroupWise Monitor Agent.
  4. A shortcut was created for you under the GroupWise Monitor menu. Monitor will run as a service on port 8200. This shortcut is provide a GUI access to the Monitor screen. You can also access it at http://yourserver.com:8200.

After the installation, if you changed the location of your GroupWise Monitor Agent files, you must copy your monitor.xml from the old location into this new location in order to preserve your settings. Restart the GroupWise Monitor service and load your Monitor agent with the GroupWise Monitor shortcut to verify that your Monitor Agent loads properly, and that your previous settings are being honored.

Linux

If your GroupWise Monitor Agent was installed on the same Linux server as any other GroupWise Agent, the Monitor Agent software will already have been upgraded by the time you read this chapter. As a matter of fact, if your Monitor Agent was already on this Linux box, you do not even need to do any configuration. However, if you are installing to a new server, here are the quick steps needed to install the Monitor.

  1. As root, run the install.sh script in your <installationfile> folder.
  2. Choose your Language.
  3. Choose Installation.
  4. Accept the License Agreement.
  5. Choose GroupWise Monitor Agent
    1. linuxinstall210.tifInstalling the GroupWise Monitor Agent
  6. Choose Install. The installation will launch and shut down any agents running if necessary. Press any key to continue after the installation completes.

At this point, the new monitor software has been installed, and you can reload the Monitor Agent. However, if for some reason you need to reconfigure the Monitor agent, follow these steps.

  1. Choose Configure.
  2. Type 1 to Continue.
  3. Type 1 to choose GroupWise (this is a left-over screen from when you could also monitor Messenger).
  4. Enter the location of a GroupWise Domain that is easily accessible from the Monitor machine. This can be any GroupWise Domain (primary or secondary) in your system.
    1. linuxinstall211.tifDomain Directory for Monitor Agent Installation
  5. You will be notified that the Monitor Agent has been configured, and you can choose to start the Monitor Agent on startup. Press any key when prompted and exit setup.

To start the Monitor Agent now, run /etc/init.d/grpwise-ma start or simply rcgrpwise-ma start

Once the Monitor Agent is loaded, you can check the upgrade by going to the IP address and port where the Monitor Agent is running. For example http://192.168.100.237:8200.

Verify that your settings are correct.

Re-enabling the GroupWise High Availability Agent

If you are using the GroupWise High Availability Agent, the original GWHA settings are not preserved during your upgrade of GroupWise Monitor. Thus you will be required to do a bit of reconfiguring. During our preparations in “GroupWise High Availability Agent Considerations” above, we had you copy your MA_OPTIONS line and place it in a text file for user in our reconfiguration.

After the Monitor Agent has been installed, check your GroupWise Monitor agent to verify it loaded (i.e. go to http://yourserver:8200). If the agent is loaded, and operational, go back to your Linux server and type:

rcgrpwise-ma stop

Now, go edit /etc/sysconfig/grpwise-ma. Look for the line that starts GROUPWISE_MA_OPTIONS. Replace the switches there with those that were in your MA_OPTIONS you saved earlier. Our line would look like this:

GROUPWISE_MA_OPTIONS=”–hauser gwha –hapassword gwhapassword –hapoll 120 –httpagentuser gwweb –httpagentpassword gwweb –httpmonuser gwmon –httpmonpassword gwmon”

Note that the option has changed from MA_OPTIONS to GROUPWISE_MA_OPTIONS.

Now start the Monitor Agent again:

rcgrpwise-ma stop

Test the High Availability Agent by shutting down one of your agents. For example, we might shut down the MTA on our system:

rcgrpwise stop CNC

What the status of the agent (either through the monitor or by running rcgrpwise status) to verify that the agent restarts.

Troubleshooting GWHA

The gwha service should still be configured. You can verify this by going to /etc/sysconfig and looking at the gwha file. Unless this file has a line that reads

disabled = yes

then the service is still enabled. If the above line has appeared, remove it.

If the Monitor Agent will not load, double check the hauser and hapassword switches. If you type them by hand, remember that it is hapassword, not hapass and Danita tends to type (over and over!).

Troubleshooting the GroupWise Monitor Agent

There are very few things that can go wrong during a Monitor upgrade. The only problems we typically see have to do with the following:

  • You neglect to keep a copy of your monitor.xml in case of difficulties.
  • You change the location of the Monitor installation files on Windows during the installation (either accidentally, or on purpose) and then do not reconfigure the agent to update the startup files for the server.

Installing the Monitor Application Software

Windows Monitor Application Installation

To install the Monitor Application perform the following:

  1. From the Windows server where IIS is installed, go to your <installationfiles> and run setup.exe.
  2. Proceed to the GroupWise Monitor: Components Screen. Uncheck “GroupWise Monitor Agent”, click Next. Please note: If you do in fact plan on having both the Monitor Agent and the Monitor Application on the same server, you must check both here. If you uncheck the Monitor Agent, and it is already installed on your server, the installation will attempt to remove it! Thus, if you need to install both, keep both checked here. Refer back to the section above on “Installing your Agent Software” if you need assistance with the prompts in this installation
  3. Indicate the IP address or DNS Name of the server where the Monitor Agent is running (i.e., the server where you installed the Monitor Agent above). Also define the HTTP Port that the Monitor Agent is listening on (the default for the HTTP Port for the Monitor Agent is 8200.) Click Next

NOTE: If you are not sure what HTTP Port the GroupWise Monitor Agent is listening on, do the following. For the Windows agent, go to the GroupWise Monitor Agent screen and select Configuration|HTTP. For the Linux agent, check the monitor.xml file in /opt/novell/groupwise/agents/bin.

  1. Choose the web server instance you wish to use on this web server (typically the default)
  2. At the Summary screen, confirm that everything is configured as you would like it to be. Then click Finish to start the installation.
  3. During the installation, you may be prompted about shutting down the web server and Java and overwriting newer files. You should choose the affirmative answer for all of these questions.
  4. When the installation is complete you will be prompted to launch the Installation Summary and restart the web server.

Linux Monitor Application Installation

Here are the quick steps needed to install the Monitor Application on Linux.

  1. As root, run the install.sh script in your <installationfile> folder.
    1. linuxinstall212.tifGroupWise Monitor Application Installation
  2. Choose your Language.
  3. Choose Installation.
  4. Accept the License Agreement.
  5. Choose GroupWise Monitor Application
  6. Choose Install
  7. The installation will begin.
  8. After the files are installed, choose Configure
  9. Press 1 to continue
  10. Enter the IP address of the Monitor Agent.
  11. Enter the Port. The default is 8200
    1. linuxinstall213.tifMonitor Application Server Settings
  12. At the next screen, unless you have configured custom locations for Apache and/or Tomcat, the defaults should be correct.
  13. After the installation, you will be instructed to restart Apache2 and Tomcat6

Loading The GroupWise Monitor Application

Now we will load the web server and the Tomcat. The instructions for loading the web server or Tomcat are different based upon the platform you are using.

Linux

Assuming you are using the default Apache2 and Tomcat6 installations on your Linux server, load the components thusly:

/etc/init.d/apache2 start

and

/etc/init.d/novell-tomcat6 start (OES)

or

/etc/init.d/tomcat6 start (SLES)

You can also check status, stop and restart using these scripts.

Microsoft IIS – Web Server

The GroupWise Monitor Application is designed to start when the Microsoft IIS Service and Web Server is started. The Microsoft IIS Web Server is designed to start with the Microsoft Internet Information Server Service is started under Control Panel|Administrative Tools|Services.

Logging Into GroupWise Monitor Application

Just point your browser to

https://yourserver.com/gwmon/gwmonitor.

For example:

https://groupwise.caledonia.net/gwmon/gwmonitor.

Once you are ready to continue, just turn to the next chapter in your upgrade plan.