Oracle SOA Suite 11g B2B HL7 v2 Inbound to WebLogic JMS Queue

I notice that people used to the eGate/Java CAPS way of doing things, when looking at migrating to the SOA Suite for HL7 messaging, are trying to reproduce the pattern “HL7v2Adapter?JMS Queue”. This is not necessary when using SOA Suite but can be done if one insists. This article walks through the process of implementing this pattern using Oracle SOA Suite 11g R1 PS3.

The process will follow these steps:
1. Obtain and configure the QBrowser tool for JMS browsing
2. Obtain and configure the HL7 Sender tool
3. Create two WebLogic JMS Queues to be used in the solution
4. Create and deploy a HL7 v2 Inbound Trading Partnership Agreement
5. Submit HL7 v2 messages and inspect them in the corresponding JMS Queue
6. Repeat steps 4 and 5 for another inbound stream

The cmplete article, which can be found at http://blogs.czapski.id.au/wp-content/uploads/2011/05/SOASuite_HL7v2_Inbound_to_JMS.pdf, will demonstrate that Oracle SOA Suite B2B HL7 infrastructure can be configured to receive message streams over multiple inbound MLLP channels and deliver each stream to a distinct JMS destination, much as eGate and Java CAPS solutions used to do.

This entry was posted in Oracle and tagged , , , , , , . Bookmark the permalink.

4 Responses to Oracle SOA Suite 11g B2B HL7 v2 Inbound to WebLogic JMS Queue

  1. Akihiro says:

    Hi Michael,
    Good entry! But I find the following clause, “Oracle SOA Suite 11g R3” in this article. Is this typo? I wonder if this is “Oracle SOA Suite 11gR1 PS3″…

  2. Pingback: Oracle SOA Suite 11g B2B HL7 v2 Inbound to WebLogic JMS Queue - WebLogic Tutorial

  3. Alka says:

    Hi Mchael,

    Packt Publishing is looking for Technical reviewers on “Oracle SOA Infrastructure Implementation Certification Handbook”. If you are interested in reviewing it do contact alkan@packtpub.com

Leave a Reply

Your email address will not be published. Required fields are marked *