This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
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