[overlord-issues] [JBoss JIRA] Created: (SOAG-104) Service activity console

Service activity console ------------------------ Key: SOAG-104 URL: https://jira.jboss.org/jira/browse/SOAG-104 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 Console for providing access to service activity information. User needs to be able to view service activity information in various ways, including: 1) Raw service events - although this view should only generally be used for detailed analysis 2) Conversation view - using correlation information to group service related events based on a business transaction 3) Conversation per Service vew - correlation information used to group service activity information for a selected service based on a business transaction. Selecting a business transaction to view could be based on time range, based on correlation attribute values, or possibly other custom properties. The console (or governance repository) should enable tokens/locators to be defined against message schema, which can be used to extract business relevant information from the business messages, and used by the console to query appropriate correlated business transactions. If the console is going to provide access to service activity information generated by a variety of different runtime platforms, where different design/modelling approaches have been used, it would be good to enable either the local model (service) or global model (conversation/choreography) views to be represented in a range of appropriate graphical notations - and eventually enable the service activity trace to be replayed back through the graphical representation. Other future requirements may enable business specific views to build on the base information - but this may be through a pluggable views in something like JBoss Workspace. The range of events that may be displayed, and their format, will be defined as a separate task - but the console should be flexible enough to cater for customisaton/extension of the event model. -- 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