Red Hat Training

A Red Hat training course is available for Red Hat Fuse

1.6. Red Hat JBoss Governance Package

This section lists the two major components within Red Hat JBoss Governance:
S-RAMP
SOA Repository Artifact Model and Protocol (based on the OASIS standard)
  • Artifact repository
    • Built on top of ModeShape
    • Stores artifact content and meta-data including:
      • Core properties (name, description, version, etc)
      • Custom ad-hoc properties (name-value)
      • Relationships between artifacts
      • Hierarchical tagging system called Classifiers
    • Rich XPath-like query language to search the repository
    • Atom based REST API
    • Automatic decomposition of artifacts based on type
      • Built in support for common S-RAMP types (XSD, WSDL, etc)
      • Extensible to support additional types (Teiid VDB, switchyard.xml, etc)
  • Command Line Interface
    • Supports interactive and batch modes
    • Built-in commands to manage and search for artifacts in the repository
    • Extensible to allow contributing custom commands
  • Maven integration
    • Can "mvn deploy" a deployment artifact directly into S-RAMP
    • Able to use S-RAMP artifacts as dependencies in maven projects
  • Web UI
    • Based on Errai 2.4
    • Allows granular management of content in the repository
    • Can be used to manipulate all artifact meta-data
RTGov
Runtime Governance
  • Activity Collector
    • Activity events can be reported directly to the Activity Server via REST service, OR
    • Embedded collector to intercept activities, pre-process the information to extract correlation details and business relevant properties, before batching events for distribution to the server.
      • Events can be 'validated' using pluggable event processors, which can be used to block business transactions
  • Activity Server
    • Provides a REST interface to enable events to be reported
    • Persists activity information
    • Distributes reported events to subscribed components
  • Event Processor Network
    • Subscribes to the Activity Server, to receive reported activity events
    • Distributes activity events through a series of registered networks, that consist of event processors to validate, transform and retransmit events. Processors can be specified using Java, Drools CEP rules and MVEL
  • Maintaining Derived Results
    • Information derived by the Event Processor Network can be presented as a set of 'active' collections
    • Components can directly access these collections, or issue queries through a REST API
  • Web UI
    • Runtime governance information is provided through a set of gadgets
      • Service Response Time Gadget - displays response time information per service and optionally operation
      • Situations Gadget - table for displaying situations detected by the event processing (for example, SLA violation)
      • Call Trace Gadget - provides a tree based visual display of the call stack associated with a business transaction
      • Service Overview - graphical representation of the services and their dependencies, showing response time and invocation details