This week i gave a workshop about the new Oracle Service Bus together with Ronald van Luttikhuizen.
The workshop is part of the WAAI project.
The WAAI project is a joint initiative between IT-eye, AMIS, Approach Alliance and Whitehorses.
Colleagues of the different companies working together to get knowledge about the new Fusion Middleware 11g stack and share this knowledge which each other.
The workshop was hosted at AMIS, thanks for help!
The attenders of the workshop had the ability to get used to the OSB. We defined 3 cases which made use of the different components of the service bus.
Since most of the attenders also had experience with the ‘old’ Oracle ESB, we had some time left to get some discussion on both of the service buses.
A short list of their experiences.
- lots of functionality
- console for editting and better support for logging/monitoring
- adapters/transport (ejb,mail)
- more validation
- lots of functionality, steep learning curve
- adapter support (db adapter)
- adapters not jca-compliant (third party)(planned for new release)
- gui not intuative for “old school oracle people”
Those are just a subset of the comments of the attenders. Since they’re based on a little experience they can’t be seen as hard facts.
Depending on the context of the customer you need to decide what product suits best. In some situations oesb and bpel are the
best match and maybe in some other cases you need more influence on the flow in osb and want to model everything in just this product.
what to model in bpel and what to model in osb?
how to synchronise ide project and changes made in the console?
osb versus mediator 11g, what will be the role of both?
We still need to invest some extra time to get the answers on a few of the questions, feel free to give comments!
Antony Reynold already talked a bit about the topic of the role of the different components in the new 11g suite.