For enterprises to fully understand and effectively govern their SOA environment, they must have a complete and coherent view of the services and other SDAs touched by their SOA initiative as well as the policies and processes that guide consistent development of SOA elements. This end-to-end view must incorporate and coordinate relevant content not only from service development and deployment activities but also from service planning efforts (e.g., proposed services and their traceability to existing system capabilities) and from existing service capabilities (perhaps sourced from packaged applications and third parties).
Organizations also need to deal with the added complexities introduced through extensive offshoring/outsourcing relationships. While these relationships clearly provide value to the enterprise in terms of both cost and flexibility, if not managed properly they can lead to provider lock-in at best and development disasters at worst. Maintaining visibility and scope of control over arms-length development activities is key to deriving the most value from those relationships.
End-to-end integrated service metamodel and governance process model – Repository Manager, Policy Manager and Service Manager provide a complete solution for development and operational governance automation. By defining a common service metamodel and governance process model across these products, Akana gives IT organizations a significant jump start towards cross-organizational fidelity and consistency, reducing the likelihood of manual error and eliminating redundant information management within the enterprise.
AnySource™ federation – Connectivity to SCM platforms and other development tools is crucial for IT organizations to accurately represent and govern their development efforts. These development systems of record are typically managed in a siloed manner with little to no communication and coordination across products. Repository Manager’s AnySource federation toolkit allows IT organizations to define and automate extraction rules that span these products, producing complete and coherent SDAs based on SDLC triggering events (e.g., source code promotion, establishment of a version baseline). Based on the well-known open source ANT framework, AnySource presents a well-understood task model for asset automation.
Service registry federations – As services enter into staging and production environments, service definitions and supporting metadata must be provisioned into the runtime registries supporting those environments. Repository Manager supports automated provisioning of such information to leading service registries such as IBM WSRR, HP SOA Systinet, TIBCO Active Matrix Registry, and any UDDI-compliant registry. These same registries can serve as sources to bring previously ungoverned services (e.g., services deployed as part of a packaged application) under development governance via Repository Manager’s Import Center.
Federated Repository Manager installations – Highly distributed development organizations may need localized repository installations to better manage content access and latency issues. Other organizations may need to establish filtered access to selective SDA information to their outsourcing partners while at the same time maintaining consistent governance processes over the SDAs developed by those partners. Repository Manager’s sophisticated federation model enables IT organizations to establish essentially any federation topology (e.g., tree, star, unidirectional point-to-point) across any combination of physically and logically separated library installations. Filtering rules can be established over each connection within the federation, thereby ensuring that only appropriate information is passed across the connection.