Solving a WebAccess Web Page Issue after Upgrade

Novell Cool Solutions: Tip
By Robert Charles Mahar

Digg This - Slashdot This Posted: 16 Oct 2007

Problem

A Forum reader recently asked:

"We upgraded to GroupWise 7.0.2 HP1 from GroupWise 6.5 SP4 (first via GroupWise 7.0.2, then applying HP1). Everything is working fine, except for a small technical issue when going to the webpage of WebAccess.

If I go to gw.xxx.com (my GroupWise WebAccess), I get the language selection page (I think this is from GroupWise 6.5). If I then click Go, I get redirected to the following page: http://gw.xxx.com/servlet/webacc

If I understand this correctly, I should be getting to http://gw.xxx.com/gw/webacc instead. What can I do?"

And here's the response from Bob Mahar ...

Solution

If users are going to http://servername, a quick fix until you can figure it out is to modify the index.html to redirect the user to the proper URL. I assume that if you go to the /gw/webacc it all works properly. The index.html may be the located in the docs folder if you were running NES.

Also, you can make the /servlet/webacc url work properly by modifying the sys:apache2\conf\GWApache2.conf file as follows:

1. In the first few lines, find the line that says "Alias /gw ...."

2. Just after that line, add the following:

redirect permanent /servlet/webacc http://server.DNS.name/gw/webacc

where, obviously, you modify the URL on the end to point to your server.

3. Run the following commands:

UNLOAD APACHE2
LOAD APACHE2

Then /servlet/webacc should work properly. Either way, you have happy users.

Reader Comments

• Right to the point. The options for stopping and restarting the apache server are as follows. AP2WEBDN ADMSRVDN AP2WEBUP ADMSRVUP These will unload all the processes for apache and reload them. Anothe item you may want to do is unload Tomcat. You unload it thusly TC4STOP TCADMDN TOMCAT4 TCADMUP These commands unload and reload tomcat and the tomcat admin process.
• Only stopping and starting apache are necessary for the redirection changes to take effect. e.g. AP2WEBDN followed by AP2WEBUP. These scripts unload and load APACHE2.NLM into the OS address space. "UNLOAD APACHE2" could have the undesirable side effect of unloading other instances of APACHE. But only a problem if you run multiple instances of APACHE. For this solution, unloading and reloading Tomcat is unnecessary.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com