5. Also the debug does NOT seem to be activated from the commandline, the log only shows debug messages when run from DevStudio.
The BIX log file shows successful execution from the DesignerStudio, no trace of my call from the Cmd (both Java and Ant), the PDF shows the trace of my Cmd call in the Extraction historty with "Could not process"
Question, I noted in Bootstrapping from the cmd is also quite expensive. As if we start up another PRPC node?, can we trim some of those routines that "MAY" not be needed for BIX to work?
Yes, BIX does start the entire engine. Your prconfig.xml file does not have some settings which reduce the start up time. Which version of BIX are you using? Are you using the prconfig.xml file which is part of the BIX distribution image (BIX can be found under the additional products folder of the Pega distribution image)
-i switch with the pzInsName of the Extract rule, but I cannot find, could this be pxInsName?
Yes, it is pxInsName. I will reach out to the documentation folks to get this corrected.
I came around this error, com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "wfe!BATCH" not found.
Again, are you using the BIX prconfig.xml file?
Also the debug does NOT seem to be activated from the commandline, the log only shows debug messages when run from DevStudio.
I noticed in the attached prlogging.xml file that all classes referring to the BIX appender are set to "info" and not "debug". Changing that should help.
That said, when you did run from the command line, BIX did not start up at all. I noticed that the text highlighted in the log file you provided is from import code and not from BIX. Did you provide the details from the PegaRULES log file or the PegaBIX log file? (I am referring to the PDF attached).
Question - HOW would this work then, if this option is not available when running an Extract rule on the cloud???
On the cloud the pxExtractDataWithArgs activity will be run by an agent. Each agent will have an Access Group set which specifies the context under which this activity will be executed. This will ensure that the right rule is picked.