In addition to the supplied Java filters, Tungsten Replicator also includes support for custom script-based filters written in JavaScript and supported through the JavaScript filter. This filter provides a JavaScript environment that exposes the transaction information as it is processed internally through an object-based JavaScript API.

The JavaScript implementation is provided through the Rhino open-source implementation. Rhino provides a direct interface between the underlying Java classes used to implement the replicator code and a full JavaScript environment. This enables scripts to be developed that have access to the replicator constructs and data structures, and allows information to be updated, reformatted, combined, extracted and reconstructed.

At the simplest level, this allows for operations such as database renames and filtering. More complex solutions allow for modification of the individual data, such as removing nulls, bad dates, and duplication of information.

To enable a JavaScript filter that has not already been configured, the static properties file (static-SERVICE.properties) must be edited to include the definition of the filter using the JavaScriptFilter class, using the script property to define the location of the actual JavaScript file containing the filter definition. For example, the supplied ansiquotes filter is defined as follows:

replicator.filter.ansiquotes=com.continuent.tungsten.replicator.filter.JavaScriptFilter
replicator.filter.ansiquotes.script=${replicator.home.dir}/samples/extensions/javascript/ansiquotes.js

To use the filter, add the filter name, ansiquotes in the above example, to the required stage:

replicator.stage.q-to-dbms.filters=mysqlsessions,pkey,bidiSlave,ansiquotes

Then restart the replicator to enable the configuration:

shell> replicator restart

If there is a problem with the JavaScript filter during restart, the replicator will be placed into the OFFLINE state and the reason for the error will be provided within the replicator trepsvc.log log.