This figure shows a diagram of the Offline Mediation Controller REST Services Manager
cloud native deployment architecture. The architecture consists of:
- RSM Deployment: The main deployment of RSM with all the components and
configurations.
- RSM HTTP and HTTPS Service: Exposes RSM to ports. Allows access to RSM
through HTTP and HTTPS protocols.
- Validator Config Map: There is a unique config map for each market
segment.
- RSM App Config Map: Contains the application.yaml file with
configurations required to start the RSM Server.
- RSM Logging Config Map: Contains the log4j2.yaml file, which contains
logging related configurations.
- Admin Server Keystore Secret: Contains the administration server keystore
file in base64-encoded format.
- RSM HTTPS TLS Secret: Contains the HTTPS TLS store to be used by RSM when
the HTTPS protocol is enabled.
- RSM App Secret: Contains all the confidential information required to
start the RSM server.
- vol-external: This is an optional PV reference. RSM will incorporate it
only if the flag rsm.pvc.ocomcExternal.enabled in the
override-values.yaml file is set to "true." When enabled, the RSM
will share the "vol-external" PV of the OCOMC core deployment. It is mandatory
to enable this flag if the node chain solution includes cartridges containing
sensitive information such as FTP or database passwords.
- rsm-vol-external: This PV is optional and can be enabled by setting the
flag "rsm.pvc.external.enabled" to "true" in the values.yaml file. When enabled,
the RSM will load custom cartridges from the specified PV into the classpath.
The source directory for it can be configured in the override-values.yaml
file.
