CoRB is a Java tool designed for bulk content-reprocessing of documents stored in MarkLogic. CoRB stands for Content Reprocessing in Bulk and is a multi-threaded workhorse tool at your disposal. In a nutshell, CoRB works off a list of documents in a database and performs operations against those documents. CoRB operations can include generating a report across all documents, manipulating the individual documents, or a combination thereof.
This document and the wiki provide a comprehensive overview of CoRB and the options available to customize the execution of a CoRB job, as well as the ModuleExecutor Tool, which can be used to execute a single (XQuery or JavaScript) module in MarkLogic.
For additional information, refer to the CoRB Wiki.
Download the latest release directly from https://github.com/marklogic-community/corb2/releases or resolve dependencies through Maven Central.
- CoRB v2.4.0 (or later) requires Java 8 (or later) to run.
- CoRB v2.3.2 is the last release compatable with Java 7 and 6.
- CoRB v2.2.0 (or later) requires marklogic-xcc 8.0.* (or later) to run.
Note: marklogic-xcc 8 is backwards compatible to MarkLogic 5 and runs on Java 1.6 or later.
To get help with CoRB
- Post a question to Stack Overflow with the
markogicandcorbtags. - Submit issues or feature requests at https://github.com/marklogic-community/corb2/issues
The entry point is the main method in the com.marklogic.developer.corb.Manager class. CoRB requires the MarkLogic XCC JAR in the classpath,
preferably the version that corresponds to the MarkLogic server version, which can be downloaded from https://developer.marklogic.com/products/xcc.
Use Java 1.8 or later.
CoRB needs options specified through one or more of the following mechanisms:
- command-line parameters
- Java system properties ex:
-DXCC-CONNECTION-URI=xcc://user:password@localhost:8202 - As properties file in the class path specified using
-DOPTIONS-FILE=myjob.properties. Relative and full file system paths are also supported.
If specified in more than one place, a command line parameter takes precedence over a Java system property, which take precedence over a property from the OPTIONS-FILE properties file.
Note: Any or all of the properties can be specified as Java system properties or key value pairs in properties file.
Note: CoRB exit codes
0- successful,0- nothing to process (ref: EXIT-CODE-NO-URIS),1- initialization or connection error and2- execution error
Note: CoRB now supports Logging Job Metrics back to the MarkLogic database log and/or as document in the database.
| Option | Description |
|---|---|
| INIT-MODULE | An XQuery or JavaScript module which, if specified, will be invoked prior to URIS-MODULE. XQuery and JavaScript modules need to have .xqy and .sjs extensions respectively. |
| INIT-TASK | Java Task which, if specified, will be called prior to URIS-MODULE. This can be used addition to INIT-MODULE for custom implementations. |
| OPTIONS-FILE | A properties file containing any of the CoRB options. Relative and full file system paths are supported. |
| PROCESS-MODULE | XQuery or JavaScript to be executed in a batch for each URI from the URIS-MODULE or URIS-FILE. Module is expected to have at least one external or global variable with name URI. XQuery and JavaScript modules need to have .xqy and .sjs extensions respectively. If returning multiple values from a JavaScript module, values must be returned as Sequence. |
| PROCESS-TASK | Java Class that implements com.marklogic.developer.corb.Task or extends com.marklogic.developer.corb.AbstractTask. Typically, it can talk to PROCESS-MODULE and the do additional processing locally such save a returned value.
|
| PRE-BATCH-MODULE | An XQuery or JavaScript module which, if specified, will be run before batch processing starts. XQuery and JavaScript modules need to have .xqy and .sjs extensions respectively. |
| PRE-BATCH-TASK | Java Class that implements com.marklogic.developer.corb.Task or extends com.marklogic.developer.corb.AbstractTask. If PRE-BATCH-MODULE is also specified, the implementation is expected to invoke the XQuery and process the result if any. It can also be specified without PRE-BATCH-MODULE and an example of this is to add a static header to a report.
|
| POST-BATCH-MODULE | An XQuery or JavaScript module which, if specified, will be run after batch processing is completed. XQuery and JavaScript modules need to have .xqy and .sjs extensions respectively. |
| POST-BATCH-TASK | Java Class that implements com.marklogic.developer.corb.Task or extends com.marklogic.developer.corb.AbstractTask. If POST-BATCH-MODULE is also specified, the implementation is expected to invoke the XQuery and process the result if any. It can also be specified without POST-BATCH-MODULE and an example of this is to add static content to the bottom of the report.
|
| THREAD-COUNT | The number of worker threads. Default is 1. |
| URIS-MODULE | URI selector module written in XQuery or JavaScript. Expected to return a sequence containing the uris count, followed by all the uris. Optionally, it can also return an arbitrary string as a first item in this sequence - refer to URIS_BATCH_REF section below. XQuery and JavaScript modules need to have .xqy and .sjs extensions respectively. JavaScript modules must return a Sequence. |
| URIS-FILE | If defined instead of URIS-MODULE, URIs will be loaded from the file located on the client. There should only be one URI per line. This path may be relative or absolute. For example, a file containing a list of document identifiers can be used as a URIS-FILE and the PROCESS-MODULE can query for the document based on this document identifier. |
| XCC-CONNECTION-URI | Connection string to MarkLogic XDBC Server. Multiple connection strings can be specified with comma as a separator. |
| Option | Description |
|---|---|
| BATCH-SIZE | The number of URIs to be executed in single transform. Default is 1. If more than 1, PROCESS-MODULE will receive a delimited string as the $URI variable, which needs to be tokenized to get individual URIs. The default delimiter is ;, which can be overridden with the option BATCH-URI-DELIM described below. Sample code for transform: declare variable URI as xs:string external;let $all-uris := fn:tokenize($URI,";") |
| BATCH-URI-DELIM | Use if the default delimiter ';' cannot be used to join multiple URIS when BATCH-SIZE is greater than 1. Default is ;. |
| DECRYPTER | The class name of the options value dycrypter, which must implement com.marklogic.developer.corb.Decrypter. Encryptable options include XCC-CONNECTION-URI, XCC-USERNAME, XCC-PASSWORD, XCC-HOSTNAME, XCC-PORT, and XCC-DBNAME. |
| COLLECTION-NAME | Value of this parameter will be passed into the URIS-MODULE via external or global variable with the name URIS. |
| COMMAND | Pause, resume, and stop the execution of CoRB. Possible commands include: PAUSE, RESUME, and STOP. If the COMMAND-FILE is modified and either there is no COMMAND or an invalid value is specified, then execution will RESUME. |
| COMMAND-FILE | A properties file used to configure COMMAND and THREAD-COUNT while CoRB is running. For instance, to temporarily pause execution, or to lower the number of threads in order to throttle execution. |
| COMMAND-FILE-POLL-INTERVAL | The regular interval (seconds) in which the existence of the COMMAND-FILE is tested can be controlled by using this property. Default is 1. |
| CONNECTION-POLICY | Algorithm for balancing load across multiple hosts used by com.marklogic.developer.corb.DefaultContentSourcePool. Options include ROUND-ROBIN, RANDOM and LOAD. Default option is ROUND-ROBIN. LOAD option returns the ContentSource or Connection with least number of active sessions. |
| CONTENT-SOURCE-POOL | Class that implements com.marklogic.developer.corb.ContentSourcePool and used to manage ContentSource instances or connections. Default is com.marklogic.developer.corb.DefaultContentSourcePool. |
| CONTENT-SOURCE-RENEW | Boolean value indicating whether to periodically check to see if a ContentSource resolves to a different IP address and create a new ContentSource to add to the resource pool. This can help transparently deal with proxies that have dynamic pools of IP addresses. Default is true |
| CONTENT-SOURCE-RENEW-INTERVAL | The regular interval (seconds) in which to resolve ContentSource IP address and add to the pool. This can help when a DNS entry may return multiple IP addresses and help spread traffic among multiple endpoints. Default is 60 |
| DISK-QUEUE | Boolean value indicating whether the CoRB job should spill to disk when a maximum number of URIs have been loaded in memory, in order to control memory consumption and avoid Out of Memory exceptions for extremely large sets of URIs. |
| DISK-QUEUE-MAX-IN-MEMORY-SIZE | The maximum number of URIs to hold in memory before spilling over to disk. Default is 1000. |
| DISK-QUEUE-TEMP-DIR | The directory where the URIs queue can write to disk when the maximum in-memory items has been exceeded. If not specified then TEMP-DIR value will be used. If neither are specified, then the default behavior is to use java.io.tmpdir. |
| ERROR-FILE-NAME | Used when FAIL-ON-ERROR is false. If specified true, removes duplicates from the errored URIs along with error messages will be written to this file. Uses BATCH-URI-DELIM or default ';' to separate URI and error message. |
| EXIT-CODE-IGNORED-ERRORS | Returns this exit code when there were errors and FAIL-ON-ERROR=false. Default is 0. |
| EXIT-CODE-NO-URIS | Returns this exit code when there is nothing to process. Default is 0. |
| EXPORT_FILE_AS_ZIP | If true, PostBatchUpdateFileTask compresses the output file as a zip file. |
| EXPORT-FILE-BOTTOM-CONTENT | Used by com.marklogic.developer.corb.PostBatchUpdateFileTask to append content to EXPORT-FILE-NAME after batch process is complete. |
| EXPORT-FILE-DIR | Export directory parameter is used by com.marklogic.developer.corb.ExportBatchToFileTask or similar custom task implementations. Optional: Alternatively, EXPORT-FILE-NAME can be specified with a full path. |
| EXPORT-FILE-NAME | Shared file to write output of com.marklogic.developer.corb.ExportBatchToFileTask - should be a file name with our without full path.
|
| EXPORT-FILE-PART-EXT | The file extension for export files being processed. ex: .tmp - if specified, com.marklogic.developer.corb.PreBatchUpdateFileTask adds this temporary extension to the export file name to indicate EXPORT-FILE-NAME is being actively modified. To remove this temporary extension after EXPORT-FILE-NAME is complete, com.marklogic.developer.corb.PostBatchUpdateFileTask must be specified as POST-BATCH-TASK. |
| EXPORT-FILE-REQUIRE-PROCESS-MODULE | Boolean value indicating whether or not to require a PROCESS-MODULE when an Export*ToFile PROCESS-TASK is specified. This can help avoid confusion when the PROCESS-MODULE was accidentally not configured and no files are generated. Default is true |
| EXPORT-FILE-SORT | If ascending or descending, lines will be sorted. If |distinct is specified after the sort direction, duplicate lines from EXPORT-FILE-NAME will be removed. i.e. ascending|distinct or descending|distinct |
| EXPORT-FILE-SORT-COMPARATOR | A java class that must implement java.util.Comparator. If specified, CoRB will use this class for sorting in place of ascending or descending string comparator even if a value was specified for EXPORT-FILE-SORT. |
| EXPORT-FILE-TOP-CONTENT | Used by com.marklogic.developer.corb.PreBatchUpdateFileTask to insert content at the top of EXPORT-FILE-NAME before batch process starts. If it includes the string @URIS_BATCH_REF, it is replaced by the batch reference returned by URIS-MODULE. |
| EXPORT-FILE-URI-TO-PATH | Boolean value indicating whether to convert doc URI to a filepath. Default is true |
| FAIL-ON-ERROR | Boolean value indicating whether the CoRB job should fail and exit if a process module throws an error. Default is true. This option will not handle repeated connection failures. |
| INSTALL | Whether to install the Modules in the Modules database. Specify true or 1 for installation. Default is false. |
| LOADER-BASE64-ENCODE | Boolean option specifying whether the content loaded by FileUrisStreamingXMLLoader or FileUrisXMLLoader (with the option LOADER-USE-ENVELOPE=true) should be base64 encoded, or appended as the child of the /corb-loader/content element. Default is false. |
| LOADER-PATH | The path to the resource (file or folder) that will be the input source for a loader class that extends AbstractFileUrisLoader, such as FileUrisDirectoryLoader, FileUrisLoader, FileUrisStreamingXmlLoader, FileUrisXmlLoader, and FileUrisZipLoader |
| LOADER-SET-URIS-BATCH-REF | Boolean option indicating whether a file loader should set the URIS_BATCH_REF. Default is false. |
| LOADER-USE-ENVELOPE | Boolean value indicating whether FileUris loaders should use an XML envelope, in order to send file metadata in addition to the file content. |
| JOB-NAME | Name of the current Job. |
| JOB-SERVER-PORT | Optional port number to start a lightweight HTTP server which can be used to monitor, change the number of threads, and pause/resume the CoRB job. Port number must be a valid port(s) or a valid range of ports.
When a port is specified and available, the job server URL will be logged to the console with both the UI The metrics URL supports the following parameters:
|
| MAX-OPTS-FROM-MODULE | Maximum number of custom inputs from the URIS-MODULE to other modules. Default is 10. |
| METADATA | The variable name that needs to be defined in the server side query to use the metadata set by the URIS-LOADER. |
| METADATA-TO-PROCESS-MODULE | If this option is set to true, XML-METADATA is set as an external variable with name METADATA to PROCESS-MODULE as well. Default is false. |
| METRICS-COLLECTIONS | Adds the metrics document to the specified collection. |
| METRICS-DATABASE | Uses the value provided to save the metrics document to the specified Database. The XCC connection specified should have the following privilege http://marklogic.com/xdmp/privileges/xdmp-invoke |
| METRICS-LOG-LEVEL | String value indicating the log level that the CoRB job should use to log metrics to ML Server Error log. Possible values are none, emergency, alert, critical, error, warning, notice, info, config, debug, fine, finer, finest. Default is none, which means metrics are not logged. |
| METRICS-MODULE | XQuery or JavaScript to be executed at the end of the CoRB Job to save the metrics document to the database. There is an XQuery module (save-metrics.xqy) and a JavaScript module (saveMetrics.sjs) provided. You can use these modules as a template to customize the the metrics document saved to the database. XQuery and JavaScript modules need to have '{@code .xqy}' and{@code .sjs} extensions respectively. |
| METRICS-NUM-FAILED-TRANSACTIONS | Maximum number of failed transaction to be logged in the metrics. Default is 0. |
| METRICS-NUM-SLOW-TRANSACTIONS | Maximum number of slow transaction to be logged in the metrics. Default is 0. |
| METRICS-ROOT | Uses the value provided to as the URI Root for saving the metrics document. |
| METRICS-SYNC-FREQUENCY | Frequency (in seconds) at which the metrics document needs to be updated in the database. By default the metrics document is not periodically updated and is only written once at the end of the job. |
| MODULE-ROOT | Default is /. |
| MODULES-DATABASE | Uses the XCC-CONNECTION-URI if not provided; use 0 for file system. |
| NUM-TPS-FOR-ETC | Number of recent transactions per second (tps) values used to calculate estimated completion time (ETC). Default is 10. |
| POST-BATCH-MINIMUM-COUNT | The minimum number of results that must be returned for the POST-BATCH-MODULE or POST-BATCH-TASK to be executed. Default is 1. |
| PRE-POST-BATCH-ALWAYS-EXECUTE | Boolean value indicating whether the PRE_BATCH and POST_BATCH module or task should be executed without evaluating how many URIs were returned by the URI selector. |
| PRE-BATCH-MINIMUM-COUNT | The minimum number of results that must be returned for the PRE-BATCH-MODULE or PRE-BATCH-TASK to be executed. Default is 1. |
| QUERY-RETRY-LIMIT | Number of re-query attempts before giving up. Default is 2. |
| QUERY-RETRY-INTERVAL | Time interval, in seconds, between re-query attempts. Default is 20. |
| QUERY-RETRY-ERROR-CODES | A comma separated list of MarkLogic error codes for which a QueryException should be retried. |
| QUERY-RETRY-ERROR-MESSAGE | A comma separated list of values that if contained in an exception message a QueryException should be retried. |
| SSL-CONFIG-CLASS | A java class that must implement com.marklogic.developer.corb.SSLConfig. If not specified, CoRB defaults to com.marklogic.developer.corb.TrustAnyoneSSLConfig for xccs connections. |
| URIS-LOADER | Java class that implements com.marklogic.developer.corb.UrisLoader. A custom class to load URIs instead of built-in loaders for URIS-MODULE or URIS-FILE options. Example: com.marklogic.developer.corb.FileUrisXMLLoader |
| URIS-REDACTED | Optional boolean flag indicating whether URIs should be excluded from logging, console, and JobStats metrics. Default is false. |
| URIS-REPLACE-PATTERN | One or more replace patterns for URIs - Used by java to truncate the length of URIs on the client side, typically to reduce java heap size in very large batch jobs, as the CoRB java client holds all the URIS in memory while processing is in progress. If truncated, PROCESS-MODULE needs to reconstruct the URI before trying to do fn:doc() to fetch the document. Usage: URIS-REPLACE-PATTERN=pattern1,replace1,pattern2,replace2,...)Example: URIS-REPLACE-PATTERN=/com/marklogic/sample/,,.xml, - Replace /com/marklogic/sample/ and .xml with empty strings. So, CoRB client only needs to cache the id '1234' instead of the entire URI /com/marklogic/sample/1234.xml. In the transform PROCESS-MODULE, we need to do let $URI := fn:concat("/com/marklogic/sample/",$URI,".xml") |
| XCC-CONNECTION-RETRY-LIMIT | Number attempts to connect to ML before giving up. Default is 3. |
| XCC-CONNECTION-RETRY-INTERVAL | Time interval, in seconds, between retry attempts. Default is 60. |
| XCC-CONNECTION-HOST-RETRY-LIMIT | Number attempts to connect to ML before giving up on a host. If not specified, it defaults to XCC-CONNECTION-RETRY-LIMIT |
| XCC-DBNAME | (Optional) Name of the content database to execute against |
| XCC-HOSTNAME | Required if XCC-CONNECTION-URI is not specified. Multiple host can be specified with comma as a separator. |
| XCC-HTTPCOMPLIANT | Optional boolean flag to indicate whether to enable HTTP 1.1 compliance in XCC. If this option is set, the xcc.httpcompliant System property will be set. Default is true. |
| XCC-PASSWORD | Required if XCC-CONNECTION-URI is not specified. |
| XCC-PORT | Required if XCC-CONNECTION-URI is not specified. |
| XCC-PROTOCOL | (Optional) Used if XCC-CONNECTION-URI is not specified. The XCC scheme to use; either xcc or xccs. Default is xcc. |
| XCC-TIME-ZONE | The ID for the TimeZone that should be set on XCC RequestOption. When a value is specified, it is parsed using TimeZone.getTimeZone() and set on XCC RequestOption for each Task. Invalid ID values will produce the GMT TimeZone. If not specified, XCC uses the JVM default TimeZone. |
| XCC-URL-ENCODE-COMPONENTS | Indicate whether or not the XCC connection string components should be URL encoded. Possible values are always, never, and auto. Default is auto. |
| XCC-USERNAME | Required if XCC-CONNECTION-URI is not specified. |
| XML-FILE | In order to use this option a class com.marklogic.developer.corb.FileUrisXMLLoader has to be specified in the URIS-LOADER option. If defined instead of URIS-MODULE, XML nodes will be used as URIs from the file located on the client. The file path may be relative or absolute. Default processing will select all of the child elements of the document element (i.e. /*/*). The XML-NODE option can be specified with an XPath to address a different set of nodes. |
| XML-METADATA | An XPath to address the node that contains metadata portion of the XML. This must be different from the XML-NODE. The metadata is set as an external variable with name METADATA to PRE-BATCH-MODULE and POST-BATCH-MODULE and also PROCESS-MODULE if enabled by METADATA-TO-PROCESS-MODULE. |
| XML-NODE | An XPath to address the nodes to be returned in an XML-FILE by the com.marklogic.developer.corb.FileUrisXMLLoader. For example, a file containing a list of nodes wrapped by a parent element can be used as a XML-FILE and the PROCESS-MODULE can unquote the URI string as node to do further processing with the node. If not specified, the default behavior is to select the child elements of the document element (i.e. /*/*) |
| XML-SCHEMA | Path to a W3C XML Schema to be used by com.marklogic.developer.corb.FileUrisStreamingXMLLoader or com.marklogic.developer.corb.FileUrisXMLLoader to validate an XML-FILE, and used by com.marklogic.developer.corb.SchemaValidateBatchToFileTask and com.marklogic.corb.SchemaValidateToFileTask post-process tasks to validate documents returned from a process module. |
| XML-SCHEMA-HONOUR-ALL-SCHEMALOCATIONS | Boolean value indicating whether to set the feature http://apache.org/xml/features/honour-all-schemaLocations. Default is true |
| XML-TEMP-DIR | Temporary directory used by com.marklogic.developer.corb.FileUrisStreamingXMLLoader to store files extracted from the XML-FILE. If not specified, TEMP-DIR value will be used. If neither are specified, then the default Java temp directory will be used. |
If a module, including those specified by PRE-BATCH-MODULE, PROCESS-MODULE or POST-BATCH-MODULE have an external or global variable named URIS_BATCH_REF, the variable will be set to the first non-numeric item in the sequence returned by URIS-MODULE. This means that, when used, the URIS-MODULE must return a sequence with the special string value first, then the URI count, then the sequence of URIs to process.
As an example, a batch ref can be a link/id of a document that manages the status of the batch job, where pre-batch module updates the status to start and post-batch module can set it to complete. This example can be used to manage status and errors in automated batch jobs.
ExportBatchToFileTask, PreBatchUpdateFileTask and PostBatchUpdateFileTask use URIS_BATCH_REF as the file name if EXPORT-FILE-NAME is not specified. This is useful for automated jobs where name of the output file name can be determined only by the URIS-MODULE.
Total count of uris is set as an external variable to PRE-BATCH-MODULE and POST-BATCH-MODULE (since 2.4.5)
Any property specified with prefix (with '.') INIT-MODULE, URIS-MODULE, PRE-BATCH-MODULE, PROCESS-MODULE, POST-BATCH-MODULE will be set as an external variable in the corresponding XQuery module (if that variable is defined as an external string variable in XQuery module). For JavaScript modules the variables need be defined as global variables.
URIS-MODULE.maxLimit=1000Expects an external string variable maxLimit in URIS-MODULE XQuery or global variable for JavaScript.PROCESS-MODULE.startDate=2015-01-01Expects an external string variable startDate in PROCESS-MODULE XQuery or global variable for JavaScript.
Alternatively, URIS-MODULE can pass custom inputs to PRE-BATCH-MODULE, PROCESS-MODULE, POST-BATCH-MODULE by returning one or more of the property values in above format before the count the of URIs. If the URIS-MODULE needs URIS_BATCH_REF (above) as well, it needs to be just before the URIs count.
let $uris := cts:uris()
return ("PROCESS-MODULE.foo=bar", "POST-BATCH-MODULE.alpha=10", fn:count($uris), $uris)Appending |ADHOC to the name or path of a XQuery module (with .xqy extension) or JavaScript (with .sjs or .js extension) module will cause the module to be read from the file system and executed in MarkLogic without being uploaded to Modules database. This simplifies running CoRB jobs by not requiring deployment of any code to MarkLogic, and makes the set of CoRB files and configuration more self contained.
INIT-MODULE, URIS-MODULE, PROCESS-MODULE, PRE-BATCH-MODULE and POST-BATCH-MODULE can be specified adhoc by adding the suffix |ADHOC for XQuery or JavaScript (with .sjs or .js extension) at the end. Adhoc XQuery or JavaScript remains local to the CoRB and is not deployed to MarkLogic. The XQuery or JavaScript module should be in its named file and that file should be available on the file system, including being on the java classpath for CoRB.
PRE-BATCH-MODULE=adhoc-pre-batch.xqy|ADHOCadhoc-pre-batch.xqy must be on the classpath or in the current directory.PROCESS-MODULE=/path/to/file/adhoc-transform-module.xqy|ADHOCXQuery module file with full path in the file system.URIS-MODULE=adhoc-uris.sjs|ADHOCAdhoc JavaScript module in the classpath or current directory.
It is also possible to set a module option with inline code blocks, rather than a file path. This can be done by prepending either INLINE-XQUERY| or INLINE-JAVASCRIPT| to the option value, followed by the XQuery or JavaScript code to execute. Inline code blocks are executed as "adhoc" modules and are not uploaded to the Modules database. The |ADHOC suffix is optional for inline code blocks.
URIS-MODULE=INLINE-XQUERY|xquery version '1.0-ml'; let $uris := cts:uris('', 'document', cts:collection-query('foo')) return (count($uris), $uris)JavaScript modules are supported and can be used in place of an XQuery module. However, if returning multiple values (ex: URIS-MODULE), values must be returned as a Sequence. MarkLogic JavaScript API has helper functions to convert Arrays into Sequence (Sequence.from()) and inserting values into another Sequence (fn.insertBefore()).
JavaScript module must have an .sjs file extension when deployed to Modules database. However, adhoc JavaScript modules support both .sjs and .js file extensions.
For example, a simple URIS-MODULE may look like this:
let uris = cts.uris();
fn.insertBefore(uris, 0, fn.count(uris));To return URIS_BATCH_REF, we can do the following:
fn.insertBefore(fn.insertBefore(uris, 0, fn.count(uris)), 0, "batch-ref")Note: Do not use single quotes within (adhoc) JavaScript modules. If you must use a single quote, escape it with a quote (ex: ''text'')
It is often required to protect the database connection string or password from unauthorized access. So, CoRB optionally supports encryption of the entire XCC URL or any parts of the XCC URL (if individually specified), such as XCC-PASSWORD.
PrivateKeyDecrypter automatically detects if the text is encrypted. Unencrypted text or clear text is returned as-is. Although not required, encrypted text can be optionally enclosed with "ENC" ex: ENC(xxxxxx) to clearly indicate that it is encrypted.
Generate keys and encrypt XCC URL or password using one of the options below.
- Use the PrivateKeyDecrypter class inside the CoRB JAR with the gen-keys option to generate a key.
java -cp /path/to/lib/* com.marklogic.developer.corb.PrivateKeyDecrypter gen-keys /path/to/private.key /path/to/public.key RSA 1024
Note: if not specified, default algorithm: RSA, default key-length: 1024
- Use the PrivateKeyDecrypter class inside the CoRB JAR with the encrypt option to encrypt the clear text such as an xcc URL or password.
java -cp /path/to/lib/* com.marklogic.developer.corb.PrivateKeyDecrypter encrypt /path/to/public.key clearText RSA
Note: if not specified, default algorithm: RSA
openssl genrsa -out private.pem 1024Generate a private key in PEM formatopenssl pkcs8 -topk8 -nocrypt -in private.pem -out private.pkcs8.keyCreate a PRIVATE-KEY-FILE in PKCS8 standard for javaopenssl rsa -in private.pem -pubout > public.keyExtract public keyecho "uri or password" | openssl rsautl -encrypt -pubin -inkey public.key | base64Encrypt URI or password. Optionally, the encrypted text can be enclosed with "ENC" ex: ENC(xxxxxx)
ssh-keygenex:key as id_rsa after selecting a passphraseopenssl pkcs8 -topk8 -nocrypt -in id_rsa -out id_rsa.pkcs8.key(asks for passphrase)openssl rsa -in id_rsa -pubout > public.key(asks for passphrase)echo "password or uri" | openssl rsautl -encrypt -pubin -inkey public.key | base64
JasyptDecrypter automatically detects if the text is encrypted. Unencrypted text or clear text is returned as-is. Though, not required, encrypted text can be optionally enclosed with "ENC" ex: ENC(xxxxxx) to clearly indicate that it is encrypted.
Encrypt the URI or password as below. It is assumed that the jasypt distribution is available on your machine.
jasypt-1.9.2/bin/encrypt.sh input="uri or password" password="passphrase" algorithm="algorithm" (ex: PBEWithMD5AndTripleDES or PBEWithMD5AndDES)
jasypt.properties file
jasypt.algorithm=PBEWithMD5AndTripleDES #(If not specified, default is PBEWithMD5AndTripleDES)
jasypt.password=passphraseHostKeyDecrypter uses internal server identifiers to generate a private key unique to the host server. It then uses that private key as input to AES-258 encryption algorithm. Due to the use of AES-258, it requires JCE Unlimited Strength Jurisdiction Policy Files.
Note: certain server identifiers used may change in cases of driver installation or if underlying hardware changes. In such cases, passwords will need to be regenerated. Encrypted passwords will be always be unique to the server they are generated on.
Encrypt the password as follows:
java -cp /path/to/lib/* com.marklogic.developer.corb.HostKeyDecrypter encrypt clearText
To test if server is properly configured to use the HostKeyDecrypter:
java -cp /path/to/lib/* com.marklogic.developer.corb.HostKeyDecrypter test
CoRB provides support for SSL over XCC. As a prerequisite to enabling CoRB SSL support, the XDBC server must be configured to use SSL. It is necessary to specify XCC-CONNECTION-URI property with a protocol of 'xccs'. To configure a particular type of SSL configuration use the following property:
TrustAnyoneSSLConfig is the default implementation of the SSLContext. It will accept any certificate presented by the MarkLogic server.
TwoWaySSLConfig is more complete and configurable implementation of the SSLContext. It supports SSL with mutual authentication. It is configurable via the following properties:
CoRB 2.4+ supports load balancing and failover using com.marklogic.developer.corb.ContentSourcePool. This is automatically enabled when multiple comma separated values (supports encryption) are specified for for XCC-CONNECTION-URI or XCC-HOSTNAME.
XCC-CONNECTION-URI=xcc://hostname1:8000/dbname,xcc://hostname2:8000/dbname,..OR
XCC-HOST-NAME=hostname1,hostname2,..The default implementation for com.marklogic.developer.corb.ContentSourcePool is com.marklogic.developer.corb.DefaultContentSourcePool. It uses below options for CONNECTION-POLICY for allocating connections to callers.
- ROUND-ROBIN - (Default) Connections are allocated using round-robin algorithm.
- RANDOM - Connections are randomly allocated.
- LOAD - Host with least number of active connections is allocated to caller.
CoRB automatically retries the requests a given URI when it encounters com.marklogic.xcc.exceptions.ServerConnectionException from MarkLogic. If necessary, the number of retry attempts can be configured using XCC-CONNECTION-RETRY-LIMIT. If multiple hosts are specified, we can optionally configure retries per each host using XCC-CONNECTION-HOST-RETRY-LIMIT. CoRB waits at least XCC-CONNECTION-RETRY-INTERVAL seconds before a connection is retried on a failed host.
CoRB also supports retries of requests failed due to query errors. This feature is only intended for sporadic query errors which are not specific to a particular URI. A good example may include occasional time out exceptions from MarkLogic when the ML is too busy and request time limit is low. We can configure which queries can be retried using QUERY-RETRY-ERROR-CODES or QUERY-RETRY-ERROR-MESSAGE (when error codes are not available). If necessary, the number of query retry attempts can be configured using QUERY-RETRY-LIMIT. CoRB waits at least QUERY-RETRY-INTERVAL seconds before retrying a query.
QUERY-RETRY-ERROR-CODES=XDMP-EXTIME,SVC-EXTIME
QUERY-RETRY-ERROR-MESSAGE=ErrorMsg1,ErrorMsg2Refer to the wiki for examples of how to execute a CoRB job and various ways of configuring the job options.
Sometimes, a two or more staged CoRB job with both a selector and transform isn't necessary to get the job done. Sometimes, only a single query needs to be executed and the output captured to file. Maybe even to execute only a single query with no output captured. In these cases, the ModuleExecutor Tool can be used to quickly and efficiently execute your XQuery or JavaScript files.