Enterprise Business Messages and Enterprise Business Objects - Empowerment for Enterprises

The Enterprise Business Messages are the packets of data which the Enterprise Business Services accept from requesters and route to providers. They carry the pieces of data needed for the requests to be understood and serviced. Needless to say, these are unique to the industry the enterprise is in business and their structures have evolved over time. As I said before, they are hostage to no application.

An application finds its way into an enterprise because of its unique ability to address specific business requirements. In the process of developing this ability, the application comes up with unique data structures.

The Enterprise Business Messages (along with the Enterprise Business Objects) empower the enterprises to evaluate the applications and transform the disparate data structures (and underlying concepts) of these 'best of the breed' applications into enterprise concepts driving their business processes.

Thus an Order Capture application would have Order entities to capture the order while a Billing application may have ability to enable billing in Customer entities for the services rendered. A service industry specific Sales Order EBM would have the structure to represent the Order captured for a Customer in Order Capture system and turn it into Customer in a Billing system with billing enabled for the services rendered.


Annaji, how important is the EBMHeader component of any EBM? We predominantly use the EBMHeader for Sender/Target/CAVS system identification and sometimes for capturing fault information, but I doubt if that is all it does or if that is all it's meant for.

Posted by Priya on August 05, 2008 at 02:22 PM PDT #

Priya, The enterprise business message (EBM) header is an integral part of every EBM. The EBM Header can be considered as a wrapper or an envelope around transactional data messages. It comprises of functional data such as Document Identification, Involved Parties (Sender, Provider, intermediary services), Security, & Transaction Rules (Transaction State & Exceptions). The EBM header provides the ability to: • Carry information that associates the message with the originator. • Uniquely identify the message for auditing, logging, security, and error handling. • Associate the message with the specific instance of the sender system that resulted in the origination of the document. • Store environment-specific or system-specific information. The requirements pertaining to infrastructure-related services such as auditing, logging, error handling, and security necessitate the introduction of additional attributes to the message header section of the EBM.

Posted by Annaji Garimella on August 07, 2008 at 09:29 AM PDT #

there are so many fields in the EBM. How do we know about which field to map to which EBM element. Is there any document for that? Please provide the silution as soon as possible.

Posted by deepak Garg on September 24, 2008 at 03:18 PM PDT #

Deepak, You are right that the EBM may contain a lot of fields, because it contains more information than just what is needed for a given integration. What would help is to start with identifying what the requirements for the integration are, and then deciding on the set of attributes that are needed by the participating application. This would help nail down the data attributes that need mapping in the Provider and Requester ABCS. The actual mapping is a functional exercise since each participating applications needs would be different. As part of the pre-packaged Process Integration Packs (PIP), we provide the ABCS that implement this mapping, so if you have a need that can be satisfied by connectors available as part of the PIPs, it would be faster and cheaper to just start with the PIP, even if you don't need both ends. Internally, as part of developing these pre-packaged integrations, we do follow a stringent SOA Governance methodology via which the mappings are discussed, reviewed and documented in great detail, although releasing this information as a product offering would require some sort of a semantic repository. -Rajesh

Posted by Rajesh Raheja on October 06, 2008 at 09:21 AM PDT #

Very interesting to clarify EBM Header learning :) Thanks

Posted by guest on May 24, 2011 at 04:46 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

News, views and implementation best practices from the Oracle Application Integration Architecture team.


« April 2014