[jboss-cvs] JBoss Messaging SVN: r2713 - trunk/docs/userguide/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 18 14:36:30 EDT 2007
Author: clebert.suconic at jboss.com
Date: 2007-05-18 14:36:30 -0400 (Fri, 18 May 2007)
New Revision: 2713
Modified:
trunk/docs/userguide/en/modules/installation.xml
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-968
Modified: trunk/docs/userguide/en/modules/installation.xml
===================================================================
--- trunk/docs/userguide/en/modules/installation.xml 2007-05-18 16:17:21 UTC (rev 2712)
+++ trunk/docs/userguide/en/modules/installation.xml 2007-05-18 18:36:30 UTC (rev 2713)
@@ -43,6 +43,9 @@
<para>The installation script will create a
<filename>$JBOSS_HOME/server/messaging</filename> configuration.</para>
+ <para>There are few extra steps at <xref
+ linkend="install.extra-steps" /></para>
+
<note>
<para>If you want to create a JBoss Messaging configuration with a
different name, modify the <literal>messaging.config.name</literal>
@@ -78,8 +81,8 @@
JBOSS_CONFIG/deploy/jms.</para>
<para>Case you are working with a configuration similar to all, make
- sure you don't have any JBossMQ files under
- /deploy-hasingleton</para>
+ sure you don't have any JBossMQ files under /deploy-hasingleton. For
+ that just remove /deploy-hasingleton</para>
</listitem>
<listitem>
@@ -90,13 +93,13 @@
<programlisting>
<application-policy name = "messaging">
- <authentication>
- <login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule" flag = "required" >
- <module-option name = "unauthenticatedIdentity">guest</module-option>
- <module-option name = "usersProperties">props/messaging-users.properties</module-option>
- <module-option name = "rolesProperties">props/messaging-roles.properties</module-option>
- </login-module>
- </authentication>
+<authentication>
+<login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule" flag = "required" >
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "usersProperties">props/messaging-users.properties</module-option>
+ <module-option name = "rolesProperties">props/messaging-roles.properties</module-option>
+</login-module>
+</authentication>
</application-policy>
</programlisting>
@@ -150,22 +153,23 @@
</itemizedlist>
</listitem>
</itemizedlist>
+
+ <para>There are few extra steps at <xref
+ linkend="install.extra-steps" /></para>
</section>
<section id="install.clustered">
<title>Clustered Installation</title>
- <para></para>
-
<itemizedlist>
<listitem>
- <para>Install JBoss Messaging using <xref
+ <para>Install JBoss Messaging as described in <xref
linkend="install.manual" /> or <xref linkend="install4.automated" />
- using the "all" (clustered) configuration</para>
+ using the "all" (clustered) configuration as your source</para>
</listitem>
<listitem>
- <para>Ensure the server id in messaging-service.xml is unique on
+ <para>Ensure the server id in messaging-service.xml is unique for
each node on the cluster</para>
</listitem>
@@ -181,6 +185,9 @@
<para>Make sure is bound to /DefaultDS and remove
hsqldb-ds.xml.</para>
+
+ <para>It's required to use a shared database in clustered
+ environment. HSQLDB won't work for a clustered config.</para>
</listitem>
<listitem>
@@ -192,64 +199,151 @@
<para>If you want to run multiple instances bound to the same IP you
could use the Binding Manager</para>
- <para><itemizedlist>
- <listitem>
- <para>Uncomment binding manager service from
- $JBOSS_HOME/yourServer/conf/jboss-service.xml</para>
- </listitem>
+ <itemizedlist>
+ <listitem>
+ <para>Uncomment binding manager service from
+ $JBOSS_HOME/yourServer/conf/jboss-service.xml</para>
+ </listitem>
- <listitem>
- <para>Specify the desired port rage (e.g. ports-01,
- ports-02... etc)</para>
- </listitem>
+ <listitem>
+ <para>Specify the desired port rage (e.g. ports-01, ports-02...
+ etc)</para>
+ </listitem>
- <listitem>
- <para>Look at
- $JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml.
- On each port range, JBoss Remoting configuration should look
- like:</para>
+ <listitem>
+ <para>Look at
+ $JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml.
+ On each port range, JBoss Remoting configuration should look
+ like:</para>
- <programlisting><!-- ********************* jboss messaging ********************** -->
+ <programlisting><!-- ********************* jboss messaging ********************** -->
<service-config name="jboss.messaging:service=Connector,transport=bisocket"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
- <delegate-config>
- <attribute name="Configuration"><![CDATA[
- <config>
- <invoker transport="bisocket">
- <attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
- <attribute name="serializationtype" isParam="true">jms</attribute>
- <attribute name="dataType" isParam="true">jms</attribute>
- <attribute name="socket.check_connection" isParam="true">false</attribute>
- <attribute name="timeout" isParam="true">0</attribute>
- <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
- <attribute name="serverBindPort">4457</attribute>
- <attribute name="leasePeriod">10000</attribute>
- <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
- <attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
- <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
- <attribute name="callbackErrorsAllowed">1</attribute>
- <attribute name="numberOfRetries" isParam="true">1</attribute>
- <attribute name="NumberOfCallRetries" isParam="true">2</attribute>
- <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
- </invoker>
- <handlers>
- <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
- </handlers>
- </config>
- ]]></attribute>
+<delegate-config>
+<attribute name="Configuration"><![CDATA[
+<config>
+<invoker transport="bisocket">
+ <attribute name="marshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="unmarshaller" isParam="true">
+ org.jboss.jms.wireformat.JMSWireFormat</attribute>
+ <attribute name="serializationtype" isParam="true">jms</attribute>
+ <attribute name="dataType" isParam="true">jms</attribute>
+ <attribute name="socket.check_connection" isParam="true">false</attribute>
+ <attribute name="timeout" isParam="true">0</attribute>
+ <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
+ <attribute name="serverBindPort">4457</attribute>
+ <attribute name="leasePeriod">10000</attribute>
+ <attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
+ <attribute name="clientSocketClass" isParam="true">
+ org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
+ <attribute name="serverSocketClass">
+ org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
+ <attribute name="callbackErrorsAllowed">1</attribute>
+ <attribute name="numberOfRetries" isParam="true">1</attribute>
+ <attribute name="NumberOfCallRetries" isParam="true">2</attribute>
+ <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
+</invoker>
+<handlers>
+ <handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
+</handlers>
+</config>
+ ]]></attribute>
</delegate-config>
<binding port="4457"/>
</service-config></programlisting>
- <para>For ports-default use port 4457, ports-01 4557, ports-02
- 4657 and ports-03 4757</para>
- </listitem>
- </itemizedlist></para>
+ <para>For ports-default you could use port 4457, ports-01 4557,
+ ports-02 4657 and ports-03 4757.</para>
+ </listitem>
+ </itemizedlist>
</listitem>
</itemizedlist>
+
+ <para>There are few extra steps at <xref
+ linkend="install.extra-steps" /></para>
</section>
+
+ <section id="install.extra-steps">
+ <title>Extra steps after your instalation is complete</title>
+
+ <para>You should also make these changes on any configuration you
+ choose, to prevent references to the old JBossMQ:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Edit $JBOSS_SERVER/server/YourConfig/jms-ds.xml and replace
+ jboss.mq by jboss.messaging on every occurrence</para>
+ </listitem>
+
+ <listitem>
+ <para>Edit $JBOSS_SERVER/server/YourConfig/config/standardjboss.xml
+ and set CreateJBossMQDestination to false on every occurrence</para>
+
+ <para>Make sure it looks like this:</para>
+
+ <para><CreateJBossMQDestination>false</CreateJBossMQDestination></para>
+
+ <para>Those Proxies will try to create a Destination on JBossMQ if
+ they can't find it on JNDI, what would cause some errors related to
+ JBoss MQ.</para>
+ </listitem>
+
+ <listitem>
+ <para>Edit $JBOSS_SERVER/server/YourConfig/config/jboss-service.xml
+ and remove the reference to JBoss MQ on JSR-77 Management
+ Bean</para>
+
+ <programlisting>
+ <!-- ==================================================================== -->
+ <!-- JSR-77 Single JBoss Server Management Domain -->
+ <!-- ==================================================================== -->
+ <mbean code="org.jboss.management.j2ee.LocalJBossServerDomain"
+
+ ... Remove this line ...
+ <attribute name="JMSService">jboss.mq:service=DestinationManager</attribute>
+ </programlisting>
+ </listitem>
+
+ <listitem>
+ <para>Change $JBOSS_SERVICE/server/YourConfig/conf/login-config.xml
+ and remove jboss-mq security policies</para>
+
+ <programlisting>
+### Remove these lines:
+
+<!-- Security domain for JBossMQ -->
+<application-policy name = "jbossmq">
+ <authentication>
+ <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
+ flag = "required">
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "dsJndiName">java:/DefaultDS</module-option>
+ <module-option name = "principalsQuery">
+ SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
+ <module-option name = "rolesQuery">
+ SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
+ </login-module>
+ </authentication>
+</application-policy>
+
+<!-- Security domain for JBossMQ when using file-state-service.xml
+<application-policy name = "jbossmq">
+ <authentication>
+ <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
+ flag = "required">
+ <module-option name = "unauthenticatedIdentity">guest</module-option>
+ <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
+ </login-module>
+ </authentication>
+</application-policy>
+-->
+
+ </programlisting>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
<section id="install.old.installation">
@@ -262,13 +356,15 @@
<itemizedlist>
<listitem>
<para>Install JBoss Messaging using the most convenient way described
- on the <link linkend="installation">previous section</link>.</para>
+ on the <link linkend="installation">previous section</link> using the
+ default configuration as your base (even for a clustered JBoss
+ Messaging)</para>
</listitem>
<listitem>
- <para>Replace the jars on this following list. There is a /thirdparty
- directory on the release bundle for your convenience, or you could
- download these packages on http://www.jboss.org.</para>
+ <para>Replace the jars on this following list. You could download
+ these jars from www.jboss.org or use the repository links provided
+ bellow:</para>
<itemizedlist>
<listitem>
@@ -276,6 +372,9 @@
<para>JBoss AOP 1.5.5.GA+</para>
+ <para><ulink
+ url="http://repository.jboss.com/jboss/aop/1.5.5.GA/lib/">http://repository.jboss.com/jboss/aop/1.5.5.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>
</listitem>
@@ -284,12 +383,18 @@
<para>$JBOSS_HOME/server/<SERVER_NAME>/lib/javassist.jar</para>
<para>Javassist 3.5.0.GA-brew+</para>
+
+ <para><ulink
+ url="http://repository.jboss.com/javassist/3.5.0.GA-brew/lib/">http://repository.jboss.com/javassist/3.5.0.GA-brew/lib/</ulink></para>
</listitem>
<listitem>
<para>$JBOSS_HOME/server/<SERVER_NAME>/lib/jboss-remoting.jar</para>
<para>JBoss Remoting 2.2.0.SP4+</para>
+
+ <para><ulink
+ url="http://repository.jboss.com/jboss/remoting/2.2.0.SP4/lib/">http://repository.jboss.com/jboss/remoting/2.2.0.SP4/lib/</ulink></para>
</listitem>
<listitem>
@@ -297,6 +402,9 @@
using a clustered configuration)</para>
<para>JGroups 2.4.1.SP3-brew+</para>
+
+ <para><ulink
+ url="http://repository.jboss.com/jgroups/2.4.1.SP3-brew/lib/">http://repository.jboss.com/jgroups/2.4.1.SP3-brew/lib/</ulink></para>
</listitem>
</itemizedlist>
</listitem>
More information about the jboss-cvs-commits
mailing list