WebAccess 6.5 and Tomcat 4

[glio]

I've just installed WebAccess 6.5 on a GroupWise server running on Netware 6.5. The WebAccess agent runs okay... but can't access through the web browser. Do I have to configure Tomcat4 in order to access those servlets after the installation? The installation is still fresh so everything is still in the default config.

Please help!

Jimmy

 

[marvhuffaker]

On NetWare 6.5, almost everything web relies on Tomcat (and LDAP).

Get those working and you'll be set. They should have installed when you installed the server, but sometimes they break in a migration and you have to fix them afterwards.

Also check your ETC\HOSTS file and make sure the first line (LOOPBACK) shows 127.0.0.1... I've seen that get whacked in a lot of migrations for some reason. That will cause Tomcat to fail to load.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[glio]

Thanks... I installed the latest patch for GW65 and WebAccess runs now. GW65 was released prior to NW65... The original release of GW65 doesn't seem to recognize the config of Tomcat on NW65.

Jimmy

 

[ITsmyfault]

jm2c -
run gw webacc in its own memory space. What you do is run a new instance of Apache on the server, which gets it's own .conf file. I bound a secondary IP address just for this web server to help protect the server. I used a non standard install location as I did not want GW Web to possibly interfere with iManager, NoRM, etc. I wanted to keep the configs clean. Also, if webacc gets whacked by something, I don't want it to affect anything else on the server - this localizes the problem to this specific apache process. The only thing you need to do is copy the COM folder to the new location - eg: if your default pub dir is /apache2/gwweb just copy the COM folder into it.
Then in the NCF file which starts the whole thing, you just go like this (change path and conf file name obvioiusly to yours..)
(unwrap this line)

load address space = gwweb apache2 -f sys:/Apache2/conf/GWWeb.conf

to unload,

unload address space = gwweb apache2

It's key to add that "apache2" at the end or bad things happen.

With a process running in its own memory space, it can crash and not hurt anything else - also there is an auto-restart feature you can use to reload the space if the OS detects the thing is not responsive or down. Both good for a web facing service IMHO.