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/mdm.

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

Parameter Name Definition
MQ_MDM_DB_TYPEDatabase type

Example: POSTGRESQL, ORACLE, and SQLSERVER

MQ_MDM_DB_HOSTDatabase server host name

Example:
pgsqldb-eks.cx4wjme9qqns.us-west-2.rds.amazonaws.com

MQ_MDM_DB_PORTDatabase port

Example:

  • 5432 for POSTGRESQL
  • 1521 for ORACLE
  • 1433 for SQLSERVER

MQ_MDM_DB_NAMEDatabase 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 MDM 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 that 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 4minutes.

Note: MQ_MDM_DB_FLUSH_STRATEGY, MQ_MDM_DB_BLOCKING_TIMEOUT, and MQ_MDM_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 Enterprise Message Service™ support:
MQ_MDM_JMS_CLUSER_TYPESet the cluster type. For example, GenericCluster or TIBCOCluster.
MQ_EMS_CLUSTER_URLSet the cluster URL. For example, tcp://localhost:7222.
MQ_MDM_FAST_CACHE_ENABLEDTo enable golden record cache, set this value to true. Else, set it to false.
MQ_MDM_HTTP_SESSION_REPLICATION_ENABLEDBy default, the value is set to true to use multiple nodes and replicate the session.
MQ_ACTIVEMQ_COMPONENT_IDSThe name by which TIBCO MDM server discovers other services

Example: MQ_ACTIVEMQ_COMPONENT_IDS: activemq.namespace.svc.cluster.local

MQ_PATTERNS_COMPONENT_IDSExample: MQ_PATTERNS_COMPONENT_IDS: patterns.namespace.svc.cluster.local

For TIBCO Patterns gateway: patternsgateway.namespace.svc.cluster.local

MQ_IGNITE_COMPONENT_IDSExample: MQ_IGNITE_COMPONENT_IDS: ignite.namespace.svc.cluster.local
MQ_MDM_COMPONENT_IDSExample: MQ_MDM_COMPONENT_IDS: mdm.namespace.svc.cluster.local
MQ_TZSet the time zone before you deploy containers in Kubernetes. All containers including the database must be in the same time zone. By default, the time zone is set to Asia/Kolkata.
MQ_PATTERNS_PRIMARYE
MQ_PATTERNS_BACKUP		To deploy a TIBCO Patterns server with primary and backup nodes. Examples:
  • patternsprimary.development.svc.cluster.local
  • patternsbackup.development.svc.cluster.local
MQ_PATTERNS_PRIMARY_GATEWAY
MQ_PATTERNS_BACKUP_GATEWAY		To deploy TIBCO Patterns Gatway. Examples:
  • patternsprimarygateway.development.svc.cluster.local
  • patternsbackupgateway.development.svc.cluster.local
MAX-PARAMETERS-COUNTSet the maximum number of parameters that can be added to the TIBCO MDM URL into the browser.
MAX-POST-SIZE Set the maximum file size to upload a file either through a web service or the TIBCO MDM UI.
MQ_HTTP_SESSION_TIMEOUTSet the session timeout for the server. By default, the value is set to 30 minutes that is 1800 seconds.
For TIBCO MDM REST API through Swagger UI
SWAGGER_MDM_HOST An IP address of the TIBCO MDM server on which you want to try out TIBCO MDM REST APIs.
SWAGGER_MDM_PORT Port of the TIBCO MDM server on which you want to try out TIBCO MDM REST APIs.