[JBoss JIRA] (BAM-139) EPN configuration tool
by Gary Brown (JIRA)
Gary Brown created BAM-139:
------------------------------
Summary: EPN configuration tool
Key: BAM-139
URL: https://issues.jboss.org/browse/BAM-139
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Tool to help build the network of event processor nodes with optional predicates.
Could be web and/or Eclipse based.
--
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
13 years, 1 month
[JBoss JIRA] (SRAMP-154) Create Information Processor derived artifact handler
by Gary Brown (JIRA)
Gary Brown created SRAMP-154:
--------------------------------
Summary: Create Information Processor derived artifact handler
Key: SRAMP-154
URL: https://issues.jboss.org/browse/SRAMP-154
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 0.2.0 - Milestone 4
Derive information processor configuration from the deployable war artifact.
When information types and context/property expressions stored in the repo, need to enhance this deriver to establish the appropriate relationships. But initial version should just represent the configuration as a specific type.
--
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
13 years, 1 month
[JBoss JIRA] (BAM-138) Information Processor configuration tool
by Gary Brown (JIRA)
Gary Brown created BAM-138:
------------------------------
Summary: Information Processor configuration tool
Key: BAM-138
URL: https://issues.jboss.org/browse/BAM-138
Project: Business Activity Monitoring
Issue Type: Feature Request
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.1
When SRAMP repo stored Information Type with expressions for deriving Context and Property information, then Information Processor configuration for a particular service could be created dynamically during the governance workflow, for deployment along side the service artifact being deployed.
One issue may be where the same information type is used across multiple services - as long as the definitions are consistent, then it shouldn't be an issue.
--
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
13 years, 1 month
[JBoss JIRA] (BAM-128) Synchronous activity event processing
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-128?page=com.atlassian.jira.plugin.sy... ]
Gary Brown commented on BAM-128:
--------------------------------
Aim should be:
- reuse EventProcessor and Predicate interfaces
- only accept ActivityType derived objects
- only return a result object, which initially can only be Block - supplied with message returned to client app
If no result object returned, then it should just record the activity event as normal.
Mechanism should be deployable as with EPN, but use a simpler configuration that does not include all of the unnecessary details.
> Synchronous activity event processing
> -------------------------------------
>
> Key: BAM-128
> URL: https://issues.jboss.org/browse/BAM-128
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M5
>
>
> The current policy enforcement example has two parts, the event evaluation using mvel to determine whether a customer should be suspended, and then an exchange handler configured in switchyard app to enforce the decision.
> This is an asynchronous approach to enforcement that potential enables a customer to exceed their restrictions (albeit briefly) before the enforcement kicks in.
> In situations where enforcement must apply immediately a policy has been broken, then we need a synchronous event evaluation to occur at the activity collector and potentially immediately affect the message exchange.
> Need to consider:
> - whether this mechanism should use a restricted form of the EPN as a way to make configuration consistent - although it would be dealing with derived ActivityType rather than an ActivityUnit at the top level, and interaction between nodes would also be synchronous, which may lead to ordering issues or configurations that would not be supported.
> - what actions are required based on the decision made in a policy - for the customer suspended case it is likely to be just throwing an exception, but are there other actions?
> Deployment of these sync policies should be equivalent to other components in the architecture.
> Benefit of having a specific mechanism may be that it doesn't cause confusion with the full blown configuration, and also the fact that it is supposed to be returning a decision, rather than just propagating derived results. Not using the EPN may have benefits of not including its mechanics in the lightweight server configuration.
> However we need to consider how it would interact with 'services' (e.g. cache) - possibly this could be a similar/same mechanism without having to use the whole EPN infrastructure.
--
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
13 years, 1 month