Rational Developer for System z

Web services enablement scenarios for each project type

This topic describes the Web services enablement scenarios available with each project type.

The types of projects are divided into four categories, as shown in Table 1.

The Web service enablement scenarios are bottom-up development, meet-in-middle development, and top-down development (see Web services enablement scenarios).

Note: For single-service projects there are several project subtypes, based on the runtime environment for which the project generates output files (shown in the Runtime column of Table 2:
Table 1. Categories of Projects
Category: Types of projects included in this category: Basis for categorization:
Single-service project
  • Web Services for CICS® Project
  • SOAP for CICS Project
  • XML Transformation for CICS Project
  • IMS™ SOAP Gateway Project
  • IMS Web 2.0 Project
  • Batch, TSO, z/OS® UNIX System Services Project
  • Each of these types of projects helps you to generate files associated with a single Web service; and
  • The development process for each of these types of projects is similar.
Database project Database application project This type of project helps you create an application that accesses a database
Service flow project Service flow project In this type of project you create a flow (or service flow) from which you can generate a comprehensive Web service that collects and processes data from multiple programs.
SCA project SCA (Service Component Architecture Project) project In this type of project you can define SCA components for CICS and assemble them into SCA composites. For additional information, refer to Developing Service Component Architecture (SCA) applications
Table 2. Web Services Enablement Scenarios for Single-Service Projects in Enterprise Service Tools
Runtime: Tasks you can accomplish:
Web Services for CICS Project
  • Bottom-up development: Generate a Web service description and runtime-specific request and response XML message processing from a high level language data structure. You can use this method to create a service provider program (one that runs using Web Services for CICS protocols) for an existing CICS application.
  • Meet-in-the-middle development: Define mappings between high level language data structures and WSDL, XML, or XSD files. You can use this method to generate runtime-specific request and response XML message processing based on the mappings.
    Note: You can use mapping to an Existing Service Interface (meet-in-middle) wizard when you run the Enterprise Service Tools Wizard Launchpad inside the Enterprise Service Tools perspective. Access to the wizard is still allowed when you run the wizard outside the Enterprise Tools perspective (see Overview of the contexts for opening the launchpad).
  • Top-down development: Generate a high-level language structure and runtime-specific request and response XML message processing from a Web service description (WSDL file). You can use this method to:
    • Create a service provider program (one that runs using Web Services for CICS protocols) for a new CICS application.
    • Create a service provider program (one that runs using Web Services for CICS protocols) for an existing CICS application.
    • Create a service requester program (one that runs using Web Services for CICS protocols).
See Web services for CICS project.
SOAP for CICS Project
  • Bottom-up development: Generate a Web service description and runtime-specific request and response XML message processing from a high level language data structure. You can use this method to create a SOAP-enabled service provider program) for an existing CICS application.
  • Meet-in-the-middle development: Define mappings between high level language data structures and WSDL, XML, or XSD files. You can use this method to generate runtime-specific request and response XML message processing based on the mappings.
See SOAP for CICS project.
XML Transformation for CICS Project
  • Bottom-up development: Generate files for the XML Transformation and runtime-specific XML processing from a high level language data structure.
  • Top-down development: Generate a high-level language structure and runtime-specific XML processing from an XSD file.
Note: Meet-in-the-middle development is not supported.
IMS SOAP Gateway Project
  • Bottom-up development: Generate a Web service description and runtime-specific request and response XML message processing from a high level language data structure. You can use this method to create a service provider program (one that runs using ISM SOAP Gateway protocols) for an existing CICS application.
  • Meet-in-the-middle development: Define mappings between high level language data structures and WSDL, XML, or XSD files. You can use this method to generate runtime-specific request and response XML message processing based on the mappings.
See IMS SOAP Gateway project.
IMS Web 2.0 Project Supports the creation of artifacts which enable IMS programs services running in the IBM Mashup Hub. This enables the transformation of IMS assets into reusable components of Web 2.0 applications through XML, ATOM, or RSS feeds..
Note:
  1. Currently only Bottom-up, Conversion Type Compiled, development is supported.
  2. Conversion from a Single-service project to Service-flow project is not allowed for IMS Web 2.0 projects.
For more information on IMS Web 2.0, see http://www.alphaworks.ibm.com/tech/ibmmsk, IBM Mashup Starter Kit.
Batch, TSO, z/OS UNIX System Services Project
  • Bottom-up development: Generate a Web service description and runtime-specific request and response XML message processing from a high level language data structure. You can use this method to create a service provider program (one that is not runtime-specific) for an existing CICS application.
  • Meet-in-the-middle development: Define mappings between high level language data structures and WSDL, XML, or XSD files. You can use this method to generate non-runtime-specific request and response XML message processing based on the mappings.
See Batch, TSO, z/OS UNIX System Services project.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)