Permalink
Browse files

initial commit

  • Loading branch information...
0 parents commit a9fcbe2c5f72119021c8af26561c9669d2fcd10e markbrooks committed Jun 5, 2012
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
@@ -0,0 +1 @@
+Copyright 2012 FuseSource
@@ -0,0 +1,179 @@
+External MQ-Fabric Client Demo
+==============================
+
+This project shows how to connect to Fuse MQ message broker running in Fuse Fabric from a JMS client running outside of Fuse Fabric (i.e. when the JMS client is not running within a managed Fuse ESB container).
+
+This project reuses the classes and resources from Fuse By Example's "Getting Started with ActiveMQ" project to demonstrate the minimal changes necessary to discover and connect to Fuse MQ brokers deployed within Fuse Fabric.
+
+The Getting Started with ActiveMQ project's used brokerUrl like this:
+
+ failover:(tcp://host1:port1,tcp://host2:port2)
+
+which are now replaced with values like this:
+
+ discovery:(fabric:broker-group-name)
+
+In addition to changing the brokerUrl's, two other changes are needed to support fabric discovery: a "zookeeper.url" System property needs to be set in the environment, and a few fabric libraries must be added to the classpath.
+
+
+Setting the zookeeper.url
+-------------------------
+
+On a typical developer machine, with Fuse Management Console running locally, the zookeeper.url System property should be set to point to the URL of the Fuse Fabric's Zookeeper instance which defaults to localhost:2181. One can append
+
+ -Dzookeeper.url=localhost:2181
+
+to the startup command line, or add
+
+ <systemProperty>
+ <key>zookeeper.url</key>
+ <value>localhost:2181</value>
+ </systemProperty>
+
+to the maven profile configuration, as is done in this project.
+
+
+Adding the fabric libraries
+---------------------------
+
+These are the dependencies added to pom.xml to support the fabric discovery protocol:
+
+ <dependency>
+ <groupId>org.fusesource.mq</groupId>
+ <artifactId>mq-fabric</artifactId>
+ <version>${mq.fabric.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.fusesource.fabric</groupId>
+ <artifactId>fabric-groups</artifactId>
+ <version>${fabric.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.fusesource.fabric</groupId>
+ <artifactId>fabric-zookeeper</artifactId>
+ <version>${fabric.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.fusesource.fabric</groupId>
+ <artifactId>fabric-linkedin-zookeeper</artifactId>
+ <version>${fabric.version}</version>
+ </dependency>
+
+
+Building the example
+--------------------
+
+To build the example, execute the command:
+
+ > mvn clean install
+
+
+
+Running the example against a default fabric broker
+---------------------------------------------------
+
+Make sure an instance of Fuse MQ message broker in the default group is running in fabric; if not, see below for instructions on deploying a default fabric-based broker.
+
+To start the default consumer open a shell, change to the project root and run the command:
+
+ > mvn -e -P consumer-default
+
+After the consumer is running, open another shell, change to the project root and run the command:
+
+ > mvn -e -P producer-default
+
+Here are some console messages you should see when running the example:
+
+ ******************************
+ Connecting to Fuse MQ Broker using URL: discovery:(fabric:default)
+ ******************************
+ Using local ZKClient
+ Client environment:zookeeper.version=3.4.3-1240972...
+ ...
+ Initiating client connection, connectString=localhost:2181 sessionTimeout=10000 watcher=org.linkedin.zookeeper.client.ZKClient@12133926
+ Opening socket connection to server /0:0:0:0:0:0:0:1:2181
+ ...
+ Socket connection established to localhost/0:0:0:0:0:0:0:1:2181, initiating session
+ Session establishment complete on server localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x137bcd28a79000b, negotiated timeout = 10000
+ Starting StateChangeDispatcher
+ Adding new broker connection URL: tcp://mbrooks1.local:50865
+ Successfully connected to tcp://mbrooks1.local:50865
+ Start consuming messages from queue://test.fabric.simple with 120000ms timeout
+ Got 1. message: 1. message sent
+ Got 2. message: 2. message sent
+ Got 3. message: 3. message sent
+ ...
+
+
+Running the example against a fabric-based network of fault-tolerant brokers
+----------------------------------------------------------------------------
+
+Start a fabric-based network of fault-tolerant (master/slave) brokers. For instructions on how to configure and deploy such a network, see the blog post [here](http://fusebyexample.blogspot.com/2012/06/using-fuse-management-console-and-fuse.html). Summary instructions are also included below.
+
+This network features two broker groups: mq-east and mq-west
+
+To start the consumer open a shell, cd to the project root and run the command:
+
+ > mvn -e -P consumer-west
+
+After the consumer is running, open another shell, cd to the project root and run the command:
+
+ > mvn -e -P producer-east
+
+You should see console messages that show the producer connected using the URL
+
+ discovery:(fabric:mq-east)
+
+and the consumer connected using the URL:
+
+ discovery:(fabric:mq-west)
+
+After the example is up and running and you see JMS messages being logged to the consumer's console, kill the broker running in the container MQ-East1 (you can stop the container using FMC, or kill the container's process in the OS) and watch the producer failover, reconnect and resume sending messages, with console output like this:
+
+ ...
+ Sending to destination: queue://fabric.simple this text: '23. message sent
+ Sending to destination: queue://fabric.simple this text: '24. message sent
+ Sending to destination: queue://fabric.simple this text: '25. message sent
+ WARN Transport (tcp://192.168.0.14:51779) failed, reason: java.io.EOFException, attempting to automatically reconnect
+ Adding new broker connection URL: tcp://mbrooks1.local:51805
+ Successfully reconnected to tcp://mbrooks1.local:51805
+ Sending to destination: queue://fabric.simple this text: '26. message sent
+ Sending to destination: queue://fabric.simple this text: '27. message sent
+ ...
+
+then kill the container MQ-West1 and observe similar failover and reconnection by the consumer.
+
+
+
+Deploying a default Fuse MQ message broker in fabric
+----------------------------------------------------
+
+Here are brief instructions on how to deploy a default instance of Fuse MQ message broker in fabric:
+
+* Launch Fuse Management Console (FMC). FMC info and downloads are [here](http://fusesource.com/products/fuse-management-console)
+
+* Connect to FMC in a browser, create a fabric if one does not yet exist and login using admin | admin credentials.
+
+* Click the Create Fuse Container button, then Next, name the container MQ (the name is not critical), click Next, select the mq profile, click Next, select Child container, click Next, select FuseManagementConsole as the parent and click Finish. The broker instance will be registered in fabric in the default group
+
+
+Deploying a fabric-based network of fault-tolerant message brokers
+------------------------------------------------------------------
+
+Here are brief instructions on deploying a fabric-based network of fault-tolerant (master/slave) message brokers. See see the blog post [here](http://fusebyexample.blogspot.com/2012/06/using-fuse-management-console-and-fuse.html) for a more complete description.
+
+* Launch Fuse Management Console (FMC).
+
+* Connect to FMC in a browser, create a fabric if one does not yet exist and login using admin | admin credentials.
+
+* Execute the following four commands one at a time in the FMC terminal:
+
+ &gt; container-create-child FuseManagementConsole MQ-East 2
+
+ &gt; container-create-child FuseManagementConsole MQ-West 2
+
+ &gt; mq-create --group mq-east --networks mq-west --assign-container MQ-East1,MQ-East2 mq-east-broker
+
+ &gt; mq-create --group mq-west --networks mq-east --assign-container MQ-West1,MQ-West2 mq-west-broker
+
+
Oops, something went wrong. Retry.

0 comments on commit a9fcbe2

Please sign in to comment.