Overlord S-RAMP is a full-featured artifact repository comprised of a common data model, powerful query language, multiple rich interfaces, flexible integration, and useful tools. It aims to provide a full implementation of the OASIS S-RAMP specification. Untangle your artifact lifecyle!
This component provides the capability to manage the lifecycle of systems from inception through deployment through subsequent change management. A flexible workflow driven approach is used to enable organizations to customize governance to fit the way they work.
This component provides the infrastructure to capture service activity information and then correlate, analyse and finally present the information in a form that can be used by a business to police Business/Service Level Agreements, and optimize their business.
If you want to centralize the governance of your APIs, this is the project for you! The API Management project provides a rich management layer used to configure the governance policies you want applied to your APIs. Once configured, the API Management runtime Policy Engine can run as part of a standard Gateway or embedded in any application.
The first Beta release of Overlord 1.1 is in progress. We have released the sub-projects (please click through to each sub-project site above for details) but do not yet have the combined installer ready to go. The combined installer will be ready for 1.1.0.Final though! (Released on July 2, 2014)
The first stable Overlord distribution, which includes S-RAMP and Design Time Governance and supports JBoss EAP 6.1 and Tomcat 7! Runtime Governance will be coming soon, we promise. (Released on March 13, 2014)
Any computer system, whether it is centralized or distributed, needs some form of governance, i.e., the act of monitoring and managing the system. Such governance may be as simple as ensuring only authorized users have access to capabilities (e.g. services), or as complex as guaranteeing the system and its components maintain a level of availability or reliability in the presence of failures or increased system load.
Managing distributed systems has always been a critical aspect for users, developers and administrators. As those distributed systems grew in scope and scalability, spanning multiple organizations with different infrastructures and trust boundaries, governance became more difficult but even more important. Governance deals with the processes by which a system operates. In order to have successful governance, some form of management, monitoring and administration is required for these processes.