Let’s take a look at some of the features that are available in the Adapter; today we’re going focus on scripting language support.
For a while now (since 2.7.0) you’ve been able to embed a script (using any JSR223 scripting language) as part of a service. You can either use EmbeddedScriptingService (where the script is inline in the XML) or ScriptingService (where you refer to the filename containing the script).
Using a script as part of your workflow is a very powerful tool during integration; sometimes it is very hard to declaratively configure everything the business requires in XML. Let’s never fall into the trap of thinking XML is a programming language.
Anyway, using a scripting language like ruby (as implemented by via JRuby) you can do as much (or as little as you like) to the message as it passes through the workflow. Accessing metadata, and subsequently deleting the file the metadata value refers to; randomly generating some data, you’re just limited by your familiarity with the scripting language.
Let’s look at an example; first of all you’ll need to download the jruby binary from [http://www.jruby.org]. Put the jar in to the adapter-lib directory and then, we’ll just insert this service into our workflow.
Here we’re just adding 2 items of metadata, messageType and documentReference, randomly generated. This is a pretty powerful way of generating test data within the adapter and checking behaviour.
If you do end up going down the road of using jruby, then just make sure to start the adapter with
-Dorg.jruby.embed.localcontext.scope=threadsafe if you’re using jruby in more than 1 workflow