Configuring the Centera fixed content device

Before you can create a Content Platform Engine object to represent an EMC Centera fixed content device, you must configure the device, and the device must be accessible to the Content Platform Engine network. You also use this procedure if you want to configure an Elastic Cloud Storage device as a fixed content device.

To create a connection from IBM® FileNet® P8 to the EMC Centera fixed content device:

1. Configure the EMC Centera system.
   Refer to the EMC Centera documentation for instructions on how to configure the EMC Centera device for use with FileNet P8 .
2. Create the PEA file on the EMC Centera system. Refer to the EMC Centera documentation for instructions on how to create a PEA file.
3. Copy the PEA file to a location accessible to the Content Platform Engine deployment. Make a note of the full path to the PEA file and its file name. The location of the file depends on the type of deployment:
   1. WebSphere and WebLogic:
      Copy the file to the same directory on each node that is containing a deployment of the FIleNetEngine application. Or create a network shared location accessible to all deployments. Ensure that the file permissions allow access to the file by the FileNetEngine application.

      For example, on Windows, the PEA file might be located with WebSphere: C:\IBM\cpe\ecs.pea

   2. Containerized deployment:
      • Create a configmap to provide the PEA file to the operator.

        The contents of the configmap are the contents of the PEA file. Name the file name configmap same as you create the configmap. Sample command to create a configmap from a PEA file: kubectl create configmap cpe-fcd-ecs --from-file=ecs.pea=<file> -n <namespace>

      • Use the CR parameter for cpe_production_setting.custom_configmap to provide the operator with the configmap to include in the deployment.

        The sub-parameter name must be meaningful to you. For example, from the sample command, cpe-fcd-ecs

        By default the file is mounted to the Liberty configuration (cpe-cfgstore) mapped location /opt/ibm/wlp/usr/servers/default/configDropins/overrides.

        Sample syntax in the CR YAML

        ecm_configuration:
           cpe:
             cpe_production_setting:
               custom_configmap:
               - name: cpe-fcd-ecs

4. Establish the pool address to use with the Content Platform Engine as the connection string for EMC. The connection string value or pool address can include multiple Centera addresses and failover information.
   1. Log in to ACCE with a user having GCD administrator privileges.
   2. Go to the Domain page: Global Configuration > Administration > Fixed Content Devices
   3. Create a new Fixed Content Device of type EMC Centera and complete the wizard or select an existing Fixed Content Device of type EMC Centera to modify.
   4. On the Configuration Parameters page, in the Pool address field enter the full path and name of the PEA file as part of the ECS Connection String value. For example, for
      WebSphere: cas.ecs.com?C:\IBM\cpe\ecs.pea

      Containerized: cas.ecs.com?/opt/ibm/wlp/usr/servers/default/configDropins/overrides/ecs.pea

5. Click Finish to complete the FCD creation wizard or click Save to commit changes to an existing FCD.
6. Wait for the new configuration to be applied to the FileNetEngine application deployment.
   1. With a WebSphere or WebLogic deployment, the new configuration is seen after a few minutes with no restart of the FileNetEngine application needed.
   2. With a containerized deployment, submit the CR file with the additional cpe_production_setting.custom_configmap parameter settings and wait for the Operator reconcile to create or update the deployment of the Content Platform Engine.