Command line options are not available when you run the extract rule from the ruleform. Extract rules are intended to be run from command line. That said, you can use the pxExtractDataWithArgs activity available from 7.1.8 onward. Please refer to the BIX user guide - https://pdn.pega.com/documents/bix-71-user-guide
Note that when run via an agent, it will run in a background thread in the same JVM as the node where it has been scheduled to run. If run via a shell script, it spawns a new JVM (process) to extract the data. So the call is whether to load the current JVM with extra processing or to spawn a new one.
Extraction could be a heavy (resource intensive) process depending on how much data you are extracting.
Also, if you are using Pega Cloud, the pxExtractDataWithArgs is the only option to extract data.
'Extraction could be a heavy (resource intensive) process depending on how much data you are extracting'
Is the resource intensiveness on the application server or on the database. I assume on both. But what is the impact like in database and app server? Does simply adding resources (CPU and Memory, and storage) resolve it even if we are using agent to run pxExtractDataWithArgs? We do not have cloud but looking at the option to use the activity be run from an agent? Are there any other considerations?
Posted: 5 years ago
Updated: 5 years ago
Posted: 21 Feb 2016 5:52 EST Updated: 22 Feb 2016 0:38 EST
Typically the extract rule has only a subset of the properties that the work object (case) has. So depending on how big the BLOB is and how much data is extracted, that much processing is needed. Yes, it will have an effect on both database and application server. Please note that when you use this activity to run as an agent, it runs only on one node rather than all nodes connected to this DB (cluster).