AllowRepositoryAutomapping - System Parameter
The Repository Model can be populated directly from your Log Events when adding special Context Options. If this option is enabled, the Logging Service will perform additional work and process the Log Events according to the provided Context Options. This pattern is recommended when you use integration brokers like MuleSoft Anypoint, and IBM Sterling or you have the need and/or possibility to have absolute control over what's being logged.
Important
You must put additional data to the Nodinite Log Events to make use of this feature.
The system parameter AllowRepositoryAutomapping is used to globally set if Nodinite should create entities in the Repository Model from Log Events.
| System Parameter Name | Data Type | Values/Example | Comment |
|---|---|---|---|
| AllowRepositoryAutomapping | boolean | true/false |
Default = false (Disabled), should be true (Enabled) when you use custom logging with Mule or code custom Log Events |
This feature comes with Nodinite version 4.3.0.76
Frequently asked questions
Additional solutions to common problems and the Nodinite System Parameters FAQ exist in the Troubleshooting user guide.
How do I change the value?
Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.
Do I need to restart anything?
This value lives in the cache for five minutes. The actual time may be different depending on the version of Nodinite.
This parameter is used by the Nodinite Logging Service to process and reprocess Log Events.
If you change this value then you must either wait for the cache to time out, or restart the Nodinite Logging Service.
Next Step
Log API
Log Events
Repository Model
Administration