Publishing BP Server applications as Business Process Server Web Services
If you have installed Business Process Server on JBoss, you must perform the following additional steps before you publish a BP Server application as a Web service.
For JBoss Community Edition 5.1: Copy jboss-javaee.jar file from OEBPS_HOME\jboss\common\lib folder to OEBPS_HOME\webapps\deploy\sbm.war\WEB-INF\lib folder.
For JBoss Enterprise Application Platform 5.1.1: Copy jboss-javaee.jar file from JBOSS_SERVER_HOME\lib folder to OEBPS_HOME\webapps\deploy\sbm.war\WEB-INF\lib folder.
Restart Business Process Servers.
To publish a BP Server application as a Web service:
1. In the Administration module, go to Applications > BP Server.
Business Process Server displays the BP Server Applications page listing all current BP Server applications as shown in the following figure.
Figure 7. Installing a BP Server Application as a Web Service
2. Use the Filtering functions to select an option from the Application Status drop-down list.
3. Click Go to display only those applications in which you are interested.
The BP Server Applications page contains information on:
Status, indicating the current status of the application. Options include All, Installed, Uninstalled, Suspended, Resumed, Published, Unpublished or Deprecated.
Process Template Name, or the name assigned by the developer when defining the process template in Progress Developer Studio for OpenEdge.
Label, or the name users see in Business Process Portal. The developer defines this name as the Label when designing the process template in Progress Developer Studio for OpenEdge.
Rule, indicating whether the application contains rules (Yes) or has none (No). If BPM Events is not running, then Business Process Server allows you to install or uninstall applications without rules, but BPM Events must be running if you want to install/uninstall applications that contain rules.
Application Name, the name of the application. Business Process Server supports versioning for applications, where a new version can be installed on an existing application. In case of a versioned application, this displays the name of the application of which the current process template is a version.
Description, providing a brief description of the application. If required, you can define the description as a text link to a lengthier, more detailed description.
Migrate ACL, select this check box, if the permissions created for other versions of this application need to be migrated to the current version of the application.
4. You can publish an application (or BPM Workflow workstep) whose status is Installed. Select the check box associated with a BP Server application you wish to publish as a Web service, and click Publish.
Note: If permission is not granted to you or your group for publishing applications, then an error message displays when you click the Publish button.
The Publish Applications page is displayed.
5. Select Methods to be published, and where to Publish.
6. Optionally, enter Service description.
7. Click Publish.
You may also publish and unpublish applications in Progress Developer Studio for OpenEdge. Select Project > Publish from the Progress Developer Studio for OpenEdge menu bar and provide the user name and password. For more information, see the OpenEdge Getting Started: Developing BPM Applications with Developer Studio.
Note: When you publish an application as a Web services, its available tasks cannot be completed using a Web Services call.
Business Process Server publishes the selected BP Server application as Web services.
Status, indicating the current status of the application. Options include All, Installed, Uninstalled, Suspended, Resumed, Published, Unpublished or Deprecated.
