Rational Developer for System z

Using the wizard launchpad

This topic describes how to use the Enterprise Service Tools Wizard Launchpad to start a single-service wizard.NOTE: This is not applicable for "An Enterprise Service Tools single-service project"

The following is not applicable for "An Enterprise Service Tools single-service project".

The Enterprise Service Tools Wizard Launchpad allows you to launch a single-service wizard and to specify certain options for the wizard.
Note: XML Transformation for CICS® runtime is not supported on the wizard launchpad.
The single-service wizards are as follows:
To start one of these wizards from the launchpad:
  1. Select options on the launchpad.
  2. Click Start.
The options on the launchpad are as follows:
Note: The list boxes on the launchpad do not contain all of their selections in all circumstances. The following details are provided for each list box.
Host runtime
Select the runtime environment on the remote z/OS® system for which you want the wizard to generate service interface files:
  • Web Services for CICS
  • SOAP for CICS
  • IMS™ SOAP Gateway
  • IMS Web 2.0
  • Batch, TSO, and z/OS UNIX System Services
Note: XML Transformation for CICS runtime is not supported on the wizard launchpad.
Each of these available runtime environments has the same name (such as Web Services for CICS) as the particular type of single-service project with which it is associated. (Each of the available types of single-service projects is used to generate files for one runtime environment - see The available types of single-service projects).
Which of these selections are present in the Host runtime list when the launchpad opens depends on the context from which the launchpad is started (see Starting the wizard launchpad):
Context from which the launchpad is started: Selections available in the Host runtime list:
A single-service project.

Example: A single-service project with a type of Web Services for CICS.
Only the runtime environment associated with the type of the single-service project.

Example: Web Services for CICS
Another type of project (such as a Local COBOL or PL/I project in the z/OS Projects perspective). All supported runtime environments.
Remote Systems view. All supported runtime environments.
Development scenario
Select the development scenario for which you want the wizard to generate files:
  • The bottom-up scenario
  • The top-down scenario
  • The meet-in-the-middle scenario
The selection that you make in this list determines which wizard opens when you click Start on the launchpad:
Selected development scenario: Wizard started: Link
Create New Service Interface (bottom-up) Create New Service Interface (bottom-up) Create New Service Interface (bottom-up) wizards
Create New Service Implementation (top-down) Create New Service Implementation (top-down) Create New Service Implementation (top-down) wizard
Map to an Existing Service Interface (meet-in-middle)
  • New XML to COBOL Mapping wizard (request mapping) wizard
  • New XML to COBOL Mapping wizard (response mapping) wizard
  • Map to an Existing Service Interface (meet-in--middle)
Map to an Existing Service Interface (meet-in-middle) wizard
Which of the available development scenarios are present in the Development scenario list when the launchpad opens depends on a number of factors, including the selected host runtime (see Summary of supported runtime environments, scenarios, and conversion types).
Important: The meet-in-middle development scenario is present in the list only when you start the Enterprise Service Tools Wizard Launchpad from a project other than Enterprise Service Tools single-service project, such as a Local Project (Workstation COBOL or PL/I) in the z/OS Projects perspective (see Two wizards used in the meet-in-middle development scenario).
Application mode
Select the type of Web service application for which you want the wizard to generate files:
  • Service Provider
  • Service Requester
Conversion type
Select the type of data conversion that you want to be used by the generated service interface files:
  • Compiled XML Conversion
  • Interpretive XML Conversion
See Runtime XML conversion: compiled or interpretive.
Which of these conversion type selections are present in the list when the launchpad opens depends on a number of factors, including the selected host runtime (see Summary of supported runtime environments, scenarios, and conversion types).
Save generation properties
The behavior and effect of this check box depend on whether the launchpad is started from a single-service project or from some other type of project.
When the launchpad is started from a single-service project:
In this situation the check box is always selected and cannot be unselected.
The effect of having the check box selected is that the wizard that is launched saves the values that you set for the various options in the wizard.
After the wizard has closed, you can re-run the wizard with the most recently used options by starting the launchpad from the project name (see Starting the launchpad from an Enterprise Service Tools single-service project).
When the launchpad is started from some other type of project:
In this situation the check box is selectable.
If you select the check box, then the wizard that is launched creates three generation properties files containing the specifications, in XML format, of the options that you select in this instance of the wizard.
The default names of the three files are Container.xml, PlatformProperties.xml, and ServiceSpecification.xml. You can specify different names for these files on the Properties tab of the File, data set, or member selection page of the wizard (see Properties tab).
You can then use these generation properties files to run the batch processor with the same options that you used in this instance of the wizard.
This automatic generation saves you the trouble of building the generation properties files for the batch processor from scratch.

Terms of use | Feedback

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