This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Web Services and the fly likes consuming web services archecture Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "consuming web services archecture" Watch "consuming web services archecture" New topic
Author

consuming web services archecture

Reed Peters
Ranch Hand

Joined: Jul 23, 2002
Posts: 38
There is tons of information on how to expose legacy backend systems via web services, but I can't find any information on how to make legacy backend system be consumers of web services. Maybe you can help. We have an RPG application that runs on an iSeries box (AS400). Periodically it wakes up and wants to send some data out to an external application via that external application web service interface. What archecture should I use to faciliate this? Should the web service java proxy and supporting java classes run in the AS400's native JVM and utilize a sockets or dataqueue interface to the backend RPG application? Or, is there some way to have a sockets host server java class running in the WebSphere Application Server's JVM listening for backend RPG socket connections. Once made, the java class contacts the web service via the proxy as usual. If this latter is the case, how to I instantiate the java sockets listener in the web container of WAS. It's not a servlet it's just a class...
Any ideas?
Thanks


Reed Peters<br />Reed@cm-inc.com
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: consuming web services archecture
 
Similar Threads
Help: Creating web service proxy using JAXB generated domains
Legacy Connectivity Notes
Legacy Connectivity ....thanx John and Amanda
Web Services and AS400 RPG
Where can I find John Wetherbie note on Legacy Connectivity