SOA Repository Federation

SOA Federation capabilities help customers share software development asset information effectively within and outside the enterprise, govern how this information is shared, and integrate this information throughout the organization’s heterogeneous software development ecosystem.

These federation capabilities benefit IT organizations by:

· Providing a single point for software information across disparate systems in the development environment

· Automating enterprise wide SOA policies and industry SOA best practices

· Driving checkpoint-based development governance (e.g., triggering, coordinating and documenting code reviews, requiring complete end-user documentation for enterprise-shared services), thereby making better use of high-demand architectural and technical resources

· Leveraging existing investments in platform SOA service repositories to be used in an enterprise SOA

Software development today is typically geographically distributed and often requires working closely with offshore teams and partners. A software asset repository is a key part of any distributed software development environment. Such repositories not only need to be able to govern production and consumption of software information, but also govern what information needs to be shared, and with whom; both within and outside the IT organization. By integrating effectively with other systems in the software development ecosystem such as source code control systems, defect management systems, requirements management systems and others, repositories provide a normalized and consolidated view over these systems. Effective repositories should also integrate seamlessly with downstream systems such as runtime registries.

The ability to effectively automate and enforce SOA policies and best practices is critical for a successful enterprise wide SOA program. Enterprises need a single point for consolidating software information from multiple systems in their development ecosystem to make and automate effective governance decisions. Companies also need a single point of control for one or more SOA registry/repositories such as IBM WSRR, HP Systinet, and others. Repository Manager’s strong federation capabilities ensure that SOA standards and policies are enforced consistently throughout the enterprise.

Repository manager provides comprehensive support for multiple federation scenarios:

· Downstream Federation

· Horizontal Federation

· Vertical Federation

· Custom Federation

· Downstream Federation: Repository Manager’s federation capabilities for leading service registries, including Akana’s Policy Manager, IBM WSRR, HP SOA Systinet, TIBCO ActiveMatrix and SAP ESR, automatically synchronize service definitions, supporting information and governance states both to and from the run-time environment. This is unique in the market and provides customers with granular control of their various registries from a single platform, adding consistency and automation to their development governance processes. With Repository Manager’s Asset Import Center, users can scan UDDI V2 and V3-compliant registries, IBM WSRR, HP SOA Systinet, TIBCO ActiveMatrix, and SAP ESR based registries for commonly used services, easily extracting them into a governed service lifecycle process. Once in Repository Manager, these services can be governed based on user requirements for enterprise service deployments; reducing the risk of application failure, security exposure or other application stability issues caused by ungoverned or rogue services.

· Horizontal Federation: Repository Manager supports separation of software development asset information based on organizational needs. For example, in an enterprise with multiple functional business units, each business unit can have a separate library as well as a consolidated library that is shared across the enterprise. In such a scenario, an enterprise may use a certification level classifier to then determine which assets should be available in the enterprise. Repository Manager can also support sharing of asset information across these libraries based on filters. For example, an enterprise with commercial and defense organizational units can be configured to uni-directionally share services from the commercial library to the defense library, thereby providing the defense organization with a broader set of capabilities while preserving security boundaries. Geographically distributed companies can use federation to co-locate library instances closer to multiple physical locations, providing local access not dependent upon Internet/intranet bandwidth at each location while maintaining software asset ownership in a distributed manner.

· Vertical Federation: Through its XML-driven AnySource adapter framework, Repository Manager can be connected to any development system of record. Requirements management tools, document management systems, SCMs, defect tracking tools and test automation environments are a few examples of the types of systems. Repository Manager can aggregate into its Software Development Asset (SDA) repository environment. AnySource is designed to automate the SDA assembly process based on development events (e.g., code promotion), extracting asset information, building references to work products managed by development tools, and establishing relationships to other assets based on development tool-managed information, and presenting the results for optional role-based governance approval. Repository Manager provides prebuilt integrations with the leading SCM platforms including IBM Rational ClearCase (standard and UCM mode, including cross-integration with ClearQuest), Microsoft Team Foundation System version control and Visual SourceSafe, Serena Dimensions and PVCS, open source Subversion and CVS, and any WebDAV-enabled platform.

· Custom Federation: Repository Manager provides extensive web service APIs to allow access to its repository and governance automation capabilities. It also provides a flexible and configurable event infrastructure that can be used to tie in events from other development systems. For example, federation with identity management systems, HR Systems (to obtain users and roles) and custom build systems can be accomplished using this API. External events in these systems can trigger changes to asset information in Repository Manager, presenting end users with a single point of view and control over their software assets.