Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Simply drop the servicemix-exec installer zip in an hotdeploy directory monitored by ServiceMix.

How it works

ServiceMix Exec service engine acts as a provider. It supports all MEP.

When used with an InOnly MEP, the Exec component executes the command and set the exchange in DONE status.

When used with an InOut MEP, the Exec components executes the command and get the command output buffer. The command output is put in the out message and send back in the exchange.

Exec in message format

Code Block
xml
xml

<message>
  <command>ls</command>
  <arguments>
    <argument>-l</argument>
    <argument>/tmp</argument>
  </arguments>
</message>
Note

If the in message doesn't contain the command tag, Exec component uses the command attribute provided in the xbean.xml. If no command is provided in the in message and in the xbean.xml, the component throws an exception and the exchange fails.

Exec out message format

When used with an InOut MEP, the Exec return the command execution output into the out message. The out message content looks like:

Code Block
xml
xml

<output>
total 6729
-rw------- 1 jb       jb   1693752 2009-04-09 09:07 f9G0lWzx.tar.part
-rw-r--r-- 1 jb       jb         8 2009-03-27 18:27 gnome-session-manager
srwxr-xr-x 1 jb       jb         0 2009-03-26 10:56 gnome-system-monitor.jb.3619273851
drwxr-xr-x 2 jb       jb      1024 2009-04-23 08:43 hsperfdata_jb
drwxr-xr-x 2 jboss    java    1024 2009-04-17 12:46 hsperfdata_jboss
drwxr-xr-x 2 weblogic java    1024 2009-04-17 09:40 hsperfdata_weblogic
-rw-r--r-- 1 jb       jb       870 2009-03-26 10:59 jbi12672.zip
-rw-r--r-- 1 jb       jb       870 2009-03-26 10:59 jbi12673.zip
</output>

Endpoint

The Exec endpoint can be very simple, waiting for command contained in the in message:

...