ActiveMQ Gateway Configuration
MATRIXX Engine uses ActiveMQ to produce outbound 5G Notify requests for SBA Gateway and to consume their inbound responses.
To enable this functionality, the ActiveMQ configuration within create_config.info must include message handlers with the following names:
- chf_chargingdatanotify for converged charging Notify requests.
- chf_spendinglimitnotify for spending limit control Notify requests.
Each of these message handlers consists of a pair of message queues, one for MATRIXX Engine to
produce Notify requests and another for it to consume their responses. The names of these
queues must correspond, respectively, with the requestQueue
and responseQueue
in SBA Gateway
configuration file (nf.yaml).
By default, MATRIXX Engine and SBA Gateway configurations use the following queue names:
- chf_chargingdatanotify:
- Request/producer queue — chf_chargingdatanotify_request.
- Response/consumer queue — chf_chargingdatanotify_response.
- chf_spendinglimitnotify:
- Request/producer queue — chf_spendinglimitnotify_request.
- Response/consumer — chf_spendinglimitnotify_response.
Responses to Notify requests are logged using the
com.matrixx.sba.chf.notify.confirmations
log4j 2.x logger in the
format:
Response for <id>: <notifyUri> -> <httpStatusCode> <responseBody>
Example:
Response for 46: http://mocknf:9098/chargingNotify/error -> 404 {"invocationResult":{"error":{"type":"Not Found","title":"I don't know what you're talking about","status":404},"failureHandling":""}}
Logging is enabled by default. Disable logging by setting the
nf.chf.notify.auditNetworkConfirmations
configuration option to false.
For information about the ActiveMQ questions in the create_config.info file or for information about configuring ActiveMQ Gateway, see the discussion about ActiveMQ Gateway configuration in MATRIXX Configuration.
For information about logging, see the discussion about monitoring and logging.