The WebSphere SOA Runtime Stack
November 8, 2006 1 Comment
In a service oriented architecture approach there are a number of different types of services involved:
Simple services – the web services, or messaging applications exposed as services.
Mediation services – allow you to perform simple message mediation between services.
Business services – allow you to choreograph services.
Each of these services require a runtime with specific capabilities to be able to run.
The WebSphere platform supports these 3 types of service through 3 different runtimes: WebSphere Process Server, WebSphere ESB and WebSphere Application Server. The differences between these are described in the table below:
|Runtime||Can host simple services||Can host mediation services||Can host business services|
|WebSphere Process Server||Yes||Yes||Yes|
|WebSphere Enterprise Service Bus||Yes||Yes||No|
|WebSphere Application Server||Yes||No||No|
It won’t suprise you to learn that WebSphere Process Server is built on top of WebSphere ESB, and WebSphere ESB is built on top of WebSphere Application Server (I like to think of it like a Russian Doll – open up WebSphere Process Server and you will find WebSphere ESB, open up WebSphere ESB and you will find WebSphere Application Server). Consequently moving from one runtime to another is relatively simple as many of the concepts are the same, e.g. administration, clustering, configuration, install etc, etc. Plus, any of the things you could do at the lower level you can do at the higher level too if you choose to do so (i.e. you can host a simple service on WebSphere Process Server if you choose to do so).
These set of products effectively form the WebSphere SOA Runtime stack.