Skip to main content

Oracle SOA JMS Adapter TOPIC configuration with SOA based Subscriber's

Hello Everyone,

Hope you enjoy blogging!!!!!

Today i am going to explain how we can use TOPIC in oracle SOA where we will publish message into Queue from one service and other services will consume message from topic.

Steps to create JMS TOPIC:


1. Click on Services Menu
2. Click on Messaging Sub-menu
3. Click on JMS Modules.
4. Click on SoaJmsModule.
5. Click new
6. Select Distributed Topic anc click next
            1. Enter Name "ProjTopic"
            2. Enter JNDI Name "jms/ProjTopic".
            3. Click on Advanced Target
            4. Select SubDeployments "SoaSubDeployments" from dorp down.
            5. Select Server "SoaJmsServer1" "SoaJmsServer2" from server list
            6. Click Finish
            7. Click on "ProjTopic"
8. Go to Configuration >> General
            9. Set Forwarding Policy to "Partitioned" (this property will make sure not replicate message into all soa cluster nodes).
10. Click Save
















Steps to create JMS TOPIC Connection Factory:

1. Click on Services Menu

2. Click on Messaging Sub-menu
3. Click on JMS Modules.
4. Click on SoaJmsModule.
5.Click New

6.Select Connection Factory and click next
            1. Enter Name "ProjTopicCF"
            2. Enter JNDI Name "jms/ProjTopicCF".
            3. Click on next by keep default values.
            4. Click on Advanced Target
            5. Select SubDeployments "SoaSubDeployments" from drop down.
            6. Click Finish
            7. Click on "ProjTopicCF".
            8. Go to Configuration >> Client
            9. Select Client ID Policy as Un-restricted.
            10. Subscription Sharing Policy as shareable.





Steps to update JMS adapter:

1. Click on Deployments.

2. Click on "JmsAdapter".
3. Click on configuration tab
4. Click on outbound connection pool tab.
5. Click New
6. Click on "oracle.tip.adapter.jms.IJmsConnectionFactory" and click next
7. Enter JNDI Name "eis/jms/ProjTopic"
8. Click on created JNDI Name and enter ConnectionFactoryLocation location as "jms/ProjTopicCF" and hit ENTER.
9. Enter "true" in "IsTopic" row & press enter button
10. Set FactoryProperties column value as ClientID=ProjTopic
11. Click Save
12. Go back to "Deployments".
13. Select check box in front of "JmsAdapter".
14. Click on update button.
15. Click next & finish.



SOA Development:
  • Create three SOA Services,
    • PublishTopicMessage
    • ReadTopicMessage1
    • ReadTopicMessage2
  • Inside ReadTopicMessage1 and ReadTopicMessage2, Open TopicConsume.JCA file and add below property in JCA file.
  • <property name="DurableSubscriber" value="SubsriberName"/>
  • Deploy both service and publish some message into JMS Topc.
Weblogic Console Topic Message checking steps:
  • Login into weblogic console.
  • Go to newly created JMS topic.
  • You will see your published messages here with list of subscribers.



Comments

Post a Comment

Popular posts from this blog

Oracle SOA 12C rest adapter with Custom HTTP headers

Most existing web applications are connected through web services, which are commonly known as SOAP services. More and more users are relying on mobile devices for communication, and they’re looking for lighter ways to access enterprise information on the go. REST services are the answer for the mobile device platform, because they get rapid responses and fast access to data. Oracle SOA Suite 12 c  provides a complete set of service infrastructure components for designing, deploying, and managing composite applications. Oracle SOA Suite 12 c  enables services to be created, managed, and orchestrated into composite applications and business processes. Some time we have need to send HTTP headers in REST service, In OSB we use header component and add what ever is needed but in oracle SOA 12C it's little bit different. Let see how we can do it. Create one SOA Application. Create one SOA Sample project inside SOA Application. Go to composite and drag drop REST ...

Swagger API document from Any WADL & Schema in Oracle SOA

Hi everyone, Hope everyone is doing well these days, Recently i started a project work over how to generate swagger API document for your any REST API, In case if you don't know what is swagger please go and check " https://swagger.io/tools/swagger-editor/ ". It's a great and easy to use tool which will help to create user friendly, human readable form API documentation with extension for generating API client in different languages with capability of testing your API from same. What is swagger editor, Design, describe, and document your API on the first open source editor fully dedicated to OpenAPI-based APIs. The Swagger Editor is great for quickly getting started with the OpenAPI (formerly known as the Swagger Specification) specification, with support for Swagger 2.0 and OpenAPI 3.0.  What benefits you will get by using swagger, Runs Anywhere, The Editor works in any development environment, be it locally or in the web. Smart Feedback, Validate you...

ParseEscapedXML Function In Oracle BPEL XSLT Is Throwing Parsing Error For Special Character &

The ampersand escape sequence "&" in a Database Record/XML Payload is being converted to '&amp;' by the BPEL composite.  This results in the XSLT transformation code throwing an oracle.xml.parser.v2.XMLParseException error/exception when the parseEscapedXML method is invoked against the data. The parseEscapedXML method was deprecated in in 12C and should not longer be used. It has been replaced by the new method oraext:parseXML. There is a know bug in the oraext:parseXML method that was address in patch 21377740. The fixes that were made in 21377740 where incorporated into the  12.2.1.0.0 GA release, thus there no patch needed  for the issue.   Note: No backport fix for 12.1.3 was released