Java step processor examples

The Content Platform Engine installation includes a sample Java™ step processor and launch processor. The processors must be configured to make them available to the workflow author.

You can use this JavaJava sample as-is or a developer can modify these sample step processors or create new ones. Your changes take effect immediately. Workflows that use the modified processors and that are in progress use the revised settings in the next applicable step. If you modify the step processors while Process Designer is running, the new information is not available until the next time you start Process Designer.

Java step processor example

To configure the Java step processor, use the following entries:

Type: Step

Name: JavaStepProc (FileNet) [or any name that you prefer]

Language: Java

Location: java/ootb/WcmStepProc.jsp

Width: 800

Height: 600

Class: filenet.vw.apps.steps.tabbed.VWTabbedStepApplication

Java launch processor example

To configure the Java launch processor, use the following entries:

Type: Launch

Name: JavaLaunchProc (FileNet) [or any name that you prefer]

Language: Java

Location: java/ootb/WcmLaunchSP.jsp

Width: 800

Height: 600

Class: filenet.vw.apps.launchers.tabbed.VWTabbedLaunchStepApplication

Step processor location example

The step processor location specifies the locations of the launch or step processor that is deployed for your web applications. Each location must be relative to the base directory for the web application as defined in the URL template.

The URL for a custom step processor that is deployed in the MyWebApp web application might look like this example, where:

Base server URL = example:8080/MyWebApp/
Base directory (URL Template) = stepprocessors/
Location = html/NewStepProcessor.jsp

   http://example:8080/MyWebApp/stepprocessors/html/NewStepProcessor.jsp