SOA Governance Tools
- Mark Skilton
- Jul 13, 2006
- 2 min read
Specific SOA Library tools are around the Design time and run time models and code.
The functionality of the library is to hold the content of these through.
The key point here is that we do not recommend buying an "SOA Library tool" as this does not exist.
Companies can manage SOA Library initially between a number of existing tools with procedures.
When they reach a critical mass of logical models and web services/BPEL they can think about using a Service registry tool such as Systinet or others to manage the library versions and environment. The initial set of web services will be held in a WebSphere for example. A third key consideration of the SOA Library tools is the link between Design-time models and Run-time models. There is a third class of tools that seek to automate the design and is very much part of the MDA landscape and has been a key area is other clients e.g. BT
Essentially the SOA Library management falls into four categories of suppliers currently:
- Design time tools
- Run time tools
- Design time to run time automation tools
- SOA Library Release management
The following are examples to some Vendors:
Design time tools
- Rational Architect/ XDE for the EAB(POV)models and Logical Meta Models (The common Data model)
- Sharepoint - for document management
- Troux - EAB management tool
- Aris - Business Process modelling
- Casewise - EAB and Business Process modelling
Run-time tools
- Rational Developer IDE for the Developers
- J2EE developer environment
- BEA Workshop and NitroX (BEA eclipse tool from M7)
- XMLSpy
- RAS/RSM + ClearCase
- IBM Websphere developer environment
SOA Registry tools
- Systinet Corp - service registry tool
- Infravio Inc
- Flashline Inc
- SOA Software Inc
- Software AG
Design automation tools
- Enterprise Architect (EA, not Telelogix) from Sparxsystems - a UML 2.0 to XSD generator
- Ormondo - a eclipse based tool from omondo.com for UML and Velocity for generation.
(http://jakarta.apache.org/velocity/) Uses XML/JMS and EJB Interfaces generated from UML model.
- Altova Semantics Works
- Protege
- System Architect (SA) 0 based on BPMN, BPEL
Lifecycle management
- Telelogic DOORS
- IBM (RequisitePro)
- Serena (RTM)
- Select (Enterprise)
Some articles on the subject:
http://www.line56.com/articles/?articleID=6656&TopicID=4
http://searchwebservices.techtarget.com/originalContent/0,289142,sid26_gci1172036,00.html
Initially I see us focusing on the following tools to manage the SOA Library in JLR
- Rational
- Their current Document Intranet library (where they currently hold
- Their preferred Business process modlelng tool. I suggested Aris or
- Their preferred Programme and Project Planning tool - MSProject currently
- Their J2EE environment.
Part of the Technology selection work with Paul Vickers is to define the technical environments necessary based
on the SOA best practice framework model I have. I would recommend at this stage to look at the Vendors for background info.
Comments