This section describes how you can develop and deploy a Post Processor Plugin. It uses a predefined project and shows how to
A project has been prepared, which served as the basis to build this sample. The project already contains the code implementing the plugin and the required packaging information. To import the prepared project interchange file, perform the following steps:
You may notice that there are several problems indicated. We will fix those in the following steps.
You can use a Java project for implementing the plugin. Also, you can use any desired Java package structure. In the provided sample, all classes are defined under the same package 'sample'.
You need to provide a class implementing the pre-defined com.ibm.task.spi.StaffQueryResultPostProcessorPlugin interface. In order to have
the class definition available in the project Java build path, you need to include the file <wps-root>/ProcessChoreographer/client/taskapi.jar,
where
The sample plugin contains code accessing the Human Task Manager EJB API methods. In order to make stub and other required API classes available, you need to include the files taskapi.jar and task137650.jar in the project Java build path. In case your plugin needs access to the Business Flow Manager EJB API methods, the files bpeapi.jar, bpe137650.jar have to be included (located in the same directory). In order to make required J2EE defined classes available, you need to include a J2EE jar. In the provided sample, the file <wps-root>/plugins/javax.j2ee.ejb.jar is included in the build path.
For packaging, a logical name of the plugin has to be defined. Using this name, a configuration file has to be provided in the META-INF/services directory of the project. In this file, in the first non-comment line, the name of the class implementing the StaffQueryResultPostProcessorPlugin interface is expected.
In the provided sample, the following applies:
The project has to be exported as a jar file containing the Java classes and the configuration file.
In order to be available for Human Task Manager, the jar file should be placed in the <wps-root>/lib or <wps-root>/lib/ext directory.
For registering, the standard WebSphere Application Server defined approach applies:
For a WPS installation, only one Post Processor Plugin can be made available. Moreover, the shared library representing the plugin has to be linked with the TaskContainer application. Again, the standard WebSphere Application Server defined approach applies:
The following steps need to be applied:
Note that the setting Staff.PostProcessorPlugin.EnablineResultSharing has to be associated with the default value 'false', as the sharing mode cannot be applied to the sample plugin.