API Management: Core Concepts/Entities Introduction This discussion is intended to hash out the core ideas/concepts/entities for the Overlord API Management project. The intent is to start with just the core, required entities and expand out from the... 
API Management: Performance is a Feature I think a key focus of the API Management project in Overlord must be reducing the overhead of the Gateway. The benefits of introducing the apiman layer into a SOA architecture are obvious: governance (inc... How to run the demos in s-ramp-0.3.0? Am I correct that you need to comment out the distributionManagement section in the 'demos' parent pom, so that the demo profile can activate its distributionManagement section? Maybe the distribution section in the p... 
Activity collection configurations to be supported for rtgov 1.0 I want to discuss how activity collection, for the purpose of runtime governance, should be controlled within a client side environment. This is where activity events are being collected in an execution environment (e... 
Rich metadata attached to S-RAMP artifacts My use case is the following: S-RAMP stores artifacts RHQ deploys the artifacts RHQ updates metadata on the artifacts in S-RAMP so that they're available for analysis The problem with 3. is that the meta... 
Using S-RAMP as a general purpose content repository I'd like to discuss with you a slightly "twisted" way of using S-RAMP repository as general purpose store for any kind of content, not just SOA-related artifacts. IMHO all the pieces are almost there: The notion of m... "mvn release" to S-RAMP - multiple artifacts When we do a 'mvn release' to S-RAMP, we should recommend to use plugins like the source and javadoc plugin etc to upload these type of supporting documentation in one go. Maybe we can upload them in a holding area (n... Actions associated with synchronous policies Hi Firstly, to set the context, the runtime governance capabilities currently support the concept of 'asynchronously' executed policies - which means that the decision and any subsequent actions are performed ... Versioning artifacts in S-RAMP The S-RAMP specification is somewhat silent when it comes to artifact versioning. There is a core property (attribute) on all artifacts named "version", but it is a simple free-form field that can be set by the ... Resolving references in S-RAMP (e.g. WSDL imports) An issue that still needs to be solved in the S-RAMP repository is how to resolve references between artifacts. For the purpose of this post I will use WSDL as an example, but the problem is generic across multi... Governance Workflows in S-RAMP (OOTB) I've been working on a workflow that is relatively simple but it should still be a real work example; and I've come up with the following where a workflow is kicked of for an artifact - let's say a war application. &... An Example Governance Workflow This discussion is intended to identify the sort of workflow that would be good to ship with Overlord "Design Time Governance" as a good default/example. A simple workflow could consist of the following steps,... S-RAMP UI Design We are currently developing the visual and interaction design for the S-RAMP UI. The first draft of the Interaction Design is available here: https://docs.jboss.org/author/display/SRAMPUI/S-RAMP+Interaction+Desi... 
DTG (Design Time Governance) - Concepts & Definitions 1 Overview The purpose of the Overlord:DTG (Design Time Repository) sub-project is to provide Design Time Governance solutions. This paper is intended to document concepts and data models that can be used as t... DTG (Design Time Governance) - User Scenarios 1 Overview This document is intended to outline the roles, activities, and (ultimately) interactions that will make up the functionality of the Overlord:DTG application. Having well understood user scenarios sho... DTG 4.4 Scenario - Creating a New Composition 4.4.1 Background It is often the case that, rather than creating a new Service, an Architect can “compose” multiple existing Services into a new asset called a Composition. Scenario 1.2 above mention... DTG 4.3 Scenario - Creating a New Service 4.3.1 Background Another common task performed by an Architect is creating new assets in a Solution, when there are no existing assets that accomplish some required piece of functionality. The most common asset ... DTG 4.2 Scenario - Adding an Asset to a Solution 4.2.1 Background One of the most common tasks performed by an Architect is adding existing assets (e.g. reusing existing Services) to a Solution. Scenario 1.2 above mentions this task multiple times, when it des... DTG 4.1 Scenario - Full SOA Project Lifecycle 4.1 Scenario - Full SOA Project Lifecycle The following series of sub-scenarios describe the full lifecycle of a new SOA project managed using Overlord:DTG. 4.1.1 Project Initiation4.1.1.1 Background The organization ... DTG 5.3 Scenario - Managing Deployment Unit Lifecycle 5.3.1 Background It’s possible that a user of the Overlord:DTG application may simply want to govern their application deployments while using alternative tools to manage Business Problem definitions and Solutio...
Log in to follow, share, and participate in this community.