Upgrading Your 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, you will need to totally reinstall your Monitor from scratch. As you know, GroupWise Monitor is similar to the GroupWise WebAccess we have always known, 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 indeed 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. For this reason we will first show how to upgrade the Monitor Agent, and then a separate installation of the Monitor Web Application software so it will not confuse those who only use the Monitor Agent in their organizations.

 

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.

 

Shutting Down the Monitor Agent

Linux

On Linux, you must upgrade all GroupWise components at the same time. Thus, if your Monitor Agent is on the same server as any other GroupWise Component, the Agent has effectively already been upgraded. If you need to upgrade your Monitor Agent software, you need to first stop all processes that are GroupWise related. This includes all GroupWise agents and gateways and GroupWise Monitor. We are assuming that you are running your agents as daemons. If, however, you are running them with their GUI consoles, unload all of the agents by shutting down the GUI consoles. Close the GroupWise Linux client if it is running on the server. Finally, to be certain that all agents and gateways are closed, type the following commands at a terminal prompt:

 

/etc/init.d/grpwise stop

/etc/init.d/grpwise-wa stop

/etc/init.d/grpwise-ma stop

 

(you may receive errors if you are not using the grpwise-ma or grpwise-wa scripts, but it does not hurt to attempt to stop them even if you do not have these scripts installed).

After all GroupWise components have been shut down, type the following into the terminal prompt to verify that no GroupWise components are running:

 

ps -A | grep gw

 

If at this point you still see GroupWise components loaded you can kill them individually, either by pid or name – for example:

 

kill 9860

(if you show a GroupWise component with the pid 9860 running)

 

or

killall gwmon

 

Windows

For Windows, you must also shut down all of your agents that access the domain database. If you are running the agents as services, go into the services console from the Control Panel, right click on the GroupWise agents, and choose stop (see Figure 10-1). If you are not running the agents as services, go to the agent consoles and exit via F7 or from the agent menus.

 

    1. services1.tiffStopping a Windows service

 

You must also close the Monitor Agent that is running on Windows. This is not a service. Press F7 at the Monitor Agent console to close the Monitor Agent.

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 from GroupWise 5.5EP or GroupWise 6.x/7x, or indeed if you are installing from scratch. The important thing to remember if you are upgrading from GroupWise 6.x/7.x 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 6.x/7.x monitor resides). However, having a backup is always nice, particularly if you have made customizations on your GroupWise Monitor.

 

Windows

 

  1. If you are upgrading from GroupWise 6.x/7.x, 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 Master SDD \admin\monitor directory, and run setup.exe.
  3. Proceed to the GroupWise Monitor: Components Screen and Uncheck “GroupWise Monitor Application”, click Next.
  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.
  5. Also verify that the IP address and Port are correct. Click Next
  6. You will be instructed to verify that any agents running on this Windows server are shut down before continuing.
  7. Since the GroupWise 7 Monitor can monitor both GroupWise agents and GroupWise Messenger agents, you will be asked which agents to monitor. If you wish to monitor both GroupWise and GroupWise Messenger agents, check both boxes. Click Next.
  8. 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.
  9. Verify your default language and Click Next
  10. You will then be given a summary of the Agent install. Verify that this information is correct and Click Next.
  11. When the installation is complete, you may launch the GroupWise Monitor Agent.
  12. A shortcut was created for you under the GroupWise Monitor menu.

 

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. 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 you have been reading the earlier chapters in this book, you will find that we are continuing on a familiar theme here! If your GroupWise 7 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. Indeed, 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. 1 As root, run the /install script at the root of your SDD.
  2. Choose Install Products
  3. Choose GroupWise Monitor
  4. Choose Install Monitor Agent. The software automatically installs to /opt/novell/groupwise/agents/bin – you will not be prompted for any information at this time.

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 Monitor Agent
  2. Click Next at the Introduction page, and accept the license.
  3. You will be prompted whether to monitor GroupWise Agents, GroupWise Messenger Agents, or both. It is easier to configure the Messenger Agents manually, so just choose GroupWise Agents.
  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.
  5. You will be notified that the Monitor Agent has been configured, and you can choose to start the Monitor Agent on startup.

 

To start the Monitor Agent now, run /etc/init.d/grpwise-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.

Troubleshooting

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 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. 1 Go to the \admin\monitor directory in your SDD, and run setup.exe
  2. Proceed to the “GroupWise Monitor: Components” screen and Uncheck the “GroupWise Monitor Agent”. Click Next
  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 you intend to use. Also indicate the location to the web server’s root directory. Indicate a drive letter path, not a UNC path. Click Next
  2. At the Language screen, choose the default language you would like to use when logging into the GroupWise Monitor Application. Click Next.
  3. At the “eDirectory Object Configuration” screen, you are given a choice where to place the Application object. As a general rule, keep the location chosen by the installation software. Many GroupWise sites put their web server in its own tree, so the web server can be in a DMZ. This is perfectly fine. Still though, place the GroupWise Monitor Application eDirectory objects in the same tree as your GroupWise objects. In other words, if the web server is in a different tree then the rest of your GroupWise system, still place the GroupWiseMonitor and the GroupWiseMonitorApplication objects in the tree where the rest of the GroupWise system is. Click Next.

 

NOTE: The eDirectory objects for the Monitor Application can be placed anywhere that you feel is appropriate in the tree. These objects are NOT technically GroupWise objects. They are a special eDirectory object that allows for a simple user interface to manage the Monitor configuration files. You can technically manage those files manually by editing the individual files. However, since not every GroupWise administrator is a seasoned web/java administrator, these eDirectory objects give you the tools you need to manage the files without really needing an in depth knowledge of the inner workings of the Monitor Application.

 

  1. At the Summary screen, confirm that everything is configured as you would like it to be. Then click Finish to start the installation.
  2. 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.
  3. When the installation is complete you will be prompted to launch the Installation Summary and restart the web server. You may not wish to restart the web server at this time. Particularly if this is the same web server that is servicing your WebAccess users and you are planning on upgrading WebAccess next. See the instructions below in Loading The GroupWise Monitor Application for information on how to load the web server and the GroupWise Monitor Application.

 

Linux Monitor Application Installation

If your older Monitor Application was installed on a server that contained other GroupWise agents, the Monitor Application software will already have been upgraded to GroupWise 2012 by the time you get to this section. However, if you are upgrading GroupWise Monitor on a server that contains no other GroupWise components, here are the quick steps needed to install the Monitor.

 

  1. As root, run the install script in your SDD
  2. Choose Install Products
  3. Choose GroupWise Monitor
  4. Choose Install Monitor Application. The software automatically installs, and you will not be prompted for any information at this time.
  5. Now choose Configure Monitor Application.
  6. Click Next at the Introduction page, and accept the license.
  7. 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.

  • The settings shown below are the defaults for Apache and Tomcat. Unless you have customized your Web Server configuration, these should be correct:
    • Apache path: /etc/apache2/conf.d
    • Tomcat path:/srv/www/tomcat5/base/webapps
    1. At the LDAP login screen, enter the details for your LDAP server. Figure 10-2 shows how to fill out this information.
      1. monitor1.tiffLDAP settings

 

  1. Once you have logged into eDirectory through LDAP, you will be asked for the location of your Monitor Application objects. If you choose the same context as your existing objects, you will receive a message informing you that the existing objects will be used. The configuration will be complete, and you will be prompted to restart your web server and Tomcat.
  2. You may not wish to restart the web server at this time, particularly if this is the same web server that is servicing your WebAccess users. See the instructions below in Loading The GroupWise Monitor Application for information on how to load the web server and the GroupWise Monitor Application.

 

Loading The GroupWise Monitor Application

  1. Load the web server and the servlet gateway. The instructions for loading the web server or servlet gateway are different based upon the platform you are using. Just like the WebAccess Application, the Monitor Application needs two components in order to work. A Java Servlet Gateway, and a web server. Below are some important tips about loading these components.

TIP: Generally it’s a good measure to re-boot the server with the web server on it after the installation. Sometimes the Monitor Application will not seem to behave as it should. When you reboot the web server, generally things work out. Look at the rest of the web server tips for instructions on the steps you may need to take to load the components that support the GroupWise Monitor Application.

 

Linux

 

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

/etc/init.d/apache2 start

and

/etc/init.d/novell-tomcat5 start

 

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.