Red Hat Training

A Red Hat training course is available for Red Hat Fuse

Chapter 11. Runtime Governance Configuration

11.1. Enabling Runtime Governance

You can enable or disable Runtime Governance through the collectionEnabled property in the $JBOSS_HOME/standalone/configuration/overlord-rtgov.properties file. By default, the value of the collectionEnabled is set to false.
This property will determine whether activity information is collected when the server is initially started.
Report a bug

11.2. Configuring Run-Time Governance

Introduction

SwitchYard uses Run-Time Governance to facilitate complete control over the shared services by following a policy based approach. SwitchYard classifies Run-Time Governance into two aspects:

  • Policy definition and enforcement
  • Collection and exposure of run-time metrics for services and service references
Run-Time Governance configurations allow you to add or modify classes to manage Run-Time Governance and also define usernames and passwords.
Report a bug

11.3. Overlord Run-Time Governance Configuration

Procedure 11.1. Task

  1. To view the Overlord Run-Time Governance properties, access the properties file located in $JBOSS_HOME/standalone/configuration/overlord-rtgov.properties.
  2. Add and modify classes to manage governance.
Report a bug

11.4. Common Properties

Table 11.1. Common Properties

Name Description
collectionEnabled This property will determine whether activity information is collected when the server is initially started. This value can be changed at runtime using the ActivityCollector MBean.
ActivityServerLogger.maxThreads This property will determine the maximum number of threads used by the activity collector to report all the activity units to the server.
ActivityServerLogger.durationBetweenFailureReports This property controls the duration (in milliseconds) between a failure being reported, if the client is having trouble contacting the activity server.
ActivityServerLogger.activityListQueueSize This property defines the queue size for pending activity lists, that are awaiting being reported to the activity server.
ActivityServerLogger.freeActivityListQueueSize This property defines the queue size to manage free activity lists that can be reused.
BatchedActivityUnitLogger.maxUnitCount, BatchedActivityUnitLogger.maxTimeInterval Activity unit batch logging properties.
infinispan.container JNDI name for default cluster to use when not specified explicitly.
Report a bug

11.5. Server Properties

Table 11.2. Server Properties

Name Description
MVELSeverityAnalyzer.scriptLocation Optional location of a MVEL script used to determine severity levels for nodes and links within the service overview diagram.
Report a bug

11.6. Client Properties

Table 11.3. Client Properties

Name Description
RESTActivityServer.serverURL This is the URL of the activity server collecting the activity events.
RESTActivityServer.serverUsername The username used to access the REST service.
RESTActivityServer.serverPassword The password used to access the REST service.
Report a bug

11.7. Database

The installer sets up the datasources for Runtime Governance, jBPM, SRAMP, and BPEL (Riftsaw). The datasources can be configured in $JBOSS_HOME/standalone/configuration/standalone.xml.

Note

By default, the datasource validation function is disabled. To enable this function, add the validate-on-match property as follows: 
<validation>
<validate-on-match>true</validate-on-match>
<valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/>
<exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/>
</validation>
Report a bug

11.8. Caching

The EPN and Active Collection mechanisms both have the ability to make use of caching provided by Infinispan. When running the Red Hat JBoss Fuse Service Works in clustered mode (that is, with standalone-full-ha.xml), it provides a default clustered cache container, which is referenced in the infinispan.container property in the overlord-rtgov.properties file.

Note

To make sure the individual named caches are clustered correctly, it is necessary to add an entry for each cache into the standalone-full-ha.xml file.
For more information on Infinispan configuration, refer JBoss Enterprise Application Platform 6.1 Development Guide.
Report a bug

11.9. Caching Example

The following cache entry for the "Principals" cache has been defined in the standalone-full-ha.xml file: 
<cache-container name="cluster" aliases="ha-partition" default-cache="default">
    <transport lock-timeout="60000"/>
    <replicated-cache name="default" mode="SYNC" batching="true">
        <locking isolation="REPEATABLE_READ"/>
    </replicated-cache>

    <!-- Configuration for Runtime Governance caches -->

    <replicated-cache name="Principals" mode="SYNC">
        <locking isolation="REPEATABLE_READ"/>
        <transaction mode="FULL_XA" locking="PESSIMISTIC"/>
    </replicated-cache>
</cache-container>
Report a bug