To use Elasticsearch as the Activity and Situation Store implementation, the following property values need to be defined:

with the additional support properties:

To use a SQL database as the Activity and Situation Store implementation, the following property values need to be defined:

with the additional support properties:

The database is defined by the datasource configuration located here: $JBOSS_HOME/standalone/deployment/overlord-rtgov/rtgov-ds.xml as part of the server installation type.

The default SQL database is the H2 file based database, and is created during the installation of the all type.

MySQL

<module xmlns="urn:jboss:module:1.1" name="mysql">
   <resources>
     <resource-root path="mysql-connector-java-5.1.12.jar"/>
   </resources>
   <dependencies>
     <module name="javax.api"/>
     <module name="javax.transaction.api"/>
   </dependencies>
</module>

<subsystem xmlns="urn:jboss:domain:datasources:1.0">

        <datasources>

            .....

            <drivers>

                ...

                <driver name="mysql" module="mysql">

                    <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

                </driver>

            </drivers>

        </datasources>

    </subsystem>

<?xml version="1.0" encoding="UTF-8"?>

<datasources>

    <datasource jndi-name="java:jboss/datasource/OverlordRTGov" pool-name="OverlordRTGov" enabled="true" use-java-context="true">

        <connection-url>jdbc:mysql://localhost:3306/rtgov</connection-url>

        <driver>mysql</driver>

        <security>

            <user-name>root</user-name>

            <password></password>

        </security>

    </datasource>

</datasources>

Postgres

<module xmlns="urn:jboss:module:1.1" name="org.postgresql">
   <resources>
     <resource-root path="postgresql-9.1-902.jdbc4.jar"/>
   </resources>
   <dependencies>
     <module name="javax.api"/>
     <module name="javax.transaction.api"/>
   </dependencies>
</module>

<subsystem xmlns="urn:jboss:domain:datasources:1.0">

        <datasources>

            .....

            <drivers>

                ...

                <driver name="postgresql" module="org.postgresql">

                    <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>

                </driver>

            </drivers>

        </datasources>

    </subsystem>

<?xml version="1.0" encoding="UTF-8"?>

<datasources>

        <datasource jndi-name="java:jboss/datasource/OverlordRTGov" pool-name="OverlordRTGov" enabled="true" use-java-context="true">

        <connection-url>jdbc:postgresql://localhost:5432/rtgov</connection-url>

        <driver>postgresql</driver>

        <security>

            <user-name>....</user-name>

            <password>....</password>

        </security>

    </datasource>

</datasources>

The samples/ordermgmt folder contains examples related to an Order Management system implemented using a SwitchYard application.

The samples/ordermgmt/app folder contains the switchyard application, with some additional interceptors to execute policies synchronously (see Activity Validators section for more information, and the Synchronous Policy quickstart more a specific example of its use).

The samples/ordermgmt/epn folder contains an Event Processor Network (see later section for details) that is used to convert switchyard application exceptions into "Situations", which is a form of alert used by the Runtime Governance platform.

The samples/ordermgmt/ip folder contains an Information Processor (see later sectoin for details) that is used to extract additional information from message payloads, that will be useful when analysing the activity events.

The samples/policy/sync folder contains a policy that is invoked synchronously - it determines whether a user has invoked the service more than once every two seconds, and if so, blocks the service invocation.

The samples/policy/async folder contains a policy for asynchronously calculating the debt associated with a customer, and suspending their account if it goes above a defined level. The suspended status of the customer is checked when they next invoke the service, and the service invocation blocked if they have been suspended.

The samples/sla/epn folder contains a policy for determining whether a Service Level Agreement has been violated, and if so, reported as a Situation.

The samples/sla/monitor folder contains a webapp that directly integrates with the RTGov components.

To install an OSGi application to provide a simple order management capabilty, with an Event Processor Network to convert exceptions into Situations, run the following command from the fuse console:

features:install rtgov-samples-ordermgmt-epn

To install a policy that will check for SLA violations, run the following command from the fuse console:

features:install rtgov-samples-sla

To install a policy that will be evaluated immediately, to prevent a customer from invoking a service more than once within two seconds, run the following comand from the fuse console:

features:install rtgov-samples-policy-async

To install a policy that will evaluate a customer’s debt level, and suspend their account if it becomes too high, run the following comand from the fuse console:

features:install rtgov-samples-policy-async