ActiveBPEL® Designer User’s Guide
Previous | Next
Creating a New Interface
No WSDL? You can use the New Interface wizard as a quick start
to generating the basics of a WSDL. The starting point for generating
a WSDL is to have one or more of the following as a basis for input
and output messages of a port type and operation:
- XML schema
- Sample XML data
To create a new interface:
- Add an xsd or xml file to a project
folder within an orchestration project. These files should describe
data types.
- In the Interfaces view, select New Interface from the
toolbar.
- In the New Interface wizard, select whether the new operation
is synchronous or asynchronous:
- request-response operation
- one-way operation
- Select the data type you want to use to describe each
of the operation’s message(s):
- Browse to the schema or sample and select it. For a schema,
select the to use for the message.
- View the message in the Preview.
- Based on the names you selected for input and output,
the wizard creates the required WSDL elements. Create more meaningful
names for the Port Type, Operation, Target Namespace, Partner Link
Type, and Role elements.
The Target Namespace is a convention
of XML Schema that enables the WSDL document to refer to itself.
It is a value that is unique, different from all other namespaces
that are defined.
- Save the new WSDL with the suggested name, or type in
a new name and save the file to a project location.
- View the generated WSDL in the WSDL editor to make corrections
and additions.
The generated WSDL is a good starting point for a process
interface. You may need to modify the WSDL as follows:
- Correct or add a schema location
- Add fault names and messages
- Add another operation and add to the partner link type
generated. (A partner link type can have two roles, which represent
two different services that communicate asynchronously. )
- Add a meaningful namespace prefix mapping for the
tns prefix,
and then when you use the operation wizard to create activities,
the prefix will be automatically added to the process
Copyright (c) 2004-2008 Active Endpoints, Inc.