Infravio Takes Metadata to SOA Governance
EJB 3.0 isn't the only mega-trend in metadata. SOA governance provider Infravio says metadata applied to registry and tooling will empower integration devs to play a more visible role when it comes to aligning IT with business needs. See how metadata outside the J2EE container may have a big impact.
EJB 3.0 isn't the only mega-trend in metadata. SOA governance provider Infravio says metadata applied to registry and tooling will empower integration devs to play a more visible role when it comes to aligning IT with business needs.
Infravio's X-Registry 5 uses metadata techniques to provide a contracts-based view a company's rules, data and workflows which company execs hope will deliver a more value-based view of Services Oriented Architecture (SOA) governance.
ESB-CON Due Diligence Day - March 2, 2006 - Free Online Conference
Join leading ESB vendors BEA Systems, IBM, Sonic Software and Sun Microsystems as they address "The Tough ESB Questions" at ESB-CON -- a live, free online event. Attendees get a full-day of ESB straight-talk about Architectures, Use Cases, Most Popular Features, Designing Pilots, Product Details, and Roadmaps for SOA. Click here for details and no-cost registration.
"We define [SOA] governance as being able to quickly adapt your software to your business, and our use of metadata makes it easier to provide a single semantic view of a company's software assets," Miko Matsumura, Infravio's vice president of marketing told IDN. And, that in turn, Matsumura said, "makes it easier for IT to define or update relationships between companies and their partners and customers,"
Among the common SOA tasks Infravio's approach allows are:
Inside Infravio's X-Registry features
Infravio's X-Registry architecture provides supports for these SOA management/governance operations:
Infravio X-Registry also supports a wide array of web services standards and functionality, including:
Inside Infravio's Metadata SOA "Stack"
Infravio's approach to SOA governance is to map business decision-making with a metadata repository, which is segmented into 3 key layers:
This approach, Matsumura said, makes it easier to apply business-driven goals, targets and performance between customers, partners and suppliers.
Configure (policies and contracts), Compose (components and processes) and Customize (Case-based service implementation).
A lot of the magic behind these layers, he added, comes from Infravio's use of metadata beyond the J2EE app server container. "Once I looked at EJB 3, and that use of metadata, I assumed that enterprise Java developers could understand that we are trying to describe SOA as an any-to-any transaction, and not a simple point-to-point one, like with many APIs."
Metadata needs to be seen as a descriptor paradigm outside the container, Matsumura added. He offers three interesting "arguments" for why metadata should be external - and not only inside a J2EE container:
#1. Metadata can provide a single semantic view of a company's software (including systems,. Records, policies, etc). "If you have a large number of policies and contracts, you may have them stored across a large number of inscrutable locations. So, metadata lets you get a single view of all these [assets] without moving them all to one single location."
#2. Metadata abstractions can make certain contract elements readable and even changeable by non-IT staff, (e.g. business people); and
#3. Metadata [via connections to a security or authentication application] provides a robust mechanism for governance, in other words, a reliable, secure method for changing any of these elements.
"Our view is that SOA is all about managing end-to-end changes in as easily and visible way as possible," Matsumura told IDN. With the core architecture in place, Matsumura said Infravio will work with Java tools vendors and the Eclipse Foundation to create more SOA-focused tools.