What is Oracle Fusion?
“Fusion Middleware” essentially represents a re-branding of many of Oracle Corporation’s products outside of Oracle’s core database and applications-software offerings.
Oracle Fusion Middleware includes software products from Oracle Corporation. This Fusion Middleware extends services that include developer tools, integration services, business intelligence, collaboration, and content management. It relies on open standards like BPEL, SOAP, XML etc.,
Oracle Fusion Middleware provides software for the development, deployment, and management of service-oriented architecture (SOA). It includes what Oracle calls “hot-pluggable” architecture, which allows users to make better use of existing applications and systems from other software vendors.
What is BPEL Process Manager?
Oracle BPEL Process Manager is a BPEL engine that is a member of the Oracle Fusion Middleware family of products. It enables enterprises to orchestrate disparate applications and Web services into business processes. The ability to quickly build and deploy these processes in a standards-based manner delivers critical functionality for developing a Service-Oriented Architecture (SOA).
Oracle BPEL engine was acquired from Collaxa, formally called Collaxa BPEL Server, in April 2004. Now it is a part of the Oracle SOA Suite
BPEL stands for Business Process Execution Language which is utilized to specify behavior of various business process based on Web Services. It is a language based on the XML platform, which enables task sharing with the help of web services among various enterprise solutions. BPEL helps to reduce complexity and cost of business processes by integrating discrete services series into an easy process flow.
What is ESB?
The enterprise service bus serves an analogous function at a higher level of abstraction. In an enterprise architecture making use of an ESB, an application will communicate via the bus, which acts as a message broker between applications. Such an approach has the primary advantage that it reduces the number of point-to-point connections required to allow applications to communicate. This, in turn, makes impact analysis for major software changes simpler and more straightforward. By reducing the number of points-of-contact to a particular application, the process of adapting a system to changes in one of its components becomes easier.
ESBs rely on accurately connecting the enterprise message model and the functionality offered by applications. If the message model does not completely encapsulate the applications’ functionality, then other applications that desire that functionality may have to bypass the bus and invoke the mismatched applications directly. Doing so violates all of the principles outlined above, and negates many of the advantages of using an ESB.