If you're getting the initial screen it means Apache is ok. The next screen is generated by Tomcat though - which would appear to be the problem. There is a bit of config that tells Apache to hand off certain requests off to Tomcat. There is a piece in the httpd.conf file to tell Apache, and there is a workers.properties file for Tomcat.
Check the httpd.conf for a bit that looks something like this (yours will be a little different)
--------------------
# this section added to link Tomcat4 to Apache in order to
# run Groupwise Webaccess 6.5
# mod_jk.nlm was installed to sys\apache\modules
LoadModule jk_module modules/mod_jk.nlm
<IfModule mod_jk.c>
JkWorkersFile sys:/tomcat_4.0.6/conf/jk/workers.properties
JkLogFile "sys:/tomcat_4.0.6/conf/jk/mod_jk.log
JkLogLevel error
JkMount /servlet/* ajp13
</IfModule>
-------------------
In workers.properties you should see something like:
-----------------------
worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
------------------------
this is assuming that Tomcat and Apache are on the same server, using port 8009. 6.5 might be using a different ajp..not sure. My config is from running Webacc 6.5 on NW5.1 and Apache (not supported) The basic idea is that if Apache does not know whether to or how to pass these requests off to Tomcat, you won't get any of the java-built pages - only the static ones.