Added some generic "When" and "Use-Cases"

git-svn-id: 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/main/webapp/users-guide/activemq/activemq-index.conf b/src/main/webapp/users-guide/activemq/activemq-index.conf
index 9c50a12..28ae697 100644
--- a/src/main/webapp/users-guide/activemq/activemq-index.conf
+++ b/src/main/webapp/users-guide/activemq/activemq-index.conf
@@ -39,5 +39,21 @@
 If you want to use ActiveMQ as a JBI component, configure servicemix-jms. You can also utilize ActiveMQ from Camel via the
 camel-jms component.
+h3. When should I use ActiveMQ?
+Whenever you have a unit of work or payload that you could process asynchronously, you would like to have multiple recipients,
+concurrent competing recipients to scale or leverage multiple processing units. If you want to spread load across multiple
+system boundaries. You want to cluster or provide fail over and messaging security, you have long running flows.
+In any of these instances it would be strongly suggested you evaluate what a scalable and secure messaging solution can bring to the table.
+h3. Common use cases
+Integration with other systems, since you can pass messages in and out of ActiveMQ from pretty much any programming language
+it is very simple to start integrating heterogeneous environments.
+Providing an event driven architecture. You can develop your solutions based on actions as opposed to looking for data or
+relying on completely synchronous behaviour.
+Providing infrastructure for messaging across large distances, leverage the network connectors and broker networks to integrate
+for example geographically different data centres.