Support of Periodic Reloading 

Use

The SAP Logging API provides options for log assignment with periodic reloading. This section covers only the general behavior, not the technical details.

For example, the use of an optional ‘+’:

com.sapmarkets.foo.logs = + log[Console]

 

The general rule – using  the log configuration without ‘+’, logs of the log controller that are already assigned are discarded, while with ‘+’, they are added to the existing list of logs.

Configuration Unchanged

When the configuration remains unchanged (which is typical once a stable configuration is defined), the use of ‘+’ is not significant. No further action is done and the objects that were already attached stay attached. This avoids loss of state of the attached objects.

Configuration Changed

The typical configuration updates include: changing the log destination, adding a log destination and modifying the properties of an existing log. The first two cases are straightforward (see Change Output Logs / Filters).

If you have already assigned logX to a location and you want to change the destination to logY in the next reloading, proceed as follows in the configuration file:

com.sapmarkets.foo.logs = logY

logX is removed.

To add to the existing logX:

com.sapmarkets.foo.logs = + logY

Both logX and logY persist.

●      The last type of modification (changing properties) mainly applies to the FileLog as it has a number of attributes. FileLog is identified by its ‘pattern’, therefore, a new pattern means a new log. This has a behavior similar to changing and adding log destination. The ‘+’ sign is important.

●      If the changes are on the other attributes, for example limit or cnt, the ‘+’ sign is not significant; no new FileLog will be created. The existing FileLog remains and will be modified with the corresponding new attribute values.