Service activity event model
----------------------------
Key: SOAG-106
URL:
https://jira.jboss.org/jira/browse/SOAG-106
Project: SOA Governance
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Behavioural Monitoring
Affects Versions: 1.0 MR3
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0 MR3
Definition of event model for reporting service activity from various runtime platforms,
and storing the information in a repository.
Event model needs to be extensible, although there should be a fixed core of standard
events defined.
The events could be interaction based, i.e. indicating messages being sent and received,
or task based i.e. task started and finished. Data related events could also be stored,
when variables are updated.
The actual events stored could be dependent upon filters defined in the activity
recorders.
Question: should the event model be XML based? Or should it support message content being
non-xml - i.e. Java objects, or other binary formats? Possible non-XML message contents
could be reported in a summarised XML form, to provide enough useful information.
The events recorded from a service may be based on local service identity information.
This can be used to group events generated by a particular session at a service, but they
won't necessarily be business relevant. To be able to correlate service activity,
associated with a particular business transaction, across multiple services, it will be
necessary to derive business identity that is common across services. However, only some
of the reported service activity events may contain the business identity properties - so
these should be used to associate the business identity with the local technology specific
service/session identity information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira