In order to listen to any Host events and trigger subsequent alerts in OBDX for the same, please follow the below steps as part of extensibility:

1. Add the below notification specific properties in Listener.properties config file in com.ofss.digx.kafka.<module>.listener subproject (out of the box project) under /src/main/resources:

       # notification
           specific properties   
           kafka.<module>.<sub-module>.consumer.group-id   
           kafka.<module>.<sub-module>.consumer.topic.name   
           kafka.enable.<module>.<sub-module>.config   
           com.ofss.digx.app.kafka.<module>.consumer.<sub-module>.<receiver-name>_POOL_SIZE=1

2. For any cz module <module>, under com.ofss.digx.cz.app.<module>.xface subproject:
   1. Get the avro schema format for the notification to be consumed from the host.
   2. Generate AVRO DTOs and add under com.ofss.digx.app.cz.<module>.dto.kafka.<sub-module> package.

      eg. for structure notification, EventMessage and LmmTmStructureEventsDTOAvro DTOs are committed under com.ofss.digx.app.liquiditymanagement.dto.kafka.structure in com.ofss.digx.app.liquiditymanagement.xface subproject

   3. Create a new subproject as com.ofss.digx.cz.kafka.<module>.listener and include api project(':com.ofss.digx.kafka.<module>.listener') as dependency in build.gradle of above subproject.
      1. For new message receiver, add entry for service implementation of com.ofss.digx.app.kafka.infra.consumer.IKafkaConsumer interface in com.ofss.digx.cz.kafka.<module>.listener subproject under /src/main/resources/META-INF/services

         eg. for structure notification, com.ofss.digx.app.kafka.liquiditymanagement.consumer.structure.StructureMessageReceiver has been added inside com.ofss.digx.app.kafka.infra.consumer.IKafkaConsumer file.

      2. Create com.ofss.digx.app.kafka.<module>.consumer.<sub-module>.<sub-module>MessageReceiver. In the new service implementation class of IKafkaConsumer interface (mentioned in above point) implement the below methods using the common classes present in the added dependency com.ofss.digx.kafka.<module>.listener subproject (eg. MessageReceiverUtility, ListenerConfig, IKafkaConsumer):

         1. Default Constructor: set properties variable to
                    be used for kafka consumer configuration/* code */ messageReceiverUtility.setProperties(properties);properties.put(ConsumerConfig.GROUP_ID_CONFIG,
                    ListenerConfig.getInstance().fetchPropertyValue("kafka.<module>.<sub-module>.consumer.group-id"));properties.put(ConsumerConfig.VALUE_DESERIALIZER_CLASS_CONFIG,
                    <deserializer-class>.class);/* code */

         2. . run(): to configure kafka consumer on topic
                    and start polling. Process notifications received on the topic
                  configured. /* code
                    */ messageReceiverUtility.run(consumer,
                    properties, Arrays.asList(ListenerConfig.getInstance().fetchPropertyValue(
                    "kafka.<module>.<sub-module>.consumer.topic.name")),
                    NOTIFICATION_SPECIFIC_AVRO_DTO.class); /* code
                    */

         3. isEnabled(): to determine if the listener needs
                    to be enabled or not by returning kafka enable config from listener
                    configuration/* code */ return
                    messageReceiverUtility.isEnabled("kafka.enable.<module>.<sub-module>.config");/* code */

         4. shutdown(): to call wakeup method on
                    consumer(stop consumer from polling on the configured topic) /* code */ messageReceiverUtility.shutdown(consumer); /* code */Refer StructureMessageReceiver class
                    under package com.ofss.digx.app.kafka.liquiditymanagement.consumer.structure (IKafkaConsumer
                    implementation for consuming structure related events)

      3. com.ofss.digx.app.cz.kafka.<module>.adapter.NotificationAdapterFactory - Introduce database entry for picking notification adapter :
         e.g.

         INSERT INTO DIGX_FW_CONFIG_ALL_B(PROP_ID,
                 CATEGORY_ID, PROP_VALUE, FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY,
                 CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER,
                 EDITABLE, CATEGORY_DESCRIPTION)
                 VALUES('<module_code>_HOST_NOTIF_<topic-name>','NotificationAdapterConfig','com.ofss.digx.app.cz.kafka.<module>.adapter.impl.<sub-module>NotificationAdapter','N',NULL,'<sub-module>
                 Notification
                 Adapter','ofssuser',SYSDATE,'ofssuser',SYSDATE,'Y',1,'N',NULL);

      4. Introduce new notification adapter for a new <sub-module> as <sub-module>NotificationAdapter under com.ofss.digx.app.cz.kafka.<module>.adapter.impl - to assemble the notification object into hostAlertDTO object and call the common host alert service

         e.g. com.ofss.digx.app.kafka.liquiditymanagement.adapter.impl.StructureNotificationAdapter

      5. Introduce new notification adapter assembler for a new <sub-module> as <sub-module>NotificationAdapterAssembler under com.ofss.digx.app.cz.kafka.<module>.adapter.impl - to assemble the notification object into hostAlertDTO object
         e.g.

         com.ofss.digx.app.kafka.liquiditymanagement.adapter.impl.assembler.StructureNotificationAdapterAssembler

      6. Configure a subscription based OBDX alert specific for the new notification configured. Post maintaining subscription for the new OBDX alert, subscribed users will receive OBDX alerts specific to the notification.

         <module> = liquiditymanagement or vam