[jboss-cvs] JBoss Messaging SVN: r6704 - trunk/docs/quickstartguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 7 10:14:02 EDT 2009
Author: jmesnil
Date: 2009-05-07 10:14:02 -0400 (Thu, 07 May 2009)
New Revision: 6704
Modified:
trunk/docs/quickstartguide/en/modules/download.xml
trunk/docs/quickstartguide/en/modules/installation.xml
trunk/docs/quickstartguide/en/modules/running.xml
Log:
Quick start guide
* running chapter
+ minor modifs on download & installation chapters
Modified: trunk/docs/quickstartguide/en/modules/download.xml
===================================================================
--- trunk/docs/quickstartguide/en/modules/download.xml 2009-05-07 14:00:07 UTC (rev 6703)
+++ trunk/docs/quickstartguide/en/modules/download.xml 2009-05-07 14:14:02 UTC (rev 6704)
@@ -19,8 +19,8 @@
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
+ Messaging Development Wiki</ulink>, and specifically <ulink
url="http://wiki.jboss.org/wiki/JBossMessagingBuildInstructions">
- "Building and Running JBoss Messaging"</ulink> page.</para>
+ Building and Running JBoss Messaging</ulink> page.</para>
</section>
</chapter>
\ No newline at end of file
Modified: trunk/docs/quickstartguide/en/modules/installation.xml
===================================================================
--- trunk/docs/quickstartguide/en/modules/installation.xml 2009-05-07 14:00:07 UTC (rev 6703)
+++ trunk/docs/quickstartguide/en/modules/installation.xml 2009-05-07 14:14:02 UTC (rev 6704)
@@ -6,16 +6,17 @@
<section id="installation.prerequisites">
<title>Prerequisites</title>
- <para><note>JBoss Messaging only runs on Java 5 or later.</note></para>
+ <note><para>JBoss Messaging only runs on Java 5 or later.</para></note>
<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>For persistence, JBoss Messaging use Java NIO to load and store data. On Linux, it is possible to use libaio instead.</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>
+ <title>Standalone JBoss Messaging Server</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:
+ to <link linkend="running.standalone">run straight out of the box</link>, the following describes the directory structure:
</para>
<programlisting>
|-- bin
@@ -24,10 +25,10 @@
| `-- stand-alone
|-- docs
| |-- api
- | |-- quickstartguide
- | |-- migrationguide
- | |-- referenceguide
- | `-- userguide
+ | |-- quickstart-guide
+ | |-- migration-guide
+ | |-- reference
+ | `-- user-manual
|-- examples
| |-- javaee
| `-- jms
@@ -69,7 +70,7 @@
</section>
<section id="installation.jboss">
- <title>Installing JBoss Messaging in JBoss AS 5</title>
+ <title>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>
Modified: trunk/docs/quickstartguide/en/modules/running.xml
===================================================================
--- trunk/docs/quickstartguide/en/modules/running.xml 2009-05-07 14:00:07 UTC (rev 6703)
+++ trunk/docs/quickstartguide/en/modules/running.xml 2009-05-07 14:14:02 UTC (rev 6704)
@@ -1,125 +1,41 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="running">
- <title>Running JBoss Messaging</title>
+ <title>Starting The Server</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
+ <title>Standalone JBoss Messaging</title>
+ <para>To run a standalone server, open up a shell or command prompt and navigate into the <literal>bin</literal> directory.
+ Then execute <literal>./run.sh</literal> (or <literal>run.bat</literal> 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
+ bin$ ./run.sh
+
+ 15:05:54,108 INFO @main [JBMBootstrapServer] Starting JBoss Messaging server
+ ...
+ 15:06:02,566 INFO @main [MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
</programlisting>
- <para>JBoss Messaging is now running. If any errors are seen, refer to the troubleshooting guide for help</para>
+ <para>JBoss Messaging is now running. If any errors are displayed or if the server was not started properly, please refer to the troubleshooting guide for help</para>
+ <para>By default, JBoss Messaging is run in a <emphasis>non-clustered</emphasis> configuration (based on the configuration in
+ <literal>config/stand-alone/non-clustered</literal> directory).</para>
</section>
<section id="running.jboss.as">
- <title>Running JBoss Messaging in JBoss AS 5</title>
- <para>TODO</para>
+ <title>JBoss Messaging In JBoss AS 5</title>
+ <para>To run JBoss Messaging in JBoss AS 5, you need to create the
+ <link linkend="installation.jboss">AS 5 profiles for JBoss Messaging</link> first.
+ Then run JBoss AS 5 with one these profiles. For example, to run JBoss AS 5 with a
+ <emphasis>non-clustered</emphasis> JBoss Messaging server, got to <literal>$JBOSS_HOME/bin</literal>
+ directory and type:</para>
+ <programlisting>
+ bin$ ./run.sh -c default-with-jbm2
+
+ 15:18:35,460 INFO [ServerImpl] Starting JBoss (Microcontainer)...
+ 15:18:35,462 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904091504)
+ ...
+ 15:19:30,305 INFO [MessagingServerImpl] JBoss Messaging Server version 2.0.0.BETA1-SNAPSHOT (Stilton, 101) started
+ ...
+ 15:19:43,601 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904091504)] Started in 1m:8s:121ms
+ </programlisting>
</section>
</chapter>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list