tenants
The
tenants
section of the Consul key-value store adds all tenant-specific configuration for the product.
The typical format of a notification key is:
/config/application/tenants/<TenantName>/<keysSpecificToThisTenant>
For example:
The following table lists the keys that are required for any TIBCO Offer and Price Engine deployment:
Key | Description | Value |
---|---|---|
jwtexpiration
|
The JWT expiration time, in milliseconds. | Positive values only.
Default value:
Maximum value:
|
miniourl
|
The URL for MinIO.
For example:
|
|
elasticsearchUrl
|
The URL for ElasticSearch.
For example:
|
|
tenantList
|
The list of all tenants. If there is only one tenant, the value isdefault .
For example, For a single tenant:
For multiple tenants:
|
|
minioAccesskey
|
The Access key for the MinIO server. | |
minioSecretKey
|
The Secret key for the MinIO server. | |
modelPollerThreadCount
|
The thread count for the model processing.
Assuming that the Model Load Engine micro service has enough RAM to process models, the recommendation is to use 100 threads for each MinIO cluster node. For example, if MinIO runs as a three node cluster, this count should be
Maximum value allowed:
|
|
The following fields are required if using the corresponding TIBCO Offer and Price Engine features. | ||
emsUrl
|
EMS Url endpoint URL. This key is required if online model loading functionality is required with "Message Adapter" microservice | |
elasticsearchUrl
|
Elastic Search endpoint URL. This key is required if Elastic Search is enabled for "Search and Browse" OPE functionality | |
com.tibco.af.ope.flags.udfignorelist
|
Any other OPE specific functional keys. For example, a key to add "ignore UDF" list |
For example, if the
com.tibco.af.ope.flags.udfignorelist
key is required only by tenant
t1
, the key has to be added in the following manner:
kv/config/application/tenants/t1/com.tibco.af.ope.flags.udfignorelist
The key applies to all tenants if it is under the
default
tenant.
In case the specific key for "default" tenant is needed to be applicable ONLY for the "default" tenant then the customer has to create a separate tenant with the name other than "default" and add the tenant-specific configuration for it.