You can set a fixed level, such as level="DEBUG", on a Logger or
Root element in log4j2.xml. Use OI_LOG_LEVEL and
DLQ_LOG_LEVEL for temporary root or DLQ changes, and package loggers
for targeted diagnostics.
With monitorInterval="300", Log4j2 detects
configuration-file changes within approximately five minutes.
To apply and verify a diagnostic change:
- Edit
<install-location>/openint-deploy/target/log4j2.xml. - Validate the XML syntax. If
xmllintis available, run:xmllint --noout log4j2.xmlThis command checks XML syntax. It does not verify whether the package applies to the request you are investigating.
- Wait up to five minutes for the configuration to reload. If you need the change immediately, restart Open Integration.
- Reproduce the affected request or integration execution.
- Review
logs/siebel-openint.logfor file logging, or the service or container console for console-only logging. - Remove the temporary package logger or change its level to INFO or ERROR after diagnosis. Do not leave TRACE or ALL enabled in a production deployment.
Note: Keep temporary diagnostic changes outside the checked-in source configuration. Changes
under
<install-location>/openint-deploy/target can be replaced
during packaging or deployment. If a logger must remain after redeployment, apply it
through the deployment’s managed configuration process.