Has anyone had success accessing web services (SOAP, WSDL) from CMS? Stev e Gantry talked about wanting to do this from assembler in the thread below. I have no ne ed for assembler. (I prefer REXX or CMS Pipelines, but we also have a C compiler.)
We're not allowed to use LDAP to access our Corporate LDAP Directory -- w e have to use a Java API or web services. No Java in CMS any more (and it performed really poo rly when we did have one). There are tools out there, but they seems to be mostly Java. SOAP i s supposed to be platform and language independent, but coding the whole thing from scratc h looks like it would take me quite a while. Basically, all I have is the WSDL documents for various web services. (WS DL is in the form of an XML document.) I found a fair amount of information on web services at <h ttp:// www.w3schools.com/wsdl/default.asp> -- but no examples in REXX or CMS Pip elines. On Tue, 21 Mar 2006 13:51:23 -0600, Chuck Arney <[EMAIL PROTECTED]> wro te: >If you are going to talk to a true Web Service via a SOAP Server, you wi ll >need to create the XML document containing the SOAP Envelope and the >parameters defined in the services WSDL in the SOAP Body. Then use the HTTP >protocol to send the request to the SOAP server and receive the response >SOAP Envelope XML document. > > > >It's certainly doable in assembler but it will be a fair learning curve if >you are not already very familiar with Web Services and HTTP. > >Chuck Arney >illustro Systems International, LLC http://www.illustro.com >Access 3270 data from anywhere with z/XML-Host >Access 3270 apps from the web with z/Web-Host >Access CMS minidisks from OS/390 or VSE with CMSACCess >Voice: 972-296-6166 > > _____ > >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Steve Gentry >Sent: Tuesday, March 21, 2006 1:40 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: VM, assembler and SOCKETS > > > > >RXSockets: I'd say about 95% of our apps are written in assembler and D MS. >The user would run a green-screen app. entering the >necessary data. This data would then be sent to the WAS Intel box. The >info processed and returned back to VM to be displayed >on the green-screen. I don't think DMS is Rexx friendly. <g>. > > > > > > > >Adam Thornton <[EMAIL PROTECTED]> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > >03/21/2006 02:27 PM >Please respond to The IBM z/VM Operating System > > > To: IBMVM@LISTSERV.UARK.EDU > cc: > Subject: Re: VM, assembler and SOCKETS > > > > >On Mar 21, 2006, at 1:23 PM, Steve Gentry wrote: > >> >> Communicate: Well, that's the issue. That's one of the things I >> need guidance on. >> The application would run on VM and request the information from a >> WAS server running on Intel. >> That information would then be returned to the VM app. >> I assumed they would communicate via TCPIP >> I've done this using Rexx sockets but in the other direction. i.e. >> I have an app. running on an http server running on Linux (running >> on an IFL running VM) >> using hipersockets, etc. >> It requests info from VM, sends it back and displays it on a web >> page. But remember, I'd really like to avoid using Rexx sockets. >> If it is >> absolutely the only way to do it, then so be it. >> > >Yeah, if they're running on different boxes (it was not clear that >WAS wasn't running on z/Linux on the same box or under the same VM >instance in your original problem formulation) TCP is the obvious >choice. > >I'm sure assembler interfaces to sockets exist and work just fine, >but why not RXSockets? It's way, way easier than any alternative >that I'm aware of. > >Adam > > > >
