[jboss-cvs] JBoss Messaging SVN: r5296 - branches/Branch_1_4/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Nov 6 22:50:05 EST 2008
Author: clebert.suconic at jboss.com
Date: 2008-11-06 22:50:04 -0500 (Thu, 06 Nov 2008)
New Revision: 5296
Modified:
branches/Branch_1_4/docs/userguide/en/modules/about.xml
branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
branches/Branch_1_4/docs/userguide/en/modules/installation.xml
branches/Branch_1_4/docs/userguide/en/modules/introduction.xml
Log:
Doc Tweaks
Modified: branches/Branch_1_4/docs/userguide/en/modules/about.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/about.xml 2008-11-06 18:41:08 UTC (rev 5295)
+++ branches/Branch_1_4/docs/userguide/en/modules/about.xml 2008-11-07 03:50:04 UTC (rev 5296)
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="about">
- <title>About JBoss Messaging 1.4</title>
+ <title>About JBoss Messaging 1.4.1</title>
<para>JBoss Messaging is the new enterprise messaging system from JBoss. It
is a complete rewrite of JBossMQ, the legacy JBoss JMS provider.</para>
-
+
<para>JBoss Messaging is the default JMS provider in JBoss Enterprise Application Platform version 4.3 or later, and JBoss SOA Platform.
It is also the default JMS provider in JBoss Application Server 5, and is the default JMS provider for JBoss ESB.</para>
@@ -19,12 +19,9 @@
<para>JBoss Messaging can also be easily installed in JBoss Community Application Server
4.2 using a few simple steps to remove JBoss MQ and replace with JBoss
- Messaging..</para>
+ Messaging.</para>
- <para>From release 1.4.0. onwards JBoss Messaging is designed for JBoss 4.2+
- only and is Java 5.</para>
-
- <para>The procedure of installing JBoss Messaging into JBoss Application
+ <para>The procedure of configuring JBoss Messaging into JBoss Application
Server is detailed in this guide.</para>
<para>Please send your suggestions or comments to the <ulink
Modified: branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2008-11-06 18:41:08 UTC (rev 5295)
+++ branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2008-11-07 03:50:04 UTC (rev 5296)
@@ -2501,12 +2501,12 @@
<section id="conf.servicebindingmanager">
<title>ServiceBindingManager</title>
- <para>If you are using the JBoss AS ServiceBindingManager to provide
- different servers with different port ranges, then you must make sure that
- the JBoss Messaging remoting configuration specified in the JBoss
- Messaging section of the ServiceBindingManager xml file exactly matches
- that in remoting-bisocket-service.xml.</para>
-
+ <para>The service binding manager on JBoss is used to provide multiple application servers instances running on the same IP using different port ranges,
+ which is very useful during development. You could have multiple IPs on the same server and bind each server on a different IP if you wanted to deal with OS configs,
+ but case you prefer not dealing with OS configs you have the option of using the ServiceBindingManager.</para>
+
+ <para>On JBoss4 you must match the remoting configs accordingly to remoting-bisocket-service.xml. On JBoss5 there is a simpler configuration where you just define the Ports using properties.</para>
+
<para>If you are using a newer version of JBM in an older version of JBAS
then the example bindings in the AS distribution may well be out of date.
It is therefore imperative that the relevant sections are overwritten with
Modified: branches/Branch_1_4/docs/userguide/en/modules/installation.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2008-11-06 18:41:08 UTC (rev 5295)
+++ branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2008-11-07 03:50:04 UTC (rev 5296)
@@ -7,7 +7,7 @@
procedure, you will create a JBoss Messaging configuration that will start a
clustered or non-clustered messaging server.</para>
- <para>Please note that JBoss EAP 4.3 or later comes with JBoss Messaging
+ <para>Please note that JBoss EAP 4.3 and JBoss 5 comes with JBoss Messaging
pre-installed as default JMS provider so if you are using that, there is no need to manually
install JBoss Messaging</para>
@@ -172,12 +172,16 @@
using clustering.</warning>
</para>
</listitem>
-
<listitem>
<para>If you want to run multiple JBoss Messaging nodes on the same
box using the same IP address, e.g. for development purposes, then
you can use the ServiceBindingManager to do this as follows:</para>
+ <para><warning>JBoss5 has introduced a much simpler ServiceBindingManager.
+ You should refer to the JBoss5 documentation about how to administer the new bindingManager if you are using JBoss5.
+ </warning></para>
+
+
<itemizedlist>
<listitem>
<para>Uncomment binding manager service from
@@ -606,15 +610,12 @@
<listitem>
<para>
- <note>JBoss Messaging 1.4.0 and 1.4.1 requires a patched version
- of jboss-remoting.jar. This version is available can be downloaded from here <ulink
- url="http://repository.jboss.com/jboss/remoting/2.2.2.SP10-brew/ ">here</ulink>The
- version is JBoss Remoting 2.2.2.SP10-brew. Please download it and
- copy it into the <literal>$JBOSS_HOME/server/<your server
- name>/lib directory</literal> of any server profiles that use
- JBoss Messaging. If you are using JBoss Messaging
- from a standalone client also make sure this jar is on your
- classpath *before* jbossall-client.jar.</note>
+ <note>
+ JBoss Messaging 1.4.1.GA requires pecific versions
+ of jboss-remoting.jar if used outside of JBoss 5. If you are installing JBoss Messaging 1.4.1.GA at JBoss 4.2+, you should use this version:
+ <ulink url="http://repository.jboss.com/jboss/remoting/2.5.0.SP1/ ">Remoting 2.5.0.SP1</ulink>.
+ If you are using JBoss5 you don't need to take any extra steps on the remoting installation.
+ </note>
</para>
</listitem>
@@ -912,10 +913,11 @@
<itemizedlist>
<listitem>
<para><note>
- JBoss Messaging 1.4.0 requires a patched version of jboss-remoting.jar. The version is JBoss Remoting 2.2.2.SP10-brew. This version is available on JBoss EAP 4.3, so if you're using a different version you should download it. The patched jar can be found
+ If you are using JBoss Messaging 1.4.1 outiside of JBoss 5 or EAP 4.3, you need to make sure you use a JBoss Remoting 2.5.0.SP1. If you are using JBoss5 or EAP 4.3 you will have the required JAR available already:
+ The version could be found at:
<ulink
- url="http://repository.jboss.com/jboss/remoting/2.2.2.SP10-brew/lib/">here</ulink>
+ url="http://repository.jboss.com/jboss/remoting/2.5.0.SP1/lib/">here</ulink>
. Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
</note></para>
Modified: branches/Branch_1_4/docs/userguide/en/modules/introduction.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/introduction.xml 2008-11-06 18:41:08 UTC (rev 5295)
+++ branches/Branch_1_4/docs/userguide/en/modules/introduction.xml 2008-11-07 03:50:04 UTC (rev 5296)
@@ -76,7 +76,7 @@
</listitem>
<listitem>
- <para>Support for most major databases including Oracle, Sybase, MS
+ <para>Support for most major databases including Oracle, DB2, Sybase, MS
SQL Server, PostgreSQL and MySQL</para>
</listitem>
More information about the jboss-cvs-commits
mailing list