Implementation Concepts

You can extend Content Engine functionality with your own server components by implementing the following Java™ interfaces in the com.filenet.api.engine package:

An event action handler can be configured to run synchronously or asynchronously. A lifecycle action handler always runs synchronously, and a document classifier always runs asynchronously.

This topic provides restrictions and best practices for implementing an event action handler, lifecycle action handler, and document classifier. As a group, all implementation types are generically referred to as "action handlers."

For additional information about these interfaces, see EventActionHandler, DocumentLifecycleActionHandler, and DocumentClassifier in the Javadoc™ documentation. To view sample source code implementations of these interfaces, go to this Content Engine directory: <drive>:/Program Files/Filenet/Content Engine/samples.

Restrictions

Best Practices