Subversion Repositories XServices

Rev

Rev 24 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed

Rev Author Line No. Line
24 brianR 1 
<?xml version='1.0' encoding='UTF-8'?><chapter>
2 
    <beginpage/>
25 brianR 3 
    <title>Getting started</title>
24 brianR 4 
    <para>This chapter describes the installation.</para>
5 
    <sect1>
6 
        <title>Prerequisites</title>
7 
        <para>tbd.</para>
8 
        <para>Sun Java SE 1.6.0</para>
9 
        <para>Apache Tomcat 6</para>
10 
    </sect1>
11 
    <sect1>
12 
        <title>Installation</title>
13 
        <para>tbd.</para>
14 
        <para>In short: Deploy .WAR file to Apache Tomcat</para>
15 
        <sect2>
16 
            <title>Securing &brs; with Basic Authentication</title>
17 
            <para>There is a quick guide explaining Basic Authentication for Tomcat here: </para>
18 
            <para><ulink url="http://oreilly.com/pub/a/java/archive/tomcat-tips.html?page=1"/></para>
19 
        </sect2>
20 
        <sect2>
21 
            <title>Limit access to &brs;</title>
22 
            <para>Sometimes you&apos;ll only want to restrict access to &brs; to only specified host names or IP addresses. This way, only clients at those specified addresses can use the &brs; web services. Tomcat provides two configuration values for that: RemoteHostValve and RemoteAddrValve.</para>
23 
            <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>
24 
            <programlisting language="xml">&lt;Context path=&quot;/XService/ArchiveService&quot; ...&gt;
25 
                &lt;Valve className=&quot;org.apache.catalina.valves.RemoteAddrValve&quot;
26 
                allow=&quot;127.0.0.1&quot; deny=&quot;&quot;/&gt;
27 
            &lt;/Context&gt;</programlisting>
28 
            <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>
29 
            <para>The &lt;context&gt; element must be placed into the server.xml file (into &lt;engine&gt;&lt;host&gt;).</para>
30 
        </sect2>
31 
    </sect1>
32 
</chapter>