Payment Service for Multiple Sub-Domains

In a MATRIXX environment where multiple customer sub-domains are implemented in separate engine chains, you can configure the Payment Service with a request-response queue pair for each engine.

Define multiple sub-domains for the Payment Service in the /opt/mtx/conf/payment-service.yaml file. For each sub-domain, you can add an additional JMS queue pair.

The format for each JMS queue pair property is: 
payment:
  service:
    subDomains:
      - name: <subdomain name x>
        inboundQueueName: <inbound queue name>
        outboundQueueName: <outbound queue name>
JMS Parameter Descriptions for Multiple Sub-Domains describes each property.
Table 1. JMS Parameter Descriptions for Multiple Sub-Domains
Property Description
- name The sub-domain name. The suffix must match a MATRIXX Engine number configured during engine configuration, where x is a sequential number starting with 0. Each sub-domain must have an inbound queue, an outbound queue, and a sub-domain name. The x value must be the same for the sub-domain set of name, inbound queue, and outbound queue as shown in the example below.
inboundQueueName The name of the Apache ActiveMQ queue from which the Payment Service receives the payment request from MATRIXX Charging Application.
outboundQueueName The name of the Apache ActiveMQ queue to which the Payment Service sends the payment reply from the payment gateway. MATRIXX Charging Application retrieves the payment reply from this queue.
The following code shows an example of a payment-service.yaml file configured for multiple sub-domains:
payment:
  service:
    subDomains:
      - name: subDomain0
        inboundQueueName: payments.engine_to_paymentservice.subdomain0
        outboundQueueName: payments.paymentservice_to_engine.subdomain0
      - name: subDomain1
        inboundQueueName: payments.engine_to_paymentservice.subdomain1
        outboundQueueName: payments.paymentservice_to_engine.subdomain1