AIA Enterprise Business Services - Conceptually, what do they represent?

The AIA Enterprise Business Services (EBS) represent the core business functions of an enterprise as they interact with the wider ecosystem of enterprises as part of day to day business interactions. They are not web services exposed by any business software application implemented in an enterprise.

Let me elaborate further. In any enterprise, we always find multitude of software applications implemented. This is mostly by design. Running a business is complicated and it is challenging to keep up with the competitors. In their quest to excel, enterprises seek best of the breed software applications evaluating their core functionalities. Thus an enterprise ends up with different software applications catering to Customer Management, Product Management, Asset Management, Order Management, Financial Management and so on. The stove pipes of applications are more narrower in scope, in reality.

The web services or APIs exposed by these software applications are granular in nature and represent their core functionalities. These applications need to be integrated in order for the enterprise to carry out the core business functions. For each of these business functions or tasks to be accomplished, multiple applications with their granular services need to participate.

The AIA Enterprise Business Services, representing these business functions or tasks, mediate the invocation of the granular web services between various participating applications.

Needless to say, the payloads of the AIA Enterprise Business Services are Enterprise Business Messages (EBM) and these represent the canonical data models of the industry in which the enterprise is doing business. They are not hostage to the participating application data models.

More on Enterprise Business Messages and Enterprise Business Objects (EBO) in next post.


It is interesting to see how many companies run various aspects of their business through multiple software platforms. I think this goes hand in hand with the evolution of technology. IT solutions were put in place, and as technology and business evolved other solutions had to be added. At some point there were platforms that addressed multiple solutions, but by now these companies had already implemented numerous applications to maintain their business. It is hard to ask a company to rethink their entire IT strategy, but this is usually very beneficial. The time and money saved by combining software solutions into one package can easily outweigh the time it takes to learn the new applications. In the long run this can improve the business model by leaps and bounds in centralizing all their IT solutions into one area. Interesting article.

Posted by Business Tracking Software on July 24, 2008 at 04:17 AM PDT #

It is agreeable the Oracle have done a study and made analysis to come up with the Enterprise Business Services that have been provided with the Foundation Pack. Of course, there will be requirements for individual firms that are not covered by the provided EBS. In that case, we might need to customize the existing the EBS, ie, extend the EBS as we do in the case of EBMs and EBOs. In the case of EBOs and EBMs, we have been provided with options of extending them. I do not seem to find them in the case of EBS. Are EBS's not extendable ? If so, why and how can we accommodate scenarios that are not taken care of by the EBS provided OOTB ?

Posted by Arun Ramesh on July 28, 2008 at 04:46 PM PDT #

Yes! Enterprise Business Services are extensible. The Enterprise Business Services are created using the WSDLs provided in the Foundation Pack. In the WSDLs, the following can be modified: 1. The payloads for each of the operation - Extensible by virtue of EBM extension 2. Adding new operations - Extensible by virtue of creating a new WSDL with new operations and creating the customer / implementation specific Enterprise Business Services from this WSDL. The case of modifying existing operations (adding different payloads or pattern or name) effectively makes them new operations. Since the Enterprise Business Services are top level executable artifacts, the extensibility requirements are much different from the lower level artifacts.

Posted by Annaji Garimella on July 29, 2008 at 04:06 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

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


« June 2016