Preparing your source FileNet Content Manager environment for the move

The traditional WebSphere® Application Server environment must be prepared to facilitate the move to the Cloud Pak container-based environment. In addition, the component containers need access to the existing directory server, database installation, and storage as well as new resources to support the content services containers.

Before you begin

Check the Detailed System Requirements External link opens a new window or tab IBM® Support technote for hardware and system requirements as well as the appropriate versions of supporting software.

For more information on the Cloud Pak environment, see Planning an enterprise installation.

About this task

This task is a part of the process to move an existing P8 domain to be managed by a container deployment of the Content Platform Engine and associated components. If your FileNet® P8 domain was already upgraded to a version that is supported for the move, certain preparation tasks that are described in this process are already accomplished and can be skipped as noted. Perform the remaining tasks that are relevant to the addition of containers to an existing FileNet P8 deployment.

Some tasks require input that results from other preparation tasks performed by other administrator roles. Plan to keep a record for use in other preparation and deployment activities.

FileNet® P8 requires a robust environment of integrated software, such as databases, Lightweight Directory Access Protocol (LDAP) servers, and components in the FileNet P8 family. This interdependence calls for preparation and collaboration with the administrators in your environment to configure the infrastructure and record the relevant details for the FileNet P8 installation and setup.

The steps you take to prepare can differ depending on your starting point and what components you want to include in your Cloud Pak environment.

Procedure

To prepare to introduce content services containers into an existing FileNet P8 system:

  1. Review the following security requirements for your systems:
    • Do not change realms (your authenticated users and groups), during a move or upgrade to containers.
    • Contact your IBM® FileNet® representative if you intend to change directory servers.
  2. (For upgrade moves) Prepare the database servers for the systems that are being upgraded to the Cloud Pak.

    Use the following information: Database administrator planning External link opens a new window or tab

  3. Ensure you have the JDBC driver files that are needed for the database version in an accessible location.
    If your FileNet P8 is already upgraded to the same release version as the targeted container deployment, you might want to copy the JDBC driver files from the system that performed the upgrade.
  4. As part of the plan to add containers to the existing FileNet P8 system or to upgrade a FileNet P8 system using containers, prepare the existing file servers for use with containers. For details, see Arranging your storage.
  5. (For upgrade moves) Use the following information to enable the asynchronous processing dispatcher to ensure that the object stores progress to a completed or ready state as part of an upgrade: Enabling the Asynchronous processing dispatcher External link opens a new window or tab.
    If your FileNet P8 domain is already upgraded to V5.5.1 or later, you can skip this step.
  6. (For upgrade moves) If the data will be upgraded by using the containers, provide the bootstrap information from the existing FileNet P8 Engine-ws.ear to the deployed containers.
    Important: If your FileNet P8 domain is already upgraded to V5.5.1 or later, you can skip this step.
    1. Locate and obtain a copy of the bootstrapped version of the EAR file .
      If you used the P8 Configuration Manager tool to bootstrap the EAR file, the path to the file is as follows:

      Content_Platform_Engine_installation_directory\ContentEngine\tools\configure\profiles\profile_name\ear\Engine-ws.ear

    2. Use an unzip or archive tool to extract the props.jar file from the APP-INF/lib location in the Engine-ws.ear file.
      The following example uses the unzip command to place the file into the /tmp directory of the machine where the command is run:
      unzip -j Engine-ws.ear APP-INF/lib/props.jar -d /tmp
    3. Place the extracted props.jar in a directory that you can access later and make a note of the location.
      You will move this file into a bootstrap persistent volume claim as part of the preparation of your new Cloud Pak environment.