Retrieving the Content event emitter module for configuration

After you deploy the Business Automation Insights and Content Platform Engine (CPE) containers on OpenShift or Kubernetes, retrieve the code module for the Content event emitter.

About this task

Retrieving the code module consists in copying it to a working directory to make it available to the Content event emitter.

For an on-premises (traditional) deployment, you can find these JAR files in the ContentBAI folder on the CPE installation media. See Preparing a traditional WebSphere Application Server deployment for Content event emitter installation.
For a containerized deployment, you need only the bai-content-emitter.jar file, which you can find in the ContentBAI\eventhandler folder of a running CPE pod. To retrieve a current version of the bai-content-emitter.jar file from a containerized deployment, make sure that the running CPE is the current version. This task is not needed if the Content operator initializes the object store.

Procedure

Create a working directory on the client that you intend to use to connect to the OpenShift or Kubernetes cluster.
```
mkdir /opt/downloads
cd /opt/downloads
```

Copy the code module from the CPE Docker image to your downloads directory.

POD=$(kubectl get pod | grep cpe-deploy- | awk '{print $1}')
kubectl cp $POD:lib/ContentBAI/eventhandler/bai-content-emitter.jar ./bai-content-emitter.jar

What to do next

You are ready to start configuring the Content event emitter.