I noticed on fabric container management console I couldn't find the Fuse MQ Details and Camel Details which is mentioned in JBOSS FUSE documentation.
Tried to add mq related profiles to the container, But I couldn't find the Fuse MQ Details and Camel Details button in the container details page.
Do I need to configure in anyother place to see the details.
I need to monitor the MQ in fabric container. But there is no details provided.
If you use the full distribution of Jboss Fuse, then it comes with AMQ broker out of the box. If you use medium or minimal, then you would need to create a broker first.
You can see this video how to create and setup a broker
http://vimeo.com/album/2635012/video/84674508
Likewise Apache Camel is only visible in the container perspective if the container has Camel running inside it.
Although on the Fabric perspective in the runtime page, there is an EIP sub tab, you can click to see a visual node diagram of all the Camel running in the JVM.
Related
I am new to Apache Camel. I have read several documentation of it and went through the examples (only of XML DSL) that Apache provide with its jar. I have a spring MVC project running over tomcat, and in the same project I need to include an Integration Framework. I have installed JBoss plugin for tooling so that I can drag and drop components but palette isn't showing any component but a message 'A palette is not working'. So, please suggest me how should I proceed to implement the same. For now I am referring Camel in Action. And, if possible, then provide an example to send a https request to any URL with some header parameters and transform its response and print it on console or write it to any file or give another https request to any other URL with the payload.
you mentioned that you installed the JBoss plugin for tooling, do you mean that you installed the JBoss Fuse Tooling?
Which version of Eclipse or JBoss Developer Studio are you using? Which OS are you using?
In Fuse Tooling, several examples are provided based on archetypes, I let you check the "CHAPTER 5. CREATING A NEW FUSE PROJECT" in
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/pdf/Tooling_User_Guide/Red_Hat_JBoss_Fuse-6.2.1-Tooling_User_Guide-en-US.pdf
We are trying to connect to MQ resource via activation specification. Referring some of old blog which points the camel JMS uses Spring JMS. Camel JMS have placeholder for messageListenerContainerFactoryRef which uses MessageListenerContainerFactory i.e., org.springframework.jms.listener.AbstractMessageListenerContainer.
We are able to make spring jms to use activation spec to connect to Websphere MQ using org.springframework.jms.listener.endpoint.JmsMessageEndpointManager. Refer Spring JMS and Websphere MQ.
Now I am unable to figure out the way to bridge JmsMessageEndpointManager with AbstractMessageListenerContainer implementation. Any direction regarding the same would be great help.
Do you think that a Spring destination resolver can help you here?
destinationResolver
null
A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).
I saw that HawtIO has a Dashboard that shows the flow of the route into each processor in it and the count for each call made.I checked into the apache Camel,I believe you are reading the JVM for getting the metrics of the Routes and the processors in it but what I don't understand is how are you able to construct this block diagram and the exact flow into each processor..
Can someone help me out with this.I am trying to build a similar UI such as hawtIO for specifically on Apache Camel and I want to know how it can be done?
Hawtio is getting its application insights with Jolokia. Jolokia is providing a HTTP bridge to JMX. So, in other words, all the informations you need are exposed by Camel MBeans via JMX.
So, you have two options to get hold of Camel's JMX info:
base your own UI on Jolokia as well.
go old school and use a JSR-160 connector.
I am still struggling with undertsanding some of Camel's main features and limitations.
My objective is to implement a demo application that can migrate camel endpoints. To achieve this everyone suggested that I should use the camel load-balancer pattern with the failover construct.
To achieve this objective people have suggested Fuse and ActiveMQ. Some have even suggested JBoss, but I am lost.
I understand that Camel needs the an implementation of a JMS server. To achieve this I can use ActiveMQ - a free implementation of a JMS server.
However camel also provies the jms-component. What is this? Is this a client implementation of JMS? If so, should I not be using an ActiveMQ client for JMS? Could someone provide a working example?
With ActiveMQ and JMS understood I can then try to find out why people suggest Fuse. I want my implementation to be as simple as possible. Why do I need Fuse? The Camel+ActiveMQ combination has the load balancer pattern with the failover mechanism right?
I am lost in this sea of new technologies, if someone could give a direction I would be thankful.
Camel provides two components. The first is the jms component, which is a generic API for working against JMS servers. The other is the activemq component, which uses the activemq API for working with activemq message brokers. The activemq component is the default component within things like servicemix/fuse, using an internal broker (not a networked/external broker).
If you are connecting to activemq, you can use either the activemq component or the jms component. The jms component will not start up a broker automatically, you would need to do this yourself.
Fusesource == JBoss Fuse == Apache ServiceMix + some addons. For argument sake, i'm going to refer to all three of these as ServiceMix.
ServiceMix is an enterprise service bus, you can lookup the term on wikipedia if you're not familiar with the concept. It uses Apache Camel to define routes between your components, implementing a number of integration patterns as you so need. ServiceMix deploys by default with Apache CXF, for JAX-RS and JAX-WS services and Apache ActiveMQ, a JMS message broker. Using Camel, you can tell service mix that when a REST API is called, do a series of steps, each step decoupled from the one before it.
JBoss Fuse (the enterprisey, costs money edition) comes with some additional components around fail over. Some of these are present in servicemix (namely, you can run servicemix in a hot stand by mode, waiting for the primary to go down). The Camel load balancer pattern doesn't really mean anything around replication, except that a message coming from one endpoint can be delivered to any of a set of a N endpoints. http://camel.apache.org/load-balancer.html
On the flipside, take a look at ServiceMix's failover http://servicemix.apache.org/docs/4.4.x/users-guide/failover.html
I think based on your question you're referring to system failure failover (needing to work against a new instance), and not a Camel Loadbalancer component (which is likely where the confusion is coming from, on the community side and your side).
start by reading these...Camel In Action, ActiveMQ In Action
I am new to camel as well as JCR's.
I am trying to connect to Liferay's content repository using the JCR component in Camel. What I am trying to achieve is pass a content id explicitly and using Camel, I want to hit the content repository of Liferay and retrive the relevant data.
I am trying my hands at the fuse IDE tool as well to get this done.
What I have managed to do so far is configure the endpoint uri to hit my repository. Not sure how to proceed further. Havent found much info on implementations
with Camel JCR.
Any pointers will be of great help!!!
Did you have chance to check out this wiki page?