IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Email > Troubleshooting and support
Log and Trace Analyzer
The adapter creates log and trace files that can be viewed with the Log and Trace Analyzer.
The Log and Trace Analyzer can filter log and trace files to isolate the messages and trace information for the adapter. It can also highlight the messages of an adapter and trace information in the log viewer.
The adapter's component ID for filtering and highlighting is a string composed of the characters EMARA plus the value of the adapter ID property.
For example, if the adapter ID property is set to 001, the component ID is EMARA001.
If you run multiple instances of the same adapter, ensure that the first eight characters of the adapter ID property are unique for each instance so that you can correlate the log and trace information to a particular adapter instance. By making the first seven characters of an adapter ID property unique, the component ID for multiple instances of that adapter is also unique, allowing you to correlate the log and trace information to a particular instance of an adapter.
For example, when you set the adapter ID property of two instances of WebSphere Adapter for Email to 001 and 002. The component IDs for those instances, EMARA001 and EMARA002, are short enough to remain unique, enabling you to distinguish them as separate adapter instances. However, instances with longer adapter ID properties cannot be distinguished from each other. If you set the adapter ID properties of two instances to Instance01 and Instance02, you will not be able to examine the log and trace information for each adapter instance because the component ID for both instances is truncated to EMARAInstanc.
For outbound processing, the adapter ID property is located in both the resource adapter and managed connection factory property groups. If you update the adapter ID property after using the external service wizard to configure the adapter for outbound processing, be sure to set the resource adapter and managed connection factory properties consistently. It prevents inconsistent marking of the log and trace entries. For inbound processing, the adapter ID property is located only in the resource adapter properties, so this consideration does not apply.
The data binding component, which converts between business objects and the native data formats in email text and attachments, does not use the adapter component ID when generating log and trace messages. Instead, it uses a string that indicates which data binding generated the message. Table 1 lists the component ID used by each adapter-specific data binding for WebSphere Adapter for Email. For custom data bindings, the data binding must set the component ID.
Component IDs for adapter-specific data bindings Data binding Component ID EmailSimpleDataBinding EMARASEDB EmailWrapperDataBinding EMARAEWDB EmailFixedStructureDataBinding EMARAFSDB See the Adapter ID (AdapterID) property.