Try OpenEdge Now
skip to main content
Application Developer's Guide
Developing BPM Workflow adapters : Developing custom adapters

Developing custom adapters

Use one of the following approaches to develop custom Adapters:
*Define any function to perform the desired activity and extend the GenericAction class (also known as a "BPM Workflow-style" Adapter). For more information, see Sample adapter code for BPM Workflow-style adapters.
*Develop BP Server Adapters by implementing the setAllInputDataslots and getAllOutputDataslots methods to implement a specific interface. For more information, see Sample adapter code for BP Server-style adapters.
*Use Business Process Server’s Adapter and Configuration Mapping Framework to create a custom managed adapter. For more information, see the Managed Adapters Guide.
All Adapter styles are now supported in BPM Designer. You can implement Web Application (formerly BPM Workflow) support of BP Server-style Adapters only for BP Server Adapter version 11.6 and up.
To develop and create a BPM Workflow-style Adapter, extend the GenericAction class. The GenericAction class has an abstract method, commit(), that must be implemented. The commit method contains the logic that tells the Adapter what you want it to do. Web Applications in BPM Designer only support the commit method. The input data to the Adapter is specified during process design time and is automatically retrieved by the Adapter.
Also, invoke the getProp<datatype>(dsName) methods of the GenericAction to access the property values. The setProp<datatype>(dsName, dsvalue) methods of the GenericAction can be used to set property values. The supported datatypes are String, Long and Double of the Number type, Boolean, and Object, as well as Vector and BSObject.
Place BPM Workflow Adapters (Java class files) in the following directories.
*If the Web application has been published, then save the BPM Workflow Adapter class files in one of the following directories, where AppServer refers to the application server that you are using:
*App_Server\...sbm\BPM Workflow\common\classes.
*App_Server\...sbm\BPM Workflow\<Application_Name>\WEB-INF\classes.
*If the Web application has not been published already, then save the class files under the following:
*OEBPS_HOME\BPM Workflow\<Application_Name>\WEB-INF\classes
It is also correct to save the files to the following directory:
* Sample adapter code for BPM Workflow-style adapters
* Sample adapter code for BP Server-style adapters
* Adding custom adapters to the process template