On Mon, Mar 26, 2012 at 3:12 PM, Waruna Ranasinghe <war...@wso2.com> wrote:

>
>
> On Mon, Mar 26, 2012 at 2:59 PM, Srinath Perera <srin...@wso2.com> wrote:
>
>> +1 for the approach for sending custom values
>>
>> When we send custom values, do we send information about the workflow
>> and instance ID etc?
>>
> No, but the workflow designer can add the instance ID to the variable he
> chose to publish into BAM, if he needs it for the analysis.
>
>
>>
>> I think we should we also have a default  set of monitoring data we
>> can push from a BPEL workflow to BAM (just like default Service stats)
>> that can be turned on easily. I think we can do this easily by
>> extending the ODE workflow event listener to emit workflow monitoring
>> data. It should send information like services invoked, how long the
>> instance ran,  .. requests send and received etc.
>>
>
+1,  Then later we can provide pre-built gadgets and analyzers for
monitoring BPEL work-flows, if BPEL can provide default set of monitoring
data.

Thanks,
KasunW


> +1.
> Lets add this to our roadmap
>
> Thanks,
> Waruna
>
>>
>> --Srinath
>>
>> On Mon, Mar 12, 2012 at 3:28 PM, Nandika Jayawardana <nand...@wso2.com>
>> wrote:
>> > Hi all,
>> >    We came up with a model to publish business process data to the
>> > BAM2 server in the following way to monitor Business Process.
>> > Basically,the idea is to implement an extension activity which would
>> > publish the process data to BAM. Developer of the business process can
>> > specify which data should be published to the bam in the following
>> > way. We took the standard 'from' syntax from bpel for selecting the
>> > data to be published. Extension activity xml syntax would be as
>> > follows.
>> >
>> > <bpel:extensionActivity>
>> >      <bam:publish>
>> >          <bam:key name="key1">
>> >                 <bam:from></bam:from>
>> >          <bam:key>+
>> >      <bam:publish>
>> > </bpel:extensionActivity>
>> >
>> > The value within the from section could be either a variable or an
>> xpath.
>> > Syntax for publishing from a variable
>> >
>> > <bpel:extensionActivity>
>> >      <bam:publish>
>> >         <bam:key name="key1">
>> >            <bam:from part="payload" variable="testVar1"/>
>> >         </bam:key>
>> >         <bam:key name="key2">
>> >            <bam:from part="payload" variable="testVar2"/>
>> >         </bam:key>
>> >      <bam:publish>
>> > </bpel:extensionActivity>
>> >
>> > Syntax for publishing from xpath
>> >
>> > <bpel:extensionActivity>
>> >        <bam:publish>
>> >            <bam:key name="key1">
>> >                <bam:from part="payload" variable="input">
>> >                        <bam:query
>> queryLanguage="urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"><![CDATA[tns:input]]></bam:query>
>> >                </bam:from>
>> >            </bam:key>
>> >        </bam:publish>
>> > <bpel:extensionActivity>
>> >
>> > <bpel:extensionActivity>
>> >        <bam:publish>
>> >            <bam:key name="key1">
>> >                <bam:from>$input.part/tns:input</bam:from>
>> >            </bam:key>
>> >        </bam:publish>
>> > <bpel:extensionActivity>
>> >
>> > Publishing from xpath is not essential as it is possible to extract
>> > values using xpath in the bam analyzer as well.  BAM server
>> > configuration data will go into the deploy.xml.
>> >
>> > Regards
>> > Nandika
>> >
>> > --
>> > Nandika Jayawardana
>> > Technical Lead
>> > WSO2 Inc ; http://wso2.com
>> > lean.enterprise.middleware
>> > _______________________________________________
>> > Dev mailing list
>> > Dev@wso2.org
>> > http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>>
>> --
>> ============================
>> Srinath Perera, Ph.D.
>>    http://www.cs.indiana.edu/~hperera/
>>    http://srinathsview.blogspot.com/
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>
>
>
> --
> -------------------------------------------------------------------------
> Waruna Ranasinghe
> Senior Software Engineer, WSO2
>
> Mobile: +94 724 318285
> BLOG: http://warunapw.blogspot.com
>
> www.wso2.com - "Lean . Enterprise . Middleware"
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kasun Weranga*
Software Engineer
**
*WSO2, Inc.
*lean.enterprise.middleware.
mobile : +94 772314602
<http://sanjeewamalalgoda.blogspot.com/>blog
:<http://sanjeewamalalgoda.blogspot.com/>
http://kasunweranga.blogspot.com/
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to