Looks good.

Please check the default value for the Summary DB datasource URL. It should
point to the STATS DB inside BAM.

Thanks,
NuwanD.

On Wed, Mar 4, 2015 at 4:53 PM, Bhathiya Jayasekara <[email protected]>
wrote:

> Hi Sumedha/Nuwan,
>
> I modified the UI as per last review feedback. Please find screenshots
> attached.
>
> Thanks,
> Bhathiya
>
> On Tue, Mar 3, 2015 at 12:09 PM, Sumedha Rubasinghe <[email protected]>
> wrote:
>
>> The idea here is to eliminate the manual steps performed in
>> https://docs.wso2.com/display/AM180/Publishing+API+Runtime+Statistics
>>
>> We did a review little while ago and it seems there is a similar
>> functionality available for AS & DSS (as mentioned in
>> https://docs.wso2.com/display/AS521/Collecting+Data+Statistics+of+Services
>> )
>>
>> source :
>> http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/data-agents/org.wso2.carbon.bam.service.data.publisher/4.2.1
>>
>> So we decided to re-use the same admin service (with some improvements)
>> and write a Jaggery UI on top of it.
>>
>>
>>
>>
>> On Mon, Mar 2, 2015 at 10:38 AM, Chanika Geeganage <[email protected]>
>> wrote:
>>
>>> Hi,
>>>
>>> We are currently working on a feature which provides a way to do the
>>> configuration for publishing statistical data in APIM, using
>>> 'admin-dashboard' jaggery app rather than changing configuration files
>>> (api-manager.xml) in the file system. The following are the main areas to
>>> be implemented
>>>
>>> 1. Enable/Disable publishing statistics.
>>> 2. Provide an UI in admin-dashboard to
>>>      - enter event receiver configuration details (ie. event receiver
>>> URL groups, username and password)
>>>      - enter configuration details of the analyser node
>>>      - enter details of the statistics datasource
>>> 3. Save the event receiver configurations in the registry.
>>> 4. Deploying the toolbox in the analyser node though the admin service
>>> 5. Save the datasource in the registry by calling ndatasource admin
>>> service.
>>> 6. Change the existing code to get the event receiver, and stat
>>> datasource details from the registry
>>>
>>> Thanks
>>>
>>> --
>>> Best Regards..
>>>
>>> Chanika Geeganage
>>> Software Engineer
>>> Mobile : +94773522586
>>> WSO2, Inc.; http://wso2.com
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Software Engineer,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
>



-- 
Nuwan Dias

Associate Tech Lead - WSO2, Inc. http://wso2.com
email : [email protected]
Phone : +94 777 775 729
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to