Migrate Content Engine operations and Component Integrator components
Component Integrator components can be implemented as Java™ Message Service (JMS) components or as Java
JAR files. If they have been implemented as JMS components, ensure that the required
JMS queues are configured in the destination environment. If the components are implemented
as Java JAR files, or if you have customized the Content Engine
operations, use the following steps to deploy the JAR files in the destination
environment:
- Copy the JAR files that implement the operations from the source Application Engine
to the destination Application Engine.
The sample Content Engine operations JAR file provided with FileNet P8 is called
p8ciops.jar and is located in the ..\FileNet\Workplace\WEB-INF\lib directory. You can
update this JAR file with your changes, or create new JAR files.
If you create a
new JAR file, make sure you add it to the classpath on the destination Application Engine.
- Register the JAR file on the destination Application Engine as follows:
- Start Process Task Manager.
- Make sure that the Component Manager is stopped.
- Click Component Manager.
- Click the new library button.
- Click the Required Libraries tab.
- Click Add.
- Browse to your JAR file.
- Click Open.
- Click Apply to save your changes.
- Start the Component Manager.
- From the destination Application Engine, use Workplace to access the
Process Configuration Console and configure the component queues. Define the necessary operations.
This step must be performed from the server on which the JAR file that implements
the Content Engine operation or the Component Integrator component resides.
For more information, see Create a component queue.
For additional information on building and deploying Content Engine operations
and Component Integrator components, see Developing Component Integrator-Based Work Performers.