A change preprocessor action contains the code that performs
the change preprocessing. You can use either Java™ or JavaScript to
implement the action. If you use JavaScript,
the code is stored in the change preprocessor action ScriptText property.
If you use Java, the code is
stored outside the action object, either as a code module or as a
class or JAR file.
When you work with change preprocessor actions, note the
following characteristics:
- Change preprocessor actions are independently persistable, so
that they can be created separately from other objects and then assigned
to one or more change preprocessor definitions.
- A Java-implemented change preprocessor can be placed in a code
module. It can coexist with other action handler types, such as an
event action, lifecycle action, or document classifier.
- If your Java-based action is not included in a code module, the
class or JAR file must be located on the local Content Platform Engine application server.
In addition, it must be included in the application server class path.
- A change preprocessor action can be enabled or disabled. If you
disable an action, all classes in the system with change preprocessor
definitions that reference the disabled action are affected. Therefore,
if you want to disable change preprocessing for a class, disable the
change preprocessor definition. If you want to disable a particular
action everywhere in the system, disable the change preprocessor action.
- You can find sample code for a change preprocessor handler in
the following location:
- Windows: C:\Programm
Files\FileNet\Content Engine\samples
- UNIX: /opt/IBM/FileNet/ContentEngine/samples
When working with change preprocessor actions, administrators
are typically required to perform the following tasks: