| 1 |
<?xml version="1.0" encoding="UTF-8"?>
|
1 |
<?xml version="1.0" encoding="UTF-8"?>
|
| 2 |
<abstract>
|
2 |
<abstract>
|
| 3 |
<title>Abstract</title>
|
3 |
<title>Abstract</title>
|
| 4 |
<para>In complex IT environments it is necessary to integrate
|
4 |
<para>In complex IT environments it is often necessary to integrate different information systems with each other, exchange data between software tools and automate actions based on events arising from user interaction. Web Services is a popular way to make remote functions available to a broad range of clients. A WebService is independent from platforms and programming languages. XML Messages are exchanged through common protocols like TCP/IP or SMTP, processed and returned (request/ response paradigm).</para>
|
| 5 |
different information systems with each other, exchange data
|
5 |
<para>Because of their nature, WebServices are a great technology to overcome system boundaries and to "orchestrate" your IT environment. They make up the basis for SOA and are the pieces that assemble automated business processes.</para>
|
| 6 |
between
|
- |
|
| 7 |
tools and automate actions and function calls depending
|
- |
|
| 8 |
on events
|
- |
|
| 9 |
arising from user interaction. To meet the requirements
|
- |
|
| 10 |
of
|
- |
|
| 11 |
integration building usually means to implement APIs and to
|
- |
|
| 12 |
create
|
- |
|
| 13 |
tool-to-tool bridges. Web Services can help to clean up
|
- |
|
| 14 |
bridges into
|
- |
|
| 15 |
interfaces as well as to abstract functions from
|
- |
|
| 16 |
their underlying
|
- |
|
| 17 |
platform and implementation.</para>
|
- |
|
| 18 |
<para>These are the major goals of the loosely coupled
|
6 |
<para>XServices is a collection of pre-build WebServices with the intention to avoid duplicate work and "re-inventing the wheel". The historical base for XServices is the 'XBridgeNG' software, which provided a set of Apache Ant Tasks with quite the same intention. The available WebService operations are most likely the "most wanted" ones, some of the for sure are "must have". This collection may overlap with other libraries. In summary the current version contains 8 WebServices with over 50 operations.</para>
|
| 19 |
integration
|
- |
|
| 20 |
strategy which is in turn one essential idea of a
|
- |
|
| 21 |
service-oriented
|
- |
|
| 22 |
architecture (SOA).</para>
|
- |
|
| 23 |
<para>provide a low level set of functions and web services.
|
- |
|
| 24 |
These can
|
- |
|
| 25 |
be orchestrated into services and used in business
|
- |
|
| 26 |
processes which
|
- |
|
| 27 |
make up the execution part of a SOA
|
- |
|
| 28 |
environment.</para>
|
- |
|
| 29 |
<para>is an add-on to XBridgeNG 2.0. It runs standalone or in
|
- |
|
| 30 |
combination with XBridgeNG. Pure XBridgeNG has two
|
- |
|
| 31 |
components:</para>
|
- |
|
| 32 |
<para>
|
- |
|
| 33 |
<itemizedlist>
|
- |
|
| 34 |
<listitem>
|
- |
|
| 35 |
<para>XML Schema for item based data types (e.g. tickets
|
- |
|
| 36 |
from a bug
|
- |
|
| 37 |
tracker system or a database record)</para>
|
- |
|
| 38 |
</listitem>
|
- |
|
| 39 |
<listitem>
|
- |
|
| 40 |
<para>Set of Apache Ant tasks to function as a bridge
|
- |
|
| 41 |
between the
|
- |
|
| 42 |
XBridgeNG XML format at legacy 3rd party
|
- |
|
| 43 |
software (e.g. HP Quality
|
- |
|
| 44 |
Center, Serena TeamTrack,
|
- |
|
| 45 |
...)</para>
|
- |
|
| 46 |
</listitem>
|
- |
|
| 47 |
<listitem>
|
- |
|
| 48 |
<para>The add Web Services (SOAP) wrapper around Apache Ant
|
- |
|
| 49 |
tasks
|
- |
|
| 50 |
(since XBridgeNG 2.0)</para>
|
- |
|
| 51 |
</listitem>
|
- |
|
| 52 |
</itemizedlist>
|
- |
|
| 53 |
</para>
|
- |
|
| 54 |
<para>The current focus is on file-based operations. do not
|
- |
|
| 55 |
contain an
|
- |
|
| 56 |
integration server or a process execution
|
- |
|
| 57 |
engine.</para>
|
- |
|
| 58 |
</abstract>
|
7 |
</abstract>
|