Using WSDL References for Efficient Design
A BPEL process uses the definitions from Web Services Description Language (WSDL) files. WSDL files contain the namespace, partner link types, operations, and messages needed to define process activities, and WSDL files are required in order to create a valid, executable BPEL definition.
You can generate WSDL files in Process Developer or you can add them to the Project Explorer view of Process Developer before you begin creating a process definition.
- •WSDL files provide several key productivity features:
- •You can drop a WSDL operation onto the Process Editor to automatically create an Web Service interaction activity (Receive, Receive/Reply, Invoke, OnMessage, or OnEvent).
- •You can automatically create the WSDL extensions required for a BPEL process if they do not already exist (partner link types, properties, property aliases).
- •You can use the WSDL definitions across processes.
Creating WSDL Extensions for BPEL
A BPEL process depends upon WSDL extensions that are unique to BPEL. Process Developer can create these extensions automatically if they do not exist in your WSDL files. The extensions are partner link types, properties, and property aliases.
- •A partner link type defines the roles played by a service and the port type provided by the service. For details, see Partner Link Type.
- •Properties and property aliases are significant for correlating a group of messages in a process and can also be used for any process variable. For more information, see Adding Variable Properties and Property Aliases.
Starting a Process by Dropping an Operation onto the Process Editor
You can begin designing a BPEL process by using the key productivity features in Process Developer. Using either of the following starting points, you expose WSDL operations that can be dragged to the Process Editor canvas to automatically create activities:
- •Add the Web services and partners used by the process, with BPEL extensions automatically generated. See Participants.
- •Use your existing WSDL to create BPEL extensions. See Interfaces, Service References, and Local WSDL.