Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Configuration Console
  Search  |  Index
Process Reference  
Process Configuration Console
Getting started
Isolated regions
  Initialize an isolated region
  Connect to an isolated region
  Disconnect from an isolated region
  Export to
IBM CrossWorlds®
  Copy an isolated region
  Remove an isolated region
  Modify isolated region properties
     Configure event logging options
     Enable or disable statistics collection
     Set performance parameters
     Set web application properties
     Configure step processors
     Specify step processor locations
Queues
Rosters
VWServices
Process Engines
Workflow database
Events and statistics
   

Configure custom step or launch processors

Use the Step Processor Info tab in Process Configuration Console to make custom step or launch processors available for use in workflow definitions. Once configured, the custom processors display in the list of available step processors or launch processors in Process Designer, and can be assigned to steps or launch steps.

FileNet P8 Platform only: Also on the Step Processor Info tab, you can configure the FileNet-provided sample Java step processor and Java launch processor to make them available in Process Designer. See Configure sample Java... below for details.

To configure a custom processor

  1. Select the icon of the isolated region you wish to modify and click Properties on the toolbar.
  2. Select the Step Processor Info tab.
  3. To add a new step processor, click Add . Enter the following parameters and descriptions as appropriate for your processor.

    Column Parameter Description

    Type

    Specify the entry as a step processor or launch processor. In addition, you can specify one of each type as the default processor for the step or launch step. The Process Designer automatically selects the appropriate default step processor when a new step is created. In addition, the Process Engine uses the default step or launch processor at runtime if the processor defined in the workflow no longer exists.

    Name

    Enter a name that identifies the step processor or launch processor in the list of available step or launch processors in the Process Designer application. We suggest that you use a name that describes both the function and language (HTML or Java) of the processor. Each step and launch processor within the isolated region must have a unique name.

    Language

    Specify the language used by the developer to create the processor.

    Location

    Specify the location on the Application Engine or web server where the processor web page(s) reside. Double-click in the Location field to open the Step Processor Info Location dialog box.

    Height

    An integer value that specifies the height, in pixels, of the processor display window. You can experiment with this to find the optimal setting for your processor.

    Width

    An integer value that specifies the width, in pixels, of the processor display window. You can to experiment with this to find the optimal setting for your processor.

    Class name

    The package name of the Java application associated with a Java-based processor. This value does not apply to HTML-based processors.

  4. To delete a processor, select the row of the processor you want to delete, then click Delete .
  5. Click OK.
  6. Click Commit on the toolbar to apply this change to your isolated region. You can commit the changes immediately, or you can wait until you have finished all your changes. See NOTE in the sidebar.

Configure sample Java step processor and launch processor (FileNet P8 Platform)

To make the FileNet-provided Java step processor or launch processor available in Process Designer, follow the procedure above and enter the following details:

  • Type: Step
  • Name: JavaStepProc (FileNet)    [or any name you like]
  • Language: Java
  • Location: java/ootb/WcmStepProc.jsp
  • Width: 800
  • Height: 600
  • Class: filenet.vw.apps.steps.tabbed.VWTabbedStepApplication

 

  • Type: Launch
  • Name: JavaLaunchProc (FileNet)   [or any name you like]
  • Language: Java
  • Location: java/ootb/WcmLaunchSP.jsp
  • Width: 800
  • Height: 600
  • Class: filenet.vw.apps.launchers.tabbed.VWTabbedLaunchStepApplication

NOTE For systems in which Process Designer is accessed from FileNet Open Client or FileNet Web Services, manual configuration of the Java launch processor and step processor is not necessary. (These processors are selectable in Process Designer by default.) The underlying files are in the following locations:

Java step processor  

   FileNet Web Services Client

   FileNet Open Client

 

tabbed/step_main.asp

java/ootb/FnSPAppletPage.aspx

Java launch processor  

   FileNet Web Services Client

   FileNet Open Client

tabbed/launcher_main.asp

java/ootb/FnLSPSppletPage.aspx

   

NOTE Modifications to processor entries take effect as soon as you commit the changes. Workflows already in progress that use the modified processors will use the revised settings for the next applicable step.

If you modify the Step Processor Info while Process Designer is running, the new information is not available until the next time you start Process Designer.