Notifications

Handlers can also be configured for notification messages which are received through ActiveMQ (AMQP). The configuration supports defining multiple ActiveMQ queue manager connections that can be referenced by notification handlers.

Notification Configuration Properties describes the configuration properties available when defining notification handlers:

Table 1. Notification Configuration Properties
Property	Description	Example Value
mdc.notifications.handlers.`handler_name`.queueManager	The name of the ActiveMQ queue manager to connect to. This must match one of the names specified in the `mdc.notifications.queueManagers` property.
mdc.notifications.handlers.`handler_name`.specVersion	(Optional) The 3GPP 5GC Specification version. If not specified, the default value is the value of the `gateway.specifications.version` property.	R15-2019-12
mdc.notifications.handlers.`handler_name`.requestQueue	The name of the queue from which notification messages from the engine are read. These are in MATRIXX Data Container (MDC) format and must be of type Mtx5GMsg.
mdc.notifications.handlers.`handler_name`.responseQueue	The name of the queue on which responses from the network are sent back to the engine. These are in MDC format and must be of type Mtx5GMsg.
mdc.notifications.handlers.`handler_name`.consumers	(Optional) The number of consumers to create for this handler. The default value is 2.
mdc.notifications.handlers.`handler_name`.auditNetworkConfirmations	(Optional) If set to true, responses from the network are logged for auditing . The default value is `true`.
The following configuration is a map of Dynamic Message Mapper configurations which are chosen based on the type of MDC that is received on the request queue.
mdc.notifications.handlers.`handler_name`.mdcMappings.`MDC_name`.requestMappingFile	The name of the Dynamic Message Mapper configuration file to use for incoming requests converting MDC to JSON. This file must exist in /opt/mtx/conf/mapping/`specificationVersion`.	ChargingNotifyRequest-5200-mapping.yaml
mdc.notifications.handlers.`handler_name`.mdcMappings.`MDC_name`.responseMappingFile	The name of the Dynamic Message Mapper configuration file to use for outgoing responses converting JSON to MDC. This file must exist in /opt/mtx/conf/mapping/`specificationVersion`.	ChargingNotifyResponse-5200-mapping.yaml
mdc.notifications.handlers.`handler_name`.mdcMappings.`MDC_name`.traceEnabled	(Optional) If set to `true`, more trace output is provided in the logs when performing mapping.
mdc.notifications.handlers.`handler_name`.mdcMappings.`MDC_name`.placeholderProperties	(Optional) A map of values that are used to replace placeholders within the mapping file that are in the format `${mapkey}`. Values can include resolvable property names in the format `${property.name}`.	`placeholderProperties: customMdcName: "Acme5GRequest"`
mdc.notifications.handlers.`handler_name`.mdcMappings.`MDC_name`.inputParameters	(Optional) A map of values that are added to the mapping input parameters by default. Values can include resolvable property names in the format `${property.name}`.	`inputParameters: nfInstanceId: "${gateway.nfInstanceId}" test: "abc"`

ActiveMQ Connection Configuration Properties describes the configuration properties available when defining an ActiveMQ connection.

Table 2. ActiveMQ Connection Configuration Properties
Property	Description
mdc.notifications.queueManagers.`queue_manager_name`.url	The URL of the ActiveMQ queue manager. This must use the AMQP protocol. The default value is `amqp://localhost:15672`.
mdc.notifications.queueManagers.`queue_manager_name`.username	The username to use when connecting to the queue manager.
mdc.notifications.queueManagers.`queue_manager_name`.password	The password to use when connecting to the queue manager.
mdc.notifications.queueManagers.`queue_manager_name`.initRetryDelayMillis	The delay (in milliseconds) between attempts to create a connection at start up. The default value is 5000.
mdc.notifications.queueManagers.`queue_manager_name`.maxconnections	The maximum number of connections in the JMS connection pool. The default value is 10.