Try OpenEdge Now
skip to main content
BP Server Developer's Guide
Business Process Server in OpenEdge : BP Server features
 

BP Server features

BP Server continues to support the following features:
*Managed adapters
*Provides frequently used adapters as out-of-the-box managed adapters.
*Provides the Adapter Configuration and Mapping Framework. For more information, refer to the Managed Adapters Guide.
*Process template versioning
*Allows installation of a new version of an installed application.
*Allows different versions of an application to be simultaneously installed, where at any time, a single version remains in the Installed state and all the others in the Deprecated state.
*Facilitates the dynamic creation of versions without stopping BP Server. For more information, refer to Processtemplate versioning.
*Four-eye principle for performers
*Allows different performers to be assigned to successive critical worksteps involving business decisions.
*Facilitates excluding performers of one or more worksteps, for another human workstep. For more information, refer to Excludingperformers for worksteps.
*Query service
*Helps faster retrieval of the workflow information.
*Reduces the network traffic and the load of the BP Server. Refer to Query service.
*Dynamic work item management using queues
*Maintains the list of queues and its dynamic groups in a database. Provides for each queue to contain multiple dynamic groups and users.
*Allows making work items available to other performers, if not completed by the specified due date. For more information, refer to Dynamic work item management using queues.
*Proxy user support
*Allows delegation of all or some of the applications to one or more users or groups.
*Provides preferred delegation setting that only needs to be applied as required.
*Java expressions in conditions and preconditions
*Enhances the usability and power of the business processes.
*Provides easier handling of BP Server dataslots (such as DECIMAL and DATETIMETZ) in decision conditions or preconditions.
*Time-bound activation
*Allows a user to specify the time when a workstep can be activated, using the "Activate on" field in the workstep properties.
*Provides the additional property "Activate after" to allow a user to specify the time after which the workstep can be activated.
*Callback adapter
*Sends alerts when the Business Process Servers change state.
*Facilitates quick action by the administrator for server problems. For more information, refer to the Application Developer’s Guide.
*Completed work item performer tracking
*Records the actual performer of a completed work item in the database.
*Provides the actual performer facilitating other dependant actions.
*Dynamic adapter loading
*Facilitates modification of the Business Process Server adapter/external performer during runtime, so that these changes are reflected immediately without server restart.
*Extend due date function
*Allows the user to specify a duration by which the due date of a workstep can be extended when it becomes overdue.
*Workstep process timer
*Provides for the workstep properties to include timer information.
*Executes the specified action after timeout. Refer to the section Setting Workstep Properties in the OpenEdge Getting Started: Developing BPM Applications with Developer Studio for more information.
*Global dataslots
*Defined at the process template level and available for use with all the instances. They are shared and any update to the value is available to all the instances in real-time.
*These dataslots are used as the workstep input and output dataslots for Activity, Adapters, and Subprocess worksteps.
*LIST dataslots
*Allows you to define a list of choices for a dataslot in the Progress Developer Studio for OpenEdge. Multiple choices can be selected from the list.
*The list contains a collection of non-unique restricted elements. For more information, refer to LIST dataslots.
*EJB method for atomic workstep
*Performer decided at runtime.
*Method plugged-in to obtain the performer(s). Refer to the EJBperformer in atomic workstep for more information.
*JMS based event publisher
*BP Server events published to the external applications.
*Default and user-defined Sender Implementation. Refer to the chapter JMS basedevent publisher for more information.
*Check for BP Server
*When BP Server is not running and the JMS message for the external workstep is received, the message is resent on the Queue three times, with a default waiting period of 15 seconds between each resend.
*Immediately before and after the adapter execution, checks if BP Server is running. Adapter execution is halted if the server is not running.
*Persistent JMS server ensures message delivery, hence restart external services is not called if either of external/Web services have persistent delivery mode.
*Read-only APIs
*Some APIs are read-only for performance improvements.
*Object-oriented API
*Support for the object-oriented APIs without using stateful session beans. For more information, see Using BP Server APIs for process template management.
*Use of the smart value objects to implement object-oriented APIs using stateless session beans. For more information, see Using BP Server APIs for process template management.
*The smart value objects improve the performance and allow transparent communication with the BP Server components.
*Changes to the data structure without affecting the client code, which is possible by using the generic attribute access pattern for the smart value objects and the API return data.
*Support for collection operation on the ProcessTemplate, ProcessInstance, WorkstepInstance, WorkItems, and Dataslots (Aggregate Value Object Pattern).
*Support for sorting on the collection data.
*Use of the session object to avoid duplicate authentication.
*Proxy workitem API
*Gets the work item list for a performer, including the work items which are assigned to the performer as proxy.
*BP Server admin utility
*Command-line utility.