Configuring Logging for Java Components

Logging configuration for Java components applies to omsServer, Orchestrator, AOPD, omsUi, and jeoms.

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

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

  • The default logLevel is:
    • INFO for com.tibco.aff package and its subpackage
    • 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, same as for the other components.

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

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

JeOMS:$AF_HOME/roles/configurator/standalone/config/OMSServerLog4j.xml is used to configure logging in database mode. For the non-database mode configure $AF_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 subpackages
    • 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 JeOMS. The console logs go under the logs folder for each service, same as for the other components.

AOPD: $AF_HOME/roles/configurator/standalone/config/AOPDLog4j.xml is used to configure logging in database mode. For the non-database mode configure $AF_HOME/roles/aopd/standalone/config/AOPDLog4j.xml.

  • The default logLevel is:
    • DEBUG for com.tibco.aff package and its subpackages
    • 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 AOPD in case of standalone deployment is aopd-local.log and in case of colocated deployment mode is omsServer-local.log. Published logs go into the logs folder for each service, same as for the other components.

OPE :$AF_HOME/roles/configurator/standalone/config/OPELog4j.xml is used to configure logging in database mode. For the non-database mode configure $AF_HOME/roles/ope/standalone/config/OPELog4j.xml

  • The default logLevel is:
    • DEBUG for com.tibco.aff package and its subpackage
    • 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 OPE in standalone deployment is ope-local.log and in case of colocated deployment mode is omsServer-local.log.