View previous topic :: View next topic
|
Author |
Message |
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
Need some ideas here.
Old system which created a flat file for us to retrieve is switching to Java. They are going to make the same information available as a SOAP service.
The information is probably less than 4,000 bytes total.
My question is, how do I call a SOAP service from a z/OS batch job?
-My research has shown that it's possible with the OMVS command cURL. I'm working on getting that enabled right now.
-We have the IMS SOAP Gateway installed, but it needs IMS TM, and indicates that it would NOT work with 'TM Batch'. I don't know if that's the same thing as BMP
-We use Control-M for mainframe scheduling and Control-M Enterprise for server side scheduling.
-We have the IBM suite of tools, such as FileManager and DFSort
Obstacles are time needed to get a BMP transaction set up at current site(especially just for a proof of concept), and security concerns for enabling cURL.
Does anyone here have practical experience calling a SOAP service from a z/OS batch job? |
|
Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
In a previous position I was doing SOAP calls from TSO/E REXX execs using the TCP/IP Socket Services. They worked quite well at the time. |
|
Back to top |
|
|
agkshirsagar
Active Member
Joined: 27 Feb 2007 Posts: 691 Location: Earth
|
|
|
|
Quote: |
Does anyone here have practical experience calling a SOAP service from a z/OS batch job? |
I have done it before. However, it was using a product called SOLA. Calling a web service is a cakewalk with the SOLA DOM API. |
|
Back to top |
|
|
Ed Goodman
Active Member
Joined: 08 Jun 2011 Posts: 556 Location: USA
|
|
|
|
update...
I got a really kick a$$ solution together using the rexx socket commands. I will post it later. It works perfectly. I can post the SOAP request and get the response back, then parse the response as needed to get the data.
Since our request/reply is so small, I can do it all in memory.
I'm exploring the cURL option now so that our security folks can evaluate the approaches for safety's sake. |
|
Back to top |
|
|
|