ConfigMap Parameters

You can update the ConfigMap parameters for YAML files and Helm chart based on the configuration that you are using.

For the YAML files, update the parameters in the Configuration.yaml file located at docker/k8s_deployment.
For the Helm chart, update the parameters in the values.yaml file located at docker/k8s_helm/pschelm.

The following table lists the parameters available in the ConfigMap file, their definitions and example values:

Parameter Name	Definition
`MQ_MDM_DB_TYPE`	Database type Example: `POSTGRES and` `ORACLE`
`MQ_MDM_DB_HOST`	Database server host name Example: `pgsqldb-eks.cx4wjme9qqns.us-west-2.rds.amazonaws.com`
`MQ_MDM_DB_PORT`	Database port Example: `5432` for `POSTGRESQL` `1521` for `ORACLE`
`MQ_MDM_DB_NAME`	Database name Example: `velodb`
`MQ_MDM_DB_USETABLESPACES`	Set this value to `true`, to set your own tablespace location. For example, Microsoft Azure SQL and on-premise database setup. Set this value to `false` for cloud platforms where you do not know the tablespace location. For example, AWS and GCP.
`MQ_MDM_DB_MIN_CONN_COUNT` `MQ_MDM_DB_MAX_CONN_COUNT`	Minimum and maximum number of database connections for TIBCO PSC database.
`MQ_MDM_DB_FLUSH_STRATEGY`	Specifies how the pool must be flushed if an error occurs. By default, the value is set to `FailingConnectionOnly`, which forces destroying connections with error.
`MQ_MDM_DB_BLOCKING_TIMEOUT`	Specifies the length of time required to wait for a connection that is available when all the connections are checked out. By default, the value is set to `300000`, which is 30 seconds.
`MQ_MDM_DB_IDLE_TIMEOUT`	Indicates the number of minutes after which unused connections are closed. By default, the value is set to `4` minutes.
Note: `MQ_PSC_DB_FLUSH_STRATEGY`, `MQ_PSC_DB_BLOCKING_TIMEOUT`, and `MQ_PSC_DB_IDLE_TIMEOUT` are required only for the JBoss WildFly application server. For the supported valid values, see WildFly documentation.
Add the following properties for TIBCO PSC support:
`MQ_MDM_JMS_CLUSER_TYPE`	Set the cluster type. For example, `TIBCOCluster`. (for TIBCO EMS, use `TIBCOCluster`)
`MQ_EMS_CLUSTER_URL`	Set the cluster URL. For example, `tcp://localhost:7222`.
`MQ_MDM_FAST_CACHE_ENABLED`	To enable golden record cache, set this value to `true`. Else, set it to `false`.
`MQ_MDM_HTTP_SESSION_REPLICATION_ENABLED`	By default, the value is set to `true` to use multiple nodes and replicate the session.
`FC_SERVICE_HOST`	Example: `PSC_SERVICE IP address (cluster/loadbalancer)`
`FC_SERVICE_PORT`	Example: `PSC_SERVICE Port exposed (cluster/loadbalancer)`
`FC_SERVICE_FLAG`	While using Ingress make the flag as true
`WEB_URL_HOST`	http://<hostname>:8080
`OPD_APP_DATA_VOLUME`	Depending on the OPD deployment take select lite or heavy configuration. (see OPD document for more details)
`MQ_IGNITE_COMPONENT_IDS`	Example: `MQ_IGNITE_COMPONENT_IDS`: `ignite.namespace.svc.cluster.local`
`MQ_MDM_COMPONENT_IDS`	Example: `MQ_PSC_COMPONENT_IDS`: `psc.namespace.svc.cluster.local`

Did you find this helpful?

Yes No