Oracle Service Bus workshop, WAAI project feedback

Yesterday we had the ‘feedback’ day/evening from the WAAI project over at IT-eye.
Part of the idea of the WAAI project is to spread the knowledge inside the company so we all know about he nice upcoming things of the Oracle Fusion 11g stack.

One of my colleagues started with the Oracle BPM presentation and workshop. Some nice info and good exercises to get in touch with the new BPM.
After that the playground was mine.
A few hours of hard work and exhausted colleagues trying to complete all the 3 cases from the workshop.

At the end i planned some time for questions and discussions.
Since most of the colleagues already had experience with the Oracle SOA Suite stack, they could do a good compair on the ‘new’ Oracle Service Bus (OSB) and the ‘old’ Oracle Enterprise Service Bus (OESB).
An overall impression would be quiet positive. They liked the new functionality in the bus althought some of the functionality needs a bit more knowlegde and experience. But thats what we will all have when we start to using new products.

A few questions which came up

  • If we’re going to use both both Oracle Service Bus and Oracle BPEl, what should we model in the OSB and what should we model in BPEL.
    Maybe longrunning statefull processes in BPEL and keep the OSB mean and clean?
    Or is there some functionality which really needs to be in the bus?
    Are there any guidelines and best practices on how to model this ?
    The possibilities of the OESB weren’t that rich. So most modelling still had to happen in for example BPEL. The OESB would mostly be used for some routing/transformation and virtualization.
    The OSB gives us a lot of functionality for modelling the message flows, so i could imagine functionality which we normally would model in BPEL can be modelled in the OSB itself.
    But would this be the correct ‘role’ of the new bus ?

  • Most of the transformations in the bus make use of the functionality of xquery.
    What are the pro and cons on both xquery and xslt ? When do we use which one ?

After all a good day and i hope my colleagues enjoyed it too.

Advertisements

ALSB Console project out of sync with file system

Short reminder for myself

During development of my alsb projects i clone, rename, move and do all sorts of things to eventually end of with one correct list of projects with good naming convention.
Once in a while when i try to rename for example proxy services back to some old name i already used i get errors about the new name already exists, although i’m pretty sure it’s not in the console anymore.

Short fix

<BEA_HOME>\user_projects\domains\<YOUR_DOMAIN>\sbgen\

Find the ear file with contains your (old) resource with the identifier you tried to use (i couldn’t find any unix command which would let me list the files in the ear, and after that let me search a string on them).
If you found the correct ear (view application.xml in the META-INF dir, the jav:display-name-elements contains your identifier).

Stop wls
Remove ear-file
Start wls and try to rename again, it should be fixed.

Book review : Processing XML Documents with JDeveloper 11g

Processing XML Documents with JDeveloper 11g

A while back i got asked by Packt to do a review on the book “Processing XML Documents with JDeveloper 11g”.
With me, some other con colleagues, so googling a bit will give you a good impression what others think about it.

The first impression which i have based on the my reading experience from the other Pack books, is that the books are easy too read and you won’t get overwhelmed with massive amounts of information.
But just enough overview about the subject to get you starting and play with the matery.

Personally, i like it when books explain the theory and besides that gives examples (code) to show me the howto things. This book i just like that, although at some points the the amount of code will get quiet big.
Although documentating large pars of code isn’t always that easy, the author tries to explain most of it in a good way.
For my own use i would google to get my hands on the code, and don’t use a book for this.

The books starts right away with samples and diving into the different apis. So a bit of background experience is adviced for the easy reading.

When reading books but also other resources like tutorials or blogs i like it when the example give me step by step instructions on how to get the examples up and running.
I want them to show me what wizzards i need to use, what settings i need to set and it would be great to show the screengrabs with it. The author explained all this real good. Besides that the book is based on the current version of the ide (Jdeveloper), no need to match possible changes in different versions of the ide.

The title is a bit misleading. Since most parts in the book are just about he usage of the different frameworks and techniques, they don’t really (just) apply to JDeveloper. Although it’s really nice have step-by-step overview of how to create the things in this ide. All the aspects a developer needs to know about when dealing with xml are discussed in the book. Aspects like parsing/creating xml (different apis), xml schema, xml schema validation, xpath, xslt, etc, all are getting discussed.
Besides those a few less ordinaire chapters like ‘JSTL XML’,’Converting XML to PDF’, ‘Converting XML to MS Excel’,’Storing XML in Oracle Berkeley DB XML’ and ‘Oracle XML Publisher’ will come by.
Still a subjects (a few) which came by on the average projects we do for customers, so always nice to have some background information on these.

Conclusion

The book fulfilled the expectations i had before i started reading it, based on the other books i read from Packt.
Easy to read, good examples, and a good resource for trying out and get some hands-on experience.

Book details

Contents

  • Preface
  • Chapter 1: Creating and Parsing an XML Document
  • Chapter 2: Creating an XML Schema
  • Chapter 3: XML Schema Validation
  • Chapter 4: XPath
  • Chapter 5: Transforming XML with XSLT
  • Chapter 6: JSTL XML Tag Library
  • Chapter 7: Loading and Saving XML with DOM 3.0 LS
  • Chapter 8: Validating an XML Document with DOM 3 Validation
  • Chapter 9: JAXB 2.0
  • Chapter 10: Comparing XML Documents
  • Chapter 11: Converting XML to PDF
  • Chapter 12: Converting XML to MS Excel
  • Chapter 13: Storing XML in Oracle Berkeley DB XML
  • Chapter 14: Oracle XML Publisher

You can order the book at Packt or Amazon

Thanks Packt for letting me do the review, and i’m looking forward for the next one!

RESTful Services with Oracle Service Bus

Restify existing services

Today i came across a nice article from jeff x davies on “RESTful Services with Oracle Service Bus“.
A nice example on how to map the different http methods to your flows in osb.
The testconsole is easy to use when doing the http calls and adding the query parameters (id=10).

But why mapping non-rest services to and rest interface

  1. You automatically get all of the monitoring, reporting, security and more provided by OSB for your RESTful services
  2. You keep the benefits of mediation. For example, of our company in this example purchased another company that provided different products, you could use the OSB to act as a fa├žade over both product catalogs while providing a single, unchanged REST interface.
  3. You can REST-ify existing, non-service enabled assets like EJBs

Some other good links