Table of Contents |
---|
| Oracle SOA suite | IBM websphere | Microsoft Biztalk | JBoss Enterprise SOA Suite | SAP Netweaver | TIBCO ActiveMatrix | Other |
---|---|---|---|---|---|---|---|
UBC |
|
|
|
|
|
|
|
Michigan |
|
|
|
|
|
|
|
Cornell | Oracle |
|
|
|
|
|
|
Georgetown |
|
|
|
|
|
|
|
Ohio State |
|
|
|
|
|
|
|
UMUC |
|
|
|
|
|
|
|
UofT |
|
|
|
|
|
|
|
MIT |
|
|
|
|
|
|
|
Washington |
|
|
|
|
|
|
|
UW-Madison |
|
|
|
|
|
|
|
UC-Irvine |
|
|
|
|
|
|
|
Colorado |
|
|
|
|
|
|
|
Indiana |
|
|
|
|
|
|
|
UofT
Using part of the Websphere suite: Message Broker. Implementing a small (100-150msg/sec) enterprise implementation. We'll scale it up as business demands increase.
MIT
We might be using a bit of SAP in places but we're not using any suite for everything or as a strategy
Washington
Only local implementations (not enterprise)
UC-Irvine
JBoss SOA suite: Production
Oracle SOA suite:Development
Colorado
Pilot is implemented, primarily focusing on the Oracle Service Bus component. Goal for the next year is to have an Enterprise class implementation
| Mulesoft | WSO2 ESB | Fuse (built on ServiceMix) | Apache ServiceMix | JBoss ESB | KSB (Kuali Service Bus) | Other Messaging |
---|---|---|---|---|---|---|---|
UBC |
|
|
|
|
| JBoss HornetQ | |
Michigan |
| * |
|
|
|
|
|
Cornell |
|
|
|
|
|
|
|
Georgetown |
|
|
|
|
| (1) |
|
Ohio State |
| * |
|
|
|
|
|
UMUC |
| (ESB) |
|
|
|
|
|
UofT |
|
|
|
|
|
| WMB (formally MQ Integrator and MQ Series) |
MIT |
|
|
|
|
|
|
|
Washington |
|
| Michigan |
|
|
|
|
UW-Madison |
| ESB |
|
|
| Cornell | Cape Clear |
UC-Irvine |
|
|
|
|
|
|
|
Colorado |
|
| KSB |
| Georgetown |
|
|
Indiana |
|
|
|
|
|
...
|
|
* Investigating: lead contender
(1) but KSB is not part of the roadmap*
Ohio State
Exploring Enterprise Service Buses, Service Registries, etc. (WSO2, Mule, Fuse, JBoss)
We have KSB but it is not our target.
UMUC
Implementing for production
UofT
Implementing a small (100-150msg/sec) enterprise implementation. We'll scale it up as business demands increase.
Washington
KSB usage is local
Exploring Oracle Service Bus
UM-W
Cape Clear is in retirement
Oracle, Fuse and WSO2 will soon be set up as part of our integration testbed
UC-Irvine
...
| JAX-WS, JAX-B | WS-Transaction | BPEL | SAML | WS-Security | WS-Trust | WS-Policy | Other |
---|---|---|---|---|---|---|---|---|
UBC | JAX-WS, JAX-B |
|
| SAML |
|
|
|
|
Michigan |
|
|
|
| WS-Security |
|
|
|
Cornell | JAX-WS, JAX-B |
|
|
|
|
|
|
|
Georgetown |
|
|
| SAML |
|
|
|
|
Ohio State | JAX-WS, JAX-B | WS-Transaction |
| SAML | WS-Security |
|
|
|
UMUC |
|
|
| SAML | WS-Security |
|
|
|
UofT | JAX-WS, JAX-B |
|
| SAML | WS-Security |
|
|
|
MIT | JAX-WS,JAX-B |
|
| SAML |
|
|
|
|
Washington | JAX-WS, JAX-B |
|
| SAML |
|
|
|
|
UW-Madison | JAX-WS, JAX-B |
| BPEL | SAML | WS-Security |
|
|
|
UC-Irvine | JAX-WS, JAX-B |
| BPEL | SAML | WS-Security |
| WS_Policy |
|
Colorado | JAX-WS, JAX-B |
|
|
|
|
|
|
|
Indiana | JAX-WS, JAX-B, JAX-RS |
|
| SAML | WS-SECURITY |
|
| oath |
| Bus | Hub-and-spoke | Point-to-point | Federated | Other |
---|---|---|---|---|---|
UBC | Y |
| Y |
|
|
Michigan |
| Y |
|
| |
Cornell |
|
| Y |
|
|
Georgetown |
| Y |
|
| |
UMUC | Y | Y | Y | Y |
|
UofT |
| Y |
|
|
|
MIT |
|
| Y |
|
|
Washington | Y |
|
|
|
|
UW-Madison | Y |
|
|
|
|
UC-Irvine |
|
|
|
| A mixture of topologies |
Colorado |
|
|
|
| A mixture of topologies |
Indiana |
|
|
|
| A mixture of topologies |
UMUC Yes - the ability to integrate via SOA/web services is a key determinant we evaluate new products on.
UofT
Yes. SOA is being talked about as a "game-changer". The business people quickly recognize the benefits of SOA, while the IT people seem to warm to it much more slowly, possibly because they see more implementation challenges than do the business folk.
MIT
Yes, but project priorities have delayed any progress in this direction
Washington
We don't have a clearly articulated technology roadmap
Pub-sub may have a greater impact than web services
UW-Madison
Not much yet. I imagine we'll see a lot or planning in the coming eighteen months.
UC-Irvine
SOA has changed the roadmap, primarily because people started thinking about real time.