The following governance concepts are described below.
...
Runtime governance comes into play, soon after the service is deployed. It monitors operational aspects of a service (service performance bottle necks, who is accessing more, etc.). Unlike design-time governance, most runtime governance functions are automated. Reports generated in this phase are important feedback, for the next service design and development iteration.
For more information on SOA Governance, see Registry Life-cycles and Forrester's Major SOA Requirements.
...
Registries and Repositories
...
WSO2 Governance Registry stores governance metadata and information on governance related entities. Registry resources storing this information and/or metadata are known as assets. Asset is a representation of any physical or digital entity that belong to an organization, which needs to be governed. In WSO2 Governance Registry, a set of predefined attributes compose an asset.
WSO2 Governance Registry provides an XML-based semantic structure called RXT (Registry Extension Types), to define the structure of a given asset type. There are two RXT categories as follows:
...
For more information on these assets, see Adding Assets.
...
Resources and Collections
...