To add a customized adapter to a process template:
After creating and storing the Adapter (class file) in the appropriate directory, enter the fully qualified Java name in the Class box of the New Adapter dialog box (accessed through dragging the New Adapter icon from the Assign participants link in the Tasks Pane to the process template). In this example, we use a sample class file named MyBPM WorkflowAdapter.
For Adapters developed without a package description in the class file, enter the name of the class file in the Class box of the New Adapter dialog box.
For Adapters developed with a package description in the class file, enter in the Class box the name of the package (in this example, "packagename") and the class file name separated by a period (.).
If the Web application has been published, then save the class files in one of the following directories, where WebAppDir refers to the application server that you are using:
If the application has not been published already, then save the class files under the following:
OEBPS_HOME\BPM Workflow\common\classes. In this case, the adapter’s class files must be copied to the AppServer directory before the application is published.
OEBPS_HOME\BPM Workflow\<Application Name>\WEB-INF\lib. Here, the adapter’s class files are automatically copied to the AppServer directory when the application is published.
It is also correct to save the files to the following directory:
After creating and storing the Adapter (class file) in the appropriate directory, enter the fully qualified Java name in the Class box of the New Adapter dialog box (accessed through dragging the New Adapter icon from the Assign participants link in the Tasks Pane to the process template). In this example, we use a sample class file named MyBPM WorkflowAdapter.