Frequently asked questions
- Do I need to configure anything for log4j2 logging to work in the Sterling Order Management System Software?
No, by default Sterling Order Management System Software code takes care of all the configuration, and logging works out-of-the box. If you encounter an error, review the exceptions, and modify your custom code to remove any log4j1x dependencies. For more information, see Migrating to log4j2.
- What should I do if I need logging to work only for my custom code and I don't want to change
the location or the names of log files?
Follow step #2 of customizing log4j2, and provide package names and levels for your custom code.
- What should I do if I need to write logs to a different location or different naming format or
logging format?
Disable the out-of-the-box configuration and provide your own configuration as explained in step #4 of customizing log4j2. This expects that you have read the official Apache documentation for log4j2 and are aware of what needs to be modified.
- What should I do if I want to write a custom appender and send logs to a different destination
than to a file?
Read the official Apache documentation for log4j2 to understand how to write a custom appender or to see whether any existing appender that is provided by Apache meets your needs. Then, disable the out-of-the-box configuration and provide your own configuration as explained in step #4 of customizing log4j2.