Monday, November 23, 2009

How to configure an ebXML communication in Oracle Fusion Middleware B2B 11g

Oracle Fusion Middleware (OFM) B2B 11g supports many business document and messaging standards. ebXML (Electronic Business using Extensible Markup Language is a B2B messaging standard that is also supported by OFM B2B 11g. Shortly described ebXML enables XML messaging over the Electronic Business messaging Service (basically a SOAP extension), abbreviated as ebMS.

This posting describes how to set-up ebXML messaging using two local OFM B2B 11g (PS1) domains. For simplicity, I will extend my previous B2B example.

Please refer to my previous postings for more info about specific B2B 11g configuration concepts:



You have to configure both Paris and Berlin. Both configurations are mirrored. Normally, you would use the CPA/CPP import functionality of OFM B2B 11g for this. Unfortunately, I don't have a CPA availabe for this simple demo.

Trading Partners
Configure the hosts and TP in both B2B installations:
  • Paris (receiving role)
  • Berlin (sending role)
(Just use all the defaults, including the TP identification type 'Name')

Configure the document
An ebXML document is defined as a Custom document protocol in OFM B2B 11g. For simplicity, I have used my previous Order document example. I only have to change the document type and definition to resp. configure the ebMS specific properties
  • Action
  • Service
  • ServiceType
  • From role
  • To role

and to configure the inbound document identification. I used the XPATH Identification Expression for identifying inbound documents. Also specify a document routing id in the routing tab (I used Berlin_Order). The routing id can be used to route inbound messages to specific applications.

Delivery Channels
For both Berlin and Paris, I have specified Delivery Channels that uses the ebMS 2.0 protocol (I could use ebMS 1.0..but I prefer newest versions :)). Configuring an ebMS 2.0 delivery channel requires some specific settings. Here are the transport protocol settings that I have used:

  • url: http://host:port/b2b/transportServlet for receiving messages over http
  • Ack mode: async
  • Response mode: none
  • Retry count: 4
  • Retry interval: 2
  • -- Leave all the other setting to their default
Deployment and testing
Deploy the agreements (make sure you configure the capabilities correctly: Berlin is the sender and Paris the receiver in this scenario) on both sides (look here how to configure capabilities and agreements). To test the ebXML configuration, I have used my previous SCA example and modified it for this example. The modifications are in the mediator component, because I have to specify extra B2B adapter properties to allow the B2B engine to identify the agreement. For outbound communication there are two ways to identify an agreement using the B2B adapter in a OFM composite:

1. To and From party + document type and revision. B2B properties:
- b2b.documentTypeName
- b2b.documentProtocolRevision
- b2b.fromTradingPartnerId
- b2b.toTradingPartnerId

2. To and From party + ebMS Action, Service and Service Type:
- b2b.ebms.Service*
- b2b.ebms.ServiceType*
- b2b.ebms.action*
- b2b.fromTradingPartnerId
- b2b.toTradingPartnerId

(*) Those properties are not defined in the JDeveloper Assign activity wizard. You have to manually type in the names in the property selection panel

I used the second option with the following values:
  • action = Order_Action
  • Service = Order_Service
  • Service Type = Order_Service_Type
  • To party = Paris
  • From party = Berlin
Deploy the SCA composite and use the Test functionality of the EM console to run a test case. You can see the exact ebMS message when you click the packed message link in the wire message details screen.


Stephen said...

A few years ago a pair of young advertising executives (Dave and Alex) rated 200 B2B print ads: only 5% were rated as excellent; one-fifth as mediocre and the large majority (79%) as poor. Dave is still around and is currently paired with someone called Eddy (of the Dave and Eddy show) but the evidence shows that B2B advertising has matured substantially in just a few short years.

College Term Papers said...

A great constructive article will help to understand the issue.

upgrade sap 6.0 said...

This post helps you configure an ebXML communication in Oracle fusion middleware B2B 11g. This topic is new for me. I don't have much information related to this title so I have to first look at the basics then I can move forward with syntax. Thanks for the post.

sap erp steps said...

I've come across the term ebXML recently. I'm surprised to see a blog post from 2009 talking about it.

Daman said...

I came across your blog during a google search. I am looking for how to implement Core Components Technical Specification(CCTS) based types in Java and/or any DB.
Do you know about that?

Abu abdillah said...

I really like your post your post contain a lot of information about b2b thanks for sharing such a great information

Sarah Hall said...

I'm grateful for your blog entry and hoping that you will continue to keep up the good work! This custom essay writing service will be of any academic use!