Deploy case notifications for NBS 7

This page walks through deploying the NBS 7 Case Notification service for NBS version 7.13. Complete the Data Processing and optional NND Service (Data Sync) deployments before starting this page. After you finish, proceed to deploy the data ingestion service (DI API) or real-time reporting (RTR) based on your deployment plan.

On this page

  1. Overview
  2. Considerations
  3. Deployment overview

Overview

The case notification pipeline begins with a Debezium source connector monitoring the ODSE.CN_transportq_out table. When new data is inserted, the connector publishes it to a Kafka topic, which the Case Notification service consumes. The service processes each event and routes output to either MSGOUTE.transportq_out or MSGOUTE.netsstransportq_out depending on event type. Faulty events are routed to MSGOUTE.case_notification_dlt (Dead Letter Table) for investigation.

Case notifications and real-time reporting (RTR) can use the same Kafka cluster. To reduce potential cost and installation impact, consider re-using the Kafka cluster that you configure here when you deploy RTR.

Considerations

Your jurisdiction can use either the NBS 7 Case Notification service or route case notifications through an integration engine like Rhapsody.

  • If you are using an alternative integration engine, skip this section. Do not deploy the notification service, and do not enable it in Kubernetes.
  • If you are moving to NBS 7 case notifications, complete the steps in this section.

Deployment overview

To deploy the notification service, complete the steps in the following order:

  1. Deploy the Debezium Kafka source connector
  2. Deploy the Case Notification service
  3. Test and integrate case notification APIs

Table of contents