Oracle Waveset 8.1.1 System Administrator's Guide

Tracing Reconciliation

If you are having problems with a reconciliation task, you can use the standard tracing facility on com.waveset.task.Reconciler to trace the Reconciler.

Use either of the following methods to enable tracing:

You can also enable tracing from the System Settings page and trace the following reconciliation methods, at the Method/Class trace Levels noted, to view useful debugging information.

Table 5–4 Reconciliation Methods/Classes to Trace

Trace this com.waveset.recon.Method/Class

At this Trace Level 

To See 

ReconTask$WorkerThread#reconcileAccount

The individual account being reconciled 

ReconTask$WorkerThread#performResponse

The individual account and user during response 

ReconUtil#deleteAccountIndex

User information to be deleted from the account index 

UserContext#aquireRepoLock

The user who is being locked for update 

UserContext#releaseRepoLock

The user who is being unlocked in the repository 

ReconUtil#deleteAccountIndex

User information to be deleted from the account index 

UserContext#aquireRepoLock

The user who is being locked for update 

ReconTask$WorkerThread#failUserExamination

All user examination requests that failed with the error 

ReconTask$WorkerThread#failUserResponses

All user response requests that failed with the error 

UserContext#releaseRepoLock

The user who is being unlocked in the repository 

ReconTask$ResourceThread#examineResource

How many accounts read from the resource 

ReconTask$ResourceThread#queueAccountReconciles

Information about each account read from the resource such as accountId, accountGUID, accountDisabled

ReconTask$ResourceThread#examineLighthouse

How many Waveset users claim to own an account on the reconciled resource queued 

ReconTask$WorkerThread#findClaimants

All Waveset users who claim to have an account on the resource 

ReconTask$WorkerThread#confirmPossibleOwners

A list of all confirmed owners of resource accounts 

ReconTask$WorkerThread#applyResponse

The response list that is being applied 

AccountContext#processAttributeWorkflow

The attribute changes and the formatted changes during the launch of the attribute change workflow 

ReconUtil#getRuleState

Full User view with the user’s attribute during rule processing 

ReconUtil#evaluateCorrelationRule

The value of the correlation rule state and result for examination 

ReconUtil#confirmPotentialOwners

A list of users who have been confirmed using the confirmation rule 

ReconUtil#getIfExistsAccountIndexEntry

To output info related to examination of the account index for a specified entry 

ReconUtil#launchWorkflow

The task instance and task definition information when launched 

ReconUtil#indexFoundAccount

The account and situation recorded during a create or update of the index for an account known to exist 

ReconUtil#indexMissingAccount

The account and situation recorded during a create or update of the index for an account NOT known to exist 

ReconUtil#listAccountsIndexSaysExist

Account information that the index says exists 

ReconTask$ResourceThreadwaitForLighthouseWorkItems#

How many users queued and processed during the Waveset user examination process 

ReconTask$ResourceThread#waitForReconcileWorkItems

How many reconciles and responses queued and processed for the specified resource 

ReconTask$WorkerThread#correlateUsers

A list of correlated/confirmed users 

ReconTask$WorkerThread#respondOrRequeue

The error message if there is a problem performing the previous response method for an account 

Response#perform

The user, response, and the user’s resource info XML before and after the modifications took place 

Response#perform

A summary of the response action on the user 

Response#createNewUserFromAccount

Full details of the response action on the user 

ReconUtil#evaluateConfirmationRule

The value of the confirmation rule state and result for examination 

ReconUtil#getCorrelatedUsers

A list of correlated users matching the specified rule result 


Note –

Remember, the higher the tracing level, the larger the trace file. Also tracing all of these methods at the same time will create a very large trace file.

When you are finished troubleshooting, remember to disable tracing by setting the exception.trace key value back to false.