The organization had been using Oracle RDBMS, Oracle Designer & Forms and even an Oracle EBS module for many years. On the side it had been running several open source J2EE web applications. Facing several new challenges, it took the plunge into SOA - the technology and the architectural principle.
This presentation tells their story.
It started with the business need of opening up the core application to several external business partners. A programmatic interface was required for submitting expense reports - in the thousands - for one business partner, who also wanted to be able to ask for the status for each one those reports.
Another external entity needed the ability to learn about relevant changes in product and pricing data through an API.
We will discuss how SOA principles were used to design the application architecture. And how the Oracle 10g SOA Suite - specifically ESB and BPEL PM - were used to implement the requirements. We go into the choices the organization had to make, the challenges they had to overcome, the skills they had to acquire and the results they achieved.
After this first stage came the next set of business requirements needed tackling. And now the first benefits could be reaped. Following the guidelines established in their first close encounter with SOA, this organization achieved the first reuse of services, could rapidly decide on the application architecture for the ADF 11g Internet Application that needed to be created and further expanded their still little SOA universe. The initial experience now enabled them to decide on whether and how to service enable specific functionality required for the web application - how to use ESB and BPEL, for example and when to use application specific database APIs rather than SOA Web Services.
This stage also taught them the necessity of Governance - what are naming conventions for elements in Schema Definitions and Services, who owns a service, what’s the required availability and how is that achieved, what are the SLAs (Service Level Agreements) around the service, how can the service be evolved with respect to new or changing needs.
The presentation will tell the story of the two stages and how the organization went about them. It will show some small demos to illustrate what was done. It will share some conclusions as to what works and what does not. Finally it briefly discusses the future plans for this organization with regard to SOA.
The presentation is for an audience that probably (though not necessarily) has a classic Oracle background and either is in the process of taking its first steps in the SOA arena or considers moving their. It should help make that process more tangible and hopefully realistic and desirable.
The organization had been using Oracle RDBMS, Oracle Designer & Forms and even an Oracle EBS module for many years. Facing several new challenges, it took the plunge into SOA - the technology and the architectural principle. This presentation tells their story. Of getting started with BPEL and ESB, with Governance and Security (OWSM) and of applying SOA principles. And of the second phase where reuse and agility started to occur.