Brutex XServices Documentation
|  | Next

# Brutex XServices Documentation

### Brian Rosenberger

`<bru@brutex.de>`

Copyright © 2011

The copyright holders make no representation about the suitability of this document for any purpose. It is provided “as is” without expressed or implied warranty.

Apache Tomcat and Apache Ant are trademarks of the Apache Software Foundation.

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.

List of Tables

2.1. rExec input parameters
2.2. runCommand input parameters
2.3. runCommandWithSSH input parameters
2.4. telnet input parameters

|  | Next
|  | Chapter 1. Getting started