| ILOG JRules User Guide > Deploying Rules > Reference > RuleApp Management Using Ant > res-write-db Task |
res-write-db Task |
PREVIOUS NEXT |
The res-write-db task adds a RuleApp archive to the database persistence of Rule Execution Server. This task does not notify any other Rule Execution Server component.
The following Ant task code provides an example of how to run the res-write-db task using the element attributes:
<res-write-db driver="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:oci:@//localhost:1521/default"
userid="bres" password="mypassword" file="myruleapp.jar">
<classpath>
<pathelement location="classes12.jar"/>
</classpath>
</res-write-db>
You can also run an encrypted res-write-db task using the credentialsfile attribute.
To run an encrypted res-write-db task, replace the following attributes:
userid="bres" password="mypassword"
with the attribute:
credentialsfile="mypasswordfile"
where credentialsfile is a text file that contains:
username=bres password=mypassword |
The file must follow the Java property files format. For more information, see http://java.sun.com/j2se/1.4.2/docs/api/java/util/Properties.html#load(java.io.InputStream). After the first execution of the res-deploy ANT task, the contents are encrypted. For example:
username={DES}oLHZROlruWw\= password={DES}als58ekruWw\= |
With encryption, the userid and password never appear in plain text in traces during the RuleApp deployment operation.
The following table describes the res-write-db element attributes and specifies whether or not they are required elements.
This classpath should contain the JDBC driver classes. Wherever path-like values need to be specified, you can use a nested element. This takes the general form of:
<classpath>
<pathelement path="${classpath}"/>
<pathelement location="lib/"/>
</classpath>
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |