Skip to main content

Apply dynamic routing on Oracle service bus

Last year on one of our project we applied oracle enteprise service (SOA suite 10.1.3.1) to integrate with a few legacy system through IBM MQ. This year we have a plan to migrate this integration on OSB (Oracle service bus) previously known Aqua logic service bus from company BEA. Today i simplify one of our integration by using dynamic routing action.

Usecase: We have a few queue predefined on MQ manager to send messages for different purpose. Messages should route by according to their message content.

By using dynamic routing action and routing table we can easily publish messages to proper destination. The input xml file is as follows
<?xml version="1.0" encoding="UTF-8"?>
<TaxDiclaration id="uuid:62fa5eac-3df4-448d-a576-916dd5b432f2">
<destination>
rtu-chanel-2
</destination>
<gtd>
<id>13421</id>
<person>
<type>physical</type>
<name>Jhone</name>
<lastname>dow</lastname>
<tid>co-321478</tid>
<date>01-11-2009</date>
</person>
</gtd>
</TaxDiclaration>

by the content of the destination tag we will route entire message to his physical destination queue. Whole process is as follows:

1) Create three business service according to the destination of MQ.
2) Define the routing table xml as follows:
<routing>
<row>
<logical>rtu-chanel-2</logical>
<physical>rtu_SB/rtu_2_Biz</physical>
</row>
<row>
<logical>rtu-chanel-3</logical>
<physical>rtu_SB/rtu_3_Biz</physical>
</row>
<row>
<logical>rtu-chanel-4</logical>
<physical>rtu_SB/rtu_4_Biz</physical>
</row>
</routing>

where logical name is the name of the service, which will get from the input xml file. Physical tag contain the qualified name of the business services.
3) Create a proxy service with file transport and configure it with proper system folder to receive file.
3.1) Add one pipeline node and two stage node on request pipeline.
3.2) Add one assign action to collect the file from the inbound transport.
3.3) On 2nd stage node, add one assign action and add the routing table xml to the Expression. Give the variable name as routingTable.
3.4) Add one more assign action which will define the destination content from the xml body as follows:
$body/TaxDiclaration/destination/text()
and give the variable name as like logicalDestination.
3.5)Add one more assign action with following xpath:
<ctx:route>
<ctx:service>{$routingTable/row[logical/text()=$logicalDestination]/physical/text()}</ctx:service>
</ctx:route>

name the variable as physicalService.
3.6) Add a route node on the proxy and put a dynamic routing action on it.
3.7.) On expression properties put the following variable named $physicalService.
Now the service bus is ready for dynamic routing. For testing purpose just put some proper xml file with logical destination, service bus will apply dynamic routing according to the content of the entire xml.

Comments

Popular posts from this blog

Send e-mail with attachment through OSB

Oracle Service Bus (OSB) contains a good collection of adapter to integrate with any legacy application, including ftp, email, MQ, tuxedo. However e-mail still recognize as a stable protocol to integrate with any application asynchronously. Send e-mail with attachment is a common task of any business process. Inbound e-mail adapter which, integrated with OSB support attachment but outbound adapter doesn't. This post is all about sending attachment though JavaCallout action. There are two ways to handle attachment in OSB: 1) Use JavaCallout action to pass the binary data for further manipulation. It means write down a small java library which will get the attachment and send the e-mail. 2) Use integrated outbound e-mail adapter to send attachment, here you have to add a custom variable named attachment and assign the binary data to the body of the attachment variable. First option is very common and easy to implement through javax.mail api, however a much more developer manage t

Tip: SQL client for Apache Ignite cache

A new SQL client configuration described in  The Apache Ignite book . If it got you interested, check out the rest of the book for more helpful information. Apache Ignite provides SQL queries execution on the caches, SQL syntax is an ANSI-99 compliant. Therefore, you can execute SQL queries against any caches from any SQL client which supports JDBC thin client. This section is for those, who feels comfortable with SQL rather than execute a bunch of code to retrieve data from the cache. Apache Ignite out of the box shipped with JDBC driver that allows you to connect to Ignite caches and retrieve distributed data from the cache using standard SQL queries. Rest of the section of this chapter will describe how to connect SQL IDE (Integrated Development Environment) to Ignite cache and executes some SQL queries to play with the data. SQL IDE or SQL editor can simplify the development process and allow you to get productive much quicker. Most database vendors have their own front-en

Load balancing and fail over with scheduler

Every programmer at least develop one Scheduler or Job in their life time of programming. Nowadays writing or developing scheduler to get you job done is very simple, but when you are thinking about high availability or load balancing your scheduler or job it getting some tricky. Even more when you have a few instance of your scheduler but only one can be run at a time also need some tricks to done. A long time ago i used some data base table lock to achieved such a functionality as leader election. Around 2010 when Zookeeper comes into play, i always preferred to use Zookeeper to bring high availability and scalability. For using Zookeeper you have to need Zookeeper cluster with minimum 3 nodes and maintain the cluster. Our new customer denied to use such a open source product in their environment and i was definitely need to find something alternative. Definitely Quartz was the next choose. Quartz makes developing scheduler easy and simple. Quartz clustering feature brings the HA and