[jboss-cvs] JBoss Messaging SVN: r2531 - trunk/docs/userguide-1.2/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Mar 1 05:22:47 EST 2007
Author: ovidiu.feodorov at jboss.com
Date: 2007-03-01 05:22:47 -0500 (Thu, 01 Mar 2007)
New Revision: 2531
Modified:
trunk/docs/userguide-1.2/en/modules/UG12_configuration.xml
Log:
more doc work
Modified: trunk/docs/userguide-1.2/en/modules/UG12_configuration.xml
===================================================================
--- trunk/docs/userguide-1.2/en/modules/UG12_configuration.xml 2007-03-01 10:18:17 UTC (rev 2530)
+++ trunk/docs/userguide-1.2/en/modules/UG12_configuration.xml 2007-03-01 10:22:47 UTC (rev 2531)
@@ -1,20 +1,32 @@
<chapter id="UG2_configuration">
<title>Configuration</title>
- <para>The JMS API specifies how a messaging client interacts with a messaging server. The exact definition and implementation of messaging services, such as message destinations and connection factories, are specific to JMS providers. JBoss Messaging has its own configuration files to configure services. If you are migrating services from JBossMQ (or other JMS provider) to JBoss Messaging, you will need to understand those configuration files.</para>
+ <para>
+ The JMS API specifies how a messaging client interacts with a messaging server. The exact
+ definition and implementation of messaging services, such as message destinations and
+ connection factories, are specific to JMS providers. JBoss Messaging has its own
+ configuration files to configure services. If you are migrating services from JBossMQ
+ (or other JMS provider) to JBoss Messaging, you will need to understand those
+ configuration files.
+ </para>
- <para>In this chapter, we discuss how to configure various services inside JBoss Messaging, which work together to provide JMS API level
- services to client applications.</para>
+ <para>
+ In this chapter, we discuss how to configure various services inside JBoss Messaging,
+ which work together to provide JMS API level services to client applications.
+ </para>
<para>
- Starting with the JBoss Messaging 1.0.1 release, the service configuration is spread among several configuration files.
- (The 1.0.0 release used to have all configuration information lumped together in the SAR's deployment
- descriptor <filename>jboss-messaging.sar/META-INF/jboss-service.xml</filename>). Depending
- on the functionality provided by the services it configures, the configuration data is
- distributed between
+ Starting with the JBoss Messaging 1.0.1 release, the service configuration is spread among
+ several configuration files (the 1.0.0 release used to have all configuration information
+ lumped together in the SAR's deployment descriptor
+ <filename>jboss-messaging.sar/META-INF/jboss-service.xml</filename>).
+ Depending on the functionality provided by the services it configures, the configuration
+ data is distributed between
<filename>messaging-service.xml</filename>,
<filename>remoting-service.xml</filename>,
- <filename>xxx-persistence-service.xml</filename>,
+ <filename>xxx-persistence-service.xml</filename>
+ (or <filename>clustered-xxx-persistence-service.xml</filename> for a clustered configuration,
+ more about clusterered configuration in <xref linkend="CLUST_configuration"/>),
<filename>connection-factories-service.xml</filename> and
<filename>destinations-service.xml</filename>.
</para>
@@ -29,49 +41,51 @@
<para>
The Server Peer is the "heart" of the JBoss Messaging JMS facade. The server's configuration,
- together with the configuration of several core plug-ins (ThreadPool and the
- MessageStore), resides in <filename>messaging-service.xml</filename> configuration file.
+ resides in <filename>messaging-service.xml</filename> configuration file.
</para>
<para>An example of a Server Peer configuration is presented below</para>
<programlisting>
+ <mbean code="org.jboss.jms.server.ServerPeer"
+ name="jboss.messaging:service=ServerPeer"
+ xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
-<mbean code="org.jboss.jms.server.ServerPeer"
- name="jboss.messaging:service=ServerPeer"
- xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
+ <constructor>
+ <!-- ServerPeerID -->
+ <arg type="int" value="0"/>
+ <!-- DefaultQueueJNDIContext -->
+ <arg type="java.lang.String" value="/queue"/>
+ <!-- DefaultTopicJNDIContext -->
+ <arg type="java.lang.String" value="/topic"/>
+ </constructor>
- <constructor>
- <!-- ServerPeerID -->
- <arg type="java.lang.String" value="server.0"/>
- <!-- DefaultQueueJNDIContext -->
- <arg type="java.lang.String" value="/queue"/>
- <!-- DefaultTopicJNDIContext -->
- <arg type="java.lang.String" value="/topic"/>
- </constructor>
+ <attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>
+ <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
+ <attribute name="DefaultSecurityConfig">
+ <security>
+ <role name="guest" read="true" write="true" create="true"/>
+ </security>
+ </attribute>
+ <attribute name="DefaultDLQ">
+ jboss.messaging.destination:service=Queue,name=DLQ</attribute>
+ <attribute name="DefaultMaxDeliveryAttempts">10</attribute>
+ <attribute name="DefaultExpiryQueue">
+ jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
+ <attribute name="DefaultRedeliveryDelay">0</attribute>
+ <attribute name="QueueStatsSamplePeriod">5000</attribute>
+ <attribute name="FailoverStartTimeout">60000</attribute>
+ <attribute name="FailoverCompleteTimeout">300000</attribute>
+ <attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
- <depends optional-attribute-name="ThreadPool">
-jboss.messaging:service=ThreadPool
-</depends>
- <depends optional-attribute-name="PersistenceManager"
- >jboss.messaging:service=PersistenceManager</depends>
- <depends optional-attribute-name="MessageStore">
-jboss.messaging:service=MessageStore
- </depends>
- <depends optional-attribute-name="ChannelMapper">
-jboss.messaging:service=ChannelMapper
- </depends>
+ <depends optional-attribute-name="PersistenceManager">
+ jboss.messaging:service=PersistenceManager</depends>
+ <depends optional-attribute-name="JMSUserManager">
+ jboss.messaging:service=JMSUserManager</depends>
+ <depends>jboss.messaging:service=Connector,transport=bisocket</depends>
- <!-- Set to -1 to completely disable client leasing -->
- <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
- <attribute name="DefaultSecurityConfig">
- <security>
- <role name="guest" read="true" write="true" create="true"/>
- </security>
- </attribute>
</mbean>
-
</programlisting>
<section id="conf.serverpeer.securitydomain">
@@ -231,21 +245,21 @@
<attribute name="CreateTablesOnStartup">true</attribute>
<attribute name="UsingBatchUpdates">true</attribute>
<attribute name="SqlProperties"><![CDATA[
-CREATE_MESSAGE_REF=CREATE TABLE JMS_MESSAGE_REFERENCE
- (CHANNELID BIGINT, MESSAGEID BIGINT, TRANSACTIONID BIGINT, STATE CHAR(1),
- ORD BIGINT, DELIVERYCOUNT INTEGER, RELIABLE CHAR(1), LOADED CHAR(1),
+CREATE_MESSAGE_REF=CREATE TABLE JMS_MESSAGE_REFERENCE
+ (CHANNELID BIGINT, MESSAGEID BIGINT, TRANSACTIONID BIGINT, STATE CHAR(1),
+ ORD BIGINT, DELIVERYCOUNT INTEGER, RELIABLE CHAR(1), LOADED CHAR(1),
PRIMARY KEY(CHANNELID, MESSAGEID))
-CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JMS_MESSAGE_REF_TX ON
+CREATE_IDX_MESSAGE_REF_TX=CREATE INDEX JMS_MESSAGE_REF_TX ON
JMS_MESSAGE_REFERENCE (TRANSACTIONID)
CREATE_IDX_MESSAGE_REF_ORD=CREATE INDEX JMS_MESSAGE_REF_ORD ON JMS_MESSAGE_REFERENCE (ORD)
-CREATE_IDX_MESSAGE_REF_MESSAGEID=CREATE INDEX JMS_MESSAGE_REF_MESSAGEID ON
+CREATE_IDX_MESSAGE_REF_MESSAGEID=CREATE INDEX JMS_MESSAGE_REF_MESSAGEID ON
JMS_MESSAGE_REFERENCE (MESSAGEID)
-CREATE_IDX_MESSAGE_REF_LOADED=CREATE INDEX JMS_MESSAGE_REF_LOADED ON
+CREATE_IDX_MESSAGE_REF_LOADED=CREATE INDEX JMS_MESSAGE_REF_LOADED ON
JMS_MESSAGE_REFERENCE (LOADED)
-CREATE_IDX_MESSAGE_REF_RELIABLE=CREATE INDEX JMS_MESSAGE_REF_RELIABLE ON
+CREATE_IDX_MESSAGE_REF_RELIABLE=CREATE INDEX JMS_MESSAGE_REF_RELIABLE ON
JMS_MESSAGE_REFERENCE (RELIABLE)
-INSERT_MESSAGE_REF=INSERT INTO JMS_MESSAGE_REFERENCE (CHANNELID, MESSAGEID,
- TRANSACTIONID, STATE, ORD, DELIVERYCOUNT, RELIABLE, LOADED)
+INSERT_MESSAGE_REF=INSERT INTO JMS_MESSAGE_REFERENCE (CHANNELID, MESSAGEID,
+ TRANSACTIONID, STATE, ORD, DELIVERYCOUNT, RELIABLE, LOADED)
VALUES (?, ?, ?, ?, ?, ?, ?, ?)
.... ]]>
</attribute>
@@ -260,9 +274,9 @@
jboss:service=TransactionManager</depends>
<attribute name="DataSource">java:/DefaultDS</attribute>
<attribute name="SqlProperties"><![CDATA[
-CREATE_USER_TABLE=CREATE TABLE JMS_USER (USERID VARCHAR(32) NOT NULL,
+CREATE_USER_TABLE=CREATE TABLE JMS_USER (USERID VARCHAR(32) NOT NULL,
PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128), PRIMARY KEY(USERID))
-CREATE_ROLE_TABLE=CREATE TABLE JMS_ROLE (ROLEID VARCHAR(32) NOT NULL,
+CREATE_ROLE_TABLE=CREATE TABLE JMS_ROLE (ROLEID VARCHAR(32) NOT NULL,
USERID VARCHAR(32) NOT NULL, PRIMARY KEY(USERID, ROLEID))
SELECT_PRECONF_CLIENTID=SELECT CLIENTID FROM JMS_USER WHERE USERID=?
....
@@ -530,7 +544,7 @@
<loader-repository>jboss.messaging:loader=ScopedLoaderRepository
<loader-repository-config>java2ParentDelegation=false</loader-repository-config>
</loader-repository>
- <mbean
+ <mbean
code="org.jboss.jms.server.destination.Queue"
name="jboss.messaging.destination:service=Queue,name=testQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
@@ -582,7 +596,7 @@
</para>
<programlisting>
- errrrrfff eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
+ errrrrfff eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
<?xml version="1.0" encoding="UTF-8"?>
<server>
<loader-repository>
@@ -591,7 +605,7 @@
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
- <mbean
+ <mbean
code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.destination:service=ConnectionFactory"
xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
@@ -615,7 +629,7 @@
</bindings>
</attribute>
</mbean>
-</server>
+</server>
</programlisting>
More information about the jboss-cvs-commits
mailing list