Configuring the Content event emitter for the first time

Configure the Content event emitter through the Administration Console for Content Platform Engine to set up your events, actions, and document processes.

Before you begin

Determine your access to the Administration Console for Content Platform Engine:
Container deployments

The content-fncm-access-info ConfigMap contains the routes that enable you to access various platform components. The ConfigMap name is prefixed with the deployment name and type (by default in FileNet® P8 containers content-fncm and in ICP4BA content-cp4ba).

  1. In the OpenShift Console, go to Workloads > ConfigMaps.
  2. Search for the string content-fncm-access-info or content-cp4ba-access-info. You can also retrieve the information for the acce route by running the following command.
    kubectl get cm content-fncm-access-info -n <namespace> | grep acce
    For example, content_platform_engine_server:port/acce, where,
    content_platform_engine_server
    The name of the server where Content Platform Engine is deployed.
    port
    The HTTPS port that is used by the web application on the server where Content Platform Engine is deployed. In a highly available environment, use the load-balanced virtual name for the content_platform_engine_server:port (for example, you can use https://virtual_server/acce).

About this task

Create an event action and subscription with the bai-content-emitter.jar file as the code module.

Procedure

  1. Log in to the Administration Console for Content Platform Engine.
  2. Go to Object Stores > object store name > Events, Actions, Processes.
    The object store name placeholder represents the name of the object store where you want to create the event action and subscription, for example, TARGET or DESIGN.
  3. Right-click Event Actions and select New Event Action:
    1. Enter a name for the event action, for example MyBAIEventAction, and then click Next.
    2. At the Event Action Type Selection section, proceed as follows.
      1. Check Status: Enabled.
      2. Select Event Action: Event Action.
      3. Click Next.
    3. At the Specify the Type of Event Action section, proceed as follows.
      1. Select Type: Class.
      2. At Java class handler:, enter com.ibm.bai.content.event.emitter.eventhandler.ContentEmitterHandler
      3. Check Configure code module.
      4. Click Next.
    4. At the Specify the Code Module section, proceed as follows.
      1. Enter the Code module title, for example: EmitterCodeModule
      2. At Content elements:, click Browser to select the bai-content-emitter.jar file that you retrieved in the previous steps and set the Type: to application/java-archive.
      3. Click Next, then click Finish.
  4. To create an event subscription, right-click Subscriptions and select New Subscription.
    1. Enter a Display name, for example BAISubscription, and then click Next.
    2. At the Select Classes section, set Class type and Class to Document, and then click Next.
    3. At the Specify the Subscription Behavior section, keep the default settings and click Next.
    4. At the Select the Triggers section, select Creation Event, Update Event, and Deletion Event. Then click Next.
      1. You can also select Get Content Event. Selecting this event results in a large increase in emitted events.
      2. Events other than Creation Event, Update Event, Deletion Event, and Get Content Event are not supported.
    5. At the Event action section, for Select an event action, select the event action for BAI that you created in the previous step, for example MyBAIEventAction. Click Next.
    6. At the Specify Additional Options section, make the following selections.
      1. For Initial state:, select Enable the Subscription.
      2. For Subclass option:, select Include subclasses if you want to emit subclasses.
      3. Do not select Run synchronously.
    7. Click Next, then click Finish to create a new subscription.