Example Use Cases

While CORB has many options and is extensible even further, there are two typical uses for CORB: manipulating data, and generating a report.

As mentioned previously, the properties for CORB options can be set several ways:

• directly on the command line using main method argument positioning
• system properties, often set with –D commandline switches
• using the OPTIONS-FILE option to specify a properties file

If the same option is provided in multiple places, the order of precedence is: main arguments, system properties, and finally OPTIONS-FILE properties.

With so many ways to set properties, it is not reasonable to have an example in this section for every possibility. Therefore, this wiki provides one example using class arguments, one example using system properties arguments, and the rest using a properties file which could be considered a best practice.

Regardless of which approach is used, it will always be necessary to have the required jars on the classpath when executing CORB.

• CORB jar
• MarkLogic XML Contentbase Connector (XCC) jar

(optional) if encryption encryption is being used, then you will also need to have the Jayspt jar and jasypt.properties on the classpath.