webMethods Adapter Runtime 10.7 | webMethods Adapter Runtime Documentation | webMethods Adapter Runtime User’s Documentation | Configuration Variables Templates for Adapter Assets in Microservices Runtime | Configuration Variables Templates for Adapter Assets in Microservices Runtime
 
Configuration Variables Templates for Adapter Assets in Microservices Runtime
The webMethods Adapter Runtime (ART) asset properties which can be configured from Integration Server Administrator are available in configuration variables template generated by Microservices Runtime. Microservices Runtime generates an application.properties file. For more information, see Developing Microservices with webMethods Microservices Runtime.
You can update the values of the properties in the application.properties file and pass the updated values to Microservices Runtime. Microservices Runtime loads the information from the application.properties file and updates the webMethods Adapter Runtime assets configuration properties.
What Does an Adapter Runtime (ART) Assets Configuration Property Look Like?
The configuration data is a series of key-value pairs where the key name reflects the asset and a particular asset property for which you can supply a value. Each property name follows this pattern:
assetType.assetPackageName.assetName.propertyName=value
where,
*assetType is the type of webMethods Adapter Runtime asset like connection, listener or notification.
*assetPackageName is the Integration Server package which stores the webMethods Adapter Runtime assets.
*assetName is the name given to the asset like an alias.
*propertyGroup is the group to which the asset property belongs. The values can be onnectionManagerSettings and connectionSettings.
*propertyName is the asset property for which you can set a value.
Connection properties follow this pattern:
artConnection.<packageName>.<connectionName>.propertyGroup.property=value
For example, to update the database name in a JDBC connection connections:OracleConnection:
artConnection.TestPackage.connections.OracleConnection.connectionSettings.databaseName=orclcdb
Note:
The general properties are not grouped in with the propertyGroup. For example, to disable the connection connections:OracleConnection, the value of connectionEnabled property must be set to false.
artConnection.TestPackage.connections.OracleConnection.connectionEnabled=false
Listener properties follow this pattern:
artListener.<packageName>.<listenerName>.propertyGroup.property=value
For example, to update the deadLetterQueue in the MQ listener listener:listener1:
artListener.TestPackage.listener.listener1.listenerSettings.deadLetterQueue=TestQueue
Polling Notification properties follow this pattern:
artNotification.<packageName>.<notificationName>.propertyGroup.property=value
For example, to update the polling interval in JDBC polling notification notifications:BasicNotification:
artNotification.TestPackage.notifications.BasicNotification.extendedStatus.notificationInterval=10
You must encrypt sensitive data such as passwords before using it in the configuration variables template. For more information on generating an encrypted value in Microservices Runtime, see Developing Microservices with webMethods Microservices Runtime and webMethods Integration Server Administrator’s Guide.