I am using RabbitMq as my message queue and I have to use AMQP protocol in my application. I am publishing messages to my queues in RabbitMq and consume the messages using nodejs client. As an enhancement I want to omit the nodejs consumer client and replace it with WSO2 Data Service Server, since currently the nodejs client calls the services hosted on wso2-dss, after fetching them from queue.
I searched a lot and I didn't find proper way to do this without using wso2-esb. I may be able to solve my problem with qpid client, but I really need help.
Please go through https://docs.wso2.com/display/ESB490/RabbitMQ+AMQP+Transport and http://itsmaheeka.blogspot.com/2015/09/esb-490-enhanced-rabbitmq-support.html to get an idea about RabbitMq transport.ESB provides inbuilt RabbitMq transport But for DSS you may have to install required features.
You can directly use the DSS JMS transport[1] to achieve this, because RabbitMQ support JMS.
[1] https://docs.wso2.com/display/DSS350/JMS+Transport
Related
I've been working with WSO2 Message Broker in order to publish and consume messages through jms and other clients. I've gone through the official documentation including the samples.
What I want to know is that, is it possible for WSO2 MB to handle http requests directly instead of jms. Yes you can do something like this, by converting http to jms through WSO2 ESB which seems like a long process.
ie: I mean having http as the end point or the transport to publish and consume messages directly in WSO2 Message Broker.
In order to achieve this, you will have to use ESB + MB set up as explained at [1]. What you can do is to use ESB to wrap JMS functionality using a HTTP client. It is recommended to use ESB externally in a separate JVM when using this setup.
[1] http://wso2.com/library/articles/2013/03/configuring-wso2-esb-wso2-message-broker/
Regards,
Pubudu.
In SOAP, I see that there is a broker for orchestrating the connections between components. I want to know that is there a similar broker in REST?
There is no broker in SOAP, as long as somebody introduces one between the components (consumer, provider). SOAP is just a protocol. It can be used without a broker/ESB, for instance with direct http connections.
The same applies for REST.
I have a CXF webservice which is supporting SOAP over JMS, where I have used ActiveMQ as message broker system. The soap messages are sent to the request queue and soap responses are sent back to reply queue. Now I am planning to replace RabbitMQ with ActiveMQ. But the issue I am facing is that RabbitMQ doesn't implement JMS APIs. Can we use RabbitMQ for SOAP/JMS webservices?
Note: I am using org.apache.cxf.transport.jms.JMSConfigFeature as jaxws:features in the spring config file.
As you state, RabbitMQ does not support JMS so the simple answer is no, you can't do SOAP over JMS with RabbitMQ.
However, Pivotal has a (commercial) JMS library connector implementation for RabbitMQ that should make it possible.
I've a question for you.
I have to implement a queue governing the accesses to a database on Server.
The Server is in PHP and MySQL. I implemented an Android app to send and store data into DB by WebServices with HTTP Requests.
I thought to use the Mosquitto broker to implement the aforementioned "accessed queue".
First, can I use Mosquitto for this purpose? Furthermore, is it necessary to parse the HTTP Requests in the MQTT Requests and viceversa?
I'm new in MQTT. I know how it works but i don't know how implementing it. Examples in this regard are welcome! :-)
Sorry for my bad English. Thanks a lot!
You should think of MQTT as an alternative for your WebServices implementation.
Typically in MQTT your server will implement an MQTT client library (See a list here) that will subscribe (or publish) to the topics in your Mosquitto broker that your Android App will publish (or subscribe) to.
At the same time your Android App will implement an MQTT client library (Such as Eclipse Paho Android Service) to subscribe (or publish) to the topics in the same Mosquitto broker.
Is there developers who have been succeeded deployed to wso2 esb more than 1500 proxy services
with jms transport without any problems?
Criteria:
deploying process must be very fast
wso2esb use activemq client libraries and activemq brocker
someone please help me!
This should be possible. There is no limitation on the number of proxies that an ESB can have.
You may try this with using the hot deployment capabilities of WSO2 ESB.
You may create a bunch of proxy services and place them inside:
/repository/deployment/server/synapse-config/default/proxy-services
Then the proxies with get automatically deployed..
eg:
proxy_1.xml, proxy_2.xml, proxy_3.xml,..., proxy_1500.xml etc.
However, having this number of proxy services, gives some indication of some anti-pattern in your SOA. Please review whether you need this much of proxy services in your solution architecture.