Configuration Variables Logging
When Microservices Runtime applies the configuration variables template at startup, Microservices Runtime has not yet initialized the journal logger which is used for the server log. For this reason, Microservices Runtime uses a separate logging capability for logging Microservices Runtime messages related to processing a configuration variables template. The configuration variables log contains messages about the operations, warnings, and errors that occur while Microservices Runtime applies the template.
Below is an excerpt from the configuration variables log:
2018-06-18 15:34:10 EDT [ISS.0028.0016I] Configuration variables template file
found at C:\SoftwareAG\IntegrationServer\application.properties will be used for
processing.
2018-06-18 15:34:12 EDT [ISS.0028.0007I] Changed property in
C:\SoftwareAG\IntegrationServer\instances\default\config\server.cnf. Old value:
localhost. New value: localhost,127.0.0.1. Configuration variable key:
watt.net.proxySkipList.
2018-06-18 15:34:12 EDT [ISS.0028.0017W] Encryptor is creating
because the given
wm.is.admin.WSEndpoint.message.CONSUMER.HTTPS.ws_cons_https does not exist in
the password store.
2018-06-18 15:34:12 EDT [ISS.0028.0008I] Set password in secure password store.
: wm.is.admin.WSEndpoint.message.CONSUMER.HTTPS.ws_cons_https
2018-06-18 15:34:12 EDT [ISS.0028.0017W] Encryptor is creating
because the given
wm.is.admin.WSEndpoint.transport.CONSUMER.HTTPS.ws_cons_https does not exist in the password store.
2018-06-18 15:34:12 EDT [ISS.0028.0008I] Set password in secure password store.
: wm.is.admin.WSEndpoint.transport.CONSUMER.HTTPS.ws_cons_https
2018-06-18 15:34:12 EDT [ISS.0028.0008I] Set password in secure password store.
: wm.is.admin.WSEndpoint.message.CONSUMER.HTTPS.ws_cons_https
2018-06-18 15:34:12 EDT [ISS.0028.0007I] Changed property in
C:\SoftwareAG\IntegrationServer\instances\default\config\kerberos.cnf. Old
value: . New value:
Each log message is prefixed with the time stamp and a message ID that includes the logging facility (0028), message code, and the severity level. The severity levels are described in the following table:
| Level | Description | Example |
C | Critical | Could not execute the configuration variables processing or an error occurred that caused Microservices Runtime initialization to stop. | Configuration file C:\SoftwareAG\IntegrationServer\instances\default\packages\WmPublic\config\listeners.cnf not found |
E | Error | One or more of the intended configuration changes could not be applied | java.io.FileNotFoundException: C:\SoftwareAG\IntegrationServer\instances\default\config\jndi\jndi_BasicAuth.properties (The system cannot find the file specified) |
W | Warning | A configuration variable was applied, but there is something about which you should be aware. | Property corresponding to key username not found in XML file proxy.cnf. |
I | Information | Informational messages about the progress of configuration variables processing. | Changed property in C:\SoftwareAG\IntegrationServer\instances\default\config\server.cnf. Old value: localhost New value: localhost,127.0.0.1 Configuration variable key: watt.net.proxySkipList. |
D | Debug | Low level messages, helpful for troubleshooting. | Processor found for the assetType truststore. |
Microservices Runtime does not support filtering the contents of the configuration variables log based on logging level. By default, the configuration variables log includes all messages with a severity of Information or higher. To include debug messages in the log, you must set the SAG_IS_CONFIG_VARIABLES_DEBUG environment variable to true at startup.
Microservices Runtime writes the configuration variables log messages to the console (STDOUT) and/or to the location: Integration Server_directory /instances/instanceName/logs/configurationvariables.log. A Microservices Runtime running in a Docker container always writes the configuration variables log messages to both locations.
Note:Microservices Runtime running in a Docker container also writes the server log to the console. Configuration variables log messages include “ISS.0028” in the message ID which distinguishes the messages from server log messages.
When starting an on-premises Microservices Runtime from the command line, you can specify the destination for the configuration variables log using the -log switch.
The following table identifies the command line options for specifying the destination of the configuration variables log file.
Command Line Option | Log Destination |
-log none | The console (STDOUT). |
-log both | The console (STDOUT) and Integration Server_directory /instances/instanceName/logs/configurationvariables.log. |
Note:
If the -log switch is not specified, Microservices Runtime writes the log messages to this location only: Integration Server_directory /instances/instanceName/logs/configurationvariables.log |
Starting Microservices Runtime from the command line is the same as starting Integration Server from the command line.
For information about starting Integration Server from the command line, see webMethods Integration Server Administrator’s Guide.
Microservices Runtime does not preserve the contents of the configurations variable log across restarts. When running on-premises Microservices Runtime overwrites the existing configurations variable log upon startup.