servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject svn commit: r1597941 [6/6] - in /servicemix/site/production/docs/5.0.x: ./ activemq/ activiti/ camel/ camel/deployment/ commands/ developers-guide/ karaf/ quickstart/ user/ users-guide/
Date Wed, 28 May 2014 08:20:18 GMT
Modified: servicemix/site/production/docs/5.0.x/quickstart/quickstart.pdf.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/quickstart.pdf.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/quickstart.pdf.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/quickstart.pdf.html Wed May 28 08:20:15 2014
@@ -16,92 +16,7 @@
     </div>
   </div>
   <div id="main">
-    <h1 id="Introduction">Introduction</h1><p>First of all, welcome to the Apache ServiceMix project!</p><p>The goal of this Quickstart guide is to give you a 20-minute overview of what ServiceMix is and what you can do with it.  In that time, we'll install ServiceMix on your machine, deploy some basic integration routes and extend the container with an additional feature.</p><h1 id="Installation">Installation</h1><p>Before we can start working with Apache ServiceMix, we have to get it installed and running on our local machine first.</p><h2 id="Systemrequirements">System requirements</h2><p>For running Apache ServiceMix itself, you'll need</p><ul><li><p>Java Runtime Environment (JRE) 1.6.x (Java 6) or<br/>  Java Runtime Environment (JRE) 1.7.x (Java 7)</p></li><li><p>About 100 MB of free disk space for the default assembly</p></li></ul><p>If you're developing your own integration applications and OSGi bundles, you'll also need</p><ul><li><p>Java Developer Kit (JDK) 1.6.x (Java 6) o
 r<br/>  Java Developer Kit (JDK) 1.7.x (Java 7)</p></li><li><p>Apache Maven 3.0.4 or higher</p></li></ul><h2 id="DownloadingApacheServiceMix">Downloading Apache ServiceMix</h2><p>Apache ServiceMix 5.0.0-SNAPSHOT is available under the Apache License v2 and can be downloaded from <a href="http://servicemix.apache.org/downloads.html">http://servicemix.apache.org/downloads.html</a>.</p><p>Depending on your operation system, you should download either the tar.gz or the zip file:</p><ul><li><p><tt>tar.gz</tt> for Linux/Unix/MacOS X</p></li><li><p><tt>zip</tt> for Windows</p></li></ul><h2 id="InstallingApacheServiceMix">Installing Apache ServiceMix</h2><p>Installing Apache ServiceMix is as simple as uncompressing the downloaded archive on your hard disk.  For the rest of this guide, we'll refer to the this location as <strong><tt>&lt;SERVICEMIX_HOME></tt></strong>.</p><h2 id="StartingApacheServiceMix">Starting Apache ServiceMix</h2><p>Depending on your platform, start Apache ServiceMix by
  following the instructions below.  After starting the container, you will have access to the console from which you can manage the container.</p><h3 id="OnWindows">On Windows</h3><p>In a command prompt window, navigate to the directory where you extracted ServiceMix and run the <tt>bin\servicemix.bat</tt> file.</p><p>Example: if ServiceMix in installed in the <tt>c:\tools\apache-servicemix-5.0.0-SNAPSHOT</tt> directory</p><div class="syntax"><pre name='code' class='brush: bat; gutter: false;'><code>
-&gt; cd c:\tools\apache-servicemix-5.0.0-SNAPSHOT
-&gt; .\bin\servicemix</code></pre></div><p><img border="0" src="images/start-windows.png"/></p><h3 id="OnLinuxUnixMacOSX">On Linux/Unix/MacOS X</h3><p>On a command shell, navigate to the directory where you extracted ServiceMix and the <tt>bin/servicemix</tt> shell script</p><p>Example: if ServiceMix is installed in the <tt>~/Applications/apache-servicemix-5.0.0-SNAPSHOT</tt> directory.</p><div class="syntax"><pre name='code' class='brush: bash; gutter: false;'><code>
-$ cd ~/Applications/apache-servicemix-5.0.0-SNAPSHOT
-$ ./bin/servicemix</code></pre></div><p>!/quickstart/images/start-linux.png</p>|width=75%|height=75%!<h1 id="ApacheServiceMixconsole">Apache ServiceMix console</h1><p>Now that we successfully installed and started Apache ServiceMix, we'll take a closer look at the console.  This is where you manage your ServiceMix instance, add and remove bundles, install optional features, ...</p><h2 id="Workingwithbundles">Working with bundles</h2><p>When ServiceMix is first started, a whole set of bundles providing the core features for the product are being installed.  Let's use the command console to find out more about them...</p><p>The <tt>osgi:list</tt> command can be used to get a list of all bundles currently installed.  Enter this</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:list</code></pre></div><p>This is what the output looks like if you run this on your ServiceMix instance.</p><p>!/quickstart/images/osgi-list.png</p>|title=osgi:list!<p>For every bundle, you see:</p><ul><li><p>the bundle id</p></li><li><p>the bundle state</p></li><li><p>if the bundle contains a Blueprint or Spring XML file, the next 2 columns will show you if the beans defined there were created successfully</p></li><li><p>the bundle start level</p></li><li><p>the bundle name and version</p></li></ul><p>If you're looking for something specific in the list, you can use unix-like pipes and utilities to help you.  An example: to look for all Camel related bundles...</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:list | grep camel</code></pre></div><p>!/quickstart/images/osgi-list-pipegrep.png</p>|title=osgi:list!<h2 id="Workingwithlogging">Working with logging</h2><p>Many of the applications you write will have some form of log output.  To look at the message in the log file, you can us the <tt>log:diplay</tt> command.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:display</code></pre></div><p>!/quickstart/images/log-display.png</p>|title=log:display!<p>If you're only interested in the latest exception in the log file, you can use <tt>log:display-exception</tt> instead.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:display-exception</code></pre></div><p>!/quickstart/images/log-display-exception.png</p>|title=log:display-exception!<p>You can also change the log level at runtime by using the <tt>log:set</tt> command.  You can try these commands on your instance now by first setting the log level to <tt>DEBUG</tt> and then using <tt>grep</tt> to make sure that you can actually see the extra logging.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:set DEBUG
-karaf@root&gt; log:display | grep DEBUG</code></pre></div><p>!/quickstart/images/log-set-debug.png</p>|title=log:set DEBUG!<p>Afterwards, revert the log level to its original <tt>INFO</tt> value again with <tt>log:set</tt>.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; log:set INFO</code></pre></div><h2 id="...andtheresalotmore">...and there's a lot more</h2><p>These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.</p><h1 id="UsingCamel">Using Camel</h1><p>Now that we know how to operate Apache ServiceMix through the shell console, it's time to start using it for what it is built for.  Let's build our very first integration solution with a Camel route and deploy it on ServiceMix.</p><h2 id="Oursimplescenario">Our simple scenario</h2><p>In this simple scenario, we're going to move files from an input directory called <tt>camel/input</tt> to an output directory called <tt>camel/output</tt>.  To ensure we can keep track of which files get moved, we'll also write a message to the log file whenever we move a file.</p><h2 id="Creatingtheroute">Creating the route</h2><p>
 One of the most simple ways to deploy a new route on ServiceMix, is by defining the route in a Blueprint XML file.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;file:camel/input&quot;/&gt;
-        &lt;log message=&quot;Moving ${file:name} to the output directory&quot;/&gt;
-        &lt;to uri=&quot;file:camel/output&quot;/&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-&lt;/blueprint&gt;</code></pre></div><h2 id="Deployingtheroute">Deploying the route</h2><p>In order to deploy and start the route, just copy the XML file you created into ServiceMix' <tt>deploy</tt> directory.  The file will get picked up and deployed by ServiceMix.  You will see a <tt>camel/input</tt> folder appear in your ServiceMix installation directory and any files you copy into that directory will get moved into the <tt>camel/output</tt> directory.</p><p>If you do a <tt>log:display</tt> in the shell, you will also see the log output for every file that's been moved.</p><p><img border="0" src="images/camel-sample-log.png"/></p><h2 id="Usingtheshelltomanagetheroute">Using the shell to manage the route</h2><p>Using <tt>osgi:list</tt>, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.</p><p><img border="0" src="images/camel-sample-deploy.png"/></p><p>From this output, you also learn tha
 t the bundle id for your XML file is 200.  This allow you to start and stop the route whenever necessary.  Let's give this a go now...</p><p>First, stop the route with</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:stop 200</code></pre></div><p>The route is no longer active, so any files you copy into the <tt>orders/input</tt> folder will remain there for now.  As soon as you restart the route, the pending files will get moving again.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; osgi:start 200</code></pre></div><h1 id="AddingActiveMQtotheMix">Adding ActiveMQ to the 'Mix</h1><p>Out-of-the-box, every Apache ServiceMix instance comes with an embedded ActiveMQ JMS broker.  This makes it easy to communicate between Camel routes using persistent messages on the same machine, but it will also enable you to distribute your routes over multiple instances afterwards for clustering or load-balancing.</p><h2 id="Ourscenario">Our scenario</h2><p>In this scenario, we also want to move files between directories.  Instead of logging the move directly, we are going to send an event JMS message onto a queue.  Afterwards, we will create a second Camel route to receive the events and log them.</p><h2 id="Beforewestart">Before we start</h2><p>First, we have to install an optional feature to allow Camel send and receive JMS messages.  We'll talk about optional features a bit more in the next page of this quickstart guide, but for now, just run the following comman
 d in the console.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:install camel-jms</code></pre></div><h2 id="Movingfilesandsendingeventmessages">Moving files and sending event messages</h2><p>The first Blueprint XML file we'll create contains a Camel route that moves the files from <tt>activemq/input</tt> to the <tt>activemq/output</tt> directory.  Afterwards, it will generate an event message and send that to an ActiveMQ queue called <tt>events</tt>.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;file:activemq/input&quot;/&gt;
-        &lt;to uri=&quot;file:activemq/output&quot;/&gt;
-
-        &lt;setBody&gt;
-          &lt;simple&gt;
-            FileMovedEvent(file: ${file:name}, timestamp: ${date:now:hh:MM:ss.SSS})
-          &lt;/simple&gt;
-        &lt;/setBody&gt;
-        &lt;to uri=&quot;activemq://events&quot; /&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-    &lt;bean id=&quot;activemq&quot; class=&quot;org.apache.activemq.camel.component.ActiveMQComponent&quot;&gt;
-        &lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;/&gt;
-    	&lt;property name=&quot;userName&quot; value=&quot;smx&quot;/&gt;
-    	&lt;property name=&quot;password&quot; value=&quot;smx&quot;/&gt;
-    &lt;/bean&gt;
-
-&lt;/blueprint&gt;</code></pre></div><p>Save this file in ServiceMix' <tt>deploy</tt> folder and use <tt>osgi:list</tt> to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the <tt>activemq/input</tt> directory and see them being moved to <tt>activemq/output</tt>.</p><h2 id="Receivingtheeventmessages">Receiving the event messages</h2><p>After deploying the first XML file, you're obviously not seeing any events being logged yet.  The event messages are sent to an ActiveMQ queue, but there's nobody to receive the events yet.  Let's change that now by creating a second Blueprint XML file.</p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint
-    xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-    xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-    xsi:schemaLocation=&quot;
-      http://www.osgi.org/xmlns/blueprint/v1.0.0
-      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-      &lt;route&gt;
-        &lt;from uri=&quot;activemq://events&quot;/&gt;
-        &lt;to uri=&quot;log:events&quot;/&gt;
-      &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-    &lt;bean id=&quot;activemq&quot; class=&quot;org.apache.activemq.camel.component.ActiveMQComponent&quot;&gt;
-        &lt;property name=&quot;brokerURL&quot; value=&quot;tcp://localhost:61616&quot;/&gt;
-    	&lt;property name=&quot;userName&quot; value=&quot;smx&quot;/&gt;
-    	&lt;property name=&quot;password&quot; value=&quot;smx&quot;/&gt;
-    &lt;/bean&gt;
-
-&lt;/blueprint&gt;</code></pre></div><p>As soon as this second file has been deployed, you'll start seeing the event messages in your <tt>log:display</tt> output.</p><h2 id="Usingtheshelltomanagetheroutes">Using the shell to manage the routes</h2><p>You can now start and stop both routes from the command shell.  The important thing to note here is that you can stop the event handler route while files are being processed.  As soon as you restart that bundle afterwards, you'll receive the events from all files that have been moved while the route was not running.</p><h1 id="Optionalfeatures">Optional features</h1><p>Everything discussed in the quickstart guide so far is installed out-of-the-box in Apache ServiceMix, but we also have a lot of optional features that can be installed in the container when necessary.</p><h2 id="Listoffeatures">List of features</h2><p>The list of features is available with the <tt>features:list</tt> command.  The overview shows you whether or not the featu
 re is currently installed, the version and the name of the feature.</p><p><img border="0" src="images/featureslist.png"/></p><p>The full list contains a lot of different features: optional Camel components, features for adding OBR or wrapper support to Serviceix, a web console, ...  Again, you can use things like {{</p>|}} and <tt>grep</tt> to find the things in the list that you're interested in.<div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:list | grep camel</code></pre></div><h2 id="ExampleWebconsole">Example: Web console</h2><p>To get the web console installed in ServiceMix, install the feature from your console</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:install webconsole</code></pre></div><p>Afterwards, you can verify that the feature is marked installed in the overview.  You'll notice that the <tt>webconsole-base</tt> feature has also been installed as a requirement for the <tt>webconsole</tt> feature itself.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt; features:list | grep webconsole</code></pre></div><p><img border="0" src="images/featureslist-grep-webconsole.png"/></p><p>You will now be able to point your browser to http://localhost:8181/system/console and login with user <tt>smx</tt> and password <tt>smx</tt> to access the web console.  From the webconsole, you can also start and stop bundles, install optional features again, ...</p><h1 id="Wrappingitup...">Wrapping it up...</h1><p>This is where our introductory journey through the world of Apache ServiceMix ends.  We've obviously just scratched the surface of what is possible, but we hope you have an idea of what you can expect from Apache ServiceMix and how you can use it in your environment.</p><p>For more in-depth information, have a look at our set of user guides.  Also, if you have any questions, we welcome you on our user mailing list!</p>
+    <h1 id="Introduction">Introduction</h1><p>First of all, welcome to the Apache ServiceMix project!</p><p>The goal of this Quickstart guide is to give you a 20-minute overview of what ServiceMix is and what you can do with it.  In that time, we'll install ServiceMix on your machine, deploy some basic integration routes and extend the container with an additional feature.</p><h1 id="Installation">Installation</h1><p>Before we can start working with Apache ServiceMix, we have to get it installed and running on our local machine first.</p><h2 id="Systemrequirements">System requirements</h2><p>For running Apache ServiceMix itself, you'll need</p><ul><li><p>Java Runtime Environment (JRE) 1.6.x (Java 6) or<br/>  Java Runtime Environment (JRE) 1.7.x (Java 7)</p></li><li><p>About 100 MB of free disk space for the default assembly</p></li></ul><p>If you're developing your own integration applications and OSGi bundles, you'll also need</p><ul><li><p>Java Developer Kit (JDK) 1.6.x (Java 6) o
 r<br/>  Java Developer Kit (JDK) 1.7.x (Java 7)</p></li><li><p>Apache Maven 3.0.4 or higher</p></li></ul><h2 id="DownloadingApacheServiceMix">Downloading Apache ServiceMix</h2><p>Apache ServiceMix 5.0.0-SNAPSHOT is available under the Apache License v2 and can be downloaded from <a href="http://servicemix.apache.org/downloads.html">http://servicemix.apache.org/downloads.html</a>.</p><p>Depending on your operation system, you should download either the tar.gz or the zip file:</p><ul><li><p><tt>tar.gz</tt> for Linux/Unix/MacOS X</p></li><li><p><tt>zip</tt> for Windows</p></li></ul><h2 id="InstallingApacheServiceMix">Installing Apache ServiceMix</h2><p>Installing Apache ServiceMix is as simple as uncompressing the downloaded archive on your hard disk.  For the rest of this guide, we'll refer to the this location as <strong><tt>&lt;SERVICEMIX_HOME></tt></strong>.</p><h2 id="StartingApacheServiceMix">Starting Apache ServiceMix</h2><p>Depending on your platform, start Apache ServiceMix by
  following the instructions below.  After starting the container, you will have access to the console from which you can manage the container.</p><h3 id="OnWindows">On Windows</h3><p>In a command prompt window, navigate to the directory where you extracted ServiceMix and run the <tt>bin\servicemix.bat</tt> file.</p><p>Example: if ServiceMix in installed in the <tt>c:\tools\apache-servicemix-5.0.0-SNAPSHOT</tt> directory</p><div class="syntax"><div class="highlight"><pre><span class="p">&gt;</span> <span class="n">cd</span> c:\tools\apache-servicemix<span class="m">-5</span>.<span class="m">0</span>.<span class="m">0</span>-SNAPSHOT&#x000A;&gt; .\bin\servicemix&#x000A;</pre></div>&#x000A;</div><p><img border="0" src="images/start-windows.png"/></p><h3 id="OnLinuxUnixMacOSX">On Linux/Unix/MacOS X</h3><p>On a command shell, navigate to the directory where you extracted ServiceMix and the <tt>bin/servicemix</tt> shell script</p><p>Example: if ServiceMix is installed in the <tt>~/Applica
 tions/apache-servicemix-5.0.0-SNAPSHOT</tt> directory.</p><div class="syntax"><div class="highlight"><pre><span class="nv">$ </span><span class="nb">cd</span> ~/Applications/apache-servicemix-5.0.0-SNAPSHOT&#x000A;<span class="nv">$ </span>./bin/servicemix&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/start-linux.png</p>|width=75%|height=75%!<h1 id="ApacheServiceMixconsole">Apache ServiceMix console</h1><p>Now that we successfully installed and started Apache ServiceMix, we'll take a closer look at the console.  This is where you manage your ServiceMix instance, add and remove bundles, install optional features, ...</p><h2 id="Workingwithbundles">Working with bundles</h2><p>When ServiceMix is first started, a whole set of bundles providing the core features for the product are being installed.  Let's use the command console to find out more about them...</p><p>The <tt>osgi:list</tt> command can be used to get a list of all bundles currently installed.  Enter this</p><div c
 lass="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:list&#x000A;</pre></div>&#x000A;</div><p>This is what the output looks like if you run this on your ServiceMix instance.</p><p>!/quickstart/images/osgi-list.png</p>|title=osgi:list!<p>For every bundle, you see:</p><ul><li><p>the bundle id</p></li><li><p>the bundle state</p></li><li><p>if the bundle contains a Blueprint or Spring XML file, the next 2 columns will show you if the beans defined there were created successfully</p></li><li><p>the bundle start level</p></li><li><p>the bundle name and version</p></li></ul><p>If you're looking for something specific in the list, you can use unix-like pipes and utilities to help you.  An example: to look for all Camel related bundles...</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:list | grep camel&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/osgi-list-pipegrep.png</p>|title=osgi:list!<h2 id="Workingwithlogging">Working with logging</h2><p>Many
  of the applications you write will have some form of log output.  To look at the message in the log file, you can us the <tt>log:diplay</tt> command.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:display&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-display.png</p>|title=log:display!<p>If you're only interested in the latest exception in the log file, you can use <tt>log:display-exception</tt> instead.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:display-exception&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-display-exception.png</p>|title=log:display-exception!<p>You can also change the log level at runtime by using the <tt>log:set</tt> command.  You can try these commands on your instance now by first setting the log level to <tt>DEBUG</tt> and then using <tt>grep</tt> to make sure that you can actually see the extra logging.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:set DEBU
 G&#x000A;karaf@root&gt; log:display | grep DEBUG&#x000A;</pre></div>&#x000A;</div><p>!/quickstart/images/log-set-debug.png</p>|title=log:set DEBUG!<p>Afterwards, revert the log level to its original <tt>INFO</tt> value again with <tt>log:set</tt>.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; log:set INFO&#x000A;</pre></div>&#x000A;</div><h2 id="...andtheresalotmore">...and there's a lot more</h2><p>These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.</p><h1 id="UsingCamel">Using Camel</h1><p>Now that we know how to operate Apache ServiceMix through the shell console, it's time to start using it for what it is built for.  Let's build our very first integration solution with a Camel route and deploy it on ServiceMix.</p><h2 id="Oursimplescenario">Our simple scenario</h2><p>In this simple scena
 rio, we're going to move files from an input directory called <tt>camel/input</tt> to an output directory called <tt>camel/output</tt>.  To ensure we can keep track of which files get moved, we'll also write a message to the log file whenever we move a file.</p><h2 id="Creatingtheroute">Creating the route</h2><p>One of the most simple ways to deploy a new route on ServiceMix, is by defining the route in a Blueprint XML file.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blu
 eprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:camel/input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;log</span> <span class="na">message=</span><span class="s">&quot;Moving ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:camel/output&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</s
 pan>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="Deployingtheroute">Deploying the route</h2><p>In order to deploy and start the route, just copy the XML file you created into ServiceMix' <tt>deploy</tt> directory.  The file will get picked up and deployed by ServiceMix.  You will see a <tt>camel/input</tt> folder appear in your ServiceMix installation directory and any files you copy into that directory will get moved into the <tt>camel/output</tt> directory.</p><p>If you do a <tt>log:display</tt> in the shell, you will also see the log output for every file that's been moved.</p><p><img border="0" src="images/camel-sample-log.png"/></p><h2 id="Usingtheshelltomanagetheroute">Using the shell to manage the route</h2><p>Using <tt>osgi:list</tt>, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.</p><p><img border="0" src="images/camel-samp
 le-deploy.png"/></p><p>From this output, you also learn that the bundle id for your XML file is 200.  This allow you to start and stop the route whenever necessary.  Let's give this a go now...</p><p>First, stop the route with</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:stop 200&#x000A;</pre></div>&#x000A;</div><p>The route is no longer active, so any files you copy into the <tt>orders/input</tt> folder will remain there for now.  As soon as you restart the route, the pending files will get moving again.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; osgi:start 200&#x000A;</pre></div>&#x000A;</div><h1 id="AddingActiveMQtotheMix">Adding ActiveMQ to the 'Mix</h1><p>Out-of-the-box, every Apache ServiceMix instance comes with an embedded ActiveMQ JMS broker.  This makes it easy to communicate between Camel routes using persistent messages on the same machine, but it will also enable you to distribute your routes over multiple instances after
 wards for clustering or load-balancing.</p><h2 id="Ourscenario">Our scenario</h2><p>In this scenario, we also want to move files between directories.  Instead of logging the move directly, we are going to send an event JMS message onto a queue.  Afterwards, we will create a second Camel route to receive the events and log them.</p><h2 id="Movingfilesandsendingeventmessages">Moving files and sending event messages</h2><p>The first Blueprint XML file we'll create contains a Camel route that moves the files from <tt>activemq/input</tt> to the <tt>activemq/output</tt> directory.  Afterwards, it will generate an event message and send that to an ActiveMQ queue called <tt>events</tt>.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000
 A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:activemq/input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:activemq/output&quot;</span><span class="nt">/&gt;</span>&#x000A;&#x000A;        <sp
 an class="nt">&lt;setBody&gt;</span>&#x000A;          <span class="nt">&lt;simple&gt;</span>&#x000A;            FileMovedEvent(file: ${file:name}, timestamp: ${date:now:hh:MM:ss.SSS})&#x000A;          <span class="nt">&lt;/simple&gt;</span>&#x000A;        <span class="nt">&lt;/setBody&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;activemq://events&quot;</span> <span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><p>Save this file in ServiceMix' <tt>deploy</tt> folder and use <tt>osgi:list</tt> to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the <tt>activemq/input</tt> directory and see them being moved to <tt>activemq/output</tt>.</p><h2 id="Receivingtheeventmessages">Receiving the event messag
 es</h2><p>After deploying the first XML file, you're obviously not seeing any events being logged yet.  The event messages are sent to an ActiveMQ queue, but there's nobody to receive the events yet.  Let's change that now by creating a second Blueprint XML file.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  
   <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;activemq://events&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;log:events&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><p>As soon as this second file has been deployed, you'll start seeing the event messages in your <tt>log:display</tt> output.</p><h2 id="Usingtheshelltomanagetheroutes">Using the shell to manage the routes</h2><p>You can now start and stop both routes from the command s
 hell.  The important thing to note here is that you can stop the event handler route while files are being processed.  As soon as you restart that bundle afterwards, you'll receive the events from all files that have been moved while the route was not running.</p><h1 id="Optionalfeatures">Optional features</h1><p>Everything discussed in the quickstart guide so far is installed out-of-the-box in Apache ServiceMix, but we also have a lot of optional features that can be installed in the container when necessary.</p><h2 id="Listoffeatures">List of features</h2><p>The list of features is available with the <tt>features:list</tt> command.  The overview shows you whether or not the feature is currently installed, the version and the name of the feature.</p><p><img border="0" src="images/featureslist.png"/></p><p>The full list contains a lot of different features: optional Camel components, features for adding OBR or wrapper support to Serviceix, a web console, ...  Again, you can use thin
 gs like {{</p>|}} and <tt>grep</tt> to find the things in the list that you're interested in.<div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep camel&#x000A;</pre></div>&#x000A;</div><h2 id="ExampleWebconsole">Example: Web console</h2><p>To get the web console installed in ServiceMix, install the feature from your console</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:install webconsole&#x000A;</pre></div>&#x000A;</div><p>Afterwards, you can verify that the feature is marked installed in the overview.  You'll notice that the <tt>webconsole-base</tt> feature has also been installed as a requirement for the <tt>webconsole</tt> feature itself.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep webconsole&#x000A;</pre></div>&#x000A;</div><p><img border="0" src="images/featureslist-grep-webconsole.png"/></p><p>You will now be able to point your browser to http://localhost:8181/system/console 
 and login with user <tt>smx</tt> and password <tt>smx</tt> to access the web console.  From the webconsole, you can also start and stop bundles, install optional features again, ...</p><h1 id="Wrappingitup...">Wrapping it up...</h1><p>This is where our introductory journey through the world of Apache ServiceMix ends.  We've obviously just scratched the surface of what is possible, but we hope you have an idea of what you can expect from Apache ServiceMix and how you can use it in your environment.</p><p>For more in-depth information, have a look at our set of user guides.  Also, if you have any questions, we welcome you on our user mailing list!</p>
   </div>
 </body>
 </html>
\ No newline at end of file

Modified: servicemix/site/production/docs/5.0.x/quickstart/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/quickstart/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/quickstart/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/quickstart/toc.html Wed May 28 08:20:15 2014
@@ -113,7 +113,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/user/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/user/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/user/index.html (original)
+++ servicemix/site/production/docs/5.0.x/user/index.html Wed May 28 08:20:15 2014
@@ -85,7 +85,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/user/technology-selection.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/user/technology-selection.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/user/technology-selection.html (original)
+++ servicemix/site/production/docs/5.0.x/user/technology-selection.html Wed May 28 08:20:15 2014
@@ -85,7 +85,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/user/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/user/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/user/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/user/toc.html Wed May 28 08:20:15 2014
@@ -95,7 +95,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/user/what-is-smx4.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/user/what-is-smx4.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/user/what-is-smx4.html (original)
+++ servicemix/site/production/docs/5.0.x/user/what-is-smx4.html Wed May 28 08:20:15 2014
@@ -85,7 +85,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/child-instances.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/child-instances.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/child-instances.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/child-instances.html Wed May 28 08:20:15 2014
@@ -177,7 +177,7 @@ bin/admin list
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/configuration.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/configuration.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/configuration.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/configuration.html Wed May 28 08:20:15 2014
@@ -120,7 +120,7 @@ karaf@root> config:edit foo.bar
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/deployer.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/deployer.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/deployer.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/deployer.html Wed May 28 08:20:15 2014
@@ -238,7 +238,7 @@ Export-Package =
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/directory-structure.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/directory-structure.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/directory-structure.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/directory-structure.html Wed May 28 08:20:15 2014
@@ -118,7 +118,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/failover.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/failover.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/failover.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/failover.html Wed May 28 08:20:15 2014
@@ -173,7 +173,7 @@ karaf.lock.delay=10
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/http.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/http.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/http.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/http.html Wed May 28 08:20:15 2014
@@ -135,7 +135,7 @@ root@karaf> features:install war
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/index.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/index.html Wed May 28 08:20:15 2014
@@ -118,7 +118,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/installation.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/installation.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/installation.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/installation.html Wed May 28 08:20:15 2014
@@ -139,7 +139,7 @@ tar xvf apache-karaf-x.y.tar
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/jmx.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/jmx.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/jmx.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/jmx.html Wed May 28 08:20:15 2014
@@ -118,7 +118,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/jre-tuning.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/jre-tuning.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/jre-tuning.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/jre-tuning.html Wed May 28 08:20:15 2014
@@ -417,7 +417,7 @@ jre-1.6= \
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/kar.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/kar.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/kar.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/kar.html Wed May 28 08:20:15 2014
@@ -170,7 +170,7 @@ karaf@root> features:install my
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/logging-system.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/logging-system.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/logging-system.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/logging-system.html Wed May 28 08:20:15 2014
@@ -115,54 +115,18 @@
         <div id="body">
                               <h1 id="Loggingsystem">Logging system</h1><p>Karaf provides a powerful logging system based on <a href="http://team.ops4j.org/wiki/display/paxlogging/Pax+Logging">OPS4j Pax Logging</a>. </p><p>In addition to being a standard OSGi Log service, it supports the following APIs:</p><ul><li><p>Apache Commons Logging</p></li><li><p>SLF4J</p></li><li><p>Apache Log4j</p></li><li><p>Java Util Logging</p></li></ul><p>Karaf also comes with a set of console commands that can be used to display, view and change the log levels.</p><h2 id="Configuration">Configuration</h2><h3 id="Configurationfile">Configuration file</h3><p>The configuration of the logging system uses a <a href="http://logging.apache.org/log4j/1.2/manual.html">standard Log4j configuration file</a> at the following location:</p><pre>
 [karaf_install_dir]/etc/org.ops4j.pax.logging.cfg
-</pre><p>You can edit this file at runtime and any change will be reloaded and be effective immediately.</p><h3 id="Configuringtheappenders">Configuring the appenders</h3><p>The default logging configuration defines three appenders:</p><ul><li><p>the <tt>stdout</tt> console appender is disabled by default.  If you plan to run Karaf in server mode only (i.e. with the locale console disabled), you can turn on this appender on by adding it to the list of configured appenders using the <tt>log4j.rootLogger</tt> property</p></li><li><p>the <tt>out</tt> appender is the one enabled by default. It logs events to a number of rotating log files of a fixed size.  You can easily change the parameters to control the number of files using <tt>maxBackupIndex</tt> and their size size <tt>maxFileSize</tt></p></li><li><p>the <tt>sift</tt> appender can be used instead to provide a per-bundle log file.  The default configuration uses the bundle symbolic name as the file name to log to</p></li></ul><h3 
 id="Changingtheloglevels">Changing the log levels</h3><p>The default logging configuration sets the logging levels so that the log file will provide enough information to monitor the behavior of the runtime and provide clues about what caused a problem. However, the default configuration will not provide enough information to debug most problems.</p><p>The most useful logger to change when trying to debug an issue with Karaf is the root logger. You will want to set its logging level to <tt>DEBUG</tt> in the <tt>org.ops4j.pax.logging.cfg</tt> file.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.rootLogger=DEBUG, out, osgi:VmLogAppender
-...</code></pre></div><p>When debugging a problem in Karaf you may want to change the level of logging information that is displayed on the console. The example below shows how to set the root logger to <tt>DEBUG</tt> but limiting the information displayed on the console to WARN.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.rootLogger=DEBUG, out, stdout, osgi:VmLogAppender
-log4j.appender.stdout.threshold=WARN
-...</code></pre></div><h2 id="ConsoleLogCommands">Console Log Commands</h2><p>The log subshell comes with the following commands:</p><ul><li><p><a href="../commands/log-clear.html"><tt>log:clear</tt></a>: clear the log</p></li><li><p><a href="../commands/log-display.html"><tt>log:display</tt></a>: display the last log entries</p></li><li><p><a href="../commands/log-display-exception.html"><tt>log:display-exception</tt></a>: display the last exception from the log</p></li><li><p><a href="../commands/log-get.html"><tt>log:get</tt></a>: show the log levels</p></li><li><p><a href="../commands/log-set.html"><tt>log:set</tt></a>: set the log levels</p></li><li><p><a href="../commands/log-tail.html"><tt>log:tail</tt></a>: continuous display of the log entries</p></li></ul><p>For example, if you want to debug something, you might want to run the following commands:</p><pre>
+</pre><p>You can edit this file at runtime and any change will be reloaded and be effective immediately.</p><h3 id="Configuringtheappenders">Configuring the appenders</h3><p>The default logging configuration defines three appenders:</p><ul><li><p>the <tt>stdout</tt> console appender is disabled by default.  If you plan to run Karaf in server mode only (i.e. with the locale console disabled), you can turn on this appender on by adding it to the list of configured appenders using the <tt>log4j.rootLogger</tt> property</p></li><li><p>the <tt>out</tt> appender is the one enabled by default. It logs events to a number of rotating log files of a fixed size.  You can easily change the parameters to control the number of files using <tt>maxBackupIndex</tt> and their size size <tt>maxFileSize</tt></p></li><li><p>the <tt>sift</tt> appender can be used instead to provide a per-bundle log file.  The default configuration uses the bundle symbolic name as the file name to log to</p></li></ul><h3 
 id="Changingtheloglevels">Changing the log levels</h3><p>The default logging configuration sets the logging levels so that the log file will provide enough information to monitor the behavior of the runtime and provide clues about what caused a problem. However, the default configuration will not provide enough information to debug most problems.</p><p>The most useful logger to change when trying to debug an issue with Karaf is the root logger. You will want to set its logging level to <tt>DEBUG</tt> in the <tt>org.ops4j.pax.logging.cfg</tt> file.</p><div class="syntax"><div class="highlight"><pre>log4j.rootLogger=DEBUG, out, osgi:VmLogAppender&#x000A;...&#x000A;</pre></div>&#x000A;</div><p>When debugging a problem in Karaf you may want to change the level of logging information that is displayed on the console. The example below shows how to set the root logger to <tt>DEBUG</tt> but limiting the information displayed on the console to WARN.</p><div class="syntax"><div class="highli
 ght"><pre>log4j.rootLogger=DEBUG, out, stdout, osgi:VmLogAppender&#x000A;log4j.appender.stdout.threshold=WARN&#x000A;...&#x000A;</pre></div>&#x000A;</div><h2 id="ConsoleLogCommands">Console Log Commands</h2><p>The log subshell comes with the following commands:</p><ul><li><p><a href="../commands/log-clear.html"><tt>log:clear</tt></a>: clear the log</p></li><li><p><a href="../commands/log-display.html"><tt>log:display</tt></a>: display the last log entries</p></li><li><p><a href="../commands/log-display-exception.html"><tt>log:display-exception</tt></a>: display the last exception from the log</p></li><li><p><a href="../commands/log-get.html"><tt>log:get</tt></a>: show the log levels</p></li><li><p><a href="../commands/log-set.html"><tt>log:set</tt></a>: set the log levels</p></li><li><p><a href="../commands/log-tail.html"><tt>log:tail</tt></a>: continuous display of the log entries</p></li></ul><p>For example, if you want to debug something, you might want to run the following comma
 nds:</p><pre>
 > log:set DEBUG
 ... do something ...
 > log:display
 </pre><p>Note that the log levels set using the <tt>log:set</tt> commands are not persistent and will be lost upon restart.<br/>To configure those in a persistent way, you should edit the configuration file mentioned above using the config commands or directly using a text editor of your choice.</p><p>The log commands has a separate configure file:</p><pre>
 [karaf_install_dir]/etc/org.apache.karaf.log.cfg
-</pre><h2 id="Advancedconfiguration">Advanced configuration</h2><p>The logging backend uses Log4j, but offer a number of additional features.</p><h3 id="Nestedfiltersappendersanderrorhandlers">Nested filters, appenders and error handlers</h3><h4 id="Filters">Filters</h4><p>Appender filters can be added using the following syntax:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.[appender-name].filter.[filter-name]=[filter-class]
-log4j.appender.[appender-name].filter.[filter-name].[option]=[value]</code></pre></div><p>Below is a real example:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.out.filter.f1=org.apache.log4j.varia.LevelRangeFilter
-log4j.appender.out.filter.f1.LevelMax=FATAL
-log4j.appender.out.filter.f1.LevelMin=DEBUG</code></pre></div><h4 id="Nestedappenders">Nested appenders</h4><p>Nested appenders can be added using the following syntax:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.[appender-name].appenders=[comma-separated-list-of-appender-names]</code></pre></div><p>Below is a real example:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.async=org.apache.log4j.AsyncAppender
-log4j.appender.async.appenders=jms
-
-log4j.appender.jms=org.apache.log4j.net.JMSAppender
-...</code></pre></div><h4 id="Errorhandlers">Error handlers</h4><p>Error handlers can be added using the following syntax:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.[appender-name].errorhandler=[error-handler-class]
-log4j.appender.[appender-name].errorhandler.root-ref=[true|false]
-log4j.appender.[appender-name].errorhandler.logger-ref=[logger-ref]
-log4j.appender.[appender-name].errorhandler.appender-ref=[appender-ref]</code></pre></div><h3 id="OSGispecificMDCattributes">OSGi specific MDC attributes</h3><p>Pax-Logging provides the following attributes by default:</p><ul><li><p><tt>bundle.id</tt>: the id of the bundle from which the class is loaded</p></li><li><p><tt>bundle.name</tt>: the symbolic-name of the bundle</p></li><li><p><tt>bundle.version</tt>: the version of the bundle</p></li></ul><p>An MDC sifting appender is available to split the log events based on MDC attributes.  Below is a configuration example for this appender:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-log4j.appender.sift=org.apache.log4j.sift.MDCSiftingAppender
-log4j.appender.sift.key=bundle.name
-log4j.appender.sift.default=karaf
-log4j.appender.sift.appender=org.apache.log4j.FileAppender
-log4j.appender.sift.appender.layout=org.apache.log4j.PatternLayout
-log4j.appender.sift.appender.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n
-log4j.appender.sift.appender.file=${karaf.data}/log/$\\{bundle.name\\}.log
-log4j.appender.sift.appender.append=true</code></pre></div><h3 id="EnhancedOSGistacktracerenderer">Enhanced OSGi stack trace renderer</h3><p>This renderer is configured by default in Karaf and will give additional informations when printing stack traces.<br/>For each line of the stack trace, it will display OSGi specific informations related to the class on that line: the bundle id, the bundle symbolic name and the bundle version.  This information can greatly help diagnosing problems in some cases.<br/>The information is appended at the end of each line in the following format <tt><a href="id:name:version">id:name:version</a></tt> as shown below</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-java.lang.IllegalArgumentException: Command not found:  *:foo
-	at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:225)[21:org.apache.karaf.shell.console:2.1.0]
-	at org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[21:org.apache.karaf.shell.console:2.1.0]
-	at org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[21:org.apache.karaf.shell.console:2.1.0]
-	at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[21:org.apache.karaf.shell.console:2.1.0]
-	at org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[21:org.apache.karaf.shell.console:2.1.0]
-	at org.apache.karaf.shell.console.jline.Console.run(Console.java:169)[21:org.apache.karaf.shell.console:2.1.0]
-	at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]</code></pre></div><h3 id="Usingyourownappenders">Using your own appenders</h3><p>If you plan to use your own appenders, you need to create an OSGi bundle and attach it as a fragment to the bundle with a symbolic name of <br/><tt>org.ops4j.pax.logging.pax-logging-service</tt>.  This way, the underlying logging system will be able to see and use your appenders.</p><p>So for example you write a log4j appender:<br/>class MyAppender extends AppenderSkeleton {<br/>...<br/>}</p><p>Then you need to package the appender in a jar with a Manifest like this:</p><p>Manifest:<br/>Bundle-SymbolicName: org.mydomain.myappender       <br/>Fragment-Host: org.ops4j.pax.logging.pax-logging-service<br/>...</p><p>Copy the new appender fragment into the ${karaf.home}/system directory. Karaf uses a virtual maven repository to access resources in the system<br/>directory, so the jar path should use the standard maven groupId/artifactId/version/ convention,
  where the groupId is a directory structure.</p><p>Edit ${karaf.home}/etc/startup.properties and add the new fragment bundle to the list before the pax-logging-service bundle.</p><p>Restart karaf with a clean run to reload the system bundles, and now you can use the appender in your log4j config file like shown in the config<br/>examples above.</p>
+</pre><h2 id="Advancedconfiguration">Advanced configuration</h2><p>The logging backend uses Log4j, but offer a number of additional features.</p><h3 id="Nestedfiltersappendersanderrorhandlers">Nested filters, appenders and error handlers</h3><h4 id="Filters">Filters</h4><p>Appender filters can be added using the following syntax:</p><div class="syntax"><div class="highlight"><pre>log4j.appender.[appender-name].filter.[filter-name]=[filter-class]&#x000A;log4j.appender.[appender-name].filter.[filter-name].[option]=[value]&#x000A;</pre></div>&#x000A;</div><p>Below is a real example:</p><div class="syntax"><div class="highlight"><pre>log4j.appender.out.filter.f1=org.apache.log4j.varia.LevelRangeFilter&#x000A;log4j.appender.out.filter.f1.LevelMax=FATAL&#x000A;log4j.appender.out.filter.f1.LevelMin=DEBUG&#x000A;</pre></div>&#x000A;</div><h4 id="Nestedappenders">Nested appenders</h4><p>Nested appenders can be added using the following syntax:</p><div class="syntax"><div class="highlight"><p
 re>log4j.appender.[appender-name].appenders=[comma-separated-list-of-appender-names]&#x000A;</pre></div>&#x000A;</div><p>Below is a real example:</p><div class="syntax"><div class="highlight"><pre>log4j.appender.async=org.apache.log4j.AsyncAppender&#x000A;log4j.appender.async.appenders=jms&#x000A;&#x000A;log4j.appender.jms=org.apache.log4j.net.JMSAppender&#x000A;...&#x000A;</pre></div>&#x000A;</div><h4 id="Errorhandlers">Error handlers</h4><p>Error handlers can be added using the following syntax:</p><div class="syntax"><div class="highlight"><pre>log4j.appender.[appender-name].errorhandler=[error-handler-class]&#x000A;log4j.appender.[appender-name].errorhandler.root-ref=[true|false]&#x000A;log4j.appender.[appender-name].errorhandler.logger-ref=[logger-ref]&#x000A;log4j.appender.[appender-name].errorhandler.appender-ref=[appender-ref]&#x000A;</pre></div>&#x000A;</div><h3 id="OSGispecificMDCattributes">OSGi specific MDC attributes</h3><p>Pax-Logging provides the following attributes 
 by default:</p><ul><li><p><tt>bundle.id</tt>: the id of the bundle from which the class is loaded</p></li><li><p><tt>bundle.name</tt>: the symbolic-name of the bundle</p></li><li><p><tt>bundle.version</tt>: the version of the bundle</p></li></ul><p>An MDC sifting appender is available to split the log events based on MDC attributes.  Below is a configuration example for this appender:</p><div class="syntax"><div class="highlight"><pre>log4j.appender.sift=org.apache.log4j.sift.MDCSiftingAppender&#x000A;log4j.appender.sift.key=bundle.name&#x000A;log4j.appender.sift.default=karaf&#x000A;log4j.appender.sift.appender=org.apache.log4j.FileAppender&#x000A;log4j.appender.sift.appender.layout=org.apache.log4j.PatternLayout&#x000A;log4j.appender.sift.appender.layout.ConversionPattern=%d{ABSOLUTE} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %m%n&#x000A;log4j.appender.sift.appender.file=${karaf.data}/log/$\\{bundle.name\\}.log&#x000A;log4j.appender.sift.appender.append=true&#x000A;</pre>
 </div>&#x000A;</div><h3 id="EnhancedOSGistacktracerenderer">Enhanced OSGi stack trace renderer</h3><p>This renderer is configured by default in Karaf and will give additional informations when printing stack traces.<br/>For each line of the stack trace, it will display OSGi specific informations related to the class on that line: the bundle id, the bundle symbolic name and the bundle version.  This information can greatly help diagnosing problems in some cases.<br/>The information is appended at the end of each line in the following format <tt><a href="id:name:version">id:name:version</a></tt> as shown below</p><div class="syntax"><div class="highlight"><pre>java.lang.IllegalArgumentException: Command not found:  *:foo&#x000A;	at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:225)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:162)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at org.
 apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:101)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:79)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at org.apache.karaf.shell.console.jline.Console.run(Console.java:169)[21:org.apache.karaf.shell.console:2.1.0]&#x000A;	at java.lang.Thread.run(Thread.java:637)[:1.6.0_20]&#x000A;</pre></div>&#x000A;</div><h3 id="Usingyourownappenders">Using your own appenders</h3><p>If you plan to use your own appenders, you need to create an OSGi bundle and attach it as a fragment to the bundle with a symbolic name of <br/><tt>org.ops4j.pax.logging.pax-logging-service</tt>.  This way, the underlying logging system will be able to see and use your appenders.</p><p>So for example you write a log4j appender:<br/>class MyAppender extends Ap
 penderSkeleton {<br/>...<br/>}</p><p>Then you need to package the appender in a jar with a Manifest like this:</p><p>Manifest:<br/>Bundle-SymbolicName: org.mydomain.myappender       <br/>Fragment-Host: org.ops4j.pax.logging.pax-logging-service<br/>...</p><p>Copy the new appender fragment into the ${karaf.home}/system directory. Karaf uses a virtual maven repository to access resources in the system<br/>directory, so the jar path should use the standard maven groupId/artifactId/version/ convention, where the groupId is a directory structure.</p><p>Edit ${karaf.home}/etc/startup.properties and add the new fragment bundle to the list before the pax-logging-service bundle.</p><p>Restart karaf with a clean run to reload the system bundles, and now you can use the appender in your log4j config file like shown in the config<br/>examples above.</p>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/provisioning.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/provisioning.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/provisioning.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/provisioning.html Wed May 28 08:20:15 2014
@@ -231,7 +231,7 @@ features:addUrl file:base/features/featu
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/remote-console.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/remote-console.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/remote-console.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/remote-console.html Wed May 28 08:20:15 2014
@@ -165,7 +165,7 @@ bin/client -u karaf -p karaf -a 8101 hos
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/security.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/security.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/security.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/security.html Wed May 28 08:20:15 2014
@@ -135,7 +135,7 @@ org.osgi.framework.bootdelegation = ...,
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/start-stop.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/start-stop.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/start-stop.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/start-stop.html Wed May 28 08:20:15 2014
@@ -150,7 +150,7 @@ bin/stop
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/toc.html Wed May 28 08:20:15 2014
@@ -161,7 +161,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/using-console.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/using-console.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/using-console.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/using-console.html Wed May 28 08:20:15 2014
@@ -192,7 +192,7 @@ OPTIONS
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/web-applications.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/web-applications.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/web-applications.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/web-applications.html Wed May 28 08:20:15 2014
@@ -181,7 +181,7 @@ karaf@root> osgi:install -s webbundle:ht
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/web-console.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/web-console.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/web-console.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/web-console.html Wed May 28 08:20:15 2014
@@ -124,7 +124,7 @@ org.osgi.service.http.port=8181
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/users-guide/wrapper.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/users-guide/wrapper.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/users-guide/wrapper.html (original)
+++ servicemix/site/production/docs/5.0.x/users-guide/wrapper.html Wed May 28 08:20:15 2014
@@ -201,7 +201,7 @@ On Ubuntu/Debian Systems:
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>



Mime
View raw message