is their any way to debug the process in CA IT PAM?
Yes you can. In design mode, unarchive your process, select an operator, and click on the little hand with a green check mark beside it. Use the hand with the black X to remove the breakpoint!
Once your process is breakpoint suspended, you can click on any operator to take a look at its dataset.
If you want to take a look at your global variable (Process.yourVariable), just change the selection in the dropdown at the top of the DataSet section and select your process.
This post was made to the CA Automation community which is for the CA Server Automation product. Since you have identified this post as being related to CA Process Automation I have moved it to the CA Process Automation Community.
In our PAM processes, we're processing tens/hundreds/thousands of items in rapid succession. So, I'm unable to halt on each of them. In these cases, I use a method that some folks may find useful, as well.
If I'm looking to capture debug data from a very specific data set that is embedded within many others, I'll use the Send eMail operator, as follows:
The trigger is the (very specific) condition in which I want to capture the debug data.
I collect the debug data by adding some Pre-Execution Code to the Mail Operator that contains all of the data from the process that I want to debug.
Then, I send it to myself.
Note that this works great if you're looking for a proverbial 'needle in a haystack'.
It works miserably (and will probably crash your company's eMail server) if you're trying to capture thousands of sets of data.
You are absolutely right.
Let me propose an alternative method to receive debug info.
You may consider using the "write to file" operator instead of the email one. Log everything and at the end of the Process, Send one email containing the log file.
If you think the file maybe to big to send as an attachment, write directly on a network share and send the path to this file in an email!
I did not tried it, but i think that this is the cleanest way to get every debug info from "mega loop of death".
Option number 2, what i'm doing here. I log everything in a database, and use some SQLReport to read the data.
Fantastic ideas, both, POssq.
I intend to plagiarize both of them--extensively.
Have fun, you have my blessing
Retrieving data ...