ILOG JRules User Guide > Deploying Rules > Reference > RuleApp Management Using Ant > res-fetch-all Task

The res-fetch-all task downloads all RuleApp archives from Rule Execution Server using a HyperText Transfer Protocol (HTTP) or an HTTP Over SSL (HTTPS).

Table 8 res-fetch Element Attributes
Element Attribute 
Description 
Required 
destfile 
The destination where the RuleApp archive file will be stored. 
Yes 
portnumber 
The port number of the Rule Execution Server Console. 
Yes 
hostname 
The host name of the server where the Rule Execution Server Console is installed. 
Yes 
userid 
The user name to log in the Rule Execution Server Console. 
No 
password 
The password of the user that is allow to log in the Rule Execution Server Console. 
No 
credentialsfile 
A file containing the userid and password, encrypted when the attribute is first used. If this attribute is present, the userid and password attributes must not be used. 
No 
webapp 
The prefix of the Rule Execution Server Console. 
No, default value: bres 
failonerror 
The default is set to true. If it is set to false a warning message is logged when an error occurs, but the build is not stopped.  
No 
secured 
The default is set to false. If it is set to true the task performs an HTTPS upload. 
No 

The following Ant task code provides an example how to use the element attributes:

<res-fetch-all hostname="localhost" destfile="myruleapp.jar" portnumber="7001"
 userid="bres" password="mypassword"/>

Here is an encrypted example, using the credentialsfile attribute:

<res-fetch-all hostname="localhost" destfile="myruleapp.jar" portnumber="7001"
 credentialsfile="mypasswordfile"/>

where the credentials file 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.

Related Concepts

RuleApps and RuleApp Projects

Related Topics

Task Mappings
Rule Execution Server Tasks
res-jar Task
res-fetch Task
res-deploy
res-undeploy Task
res-write-file Task
res-write-db Task
res-delete-file Task
res-delete-db Task

Related Tasks

Deploying and Exporting RuleApps

Related Samples and Tutorials

Tutorial: RuleApp Management
How to Automate Ruleset Management
How to Migrate RuleApps

Related Reference

RuleApp Management Using MBeans Accessor API
http://ant.apache.org/