Integration Server 10.3 | Microservices Runtime Guide | Using Configuration Variables Templates with Microservices Runtime | When Is the Template Applied?
 
When Is the Template Applied?
Microservices Runtime applies a configuration variables template at startup. When Microservices Runtime starts, either in a Docker container or on-premises, Microservices Runtime looks for a configuration variables template in the following locations in the specified order.
1. The location identified by the SAG_IS_CONFIG_PROPERTIES environment variable.
2. Integration Server_directory /instances/instanceName/application.properties
3. Integration Server_directory /application.properties
Once Microservices Runtime locates a template, Microservices Runtime does not look for a template in any remaining locations.
Note:
If Microservices Runtime does not find a configuration variables template at any of the above locations, Microservices Runtime proceeds with start up and does not apply a template.
Microservices Runtime processes the template, updating the configuration information in Microservices Runtime with the information in the template. While processing the template, Microservices Runtime writes log messages to the logs/configurationvariables.log to reflect the progress of the variable substitution. When substitution is complete, Microservices Runtime proceeds with startup.
While substituting variable values, Microservices Runtime ignores properties and values that do not correspond to existing assets on the Microservices Runtime. A configuration variables template can be used to change the configuration information only for assets that already exist on Microservices Runtime. That is, you cannot add assets to a Microservices Runtime by adding key-value pairs to a template
During substitution, Microservices Runtime ignores any values for properties that are not set on the Microservices Runtime. For example, suppose the configuration variables template file specifies the following for a JMS connection alias named myAlias:
jms.myAlias.clientID=abc
jms.myAlias.password=encryptedValue
jms.myAlias.user= userA
If the Microservices Runtime contains a JMS connection alias named “myAlias” and that alias specifies a Connection Client ID value of “xyz”, at startup, Microservices Runtime substitutes “abc” for “xyz”. If the myAlias connection alias does not specify values for Username or Password, Microservices Runtime does not substitute the values set in jms.myAlias.password or jms.myAlias.user.