Skip Navigation Links | |
Exit Print View | |
Oracle Java CAPS BPEL Designer and Service Engine User's Guide Java CAPS Documentation |
BPEL Designer and Service Engine User's Guide
To View the Installed or Deployed JBI Components
The Composite Application Project
BPEL Designer and Service Engine Features
Supported WS-BPEL 2.0 Constructs
BPEL Service Engine and Oracle SOA Suite
Understanding the BPEL Module Project
Creating Sample Processes in the BPEL Designer
An Asynchronous Sample Process
Travel Reservation Service Sample
Creating a Sample BPEL Module Project
Navigating in the BPEL Designer
Element Documentation and Report Generation
Creating Documentation for an Element
Collapsing and Expanding Process Blocks in the Diagram
To Collapse and Expand a Process Block
Zooming In and Out of the Diagram
Printing BPEL Diagrams and Source Files
To Preview and Print a BPEL Diagram or Source File
Creating a BPEL Module Project
To Check the Status of the GlassFish V2 Application Server in the NetBeans IDE
To Register the GlassFish V2 Application Server with the NetBeans IDE
To Start the GlassFish V2 Application Server in the NetBeans IDE
Creating a new BPEL Module Project
To Create a BPEL Module Project
Creating the XML Schema and the WSDL Document
Creating a BPEL Process Using the BPEL Designer
Creating a Composite Application Project
To Create a New Composite Application Project
Building and Deploying the Composite Application Project
To Build and Deploy the Composite Application Project
Testing the Composite Application
Test the HelloWorldApplication Composite Application Project
Developing a BPEL Process Using the Diagram
Configuring Element Properties in the Design View
Finding Usages of BPEL Components
To Find Usages of a BPEL Component
The BPEL Designer Palette Elements
Adding BPEL Components to the Process
Using the Partner Link Element
Dynamic Partner Links and Dynamic Addressing
Using the CompensateScope Element
CompensateScope Element Properties
Adding an Else If Branch to the If Element
Adding an Else Branch to the If Element
Using the Repeat Until Element
Repeat Until Element Properties
Adding Branches to the Flow Element
Changing the Order of Elements inside Flow
Adding Child Activities to the Sequence
Changing the Order of Elements inside Sequence
To Open the BPEL Mapper Window
To Create a Mapping Without Using any Functions
To Use a Function in a Mapping
To Delete a Link or Function in a Mapping
Using Type Cast and Pseudo-Components
Type Cast and Pseudo Component Limitations
Using Normalized Message Properties
Using Normalized Message Properties in a BPEL Process
Using Predefined Normalized Message Properties in a BPEL Process
To Use Predefined Normalized Message Properties in a BPEL Process
Adding Additional Normalized Message Properties to a BPEL Process
To Add a Normalized Message Property Shortcut to a BPEL Process
To Edit an NM Property Shortcut
To Delete an NM Property Shortcut
To Add a Normalized Message Property to a BPEL Process
BPEL Code Generation Using NM Properties
General Normalized Message Properties
Binding Component Specific Normalized Message Properties
To Add a Compensation Handler to Scope or Invoke Elements
To Add a Termination Handler to Scope or Process Elements
Understanding Correlation. Using the Correlation Wizard
Elements That Use and Express Correlation
Defining Correlation Using the Correlation Wizard
BPEL Process Logging and Alerting
To Set the Log Level for the BPEL Service Engine
Configuring the BPEL Service Engine Runtime Properties
Accessing the BPEL Service Engine Runtime Properties
BPEL Service Engine Deployment Artifacts
Testing and Debugging BPEL Processes
To Add a Test Case and Bind it to a BPEL Operation
Steps in Debugging BPEL Processes
Starting and Finishing a BPEL Debugging Session
Using Breakpoints to Debug BPEL Processes
Group operations over breakpoints
Monitoring Execution of BPEL Processes
Correlation Sets and Faults information
BPEL Debugger Console Messages
Monitoring the BPEL Service Engine
Installing the BPEL Monitor API and Command Line Monitoring Tool
To Install the Monitoring Tool
Using the BPEL Monitor Command Line Tool
To Use the BPEL Monitor Command Line Tool
Configuring Quality of Service (QOS) Properties, Throttling, and Redelivery
Configuring the Quality of Service Properties
To Access the Config QOS Properties Editor
Configuring Message Throttling
Configuring an Endpoint for Throttling
Using Dynamic Partner Links and Dynamic Addressing
Using a Literal to Construct an Endpoint
Using an Existing Partner Link's Endpoint
Using an Incoming Message to Extract the Endpoint
Using a Database Query to Provide an Endpoint
Sending Service Endpoint References
Configuring Persistence for the BPEL Service Engine
Setting the JVM Classpath to the Database JDBC Drivers
To Set the GlassFish JVM Classpath Settings
Configuring the User and Database for Persistence
Creating an XA Connection Pool and a JDBC Resource
To Create an XA Connection Pool
Creating a Non-XA Connection Pool and JDBC Resource
Enabling Persistence for the BPEL Service Engine
To Enable Persistence for the BPEL Service Engine
Truncating and Dropping Tables
Configuring Failover for the BPEL Service Engine
Using BPEL Schemas Different from the BPEL 2.0 Specification
Relationship of Service Endpoint to Test Cases
GlassFish V2 Application Server HTTP Port
Travel Reservation Service Endpoint Conflict
Disabling Firewalls when Using Servers
Required Correlation Set Usage is Not Detected by the Validation System
The proceeding sections describe the steps used to create a simple BPEL Module project. To demonstrate the procedures we are using the Synchronous sample project.
Accordingly, the typical procedure to follow when building a BPEL process is:
Creating a new BPEL Module Project using the New Project wizard. Creating the BPEL module project also includes:
Creating an XML Schema using the XSD Editor.
Creating the WSDL Documents using the New WSDL Editor.
Create the BPEL Processes using the BPEL Designer.
Creating a Composite Application Project.
When new projects are created using the sample projects that are included with GlassFish, the Composite Application projects are created automatically. When you create a project from scratch, you need to create the Composite Application project manually.
Add JBI Modules to the Composite Application project.
(Optional) Build the Composite Application project and make sure that the Application Server is started.
Build and Deploy the Composite Application Project to the BPEL Service Engine.
For sample processes, test cases are automatically created; for new projects, you need to create at least one test case.
(Optional) Debug the BPEL process.
The BPEL Service Engine starts together with GlassFish. Before deploying and performing test runs of a Composite Application project in the NetBeans IDE, make sure that the GlassFish Application Server is started.
The Servers node should contain a GlassFish V2 sub-node. If the GlassFish V2 node does not appear, go to To Register the GlassFish V2 Application Server with the NetBeans IDE:
If a green arrow badge appears on the GlassFish V2 node, the server is running. If a green arrow badge does not appear, go to To Start the GlassFish V2 Application Server in the NetBeans IDE.
The Add Server Instance dialog box opens.
The Add Server Instance dialog box opens.
The IDE uses this name to identify the server.
The Platform Location Folder page opens.
If you accepted the default values during the installation, the user name is admin and the password is adminadmin.
Application server startup complete.
When the server is running, the IDE displays a green arrow badge on the GlassFish V2 node.
The BPEL Service Engine is represented as sun-bpel-engine in the Services window of the IDE, under the GlassFish V2 -> JBI nodes.
The following sections use the Synchronous sample project, and provide step-by-step directions for creating a simple BPEL module project, using the Synchronous sample project.
The New Projects wizard appears.
The Projects window now contains a project node for the BPEL Module project.
Generally, the steps used to create a BPEL module project are:
Create a New BPEL Project
Create the XML Schema or XSD file
Create the WSDL Documents
Create the BPEL Process
The XSD file (XML Schema) helps to define the projects message structure or operations. Complex message structures are defined in the XSD file and imported into the WSDL Document. The WSDL Documents define the interfaces for the project. The BPEL Designer enables you to graphically design your BPEL business process.
To create the XML Schema and WSDL Document for this tutorial, following the directions provided in Creating a “Hello World” Composite Application. After you have created the XML Schema and WSDL, return here.
Now that you have created your XML Schema and WSDL Document, you can create your BPEL process.
The New BPEL Process dialog box appears.
The new BPEL file opens in the Design view of the BPEL Designer.
If the Palette and Properties windows are not displayed in your current view, click Windows -> Reset Windows on the NetBeans menu.
The IDE provides visual prompts to show you where you can drop the selection.
The BPEL Editor adds a partner link to the canvas.
The Receive1 activity is added to the process box.
The Receive1 Property Editor appears.
The IDE populates the Operation field with NewWSDLOperation.
The New Input Variable dialog box appears.
The Design view displays the new connection between PartnerLink1 and the Start activity in the process box.
A Reply1 activity is added to the design view canvas.
The Reply1 Property Editor appears.
The IDE populates the Operation field with NewWSDLOperation.
The New Input Variable dialog box appears. Click OK to accept the default values.
The Design view displays the new connection between the End activity in the process box and PartnerLink1.
The Assign1 activity is added to the design view canvas.
The BPEL Mapper appears.
This assignment copies the input statement into the output.
A BPEL Module project is not directly deployable. You must first add a BPEL Module project, as a JBI module, to a Composite Application project. You can then deploy the Composite Application project. Deploying the project makes the service assembly available to the application server and enables its service units to run.
The Select Project dialog box opens.
The Select Project dialog box closes and the HelloWorld.jar file is added to the JBI Modules node of the HelloWorldApplication Composite Application
Building a project compiles the BPEL source file and packages the BPEL file and web service artifacts, including WSDL and XSD files, into a JAR archive. Deploying the project compiles the files in the Composite Application project, packages the compiled BPEL and related web service artifacts (including WSDL and XSD files) into an archive, and deploys them to the Application Server.
When the build is complete the Output window reports Build Successful. If the Output window is not visible, choose Window -> Output -> Output.
If you do not see the deployed project, right-click the Service Assemblies node and choose Refresh.
You can test your Composite Application project by adding test cases, binding to the operation, supplying input, and then using the tester.
The New Test Case wizard opens.
A new TestCase1 node is added under the project's Test node in the Projects window, containing two sub-nodes, Input and Output.
The Source Editor appears containing the Input file, Input.xml
Note - If the Source Editor does not contain a tab for Input.xml, double-click the Input node in the Projects window to open the file.
<syn:paramA>?string?<syn:paramA>
<syn:paramA>Hello World<syn:paramA>
Output.xml is opened in the Source Editor. Initially, Output.xml is empty until the first test run populates the file.
When the Overwrite Empty Output dialog box appears, click Yes to accept new output. The first test run populates the Output.xml file displayed in the Source Editor.
The test compares the output to the contents of the output file. Because the first run of the test has nothing to compare itself to, the first test fails. Subsequent test runs will compare their output with the contents of Output.xml and should succeed.
The test case is compared to the current output file and succeeds.
You just created the HelloWorld, synchronous sample project. This sample project is available in the NetBeans IDE's samples file under Project/Samples/SOA/Synchronous BPEL Process.
This tutorial above demonstrates how to:
Create a BPEL Module project
Use the BPEL Designer to create a BPEL process
Build and deploy a Composite Application project to GlassFish
Create and run test cases