Upload
vanxuyen
View
232
Download
5
Embed Size (px)
Citation preview
IBM Software Group
© 2006 IBM Corporation
IBM CICS® Transaction Server for z/OS™ V3.1
technical overview
ibm.com/software/ts/cics
refer to IBM Software Announcement 204-285
K-H MarquardtIBM Deutschland [email protected]
GSE/CICS working group Brussels, 26.10.2006
IBM Software Group
© 2003 IBM Corporation2 IBM CICS TS for z/OS V3.1 | Technical Overview
Acknowledgements
§ The following are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM,CICS, CICS TS, CICS Transaction Server, DB2, MQ, OS/390, S/390, WebSphere, z/OS, zSeries, Parallel Sysplex.
§ Java, and all Java-based trademarks and logos, are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
§ Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
§ Other company, product, and service names and logos may be trademarks or service marks of others.
IBM Software Group
© 2003 IBM Corporation3 IBM CICS TS for z/OS V3.1 | Technical Overview
Agenda
qCICS Transaction Server Evolution
qStrategic options to integrate CICS applications
qExtentions for the CICS Web Support
qChannel & Container (“big Comarea”)
qOTE TCBs, XPLINK
qEnterprise Management
qDiscontinued function
qPrerequisites, packaging
qSummary
IBM Software Group
© 2003 IBM Corporation4 | Technical Overview
üOver 35 years and $1 Trillion invested in Applications ... IDCüOver $1 trillion processed/dayüOver 30 billion transactions/dayüMost people use CICS
Pervasive Devices
CICS today…
Combining the reliability and Combining the reliability and security of CICS software with the security of CICS software with the flexibility of eflexibility of e--business technologybusiness technology
Evolution, NOT RevolutionEvolution, NOT Revolution
IBM Software Group
© 2003 IBM Corporation5 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS Transaction Server Evolution (Highlights)
Integration Transformation System Management
CICS TS V1CICS TS V1
CPSM WUI improvements, flexible CustomizingCPSM- and RDO-Extentions for new functionssimplified CPSM migration
HTTP 1.1 in/outboundTLS, 256-bit encryptionSSL performance
Web Services SupportContainers & ChannelsOTE TCBs open for Appl.XPLINK for C,C++improved codepage conversion
CF Structure rebuild EJB Deployment simplifiedDB2 Group AttachWUI includes DefinitionsCPSM new function supportMon/Stats extendedInfo Center
OTE TCBs for DB2 AppJDBC 2.0WLM for Link BridgeEnd-to-End DebuggingXML Parser in Cobol + PL/I
Java Support, SDK 1.4.1JCICS APIsECI over TCP/IPLink3270 BridgeOTS support for EJBsSOAP for CICS Feature
CPSM WUI System Logger Macro Tables
VSAM RLSCFDT, shared TSQs
CICS BTSCICS Web Support3270 Bridge, EXCI Interface
CICS TS V2CICS TS V2
CICS TS V3CICS TS V3
in parallel: - further improvements in CICS Trx.Gateway and Universal Client- comprehensive tools portfolio (AD, PD, CICS tools)
IBM Software Group
© 2003 IBM Corporation6 IBM CICS TS for z/OS V3.1 | Technical Overview
Strategic Options for Integration
§ Standard Architectures provide comprehensive development tools and runtime support in CICS
Web services using SOAP (Simple Object Access Protocol)Enterprise JavaBeans (J2EE EJB)JCA (J2EE Connector Architecture)
§ Standard Transports are suitable for use by applications that require greater control of the protocol and do not need the development tools or qualities of service provided by the standard architectures. These applications will assume more responsibility for systems management, security, and recovery
HTTP (HyperText Transfer Protocol)WebSphere MQ (MQ APIs or JMS - Java Messaging Service)TCP/IP sockets (CICS socket feature of z/OS communication manager)
1
456
32
IBM Software Group
© 2003 IBM Corporation7 | Technical Overview
CICS TS
Strategic Options - Access into CICS
Web services
ServletBrowser
JCA
EJB
WebSphere MQ
TCP/IP Sockets
Web services
1
4
5
6
3
2
J2EE App Server
DB
A
I
SOAP
http
IBM Software Group
© 2003 IBM Corporation8 | Technical Overview
Strategic Options - Access from CICS
CICS TS
1
5
6
4
2B
A
Web services
Web server
WebSphere MQ
TCP/IP Sockets
EJB
Web services
J2EE App Server
SOAP
http
IBM Software Group
© 2003 IBM Corporation9 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS Web Services Support
dynamic resource install
HTTP listener
WebSphere MQtrigger monitor
ServiceRequester
ServiceProvider
Pipeline
HTTP orWebSphere MQ
Server Application
TransportClient Application
CICS TS
Handler chain
HFS files
WSDL
WSBind
Pipelineconfig
CSDURIMAP
SOAP body
XML
Data Mapping
Languagestructure0101001
WEBSERVICE
PIPELINE
WSDL
WSBind
CPIH
1
http://www.../example/myService
Endpoint = /example/myService
CICS as Service Provider
IBM Software Group
© 2003 IBM Corporation10 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS web services => access to/from CICS via SOAP protocol
Øbest suited for integration in an SOA (service oriented architecture)
4CICS can be service provider and/or service requester4 loose coupling
4service description, message layout and transport in WSDL document4plattform and language independance through XML
ØWeb services standard support for inbound and outbound4SOAP 1.1 and 1.2, WS-I Basic profile 1.0a, WS-Security, WS-Atomic Trx.
ØHTTP/1.1 or WebSphere MQ transport4transport mechanism is transparent to CICS applications
Øextensive tooling available4WD/z – IDE for host application development and debugging4CICS provides Utilities to generate WSDL from language structure4CICS service flow feature
4Design and generate component in WD/z4Runtime component in CICS
1
IBM Software Group
© 2003 IBM Corporation11 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS Web Services Support …
ServiceProvider
ServiceRequester
Pipeline
Client ApplicationExec cics invoke webservice(x)
TransportServer Application
CICS TS
Dynamic resource install
HTTP
WebSphere MQ
SOAP body
XML
HTTP orWebSphere MQ
Handler chain
Data Mapping
Handle response
Languagestructure0101001
1
CICS as Service RequesterHFS
WSDL
WSBind
Pipelineconfig
CSD
PIPELINE
WEBSERVICE
URIMAP
IBM Software Group
© 2003 IBM Corporation12 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS EJB ContainerJava Client
EJB
CICS Corba Server / EJB Container
CICS EJB Serversession bean in CICS
(local / remote)
session + entity bean in other EJS
JCICS: Link / Start+ CICS Ress.Access
CICS-Pgm(DPL) via Java Connector (CTG)
JDBC, SQLJ
"any Java", e.g. XML, java.net, etc.
Java IDL
Client
CORBA Client
ORB
EJBHome
EJBObject
RMI/IIOP
RMI/IIOP
IIOP
Ø CICS supports subset of EJB 1.1 specificationð see http://java.sun.com/products/ejb
P Session Beans ð statefull and stateless
o Entity Beans are not supported in CICSð solution is method calls to remote Entity Beans or local DB access
o certain J2EE APIs are not implemented in CICS (e.g. mail APIs)ð not suitable for CICS
Ø existing procedural logic can be reused
Cobol
2
IBM Software Group
© 2003 IBM Corporation13 IBM CICS TS for z/OS V3.1 | Technical Overview
qIBM SDK for z/OS, Java™ 2 Technology Edition (1.4.2)ƒfull function JVM, Java compatible logoƒdownload from http://www.s390.ibm.com/java/
SDK 1.4.2 delivers many enhancements in the areas of security, XML,networking and debugging as well as fixes
CShared class cacheƒseveral worker JVMs share the class cache
ƒJVM base classes, trusted middleware, sharable appl. classesƒMaster JVM (runs on JM TCB)
ƒone per CICS region, owner of shared class cache and Jit-compiled code
ƒpool of n worker JVMs (run on J8/J9 TCBs) ƒexecute Java application
Java Evolution
Shared Class Cache
Master JVM
JVM classes
Middleware
Application
Worker JVM
Worker JVMWorker
JVM
JVM
JVM pool in CICS
Class Cache
JVM
Class Cache
2
IBM Software Group
© 2003 IBM Corporation14 IBM CICS TS for z/OS V3.1 | Technical Overview
Introduction to J2CA terminology
Common Client Interface (CCI)
J2EEApplication Server
Application Component
Resource Adapter
Enterprise Information System
System Contracts
Container-Component Contract
Connection ManagementTransactionManagementSecurityManagementLife Cycle ManagementWork ManagementMessage InflowTransaction Inflow
EIS Specific Interface
ConnectionPooling
TransactionManager
SecurityManager
New in JCA 1.5
3
IBM Software Group
© 2003 IBM Corporation15 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS TG
Client daemon
Gateway daemon
CICSServer
Protocol handler APPC
TCP62 TCP/IP
TCPor SSL
z/OS, OS/390VSE, TxSeries
Distributed platform
ctgjni.dll
JNI module
Java
Client
ctgclient.jarcicseci.rarcicseciXA.rarcicsepi.rar
ctgserver.jar
CTG for Multiplatforms
AIX, Linux/Intel, Linux/Power, z-Linux, HP-UX, Sun Solaris, Windows XP&2000
3
IBM Software Group
© 2003 IBM Corporation16 IBM CICS TS for z/OS V3.1 | Technical Overview
CTG for z/OS
z/OS
CICS TG
EXCI
Java
Client
Gateway
daemon
CICS TSProtocol handler
MRO
TCPorSSL
libctgjni.so
JNI module
Java
Client
ctgserver.jarctgclient.jarcicseci.rarcicseciXA.rar
IRC
3
IBM Software Group
© 2003 IBM Corporation17 IBM CICS TS for z/OS V3.1 | Technical Overview
Channel & Containers§ more flexible alternative to comarea
–data exchange between CICS programs and transactions
–logically related data in separate containers
–helps to avoid overlays•reduces complexity•simplify application changes
§ Container: CICS maintained storage–dynamically allocated by CICS–deletion after last program returns –no size limitation
§ a channel can hold 1 to n containers–unit for data exchange–only 1 channel can be transferred
§ efficient data transport–only changed data is transferred
§ flexible codepage conversion–CP can be defined in PUT/GET commands
Existing COMAREA application
Program A
EXEC CICS PUT CONTAINER(container name)CHANNEL(channel-name)FROM(structure)
EXEC CICS LINK PROGRAM(‘PROGRAMB’)CHANNEL(channel-name)
EXEC CICS GET CONTAINER(container name)INTO(structure)
Program B
EXEC CICS GETCONTAINER(container name)INTO(structure)
EXEC CICS PUTCONTAINER(container name)FROM(structure)
Program A
EXEC CICS LINK PROGRAM(‘PROGRAMB’)COMMAREA(structure)
Program B
EXEC CICS ADDRESSCOMMAREA(structure-ptr)
Appl. using Container and Channel
IBM Software Group
© 2003 IBM Corporation18 IBM CICS TS for z/OS V3.1 | Technical Overview
§ Container: can be compared to a „named Comarea“– storage allocation above 16MB, below 2GB– allocation, access and lifetime managed by CICS
• allocation at time of PUT command execution
– non-persistent storage
§ Channel: can be compared to a “named parm list”– one to many containers per channel (no limitation)– a server program may receive different channels
• processing logic depending on channel name– only one channel can be passed
• DPL, XCTL, START, RETURN
§ dynamic codepage conversion– Exec CICS GET / PUT Container (a) … INTOCCSID(x) / FROMCCSID(x)– overrides static definition in URI resource– requires z/OS conversion support
Channel & Containers ...
IBM Software Group
© 2003 IBM Corporation19 IBM CICS TS for z/OS V3.1 | Technical Overview
Channel & Containers – “best practices”
§ reduced complexity, optimal performance
– separate containers for Input and Output
– dedicated container for error information
– separate containers for different structures• no overlays
– separate containers for different data types• e.g. character / binary data
– separate containers for “read only” vs. read/write data
– separate container for large amount of data
– define channel and container names in copybook
IBM Software Group
© 2003 IBM Corporation20 IBM CICS TS for z/OS V3.1 | Technical Overview
§ URIMAP resource definition– associates URI with corresponding CICS processing
• CICS as web service provider– associates URI with PIPELINE and WEBSERVICE definitions
• CICS as web service requester or HTTP client– avoids hardcoding of server URLs
• CICS as HTTP server– can replace the analyser exit
§ CICS TS 3.1 HTTP listener extentions– conditionally conforms to HTTP/1.1 specifications
• persistent connections• pipelining (send several requests without waiting for acknowledgement)• chunking (separates a message in smaller pieces for performant transport)
– static response – e.g. DOCTEMPLATE or HFS file returned as static page
– dynamic response - using Exec CICS Web APIs in application
– redirection – redirects request to different server
CICS web support extentions
IBM Software Group
© 2003 IBM Corporation21 IBM CICS TS for z/OS V3.1 | Technical Overview
§ DOCTEMPLATEs– can now be stored in HFS files
§ Codepage conversion– CICS can use the Unicode™ conversion services of z/OS
• Converts character data between UTF-8, UTF-16, ASCII CPs and EBCDIC
• for setup see z/OS manual SA22-7649
– Codepage conversion can be specified in• Exec CICS Web API• Analyser programm• URIMAP resource definition• Container API
CICS web support extentions …
IBM Software Group
© 2003 IBM Corporation22 IBM CICS TS for z/OS V3.1 | Technical Overview
Utilisation of OTE TCBs and XPLINK for C, C++
§API=OPENAPI – program resource definition
–for Cobol, PL/I, ASM, C, und C++ programs (C without XPLink ! )
–programs must be reentrant and threadsafe !!
–program execution on new L8 / L9 TCBs
§Compile/Link of C, C++ programs with XPLINK option
–provides performance improvements and page protection
–programs must be reentrant and threadsafe !!
–program execution on new X8 / X9 TCBs
§OTE TCBs used for SSL connection management
–new SP mode TCB, owns shared LE enclave and SSL cache
–new S8 TCBs allocated from SSL-TCB pool for duration of SSL operation• reduces storage demand, allows more parallel SSL sessions
IBM Software Group
© 2003 IBM Corporation23 IBM CICS TS for z/OS V3.1 | Technical Overview
TCB switching CICSAPI vs. OPENAPI
Program start
EXEC CICSthreadsafe
EXEC SQL
EXEC CICSthreadsafe
EXEC SQL
EXEC SQL
Program start
EXEC SQL
EXEC CICSthreadsafe
EXEC CICSthreadsafe
EXEC SQL
EXEC SQL
EXEC CICSnon-threadsafe
EXEC RETURN EXEC RETURN
THREADSAFE + CICSAPI(as in V2)
THREADSAFE + OPENAPI
EXEC CICSthreadsafe
EXEC CICSthreadsafe
EXEC CICSthreadsafe
QR TCB QR TCBL8 TCB L8 TCB
EXEC SQL EXEC SQL
EXEC CICSnon-threadsafe
after task start immediate switch to L8
syncpointingsyncpointing
Caution: user key programs with DB2 + OpenApi: user key = L9 TCB, but DB2 must execute on L8 TCB
IBM Software Group
© 2003 IBM Corporation24 IBM CICS TS for z/OS V3.1 | Technical Overview
Security Updates
§ Support of Transport Layer Security TLS 1.0 (based on SSL 3.0)
§ Selection of new cipher suites
– support of AES cipher suites (128-bit, 256-bit)
– can now specify min. / max. encryption levels• SIT parm, suitable level is negotiated with clients
§ Performance improvements for SSL
– SSL cache in local storage or coupling facility (sysplex)
– support for more parallel SSL sessions through S8 TCB pool
§ Certificate Revocation list (CRL) processing
– allows checks against the CRL during SSL handshake with clients
– new transaction CCRL allows updates to CRL in an LDAP server
§ Revoked User now results in USERIDERR
§ Support for case sensitive passwords
IBM Software Group
© 2003 IBM Corporation25 IBM CICS TS for z/OS V3.1 | Technical Overview
Architectural patterns – new sample application
§ new CICS Sample Application
– demonstrates “best practices”
• separation of presentation logic, business logic and data access• usage of channel and containers• CICS web services with SOAP over http
– Catalog and Order Application
• executables and source code available• Cobol• data access to VSAM data sets
– illustrates end-to-end scenario
IBM Software Group
© 2003 IBM Corporation26 IBM CICS TS for z/OS V3.1 | Technical Overview
CPSM WUI
§ Improved panels– more information
– multi column details
– display filter
§ User favorites and group profiles
§ Result set warning
§ Confirmation for used filter
§ dynamic selection lists
§ improved BAS admin views
§ Support for new resources in CICS 3.1
§ Batchrep improvements
CollapsibleFilters
Reduction inwhite space
Ability to add aview to favourites
Favourite views
User Profiles
Improved visualpresentation
Selection lists
Single point of control and definition, many usability enhancements
IBM Software Group
© 2003 IBM Corporation27 IBM CICS TS for z/OS V3.1 | Technical Overview
Simplified CICSPlex SM Setup and Configuration
Ø CAS and TSO Component no longer needed
1. install and activate new CMAS
2. Configure MP CMASa. define CICSplexb. define regionsc. define WUI serverd. link to partner CMAS
3. configure second CMAS- define link to MP CMAS
4. install agent code (MASs)
5. Install and activate WUI Server
6. Auto-import WUI views
Sysplexinformation
MVS1 MVS2
CPSMRepository
MPCMAS
CPSMWUI Server
CPSMRepositoryCMAS
CICS CICS CICS CICS CICSCICS
IBM Software Group
© 2003 IBM Corporation28 | Technical Overview
CICS Information CenterThe Eclipse framework reflects strategic direction for delivering IBM documentation
§ New search engine§ Consistent look and feel§ Integration with other
product information§ Customizable – add your
own information§ Improved navigation§ Available on the IBM Web
site, installable on your workstation, or servers;– Windows 2000, XP – Linux Red Hat Enterprise 3.0 – Linux SUSE Enterprise 8 and 9– AIX® V5.2 and V5.3– For server installation only: – z/OS V1.4, or later – z/Linux Red Hat Enterprise 3.0 – z/Linux SUSE Enterprise 8 and 9
IBM Software Group
© 2003 IBM Corporation29 IBM CICS TS for z/OS V3.1 | Technical Overview
Discontinued functions
N OS/VS COBOL – programs abend ALIK
V 1 byte console ids
V High Performance Java (HPJ)
V ECI Base Classes (ECIREQUEST)
C recommendation: use CCI Connector for CICS
V Common Connector Framework (CCF)
C recommendation: use CCI Connector for CICS
V TCAM TOR
V CPSM remote MAS agent for Windows
V CICS Transaction Affinities Utility has only Scanner component
C Detector and Reporter have moved to IBM CICS Interdependency Analyzer for z/OS
IBM Software Group
© 2003 IBM Corporation30 IBM CICS TS for z/OS V3.1 | Technical Overview
CICS TS V3.1 packaging
§ CICS TS V3.1 elements– CICS Transaction Server
– CICSPlex System Manager
– Information Center
– REXX Development and runtime for CICS
– CICS Application Migration Aid
– CICS Integrator Adapter
§WebSphere Developer for z (WD/z) promotion– Integrated development environment for CICS and WebSphere
• COBOL, PL/I, Java and J2EE development• z/OS file system integration
– One license included, no service entitlement
IBM Software Group
© 2003 IBM Corporation31 IBM CICS TS for z/OS V3.1 | Technical Overview
Prerequisites
§ z/OS Version 1 Release 4 (5694-A01) +
§ IBM SDK for z/OS Java 2 Technology Edition, V1.4.2• Prerequisite for CICS Web services assistant (DFHLS2WS / WS2LS)• Java programs and EJBs in CICS benefit from many improvements
§ for WS-Security support§ IBM XML Toolkit for z/OS V1.7 (no charge, Pnr.5655-J51)
§ latest compilers supported– IBM Enterprise COBOL for z/OS and OS/390 V3 (5655-G53)
– IBM Enterprise PL/I for z/OS and OS/390 V3 (5655-H31)
– z/OS C/C++ (component of 5694-A01)
§ see announcement letter (204-285) for a complete list of HW/SW prerequisites and supported compilers
IBM Software Group
© 2003 IBM Corporation32 IBM CICS TS for z/OS V3.1 | Technical Overview
Planning
§ CICS TS V1 went out of service in April 2006
§ SOAP for CICS Feature can coexist
– still supported to ease migration to CICS Web Services
– message adapters need modification
• Channel & Container interface
§ Statement of direction for discontinued functions
– CPSM TSO User Interface after CICS TS 3.1
– in a future Release• ONC RPC feature• CICS Web Interface COMMAREA interfaces• CICS Web Server plug-in
IBM Software Group
© 2003 IBM Corporation33 | Technical Overview
Summary§ CICS TS and WebSphere Application Server are IBM's strategic
middleware products that together support practically any mission critical solution– Interoperate well using Web services and connectors to support end-to-end on demand systems– Complement z/OS QoS such as high availability, scalability, low cost per transaction, security
§ CICS TS provides the base for the majority of mainframe applications today– An efficient and optimized runtime for the reuse and transformation of existing CICS applications– Provides easy to use services that exploit new technologies by building on CICS skills– First class support and management of mixed application types and workloads
§ Web services capabilities to extend CICS applications to a Services Oriented Architecture
§ Support for industry-leading SSL and TLS protocols
Increased ease of CICS Integration
EnhancedApplication Transformation
Improved performance &Enterprise Management
§ Ability to leverage single development tool for application transformation and integration
§ Service Flow Feature§ Optimized CICS data exchange capabilities
§ Improved workload throughput§ Enhanced C and C++ programs performance
§ Extension of the CICSPlex SM Web User Interface
IBM Software Group
© 2003 IBM Corporation34 IBM CICS TS for z/OS V3.1 | Technical Overview
Further Information§ IBM CICS Transaction Server for z/OS V3.1
– IBM Software Announcement 204-285, Transaction Servers & Tools e-newsletter, education, and services - see ibm.com/cics
– Release Guide, Migration Guide, Books and Manuals, Brochures, Demos, and Technical documents – see ibm.com/cics/library/
§ IBM CICS Tools - see ibm.com/cics/tools
§ IBM Websphere Enterprise Developer -see ibm.com/software/awdtools/studioenterprisedev/
§ IBM SDK for z/OS, Java 2 Technology Edition V1.4
go to ibm.com/servers/eserver/zseries/software/java
§ IBM z/OS - see ibm.com/servers/eserver/zseries/zos
thanks for your attention
IBM Software Group
© 2003 IBM Corporation35 IBM CICS TS for z/OS V3.1 | Technical Overview
Web services terminology
§ Extensible Markup Language (XML)– A standard for document markup, which uses a generic syntax to mark up
data with simple, human-readable tags. The standard is endorsed by the World Wide Web Consortium (W3C).
§ Service provider– The collection of software that provides a Web service.
§ Service provider application
– An application that is used in a service provider. Typically, a service provider application provides the business logic component of a service provider.
§ Service requester– The collection of software that is responsible for requesting a Web service
from a service provider.
§ Service requester application– An application that is used in a service requester. Typically, a service
provider application provides the business logic component of a service requester.
§ SOAP– Formerly an acronym for Simple Object Access Protocol. A lightweight
protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts:
• An envelope that defines a framework for describing what is in a message and how to process it.
• A set of encoding rules for expressing instances of application-defined data types.
• A convention for representing remote procedure calls and responses.
– SOAP can be used with other protocols, such as HTTP.
§ SOAP intermediary – A SOAP node that is both a SOAP receiver and a SOAP sender and is
targetable from within a SOAP message. It processes the SOAP header blocks targeted at it and acts to forward a SOAP message towards an ultimate SOAP receiver.
§ SOAP node
– Processing logic which operates on a SOAP message.
§ UDDI - Universal Description, Discovery and Integration– Universal Description, Discovery and Integration (UDDI) is a specification
for distributed Web-based information registries of Web services. UDDI is also a publicly accessible set of implementations of the specification that allow businesses to register information about the Web services they offer so that other businesses can find them.
§ Web service– A software system designed to support interoperable machine-to-machine
interaction over a network. It has an interface described in a machine-processable format (specifically, Web Service Description Language, or WSDL).
§ Web service binding file– A file, associated with a WEBSERVICE resource, which contains
information that CICS uses to map data between input and output messages, and application data structures.
§ Web service description
– An XML document by which a service provider communicates the specifications for invoking a Web service to a service requester. Web service descriptions are written in Web Service Description Language (WSDL).
§ WSDL - Web Service Description Language– An XML application for describing Web services. It is designed to
separate the descriptions of the abstract functions offered by a service, and the concrete details of a service, such as how and where that functionality is offered.
§ XML
– Extensible Markup Language.
§ XML namespace– A collection of names, identified by a URI reference, which are used in
XML documents as element types and attribute names.
§ XML schema– An XML document that describes the structure, and constrains the
contents of other XML documents.
§ XML schema definition language– An XML syntax for writing XML schemas, recommended by the World
Wide Web Consortium (W3C).