You can deploy custom workflow launch and step processors
that were created by using the IBM® Content Navigator toolkit. Depending on
your application server, some details can vary.
When you use the
IBM Content Navigator toolkit
to create a custom step processor, the three files that are displayed
in the table implement the custom launch or step processor:
Name format |
Description |
customStepProcessor.jsp |
The step processor controller registered in
the workflow system to identify it as a launch or step processor to
use in workflows. |
customStepProcessorLayout.html |
Provides the HTML template for the step processor
widget. |
customStepProcessorLayout.js |
If needed, extends the Content Navigator Process
Widgets package with more code as needed by the custom step processor. |
The files must be deployed with the IBM Content Navigator application and IBM Content Navigator must be restarted. The
custom step processor must also be registered into the isolated region
that hosts the deployed application.
An example that directly copies files into the IBM Content Navigator deployed location on
the application server:
- Under the WebContent directory (typically navigator.ear\navigator.war)
in the IBM Content Navigator deployed
location on the application server, create the subdirectories by using
names that are appropriate to your application and environment. For
example, create the following subdirectories: deployment_directory\navigator.war\customStepProcessors, deployment_directory\navigator.war\customStepProcessors\templates.
- Copy the three files to these locations:
Name format |
Location |
customStepProcessor.jsp |
\navigator.war |
customStepProcessorLayout.html |
\navigator.war\customStepProcessors\templates |
customStepProcessorLayout.js |
\navigator.war\customStepProcessors |
To register the custom launch processor or step processor
in the isolated region:
- Log on to the administration console by using a Content Platform Engine account with administrative
privileges for the workflow system or legacy workflow system that
the application is being migrated into.
- To register the custom step processors, open the object
store or legacy workflow system that the application is being migrated
into.
- Navigate to and select the isolated region of interest.
- Use the Step Processors tab to register
the launch processor or step processor. In the workflow
system configuration, the step processor definitions are kept with
the isolated region properties. If you use FileNet® Deployment Manager to migrate and deploy
the workflow system configuration from the source environment to the
destination environment, include the isolated region properties in
the export manifest that you used to create the deployment data set.
If you use the isolated region properties in the export manifest,
you do not have to use the administration console to manually register
the step processors.