Question

2
Replies
230
Views
BalajiS6010 Member since 2018 4 posts
Victaulic
Posted: 1 year ago
Last activity: 1 year 5 months ago
Closed
Solved

Running multiple extracts using BIX command line

Am trying to run BIX extraction standalone..

Below command worked perfectly fine by supplying InsName of the extract rule.

java -XX:+HeapDumpOnOutOfMemoryError -Xms768m -Xmx2048m -Dcom.pega.pegarules.bootstrap.properties.url=config\prbootstrap.properties -Dpegarules.config=config\prconfig.xml -Dpegarules.logging.configuration=config\prlog4j2.xml -Dpega.logdir=D:\MyOrgBIX\logs -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -a balajisri -p mypassword -g "20190507T040000.000 GMT" -G "20190514T040000.000 GMT" -P %tempfldr%\ -i DATA-WORKATTACH-NOTE!CMD_EXTRACT_NOTES

However I need to run multiple extracts using the same JVM. Is there a way to supply multiple extracts to above command? Any suggestions?

I tried below options a & b, but it does NOT accept.

Option a:

java -XX:+HeapDumpOnOutOfMemoryError -Xms768m -Xmx2048m -Dcom.pega.pegarules.bootstrap.properties.url=config\prbootstrap.properties -Dpegarules.config=config\prconfig.xml -Dpegarules.logging.configuration=config\prlog4j2.xml -Dpega.logdir=D:\MyOrgBIX\logs -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -a balajisri -p mypassword -g "20190507T040000.000 GMT" -G "20190514T040000.000 GMT" -P %tempfldr%\ -i PEGASOCIAL-MESSAGE!CMD_EXTRACT_INTERACTION_NOTES, com.pega.pegarules.data.internal.access.ExtractImpl -a balajisri -p Pega0818@Aug -g "20190507T040000.000 GMT" -G "20190514T040000.000 GMT" -P %tempfldr%\ -i DATA-WORKATTACH-NOTE!CMD_EXTRACT_NOTES

nor below

Option b:

java -XX:+HeapDumpOnOutOfMemoryError -Xms768m -Xmx2048m -Dcom.pega.pegarules.bootstrap.properties.url=config\prbootstrap.properties -Dpegarules.config=config\prconfig.xml -Dpegarules.logging.configuration=config\prlog4j2.xml -Dpega.logdir=D:\MyOrgBIX\logs -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -a balajisri -p mypassword -g "20190507T040000.000 GMT" -G "20190514T040000.000 GMT" -P %tempfldr%\ -i PEGASOCIAL-MESSAGE!CMD_EXTRACT_INTERACTION_NOTES, DATA-WORKATTACH-NOTE!CMD_EXTRACT_NOTES

In BIX log, I see below :

2019-05-13 16:05:10,194 [ us-hq-ps-app-d] [ ] [ ] ( internal.access.ExtractImpl) INFO - Usage: com.pega.pegarules.data.internal.access.ExtractImpl
where
-i <InstanceName> Comma delimited list of Rule-Admin-Extract Instances to include
You may specify a range of pzInsKey or pxCreateDateTime properties,
if you provide both, only the pzInsKey range will be used.
-z <start key> Only instances with a pzInsKey equal to or greater than <start key>
-Z <end key> Only instances with a pzInsKey equal to or less than <end key>
-d <start date> Only instances with a pxCreateDateTime equal to or greater than <start date>
-D <end date> Only instances with a pxCreateDateTime equal to or less than <end date>
-u <start date> Only instances with a pxUpdateDateTime equal to or greater than <start date>
-U <end date> Only instances with a pxUpdateDateTime equal to or less than <end date>
-X <Schema file Path> Generate only a set schema file for the export - NO DATA EXPORTED
-k <Identifier for this run. Must be alphanumeric> Add a unique identifer for this run of extractImpl
You may also indicate how many SQL updates done before issuing a database commit.
The default is 100.
-b <number of updates before a batch is issued>
You may also use multiple threads (this will only work if you specify more than one class)
-a <username> To rule resolve Rule-Admin-Extract instances
-p <password> To rule resolve Rule-Admin-Extract instances
-t <number of threads>
-c Include children classes
-f Include this option to force an extract to terminate at the first error.
Otherwise, extraction continues with errors (errors are written to the BIX log)
-l <delimiter>Delimiter character for CSV output
-xInclude header and footer information for XML/CSV output
-o Do a boolean OR between the create (-d/-D) and update (-u/U) timestamps
-n Do not sort the instances based on the instance key prior to extraction
-TTo Specify tenant name in MultiTenant Environment
Warning: In case of any error, BIX cannot be restarted based on the last instance key printed in the log
***Edited by Moderator: Pallavi to update platform capability tags***
Data Integration Reporting
Moderation Team has archived post
Share this page LinkedIn