Rational Developer for System z

How an operation uses messages

You use an operation to specify the invocation information for a program, including the program's input message, its output message, and its fault messages if any.

An operation is an artifact that specifies the information required to invoke a flow, a nonterminal application, or an outbound Web service (see Basic information about operations).

An operation contains the following elements:

Table 1. Elements of an operation
Element:   Description:
Port type: The class to which the operation belongs.
Operation: The name of this operation. The operation contains a reference to the input message, a reference to the output message if any, and references to fault messages if any.
Input message: A reference to the input message of the program to be invoked.
Output message: A reference to the output message of the program to be invoked.
Faults messages: A reference to the faults messages if any of the program to be invoked.
Thus an operation specifies the type of the program to be invoked and (through references) the interface messages of the program (see Interface messages).
Note: By default the operation is given the same name as the program that it describes, but the name does does not have to be the same. The name of the program is stored in the generation properties file.

Operations are stored in operations files (extension .wsdl). You can create or modify operations in the operations editor (see Operations editor).

After you have defined the elements of an operation you can associate the operation with the program that the operation describes. There are two different kinds of association:


Terms of use | Feedback

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