1 / 13

Modern Application Architectures for COBOL Developers - Continuing the drilldown

Modern Application Architectures for COBOL Developers - Continuing the drilldown. Presenter’s name Title email address. WSDL. Top down. Web service requester. Web service provider. CICS. CICS as provider. CICS as requester. Bottom up. Language structure(s).

arne
Download Presentation

Modern Application Architectures for COBOL Developers - Continuing the drilldown

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modern Application Architectures for COBOL Developers - Continuing the drilldown • Presenter’s name • Title • email address

  2. WSDL Top down Web service requester Web service provider CICS CICS as provider CICS as requester Bottom up Language structure(s) Web Services Enablement Styles

  3. Where a wrapper program fits in Business Logic Wrapper Program Conversion (SOAP ↔ COMMAREA) Pipeline

  4. CICS as a service provider CICS TS V3.1 TCPIPSERVICE CSOL SOAP message CPIH CWXN Service Requester Pipeline URIMAP matching handlers URIMAP HFS handlers dynamic install pipeline config handlers WSDL PIPELINE data mapping CICS provided utility dynamic install Business Logic WSBind WEBSERVICE Language structure

  5. Defining the CICS Web Services Resources • Define a TCPIPSERVICE (or WMQ) and a PIPELINE • Then install the PIPELINE definition and issue CEMT PERFORM PIPELINE SCAN • CICS uses the PIPELINE definition to • Locate the WSBind file • From the WSBind file, CICS will dynamically create a WEBSERVICE resource • CICS will also dynamically create a URIMAP definition • Can define everything individually if preferred

  6. CICS usage of the WSBind file • CICS as a service provider • CICS as a service requester CICS Web services Service Requester business logic pipeline HLL data structure SOAP body Data mapping WSBind file WEBSERVICE resource WSDL CICS CICS Web services business logic Service Provider HLL data structure pipeline SOAP body Data mapping WSBind file WEBSERVICE resource WSDL CICS

  7. The Business Tier Client Tier Middle Tier Enterprise Information Systems Tier EJB Container (EJBs) Core Applications and Services (CICS IMS) Web Container (Servlets, JSPs, JSF WAS, Java) Web Client (HTML, JavaScript) Web Services JCA MQ Etc. Relational Databases Enterprise Resource Planning Systems J2EE Services (JNDI, JMS, JavaMail)

  8. CICS as a Web service requester CICS TS V3.1 ServiceRequester ServiceProvider Client Application Transport Pipeline HTTP Server Application WebSphere MQ Handler chain HTTP or WebSphere MQ SOAP body XML Data Mapping Language structure 0101001 Dynamic install HFS CSD 1. Develop • Use existing WSDL • Language structure • CICS Client Application 2. Generate • Language structure • WSBIND 3. Configure • Pipeline • Pipeline configuration • WEBSERVICE Pipeline config PIPELINE WSDL WEBSERVICE WSBind

  9. CICS API’s • Invoking a Web Service from a CICS application program • CICS as a service requester • EXEC CICS INVOKE WEBSERVICE ( ) CHANNEL ( ) URI ( ) OPERATION ( ) • WEBSERVICE: name of the Web Service to be invoked • CHANNEL: name of the channel containing data to be passed to the Web Service (DFHWS-DATA container) • URI: Universal Resource Identifier of the Web Service (optional) • OPERATION: name of the operation to be invoked

  10. Resources (1 of 4) • Application Development for CICS Web Services, SG24-7126-00(http://www.redbooks.ibm.com/abstracts/sg247126.html?Open ) • Implementing CICS web services (redbook) SG24-7206( http://www.redbooks.ibm.com/abstracts/sg247206.html?Open ) • CICS Info Center • http://publib.boulder.ibm.com/infocenter/cicsts31/index.jsp • About the Info Center for CICS(http://www-1.ibm.com/support/docview.wss?rs=1083&context=SSGMGV&context=SSZPSF&context=SSZMG3&dc=D600&uid=swg21200934&loc=en_US&cs=UTF-8&lang=en ) • Web Services Guide • A new book in the CICS Infocenter for CICS TS V3.1 • CICS TS 3.1 Release Guide, SC34-6421 • CICS TS 3.1 Migration Guide(s) • CICS TS 3.1 URLs • “Home Page” (http://www.ibm.com/software/htp/cics/tserver/v31/ ) • Library (http://www.ibm.com/software/htp/cics/library/cicstsforzos31.html )

  11. Resources (2 of 4) • Web Services Architecture (@ W3C) • http://www.w3.org/TR/ws-arch/ • Web Services Zone (@ IBM developerWorks) • http://www.ibm.com/developerworks/webservices/ • Websphere V5 Web Services Handbook • Redbook: SG24-6891 • Web Services for the Enterprise: Providing a Web Services Interface To a CICS Application • Whitepaper: G325-1111-2 • CICS Info Center

  12. Resource (3 of 4) • SOAP 1.1 Specification • http://www.w3.org/TR/SOAP/ • Apache SOAP4J: xml.apache.org • SOAP4J version 2.2, stable, ready for use • AXIS (First release available) • W3 standardization: w3.org/2000/xp • SOAP 1.2 specification • XML Protocol working group requirements and charter • SOAP - WebServices Resource Center • http://www.soap-wrc.com/webservices/default.asp • MANY resources - e.g., link to SOAP::Lite for Perl • Xmethods lists publicly-accessible web services • http://www.xmethods.net

  13. Resources (4 of 4) • WSDL 1.1 Specification • http://w3.org/TR/wsdl • WSDL4J • http://oss.software.ibm.com/developerworks/projects/wsdl4j • WSDL Toolkit (part of WSTK) • http://ibm.com/alphaworks (look under xml on left) • WebSphere Developer for zSeries • http://ibm.com/software/awdtools/devzseries • WSDK (WebSphere SDK for Web Services): • http://ibm.com/developerworks/webservices/wsdk/ • Articles and tutorials: • http://ibm.com/developerworks/webservices

More Related