The original poster pointed out that they are *already* using CICS Web Services. Now they want to access Web Services from batch (and/or vice versa).
So the question now is whether it makes sense to buy, develop, test, secure, implement, operate, manage, support, and maintain a *second*, entirely separate Web Services capability versus just accessing the excellent one they've got in production. It's trivially easy to access CICS from batch, requiring no special skills. I seriously doubt whether any other option is going to make business sense, absent a "damn good reason" -- or preferably several such reasons. By the way, CICS TS V4.2 uses Apache Axis2. That's a very good thing, because it's very industry standard and moves with the industry. And that's the point of Web Services, to provide interoperability across application services. - - - - - Timothy Sipples Resident Enterprise Architect Value Creation & Complex Deals Team IBM Growth Markets (Based in Singapore) E-Mail: timothy.sipp...@us.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
