1,7 → 1,7 |
<?xml version="1.0" encoding="UTF-8"?><book xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" version="5.0"> |
<title>Brutex XServices Documentation</title> |
<bookinfo> |
<date>February, 16th 2010</date> |
<date>Januar 2012</date> |
<author> |
<firstname>Brian</firstname> |
<surname>Rosenberger</surname> |
9,7 → 9,7 |
</author> |
<corpname>Brutex Network</corpname> |
<copyright> |
<year>2011</year> |
<year>2012</year> |
</copyright> |
<legalnotice> |
<para> |
20,66 → 20,29 |
</para> |
</legalnotice> |
<legalnotice> |
<para> |
<literallayout> |
Licensed under the Apache License, Version 2.0 (the "License"); |
you may not use this file except in compliance with the License. |
You may obtain a copy of the License at |
|
http://www.apache.org/licenses/LICENSE-2.0 |
|
Unless required by applicable law or agreed to in writing, software |
distributed under the License is distributed on an "AS IS" BASIS, |
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
See the License for the specific language governing permissions and |
limitations under the License. |
</literallayout></para> |
<para>Apache Tomcat and Apache Ant are trademarks of the Apache |
Software Foundation.</para> |
</legalnotice> |
<abstract xml:base="common/abstract.xml"> |
<title>Abstract</title> |
<para>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.</para> |
<para>These are the major goals of the loosely coupled |
integration |
strategy which is in turn one essential idea of a |
service-oriented |
architecture (SOA).</para> |
<para>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.</para> |
<para>is an add-on to XBridgeNG 2.0. It runs standalone or in |
combination with XBridgeNG. Pure XBridgeNG has two |
components:</para> |
<para> |
<itemizedlist> |
<listitem> |
<para>XML Schema for item based data types (e.g. tickets |
from a bug |
tracker system or a database record)</para> |
</listitem> |
<listitem> |
<para>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, |
...)</para> |
</listitem> |
<listitem> |
<para>The add Web Services (SOAP) wrapper around Apache Ant |
tasks |
(since XBridgeNG 2.0)</para> |
</listitem> |
</itemizedlist> |
</para> |
<para>The current focus is on file-based operations. do not |
contain an |
integration server or a process execution |
engine.</para> |
</abstract> |
<title>Abstract</title> |
<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> |
<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> |
<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> |
</abstract> |
</bookinfo> |
<chapter id="installation"> |
<beginpage/> |
3350,7 → 3313,7 |
]]></programlisting> |
</para> |
</section> |
</section> |
</section> |
<section id="executeservices" version="5.0" xml:base="ExecuteServices.xml" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"> |
<title>ExecuteServices</title> |
<para>The ExecuteService bundles local and remote command |
3827,6 → 3790,15 |
<para>The FileServces bundles various file operations. Its WSDL is located at |
http://server:port/XServices/FileService?wsdl</para> |
</section> |
<section id="mailservices" version="5.0" xml:base="MailServices.xml" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"> |
<title>MailServices</title> |
<para>The MailService contains mail send and receive operations. Its WSDL is located at |
http://server:port/XServices/MailService?wsdl</para> |
<section version="5.0" xml:base="MailServices/sendMailSimple.xml" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"> |
<title>sendMailSimple</title> |
<para>Send email.</para> |
</section> |
</section> |
<section id="miscservices" version="5.0" xml:base="MiscServices.xml" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"> |
<title>MiscServices</title> |
<para>The MiscService bundles various operations. Its WSDL is located at |
3897,7 → 3869,16 |
]]></screen> |
</para> |
</section> |
</section> |
<section version="5.0" xml:base="MiscServices/sleep.xml" xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"> |
<title>sleep</title> |
<para>Delays the response by the given minutes/ seconds. Please note, |
that it may take more time to perform the server roundtrip (network |
delays, parsing, etc.). Also you may have a network timeout set up in |
Tomcat or your client that prevents this web service to respond |
correctly. |
</para> |
</section> |
</section> |
</chapter> |
|
<chapter id="xmltypes"> |