Deploying the Case event emitter application

Edit online
Draft comment:
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15
After the Case event emitter application is configured and repackaged, you deploy it manually to your WebSphere® Application Server instance for IBM® Case Manager.

About this task

You can deploy for the first time to a stand-alone WebSphere Application Server instance, or upgrade an existing instance, or you can deploy to a clustered WebSphere Application Server environment.

If the deployment returns class loading issues, see Resolving JAR file and class loading errors.

Deploying to a WebSphere Application Server stand-alone instance for the first time

Edit online

Procedure

  1. Open the WebSphere Application Server administration console.
  2. Browse to Applications > Application Types > Websphere enterprise applications and click Install.
  3. Select Local file system, and then browse and select the CaseEventEmitter.war file that you have created.
  4. Click Next until you complete the installation, keeping the default values at each step.
  5. Save to the master configuration and start the application.

Updating a WebSphere Application Server stand-alone instance

Edit online

About this task

To update an existing application, you can uninstall it and follow the procedure for "Deploying to a WebSphere Application Server stand-alone instance for the first time" again, or you can go through the following update steps.

Procedure

  1. Browse to Applications > Application Types > Websphere enterprise applications and stop the existing CaseEventEmitter application.
  2. Select the CaseEventEmitter application and click Update.
  3. Select Replace the entire application > Local file system, and browse to the new WAR file.
  4. Click Next until you complete the installation, keeping the default values at each step.

Deploying to a WebSphere Application Server cluster for the first time

Edit online

Procedure

  1. Open the WebSphere Application Server administration console.
  2. Browse to Applications > Application Types > Websphere enterprise applications and click Install.
  3. Select Local file system, and then browse to the CaseEventEmitter.war file that you have created.
  4. On the Map modules to servers page, select the cluster to which you want to deploy this event emitter.
  5. Click Next until you complete the installation, keeping the default values at each step.
  6. Save to the master configuration and start the application.

Updating a WebSphere Application Server cluster

Edit online

About this task

To update an existing application, you can uninstall it and follow the procedure for initial cluster deployment again, or you can go through the following update steps.

Procedure

  1. Browse to Applications > Application Types > Websphere enterprise applications and stop the existing CaseEventEmitter application.
  2. Select the CaseEventEmitter application and click Update.
  3. Select Replace the entire application > Local file system, and browse to the new WAR file.
  4. On the Map modules to servers page, select the cluster to which you want to deploy this event emitter.
  5. Click Next until you complete the installation, keeping the default values at each step.

Checking deployment

Edit online

Procedure

  1. Open the deployed application from the https://host:port/caseeventemitter/ URL.

    The host placeholder is the host name of the WebSphere Application Server instance where the Case event emitter application is deployed and port is the port for the default host. If you use an HTTPS URL, the port number is the secure port number of the default host.

    HTTPS example: https://localhost:9443/caseeventemitter
  2. Check the logs.

    Remember to set logging and tracing as documented in Enabling detailed tracing on the Case event emitter.

  3. If the Case events are emitted to local Kafka, you can use the local Kafka consumer to read the events from the topic.

    For more information about Kafka configurations, see Configuring event output to Kafka.

    For example, navigate to the local Kafka installation and run the following command.
    bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic ibm-bai-ingress --from-beginning --property print.key=true --property print.value=true --property key.deserializer=org.apache.kafka.common.serialization.StringDeserializer --property value.deserializer=org.apache.kafka.common.serialization.StringDeserializer

    This command prints the key-value pair for all the Kafka messages in the ingress Kafka topic.

  4. Monitor events in the dashboards.

    For more information, see Visualizing data External link opens a new window or tab.