The XSLT service consumes messages from the given source queue (or wildcard), processes their content with a profidex XSLT file, and sends the results to the given destination queue. Physically, the it is an executable jar file that can be configured via system properties or environment variables.
The XSLT service is just an executable jar, the jar artifact for this module is executable. Configuration is provided by using environment variables, or system properties (it doesn't matter which). For example,
export xslt.file=/path/to/transform.xsl
java -jar target/rmap-loader-transform-xsl-0.0.1-SNAPSHOT.jar -Djms.queue.dest="rmap.harvest.disco.transformed.ACM.2015-04012"
ActiveMQ broker URL. Default is tcp://localhost:61616
JMS username. Leave undefined if authentication is not used.
JMS password. Leave undefined if authentication is not used.
Destination JMS queue to send transformed records to. Default is rmap.harvest.disco.transformed.
Source JMS queue (or wild card) to look for records to transform. Default is rmap.harvest.xml.>.
Maximum number of JMS connections. Default is 10.
File path to the xslt file to use for the transform.
Any environment variable or system propertu that begins with LOG. can be used to specify the logging level of
the logger whose name appears after the LOG. characters. For example, setting the environment variable:
LOG.info.rmapproject=DEBUG
This will set the logger called info.rmapproject to the DEBUG level.