Deploying containers

The process to move or upgrade your existing traditional WebSphere Application Server P8 domain to change to an environment that is fully deployed on containers is similar to a new installation on containers, except that you use your existing configuration of supporting software like databases and directory servers. The move or upgrade to the newer version is accomplished by the deployment and startup of the component containers.

About this task

An upgrade deployment means to move to containers and upgrade the level of software currently in use in your traditional WebSphere deployment environment. An upgrade deployment starts from a V5.2.x or V5.5.x installation, and upgrades to V5.5.x as part of the conversion.

A move deployment means to move to containers without changing the level of software currently in use. A move deployment starts from a traditional V5.5.x or later installation.

Before you start the move or upgrade, read through the information on preparing your environment, make sure you have performed all of the required preparation steps, and review the steps for a new container deployment. The move process includes a full backup of your source system.

If your source IBM Content Navigator is configured for SSO, choose the SSO container image for Navigator.

Procedure

To move your installation to containers:

  1. Follow the steps in Validating the YAML in your custom resource file, providing the values for your environment.
    Important: Do not include the initialization and verification sections in your custom resource. These capabilities do not apply in a move to containers.
  2. Follow the steps in Stop the IBM Content Search Services index dispatcher.
  3. Stop all instances of the IBM Content Search Services servers that are part of this FileNet P8 domain.
    As the root user, navigate to /opt/IBM/ContentSearchServices/CSS_Server/bin, and enter the following command:
    ./shutdown.sh
  4. Stop and back up the Content Platform Engine components and databases.
    After the database backups complete, ensure that the databases are running.
  5. (For upgrade moves) Verify that the props.jar file, extracted from the traditional WebSphere Application Server deployed Engine-ws.ear as described in section "Prepare your source FileNet Content Manager environment for the move," was placed it into the directory that you created for the Content Platform Engine FileNet (for upgrade) bootstrap persistent volume claim you will use for the Content Platform Engine container deployment.
    To do this before the cpe container is deployed, the bootstrap persistent volume claim must be statically provisioned instead of waiting for the persistent volume claim to be dynamically provisioned storage on demand by the operator.
    Important: If your FileNet P8 domain is already upgraded to V5.5.1 or later, you can skip this step.
  6. If you are moving IBM Content Navigator, copy the Navigator master encryption key, backed-up as described in section "Prepare your source FileNet Content Manager environment for the move," to the persistent volume claim created for the IBM Business Automation Navigator Liberty configuration data.
    To do this before the Navigator container is deployed, the Navigator Liberty configuration data persistent volume claim must be statically provisioned instead of waiting for the persistent volume claim to be dynamically provisioned storage on demand by the operator.
  7. Use the instructions in Deploying the custom resource to apply your custom resource file by using the operator.
    Follow the included steps to verify your deployment after the process completes.

What to do next

To perform post deployment tasks, see topic Completing post deployment tasks.