Java Message Service, or JMS is an API for Java middleware oriented messages through the JMS API where two or more applications can communicate by messages.
Let this first Post learn to Create and Configure locally a JMS queue in the Oracle Service Bus Web Console, then learn how to Create a Message to send through this JMS Queue and soon after we will Receive this message and store it in our database using a BPEL process
See the links below to check the other parts:
- Working with JMS messages on OSB – Part 1: Creating and Configuring Queues
- Working with JMS messages on OSB – Part 2: Publishing a Message Queue
- Working with JMS Messages on OSB – Part 3: Receiving Message
Let’s start 🙂
In your browser go to the address http://localhost:9000/console
Note: The 9000 port is the number I chose to create my Domain OSB
Login:
In the screenshot below click JMS Servers to create our JMS server
Click below New
Fill as follows:
Name: BlogJMSServer
Persistent Store: FileStore (will be set up local files for your JMS queues)
Click Next
Below Target in select AdminServer and click Finish
See below our JMS Server created.
Now let’s create our JMS Module for that click JMS Modules as follows:
Below click New to create a module which is actually just a place where we “organize” our ranks and settings
Fill as follows:
Name: BlogModule
Descriptr File Name: BlogModule
On Location In Domain can leave blank and click Next
In Server AdminServer select the option and click Next
Below check the Would you like to add resources to this JMS system module and click Finish
See below our BlogModule was created and we can now create the rest of our settings:
Now let’s create our connection factory, for it yet in the screen above click New, select the connection factory and click Next option as below
Fill as follows:
Name: ConnectionFactoryBlog
JNDI Name: ConnectionFactoryBlog
Leave everything else like this (default) and click Next
Click on the screen below Advanced Targeting
Now click Create a New Subdeployment
Down in Subdeplyment Name put the nameConnectionFactoryBlogSubdeployment and click OK
Below sure that in Subdeployments Factory is the name we created and Servers check the AdminServer option and click Finish
Below we create our connection factory successfully created and is pointing (Targets) correctly to our AdminServer
We will now create our Queue
Even in the above screen click New, select the Queue option and click Next as follows:
Fill as follows:
Name: BlogQueue
JNDI Name: BlogQueue
Click Next
In Subdeployments click on Create a New Subdeployment
In Subdeployment Name: put the name BlogQueueSubdeployment and click OK
Note that in Subdeployments already named we create JMS Servers and select the JMS server we created (BlogJMSServer) and click Finish
See below our Queue (BlogQueue) was created successfully and is pointing (Targets) correctly to our JMS server (BlogJMSServer)
There, we have already created and configured our JMS Queue successfully.
Hugs and until the Next
/:-D
CESAR GUERRA said:
Hola,
Buen post, pero te faltó hacer hincapié en la configuraciones que se debe de hacer en la Factory para transaccionalidad, en la Queue para lo que es tiempo entre reintentos y máximo de estos reintentos, así como la configuración de la Error Queue que es tan importante.
Saludos.
Uans said:
Hola Cesar, Más tarde se creó un puesto específico para esto, pero de todos modos gracias por la crítica que siempre es bienvenida.