[JBoss JIRA] (BAM-114) Configuration of REST Active Server client
by Gary Brown (JIRA)
Gary Brown created BAM-114:
------------------------------
Summary: Configuration of REST Active Server client
Key: BAM-114
URL: https://issues.jboss.org/browse/BAM-114
Project: Business Activity Monitoring
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
When CDI used to compose the BAM components in a client environment, where activity events are reported to a remote activity server via REST, then need to config the server location.
One approach could be via JMX - but should see if approaches should be supported.
--
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
11 years, 5 months
[JBoss JIRA] (BAM-113) BAM should work in a clustered JBossAS environment
by Gary Brown (JIRA)
Gary Brown created BAM-113:
------------------------------
Summary: BAM should work in a clustered JBossAS environment
Key: BAM-113
URL: https://issues.jboss.org/browse/BAM-113
Project: Business Activity Monitoring
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 1.0.0.M4
Current version works in a standalone server. Need to ensure that it can also work in a clustered environment. Areas to check:
(1) JMS event distribution - ensure event processor work is distributed across multiple servers without problem, and that all servers are notified of results to update their local active collection representations.
(2) When caching used in support of the event processing and/or active collections, ensure that caches are correctly configured to work in the cluster.
(3) CEP configuration to work in a cluster.
--
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
11 years, 5 months
[JBoss JIRA] (BAM-111) Graphical representation of the current status of a conversation instance
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-111?page=com.atlassian.jira.plugin.sy... ]
Gary Brown updated BAM-111:
---------------------------
Fix Version/s: 1.1
(was: 1.0.0.M4)
> Graphical representation of the current status of a conversation instance
> -------------------------------------------------------------------------
>
> Key: BAM-111
> URL: https://issues.jboss.org/browse/BAM-111
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.1
>
> Attachments: CommsDiagStyle.gliffy, CommsDiagStyle.png, FlowDiagStyle.gliffy, FlowDiagStyle.png
>
>
> Initially the Savara web console will display a conversation instance as a table of activity events.
> This task will provide a graphical status view of the conversation instance, showing the execution path taken, and if still active, where the instance is currently in its execution.
> Although BPMN2 is the principle choreography representation that will be used, not all choreographies will be defined with a BPMN2 choreography - so we need to consider how this graphical representation will be defined.
> One approach may be to derive a BPMN2 like representation, based on the global Scribble protocol definition, as this will be the canonical representation used for all conversations being monitored. It would also be simpler than the BPMN2 original - just depends whether users would expect to see if based on the original representation.
> The other approach would be to only support graphical representation where a BPMN2 choreography has been defined, and provide a faithful graphical representation of the original choreography.
> To be decided ....
> However the same approach could be used as with RiftSaw - generate SVG images as snapshots of the state, and if the state changes while displaying, then just generate a new image.
--
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
11 years, 5 months
[JBoss JIRA] (BAM-111) Graphical representation of the current status of a conversation instance
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-111?page=com.atlassian.jira.plugin.sy... ]
Gary Brown commented on BAM-111:
--------------------------------
Some of this capability is provided with the call trace graph, which shows the trace of a business transaction instance as a tree structure.
This issue is looking to provide a graphical diagram to show the relationship between the tasks. It would be useful, but is not urgent for the first version - firstly we should make sure the correlation across components, and the representation as a call trace, work well.
> Graphical representation of the current status of a conversation instance
> -------------------------------------------------------------------------
>
> Key: BAM-111
> URL: https://issues.jboss.org/browse/BAM-111
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
> Attachments: CommsDiagStyle.gliffy, CommsDiagStyle.png, FlowDiagStyle.gliffy, FlowDiagStyle.png
>
>
> Initially the Savara web console will display a conversation instance as a table of activity events.
> This task will provide a graphical status view of the conversation instance, showing the execution path taken, and if still active, where the instance is currently in its execution.
> Although BPMN2 is the principle choreography representation that will be used, not all choreographies will be defined with a BPMN2 choreography - so we need to consider how this graphical representation will be defined.
> One approach may be to derive a BPMN2 like representation, based on the global Scribble protocol definition, as this will be the canonical representation used for all conversations being monitored. It would also be simpler than the BPMN2 original - just depends whether users would expect to see if based on the original representation.
> The other approach would be to only support graphical representation where a BPMN2 choreography has been defined, and provide a faithful graphical representation of the original choreography.
> To be decided ....
> However the same approach could be used as with RiftSaw - generate SVG images as snapshots of the state, and if the state changes while displaying, then just generate a new image.
--
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
11 years, 5 months
[JBoss JIRA] (BAM-110) Activity event generator
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-110?page=com.atlassian.jira.plugin.sy... ]
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
11 years, 5 months
[JBoss JIRA] (BAM-77) Backing store for active collections
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-77?page=com.atlassian.jira.plugin.sys... ]
Gary Brown commented on BAM-77:
-------------------------------
The other approach is to just deal with this as a startup situation, and use it to bootstrap the local copy. This will depend upon the importance of the information, and whether precise synchronization is required - but if not, then it may be a simple low cost approach to get the new server up and running. However it also assumes that other servers are already running. If this is a problem, then the only solution may be using a real persistent store.
> Backing store for active collections
> ------------------------------------
>
> Key: BAM-77
> URL: https://issues.jboss.org/browse/BAM-77
> Project: Business Activity Monitoring
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
>
> Although active collections generally represent a realtime transient snapshot of some relevant information, on occasions it may be necessary that all instances of a collection across a cluster are consistent, and complete (e.g. on a server startup situation).
> In this situations, the active collection would require some shared state mechanism (e.g. cache) to replicate their state. The issue is that each server in the cluster will attempt to update their instance of the collection, so this needs to be handled (e.g. before applying the change check that it is required - but this may require some synchronization).
> Due to the potential performance implications, this type of active collection should ideally only be used where infrequent updates are applied.
--
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
11 years, 5 months
[JBoss JIRA] (BAM-26) Investigate deserialising custom activity types
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-26?page=com.atlassian.jira.plugin.sys... ]
Gary Brown commented on BAM-26:
-------------------------------
The simplest approach would be to define a 'CustomActivityType' and mainly use the properties fields to provide the relevant information. The specific custom activity type should be defined in a field.
> Investigate deserialising custom activity types
> -----------------------------------------------
>
> Key: BAM-26
> URL: https://issues.jboss.org/browse/BAM-26
> Project: Business Activity Monitoring
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 1.0.0.M4
>
>
> Currently the JSON deserialization uses a type field to determine the ActivityType.
> However this is only possible because the types have been registered against the ActivityType class using the Jackson JsonSubTypes annotation.
> The benefit of the type field approach is that it is language independent (whereas @class is Java specific) and the amount of information in the json encoding is smaller (i.e. no package name).
> However this approach means it is not easy for users to add new ActivityType derived classes, as the class would need to be added to the JsonSubTypes derived in the annotations for ActivityType class.
> Another approach would be to have own type registry that custom activity type classes could also be registered with.
> Need to investigate the possibilities and how the user's custom classes would be added to the AS7 installation easily. May need to update the org.overlord.bam module?
--
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
11 years, 5 months
[JBoss JIRA] (BAM-89) Error has been thrown when stop the SwitchYard with BAM installed.
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/BAM-89?page=com.atlassian.jira.plugin.sys... ]
Gary Brown resolved BAM-89.
---------------------------
Fix Version/s: (was: 1.0.0.M4)
Resolution: Duplicate Issue
Same issue as BAM-22
> Error has been thrown when stop the SwitchYard with BAM installed.
> ------------------------------------------------------------------
>
> Key: BAM-89
> URL: https://issues.jboss.org/browse/BAM-89
> Project: Business Activity Monitoring
> Issue Type: Bug
> Reporter: Jeff Yu
> Assignee: Gary Brown
>
> When you installed the BAM distro, and the samples. Then you just press Ctrl+C to stop the SwitchYard, you'll see the following exception.
> ==========
> 22:30:33,849 ERROR [org.jboss.ejb3.invocation] JBAS014134: EJB Invocation failed on component EPNManager for method public abstract void org.overlord.bam.epn.EPNManager.removeNetworkListener(org.overlord.bam.epn.NetworkListener): javax.ejb.EJBTransactionRolledbackException: JBAS011049: Component is stopped
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:139) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:204) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.1.Final.jar:7.1.1.Final]
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.1.Final.jar:7.1.1.Final]
--
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
11 years, 5 months