Rational Developer for System z

Importing a Web service definition

The Import Web Services Definition wizard reads a Web service definition from an existing WSDL file and generates from that definition the artifacts that define the invoke interface for a flow.

For more information about the artifacts generated by this wizard, see the subsection Files created when a Web service definition is imported further on in this topic.

Importing a Web service definition saves you the work of manually creating an operations file and a message file to define the invoke interface for a flow (see A flow and Basic information about operations for general information about flows and operations).

After you create an invoke interface for a flow, you must associate it with the flow that you want to use it with (see Associating an operation with the flow). You can associate the invoke interface either with the primary flow in your design or with a subordinate flow.

Note: As a convenience, you can also import a WSDL file and associate the invoke interface with a flow (that is, you can perform the same functionality that is in this wizard) when you create a new flow (see 2. Associate operation) or when you create the primary flow of a new service flow project (2. Associating a service interface).

Using the Import Web Services Definition wizard

Note: This same wizard is used in a different context to import an outbound Web service definition into an outbound Web services subproject of your service flow project (see Importing an outbound Web service definition).
To import a Web service definition:
  1. In the EST Project Explorer, right-click anywhere within a service flow project.
  2. Select Import > WSDL. The Import Web Service Definition wizard opens.
  3. On the first page of the wizard, titled Import Web Service Definitions:
    1. In the WSDL files to import list box, list the WSDL files that contain the Web service definition or definitions that you want to import:
      1. Click FileSystem to select a file from the workstation's file system, or click Workspace to select a file from the current workspace that you are using in the workbench.
      2. Click Remote to select a file on the remote system.
      3. Click Remove to remove a file from the list.
    2. In the Project Name list box, select the interface definition subproject in which you want the new operation file and message file for each imported Web service to be stored.
      Note: The only types of subprojects listed in the Project Name list box are existing interface definition subprojects.
    3. Select the list box Overwrite existing resources without warning if you want the wizard to overwrite existing files having the same names without prompting you.
    4. Click Next to go to the next page of the wizard or Finish to close the wizard:
      • Click Next and go to the next page if you want to select which Web service definitions are to be imported.
      • Click Finish if you want the wizard to import all the Web service definitions in all the WSDL files listed in the WSDL files to import list box.
  4. On the second page of the wizard, titled Select operations:
    1. Select the check box beside each Web service definition that you want to import.
      Note: By default, all the check boxes are selected.
    2. Click Finish.

When you click Finish, the wizard creates, in the interface definition subproject that you selected on the first page of the wizard, a set of files for each Web service definition that you selected on the second page of the wizard (or for all the Web service definitions in all the WSDL files listed on the first page of the wizard, if you clicked Finish on the first page).

For a description of each type of file, see the next section of this topic.

Files created when a Web service definition is imported

The types of files created for each imported Web service definition are listed in Table 1:
Table 1. Types of files created for an imported Web service definition
Folder in the interface definition subproject: Type of file created in the folder: Example of type of file created:
Operations folder An operations file containing an operation that defines an invoke interface for a flow. processCatalogOrder.wsdl
Message folder A message file containing the messages referenced by the operation. processCatalogOrderMessages.sfmxsd
Each type of file that is created is described in Table 2:
Table 2. Description of types of files created
File: Description:
Operations file The operations file contains only one operation. This operation contains the interface information needed to invoke a flow, including a port type, a program name, and references to an input message, an output message, and one or more fault messages if any.
Note: These operations files have the same format as the operations files used in the Operations folder of a nonterminal applications subproject, and similar content (see Working with operations and Operations editor).
Messages file The messages file contains definitions of the input message, the output message, and the fault messages (if any) referenced by the operation in the operations file.
Note: These message files have the same format as the message files used in the Messages folder of a nonterminal applications subproject, and similar content (see Working with messages and Flow message editor).

Terms of use | Feedback

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