General Notes About Tracing Adapters

When you enable tracing for an adapter, you must identify the methods that you want to trace by typing:

com.waveset.adapter.sample.MyResourceAdapter

You must also provide calls to create log entries for any new methods in your custom resource adapter so the adapter can write its resource settings to a log file.

In some cases, you can specify additional logging parameters for the resource instance, such as:

• Maximum Log Archives

• Maximum Active Log Age

• Log File Path

• Maximum Log File Size

• Log Level

• To further debug the synchronization process, you can configure synchronization logging for an Active Sync adapter. Instructions are provided in the Waveset online help.

• Tracing custom Java code can be useful when you are writing your own resource adapter. See Tracing Custom Code for more information.

• You can instrument code with trace points to help assess and resolve problems more effectively. See Instrumenting Code with Trace Points for more information.

• For more information about tracing specific adapter methods, see the Oracle Waveset 8.1.1 Resources Reference.

• The following tasks were moved from the adapter to the task package in Identity Manager version 8.0. You must update the paths if you have tracing enabled for any of these tasks, or if you have customized task definitions referencing these packages.

  Old Package Name	New Package Name
  com.waveset.adapter.ADSyncFailoverTask	com.waveset.task.ADSyncFailoverTask
  com.waveset.adapter.ADSyncRecoveryCollectorTask	com.waveset.task.ADSyncRecoveryCollectorTask
  com.waveset.adapter.SARunner	com.waveset.task.SARunner
  com.waveset.adapter.SourceAdapterTask	com.waveset.task.SourceAdapterTask