Configuring the Apache Pulsar transport

The Apache Pulsar allows the probe to integrate with an Apache Pulsar server to consume events.

Apache Pulsar transport properties table

The following table describes the properties used to configure the pulsarTransport.properties file.

Table 1. Apache Pulsar transport properties

Property name

Description

PulsarClientMode
Use this property to specify whether the Pulsar client is running in CONSUMER or PRODUCER mode.
Note: By default PulsarClientMode is commented out, so you must uncomment it to use it.

ConnectionPropertiesFile

Use this property to specify the JSON file holding the Apache Pulsar connection properties.

Apache Pulsar connection properties table

The following table describes the properties used to configure the pulsarConnectionProperties.json file.

Table 2. Pulsar connection properties

Property name

Description

pulsar_client

properties

Use this property to specify the path to a file holding Apache Pulsar client properties in key-value format, for example: key=value

The default is /opt/IBM/tivoli/netcool/omnibus/java/conf/pulsarClient.properties.

pulsar_consumer

properties

Use this property to specify the path to a file holding Apache Pulsar consumer properties in key-value format, for example: key=value

The default is /opt/IBM/tivoli/netcool/omnibus/java/conf/pulsarConsumer.properties.

pulsar_producer

properties

Use this property to specify the path to a file holding Apache Pulsar producer properties in key-value format, for example: key=value

The default is /opt/IBM/tivoli/netcool/omnibus/java/conf/pulsarProducer.properties.

Note: By default, the Probe for Message Bus and the Gateway for Message Bus both use the same pulsarConnectionProperties.json file. Typically you would use the pulsar_producer property with the Gateway for Message Bus, but not the probe.