One of the challenges for documenting or debugging a live production CA Identity Management solution with 100's or 1000's of business rules, across multiple J2EE nodes, is to identify the full data flow for a single transaction.
While out at a client site, I was able to observe a valuable additional, that could be harvested for the above use-case.
The ability to output the IM task session ID (UUID) to the IM J2EE debug logs for PX Rules.
Let me summarize the business logic options and the PX challenge:
Process followed to leverage this feature:
<BusinessLogicTaskHandler name="Task Session Attribute" description="">
Select the IM task(s) that you wish to monitor:
Copy and paste in the java script.
- Alternatively, you may export the IM environment out to XML, and use Notepad++ or other edit tool to search/replace this body of text; then re-import the XML to update the IM tasks.
Step 2b: Add in the Action Rule Actions.
- Example below testing the various messages actions to the VST and/or the J2EE logs.
Skip step 7: Will revise.
Task Session ID in PX Policy