The inputs and outputs of each service operation are defined in the service as an XML schema. Before a service interaction can be used in a business process, its schema must be extracted from the WSDL file and saved as .xsd files. The Service Interaction Editor is used to extract the schema file. If a WSDL has an input schema, you must extract that schema for your operation. You can extract both an input and output schema for web services and databases only.
To extract a schema from a service:
From the Orchestration
Navigator view, double-click on the .iface file.
The Service Interaction Editor displays the .iface file.
Expand the tree to
display the input and output nodes below the relevant operation. You may
have only an input or multiple inputs and outputs.
Note that input and output are relative to the operation of the service,
not to a business process.
For messaging,
if using the service as a Notification operation:
Right-click the Output node and select Extract Schema.
For messaging,
if using the service as a One-Way operation:
Right-click the Input node and select Extract Schema.
For databases,
using the service as a Request/Reply:
Individually select and extract the schema for both the input and the
output node.
In the Save-As window, select the Schemas folder and use the name that is automatically generated or change that name. (The extension is automatically appended.)
Click OK.
Properties for each service interaction are displayed in the Properties View and references to where the service interaction is used are displayed in the Dependencies view.
Note: Because a service interaction has numerous dependencies, be careful when you delete, remove, move, or rename an .iface file that is already being used in a business process.