Integration Server 10.5 | Microservices Runtime Guide | Using Configuration Variables Templates with Microservices Runtime | When Is the Template Applied? | How the Configuration Is Updated When IS_10.5_Core_Fix7 Is Not Applied
 
How the Configuration Is Updated When IS_10.5_Core_Fix7 Is Not Applied
While substituting variable values and IS_10.5_Core_Fix7 or higher is not applied, 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.