Configuration Image Contents

The default configuration for a MATRIXX component can be overridden as needed, using a configuration source. The contents of images for Docker-type configuration sources vary depending on the component the image reconfigures.

Configuration images are not required. Default configuration values are applied in MATRIXX component images. Use configuration sources to change specific settings for your deployment. Different configuration sources can be constructed for each component, or all configuration files can be delivered in different directories within a single source, using the directoriesToUnpack option to select the directory for the component. The following sections describe contents and intended usage for component configuration images where needed in your deployment.

Note: Sideloader images provided with MATRIXX are templates that include all default values and, if applied, they overwrite configuration that might have been made using properties in your Helm values file or files. The templates are intended for use as a reference when creating your own images for configuration. Images created from the templates normally contain a highly modified subset of the files included with the templates.

Engine Configuration Image Contents

The MATRIXX Engine configuration image can contain multiple configuration files to be merged at start-up as inputs for the create_config.py command. Files are loaded in alphabetical order. Each filename must end in create_config.info.

If a configuration question exists in two or more files, then the answer from the file with the alphanumerically higher name is used. You can group configuration elements by functional area such as custom MATRIXX Data Containers (MDCs), CCF, or selective updates. You can also layer configuration to apply more specific configuration over less-modified or default files. This can be useful when moving template configuration between deployments.

Files in an engine configuration source override corresponding equivalents from the topology-configmap ConfigMap. These files are named to allow default configuration to be available that can be overridden as needed. The topology-configmap ConfigMap has files with derived configuration generated specifically for the topology defined in the Helm values file. These have alphanumerically high file names because they should not be overridden in most scenarios.

Files Included in the topology-configmap ConfigMap describes files that may be overridden by files in an engine configuration image.

Table 1. Files Included in the topology-configmap ConfigMap
Name Purpose
0-default_create_config.info Provides basic default configuration for a simple deployment. The configuration questions are likely to be overridden by other files supplied in the configuration source.
zz9-activemq_create_config.info Provides the derived ActiveMQ configuration from the engine, based on the other components deployed within the environment. This configuration does not need to be overridden in most scenarios.
Note: MATRIXX Support recommends that you do not change the configuration in this file.
zz9-topology_create_config.info Provides topology-focused configuration for the engine, based on the other components deployed within the environment. This configuration does not need to be overridden in most scenarios.
Note: Providing a file in a configuration source with the same name as one of the file listed in Files Included in the topology-configmap ConfigMap causes the file to be completely overwritten. To only modify the configuration contained in the original file, give a file containing just the specific changes in a file with an alphanumerically higher filename.

TRA Configuration Image Contents

A Traffic Routing Agent (TRA) configuration image can contain files required for TRA. These files are not merged the way that the engine files are merged. Use exact file names that completely override the default configuration.

The following files can be overridden by a TRA configuration source.

  • tra_create_config.info
  • tra_config.xml
  • process_control.cfg
  • rcc_base.cfg (A rcc_base.cfg file provided in a configuration source only applies to TRA-RT. )
  • <pod_name>_tra_config_network_topology.xml (Optional) When providing this file in a in a configuration source, replace <pod_name> with the specifics for the pod running TRA. For example, trart-s1-0_tra_config_network_topology.xml.

Network Enabler Configuration Image Contents

As with the MATRIXX Engine image, the Network Enabler (NE) configuration image can contain multiple configuration files named *_create_config.info. The files are merged at start-up as inputs for the create_config.py command and loaded in alphabetical order.

If a configuration question exists in two or more files, then MATRIXX uses the answer from the file with the alphanumerically higher name.

The 0-default_create_config.info file supplies the NE default configuration, including whether CCF is enabled and the port ranges to use. NE default configuration derives from the topology supplied in your Helm values file, through the ne-ag1-sideloader-default-config ConfigMap.

To override NE default configuration, you must use a configuration source.

Java App Configuration Image Contents

Files included in configuration sources for reconfiguring MATRIXX gateways and web apps replace existing files with the same name within the component container. Other files are preserved. A typical configuration source has configuration files in the /opt/mtx/conf directory and any binary extension files, such as JAR files, in the /opt/mtx/ext directory according to the requirements of that component.