My prconfig.xml (without keyring as yet )

<?xml version="1.0" encoding="UTF-8"?>

<pegarules>

  <env name="identification/systemName" value="pega" />

  <env name="initialization/settingsource" value="merged" />

  <env name="fua/conclusionQueryPerformance" value="false" /> 

  <env name="initialization/minimalStartup" value="true" />

  <env name="ruleresolution/useclassancestorjoin" value="false" />

  <env name="ruleresolution/userulesetindexjoin" value="false" />

  <env name="ruleresolution/usejoinsforallclasses" value="false" />

  <env name="agent/enable" value="false" />

  <env name="fua/enableAssemblyAvoidance" value="false" />

  <env name="agent/masteragentenable" value="false" />

  <env name="initialization/daemonenable" value="false" />

  <env name="usage/usagetrackingenabled" value="false" />

  <env name="asyncservices/enable" value="false" />

  <env name="/compatibility/BIXUseOptimizedClipboardXML" value="true" />

  <env name="/compatibility/BIXdisableForwardChaining" value="true" />

  <env name="/compatibility/BIXdisableBackwardChaining" value="false" />

  <!-- This is a minimum format prconfig.xml file.  Only the settings which are required to access settings in the database are included.

  All other settings which were formerly located only in this file are now Data-Admin-System-Settings.      -->

  <env name="initialization/settingsource" value="merged" />

  <!-- seri: We still need these entries even if we do NOT bootstrap from Container Managed JNDI, ie using prdbcp.jar ??? -->

  <env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES"/>

  <env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaRULES"/>

  <!-- Most nodes have a 'default' classification and for these nodes, no additional changes need to be made to this file.  However,

  if this is node has a non-general purpose, for example: 'Agent', then the node classification setting should be added to this file. -->

  <!--env name="initialization/nodeclassification" value="Agent" /> -->

  <!--<env name="/Authentication/RedirectGuests" value="false"/>-->

  <!-- Settings can still be put in this file.  If they are, then the value in this file will override the value in the database

  for this node.  This is useful for settings which are specific to this node and should not be shared by multiple nodes on this

  system. -->

  <!--

  Pegasystems recommends that you use Application Server connection pooling to the database for Websphere and

  Weblogic.  These examples are provided if you need to use Pega Connection Pooling for Tomcat or for testing purposes.

  If you are using Application server connection pooling, there is no longer a need to edit this file.

  ****The new format for this file is only valid if you are using Application Server connection pooling. If you are not, please replace

  this file with an older version. ***

  Oracle 10g (Type 4) oracle.jdbc.OracleDriver                jdbc:oracle:thin:@serverName:1521:db

  IBM DB/2 Type 4     com.ibm.db2.jcc.DB2Driver               jdbc:db2://serverName:port/dbName

  SQL Server 2005     com.microsoft.sqlserver.jdbc.SQLServerDriver jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false

  -->

  <!--<env name="database/drivers" value="com.microsoft.sqlserver.jdbc.SQLServerDriver;oracle.jdbc.OracleDriver" />-->

  <env name="database/drivers" value="org.postgresql.Driver" />

  <!--<env name="database/databases/PegaRULES/url" value="jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false" /> -->

  <env name="database/databases/PegaRULES/url" value="jdbc:postgresql://localhost:5436/pega" />

  <env name="database/databases/PegaRULES/userName" value="pega" />

  <env name="database/databases/PegaRULES/password" value="pega" />

  <!--<env name="database/databases/PegaDATA/url" value="jdbc:sqlserver://serverName:1433;SelectMethod=cursor;SendStringParametersAsUnicode=false" /> -->

  <env name="database/databases/PegaDATA/url" value="jdbc:postgresql://localhost:5436/pega" />

  <env name="database/databases/PegaDATA/userName" value="pega" />

  <env name="database/databases/PegaDATA/password" value="pega" />

  <env name="database/databases/PegaRULES/defaultSchema" value="personaledition"/>

  <env name="database/databases/PegaDATA/defaultSchema" value="personaledition"/>

  <env name="compatibility/BIXUseOptimizedClipboardXML" value="true" />

  <env name="compatibility/BIXUseOptimizedClipboardXML" value="true" />

  <env name="compatibility/BIXdisableForwardChaining" value="true" />

  <env name="bix/useHistoryClasses" value="true" />

</pegarules>

//-------------------------

OK, I need to put -a aesdeveloper -p password to get it working.

<?xml version="1.0" encoding="UTF-8" ?>

<project name="BixAnt" default="BixAntTest1" >

<target name="BixAntTest1" >

<!--

-i <InstanceName> Specify the pzInsName of the Rule-Admin-Extract or a comma-delimited list of Rule-Admin-Extract instances.

Note: This option is not available when running an Extract rule on the cloud.

-I <path and filename that you view XML and download the file> Use an Extract rule specified in an external file in XML format.

-->

  <property name="ArgLine_Rule-Admin-Extract_pzInsName" value="SCO1-MYAPP1-WORK-MYAPP1CASE1!MYAPP1BIXCSV3" />

  <property name="ArgLine_XMLFile" value="c:/temp2/bixtest/extspec/SCO1-MYAPP1-WORK-MYAPP1CASE1!MYAPP1BIXCSV3.xml" />

  <echo message="SCO1-MYAPP1-WORK-MYAPP1CASE1!MYAPP1BIXCSV Export!" />

  <condition property="java.version" value="7" >

  <matches string="${java.version}" pattern="1.7.*" />

  </condition>

  <echo message="using java version ${java.version}" />

  <java classname="com.pega.pegarules.pub.PegaRULES" failonerror="true" fork="true" >

  <classpath>

  <fileset dir="./MyCipher/WEB-INF/lib" >

  <include name="*.jar" />

  </fileset>

  <pathelement path="./MyCipher/WEB-INF/lib" />

  <pathelement path="${java.class.path}" />

  </classpath>

  <jvmarg value="-Xms128m" />

  <jvmarg value="-Xmx512m" />

  <!--<jvmarg value="-verbose" />-->

  <jvmarg value="-Dcom.pega.pegarules.bootstrap.ignorejndi=true" />

  <jvmarg value="-Dcom.pega.pegarules.bootstrap.properties.url=file:///C:/PRPC/AES/BIXCmd/PRPCCrypto/MyCipher/WEB-INF/classes/prbootstrap.properties" />

  <jvmarg value="-Dpegarules.configuration=MyCipher/WEB-INF/classes/prconfig.xml" />

  <jvmarg value="-Dpegarules.logging.configuration=MyCipher/WEB-INF/classes/prlogging.xml" />

  <arg value="com.pega.pegarules.data.internal.access.ExtractImpl" />

  <arg line="-i"/>

  <arg value="${ArgLine_Rule-Admin-Extract_pzInsName}" />

  <arg line="-a"/>

  <arg value="aesdeveloper" />

  <arg line="-p"/>

  <arg value="password" />

  </java>

</target>

</project>

//------------------ OR ---------------

echo "Seri Start"

java.exe -classpath "./MyCipher/WEB-INF/lib/prbootstrap.jar;./MyCipher/WEB-INF/lib/prbootstrap-api.jar;./MyCipher/WEB-INF/lib/prbootstrap.jar;./MyCipher/WEB-INF/lib/prdbcp.jar;./MyCipher/WEB-INF/lib/postgresql-9.2-1002.jdbc4.jar" -Xms128m -Xmx256m -Dcom.pega.pegarules.bootstrap.properties.url="file:///C:/PRPC/AES/BIXCmd/PRPCCrypto/MyCipher/WEB-INF/classes/prbootstrap.properties" -Dpegarules.config=./MyCipher/WEB-INF/classes/prconfig.xml -Dpegarules.logging.configuration=./MyCipher/WEB-INF/classes/prlogging.xml -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES  com.pega.pegarules.data.internal.access.ExtractImpl -i PEGAAES-WORK-ACTION!SAMPLE -a aesdeveloper -p password

echo "Seri End"

//------------------------------------

Question - HOW would this work then, if this option is not available when running an Extract rule on the cloud???

Cheers

Seri