CIB jsMerge can be called via CIB runshell as follows:

Cibrsh.exe <property1>=<value1> <property2>=<value2> -js [<inputfile name><outputfile name>]

Example 1:

Cibrsh.exe scriptfile=myScript.js licenseCompany=licensee licenseKey=xxxx-xxxxx-xxxxxxxx datafile=data.csv –js input.odt output.odt 

When calling via CIB runshell it is possible to insert "inputfile name" and "outputfile name" via property using prefix “inputfile=” and “outputfile=”:

Example 2:

Cibrsh.exe scriptfile=myScript.js licenseCompany=licensee licenseKey=xxxx-xxxxx-xxxxxxxx
datafile=data.csv inputfile=input.odt outputfile=output.odt –js

Notes:

The properties licenseCompany and licenseKey have to be set for every call.

Properties can be set directly in the CIB runshell call (command line) or in the script file. The following rules apply:

• If properties are set directly in the CIB runshell call, they by default take precedence over script file properties.
• If the properties set in the scriptfile should take effect, the override-parameter within the setProperty() command has to be set to "true".

Example:
For the CIB runshell call already shown above

Cibrsh.exe scriptfile=myScript.js licenseCompany=licensee licenseKey=xxxx-xxxxx-xxxxxxxx datafile=data.csv
inputfile=input.odt outputfile=output.odt –js 

The following is set in the script file "myScript":

setProperty("inputfile", "./differentInput.odt", true);
setProperty("outputfile", "differentOutput.odt", false);
setProperty("datafile", "test/differentData.csv");

In this example the input file "differentInput" from the script "myScript.js" is passed to CIB jsMerge because the override-parameter was set to "true". The property passed via the direct command line CIB runshell call is ignored in this case.

The outputfile "output.odt" and the data source "data.csv" are passed as specfified in the direct command line CIB runshell call because the properties’ override parameters set in the scriptfiles are either set to "false" or have no override-parameter set.