McDewey

registerModule(TraceModule, TraceWriterManager) public static com.cisco.services.tracing.TraceManager registerModule(com.cisco.services.tracing.TraceModule module, com.cisco.services.tracing.TraceWriterManagertraceWriterManager) Returns an instance of a TraceManager object. Trace output will be redirected to the TraceWriterManager object specified. Services Tracing Interface Hierarchy The following interface hierarchy is contained in the com.cisco.services.tracing package. com.cisco.services.tracing.Trace, on page 714 com.cisco.services.tracing.ConditionalTrace, on page 721 com.cisco.services.tracing.UnconditionalTrace, on page 722 com.cisco.services.tracing.TraceManager, on page 723 com.cisco.services.tracing.TraceModule, on page 727 com.cisco.services.tracing.TraceWriter, on page 728 com.cisco.services.tracing.TraceWriterManager, on page 731 Trace The Trace interface defines the methods that allow application tracing. Trace also defines the standard trace types as specified by Syslog Trace Logging.Syslog currently defines 8 levels of trace. The severity of the message is indicated in the trace as a number ranging between [0-7] (0 and 7 included). Currently 7 is HIGHEST_LEVEL and 0 is the LOWEST_LEVEL trace. All 8 levels are predefined here as static int types for reference in tracing sub-system implementations. The severities traced are as follows: 0 = EMERGENCIES System unusable 1 = ALERTS Immediate action needed 2 = CRITICAL Critical conditions 3 = ERROR Error conditions 4 = WARNING Warning conditions 5 = NOTIFICATION Normal but significant condition 6 = INFORMATIONAL Informational messages only 7 = DEBUGGING Debugging messages Declaration public interface Trace Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 714 Cisco Unified JTAPI Alarms and Services Services Tracing Interface Hierarchy