[overlord-issues] [JBoss JIRA] (BAM-110) Activity event generator

[Gary Brown (JIRA)]

     [ https://issues.jboss.org/browse/BAM-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Brown updated BAM-110:
---------------------------

    Fix Version/s: 1.1
                       (was: 1.0.0.M4)


The current version includes an event generate driven by example transactions. This issue may provide a higher level way to define these example transactions using business process descriptions - but is not urgent as the current mechanism is adequate.
                
> Activity event generator
> ------------------------
>
>                 Key: BAM-110
>                 URL: https://issues.jboss.org/browse/BAM-110
>             Project: Business Activity Monitoring
>          Issue Type: Feature Request
>            Reporter: Gary Brown
>            Assignee: Gary Brown
>             Fix For: 1.1
>
>
> Create an activity event generator that will be driven by a scribble protocol derived from a choreography (WS-CDL or BPMN2).
> The protocol will define the alternate paths that can taken, representing valid executions of the business protocol. Example messages will need to be defined for each interaction, to represent templates for the messages that should be passed. These templates will include tags associated with values that should be replaced.
> One special tag will represent the conversation id that would be used to correlate the events. Although consideration should be given regarding how to support sub-conversations.
> Other tag fields will have values defined in supporting files, and these values will be randomly selected for each instance of a message that is generated. These fields will eventually be used in more advanced queries.
> Need to determine how to generate erronous business transactions, when required. The generator should be configured with a 'factor' that indicates how often an erronous transaction should be generated. Errors could be produced by simply sending a random message, normally associated with the business transaction, but not the type that is expected next (or for simplicity, just send the initial message again).
> Eventually, when SLAs and assertions are defined in the model, we should consider generating nessages/transactions that satisfy and violate those policies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira