[
https://jira.jboss.org/jira/browse/SOAG-105?page=com.atlassian.jira.plugi...
]
Gary Brown commented on SOAG-105:
---------------------------------
Triggering further processing:
SAM discusses using a CEP solution to process service activity information, to trigger
further processing. This could be based on the service activity event stream.
However the behavioural service validation requires the service activity (interaction
based) information to be enriched with the conversation identity, and therefore the
validation cannot be triggered based on the raw event stream - it will need to be
triggered based on the stored information with the additional properties.
Need to consider whether other validation needs to be based on the enriched information,
and therefore provide a way in which the enriched information can be treated as a
different event source that could be used by other interested components (or CEP rules).
Service activity repository
---------------------------
Key: SOAG-105
URL:
https://jira.jboss.org/jira/browse/SOAG-105
Project: SOA Governance
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Behavioural Monitoring
Affects Versions: 1.0 MR3
Reporter: Gary Brown
Assignee: Jeff Yu
Fix For: 1.0 MR3
Persistence storage for service activity information.
Information will be received from a variety of event sources reporting service activity
information - which will then be persisted in the database.
Information enrichment needs to be supported. This can be in the form of extracting
conversation identity information, or other custom properties, which can then be used to
query the service activity information.
NOTE: Although the storage of service activity information could be used to trigger a
variety of activities, including deriving the properties described above, as well as
performing higher level validation, the behavioural validation is dependent upon the
conversation identity fields - and therefore it may be better to derive this base
information when recording the service activity information. But other information and
validation tasks can be triggered based on the storage of the service information -
possibly using DNA at some point (i.e. the sequencing mechanism).
--
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