iSeries Access for Web using Tomcat

[Tom H]

I have been attempting to get this product to work for the past two
days and have been unsuccessful. I have read both the iSeris Access
manual from IBM (version 5) and an article published today by
midrangeserver.com. As far as I can tell everything is correctly
setup.

Here is what I have done so far:

All the products needed are installed. All the latest PTF's are
installed. A web instance using port 2016 has been created with the
Tomcat configuration. I have also created the Tomcat server using the
same port. The HTTP instance starts, the Tomcat server starts. I can
get to the default web page for the HTTP server. When I try to get to
the iSeries access page (http://192.168.100.40/webaccess/iWAHome) all
I get is a page not found error.

What I would like help with is troubleshooting hints. Anyone know
what log files I can check to determine what is going on and what the
error is.

Thanks for your assistance.

[DBowman]

We just recently did this too....we set up the HTTP server to use port 2016
and the Tomcat server to use port 2018. To access the page your URL should
be http://192.168.100.40:2016/webaccess/iWAHome

DCharles

"Tom H" <tha...@printgrc.com> wrote in message
news:943671d7.03091...@posting.google.com...

[erich]

Hi Tom
Not sure if your note has a typo but check your URL must point to the
port ie should be http://192.168.100.40:2016/webaccess/iWAHome
Regards
Erich

tha...@printgrc.com (Tom H) wrote in message news:<943671d7.03091...@posting.google.com>...

[Tom H]

You are right on the URL. That was a typo on my part.

However my problem is how do I troubleshoot this connection? What
error logs are there and where do I find them?

"DBowman" <dfch...@dejazzd.com> wrote in message news:<hah8b.1986$vj4.2...@nnrp1.ptd.net>...

[Tom H]

I have found some log files from the HTTP server, but they do not seem
to sshow what the exact error is. I am posting them below in the
hopes that someone can help. Even though I am requesting
http://192.168.100.40:2016/webaccess/iWAHome the webserver does not
seem to be passing the request onto the Tomcat server. Am I correct
in my assumption from these log files? What would cause that?

error_log.Q103091200

[Fri Sep 12 03:22:53 2003] [notice] ZSRV_MSG0385: Apache configured --
resuming normal operations.
[Fri Sep 12 12:47:35 2003] [error] [client 127.0.0.1] Invalid method
in request 4 z
[Fri Sep 12 12:47:35 2003] [error] [client 192.168.100.209]
ZSRV_MSG0018: File does not exist, referer: http://192.168.100.40/
[Fri Sep 12 12:47:35 2003] [error] [client 192.168.100.209]
ZSRV_MSG0016: URI in request GET /webaccess/iWAHome HTTP/1.1 is not
valid, referer: http://192.168.100.40/
[Fri Sep 12 13:03:22 2003] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.
[Fri Sep 12 14:05:21 2003] [notice] ZSRV_MSG0385: Apache configured --
resuming normal operations.
[Fri Sep 12 14:09:02 2003] [error] [client 127.0.0.1] Invalid method
in request 4 Ė
[Fri Sep 12 14:09:02 2003] [error] [client 192.168.100.209]
ZSRV_MSG0018: File does not exist, referer: http://192.168.100.40/
[Fri Sep 12 14:09:02 2003] [error] [client 192.168.100.209]
ZSRV_MSG0016: URI in request GET /webaccess/iWAHome HTTP/1.1 is not
valid, referer: http://192.168.100.40/
[Fri Sep 12 14:09:14 2003] [error] [client 127.0.0.1] Invalid method
in request 4 Ė
[Fri Sep 12 14:09:14 2003] [error] [client 192.168.100.209]
ZSRV_MSG0018: File does not exist, referer: http://192.168.100.40/
[Fri Sep 12 14:09:14 2003] [error] [client 192.168.100.209]
ZSRV_MSG0016: URI in request GET /webaccess/iWAHome HTTP/1.1 is not
valid, referer: http://192.168.100.40/
[Fri Sep 12 14:11:15 2003] [error] [client 127.0.0.1] ZSRV_MSG0016:
URI in request 4 is not valid
[Fri Sep 12 14:11:15 2003] [error] [client 192.168.100.209]
ZSRV_MSG0018: File does not exist, referer: http://as400.grchome.com
[Fri Sep 12 14:11:15 2003] [error] [client 192.168.100.209]
ZSRV_MSG0016: URI in request GET /webaccess/iWAHome HTTP/1.1 is not
valid, referer: http://as400.grchome.com
[Fri Sep 12 14:11:54 2003] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.

access_log.Q103091200

127.0.0.1 - - [12/Sep/2003:12:47:34 -0700] " 4 z " 501 218 "-" "-"
192.168.100.209 - - [12/Sep/2003:12:47:34 -0700] "GET
/webaccess/iWAHome HTTP/1.1" 404 215 "http://192.168.100.40/"
"Opera/7.11 (Windows NT 5.0; U) [en]"
127.0.0.1 - - [12/Sep/2003:14:09:01 -0700] " 4 Ė " 501 218 "-" "-"
192.168.100.209 - - [12/Sep/2003:14:09:01 -0700] "GET
/webaccess/iWAHome HTTP/1.1" 404 215 "http://192.168.100.40/"
"Opera/7.11 (Windows NT 5.0; U) [en]"
127.0.0.1 - - [12/Sep/2003:14:09:13 -0700] " 4 Ė " 501 218 "-" "-"
192.168.100.209 - - [12/Sep/2003:14:09:13 -0700] "GET
/webaccess/iWAHome HTTP/1.1" 404 215 "http://192.168.100.40/"
"Opera/7.11 (Windows NT 5.0; U) [en]"
127.0.0.1 - - [12/Sep/2003:14:11:14 -0700] " 4 " 400 189 "-" "-"
192.168.100.209 - - [12/Sep/2003:14:11:14 -0700] "GET
/webaccess/iWAHome HTTP/1.1" 404 215 "http://as400.grchome.com"
"Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; .NET CLR
1.1.4322)"

[DCharles]

The HTTP server and the Tomcat server must use different ports.

"Tom H" <tha...@printgrc.com> wrote in message
news:943671d7.03091...@posting.google.com...

[Martin Rowe]

Hi Tom

I got the same result (with the :port in the url) when installing the IWA
beta last week. Just in case I'm not the only one who overlooked the
obvious this was my error:

I'm not sure if the commands for the standard version (which I've not
used) are the same as for the beta, but when running the command
QIWA2/CFGACCWEB2 APPSVRTYPE(*ASFTOMCAT) TCSVRNAME(iwatc)
TCHOMEDIR('/ASFTomcat/iwatc') TCUSRPRF (QTMHHTTP)
I got the java shell with nothing happening so after a minute or so I F3'd
out of it assuming it had already completed and I'd just missed seeing
the output. Turns out I hadn't given it long enough, as it took >2 minutes
before seeing any output on our 2 way 730, and well over a minute on our 4
way 730. After restarting the HTTP & Tomcat servers it finally worked ;)

I had a brief look at the midrangeserver article (which arrived just
*after* I'd got it set up) and I think the web_server_examples.html page
(and the readme.html) that came with the beta gave a more comprehensive
guide. If those documents aren't in the standard product and you don't
fancy a 90Mb download just for a couple of web pages I can send you the
files (not sure IBM would like me posting them on my server).

Regards, Martin
--
mar...@dbg400.net AIM/Gaim: DBG400dotNet http://www.dbg400.net /"\
DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ /
Source free test environment tools and others (file/spool/misc) X
Debian GNU/Linux | ASCII Ribbon Campaign against HTML mail & news / \

[Tom H]

I wanted to follow up with everyone who were kind enough to reply.
After some struggling with the setup, it did turn out to be the two
port issue. After leaving the HTTP server instance on port 2016 and
setting the Tomcat on 2018, it finally worked.

Thanks to all of you for your help.

[Jim]

I was a lurker for this post, but would like to thank Martin for his input.

We just got back from COMMON (see the COMMON thread for my take on it) and
we wanted to try Access for Web. We followed all the instructions exactly
and it would not come up.

Turns out there was no mention in the COMMON lab handout for any resulting
messages from the CFGACCWEB2 command, we weren't waiting long enough, and
just hitting F3 prior to it completing, thinking that if we got a command
line back it was completed. Guess what? It's not.

Here's the last line you should see:

Java program completed.

If you've never ran it before, you don't have a clue it's still working on
something, and there's nothing in the Docs about waiting for this.

As soon as we re-ran the command and waited longer, we started getting the
messages.

Thanks Martin. I've asked the Access for Web lab leaders to include this in
the next
set of handouts...

z

[Martin Rowe]

On Thu, 18 Sep 2003 03:40:59 +0000, Jim wrote:

> I was a lurker for this post, but would like to thank Martin for his
> input.
>
> We just got back from COMMON (see the COMMON thread for my take on it)
> and we wanted to try Access for Web. We followed all the instructions
> exactly and it would not come up.
>
> Turns out there was no mention in the COMMON lab handout for any
> resulting messages from the CFGACCWEB2 command, we weren't waiting long
> enough, and just hitting F3 prior to it completing, thinking that if we
> got a command line back it was completed. Guess what? It's not.
>
> Here's the last line you should see:
>
> Java program completed.

Hi Jim

I did track this info down afterwards in one of the other documents
on the IWA web site[1], but there didn't seem to be any mention of it in
the docs that came with the beta. Still, I'm glad the info was useful - I
don't feel *quite* as silly now ;)

As an aside, once I did get it running I hit on a problem with group jobs
not working in the web session. I reported to the feedback team at
the end of last week and they emailed back on Monday asking for more
details. I replied Tuesday morning and they emailed a fix that afternoon!
Not bad for an 'unsupported' product :) It's all working quite well now,
though not as quick as I'm used to in tn5250 ;)

Regards, Martin
[1] From the CFGACCWEB2 CL reference in Appendix E of iSeries Access
for Web Installation and User Guide -
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/sm01/c4155181.pdf
- "When the command runs, a Java Shell Display session starts. Status
information displays, indicating what the command is processing. As the
command runs, detailed status and error information is logged to
/QIBM/UserData/Access/Web2/logs/cmds.log. After the command completes, the
web application server may have to be ended and restarted. The iSeries
Access for Web configuration will need to be started before it can be
accessed."