[jboss-cvs] JBoss Messaging SVN: r5557 - branches/Branch_1_4/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Dec 22 02:56:11 EST 2008
Author: gaohoward
Date: 2008-12-22 02:56:11 -0500 (Mon, 22 Dec 2008)
New Revision: 5557
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
Log:
JBM 1.4.2.GA -- Doc update
Modified: branches/Branch_1_4/docs/userguide/en/modules/about.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/about.xml 2008-12-22 06:37:57 UTC (rev 5556)
+++ branches/Branch_1_4/docs/userguide/en/modules/about.xml 2008-12-22 07:56:11 UTC (rev 5557)
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="about">
- <title>About JBoss Messaging 1.4.1</title>
+ <title>About JBoss Messaging 1.4.2</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>
Modified: branches/Branch_1_4/docs/userguide/en/modules/configuration.xml
===================================================================
--- branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2008-12-22 06:37:57 UTC (rev 5556)
+++ branches/Branch_1_4/docs/userguide/en/modules/configuration.xml 2008-12-22 07:56:11 UTC (rev 5557)
@@ -31,81 +31,6 @@
considered the security implications before removing the security
interceptor.</para>
- <section id="conf.jb5.securityMetadataStore">
- <title>JBoss5 Specific - Configuring the SecurityStore</title>
-
- <para>Starting on JBossMessaging 1.4.1 the SecurityStore is a pluggable
- object, and it has a default implementation on
- messaging-service.xml.</para>
-
- <programlisting> <!-- The SecurityStore mbean -->
- <mbean code="org.jboss.jms.server.security.SecurityMetadataStore"
- name="jboss.messaging:service=SecurityStore">
-
- <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis
- -->
- <attribute name="DefaultSecurityConfig">
- <security>
- <role name="guest" read="true" write="true" create="true"/>
- </security>
- </attribute>
-
- <!-- The JAAS security domain to use for JBoss Messaging -->
- <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
-
- <!--
- This attribute defines what's the SuckerPassword used on this SecurityStore
- -->
- <attribute name="SuckerPassword">CHANGE ME!!</attribute>
- </mbean> </programlisting>
-
- <section id="conf.securityMetadataStore.attributes">
- <title>SecurityStore Attributes</title>
-
- <section id="conf.securityMetadataStore.attributes.defaultsecurity">
- <title>DefaultSecurityConfig</title>
-
- <para>Default security configuration is used when the security
- configuration for a specific queue or topic has not been overridden in
- the destination's deployment descriptor. It has exactly the same
- syntax and semantics as in JBossMQ.</para>
-
- <para>The <literal>DefaultSecurityConfig</literal> attribute element
- should contain one <literal><security></literal> element. The
- <literal><security></literal> element can contain multiple
- <literal><role></literal> elements. Each
- <literal><role></literal> element defines the default access for
- that particular role.</para>
-
- <para>If the <literal>read</literal> attribute is
- <literal>true</literal> then that role will be able to read (create
- consumers, receive messaages or browse) destinations by
- default.</para>
-
- <para>If the <literal>write</literal> attribute is
- <literal>true</literal> then that role will be able to write (create
- producers or send messages) to destinations by default.</para>
-
- <para>If the <literal>create</literal> attribute is
- <literal>true</literal> then that role will be able to create durable
- subscriptions on topics by default.</para>
- </section>
-
- <section id="conf.securityMetadataStore.attributes.securitydomain">
- <title>SecurityDomain</title>
-
- <para>The JAAS security domain to be used by this server peer</para>
- </section>
-
- <section id="conf.securityMetadataStore.attributes.suckerpassword">
- <title>SuckerPassword</title>
-
- <para>This defines how the SecurityStore will authenticate the sucker
- user (JBM.SUCKER)</para>
- </section>
- </section>
- </section>
-
<section id="conf.serverpeer">
<title>Configuring the ServerPeer</title>
@@ -2501,10 +2426,8 @@
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>On JBoss4 you must match the remoting configs accordingly to remoting-bisocket-service.xml. </para>
- <para>On JBoss5 you just need to define -Djboss.service.binding.set=ports-default|ports-01|ports-02 when you start your application server. Look at /server/conf/bindings.mxl and on JBoss5 documentation for more information.</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-12-22 06:37:57 UTC (rev 5556)
+++ branches/Branch_1_4/docs/userguide/en/modules/installation.xml 2008-12-22 07:56:11 UTC (rev 5557)
@@ -9,7 +9,7 @@
<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>
+ install JBoss Messaging.</para>
<para>By default, JBoss AS 4.2 ships with JBossMQ as default JMS provider.
In order to use the JBoss AS instance with JBoss Messaging, you need to
@@ -175,12 +175,7 @@
<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>
-
+ you can use the ServiceBindingManager to do this as follows:</para>
<itemizedlist>
<listitem>
@@ -261,8 +256,8 @@
may be out of date and you will need to copy the config from
<literal>remoting-bisocket-service.xml. DO NOT just copy and
paste from the above example - copy it from the JBoss Messaging
- distribution.</literal>. On JBoss5 the ports are controlled by
- system-property substitution hence you don't need to worry about copying the config into bindings.xml</warning>
+ distribution.</literal>.
+ </warning>
<para>You should ensure that each node is configured to use a
different ports range.</para>
@@ -613,17 +608,16 @@
<listitem>
<para>
<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.SP2/ ">Remoting 2.5.0.SP2</ulink>.
- If you are using JBoss5 you don't need to take any extra steps on the remoting installation.
- </note>
+ JBoss Messaging 1.4.2 requires a patched version of jboss-remoting.jar. This version is available
+ and can be downloaded from <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</literal> directory 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>
</para>
</listitem>
- <para>You should also make these changes on any configuration you
- choose, to remove all references to the old JBossMQ:</para>
-
<listitem>
<para>Edit <literal>$JBOSS_CONFIG/deploy/jms-ds.xml</literal> and
replace jboss.mq by jboss.messaging on every occurrence</para>
@@ -915,14 +909,11 @@
<itemizedlist>
<listitem>
<para><note>
- If you are using JBoss Messaging 1.4.1 outiside of JBoss 4.2 or EAP 4.3, you need to make sure you use a JBoss Remoting 2.5.0.SP2. 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.5.0.SP2/lib/">here</ulink>
-
- . Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
- </note></para>
+ JBoss Messaging 1.4.2 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 at <ulink url="http://repository.jboss.com/jboss/remoting/2.2.2.SP10-brew/lib/">here</ulink>.
+ Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
+ </note></para>
</listitem>
<listitem>
@@ -938,9 +929,9 @@
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/deploy/jboss-aop.deployer/jboss-aop.jar</para>
- <para>JBoss AOP 2.0.0.SP1</para>
+ <para>JBoss AOP 1.5.6.GA</para>
- <para><ulink url="http://repository.jboss.com/jboss/aop/2.0.0.SP1/lib/">http://repository.jboss.com/jboss/aop/2.0.0.SP1/lib/</ulink></para>
+ <para><ulink url="http://repository.jboss.com/jboss/aop/1.5.6.GA/lib/">http://repository.jboss.com/jboss/aop/1.5.6.GA/lib/</ulink></para>
<para>(For AOP, sometimes you have to use a specific JAR according to
your JVM of choice. Use the most convenient for you)</para>
@@ -949,10 +940,10 @@
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/lib/javassist.jar</para>
- <para>Javassist 3.9.0.GA</para>
+ <para>Javassist 3.8.0.GA</para>
<para><ulink
- url="http://repository.jboss.com/javassist/3.9.0.GA/lib/">http://repository.jboss.com/javassist/3.9.0.GA/lib/</ulink></para>
+ url="http://repository.jboss.com/javassist/3.8.0.GA/lib/">http://repository.jboss.com/javassist/3.8.0.GA/lib/</ulink></para>
</listitem>
<listitem>
@@ -970,59 +961,6 @@
</itemizedlist>
</section>
- <section id="inst.remoteclient.jb5">
- <title>Accessing JBoss Messaging from a remote client - JBoss 5.0</title>
-
- <para>In order to access JBoss Messaging from a client outside the JBoss
- app server, you will need to ensure the following jar files are on the
- client classpath:</para>
-
- <itemizedlist>
- <listitem>
- <para>$JBOSS_HOME/client/jnp-client.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-javaee.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-messaging.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-remoting.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-serialization.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/javassist.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-aop-client.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/trove.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/log4j.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-logging-spi.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-logging-log4j.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-common-core.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/jboss-mdr.jar</para>
- </listitem>
- <listitem>
- <para>$JBOSS_HOME/client/concurrent.jar</para>
- </listitem>
- </itemizedlist>
- </section>
-
<section id="inst.mqmessagemigration">
<title>Migrating Messages from JBoss MQ to JBoss Messaging</title>
More information about the jboss-cvs-commits
mailing list