Upgrading the GroupWise Calendar Publishing Host

Upgrading the GroupWise Calendar Publish Host is relatively painless, and can be done as soon as the Post Offices it services are upgraded.

If you are running GroupWise Calendar Publishing Host along with GroupWise WebAccess and/or the GroupWise Monitor Application 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.

There are new administration options for the Calendar Publishing Host though, and you will need to read the section below on

Preparing for the Upgrade

There is very little preparation that must be made for the GroupWise Calendar Publishing Host upgrade. It can reside anywhere, and no database adjustments are made when it is installed. You must know the name of your Calendar Publishing Host. To find this information do the following:

  1. In the Administration Console, click on System|Calendar Publishing.
  2. You will see a list of your Calendar Publishing Hosts.
    1. List of Calendar Publishing Hostslinuxinstall176.tif
  3. Note the name of the Calendar Publishing Host that you are upgrading. In our case it is CalPubHost.
  4. Now click on Post Office Agents, and choose the Post Office Agent in question. Ours is for our Caledonia Post Office.
  5. Click on the Agent Settings Tab.
  6. Scroll to the bottom of the page to view the Calendar Publishing Host settings. Note the Port Number. The default is 7171
    1. linuxinstall177.tifThe Calendar Publishing settings

Close this Window if you choose.

Installing the Calendar Publishing Host Software

Windows

To install the Calendar Publishing Host software perform the following:

  1. From the Windows server where IIS is installed, go to your <installationfiles> and run setup.exe.
  2. Choose GroupWise Calendar Publishing Host.
    1. linuxinstall179.tifInstalling the Calendar Publishing Host
  3. Choose your language.
  4. At the prompt, click next
  5. Accept the license agreement.
  6. Enter the Calendar Publishing Host Name. In our case this is CalPubHost
  7. Choose the IIS web server instances for your Calendar Publishing Host
  8. Enter the IP address of the POA for your Calendar Publishing Host. Ours is 192.168.110.192
  9. Enter the Calendar Publishing Port Number that we looked up above. The default is 7171.
  10. At the Summary screen, confirm that everything is configured as you would like it to be. Then click Install.
  11. 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.
  12. When the installation is complete you will be presented with steps to configure your Calendar Publishing Host. Since this is an upgrade, that should already be completed. Click Next.
  13. You will be prompted to launch the Installation Summary and restart the web server.

Linux

Here are the quick steps needed to install the Calendar Publishing Host on Linux.

  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 Calendar Publishing Host.
    1. linuxinstall174.tifThe Calendar Publishing Host Installation
  6. Choose Install
  7. The installation will begin. Tomcat and Apache will be unloaded during the installation. Press Any Key to Continue.
  8. After the files are installed, choose Configure
  9. Press 1 to continue
  10. Enter the Calendar Publishing Host Name. In our case this is CalPubHost
  11. Enter the IP address of the POA for your Calendar Publishing Host. Ours is 192.168.110.192
  12. Enter the Calendar Publishing Port Number that we looked up above. The default is 7171.
  13. At the next screen, unless you have configured custom locations for Apache and/or Tomcat, the defaults should be correct.
  14. After the installation, you will be instructed to restart Apache2 and Tomcat6

Loading The GroupWise Calendar Publishing Host

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 Calendar Publishing Host 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.

Checking the GroupWise Calendar Publishing Host

Just point your browser to

http://yourserver.com/gwcal

For example:

http://groupwise.caledonia.net/gwcal

You will see any published calendars that are available for the System.

  1. linuxinstall178.tifPublished Calendars

Configuring Calendar Publishing Host Administration

After you have upgraded your Calendar Publishing Host and have verified that it is working, it’s time to look at the new administration options. Similarly to WebAccess, Calendar Publishing Host now has its own configuration file on the web server.

Let’s go to look at this file.

Linux: /var/opt/novell/groupwise/calhost/calhost.cfg

Windows: c:\novell\groupwise\calhost\calhost.cfg

This file will look very similar to the webacc.cfg that you are probably familiar with.

Enable the CalHost Administration Console

  1. In your favorite text editor, search for the line that reads

Admin.WebConsole.enable=false

  1. If this is preceded by a # sign, remove the # to activate this line
  2. change false to true.

Now you must restart Tomcat on your server

For Linux, run

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

or

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

On Windows, click Start > Administrative Tools > Services. Then right-click Tomcat 6, and click Restart.

Load the CalHost Administration Console

To load the CalHost Administration Console, navigate to your server in a web browser like this:

http://yourserver.com/gwcal/admin

You will be prompted to login. Use your gwadmin user credentials you created when we set up the system. Any user who has rights as a Post Office Administrator or higher can log into this console with their own GroupWise credentials.

  1. linuxinstall189.tifLogging into the Calendar Publishing Host Administration Console

Post Office Settings

You will be presented with the following screen:

  1. linuxinstall190.tifThe Calendar Publishing Host Administration Console

This screen will show you the settings that were migrated to the new Calendar Publishing Host configuration during upgrade. If the IP address of your POA were to change, you would edit that here.

We’ll quickly run through the other screens of this administration console.

Logging Settings

On the Logging Screen you can set your logging settings.

  1. linuxinstall191.tifThe CalHost Log Settings

These settings are very similar to the logging settings for all of your GroupWise agents. The one addition here is that you can choose to log both to the GroupWise agent logs and the Tomcat logs if you desire.

Authentication Settings

If you need to change which Administration Service the Calendar Publishing Host Admin authenticates to, you can do so here.

  1. linuxinstall192.tifCalendar Publishing Host Admin Authentication Settings

Please be aware that this can be affected by the settings we described in “Verifying MTA Network Settings” on page 12.

Customize

If you click on the Customize tab, you can change the way the published calendars page looks. For example, we’ve added a Caledonia logo, changed the text and placed the changed text at the bottom edge of the logo.

  1. linuxinstall209.tifClient Customization Settings
  2. linuxinstall193.tifCalPub Customizations

Updating your Changes

You will notice that on all of the setup screens above there is a notice that you may need to wait up to 10 minutes for changes to occur.

There is a setting in the calhost.cfg that defines this time

Config.Update.check=10

While it would be possible to set this for a shorter timeframe, you can also simply restart Tomcat to effect a change immediately.

For Linux, run

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

or

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

On Windows, click Start > Administrative Tools > Services. Then right-click Tomcat 6, and click Restart.

Troubleshooting

There is little that might go wrong with the actual Calendar Publishing Host upgrade. That said, the addition of the Calendar Publishing Host Administration Console can have its moments!

There are settings in the calhost.cfg that pertain to how the new admin console connects to the GroupWise Administration Service.

######################################################################

# Application Administration Tool

######################################################################

Admin.WebConsole.enable=true

Admin.RestService.host=127.0.0.1

Admin.RestService.port=9710

There are a couple of reasons why these default settings might not work for you:

  • If you are running the Calendar Publishing Host on a server that does not have a GroupWise Administration Service running, the setting of 127.0.0.1 will be invalid. You will need to change it to the proper ID address.
  • If you have an MTA running on this server, but it is set to bind to a specific IP address, the Admin Service will also not be listening on localhost (127.0.0.1) and you should change this to the specific location. Indeed, if your MTA is set to a host name rather than an IP address, the Admin Service could complain if you enter an IP address here. Test to see which works properly for you.
  • If you have modified the default port for your Admin Service, you will also need to change the information here.

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