I for one am very grateful that you have commented on your resolution.
Glad to see you have everything running now.
Philip
On Mar 8, 2006, at 11:04 AM, Pete Helgren wrote:
Thanks Philip.
Yes, the first the place I go is the documentation, then the forum
(to search) and then Google. If I am stumped, then I bother a
human (first at my company and then post a question). We are all
busy people and answering a question that has been already answered
isn't very productive. However, Googling can be both blessing and
curse.
However, I did identify and fix the problem while I was waiting for
a post back. The fact that the URL got a positive response back
from Axis told me that all was well at the installation end.
The .net client issue was a little more challenging. Turns out
there is a file that has a .config extension that has the host name/
address and port. It is buried with a bunch of other configuration
files so I had updated the wrong one. When I finally changed the
correct file to use the correct host name, the .net client began to
work. The 404 error was gone.
The IBM RPGLE program was a bit more of a challenge. It was
contacting the Axis application server but Axis (Tomcat) was
returning an HTTP 500 message. Using TCPMon (which is a great tool
that could use some slightly better documentation) I discovered
that the XML was improperly formatted. Once that was corrected,
the 500 error was gone.
So it was just tracking down the causes for each client app error,
rather than an Axis problem.
I am a bit new to web services so I am still in learning curve
mode. I am documenting this here is case anyone else runs into
newbie issues like this...
Pete
Gonia, Philip T wrote:
