RE: Performance problems with Java SOAP client

Is the Java program running in an Application server like Tomcat or WAS?
If not then that is probably where you are incurring some of the
overhead because the classes aren't being cached as good as they could
be.  That is just what I have noticed from my experience, no hardlined
performance testing though.

For a solution I would have my Java SOAP web service sitting in Tomcat
or WAS waiting for requests via HTTP POST, parse the SOAP document, call
the COBOL program via SQL UDF's or PCML, and then return the response
back to the sender.

If you rewrite the program in RPG, for example, you will find that
everything needs to be built from the ground up (your WSDL, publishing
to UDDI, SOAP envelope handling, etc).  If you already have Java
knowledge in your shop then talk amongst your group and come to an
agreement on where the two should meet (the other being COBOL or RPG).
In some cases it might be best to use Java all the way through depending
on what type of functionality you are trying to get from this web
service.

Those are my thoughts,
Aaron Bartell 

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] 
Sent: Sunday, July 18, 2004 8:53 PM
To: JAVA400-L@xxxxxxxxxxxx
Subject: Performance problems with Java SOAP client

Hello !

Some of our customers want to use webservices on their ISeries (V5R2)
machines We have made a Java SOAP client, but they say that the
performance is unacceptable.
The program is very simple:  it receives some data, calls some COBOL
program, and returns some data.

We are exploring some ideas, and we would like to get some feedback of
this forum:

a)  Tuning Java:  Besides using OPTIMIZE(40), what else can we do ?

b)  Rewrite the program in some native language ( ILE C or ILE RPG):
     we know that there is a XML parser for procedural languages, but we
have not found
    a SOAP library.   Would it be complex to write our own SOAP routines
?
    We have some experience writing TCP programs, but not HTTP or SOAP
programs
    in these languages.

c) Get the Java client out of the Iseries:  the program still will
handle SOAP messages, 
   but it will use TCP and plain messages to communicate with a ILE C
program 
   in the Iseries.    

I would appreciate your opinions and suggestions.

Thank you, 


         Andy D'Aquila


--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/java400-l.