Describing Details of the isTraceLoggingEnabled Custom XPath Function Describing Details of the logTraceMessage Custom XPath Function Describing the Trace Logging Java API

Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-35 These custom XPath trace logging functions are available to BPEL and Mediator services operating in an Oracle AIA ecosystem. ■ aia:isTraceLoggingEnabledString logLevel, String processName Determines whether trace logging is enabled for the service or at the overall system level. ■ aia:logTraceMessageString level, Element ebmHeader, String message Generates the actual trace log. When developing a BPEL or Mediator process, always call the aia:isTraceLoggingEnabled function first. If it returns a true result, then have the process call the aia:logTraceMessage function. These log files are stored in the aia.homelogs directory. In addition to these custom XPath functions, a Java API is also available so that any application developer can use it to log trace messages. For more information about using trace logs, see Using Trace and Error Logs in Oracle Fusion Middleware Infrastructure Components and Utilities Users Guide for Oracle Application Integration Architecture Foundation Pack.

24.10.1 Describing Details of the isTraceLoggingEnabled Custom XPath Function

The isLoggingEnabled custom XPath function is a utility function that returns a Boolean result. The function signature is: aia:isTraceLoggingEnabled String logLevel, String processName These are the parameter details: ■ logLevel Possible values include: – Severe – Warning – Info – Config – Fine – Finer – Finest ■ processName Name of the Oracle AIA service using this function.

24.10.2 Describing Details of the logTraceMessage Custom XPath Function

The logTraceMessage custom XPath function generates a trace message, which contains the details of the message to be included in the trace log. This function accepts the EBM header and the verbose logging message as parameters. Various elements from the EBM header will be used to populate supplemental attributes to the log message. If the EBM header is not passed, these supplemental attributes are set as empty strings. 24-36 Developers Guide for Oracle Application Integration Architecture Foundation Pack The function signature is aia:logTraceMessage String level, Element ebmHeader, String message. These are the parameter details: ■ level Possible values include: – Severe – Warning – Info – Config – Fine – Finer – Finest ■ ebmHeader EBM header. ■ message Verbose text message to be logged.

24.10.3 Describing the Trace Logging Java API

In addition to the isTraceLoggingEnabled and logTraceMessage custom XPath functions, a trace Logging Java API is also available so that any application developer can log trace messages. These functions are available through the trace logging Java API. One of the function signatures is AIALogger.isTraceLoggingEnabled String logLevel, String processName. This function determines whether trace logging is enabled for the service or at the overall system level. These are the parameter details: ■ logLevel Possible values include: – Severe – Warning – Info – Config – Fine – Finer – Finest ■ processName Name of the Oracle AIA service using this function. Another function signature is AIALogger.logTraceMessage String level, Element ebmHeader, String message. This function generates the actual trace log. These are the parameter details: ■ level Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-37 Possible values include: – Severe – Warning – Info – Config – Fine – Finer – Finest ■ ebmHeader EBM header. ■ message Verbose text message to be logged. 24-38 Developers Guide for Oracle Application Integration Architecture Foundation Pack 25 Working with AIA Design Patterns 25-1 25 Working with AIA Design Patterns This chapter discusses the design patterns used in Oracle Application Integration Architecture AIA and provides solutions to specific problems that you may encounter. This chapter includes the following sections: ■ Section 25.1, AIA Message Processing Patterns