[jboss-cvs] JBoss Messaging SVN: r6700 - in trunk/docs: user-manual and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 7 06:34:10 EDT 2009
Author: timfox
Date: 2009-05-07 06:34:08 -0400 (Thu, 07 May 2009)
New Revision: 6700
Added:
trunk/docs/user-manual/
trunk/docs/user-manual/build.xml
trunk/docs/user-manual/en/
trunk/docs/user-manual/en/images/
trunk/docs/user-manual/en/master.xml
trunk/docs/user-manual/en/modules/
trunk/docs/user-manual/en/modules/about.xml
trunk/docs/user-manual/en/modules/download.xml
trunk/docs/user-manual/en/modules/examples.xml
trunk/docs/user-manual/en/modules/installation.xml
trunk/docs/user-manual/en/modules/introduction.xml
trunk/docs/user-manual/en/modules/running.xml
trunk/docs/user-manual/user-manual.xpr
Log:
added skeleton
Added: trunk/docs/user-manual/build.xml
===================================================================
--- trunk/docs/user-manual/build.xml (rev 0)
+++ trunk/docs/user-manual/build.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,17 @@
+<project name="jbmessaging.user-manual" default="all" basedir=".">
+
+ <property name="build.dir" value="${basedir}/../../output/docs/user-manual"/>
+ <property name="pdf.name" value="JBossMessaging_UserManual.pdf"/>
+ <import file="${basedir}/../../lib/docbook-support/support.xml"/>
+
+ <target name="all" depends="clean">
+ <mkdir dir="en/images" />
+ <antcall target="lang.all"><param name="lang" value="en"/></antcall>
+ </target>
+
+ <target name="html.doc" description="creates the html docs only and opens a browser">
+ <mkdir dir="en/images" />
+ <antcall target="lang.dochtml"><param name="lang" value="en"/></antcall>
+ </target>
+
+</project>
Added: trunk/docs/user-manual/en/master.xml
===================================================================
--- trunk/docs/user-manual/en/master.xml (rev 0)
+++ trunk/docs/user-manual/en/master.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN"
+ "../../../lib/docbook-support/support/docbook-dtd/docbookx.dtd" [
+ <!ENTITY about SYSTEM "modules/about.xml">
+ <!ENTITY introduction SYSTEM "modules/introduction.xml">
+ <!ENTITY download SYSTEM "modules/download.xml">
+ <!ENTITY installation SYSTEM "modules/installation.xml">
+ <!ENTITY running SYSTEM "modules/running.xml">
+ <!ENTITY examples SYSTEM "modules/examples.xml">
+ ]>
+<book lang="en">
+ <bookinfo>
+ <title>JBoss Messaging 2.0 User Manual</title>
+ <subtitle>Setting the Standard for High Performance Messaging</subtitle>
+ </bookinfo>
+
+ <toc></toc>
+
+ &about;
+ &introduction;
+ &download;
+ &installation;
+ &running;
+ &examples;
+</book>
Added: trunk/docs/user-manual/en/modules/about.xml
===================================================================
--- trunk/docs/user-manual/en/modules/about.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/about.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="about">
+ <title>About JBoss Messaging</title>
+ <para>TODO: copy blurb from User Guide</para>
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/en/modules/download.xml
===================================================================
--- trunk/docs/user-manual/en/modules/download.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/download.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="download">
+ <title>Download</title>
+ <para>The official JBoss Messaging project page is <ulink
+ url="http://www.jboss.org/jbossmessaging/">http://www.jboss.org/jbossmessaging/</ulink>.</para>
+
+ <section id="download.software">
+ <title>Software Download</title>
+ <para>The download location is the JBoss Labs Messaging Project download
+ zone: <ulink
+ url="http://www.jboss.org/jbossmessaging/downloads/">http://www.jboss.org/jbossmessaging/downloads/</ulink></para>
+ </section>
+
+ <section id="download.svn">
+ <title>SVN Repository</title>
+ <para>You can checkout the development version of JBoss Messaging directly from its
+ Subversion repository. Be aware that the
+ information provided in this manual might then not be accurate. For the
+ latest instructions on how to check out and build source code, please go
+ to <ulink
+ url="http://wiki.jboss.org/wiki/JBossMessagingDevelopment">
+ Messaging Development wiki</ulink>, and specifically <ulink
+ url="http://wiki.jboss.org/wiki/JBossMessagingBuildInstructions">
+ "Building and Running JBoss Messaging"</ulink> page.</para>
+ </section>
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/en/modules/examples.xml
===================================================================
--- trunk/docs/user-manual/en/modules/examples.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/examples.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,228 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="examples">
+ <title>Running the Examples</title>
+
+ <para>In the directory<literal>examples</literal>, you will find 2 sets of examples:
+ </para>
+ <itemizedlist>
+ <listitem>a set of JMS examples</listitem>
+ <listitem>a set of non-JMS examples that demonstrate how to use the JBoss Messaging core API</listitem>
+ </itemizedlist>
+ <para>The examples will be expanded on before JBoss Messaging 2.0 GA release</para>
+ <para>It is highly recommended that you familiarise yourself with the
+ examples.
+ </para>
+ <para>Make sure you start JBoss Messaging before running the
+ examples!
+ </para>
+ <section id="examples.jms">
+ <title>The JMS examples</title>
+ <para>The following JMS examples are provided. To run these you will first need to start the server as shown
+ in the installation chapter.
+ </para>
+
+ <para>For each example, you can always override the default ports it will
+ try to connect to by editing jndi.properties in the config directory
+ </para>
+ <para>To run a specific example open up a shell or command prompt and navigate into the
+ <literal>examples/jms</literal>
+ directory and run the command ant followed by the example name, as follows
+ </para>
+ <programlisting>
+ ant queueExample
+ </programlisting>
+ <para>The output should be similar to the following</para>
+ <programlisting>
+ Buildfile: build.xml
+
+ init:
+ [mkdir] Created dir: /home/andy/projects/jBossMessaging/docs/examples/jms/build
+
+ compile:
+ [javac] Compiling 5 source files to /home/andy/projects/jBossMessaging/docs/
+ examples/jms/build
+
+ queueExample:
+ [java] 10:59:02,124 INFO @main [QueueExample] sending message to queue
+ [java] 10:59:02,187 INFO @main [QueueExample] message received from queue
+ [java] 10:59:02,187 INFO @main [QueueExample] message = This is a text message!
+
+ BUILD SUCCESSFUL
+ Total time: 3 seconds
+ </programlisting>
+ <para>The following examples are available</para>
+ <itemizedlist>
+ <listitem>
+ <para>queueExample</para>
+ <para>This example shows a simple send and receive to a remote queue
+ using a JMS client
+ </para>
+ </listitem>
+ <listitem>
+ <para>topicExample</para>
+ <para>This example shows a simple send and receive to a remote topic
+ using a JMS client
+ </para>
+ </listitem>
+ <listitem>
+ <para>durSubExample</para>
+ <para>This example shows the use of a durable subscriber.
+ </para>
+ </listitem>
+ <listitem>
+ <para>perfSender</para>
+ <para>This example will run a basic performance test. It sends messages to a destination according to the specified parameters. This needs to be used in conjunction with the perfListener example.
+ The number of messages, delivery mode etc can be configured as follows:
+ <programlisting>
+ ant -Dmessage.count=20000 -Ddelivery.mode=PERSISTENT perfSender
+ </programlisting>
+ </para>
+
+ <para>
+ The following parameters can be configured for the sender
+ <itemizedlist>
+ <listitem>
+ <para>message.count</para>
+ <para>The number of messages to send.</para>
+ </listitem>
+ <listitem>
+ <para>delivery.mode</para>
+ <para>The delivery mode to use, PERSISTENT or NON_PERSISTENT.</para>
+ </listitem>
+ <listitem>
+ <para>message.warmup.count</para>
+ <para>How many messages to warm up for. Because of the JIT compiler maximum throughput will take a
+ little
+ while to kick in.
+ </para>
+ </listitem>
+ <listitem>
+ <para>message.size</para>
+ <para>The size of message to send, in bytes</para>
+ </listitem>
+ <listitem>
+ <para>sess.trans</para>
+ <para>Whether or not the session is transacted.</para>
+ </listitem>
+ <listitem>
+ <para>sess.trans.size</para>
+ <para>If the session is transacted the batch size to commit.</para>
+ </listitem>
+ <listitem>
+ <para>queue.lookup</para>
+ <para>The name of the queue to use.</para>
+ </listitem>
+ <listitem>
+ <para>cf.lookup</para>
+ <para>The name of the connection factory to use.</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>perfListener</para>
+ <para>This example will run a basic performance test. It will consume messages from a destination according to the parameters specified. Before running start the example and wait for it to
+ start, you will see
+ <literal>READY!!!</literal>
+ when the listener has started. The number of messages,
+ delivery mode etc can be configured as follows:
+ <programlisting>
+ ant -Dmessage.count=20000 -Ddelivery.mode=PERSISTENT perfSender
+ </programlisting>
+ </para>
+
+ <para>If running the sender and listener seperately make sure to run the listener with the parameter
+ <literal>drain.queue</literal>
+ set to false
+ </para>
+ <para>
+ The following parameters can be configured:
+ <itemizedlist>
+ <listitem>
+ <para>message.count</para>
+ <para>The number of messages to consume.</para>
+ </listitem>
+ <listitem>
+ <para>message.warmup.count</para>
+ <para>How many messages to warm up for. Because of the JIT compiler maximum throughput will take a
+ little
+ while to kick in.
+ </para>
+ </listitem>
+ <listitem>
+ <para>sess.trans</para>
+ <para>Whether or not the session is transacted.</para>
+ </listitem>
+ <listitem>
+ <para>sess.trans.size</para>
+ <para>If the session is transacted the batch size to commit.</para>
+ </listitem>
+ <listitem>
+ <para>sess.ackmode</para>
+ <para>The acknowledge mode to use, DUPS_OK or AUTO_ACK. Ignored if the session is transacted</para>
+ </listitem>
+ <listitem>
+ <para>drain.queue</para>
+ <para>Whether or not the listener will empty the queue before starting.</para>
+ </listitem>
+ <listitem>
+ <para>queue.lookup</para>
+ <para>The name of the queue to use.</para>
+ </listitem>
+ <listitem>
+ <para>cf.lookup</para>
+ <para>The name of the connection factory to use.</para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>There are also some ant targets for running the perf sender and listener in different modes:
+ <programlisting>
+ perfNonTransactionalSender
+ perfTransactionalSender
+ perfAutoAckListener
+ perfDupsOKListener
+ perfDupsOKListener
+ </programlisting>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="examples.messaging">
+ <title>The Messaging examples</title>
+ <para>The messaging examples demonstrate the use of the messaging core API and also how to create and run an
+ embedded
+ instance of JBM. The following examples are available:
+ </para>
+ <para>to run a specific example open up a shell or command prompt and navigate into the
+ <literal>examples/messaging</literal>
+ directory and run the command ant followed by the example name, as follows
+ </para>
+ <programlisting>
+ ant simpleClient
+ </programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>SimpleClient</para>
+ <para>This example shows a simple send and receive to a remote queue
+ using a core messaging client. The server will need to be running for this example.
+ </para>
+ </listitem>
+ <listitem>
+ <para>SSLClient</para>
+ <para>This example shows a simple send and receive to a remote queue using SS. The server will need to be
+ running and configured to use SSL for this example. Refer to the configuration chapter for details on how
+ to do this.
+ </para>
+ </listitem>
+ <listitem>
+ <para>simpleExample</para>
+ <para>This example shows how to create an embedded JBM server using the core API. The server must not have
+ been started before running this example.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/en/modules/installation.xml
===================================================================
--- trunk/docs/user-manual/en/modules/installation.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/installation.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="installation">
+ <title>Installation</title>
+ <para>This section describes how to install JBoss Messaging.
+ </para>
+
+ <section id="installation.prerequisites">
+ <title>Prerequisites</title>
+ <para><note>JBoss Messaging only runs on Java 5 or later.</note></para>
+ <para>By default, JBoss Messaging server is run with 1GB of memory. If your computer has less memory,
+ modify the value in <literal>bin/run.sh</literal> accordingly.</para>
+ <para><ulink url="http://ant.apache.org/">Apache Ant</ulink> is required to create the profiles for JBoss AS 5 and run the examples.</para>
+ </section>
+
+ <section id="installation.standalone">
+ <title>Installing JBoss Messaging standalone</title>
+ <para>After downloading the distribution, unzip it into your chosen directory. At this point it should be possible
+ to run straight out of the box, the following describes the directory structure:
+ </para>
+ <programlisting>
+ |-- bin
+ |-- config
+ | |-- jboss-as
+ | `-- stand-alone
+ |-- docs
+ | |-- api
+ | |-- quickstartguide
+ | |-- migrationguide
+ | |-- referenceguide
+ | `-- userguide
+ |-- examples
+ | |-- javaee
+ | `-- jms
+ |-- lib
+ |-- licenses
+ `-- schemas
+ </programlisting>
+ <itemizedlist>
+ <listitem>
+ <para><literal>bin</literal> -- binaries and scripts needed to run JBoss Messaging</para>
+ </listitem>
+ <listitem>
+ <para><literal>config</literal> -- configuration files needed to configure JBoss Messaging. This contains configurations
+ to run JBoss Messaging either in standalone or inside JBoss AS 5. Please refer to the reference
+ guide for details on configuration.
+ </para>
+ </listitem>
+ <listitem>
+ <para><literal>docs</literal> -- guides and javadocs for JBoss Messaging
+ </para>
+ </listitem>
+ <listitem>
+ <para><literal>examples</literal> -- JMS and Java EE examples. Please refer to the 'running examples'
+ chapter for details on how to run them.
+ </para>
+ </listitem>
+ <listitem>
+ <para><literal>lib</literal> -- jars and libraries needed to run JBoss Messaging
+ </para>
+ </listitem>
+ <listitem>
+ <para><literal>licenses</literal> -- licenses for JBoss Messaging
+ </para>
+ </listitem>
+ <listitem>
+ <para><literal>schemas</literal> -- XML Schemas used to validate JBoss Messaging configuration files</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="installation.jboss">
+ <title>Installing JBoss Messaging in JBoss AS 5</title>
+ <para>JBoss Messaging 2.0 can be deployed in <ulink url="http://www.jboss.org/jbossas/">JBoss AS 5</ulink>.
+ It is not shipped by default with the application server and you need to create new AS 5 profiles to run AS 5 with JBoss Messaging.</para>
+
+ <para>To create AS 5 profiles:</para>
+ <orderedlist>
+ <listitem><para>Download JBoss AS 5</para></listitem>
+ <listitem><para>Set the environment property <literal>JBOSS_HOME</literal> to point to the directory where you installed JBoss AS 5</para></listitem>
+ <listitem><para>run <literal>ant</literal> in JBoss Messaging's <literal>config/jboss-as</literal> directory</para></listitem>
+ </orderedlist>
+
+ <para>This will create 2 new profiles in <literal>$JBOSS_HOME/server</literal>:</para>
+ <itemizedlist>
+ <listitem><para><literal>default-with-jbm2</literal> -- it corresponds to AS 5 <literal>default</literal>
+ profile with JBoss Messaging 2 as its JMS provider. In this profile, JBoss Messaging is <emphasis>non-clustered</emphasis></para></listitem>
+ <listitem><para><literal>all-with-jbm2</literal> -- it corresponds to AS 5 <literal>all</literal>
+ profile with JBoss Messaging 2 as its JMS provider. In this profile, JBoss Messaging is <emphasis>clustered</emphasis></para></listitem>
+ </itemizedlist>
+
+ <para>You can then start JBoss AS 5 using one of these profiles:</para>
+ <programlisting>$JBOSS_HOME/bin/run.sh -c default-with-jbm2</programlisting>
+
+ </section>
+
+
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/en/modules/introduction.xml
===================================================================
--- trunk/docs/user-manual/en/modules/introduction.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/introduction.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction">
+ <title>Introduction</title>
+ <para>TODO</para>
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/en/modules/running.xml
===================================================================
--- trunk/docs/user-manual/en/modules/running.xml (rev 0)
+++ trunk/docs/user-manual/en/modules/running.xml 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="running">
+ <title>Running JBoss Messaging</title>
+
+ <section id="running.standalone">
+ <title>Running JBoss Messaging in Standalone</title>
+ <para>To run JBM, open up a shell or command prompt and navigate into the 'bin' directory. Then execute './run.sh'
+ (or 'run.bat' on windows) and you should see the following output
+ </para>
+ <programlisting>
+ java -Xmx512M -Dorg.jboss.logging.Logger.pluginClass=org.jboss.messaging.core
+ .logging.JBMLoggerPlugin -Djava.library.path=. -classpath ../lib/xercesImpl.j
+ ar:../lib/trove.jar:../lib/slf4j-log4j12.jar:../lib/slf4j-api-1.4.3.jar:../li
+ b/mina-core-2.0.0-M2-20080418.144850.jar:../lib/log4j.jar:../lib/jnpserver.ja
+ r:../lib/jgroups.jar:../lib/jboss-xml-binding.jar:../lib/jbossts-common.jar:.
+ ./lib/jboss-transaction-spi.jar:../lib/jbosssx-client.jar:../lib/jboss-securi
+ ty-spi.jar:../lib/jboss-messaging.jar:../lib/jboss-messaging-client.jar:../li
+ b/jboss-kernel.jar:../lib/jbossjta.jar:../lib/jbossjta-integration.jar:../lib
+ /jboss-javaee.jar:../lib/jboss-jaspi-api.jar:../lib/jboss-dependency.jar:../l
+ ib/jboss-container.jar:../lib/jboss-common-logging-spi.jar:../lib/jboss-commo
+ n-core.jar:../lib/jboss-aop-mc-int.jar:../lib/jboss-aop-jdk50.jar:../lib/java
+ ssist.jar:../lib/concurrent.jar:../lib/commons-logging.jar:../config/ org.jbo
+ ss.jms.server.microcontainer.JBMBootstrapServer jbm-standalone-beans.xml
+ 10:25:57,225 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
+ t/data/bindings does not already exists
+ 10:25:57,226 INFO @main [JournalStorageManager] Creating it
+ 10:25:57,270 INFO @main [JournalStorageManager] Directory /home/andy/jbm-tes
+ t/data/journal does not already exists
+ 10:25:57,271 INFO @main [JournalStorageManager] Creating it
+ 10:25:57,276 INFO @main [JournalStorageManager] AIO loaded successfully
+ 10:25:57,689 INFO @main [MinaService] Registering:tcp://localhost:5400
+ 10:25:57,707 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ g.core.deployers.impl.SecurityDeployer at fe0fd9 with urlfile:/home/andy/project
+ s/jBossMessaging/build/messaging-2.0.0.alpha1/config/queues.xml
+ 10:25:57,758 INFO @main [XmlDeployer] deploying jms.topic.testTopic
+ 10:25:57,761 INFO @main [XmlDeployer] deploying jms.topic.securedTopic
+ 10:25:57,761 INFO @main [XmlDeployer] deploying jms.topic.testDurableTopic
+ 10:25:57,762 INFO @main [XmlDeployer] deploying jms.queue.testQueue
+ 10:25:57,762 INFO @main [XmlDeployer] deploying jms.queue.NoSuchQueue
+ 10:25:57,763 INFO @main [XmlDeployer] deploying jms.topic.NoSuchTopic
+ 10:25:57,763 INFO @main [XmlDeployer] deploying queuetempjms.*
+ 10:25:57,764 INFO @main [XmlDeployer] deploying topictempjms.*
+ 10:25:57,764 INFO @main [XmlDeployer] deploying *
+ 10:25:57,765 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ g.core.deployers.impl.QueueSettingsDeployer at 1220b36 with urlfile:/home/andy/p
+ rojects/jBossMessaging/build/messaging-2.0.0.alpha1/config/queues.xml
+ 10:25:57,783 INFO @main [XmlDeployer] deploying jms.queue.QueueWithOwnDLQAndE
+ xpiryQueue
+ 10:25:57,784 INFO @main [XmlDeployer] deploying jms.topic.TopicWithOwnDLQAndE
+ xpiryQueue
+ 10:25:57,784 INFO @main [XmlDeployer] deploying jms.queue.QueueWithOwnRedeliv
+ eryDelay
+ 10:25:57,784 INFO @main [XmlDeployer] deploying jms.topic.TopicWithOwnRedeliv
+ eryDelay
+ 10:25:57,785 INFO @main [XmlDeployer] deploying jms.queue.testDistributedQueu
+ e
+ 10:25:57,785 INFO @main [XmlDeployer] deploying jms.topic.testDistributedTopi
+ c
+ 10:25:57,785 INFO @main [XmlDeployer] deploying jms.queue.testPerfQueue
+ 10:25:57,785 INFO @main [XmlDeployer] deploying *
+ 10:26:02,824 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ g.core.deployers.impl.SecurityManagerDeployer at 1a1ff9 with urlfile:/home/andy/
+ projects/jBossMessaging/build/messaging-2.0.0.alpha1/config/jbm-security.xml
+ 10:26:02,831 INFO @main [XmlDeployer] deploying guest
+ 10:26:02,991 INFO @main [FileDeploymentManager] Deploying org.jboss.messagin
+ g.jms.server.impl.JMSServerDeployer at d6c07 with urlfile:/home/andy/projects/jB
+ ossMessaging/build/messaging-2.0.0.alpha1/config/jbm-jms.xml
+ 10:26:03,005 INFO @main [XmlDeployer] deploying DLQ
+ 10:26:03,035 INFO @main [XmlDeployer] deploying ExpiryQueue
+ 10:26:03,038 INFO @main [XmlDeployer] deploying testQueue
+ 10:26:03,044 INFO @main [XmlDeployer] deploying testPerfQueue
+ 10:26:03,046 INFO @main [XmlDeployer] deploying A
+ 10:26:03,048 INFO @main [XmlDeployer] deploying B
+ 10:26:03,050 INFO @main [XmlDeployer] deploying C
+ 10:26:03,051 INFO @main [XmlDeployer] deploying D
+ 10:26:03,072 INFO @main [XmlDeployer] deploying ex
+ 10:26:03,075 INFO @main [XmlDeployer] deploying PrivateDLQ
+ 10:26:03,077 INFO @main [XmlDeployer] deploying PrivateExpiryQueue
+ 10:26:03,078 INFO @main [XmlDeployer] deploying QueueWithOwnDLQAndExpiryQueu
+ e
+ 10:26:03,080 INFO @main [XmlDeployer] deploying QueueWithOwnRedeliveryDelay
+ 10:26:03,081 INFO @main [XmlDeployer] deploying testDistributedQueue
+ 10:26:03,083 INFO @main [XmlDeployer] deploying testTopic
+ 10:26:03,086 INFO @main [XmlDeployer] deploying securedTopic
+ 10:26:03,087 INFO @main [XmlDeployer] deploying testDurableTopic
+ 10:26:03,088 INFO @main [XmlDeployer] deploying TopicWithOwnDLQAndExpiryQueu
+ e
+ 10:26:03,089 INFO @main [XmlDeployer] deploying TopicWithOwnRedeliveryDelay
+ 10:26:03,090 INFO @main [XmlDeployer] deploying testDistributedTopic
+ 10:26:03,091 INFO @main [XmlDeployer] deploying testConnectionFactory
+ 10:26:03,091 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,101 INFO @main [XmlDeployer] deploying ConnectionFactory
+ 10:26:03,101 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,102 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,103 WARN @main [JMSServerManagerImpl] Binding for java:/ConnectionF
+ actory already exists
+ 10:26:03,103 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,104 WARN @main [JMSServerManagerImpl] Binding for java:/XAConnectio
+ nFactory already exists
+ 10:26:03,104 INFO @main [XmlDeployer] deploying ClusteredConnectionFactory
+ 10:26:03,104 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,105 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredCo
+ nnectionFactory already exists
+ 10:26:03,106 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,106 WARN @main [JMSServerManagerImpl] Binding for java:/ClusteredXA
+ ConnectionFactory already exists
+ 10:26:03,107 INFO @main [XmlDeployer] deploying MyExampleConnectionFactory
+ 10:26:03,107 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,118 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,130 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,131 INFO @main [JMSServerManagerImpl] Creating cf ** with ws:1000
+ 10:26:03,133 INFO @main [JBMBootstrapServer] JBM Server Started
+ </programlisting>
+ <para>JBoss Messaging is now running. If any errors are seen, refer to the troubleshooting guide for help</para>
+ </section>
+
+ <section id="running.jboss.as">
+ <title>Running JBoss Messaging in JBoss AS 5</title>
+ <para>TODO</para>
+ </section>
+
+</chapter>
\ No newline at end of file
Added: trunk/docs/user-manual/user-manual.xpr
===================================================================
--- trunk/docs/user-manual/user-manual.xpr (rev 0)
+++ trunk/docs/user-manual/user-manual.xpr 2009-05-07 10:34:08 UTC (rev 6700)
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project>
+ <meta>
+ <filters directoryPatterns="" filePatterns=""
+ positiveFilePatterns="" showHiddenFiles="false"/>
+ <options/>
+ </meta>
+ <projectTree name="quickstart.xpr">
+ <folder name="en">
+ <folder name="images"/>
+ <folder name="modules">
+ <file name="en/modules/about.xml"/>
+ <file name="en/modules/download.xml"/>
+ <file name="en/modules/examples.xml"/>
+ <file name="en/modules/installation.xml"/>
+ <file name="en/modules/introduction.xml"/>
+ <file name="en/modules/running.xml"/>
+ </folder>
+ <file name="en/master.xml"/>
+ </folder>
+ </projectTree>
+</project>
More information about the jboss-cvs-commits
mailing list