This tutorial guides you on how to create a BPEL process and to assign a value in the request to the response using WSO2 Integration Studio. It walks you through the steps to demonstrate how you can assign the input string of the request message to the result string of the response message.
Tip | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
Before you begin, Install Oracle Java SE Development Kit (JDK) version 1.8.* and set the JAVA_HOME environment variable.
|
This tutorial includes the following sections:
...
Deploying the BPEL Workflow
After creating the deployable archive, follow the steps below to deploy the BPEL Workflow.
Start the Business Process profile of WSO2 EI.
Panel borderColor #542989 bgColor #ffffff borderWidth 1 Localtabgroup Localtab title On MacOS/Linux/CentOS Open a terminal and execute the following command:
Code Block wso2ei-6.4.0-business-process
Localtab title On Windows Go to Start Menu -> Programs -> WSO2 -> Enterprise Integrator 6.4.0 Business Process. This will open a terminal and start the business process profile.
- In a web browser, open the Management Console of the Business Process profile , and log in with the default credentials (username: admin and password: admin ).
Click Main → Manage → Processes → Add → BPEL , browse the ZIP file of the BPEL Workflow and click Upload .
Tip You can find sample BPEL package ZIP files in the
<EI/HOME>/samples/business-process/bpel
directory. Also, instead of using the Management Console, you can deploy a BPEL process manually by creating the<EI_HOME>/repository/deployment/server/bpel
directory, and copying the ZIP file to it. For instructions on preparing the process ZIP file, see /wiki/spaces/EI6xx/pages/49612261 .In the New BPEL Package window, browse and select the BPEL Package ZIP file and click Upload.
You view the deployed BPEL process listed under the Deployed Processes as shown below.
- Package Name: The name of the package containing at least the deployment descriptor and one or more process definitions (BPEL), WSDL and XSDs.
- 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.
- Manage: A newly-created process has status as “Active", which can be retired by clicking on the “Retire" link. Once a process is retired, a new instance of it cannot be created.
Tip If you do not view the new process, refresh the browser or click Main → Manage → Processes → List → BPEL .
Expand | ||
---|---|---|
| ||
There are two ways to undeploy a BPEL Workflow.
|
...