To schedule an extract from within the Designer Studio, modify the RunExtract agent that is in the Pega-BIX ruleset to periodically invoke the pxExtractDataWithArgs activity to run a BIX Extract rule. This activity takes as arguments the class and name of the Extract rule to run and, as a single string, the list of BIX command-line parameters desired for each run. The agent must only be enabled on the dedicated node for BIX processing to help avoid any negative performance impacts to production while the Extract rule is running.
The agent/threadpoolsize
setting in the prconfig.xml file controls the number of threads available in the agent pool, and consequently, the number of agents that can be run concurrently. If you schedule more agents to run concurrently than the value of the agent/threadpoolsize
setting, you might get a stale thread error. Increase the value of the agent/threadpoolsize
setting. The default value of the agent/threadpoolsize
setting is 5 and the maximum value is 10.
Agents in standard mode that do not have queue items created for them will appear to have run, but the activity is not executed.
If you are using an agent that calls pxExtractDataWithArgs, place quotes around the values. The extract fails if you do not use quotes. For example:
z "TEST-TESTAPP-WORK G-12" -Z "TEST-TESTAPP-WORK G-12"
If you are using an agent that calls a wrapper activity that calls pxExtractDataWithArgs, place quotes around the values and around the entire parameter string. Use the backslash to escape the quotes around the values. For example:
"z \"TEST-TESTAPP-WORK G-12" -Z \"TEST-TESTAPP-WORK G-12\""
The -i, -a, -p, -T, and -P command-line parameters are not supported for pxExtractDataWithArgs. The -X, -b, and -f command-line parameters cannot be used if pxExtractDataWithArgs is used on a Pega Cloud instance.
See Optional command-line BIX parameters and Agents rules.
This functionality is available when you purchase and install the BIX application.