servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ksobkow...@apache.org
Subject svn commit: r1595363 [9/9] - in /servicemix/site/production/docs/5.0.x: activemq/ activiti/ camel/ camel/deployment/ commands/ developers-guide/ karaf/ quickstart/ user/ users-guide/
Date Fri, 16 May 2014 21:50:34 GMT
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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="KarafUsersGuide">Karaf Users Guide</h1><ul><li><p><a href="installation.html">Installing Karaf</a></p></li><li><p><a href="directory-structure.html">Directory Structure</a></p></li><li><p><a href="start-stop.html">Starting and stopping Karaf</a></p></li><li><p><a href="using-console.html">Using the console</a></p></li><li><p><a href="wrapper.html">Service Wrapper</a></p></li><li><p><a href="web-console.html">Web console</a></p></li><li><p><a href="remote-console.html">Remote console</a></p></li><li><p><a href="child-instances.html">Child instances</a></p></li><li><p><a href="security.html">Security</a></p></li><li><p><a href="failover.html">Failover Deployments</a></p></li><li><p><a href="logging-system.html">Logging system</a></p></li><li><p><a href="deployer.html">Deployer</a></p></li><li><p><a href="provisioning.html">Provisioning</a><br/>*&#xa0;<a href="provisioning-schema.html">Provisioning Schema</a></p></li><li><p><a href="kar.html">Karaf Archive</
 a></p></li><li><p><a href="configuration.html">Configuration</a></p></li><li><p><a href="http.html">Pax Web (OSGi HttpService)</a></p></li><li><p><a href="web-applications.html">Web applications</a></p></li><li><p><a href="wrapper.html">OS integration</a></p></li><li><p><a href="jre-tuning.html">JRE packages tuning</a></p></li><li><p><a href="jmx.html">Monitoring and Administration using JMX</a></p></li></ul>
+                              <h1 id="KarafUsersGuide">Karaf Users Guide</h1><ul><li><p><a href="installation.html">Installing Karaf</a></p></li><li><p><a href="directory-structure.html">Directory Structure</a></p></li><li><p><a href="start-stop.html">Starting and stopping Karaf</a></p></li><li><p><a href="using-console.html">Using the console</a></p></li><li><p><a href="wrapper.html">Service Wrapper</a></p></li><li><p><a href="web-console.html">Web console</a></p></li><li><p><a href="remote-console.html">Remote console</a></p></li><li><p><a href="child-instances.html">Child instances</a></p></li><li><p><a href="security.html">Security</a></p></li><li><p><a href="failover.html">Failover Deployments</a></p></li><li><p><a href="logging-system.html">Logging system</a></p></li><li><p><a href="deployer.html">Deployer</a></p></li><li><p><a href="provisioning.html">Provisioning</a><br/>*&#xa0;<a href="provisioning-schema.html">Provisioning Schema</a></p></li><li><p><a href="kar.html">Karaf
  Archive</a></p></li><li><p><a href="configuration.html">Configuration</a></p></li><li><p><a href="http.html">Pax Web (OSGi HttpService)</a></p></li><li><p><a href="web-applications.html">Web applications</a></p></li><li><p><a href="wrapper.html">OS integration</a></p></li><li><p><a href="jre-tuning.html">JRE packages tuning</a></p></li><li><p><a href="jmx.html">Monitoring and Administration using JMX</a></p></li></ul>
         </div>
       
           </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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Installation">Installation</h1><p>This chapter describes how to install Apache Karaf for both Unix and Windows platforms, including<br/>prerequisite software and necessary download links.</p><h2 id="PreInstallationRequirements">Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li><p>20 MB of free disk space for the Apache Karaf x.y binary distribution.</p></li></ul><p><strong>Operating Systems:</strong></p><ul><li><p>Windows: Windows Vista, Windows XP SP2, Windows 2000.</p></li><li><p>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, any Unix platform that supports Java.</p></li></ul><p><strong>Environment:</strong></p><ul><li><p>Java SE Development Kit 1.5.x or greater (<a href="http://www.oracle.com/technetwork/java/javase/">http://www.oracle.com/technetwork/java/javase/</a>).</p></li><li><p>The JAVA_HOME environment variable must be set to the directory where the Java runtime is installed, e.g., <tt>c:\Program Files\
 jdk.1.5.0_06</tt>. To accomplish that, press Windows key and Break key together, switch to "Advanced" tab and click on "Environment Variables". Here, check for the variable and, if necessary, add it.</p></li></ul><h2 id="BuildingfromSources">Building from Sources</h2><p>If you intend to build Karaf from the sources, the requirements are a bit different:</p><p><strong>Hardware:</strong></p><ul><li><p>200 MB of free disk space for the Apache Karaf x.y source distributions or SVN checkout, the Maven build and the dependencies Maven downloads.</p></li></ul><p><strong>Environment:</strong></p><ul><li><p>Java SE Developement Kit 1.5.x or greater (<a href="http://www.oracle.com/technetwork/java/javase/">http://www.oracle.com/technetwork/java/javase/</a>).</p></li><li><p>Apache Maven 2.2.1 (<a href="http://maven.apache.org/download.html">http://maven.apache.org/download.html</a>).</p></li></ul><h3 id="BuildingonWindows">Building on Windows</h3><p>This procedure explains how to download and 
 install the source distribution on a Windows system. <strong>NOTE:</strong> Karaf requires Java 5 is compile, build and run.</p><ol><li><p>From a browser, navigate to <a href="http://karaf.apache.org/index/community/download.html">http://karaf.apache.org/index/community/download.html</a>.</p></li><li><p>Scroll down to the "Apache Karaf" section and select the desired distribution.<br/>For a source distribution, the filename will be similar to: <tt>apache-karaf-x.y-src.zip</tt>.</p></li><li><p>Extract Karaf from the ZIP file into a directory of your choice. Please remember the restrictions concerning illegal characters in Java paths, e.g. !, % etc.</p></li><li><p><span id="WindowsSourceInstallation"></span> Build Karaf using Maven 2.2.1 or greater and Java 5.<br/>The recommended method of building Karaf is the following:</p><pre>
+                              <h1 id="Installation">Installation</h1><p>This chapter describes how to install Apache Karaf for both Unix and Windows platforms, including<br/>prerequisite software and necessary download links.</p><h2 id="PreInstallationRequirements">Pre-Installation Requirements</h2><p><strong>Hardware:</strong></p><ul><li><p>20 MB of free disk space for the Apache Karaf x.y binary distribution.</p></li></ul><p><strong>Operating Systems:</strong></p><ul><li><p>Windows: Windows Vista, Windows XP SP2, Windows 2000.</p></li><li><p>Unix: Ubuntu Linux, Powerdog Linux, MacOS, AIX, HP-UX, Solaris, any Unix platform that supports Java.</p></li></ul><p><strong>Environment:</strong></p><ul><li><p>Java SE Development Kit 1.5.x or greater (<a href="http://www.oracle.com/technetwork/java/javase/">http://www.oracle.com/technetwork/java/javase/</a>).</p></li><li><p>The JAVA_HOME environment variable must be set to the directory where the Java runtime is installed, e.g., <tt>c:\Prog
 ram Files\jdk.1.5.0_06</tt>. To accomplish that, press Windows key and Break key together, switch to "Advanced" tab and click on "Environment Variables". Here, check for the variable and, if necessary, add it.</p></li></ul><h2 id="BuildingfromSources">Building from Sources</h2><p>If you intend to build Karaf from the sources, the requirements are a bit different:</p><p><strong>Hardware:</strong></p><ul><li><p>200 MB of free disk space for the Apache Karaf x.y source distributions or SVN checkout, the Maven build and the dependencies Maven downloads.</p></li></ul><p><strong>Environment:</strong></p><ul><li><p>Java SE Developement Kit 1.5.x or greater (<a href="http://www.oracle.com/technetwork/java/javase/">http://www.oracle.com/technetwork/java/javase/</a>).</p></li><li><p>Apache Maven 2.2.1 (<a href="http://maven.apache.org/download.html">http://maven.apache.org/download.html</a>).</p></li></ul><h3 id="BuildingonWindows">Building on Windows</h3><p>This procedure explains how to dow
 nload and install the source distribution on a Windows system. <strong>NOTE:</strong> Karaf requires Java 5 is compile, build and run.</p><ol><li><p>From a browser, navigate to <a href="http://karaf.apache.org/index/community/download.html">http://karaf.apache.org/index/community/download.html</a>.</p></li><li><p>Scroll down to the "Apache Karaf" section and select the desired distribution.<br/>For a source distribution, the filename will be similar to: <tt>apache-karaf-x.y-src.zip</tt>.</p></li><li><p>Extract Karaf from the ZIP file into a directory of your choice. Please remember the restrictions concerning illegal characters in Java paths, e.g. !, % etc.</p></li><li><p><span id="WindowsSourceInstallation"></span> Build Karaf using Maven 2.2.1 or greater and Java 5.<br/>The recommended method of building Karaf is the following:</p><pre>
 cd [karaf_install_dir]\src
 </pre><p> where <tt>[karaf_install_dir]</tt> is the directory in which Karaf was installed.</p><pre>
 mvn

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="MonitoringandAdministrationusingJMX">Monitoring and Administration using JMX</h1><p>Apache Karaf provides a large set of MBeans that allow you to fully monitore and administrate Karaf using any JMX client<br/>(like jconsole for instance).</p><p>You can find more or less the same actions that you can do using the shell commands on the JMX layer.</p><p>Apache Karaf provides the following MBeans:</p><ul><li><p>org.apache.karaf:type=admin to administrate the child instances</p></li><li><p>org.apache.karaf:type=bundles to manipulate the OSGi bundles</p></li><li><p>org.apache.karaf:type=config to manipulate the Karaf configuration files (in the etc folder) and the ConfigAdmin layer</p></li><li><p>org.apache.karaf:type=dev to get information and manipulate the OSGi framework</p></li><li><p>org.apache.karaf:type=diagnostic to create information file (dump) about Karaf activity</p></li><li><p>org.apache.karaf:type=features to manipulate the Karaf features</p></li>
 <li><p>org.apache.karaf:type=log to manipulate to logging layer</p></li><li><p>org.apache.karaf:type=packages to manipulate to PackageAdmin layer and get information about exported and imported packages</p></li><li><p>org.apache.karaf:type=services to get information about the OSGi services</p></li><li><p>org.apache.karaf:type=system to shutdown the Karaf container itself</p></li><li><p>org.apache.karaf:type=web to get information about the Web bundles (installed with the war feature)</p></li><li><p>org.apache.karaf:type=obr to manipulate the OBR layer (installed with the obr feature)</p></li></ul>
+                              <h1 id="MonitoringandAdministrationusingJMX">Monitoring and Administration using JMX</h1><p>Apache Karaf provides a large set of MBeans that allow you to fully monitore and administrate Karaf using any JMX client<br/>(like jconsole for instance).</p><p>You can find more or less the same actions that you can do using the shell commands on the JMX layer.</p><p>Apache Karaf provides the following MBeans:</p><ul><li><p>org.apache.karaf:type=admin to administrate the child instances</p></li><li><p>org.apache.karaf:type=bundles to manipulate the OSGi bundles</p></li><li><p>org.apache.karaf:type=config to manipulate the Karaf configuration files (in the etc folder) and the ConfigAdmin layer</p></li><li><p>org.apache.karaf:type=dev to get information and manipulate the OSGi framework</p></li><li><p>org.apache.karaf:type=diagnostic to create information file (dump) about Karaf activity</p></li><li><p>org.apache.karaf:type=features to manipulate the Karaf feature
 s</p></li><li><p>org.apache.karaf:type=log to manipulate to logging layer</p></li><li><p>org.apache.karaf:type=packages to manipulate to PackageAdmin layer and get information about exported and imported packages</p></li><li><p>org.apache.karaf:type=services to get information about the OSGi services</p></li><li><p>org.apache.karaf:type=system to shutdown the Karaf container itself</p></li><li><p>org.apache.karaf:type=web to get information about the Web bundles (installed with the war feature)</p></li><li><p>org.apache.karaf:type=obr to manipulate the OBR layer (installed with the obr feature)</p></li></ul>
         </div>
       
           </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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="JREandsystempackagestuning">JRE and system packages tuning</h1><p>Some packages are part of the JRE, but could be provided by tier libraries.</p><p>Some examples of package in this case are:</p><ul><li><p><tt>javax.xml.stream</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles (and the implementation of provided by Woodstox).</p></li><li><p><tt>com.sun.org.apache.xerces.internal.dom</tt> package is provided by the JRE, but also by Apache Xerces.</p></li><li><p><tt>javax.activation</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles.</p></li><li><p><tt>javax.annotation</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles.</p></li><li><p>etc ...</p></li></ul><p>We should define in the Karaf instance which packages should be provided by the JRE or by tier bundles.</p><p>Moreover, we should manage the exported packages of JRE depending of the JRE version: the JRE 1.6 provides more pa
 ckages<br/>than the 1.5 one.</p><p>To customize this in Karaf, you can tune the <tt>etc/jre.properties</tt> file.</p><p>In the <tt>etc/jre.properties</tt> file, you have two properties <tt>jre-1.5</tt> and <tt>jre-1.6</tt>.</p><p>They allow you to define the packages exported by the JRE (in function of the runtime version).<br/>Each property provide the exhaustive list of packages provided by the JRE (and so part of the sytem packages).</p><p>For instance, a "standard" Karaf distribution provides the following <tt>etc/jre.properties</tt>:</p><pre>
+                              <h1 id="JREandsystempackagestuning">JRE and system packages tuning</h1><p>Some packages are part of the JRE, but could be provided by tier libraries.</p><p>Some examples of package in this case are:</p><ul><li><p><tt>javax.xml.stream</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles (and the implementation of provided by Woodstox).</p></li><li><p><tt>com.sun.org.apache.xerces.internal.dom</tt> package is provided by the JRE, but also by Apache Xerces.</p></li><li><p><tt>javax.activation</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles.</p></li><li><p><tt>javax.annotation</tt> package is provided by the JRE, but also by Apache Geronimo Spec bundles.</p></li><li><p>etc ...</p></li></ul><p>We should define in the Karaf instance which packages should be provided by the JRE or by tier bundles.</p><p>Moreover, we should manage the exported packages of JRE depending of the JRE version: the JRE 1.6 provid
 es more packages<br/>than the 1.5 one.</p><p>To customize this in Karaf, you can tune the <tt>etc/jre.properties</tt> file.</p><p>In the <tt>etc/jre.properties</tt> file, you have two properties <tt>jre-1.5</tt> and <tt>jre-1.6</tt>.</p><p>They allow you to define the packages exported by the JRE (in function of the runtime version).<br/>Each property provide the exhaustive list of packages provided by the JRE (and so part of the sytem packages).</p><p>For instance, a "standard" Karaf distribution provides the following <tt>etc/jre.properties</tt>:</p><pre>
 #
 # Java platform package export properties.
 #

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="KarafArchivesKAR">Karaf Archives (KAR)</h1><p>Karaf provides a specific archive format named the KAR (Karaf ARchive).</p><p>Basically, the kar format is a jar (so a zip file) which contains a set of feature descriptor and bundle jar files.</p><p>For instance, a kar looks like:</p><ul><li><p>my-features-1.xml</p></li><li><p>bundle1.jar</p></li><li><p>bundle2.jar</p></li><li><p>bundle3.jar</p></li></ul><p>all packaged in zip format.</p><h2 id="Createakararchive">Create a kar archive</h2><p>You can create a kar file by hand, just by zip compressing a directory representing the kar content.</p><p>You can also use the Karaf features maven plugin. The features maven plugin provides an create-kar goal.</p><p>The kar-archive goal:<br/>1. Reads all features specified in the features descriptor.<br/>2. For each feature, it resolves the bundles defined in the feature.<br/>3. All bundles are packaged into the kar archive.</p><p>For instance, you can use the following
  POM to create a kar:</p><pre>
+                              <h1 id="KarafArchivesKAR">Karaf Archives (KAR)</h1><p>Karaf provides a specific archive format named the KAR (Karaf ARchive).</p><p>Basically, the kar format is a jar (so a zip file) which contains a set of feature descriptor and bundle jar files.</p><p>For instance, a kar looks like:</p><ul><li><p>my-features-1.xml</p></li><li><p>bundle1.jar</p></li><li><p>bundle2.jar</p></li><li><p>bundle3.jar</p></li></ul><p>all packaged in zip format.</p><h2 id="Createakararchive">Create a kar archive</h2><p>You can create a kar file by hand, just by zip compressing a directory representing the kar content.</p><p>You can also use the Karaf features maven plugin. The features maven plugin provides an create-kar goal.</p><p>The kar-archive goal:<br/>1. Reads all features specified in the features descriptor.<br/>2. For each feature, it resolves the bundles defined in the feature.<br/>3. All bundles are packaged into the kar archive.</p><p>For instance, you can use the
  following POM to create a kar:</p><pre>
 &lt;?xml version="1.0" encoding="UTF-8"?>
 &lt;project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
 

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,15 +113,51 @@
 
         </div>
         <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>
+                              <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"><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>
+</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>
 > 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"><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>
+</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>
         </div>
       
           </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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Provisioning">Provisioning</h1><p>Karaf provides a simple, yet flexible, way to provision applications or "features".  Such a mechanism is mainly provided by a set of commands available in the <tt>features</tt> shell.  The provisioning system uses xml "repositories" that define a set of features.</p><h2 id="Repositories">Repositories</h2><p>The complete xml schema for feature descriptor are available on <a href="provisioning-schema.html">Features XML Schema</a> page. We recommend using this XML schema. It will allow Karaf to validate your repository before parsing. You may also verify your descriptor before adding it to Karaf by simply validation, even from IDE level.</p><p>Here is an example of such a repository:</p><pre>
+                              <h1 id="Provisioning">Provisioning</h1><p>Karaf provides a simple, yet flexible, way to provision applications or "features".  Such a mechanism is mainly provided by a set of commands available in the <tt>features</tt> shell.  The provisioning system uses xml "repositories" that define a set of features.</p><h2 id="Repositories">Repositories</h2><p>The complete xml schema for feature descriptor are available on <a href="provisioning-schema.html">Features XML Schema</a> page. We recommend using this XML schema. It will allow Karaf to validate your repository before parsing. You may also verify your descriptor before adding it to Karaf by simply validation, even from IDE level.</p><p>Here is an example of such a repository:</p><pre>
 &lt;features xmlns="http://karaf.apache.org/xmlns/features/v1.0.0">
     &lt;feature name="spring" version="3.0.4.RELEASE">
         &lt;bundle>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.aopalliance/1.0_1&lt;/bundle>

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Usingremoteinstances">Using remote instances</h1><h2 id="Configuringremoteinstances">Configuring remote instances</h2><p>It does not always make sense to manage an instance of Karaf using its local console. You can manage Karaf remotely using a remote console.</p><p>When you start Karaf, it enables a remote console that can be accessed over SSH from any other Karaf console or plain SSH client.  The remote console provides all the features of the local console and gives a remote user complete control over the container and services running inside of it.</p><p>The SSH hostname and port number is configured in the <tt>[karaf_install_dir]/etc/org.apache.karaf.shell.cfg</tt> configuration file with the following default values:</p><pre>
+                              <h1 id="Usingremoteinstances">Using remote instances</h1><h2 id="Configuringremoteinstances">Configuring remote instances</h2><p>It does not always make sense to manage an instance of Karaf using its local console. You can manage Karaf remotely using a remote console.</p><p>When you start Karaf, it enables a remote console that can be accessed over SSH from any other Karaf console or plain SSH client.  The remote console provides all the features of the local console and gives a remote user complete control over the container and services running inside of it.</p><p>The SSH hostname and port number is configured in the <tt>[karaf_install_dir]/etc/org.apache.karaf.shell.cfg</tt> configuration file with the following default values:</p><pre>
 sshPort=8101
 sshHost=0.0.0.0
 sshRealm=karaf

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Security">Security</h1><h2 id="Managingusersandpasswords">Managing users and passwords</h2><p>The default security configuration uses a property file located at <tt><a href="karaf-install-dir.html">karaf-install-dir</a>/etc/users.properties</tt> to store authorized users and their passwords.</p><p>The default user name is <tt>karaf</tt> and the associated password is <tt>karaf</tt> too.  We strongly encourage you to change the default password by editing the above file before moving Karaf into production.</p><p>The users are currently used in three different places in Karaf:</p><ul><li><p>access to the SSH console</p></li><li><p>access to the JMX management layer</p></li><li><p>access to the Web console<br/>Those three ways all delegate to the same JAAS based security authentication.</p></li></ul><p>The <tt>users.properties</tt> file contains one or more lines, each line defining a user, its password and the associated roles.</p><pre>
+                              <h1 id="Security">Security</h1><h2 id="Managingusersandpasswords">Managing users and passwords</h2><p>The default security configuration uses a property file located at <tt><a href="karaf-install-dir.html">karaf-install-dir</a>/etc/users.properties</tt> to store authorized users and their passwords.</p><p>The default user name is <tt>karaf</tt> and the associated password is <tt>karaf</tt> too.  We strongly encourage you to change the default password by editing the above file before moving Karaf into production.</p><p>The users are currently used in three different places in Karaf:</p><ul><li><p>access to the SSH console</p></li><li><p>access to the JMX management layer</p></li><li><p>access to the Web console<br/>Those three ways all delegate to the same JAAS based security authentication.</p></li></ul><p>The <tt>users.properties</tt> file contains one or more lines, each line defining a user, its password and the associated roles.</p><pre>
 user=password[,role][,role]...
 </pre><h2 id="Managingroles">Managing roles</h2><p>JAAS roles can be used by various components. The three management layers (SSH, JMX and WebConsole) all use a global role based authorization system. The default role name is configured in the <tt>etc/system.properties</tt> using the <tt>karaf.admin.role</tt> system property and the default value is <tt>admin</tt>. All users authenticating for the management layer must have this role defined.</p><p>The syntax for this value is the following:</p><pre>
 [classname:]principal

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="StartingandStoppingKaraf">Starting and Stopping Karaf</h1><p>This chapter describes how to start and stop Apache Karaf and the various options that are available.</p><h2 id="StartingKaraf">Starting Karaf</h2><h3 id="OnWindows">On Windows</h3><p>From a console window, change to the installation directory and run <tt>Karaf</tt>. For the binary distribution, go to</p><pre>
+                              <h1 id="StartingandStoppingKaraf">Starting and Stopping Karaf</h1><p>This chapter describes how to start and stop Apache Karaf and the various options that are available.</p><h2 id="StartingKaraf">Starting Karaf</h2><h3 id="OnWindows">On Windows</h3><p>From a console window, change to the installation directory and run <tt>Karaf</tt>. For the binary distribution, go to</p><pre>
 cd [karaf_install_dir]
 </pre><p>where <tt>karaf_install_dir</tt> is the directory in which Karaf was installed, e.g., <tt>c:\Program Files\apache-karaf-x.y</tt>.</p><p>Then type:</p><pre>
 bin\karaf.bat

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <ul>
+                              <ul>
   <li id="karaf-users-guide">
     <a href="#">User's Guide</a>
     <ul>

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Usingtheconsole">Using the console</h1><h2 id="Viewingavailablecommands">Viewing available commands</h2><p>To see a list of the available commands in the console press the <tt>&lt;tab></tt> key at the prompt.</p><pre>
+                              <h1 id="Usingtheconsole">Using the console</h1><h2 id="Viewingavailablecommands">Viewing available commands</h2><p>To see a list of the available commands in the console press the <tt>&lt;tab></tt> key at the prompt.</p><pre>
 root@root> Display all 182 possibilities? (y or n)
 *:help                           addurl                           admin:change-opts
 admin:change-rmi-registry-port   admin:change-ssh-port            admin:connect

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Webapplications">Web applications</h1><h2 id="Installingwarsupport">Installing war support</h2><p>The following steps will install the "war" feature (support for deploying WAR files with Servlet and JSPs into a Jetty server) into your Karaf instance.</p><ol><li><p>List the available features -</p><pre>karaf@root> features:list 
+                              <h1 id="Webapplications">Web applications</h1><h2 id="Installingwarsupport">Installing war support</h2><p>The following steps will install the "war" feature (support for deploying WAR files with Servlet and JSPs into a Jetty server) into your Karaf instance.</p><ol><li><p>List the available features -</p><pre>karaf@root> features:list 
  State        Name
 . . .
 [uninstalled] [2.2.0] obr        karaf-2.2.0

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="Webconsole">Web console</h1><p>The Karaf web console provides a graphical overview of the runtime.<br/>You can use it to:</p><ul><li><p>install and uninstall features</p></li><li><p>start, stop, install bundles</p></li><li><p>create child instances</p></li><li><p>configure Karaf</p></li><li><p>view logging informations</p></li></ul><h2 id="Installingthewebconsole">Installing the web console</h2><p>The web console is not installed by default.  To install it, run the following command from the Karaf prompt:</p><pre>
+                              <h1 id="Webconsole">Web console</h1><p>The Karaf web console provides a graphical overview of the runtime.<br/>You can use it to:</p><ul><li><p>install and uninstall features</p></li><li><p>start, stop, install bundles</p></li><li><p>create child instances</p></li><li><p>configure Karaf</p></li><li><p>view logging informations</p></li></ul><h2 id="Installingthewebconsole">Installing the web console</h2><p>The web console is not installed by default.  To install it, run the following command from the Karaf prompt:</p><pre>
 root@karaf> features:install webconsole
 </pre><h2 id="Accessingthewebconsole">Accessing the web console</h2><p>To access the console for an instance of Karaf running locally, enter the following address in your web browser:</p><pre>
 http://localhost:8181/system/console

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=1595363&r1=1595362&r2=1595363&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 Fri May 16 21:50:31 2014
@@ -113,7 +113,7 @@
 
         </div>
         <div id="body">
-                    <h1 id="ServiceWrapper">Service Wrapper</h1><h2 id="Introduction">Introduction</h2><p>The Karaf Wrapper (for service wrapper) makes it possible to install Karaf as a Windows Service. Likewise, the scripts shipped with Karaf also make it very easy to install Karaf as a daemon process on Unix systems.</p><p>The Wrapper correctly handles "user's log outs" under Windows, service dependencies, and the ability to run services which interact with the desktop.</p><h2 id="Supportedplatforms">Supported platforms</h2><p>The following platforms are supported by the Karaf Wrapper:</p><ul><li><p>AIX</p></li><li><p>FreeBSD</p></li><li><p>HP-UX, 32-bit and 64-bit versions</p></li><li><p>SGI Irix</p></li><li><p>Linux kernels 2.2.x, 2.4.x, 2.6.x. Known to work with Debian, Ubuntu, and Red Hat, but should work with any distribution. Currently supported on both 32-bit and 64-bit x86, Itanium, and PPC systems.</p></li><li><p>Macintosh OS X</p></li><li><p>Sun OS, Solaris 9 and 10. Cur
 rently supported on both 32-bit and 64-bit sparc, and x86 systems.</p></li><li><p>Windows - Windows 2000, XP, 2003, Vista, 2008 and Windows 7. Currently supported on both 32-bit and 64-bit x86 and Itanium systems. Also known to run on Windows 98 and ME, however due the lack of support for services in the OS, the Wrapper can be run only in console mode.</p></li></ul><h2 id="Installation">Installation</h2><p>Karaf Wrapper is an optional feature. To install it, simply type:</p><pre>
+                              <h1 id="ServiceWrapper">Service Wrapper</h1><h2 id="Introduction">Introduction</h2><p>The Karaf Wrapper (for service wrapper) makes it possible to install Karaf as a Windows Service. Likewise, the scripts shipped with Karaf also make it very easy to install Karaf as a daemon process on Unix systems.</p><p>The Wrapper correctly handles "user's log outs" under Windows, service dependencies, and the ability to run services which interact with the desktop.</p><h2 id="Supportedplatforms">Supported platforms</h2><p>The following platforms are supported by the Karaf Wrapper:</p><ul><li><p>AIX</p></li><li><p>FreeBSD</p></li><li><p>HP-UX, 32-bit and 64-bit versions</p></li><li><p>SGI Irix</p></li><li><p>Linux kernels 2.2.x, 2.4.x, 2.6.x. Known to work with Debian, Ubuntu, and Red Hat, but should work with any distribution. Currently supported on both 32-bit and 64-bit x86, Itanium, and PPC systems.</p></li><li><p>Macintosh OS X</p></li><li><p>Sun OS, Solaris 9 a
 nd 10. Currently supported on both 32-bit and 64-bit sparc, and x86 systems.</p></li><li><p>Windows - Windows 2000, XP, 2003, Vista, 2008 and Windows 7. Currently supported on both 32-bit and 64-bit x86 and Itanium systems. Also known to run on Windows 98 and ME, however due the lack of support for services in the OS, the Wrapper can be run only in console mode.</p></li></ul><h2 id="Installation">Installation</h2><p>Karaf Wrapper is an optional feature. To install it, simply type:</p><pre>
 karaf@root> features:install wrapper
 </pre><p>Once installed, wrapper feature will provide <tt>wrapper:install</tt> new command in the Karaf shell:</p><pre>
 karaf@root> wrapper:install --help



Mime
View raw message