Hi - I have a query related to database cleanup workflow, which is OOTB workflow with Adobe Campaign v6/v7. I understand it executes below command via nlserver module.
cleanup -instance:<%= instanceName %>
1) How is this instanceName defined - is it via the configuration xmls ?
2) How can we get the information about some source code of cleanup command, as in any location/script which will give us an idea which all SQLs will be executed in what sequence they are formed etc via cleanup command ?
I have found the actual problem for which I was looking for details around this cleanup workflow.
Basically, the workflow in our instance used to fail regularly without any details in the logs (xtkworkflowlog). Finally we identified that the session which insert data in xtkworkflowlog table has been timed out. We have DB idle time out setting as 30 mins, now hypothesis what I have build is that the session which writes data in logs (xtkworkflowlog) is waiting for response from actual workflow task, which if has been running for more than 30 min then due to inactivity - it may be getting idle and thus getting timed out. So when the activity gets completed it gives response to the primary session which was already timed out and thus workflow fails.
So I wanted to understand how wfserver manages the session, I could not find any documentation and would be helpful if someone can help with it.
The instanceName is an internal personalisation code that is inbuilt into product.
Also the cleanup module is all a blackbox, you cannot tab into the code. If you wish to have a read of the SQLs it is firing dedicated to your instance, please go to command line of the server and type following command
Thanks Vipul, yes have tried that command line option already and instead of wdbc, I had used * option with a tracefile . The reason I wanted to tab into code was to understand how it generates & submits SQLs. Is it a case that once the cleanup is fired, it will connect to Database and will continue to execute all the SQL's or it will do it via multiple session or so