<html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Brutex XServices Documentation</title><link href="corpstyle.css" type="text/css" rel="stylesheet"><meta content="DocBook XSL-NS Stylesheets V1.76.1" name="generator"><meta name="description" content="Abstract In complex IT environments it is necessary to integrate different information systems with each other, exchange data between tools and automate actions and function calls depending on events arising from user interaction. To meet the requirements of integration building usually means to implement APIs and to create tool-to-tool bridges. Web Services can help to clean up bridges into interfaces as well as to abstract functions from their underlying platform and implementation. These are the major goals of the loosely coupled integration strategy which is in turn one essential idea of a service-oriented architecture (SOA). provide a low level set of functions and web services. These can be orchestrated into services and used in business processes which make up the execution part of a SOA environment. is an add-on to XBridgeNG 2.0. It runs standalone or in combination with XBridgeNG. Pure XBridgeNG has two components: XML Schema for item based data types (e.g. tickets from a bug tracker system or a database record)Set of Apache Ant tasks to function as a bridge between the XBridgeNG XML format at legacy 3rd party software (e.g. HP Quality Center, Serena TeamTrack, ...)The add Web Services (SOAP) wrapper around Apache Ant tasks (since XBridgeNG 2.0) The current focus is on file-based operations. do not contain an integration server or a process execution engine."><link rel="home" href="index.html" title="Brutex XServices Documentation"><link rel="next" href="installation.html" title="Chapter 1. Getting started"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Brutex XServices Documentation</th></tr><tr><td align="left" width="20%"> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="installation.html">Next</a></td></tr></table><hr></div><div class="breadcrumbs"><span class="breadcrumb-node">Brutex XServices Documentation</span></div><div class="book" title="Brutex XServices Documentation"><div class="titlepage"><div><div><h1 class="title"><a name="N10001"></a>Brutex XServices Documentation</h1></div><div><div class="author"><h3 class="author"><span class="firstname">Brian</span> <span class="surname">Rosenberger</span></h3><code class="email"><<a class="email" href="mailto:bru@brutex.de">bru@brutex.de</a>></code></div></div><div><p class="copyright">Copyright © 2011 </p></div><div><div class="legalnotice" title="Legal Notice"><a name="N10017"></a><p> The copyright holders make no representation about the suitability of this document for any purpose. It is provided <span class="quote">“<span class="quote">as is</span>”</span> without expressed or implied warranty. </p></div></div><div><div class="legalnotice" title="Legal Notice"><a name="N1001D"></a><p>Apache Tomcat and Apache Ant are trademarks of the Apache Software Foundation.</p></div></div><div><div class="abstract" title="Abstract"><p class="title"><b>Abstract</b></p><p>In complex IT environments it is necessary to integrate different information systems with each other, exchange data between tools and automate actions and function calls depending on events arising from user interaction. To meet the requirements of integration building usually means to implement APIs and to create tool-to-tool bridges. Web Services can help to clean up bridges into interfaces as well as to abstract functions from their underlying platform and implementation.</p><p>These are the major goals of the loosely coupled integration strategy which is in turn one essential idea of a service-oriented architecture (SOA).</p><p>provide a low level set of functions and web services. These can be orchestrated into services and used in business processes which make up the execution part of a SOA environment.</p><p>is an add-on to XBridgeNG 2.0. It runs standalone or in combination with XBridgeNG. Pure XBridgeNG has two components:</p><p> </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>XML Schema for item based data types (e.g. tickets from a bug tracker system or a database record)</p></li><li class="listitem"><p>Set of Apache Ant tasks to function as a bridge between the XBridgeNG XML format at legacy 3rd party software (e.g. HP Quality Center, Serena TeamTrack, ...)</p></li><li class="listitem"><p>The add Web Services (SOAP) wrapper around Apache Ant tasks (since XBridgeNG 2.0)</p></li></ul></div><p> </p><p>The current focus is on file-based operations. do not contain an integration server or a process execution engine.</p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="installation.html">1. Getting started</a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#N10042"></a></span></dt><dd><dl><dt><span class="section"><a href="installation.html#N10048">Installation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="services.html">2. Available Services</a></span></dt><dd><dl><dt><span class="section"><a href="services.html#archiveservices">ArchiveServices</a></span></dt><dt><span class="section"><a href="executeservices.html">ExecuteServices</a></span></dt><dd><dl><dt><span class="section"><a href="executeservices.html#N10089">rExec </a></span></dt><dt><span class="section"><a href="executeservices.html#N10104">runCommand</a></span></dt><dt><span class="section"><a href="executeservices.html#N1017B">runCommandWithSSH</a></span></dt><dt><span class="section"><a href="executeservices.html#N101FC">telnet</a></span></dt></dl></dd><dt><span class="section"><a href="fileservices.html">FileServices</a></span></dt><dt><span class="section"><a href="miscservices.html">MiscServices</a></span></dt></dl></dd><dt><span class="chapter"><a href="xmltypes.html">3. XML Types</a></span></dt><dd><dl><dt><span class="section"><a href="xmltypes.html#N102AA"></a></span></dt><dd><dl><dt><span class="section"><a href="xmltypes.html#N102B0">AntProperty type</a></span></dt><dt><span class="section"><a href="xmltypes.html#N102C5">FileResource type</a></span></dt><dt><span class="section"><a href="xmltypes.html#hostconnection">HostConnection type</a></span></dt><dt><span class="section"><a href="xmltypes.html#patternelement">PatternElement type</a></span></dt><dt><span class="section"><a href="xmltypes.html#patternsettype">PatternSetType type</a></span></dt><dt><span class="section"><a href="xmltypes.html#N10367">ReturnCode type</a></span></dt><dt><span class="section"><a href="xmltypes.html#selectortype">SelectorType type</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="executeservices.html#N10096">rExec input parameters </a></dt><dt>2.2. <a href="executeservices.html#N10111">runCommand input parameters</a></dt><dt>2.3. <a href="executeservices.html#N10188">runCommandWithSSH input parameters</a></dt><dt>2.4. <a href="executeservices.html#N10209">telnet input parameters</a></dt></dl></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="installation.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%"> </td><td align="center" width="20%"> </td><td valign="top" align="right" width="40%"> Chapter 1. Getting started</td></tr></table></div></body></html>