OSB-12C : Creation of JMS read/write queue

-
JMS or Java Messaging Service is widely used technology. We can use this JMS technology in OSB elegantly.

 Weblogic server supports JMS and we can create queues to read/write messages from/to external applications.

 In this post I am showing how to create simple JMS read/write queue in weblogic server.

 1. Login into weblogic server console (http://localhost:7008/console) locate JMS modules under services -> Messaging -> JMS Modules



2. Take session in weblogic server by clicking 'Lock and Edit' session. Click on 'New' radio button under JMS module.





















3. Give proper valid name for your module. (In this post, I have used 'WriteFileModule' as my JMS Module name).















4. Let the scope be 'Global'.Click on 'Next' button.

 5. Select the targets for JMS system module. Click on 'Finish'













Note : Next we need to create 'Connection Factory' and 'Queues' under modules. Hence click radio button for 'Would you like to add resources to JMS system module'.


























6. Next we need to create 'ConnectionFactory'. Click on 'New' inside 'WriteFileModule' and select 'ConnectionFactory' from list.















7. Specify proper name and JNDI name for ConnectionFactory. (Here in this post i have specified 'WriteJMSConnectionFactory' same name for both). But as best practice please give proper JNDI name for connection factory.











8. Specify targets for ConnectionFactory and click on 'Finish' button. We can see message on conosle 'ConnectionFactory created successfully.

























9. Next we need to create 'Queue'. Click on 'New' inside 'WriteFileModule' and select 'Queue' from list.













10. Specify proper name and JNDI name for Queue. (Here in this post i have specified 'WriteJMSQueue' same name for both). But as best practice please give proper JNDI name for Queue.














11. Click on 'Next' and select 'Create a New Subdeployment' option.















12. Select JMS server as Target for Subdeployments. (For this post i have created new JMS server named as 'TestXAJMSServer').





















13. Once queue got created successfully, we can see message on console 'The JMS queue was created successfully.'














14. Commit the changes by clicking on 'Activate the changes' button in weblogic console.










15. Similarly create one more JMS module,ConnectionFactory and queue and name it as below.
JMS Module : ReadJMSModule
ConnectionFactory : ReadJMSConnectionFactory

 Queue : ReadJMSQueue





















16. Next for testing purpose we need to create 'JMSPollingProxy' (Proxy Service) and 'Write_JMS' (Business Service). Here as OSB-12c is bundled with Jdeveloper, we are using using Jdev to create and execute proxy and business services.


















Note : Please ignore 'From Template' option as of now. I will explain about 'template' in separate post.

 Let Service Type of proxy service be 'AnyXML'.

 Specify URI for JMS buisness service in below format.

 jms://(host:port)/FactoryJNDIName/QueueJNDIName

 eg : jms://localhost:8013/WriteJMSConnectionFactory/ReadJMSQueue.
















Next create Business Service and name it as 'JMS_Write'.








































Let Service Type be 'Messaging' with Request as 'XML' and Response as 'None'
















17. Specify URI for JMS buisness service in below format.

 jms://(host:port)/FactoryJNDIName/QueueJNDIName
















select Message type as 'Text'.
































18. Next in proxy service, add a route node and invoke 'Write_JMS' business service.











































19. Next we need to do a round of testing . Here i will be sending text message from 'ReadQueue' and message will be written into 'WriteQueue'.

 JMSPollingProxy will be continously polling 'ReadQueue' as and when message enters into queue, proxy will pick message and route it to 'WriteQueue' via business service

 20. To send message, login into weblogic console and migrate to below mentioned path

 Home -> Summary Of JMS Modules -> ReadFileModule -> Summary Of JMS Messages -> ReadJMSQueue -> Monitoring














21. Click on 'Show Messages'. Then Click on 'New'. Give proper valid xml request in body and click on OK button.













































22. we can see message on conosle 'JMS Message sent successfully.'














23. Now migrate to 'WriteJMSQueue' in console

 Home -> Summary Of JMS Modules -> WriteFileModule -> Summary Of JMS Messages -> WriteJMSQueue -> Monitoring














we can see number of messages in 'Message Current' tab. Click on 'show message' button.














24. click on 'MessageID' to see contents of message.




























This shows that message has been successfully read from queue1 and written into queue2.

 Thank you,
Tapan Hegde
Location: Bengaluru, Karnataka, India

Comments

Post a Comment

Popular posts from this blog

OSB-12C : XA Transactional Support feature

-
Image
OSB 12c supports both XA as well as Non-XA transactions. An XA transaction is a "global transaction" that may span multiple resources. It involves a coordinating transaction manager, with one or more databases (or other resources, like JMS) all involved in a single global transaction. XA transactions come from the X/Open group specification on distributed, global transactions. JTA includes the X/Open XA spec, in modified form. XA gets involved when you want to work with multiple resources - 2 or more databases, a database and a JMS connection, all of those plus maybe a JCA resource - all in a single transaction. In this scenario, you'll have an app server like WebSphere or Weblogic or JBoss acting as the Transaction Manager, and your various resources (Oracle, Sybase, IBM MQ JMS, SAP etc) acting as transaction resources.  Your code can then update/delete/publish/whatever across the many resources. When you say "commit", the results are committe...
Read more

Static code analysis of Terraform .tf files using ‘Checkov’ — Secure your infrastructure

-
Image
  Hands on shelf! We can all agree that Terraform is great tool for infrastructure creation and provisioning. When we write terraform .tf files for infra creation we might miss something and we add something which can lead to security issues. Security should be prime factor for any devops related use-case. When I was searching internet for is there any tool which will scan terraform files and give a picture what may go wrong (from security perspective), I came across this very useful tool named ‘Checkov’ Link :  https://www.checkov.io/1.Welcome/Quick%20Start.html Checkov is a   static code analysis tool for scanning infrastructure as code (IaC) files for misconfigurations that may lead to security or compliance problems. Checkov includes more than 750 predefined policies to check for common misconfiguration issues. In this post, I am going to discuss how to do static code analysis of terraform tf files using checkov. step 1 : Install checkov in your machine. $ pip install...
Read more

OSB12c : Schema Validation - Dynamic Validation

-
Image
We can use validate node in OSB to validate schema. There was an option to validate the payload in OSB 11g but it was static, however from 12c there is a new feature included in the OSB validation activity that is validating the data dynamically. This will allow the user to validate the input data or other data dynamically based on certain condition. Thus the process can be stopped at the beginning itself the data validation goes wrong. You have the option to save the validation result or raise an error. Use case: 1. Create a WSDL based service 2. Add validate (dynamic) to validate incoming request structure. 3. If any violation in request structure compared with schema, Error will be raised with proper error code and description. Create new folder and name it as ‘DynamicValidateSchema_UseCase’. Create sub folders structure as shown in below image. For this use case we have created two XSDs and placed it inside Resources -> XSD folder EmployeeDetailsReq...
Read more