Integration Server 10.3 | Microservices Runtime Guide | Using Configuration Variables Templates with Microservices Runtime | Editing a Configuration Variables Template
 
Editing a Configuration Variables Template
 
Encrypting Values for the Variables Template
After you generate a configuration variables template from a Microservices Runtime, you modify the configuration variables template to contain the property values that you want applied to a Microservices Runtime at startup. You can hard code values or specify an environment variable as the value. You can also encrypt values to protect sensitive data.
Keep the following information in mind when you edit a configuration variables template.
*Any value that you specify must meet the requirements for the associated property. For example, global variable values cannot exceed 255 characters. If the value is not valid, failures will occur at runtime, either during server initialization or when clients start sending in requests.
*A configuration variables template can be used to change the configuration information for assets that already exist on the Microservices Runtime only. You cannot add assets to a Microservices Runtime by adding key-value pairs to a template.
*The configuration variables template lists only assets that existed on the Microservices Runtime from which you generated the template. You can add assets to the template if you know those assets will exist on the Microservices Runtime that will use the template. At startup, if the template specifies a value for a non-existent asset, the Microservices Runtime logs a message to the configuration variables log.
For more information about assets and properties and the corresponding key name, see Configuration Variables Template Assets.
*When Microservices Runtime generates an application.properties template, any properties that contain an alias name with a period (.) include another period as an escape character. For example, for a JMS connection alias named my.JMS.alias, the template property corresponding to the Client ID in the alias the name: jms.my..JMS..Alias.clientID=value
Do not remove the period (.) acting as the escape character.
If you edit the template by adding a key-value pair for an asset property and the asset property includes an alias name with a period (.), make sure to add another period to serve as the escape character.
*To supply a value in the template
1. Open the template in a text editor.
2. For each value that you want to supply, do one of the following:
To
Enter this for the property value
Hard code a value
The value you want to use.
Use an environment value as the value
The name of the environment variable in the format: $env{environmentVariableName}
Where environmentVariableName is the name of the environment variable. For example: $env{JDBC_URL}
Encrypt a value
Use Microservices Runtime Administrator to generate an encrypted value and then copy that value into the template. For more information see, Encrypting Values for the Variables Template.
While Microservices Runtime accepts clear text passwords as well as encrypted ones, Software AG recommends that you encrypt all passwords and other sensitive data in your configuration variables templates.
3. Repeat the above step for each key that you want to set.
4. Save the template.