12
Simple HTTTP & JMS for beginners * this tutorial show simple used of HTTP as an inbound endpoint and JMS as inbound and outbound endpoints with the used of ActiveMQ as the messaging technology

Simple http and jms for beginners

Embed Size (px)

Citation preview

Page 1: Simple http and jms for beginners

Simple HTTTP & JMS for beginners

* this tutorial show simple used of HTTP as an inbound endpoint and JMS as inbound and outbound endpoints with the used of ActiveMQ as the messaging technology

Page 2: Simple http and jms for beginners

- create a mule project

Page 3: Simple http and jms for beginners

- add and http inbound component

Page 4: Simple http and jms for beginners

- configure http listener

Page 5: Simple http and jms for beginners

- drag and drop the jms connector from the right pane then configure your jams connection, in my case i chose active mq for my messaging.- be sure you have an active mq installed in your local server

Page 6: Simple http and jms for beginners

- name your queue like this, this will be the queue that your payload you entered or came from http will be placed or stored

Page 7: Simple http and jms for beginners

- this queue will be used later so that you can see how the jms queueing works in mulesb.

- put a logger then try to run your application

Page 8: Simple http and jms for beginners

- you can see this once you have successfully deployed your mule application

Page 9: Simple http and jms for beginners

- try to post via http using postman. From example below add json as my payload- from other screenshot you can see that the outbound jams queue has an enqueued

count 1. That is the message received from http going to jms

Page 10: Simple http and jms for beginners

- the message received by test.jms.queue- i copied it and will send it to test.jms.dequeue

Page 11: Simple http and jms for beginners

- pasted the value here in test.jms.dequeue, then click send

Page 12: Simple http and jms for beginners

- you will notice that the message we inputted in test.jms.queue was printed or logged in simpleFlow1 which is the 2nd flow we created with a JMS inbound on it.

- this means we successfully send and retrieve the jms with different queue endpoints.