PubSub Configuration Interface
Overview
A PubSub Configuration interface type defines the Fabric connection to message provider (such as Apache Kafka or JMS) using the PubSub abstraction layer. The configuration is performed via the [default_pubsub] section as described further in this article.
For details about moving the existing project to the new abstraction layer configuration, refer to the Fabric Upgrade Procedure to 7.0.
Default PubSub Settings
All the PubSub connection settings are defined in the [default_pubsub] section of config.ini and not in the interface. The [default_pubsub] section allows to define the connection settings in one location and apply them across various Fabric processes.
The only parameter included in the interface definition is the Config Section. It holds the name of the config.ini section where the connection settings are defined. By default, it is set to default_pubsub.
The [default_pubsub] section is also used by CDC and Common DB processes for the same purpose of connecting to Kafka. For more details about overriding the CDC and Common DB connection settings, refer to the CDC Configuration and CommonDB Configuration articles.
Parameters Description
The main configuration setting of the [default_pubsub] section of config.ini are:
TYPE - the PubSub type that can have one of the following values:
- KAFKA (default) - execute the message handling via Apache Kafka.
- JMS - execute the message handling via JMS.
- MEMORY - execute the message handling via an internal queue that runs on localhost. This type can only be used for debug purpose. The Fabric Studio automatically sets TYPE=MEMORY in the project's config.ini.
- NO_OP - do not send or receive the messages. This type can only be used for debug purpose.
- ERROR - simulate throwing an Unsupported Operation exception. This type can only be used for debug purpose.
BOOTSTRAP_SERVERS - holds the IP address of the Kafka servers. It is possible to populate several IP addresses separated by a comma.
TRANSACTION_MODE - determines how the publisher handles transactions. There are 3 such modes:
- ASYNC (default) - messages are sent asynchronously. An acknowledgement is received only after a commit is performed. Async mode doesn't guarantee that all messages would be committed.
- BROKER - the transactional producer allows sending data to multiple partitions and guarantees all these writes are either committed or discarded. This is done by grouping multiple calls to be sent into a transaction. Once a transaction is started, you can either commit or rollback to complete it.
- IGNORE - messages are sent synchronously. Commit is done one by one.
Security protocol and other SSL/SASL properties - mandatory to be set when Kafka is defined with either SSL or SASL.
- The supported protocols are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.
- The supported SASL flavors are: SASL_SCRAM, SASL_LDAP, SASL_GSSAPI, SASL_PLAIN.
Group ID, Topic and Partitions
The GROUP_ID, TOPIC and PARTITIONS parameters are mandatory when setting up Kafka. These parameters should be defined as either:
- The Pub / Sub Actors' input arguments, or
- In the custom section of config.ini while adding the section name to the PubSub Configuration interface that the Actor is using.
If the GROUP_ID, TOPIC and PARTITIONS parameters are not found in either of the above, the exception will be thrown at run time.
How Do I Override The Default Settings?
When different connection settings are required for various processes, you can create additional section(s) in the config.ini and add their names to the interface’s Config Section parameter, separated by comma.
The first section name from this list, which is found in the config.ini, will be used. If, for any reason, the section name defined in the interface does not exist in the config.ini, the settings will be taken from the [default_pubsub] section. The new section does not have to include all the parameters, but only those that override the default section's settings.
PubSub Configuration Interface
Overview
A PubSub Configuration interface type defines the Fabric connection to message provider (such as Apache Kafka or JMS) using the PubSub abstraction layer. The configuration is performed via the [default_pubsub] section as described further in this article.
For details about moving the existing project to the new abstraction layer configuration, refer to the Fabric Upgrade Procedure to 7.0.
Default PubSub Settings
All the PubSub connection settings are defined in the [default_pubsub] section of config.ini and not in the interface. The [default_pubsub] section allows to define the connection settings in one location and apply them across various Fabric processes.
The only parameter included in the interface definition is the Config Section. It holds the name of the config.ini section where the connection settings are defined. By default, it is set to default_pubsub.
The [default_pubsub] section is also used by CDC and Common DB processes for the same purpose of connecting to Kafka. For more details about overriding the CDC and Common DB connection settings, refer to the CDC Configuration and CommonDB Configuration articles.
Parameters Description
The main configuration setting of the [default_pubsub] section of config.ini are:
TYPE - the PubSub type that can have one of the following values:
- KAFKA (default) - execute the message handling via Apache Kafka.
- JMS - execute the message handling via JMS.
- MEMORY - execute the message handling via an internal queue that runs on localhost. This type can only be used for debug purpose. The Fabric Studio automatically sets TYPE=MEMORY in the project's config.ini.
- NO_OP - do not send or receive the messages. This type can only be used for debug purpose.
- ERROR - simulate throwing an Unsupported Operation exception. This type can only be used for debug purpose.
BOOTSTRAP_SERVERS - holds the IP address of the Kafka servers. It is possible to populate several IP addresses separated by a comma.
TRANSACTION_MODE - determines how the publisher handles transactions. There are 3 such modes:
- ASYNC (default) - messages are sent asynchronously. An acknowledgement is received only after a commit is performed. Async mode doesn't guarantee that all messages would be committed.
- BROKER - the transactional producer allows sending data to multiple partitions and guarantees all these writes are either committed or discarded. This is done by grouping multiple calls to be sent into a transaction. Once a transaction is started, you can either commit or rollback to complete it.
- IGNORE - messages are sent synchronously. Commit is done one by one.
Security protocol and other SSL/SASL properties - mandatory to be set when Kafka is defined with either SSL or SASL.
- The supported protocols are: PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL.
- The supported SASL flavors are: SASL_SCRAM, SASL_LDAP, SASL_GSSAPI, SASL_PLAIN.
Group ID, Topic and Partitions
The GROUP_ID, TOPIC and PARTITIONS parameters are mandatory when setting up Kafka. These parameters should be defined as either:
- The Pub / Sub Actors' input arguments, or
- In the custom section of config.ini while adding the section name to the PubSub Configuration interface that the Actor is using.
If the GROUP_ID, TOPIC and PARTITIONS parameters are not found in either of the above, the exception will be thrown at run time.
How Do I Override The Default Settings?
When different connection settings are required for various processes, you can create additional section(s) in the config.ini and add their names to the interface’s Config Section parameter, separated by comma.
The first section name from this list, which is found in the config.ini, will be used. If, for any reason, the section name defined in the interface does not exist in the config.ini, the settings will be taken from the [default_pubsub] section. The new section does not have to include all the parameters, but only those that override the default section's settings.
