[jboss-cvs] JBoss Messaging SVN: r2709 - in trunk/docs/userguide/en: modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri May 18 00:32:51 EDT 2007
Author: clebert.suconic at jboss.com
Date: 2007-05-18 00:32:51 -0400 (Fri, 18 May 2007)
New Revision: 2709
Removed:
trunk/docs/userguide/en/modules/c_installation.xml
Modified:
trunk/docs/userguide/en/master.xml
trunk/docs/userguide/en/modules/installation.xml
Log:
http://jira.jboss.org/jira/browse/JBMESSAGING-968 - installation procedures (manual, clustered and other updates)
Modified: trunk/docs/userguide/en/master.xml
===================================================================
--- trunk/docs/userguide/en/master.xml 2007-05-17 21:45:43 UTC (rev 2708)
+++ trunk/docs/userguide/en/master.xml 2007-05-18 04:32:51 UTC (rev 2709)
@@ -6,7 +6,6 @@
<!ENTITY c_overview SYSTEM "modules/c_overview.xml">
<!ENTITY gettingstarted SYSTEM "modules/gettingstarted.xml">
<!ENTITY nc_installation SYSTEM "modules/installation.xml">
-<!ENTITY c_installation SYSTEM "modules/c_installation.xml">
<!ENTITY runningexamples SYSTEM "modules/runningexamples.xml">
<!ENTITY configuration SYSTEM "modules/configuration.xml">
<!ENTITY c_configuration SYSTEM "modules/c_configuration.xml">
@@ -32,8 +31,6 @@
&nc_installation;
- &c_installation;
-
&runningexamples;
&configuration;
Deleted: trunk/docs/userguide/en/modules/c_installation.xml
===================================================================
--- trunk/docs/userguide/en/modules/c_installation.xml 2007-05-17 21:45:43 UTC (rev 2708)
+++ trunk/docs/userguide/en/modules/c_installation.xml 2007-05-18 04:32:51 UTC (rev 2709)
@@ -1,319 +0,0 @@
-<chapter id="c_installation">
-
- <title>JBoss Messaging Clustered Installation</title>
-
- <note>
- You need Apache ant 1.7.0 or newer pre-installed on your system and available in
- you path in order to be able to perform the installation process described below.
- </note>
-
- <para>
- Use the <filename>release-admin.xml</filename> ant script shipped with the release to
- create individual cluster node configurations.
- </para>
-
- <para>
- The typical usage is:
- </para>
-
- <programlisting>
-cd util
-ant -f release-admin.xml [-Did=node-id] [-Dports=port-config-label]
-[-Ddatabase=db-name] cluster-node
- </programlisting>
- <para>
- where:
- <itemizedlist>
- <listitem>
- <filename>node-id</filename> is the unique node ID, an integer that must be unique per
- cluster. If not specified, it defaults to 0.
- </listitem>
- <listitem>
- <filename>port-config-label</filename> is a binding manager server configuration label.
-
- The short story behind this parameter is the following: multiple application servers
- running on the same physical machine need to use different service port ranges to avoid
- port conflicts. You can configure the whole port range used by a server instance
- by enabling a special service, the binding management service, and specifiying a
- "server" configuration in the binding manager's configuration file, which will determine
- specific port values to use when starting that instance.
-
- The Messaging installation script can enable the service binding manager and performs
- all configuration changes automatically. You only need to specify the "server"
- configuration you want to use, as 'port-config-label'.
-
- If you plan to run your clustering nodes on different physical machines, this parameter
- is irrelevant, and you should not use it. However, if you install two (or more) nodes of
- your cluster on the same physical machine, you need to give the value corresponding to
- a specific "server" configurations in the binding manager configuration file. JBoss AS
- ships "out-of-the-box" with several pre-configured port ranges: 'ports-default',
- 'ports-01', 'ports-02', 'ports-03'. Use one of these.
-
- If -Dports is not specified, the clustered instance created this way will fall over to
- the default port range for a JBoss instace.
-
- More details about the binding management service can be found in the Application Server
- documentation, at the following address
- <ulink url="http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#ch10.bindingmanager">http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#ch10.bindingmanager</ulink>
- </listitem>
- <listitem>
- <filename>db-name</filename> is the name of the database you want to create the configurations for. Supported database names are: mysql, oracle,
- postgresql, mssql, and sybase. Notice that if you create database configuration to any database other than MySQL, you will still need to
- manually install the database JDBC drivers (MySQL drivers are provided as part of the distribution).
- </listitem>
- </itemizedlist>
- </para>
-
- <para>
- Notice that you should have environment variable JBOSS_HOME correctly set to point to your JBoss AS distribution directory before executing any of the
- scripts.
- </para>
-
- <para>
- For example, in order to create the configuration for a four-node cluster intended to run
- on the same physical machine, use the following sequence:
- </para>
-
- <programlisting>
-ant -f release-admin.xml cluster-node
-ant -f release-admin.xml -Did=1 -Dports=ports-01 cluster-node
-ant -f release-admin.xml -Did=2 -Dports=ports-02 cluster-node
-ant -f release-admin.xml -Did=3 -Dports=ports-03 cluster-node
- </programlisting>
-
- <para>
- The sequence will create four cluster node configurations ("messaging-node0",
- "messaging-node1", "messaging-node2" and "messaging-node3").
- </para>
-
- <para>
- The first command will create a cluster node with ID equals to '0' and using the
- default JBoss AS port assignments.
- </para>
-
- <para>
- <warning>
- The configuration that has just been created uses a generic mysql service descriptor.
-
- Check <filename>$JBOSS_HOME/server/messaging-node<id>/deploy/mysql-ds.xml</filename>
- and verify that that:
- <itemizedlist>
- <listitem>1. Your database is indeed mysql.</listitem>
- <listitem>2. It is accessible from every physical node you installed Messaging on.</listitem>
- <listitem>3. Contains a schema (database/tablespace) named 'messaging'.</listitem>
- <listitem>4. The URL (hostname and port), username and password are correct.</listitem>
- <listitem>5. The installed mysql-driver.jar's version maches your database.</listitem>
- </itemizedlist>
- </warning>
- </para>
-
-
- <para>
- To start the cluster, from four different terminals, run:
- </para>
-
- <programlisting>
-cd $JBOSS_HOME/bin
-./run.sh -c messaging-node0
-
-cd $JBOSS_HOME/bin
-./run.sh -c messaging-node1
-
-cd $JBOSS_HOME/bin
-./run.sh -c messaging-node2
-
-cd $JBOSS_HOME/bin
-./run.sh -c messaging-node3
- </programlisting>
-
-
- <para>
- A successful two node cluster startup produces a log similar to:
- </para>
-
-
- <para>
- Node 0:
- </para>
-
-
- <programlisting>
-...
-
-00:24:04,796 WARN [JDBCPersistenceManager]
-
-JBoss Messaging Warning:
- DataSource connection transaction isolation should be READ_COMMITTED, but it
- is currently REPEATABLE_READ.
- Using an isolation level less strict than READ_COMMITTED may lead to data
- consistency problems.
- Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
-
-00:24:05,718 INFO [ServerPeer] JBoss Messaging 1.2.0.CR1 server [0] started
-00:24:06,328 INFO [STDOUT]
--------------------------------------------------------
-GMS: address is 127.0.0.1:2452
--------------------------------------------------------
-00:24:08,406 INFO [DefaultClusteredPostOffice] ClusteredPostOffice
-[0:Clustered JMS:127.0.0.1:2452] got new view [127.0.0.1:2452|0] [127.0.0.1:2452]
-00:24:08,468 INFO [STDOUT]
--------------------------------------------------------
-GMS: address is 127.0.0.1:2455
--------------------------------------------------------
-00:24:10,906 INFO [ConnectionFactory] Connector socket://10.11.14.105:4457 has leasing
-enabled, lease period 10000 milliseconds
-00:24:10,921 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory,
-java:/ConnectionFactory, java:/XAConnectionFactory] started
-00:24:10,953 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,953 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,953 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,953 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/A] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/B] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/C] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/D] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,968 INFO [QueueService] Queue[/queue/ex] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:24:10,984 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:24:11,000 INFO [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:11,000 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:24:11,093 INFO [ConnectionFactoryBindingService] Bound
-ConnectionManager'jboss.jca:name=JmsXA,service=ConnectionFactoryBinding' to JNDI
-name 'java:JmsXA'
-00:24:11,375 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
-warUrl=.../deploy/jmx-console.war/
-00:24:12,171 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
-00:24:12,421 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
-00:24:12,453 INFO [JkMain] Jk running ID=0 time=0/47 config=null
-00:24:12,515 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0
-date=200611221632)]
-Started in 30s:375ms
-
-00:27:21,343 INFO [DefaultClusteredPostOffice] ClusteredPostOffice
-[0:Clustered JMS:127.0.0.1:2452] got new view [127.0.0.1:2452|1]
-[127.0.0.1:2452, 127.0.0.1:2474]
-
-</programlisting>
-
- <para>
- Node 1:
- </para>
-
- <programlisting>
-
-...
-
-00:33:54,468 WARN [JDBCPersistenceManager]
-
-JBoss Messaging Warning:
-DataSource connection transaction isolation should be READ_COMMITTED, but it is
-currently REPEATABLE_READ.
-Using an isolation level less strict than READ_COMMITTED may lead to data consistency
-problems.
-Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
-
-00:33:55,062 INFO [ServerPeer] JBoss Messaging 1.2.0.CR1 server [1] started
-00:33:55,609 INFO [STDOUT]
--------------------------------------------------------
-GMS: address is 127.0.0.1:2514
--------------------------------------------------------
-00:33:57,734 INFO [DefaultClusteredPostOffice]
-ClusteredPostOffice[1:Clustered JMS:127.0.0.1:2514] got new
-view [127.0.0.1:2452|3] [127.0.0.1:2452, 127.0.0.1:2514]
-00:33:57,765 INFO [STDOUT]
--------------------------------------------------------
-GMS: address is 127.0.0.1:2519
--------------------------------------------------------
-00:34:00,203 INFO [ConnectionFactory] Connector socket://10.11.14.105:4557 has leasing
-enabled, lease period 20000 milliseconds
-00:34:00,203 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory,
-java:/ConnectionFactory, java:/XAConnectionFactory] started
-00:34:00,234 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=75000, pageSize=2000,
-downCacheSize=2000
-00:34:00,234 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,234 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/A] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/B] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/C] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/D] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,250 INFO [QueueService] Queue[/queue/ex] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=75000,
-pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started,
-fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,265 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,296 INFO [QueueService] Queue[/queue/testDistributedQueue]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,296 INFO [TopicService] Topic[/topic/testDistributedTopic]
-started, fullSize=75000, pageSize=2000, downCacheSize=2000
-00:34:00,343 INFO [ConnectionFactoryBindingService] Bound
-ConnectionManager 'jboss.jca:name=JmsXA,
-service=ConnectionFactoryBinding' to JNDI name 'java:JmsXA'
-00:34:00,453 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console,
-warUrl=.../deploy/jmx-console.war/
-00:34:00,796 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8180
-00:34:01,078 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8109
-00:34:01,125 INFO [JkMain] Jk running ID=0 time=0/125 config=null
-00:34:01,125 INFO [Server] JBoss (MX MicroKernel)
-[4.0.5.GA (build: CVSTag=Branch_4_0 date=200611221632)] Started in 22s:547ms
-
-
- </programlisting>
-
-
- <note>
- The installation script may fail while installing Messaging with source-generated
- JBoss 4.0.5.GA-ejb3 instance. This is because release-admin.xml relies on finding
- <filename>$JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml</filename>.
- 4.0.5.GA-ejb3 installations seem not to have a "docs" sub-directory. A very simple work-around
- for this situation is to recursively copy the "docs" sub-directory available under a regular
- (non-EJB3) source-generated 4.0.5.GA instance and retry the installation process.
- </note>
-
-
-</chapter>
Modified: trunk/docs/userguide/en/modules/installation.xml
===================================================================
--- trunk/docs/userguide/en/modules/installation.xml 2007-05-17 21:45:43 UTC (rev 2708)
+++ trunk/docs/userguide/en/modules/installation.xml 2007-05-18 04:32:51 UTC (rev 2709)
@@ -1,12 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="installation">
- <title>JBoss Messaging Non-Clustered Installation</title>
+ <title>JBoss Messaging Installation</title>
- <para>This section describes the procedure to perfom a non-clustered
- installation. At the end of this procedure, you will create a JBoss
- Messaging configuration that will start a non-clustered messaging server. To
- find out how you can install JBoss Messaging in a clustered configuration,
- please proceed to <xref linkend="c_installation" />.</para>
+ <para>This section describes procedures on how to install JBoss Messaging
+ into JBoss AS. At the end of this procedure, you will create a JBoss
+ Messaging configuration that will start a clustered or non-clustered
+ messaging server.</para>
<para>By default, a JBoss AS 4.0.x and 4.2.0 instance ships with JBossMQ as
default JMS provider. In order to use the JBoss AS instance with JBoss
@@ -29,7 +28,7 @@
<title>Installing JBoss Messaging on JBoss AS 4.2.0.GA</title>
<section id="install4.automated">
- <title>Installation procedure</title>
+ <title>Automated Non Clustered Installation</title>
<para>Set up the <literal>JBOSS_HOME</literal> environment variable to
point to the JBoss 4.x installation you want to use JBoss Messaging
@@ -61,65 +60,255 @@
</note>
</section>
- <section id="install.old.installation">
- <title>JBoss Messaging on JBoss 4.0.4.GA and JBoss 4.0.5.GA</title>
+ <section id="install.manual">
+ <title>Manual Non Clustered Installation</title>
- <note>
- You should avoid using JBossMessaging on any version prior to JBoss 4.2.0.GA, such as 4.0.5.GA and 4.0.4.GA. JBoss Messaging uses newer versions of JBoss AOP, JBoss Remoting and JGroups compared to JBoss 4.0.X. If you really need to install JBoss Messaging on those versions you will have to update those jars as described on this section but this might cause problems with other components such as JBoss Web Services and EJB3.
- </note>
+ <para>For this procedure we suppose you have a standard configuration
+ such as default or all. Consider
+ JBOSS_CONFIG=$JBOSS_HOME/server/<YourConfiguration>:</para>
<itemizedlist>
<listitem>
- <para>Execute ant -f release-admin as described on the previous
- section</para>
+ <para>Move JBOSS_CONFIG/deploy/jms/jms-ds.xml and
+ JBOSS_CONFIG/deploy/jms/jms-ra.rar to JBOSS_CONFIG/deploy</para>
</listitem>
<listitem>
- <para>Replace these jars. There is a /thirdparty directory on the
- release bundle you could use as source, or download these packages
- accordingly:</para>
+ <para>Remove the old JBoss MQ by removing
+ JBOSS_CONFIG/deploy/jms.</para>
- <itemizedlist>
- <listitem>
- <para>$JBOSS_HOME/server/<SERVER_NAME>/deploy/jboss-aop.deployer/jboss-aop.jar</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>
+ </listitem>
- <para>JBoss AOP 1.5.5.GA+</para>
+ <listitem>
+ <para>Add a security policy called "messaging" on
+ JBOSS_CONFIG/config/login-config.xml. You could use this as an
+ example, or create one according to JBoss Security
+ Documentation:</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>
+ <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>
+</application-policy>
+ </programlisting>
+ <para>Case you are using this provided policy you should also create
+ messaging-users.properties and messaging-roles.properties to
+ JBOSS_CONFIG/config/props/</para>
+
+ <programlisting>
+# messaging-roles.properties
+# Add roles as you like
+# user=role1,role2,...
+#
+guest=guest
+ </programlisting>
+
+ <programlisting>
+# messaging-users.properties
+
+# Add users as you like
+# user=password
+#
+guest=guest
+ </programlisting>
+ </listitem>
+
+ <listitem>
+ <para>Unzip jboss-messaging.sar from your download package into
+ JBOSS_CONFIG/deploy/jboss-messaging.sar</para>
+ </listitem>
+
+ <listitem>
+ <para>For use in production it is highly recommended to use a
+ different database other than HSQLDB.</para>
+
+ <itemizedlist>
<listitem>
- <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/javassist.jar</para>
-
- <para>Javassist 3.5.0.GA-brew+</para>
+ <para>Replace
+ JBOSS_CONFIG/deploy/jboss-messaging.sar/hsqldb-persistence-service.xml
+ by the persistence-service of from
+ <downloadPackage>/examples/config.</para>
</listitem>
<listitem>
- <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/jboss-remoting.jar</para>
-
- <para>JBoss Remoting 2.2.0.SP4+</para>
+ <para>Configure a JCA datasource using an example from
+ $JBOSS_HOME/docs/examples/jca</para>
</listitem>
<listitem>
- <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/jgroups.jar (if
- using a clustered configuration)</para>
-
- <para>JGroups 2.4.1.SP3-brew+</para>
+ <para>Remove hsqldb-ds.xml from JBOSS_CONFIG/deploy</para>
</listitem>
</itemizedlist>
</listitem>
+ </itemizedlist>
+ </section>
+ <section id="install.clustered">
+ <title>Clustered Installation</title>
+
+ <para></para>
+
+ <itemizedlist>
<listitem>
- <para>Make sure you use jboss-messaging-fat-client.jar on any client
- VM. This file should have precedence on jboss-all-client.jar on the
- ClassPath</para>
+ <para>Install JBoss Messaging using <xref
+ linkend="install.manual" /> or <xref linkend="install4.automated" />
+ using the "all" (clustered) configuration</para>
</listitem>
+
+ <listitem>
+ <para>Ensure the server id in messaging-service.xml is unique on
+ each node on the cluster</para>
+ </listitem>
+
+ <listitem>
+ <para>replace hsqldb-persistence-service.xml with
+ YourDatabase-clustered-persistence-service.xml from
+ downloadPackage/examples/config</para>
+ </listitem>
+
+ <listitem>
+ <para>Deploy a JCA datasource as in
+ $JBOSS_SERVER/docs/examples/jca</para>
+
+ <para>Make sure is bound to /DefaultDS and remove
+ hsqldb-ds.xml.</para>
+ </listitem>
+
+ <listitem>
+ <para>Install your database driver jar into
+ $JBOSS_SERVER/<YourServer>/lib</para>
+ </listitem>
+
+ <listitem>
+ <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>
+
+ <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>
+
+ <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>
+ <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>
+ </listitem>
</itemizedlist>
</section>
</section>
+ <section id="install.old.installation">
+ <title>JBoss Messaging on JBoss 4.0.4.GA and JBoss 4.0.5.GA</title>
+
+ <warning>
+ You should avoid using JBossMessaging on any version prior to JBoss 4.2.0.GA, such as 4.0.5.GA and 4.0.4.GA. JBoss Messaging uses newer versions of JBoss AOP, JBoss Remoting and JGroups compared to JBoss 4.0.X. If you really need to install JBoss Messaging on those versions you will have to update those jars as described on this section but this might cause problems with other components such as JBoss Web Services and EJB3.
+ </warning>
+
+ <itemizedlist>
+ <listitem>
+ <para>Install JBoss Messaging using the most convenient way described
+ on the <link linkend="installation">previous section</link>.</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>
+
+ <itemizedlist>
+ <listitem>
+ <para>$JBOSS_HOME/server/<SERVER_NAME>/deploy/jboss-aop.deployer/jboss-aop.jar</para>
+
+ <para>JBoss AOP 1.5.5.GA+</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>
+
+ <listitem>
+ <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/javassist.jar</para>
+
+ <para>Javassist 3.5.0.GA-brew+</para>
+ </listitem>
+
+ <listitem>
+ <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/jboss-remoting.jar</para>
+
+ <para>JBoss Remoting 2.2.0.SP4+</para>
+ </listitem>
+
+ <listitem>
+ <para>$JBOSS_HOME/server/<SERVER_NAME>/lib/jgroups.jar (if
+ using a clustered configuration)</para>
+
+ <para>JGroups 2.4.1.SP3-brew+</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>Make sure you use jboss-messaging-fat-client.jar on any client
+ VM. This file should have precedence on jboss-all-client.jar on the
+ ClassPath</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
<section id="startingtheservice">
<title>Starting the Server</title>
More information about the jboss-cvs-commits
mailing list