Migrate component queues that were created with a legacy
Component Manager in a developer environment to the current version
of Component Manager.
The following procedure describes how to migrate component
queues in a developer environment by using Process Configuration Console.
This procedure must be completed before you start the procedure in
Migrating component queues
in a Test Environment
- Update any custom code as follows:
- Optional: Replace any references to the
Compatibility Layer for the 3.5.x Content Java™ API with references to the Content Engine Java API.
- Replace any references to local files on the Workplace or IBM®
FileNet® Workplace XT server. The
new Component Manager runs on Content Platform Engine and therefore does
not have access to files on the Workplace and IBM
FileNet Workplace XT servers.
- Reconfigure the queue adapter to use one of the following
component types:
The deprecated component types are not listed in the
table. These types are for queues that you do not want to migrate.
- Update the component queue definition in Process Configuration
Console as follows:
- Create a code module with the required JAR files. Do not include any of the JAR files that are provided with FileNet P8 as they are already
included in the Content Platform Engine EAR
file.
- If you are using a login context other than CELogin,
complete the following steps for each component adapter:
- Update other settings, such as the batch size and polling
rate, to ensure adequate throughput. For information, see Adapter properties
- Click Finish to save your changes.
- Save your changes. If the Enable
Queue Processing in Server adapter setting is selected,
these changes are active as soon as the Process Configuration Console
changes are committed.
- Test your updates to ensure that the component is functioning
correctly. When the new Component Manager starts, it automatically
processes any work items that were queued up for processing by the
legacy Component Manager.
- Create an export package for moving the updates to a test
environment. Include the following items in the package:
- The code module that includes the new JAR files from the development
object store.
- The region definition.
- To export the updated component queue definitions, in the Operations section,
click Import to import each operation that
you want to add to the queue.