Subversion Repositories XServices

Compare Revisions

No changes between revisions

Ignore whitespace Rev 166 → Rev 180

/xservices/branches/xservices-jre7/doc/common/installation.xml
0,0 → 1,60
<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook" version="5.0"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
 
 
<title>Installation</title>
<para>As of February 2013, XServices require Java 7. Older builds run against Java 5.</para>
<para>Apache Tomcat 7</para>
<para>tbd.</para>
<para>In short: Deploy .WAR file to Apache Tomcat</para>
<section>
<title>Securing with Basic Authentication</title>
<para>There is a quick guide explaining Basic Authentication for Tomcat here: <link
xlink:href="http://oreilly.com/pub/a/java/archive/tomcat-tips.html?page=1">
http://oreilly.com/pub/a/java/archive/tomcat-tips.html?page=1</link>
</para>
<para>
</para>
</section>
<section>
<title>Limit access by IP address</title>
<para>Sometimes you&apos;ll only want to restrict access to to
only
specified host names or IP addresses. This way, only
clients at
those specified addresses can use the web services.
Tomcat provides
two configuration values for that:
RemoteHostValve and
RemoteAddrValve.</para>
<para>These Valves allow you to filter requests by host name or
by IP
address, and to allow or deny hosts that match. The
example below
restricts access to the ArchiveService from any
machine that is not
the local host.</para>
<programlisting language="xml">&lt;Context
path=&quot;/XService/ArchiveService&quot;
...&gt; &lt;Valve
className=&quot;org.apache.catalina.valves.RemoteAddrValve&quot;
allow=&quot;127.0.0.1&quot; deny=&quot;&quot;/&gt; &lt;/Context&gt;
</programlisting>
<para>If no allow pattern is given, then patterns that match
the deny
attribute patterns will be rejected, and all others
will be allowed.
Similarly, if no deny pattern is given,
patterns that match the
allow attribute will be allowed, and
all others will be denied.
</para>
<para>The &lt;context&gt; element must be placed into the
server.xml
file (into &lt;engine&gt;&lt;host&gt;).</para>
</section>
 
</section>
Property changes:
Added: svn:mime-type
+text/plain
\ No newline at end of property
/xservices/branches/xservices-jre7/doc/common/abstract.xml
0,0 → 1,25
<?xml version="1.0" encoding="UTF-8"?>
<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 them 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>
Property changes:
Added: svn:mime-type
+text/plain
\ No newline at end of property