Oracle Fusion Middleware 11g has finally arrived and it’ll give as well developers as customers the possibility to implement bleeding edge technology throughout the Oracle Stack. Just looking at the different features and functionalities that have been build into the stack is amazing and most of all, you can’t get round fusion anymore. So let’s have a look at what fusion has to offer us (it’ll swipe you of your feet!): So now we have the backbone of our infrastructure laid out, now it’s time to have a look at the different components that will offer these functionalities. In other words SCA Suite, Webcenter Suite, Forms, Reports and Fusion Apps will use the same infrastructure which will enable the usage of consistent admin and management tools whilst leveraging capabilities of the infrastructure and database throughout the entire stack. My 2 cents … Fusion has become a reality with unlimited functionality and features!
Working within a forms, JEE, DB or Apps environment, everyone will be using the same technologies throughout the stack … The fusion ages kicked in!
Archive for the ‘SCA’ Category
OFM 11g Launch – The fusion ages kicked in
July 2, 2009So what is FUSION exactly … well it’s exactly what you want it to be !!!
September 6, 2008When you’re looking into Oracle 11g, what’s coming up, you will notice one thing very clearly … FUSION. SCA, Webcenter, Jdeveloper, OWB, ODI, BPM Suite, Oracle Service Bus, … it’s all becoming 1 user experience.
If we take a look at the Oracle Fusion Approach, you will have the same user experience in each environment you working in.
The IDE’s are converging, the management console’s are converging, … in other words the developer experience, dba experience, management experience, etl experience … every person, every team will work in the same UI, having the same experiences and in other words can team up with all different teams and projects.
It’s amazing when looking at OWB 11g release … it’s ODI put in a Jdeveloper UI, it’s like you’re working inside Jdeveloper not on a web application, soa architecture, database application … no your designing your datawarehouse.
AIA patterns can be used in BPA Suite, BPM Suite will hold all the features of BPMN to deliver a BPEL Blueprint which can be enriched in your Bpel designer. Bpel designer can be used in Jdeveloper or Eclipse, as well as the ESB Designer. Having the Jdeveloper experience and talking about data integration aspects and ETL, well no problem open up OWB 11g and have the same developer experience. The IDE looks the same, works in the same manner as Jdeveloper as well for OWB as for ODI, all suites converge … were do you have that experience now?
Moving towards 11g you will have the converge of BEA and Oracle to have a stronger middleware, an enhanced governance-approach (using AL Enterprise repository) and a whole new feature set coming up in SCA.
So now the million dollar question … when can we use all this great stuff ;o)
AIA – Application Integration Architecture
January 19, 2008This week I went to the SOA Forum in Lisbon which was really interesting because I was able to discuss the different features of ODI, SCA, BPA, AIA, … with other partners and of course Oracle.
The AIA presentation was really great because now I got an in depth view of the amazing features and development that has been done by the Apps people.
AIA now delivers SOA integration to all the Apps people so your available to integrate with Siebel, SAP, … using Process Integration Packs, the so called PIPs. These packs include the needed services, data, error-handling, validation-logic etc. to be able to integrate your E-business Suite application to third-party clients.
What struck me the most was that a lot features should be made available to the SOA community as well, the fusion middleware stack so to say.
What are these amazing features that should be promoted to the fusion middleware stack:
- Enterprise Business Object : The EBO is being used within AIA to describe the true business objects (such as customer, product, …) in a standardized way. Through using these objects any services can retreive the payload and messages in a standardized way and integration is garantied in a loosely-coupled way.
- Enterprise Business Services : The EBS can be seen as the black dot in the middle that handles the payloads of 3-party applications and transforms your 3-party messages into standard EBO’s.
- Application Business Connectivity Service : ABC is the important part inside the PIP’s (Process Integration Packs) which will handle the interfacing with SAP, PeopleSoft, Siebel, … and respond with a standardized payload, namely the EBO to your EBS. => This connector can be seen as the Adapters you’re already familiair with within Enterprise Service Bus and BPEL.
- Composite Application Validation System and Composite Application Error Management and Resolution : enables you to test and simulate your integration services without the need for the whole architecture to be in place. No need for a Siebel-EBS dev, test, q&a and production environment, just test and simulate your processes using the AIA-validation and error packs. The error handling has been augmented so error messages are exchanged in a standardized way and the wright application and the wright user are notified in real-time. This validation logic and error handling could be a true value asset for the Fusion Middleware Market as well, which could just be a service offered by the SCA, by the composite.
- BSR = Business Service Repository, which is an extension on the already existing UDDI but is an answer to the common need for higher-level repositories for models and objects. The UDDI as we know it today only serves as a repository for services which are specific to applications. By taking this to the next level, the customer can now offer a portfolio of solutions instead of a portfolio of services. The BSR will act as a catalog of objects, messages and services that compose the integration scenarios.
AIA has tackled big integration issues already … and the fusion of apps and middleware will be the next level?