Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Engine Reference  
  Search  |  Index  
Concepts
  About attachments
  About the Component Integrator
  About launching a workflow
  About milestones
  About operations
About the RMI registry
About rosters
About routing
About rules
  About security
  About security queues
  About step processors
  About step states
  About system maps
  About transfer
  About workflow fields
  About workflow maps
  About workflow participants
  Component queue security issues
  Content Engine (CE) operations
  Coordinate information
  Custom web applications
  Eliminating port 32771 conflicts
  Java Runtime Environment (JRE)
  Maximum index key size
  Naming conventions
  System fields
  Troubleshooting
  Wildcards
  Workflow database field size limitations
  Workflow exceptions
Events & Statistics
Expressions
Procedures
   

About configuring a web application or custom step processor

Use the following general procedure to configure a custom web application or custom step processor for the Process Engine.

Step 1: Install your application or custom step processors on the application server.

Step 2: Register custom web application, specifying the base server URL and the ID number of the application.

Using the Process Configuration Console, specify the base server URL in either a VWService to set it for the entire service, or set it for a specific isolated region. For instructions see Set web application properties for VWService or Set web application properties for an isolated region in the online Help for Process Configuration Console.

Step 3: Register custom step processors and launch processors, using the Process Configuration Console to specify the location and the URL template. For instructions see Configure step processors in the online Help for Process Configuration Console.

Step 4: To confirm that you have successfully configured a step processor, open Process Designer and add a step. With the step selected, display the list of available step processors in the Step Properties pane—your new step processor should be listed.

 

At runtime, the system uses the following process to determine the appropriate URL template:

  1. Retrieves the location and URL template from the current web application.
  2. If the location or URL template is not specified in the current web application, checks the default web application to retrieve the location, URL template, and web server base URL. The system checks for default web application using the following hierarchy:
    1. Check the default indicated by the user's preferences.
    2. Check the isolated region's default.
    3. Check the VWService's default.
  3. If the location, URL template, or web server base URL is not found anywhere in step 2 (i.e., using the default web application), repeat the process for the remaining web applications in the VWService.
  4. If the location, URL template, or web server base URL is still not found, use the default step processor for the current isolated region. For information on setting the default step processor for an isolated region see Configure step processors in online Help for Process Configuration Console