The iceberg metaphor is apt when considering services within an enterprise: very few service implementations are greenfield, with the vast majority built upon one or more existing (typically strategic) capabilities already present in the enterprise or provisioned by business partners. The service interface, while important, is the small percentage of the total service that sits above the water line; mainframe and distributed applications, data views, EDI feeds, and many more software assets sit below the water line to make up the service implementation. Discovering and understanding these widely varied software development assets (SDAs) is crucial to an organization’s effective SOA development governance efforts.
Graphical Reference Models – Repository Manager’s patented graphical reference models allow organizations not only to visually represent important domain perspectives (e.g., business domain, technical domain) within their repository installation but to automatically map their SDAs to domain elements as part of the production governance process. Once mapped, these SDAs can be discovered by potential consumers via visual navigation, providing an intuitive and easy-to-use way to search for services and other content.
Deep IDE Integration – Visual Studio and Eclipse-based (both native and commercial variants) integrations give developers a natural and seamless interface into Repository Manager. Multi-view perspectives, drag-and-drop and other advanced interaction behaviors, and user-friendly dialogs and wizards simplify the process by which developers find the services they need.
Search Alerts – Sometimes what you need isn’t ready exactly when you need it. Repository Manager gives developers and other SDA consumers a way to “set and forget” searches. When the desired asset becomes available, consumers are notified of the fact via email or RSS feed. Many IT organizations use this approach to automatically disseminate architectural guidance to the broader team, ensuring everyone stays up-to-date with the latest SOA development approaches.
Consumer contract provisioning – As developers discover a suitable service for use in their application or other consuming composition, they need to specify the expected usage characteristics (i.e., the proposed service level agreement) for that service. Repository Manager directly exposes the valid service level policies defined within Policy Manager to developers for selection, and upon consumption governance approval automatically provisions a draft consumption contract to Policy Manager for downstream operational governance application. This end-to-end provisioning model ensures a consistent view across both development and production perspectives, greatly reducing the likelihood of operational errors when deploying SOA-based applications.
For more information about Akana’s market-leading products, click here.