[jboss-cvs] JBossAS SVN: r75576 - in projects/docs/enterprise/4.3/examples/jboss-messaging-examples: queue-failover and 1 other directory.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2008-07-09 22:55:53 -0400 (Wed, 09 Jul 2008)
New Revision: 75576

Added:
   projects/docs/enterprise/4.3/examples/jboss-messaging-examples/README.txt
Modified:
   projects/docs/enterprise/4.3/examples/jboss-messaging-examples/queue-failover/build.xml
Log:
updated Messaging examples with fixes provided by Phillip and readme file


Added: projects/docs/enterprise/4.3/examples/jboss-messaging-examples/README.txt
===================================================================
--- projects/docs/enterprise/4.3/examples/jboss-messaging-examples/README.txt	                        (rev 0)
+++ projects/docs/enterprise/4.3/examples/jboss-messaging-examples/README.txt	2008-07-10 02:55:53 UTC (rev 75576)
@@ -0,0 +1,30 @@
+Running the JBoss Messaging Examples
+
+First set the environment variable JBOSS_HOME to point to your JBoss AS installation.
+
+export JBOSS_HOME=/home/jboss/jboss-eap-4.3/jboss-as
+
+To run the clustering examples, you will need to create a copy of the all configuration.  Use the following commands.
+cd $JBOSS_HOME/server
+cp -r all all2
+
+Now, we need to change the ports that the all2 configuration listens on since you can't have two instances listening on the same ports.
+Edit the file $JBOSS_HOME/server/all2/conf/jboss-service.xml.  If you scroll down a bit, you will see the heading "Binding Manager".  Place the following xml snippit below this heading.
+
+   <mbean code="org.jboss.services.binding.ServiceBindingManager"
+     name="jboss.system:service=ServiceBindingManager">
+     <attribute name="ServerName">ports-01</attribute>
+     <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute>
+     <attribute name="StoreFactoryClassName">
+       org.jboss.services.binding.XMLServicesStoreFactory
+     </attribute>
+   </mbean>
+
+Optionally, you could edit the file $JBOSS_HOME/server/all2/deploy/jboss-messaging.sar/messaging-service.xml.  You should change the ServerPeerID to '1' instead of '0'.  Another way of setting the server peer is with the jboss.messaging.ServerPeerID property as used below.
+
+To start the cluster you can use the following commands:
+
+./run.sh -c all -u 228.3.2.1 
+./run.sh -c all2 -u 228.3.2.1 -Djboss.messaging.ServerPeerID=1
+
+At this point, you should be able to run any of the messaging clustering examples.

Modified: projects/docs/enterprise/4.3/examples/jboss-messaging-examples/queue-failover/build.xml
===================================================================
--- projects/docs/enterprise/4.3/examples/jboss-messaging-examples/queue-failover/build.xml	2008-07-10 02:55:13 UTC (rev 75575)
+++ projects/docs/enterprise/4.3/examples/jboss-messaging-examples/queue-failover/build.xml	2008-07-10 02:55:53 UTC (rev 75576)
@@ -52,7 +52,7 @@
    </target>
 
    <target name="sanity-check" depends="identify">
-      <available property="client.jar.present" file="${messaging.client.jar.path}/${messaging.client.jar.name}"/>
+      <available property="client.jar.present" file="${jboss.home}/server/all/lib/${messaging.client.jar.name}"/>
       <fail message="Could not find client jar ${messaging.client.jar.path}/${messaging.client.jar.name}"
             unless="client.jar.present"/>
    </target>
@@ -83,8 +83,8 @@
 
    <target name="deploy" depends="jar">
       <copy file="./output/lib/application-server-killer.jar"
-            todir="${jboss.home}/server/messaging-node0/deploy"/>
-      <antcall target="sleep"><param name="sleep.interval" value="5"/></antcall>
+            todir="${jboss.home}/server/all/deploy"/>
+      <antcall target="sleep"><param name="sleep.interval" value="10"/></antcall>
    </target>
 
 
@@ -100,7 +100,7 @@
    </target>
 
    <target name="undeploy">
-      <delete file="${jboss.home}/server/messaging-node0/deploy/application-server-killer.jar" quiet="true"/>
+      <delete file="${jboss.home}/server/all/deploy/application-server-killer.jar" quiet="true"/>
    </target>
 
    <target name="clean" depends="undeploy">