HP Systinet 3.00 Brings Automation to SOA Governance
HP is shipping SOA Systinet 3.00, an upgraded to its foundation SOA Governance product to boost SOA returns by offering improved visibility and integration between SOA design time and runtime, boost automation and expanding support for SOA and business process.
HP is shipping HP SOA Systinet 3.00, an upgrade to its foundation SOA Governance product to boost SOA returns by offering improved visibility and integration between SOA design time and runtime, boost automation and expanding support for SOA and BPM.
"We've found our Systinet SOA Governance customers can get faster and better results from their SOA projects and take better advantage of SOA's iterative approach to design, test, deploy and update across the whole SOA lifecycle," Kelly Emo, HP Software's SOA Product Marketing Manager told IDN.
"With Systinet 3.00, we're building on this in several ways we think can bring efficiencies to IT and business with more automation, better visibility into what's going on in repositories and active services and a whole lot of features that just take the head-scratching out of SOA and SOA Governance," Emo added.
Systinet 3.00 also extends better integration between design time and runtime phases, Emo added. "The whole integration between what is being planned and what is actually deployed is so critical to rapid provisioning of new services and their success for customers. Systinet's last release [Systinet 2.5.2] offered customers what we call an 'automated loading dock' that uses automation and templates to speed the launch of new services. We push that capability further with Systinet 3.00," she told IDN.
HP SOA Systinet 3.00's Top Features include:
"This lets customers set up an automated test and workflow operation for launching SOA services, while giving go/no-go voting rights to various IT staff," Emo said.
"Customers are telling us that using UDDI to exchange CMDB and Systinet is becoming a bigger deal because it makes it easier to configure their own service categorization for wider sharing and reuse," Emo said. This is especially true for companies who want to tie in packaged applications into a governable SOA environment, without using the sometimes-arcane naming conventions some ISVs use, she added.