Hoping to become the newest got-to-have-it item in the IT world, Systinet Corp. today released its latest beefed-up registry for service-oriented architecture (SOA).
Version 6.0 of the Burlington, Mass., company's registry features a configurable user profiles console, subscription/notification added to the business services console and full implementation of Systinet's Governance Interoperability Framework, which allows for easier exchange of meta data. More importantly, it marks continued progress for the company that built itself around the much misunderstood and defamed UDDI registry.
While three years ago, many snickered that UDDI was an unnecessary component in a Web services infrastructure, many analysts now are saying it's essential.
"In my opinion, policy, enforcement of policy and governance of policy are the big holes in adoption of SOA," said Anne Thomas Manes, a vice president and research director at The Burton Group. "A registry performs that absolutely critical task of making those policies available to developers and making sure they're conforming to those policies."
In fact, Manes deems a registry "one of the first things you want to put up in an SOA infrastructure."
Along with the business service registry is a new integrated product called the Systinet Policy Manager. It performs the exact functions Manes believes need to be addressed to build an enterprise-wide SOA.
Systinet envisions the more robust registry as the "SOA system of record," said David Butler, vice president of marketing for Systinet, providing integration at the data control and user interface level between Web services management, security, integration, enterprise information integration, composite application and business intelligence solutions.
"It's the magnet for all the information inside of a service-oriented architecture," Butler said. "The registry should be able to serve and coordinate developers, business analysts and architects."
According to Manes, one of the barriers to UDDI adoption had been the difficulty for business users to search through an UDDI registry due to a complex data model. However, the configurable consoles mark Systinet's attempt at resolving that issue.
"Usability for the non-technical person has been a major focus for us with this release," Butler said.
When UDDI registries first came into the spotlight in the earlier part of the decade, they were pitched by some as massive public registries of available business services, much like a massive, online Yellow Pages.
"It was promoted as this all-powerful registry in the sky and the concept left people running away in terror," Manes said. She added that many mistakenly believed a registry was designed for the "dynamic location of services at runtime" rather than for discovery during development time and for Web services management.
"You don't want to put services out there and have gazillions of people using them without control," she said. "An application shouldn't be put into production until you've got registry and management in there. Don't let chaos set in."
The new policy manager uses XQuery, XPath and Schemation for policy creation and open application program interfaces to integrate with third-party products for runtime governance and enforcement.
"Registries are absolutely required in a service-oriented architecture," said Ron Schmelzer, senior analyst at ZapThink LLC, of Waltham, Mass. "Companies that don't have it really haven't implemented a service-oriented architecture."
In related news, BEA Systems Inc. last week made the Systinet registry a core component of its AquaLogic Web services development platform.
Systinet now has half of what it's branding as its Blizzard platform available. Coming later in the year will be an information manager that tracks SOA assets and performs lifecycle management, along with a contract and impact management tool that provides service level agreements, relationship management and dependency analysis.