"Bash! SampleExtract Event not found" error occured while running BIX command line extraction

General
, , , ,
1

Summary: We are trying to execute BIX command line extraction and getting “Bash! SampleExtract Event not found” error.

Please find the configuration that we did before running BIX.

BIX rule output format is CSV. Rule is in production ruleset.

Operator ID that we are passing as a parameter has access to production ruleset.

  1. prbootstrap.properties- Uncommented below commented lines and add below details

com.pega.pegarules.bootstrap.allclasses.dbcpsource=xxx.oracle
xxx.oracle.url=“jdbc:oracle:thin:@//xxx:1529/xxx”
xxx.oracle.username=“xxx”
xxx.oracle.password=“xxxx”
oracle.jdbc.class=oracle.jdbc.OracleDriver

com.pega.pegarules.bootstrap.allclasses.schema=“XXX_XXXRULES”
com.pega.pegarules.bootstrap.datatables.schema="XXX_XXXDATA

  1. prconfig.xml- uncommented and add below details

We have executed below 2 command under "apps/pega722/additional_products/bix" folder and in both the case we are getting same error:

java -Xms512m -classpath “.;lib\prbootstrap.jar;lib\prdbcp.jar;lib\jsr94-1.0.jar;$CLASSPATH$” -Dcom.pega.pegarules.bootstrap.properties.url=config\prbootstrap.properties -Dpegarules.config=config\prconfig.xml -Dpegarules.logging.configuration=config\prloggging.xml -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -i ANTM-PS-PLM-WORK-LOB!TRANSACTIONEXTRACT

java -Xms512m -classpath “.;lib\prbootstrap.jar;lib\prdbcp.jar;lib\jsr94-1.0.jar;$CLASSPATH$” -Dcom.pega.pegarules.bootstrap.properties.url=“./config/prbootstrap.properties” -Dpegarules.config=“./config/prconfig.xml” -Dpegarules.logging.configuration=“./config/prloggging.xml” -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -i ANTM-PS-PLM-WORK-LOB!TRANSACTIONEXTRACT

Error:“Bash! Event not found”

2

Hello,

Are you sure this is a Pega issue? I can see articles on the net with that same error message due to some server configuration.

3

@MarcLasserre_GCS - This got resolved. Instead of running the BIX command manually, we are now executing bix.xml build file using below command

ant -buildfile bix.xml.

Thanks,

Ajay