IBM Business Process Manager (formerly WebSphere BPM)
The IBM Business Process Manager plug-in includes steps that take the following actions on Business Process Manager cells:
- Deploy process application snapshots to an online (connected) Process Server.
- Deploy process application snapshots to an offline (disconnected) Process Server.
- Import and Export process applications to and from a Process Center.
Process service modules that are EAR files can also be deployed to a Process Server by using the WebSphere Application Server – Deployment plug-in for IBM UrbanCode Deploy.
This plug-in provides the following steps that automate deployment of process applications:
- Deploy process application snapshot.
- Generate offline package.
- Deploy offline package.
- Export a process application from a Process Center and import it into another Process Center.
The following steps are an overview of the typical process to follow:
- Create resources. For the deployment of process application snapshots to an online or offline process server, you must populate resources manually. You can view the resources that you create in the Resources view. Each resource corresponds either to the Process Center or to an offline Process Server.
- Define properties for the resources that you created manually.
- Define components, applications, and environments to automate deployment.
This plug-in requires version 6.0.1 of IBM UrbanCode Deploy.
The IBM UrbanCode Deploy plug-in for WebSphere Business Process Manager supports Business Process Manager versions 8.5 and later. Standard and Advanced editions are supported.
The steps in this plug-in run on any agents that the IBM UrbanCode Deploy server supports.
No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy.
Fixes APAR PH08137: Exception WASX8009E Invalid Parameter with BPM Deploy Process Application Snapshot step with spaces in Process Server Name
Warn the user when either conflicting credential properties or no credential properties are set. General refactoring.
- Updated all descriptions to specify whether the step connects to a Process Server or Process Center server.
- All step descriptions have the BPM command they are utilizing. If you are having trouble, we recommend referencing the WebSphere BPM documentation for CLI specific help. Many questions can be answered by following WebSphere BPM’s official CLI documentation.
- Most steps will connect to and run against the Process Center server. However, we recommend that there is at least one agent is installed on every Process Server and Process Center server. By running against the agent located on the correct server, this will eliminate the need to specify each step’s Host property. This is achievable through proper UrbanCode Deploy environment and resource management.
- The Update Installation Information step’s Process application track property is now optional for Process Center servers. It is still required for Process Servers.
All step descriptions now include their wsadmin scriptings commands.
Fixes APAR PI78360 – Updated acronym parsing and identification.
Support encrypted properties.
Added timeout to Generate Offline Package to prevent BPM command line race conditions.
The Track, Container, and Snapshot acronym finder will return the entered value if not found.
Version 6 adds a verbose mode to display additional troubleshooting output.
Updated finder for identifying the track, snapshot, or container acronym from its full name.
Version 5 adds functionality for the following BPM functions:
Minor fixes to “Deploy Offline Package” and “Deploy Process Application Snapshot” steps.
Version 4 adds functionality to pass the host name to the wsadmin script for all process steps.