...
4. The "Deployed Processes" page opens with the newly-added process listed. For example,
- 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:
- 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.
5. Click the "Process ID" to access its information dashboard. For example,
Once the process is deployed in the BPS, it will be exposed as a BPEL service. Click "Services -> List" menu under the "Main" menu.
...
| Info | ||
|---|---|---|
| ||
Instead of using the management console, you can deploy a BPEL process manually by copying the zipped file to the $CARBON_HOME/repository/deployment/server/bpel directory. For instructions on preparing the process zip file, refer to section Preparing for Process Deployment. |
Managing a BPEL Process Instance
| Excerpt | ||
|---|---|---|
| ||
Instructions to add a BPEL process in WSO2 BPS and manage it as a service. |