Configuring Logging for Java Components

Logging configuration for Java components applies to omsServer, Orchestrator, Automated Order Plan Development, Order Management Server UI, and Jeopardy Management System.

Logging is done using Log4j framework. Each component has a separate file for Log4j configurations as explained below.

Order Management Server and Orchestrator: $OM_HOME/roles/configurator/standalone/config/OMSServerLog4j.xml is used to configure logging in database mode. For the non-database mode configure $OM_HOME/roles/omsServer/standalone/config/OMSServerLog4j.xml.

  • The default logLevel is:
    • INFO for com.tibco.aff package and its sub package
    • ERROR for all other packages
  • Default publishLogLevel (for central logging)
    • WARN (Look for "JMSAppender" and the following entry within it <param name="Threshold" value="WARN"/>)
  • Local log file used by omServer and Orchestrator is omsServer-local.log. Published logs go into the logs folder for each service, the same as for the other components.

Order Management Server UI: $OM_HOME/roles/configurator/standalone/config/OMSUILog4j.xml is used to configure logging in database mode. For the non-database mode configure $OM_HOME/roles/omsui/standalone/config/OMSUILog4j.xml.

  • The default logLevel is:
    • INFO for com.tibco.aff package and its sub package
    • ERROR for all other packages
  • Local log file used by omUi component is omsui-local.log.
  • Order Management Server UI does not send messages to the central log server.

Jeopardy Management System:$OM_HOME/roles/configurator/standalone/config/OMSServerLog4j.xml is used to configure logging in database mode. For the non-database mode configure $OM_HOME/roles/omsServer/standalone/config/OMSServerLog4j.xml.

  • The default logLevel is:
    • INFO for com.tibco.aff.jeoms and com.tibco.aff.eca.engine packages and their sub packages
    • ERROR for all other packages
  • Default publishLogLevel (for central logging)
    • INFO (Look for "JeomsJMSAppender" and the following entry within it <param name="Threshold" value="INFO"/>)
  • There is no local log file for Jeopardy Management System. The console logs go under the logs folder for each service, the same as for the other components.

Automated Order Plan Development: $OM_HOME/roles/configurator/standalone/config/AOPDLog4j.xml is used to configure logging in database mode. For the non-database mode configure $OM_HOME/roles/aopd/standalone/config/AOPDLog4j.xml.

  • The default logLevel is:
    • DEBUG for com.tibco.aff package and its sub packages
    • ERROR for all other packages
  • Default publishLogLevel (for central logging)
    • WARN (Look for "JMSAppender" and the following entry within it <param name="Threshold" value="WARN"/>)
  • Local log file used by Automated Order Plan Development in case of standalone deployment is aopd-local.log and in case of collocated deployment mode is omsServer-local.log. Published logs go into the logs folder for each service, the same as for the other components.