Creating New Assets with the Configurations Variable Template
For some asset types, you can add assets to Microservices Runtime by adding key-value pairs to the configuration variables template that is applied at startup. Any asset that you create must meet the naming requirements for the asset. An incorrectly configured asset can cause Microservices Runtime startup fail or result in failure during later server operations.
To add an asset to a configuration variables template, follow the procedure and guidelines in
Editing a Configuration Variables
Template.
The following list identifies the asset types for which you can create an asset through application of a configuration variables template:
Access Control List (ACL)
Broker connection alias
Note:
Only one Broker connection alias can exist on a Microservices Runtime (or an Integration Server). If the application.properties file being applied to the Microservices Runtime specifies a Broker connection alias, but a Broker connection alias already exists on Microservices Runtime, an error is written to the configurationvariables.log and the Broker configuration is not updated.
Consul
Email port
File polling port
Global variable (Package-Level)
Global variable (Server-Level)
Group
JDBC pool alias
JMS connection alias
JNDI provider alias
Keystore alias
LDAP configuration
Proxy server alias
Remote server alias
SFTP server alias
SFTP user alias
Truststore alias
Universal Messaging connection alias (
webMethods messaging)
User account