After deploying BPEL Workflows, you can use the Management Console of the Business Process profile to explore it. To do this, in the Management Console, click Main → Manage → Processes → List → BPEL and click the Process ID of the deployed process.
Also, once the process is deployed, it will be exposed as a BPEL service. In the Management Console, click Main → Manage → Services → List. You will view the service of the BPEL process listed under Deployed Services.
You view the below Information Dashboard.
This Information Dashboard contains the following sections:
You view the following information about the process under Process Details.
- Process ID: A unique ID to identify the deployed BPEL process.
- Version: If a package with an existing name is uploaded, the processes in the package will be versioned. All old processes in the package will be retired and new version deployed. Since there is only package-level versioning available, the new package should include all the processes defined in the old package, even though you may only need to update a single process in that package.
- Status: Status of the process. Can be either "Active" or "Retired".
- Deployed Date: Date and time of the package deployment.
- Package Name: The name of the package containing at least the deployment descriptor and one or more process definitions (BPEL), WSDL and XSDs.
- Deployment Information: You view the following information about the deployment in the Deployment Descriptor.
When a process is triggered by a user through the TryIt tool for example, an instance of that process is created in EI Business Process. Each process can have numerous instances. They are summarized graphically with statuses in summary as follows.
Partner links are created for other partner processes that are called by the BPEL process you deploy. For more information on partner links, see BPEL 2.0 Specification.
The "Try this service" link directs you to a new window where the operations available the BPEL service is displayed. Using this window, you can check whether the service provides the desired output. The URL for invoking the TryIt tool can also be appended by concatenating the endpoint URL of your service with the following string:
- ?tryit : Ajax client for simple, generic interactions with the service.
The TryIt link will be enabled in your service dashboard only if "org.wso2.carbon.tryit" feature of the WSO2 feature repository is installed in your Carbon instance. For instructions on triggering the TryIt tool, see Try It .
WSDL 1.1 and WSDL 2.0
Click on the links to the WSDL 1.1 and the WSDL 2.0 to open the page with XML configuration. The URLs for the WSDL files of the service can also be appended by concatenating the endpoint URL of the service with the following strings:
- ?wsdl2 : WSDL 2.0 description of the service
- ?wsdl : WSDL 1.1 description of the service
The WSDLs describe the operations the service exposes, the structure of the XML that is sent and received by each operation, and how to communicate with the service to retrieve the XML content. By default, six different types of endpoints are deployed. Each of these endpoint types are represented by the WSDL 2.0 <endpoint> elements of the service, and by the <binding> elements which these endpoints refer to. The default six types of endpoints are as follows:
- SOAP 1.2 over HTTP
- SOAP 1.1 over HTTP
- Plain old XML/REST over HTTP
- SOAP 1.2 over HTTPS
- SOAP 1.1 over HTTPS
- Plain old XML/REST over HTTPS
The BPEL code for the process. For example,
The graphical workflow of the process. For example,
Now that you understand how to create, deploy and explore BPEL artifacts, next take a look at: