Sorry for not being specific. What didn't work for me is the jaggery graph.
There I see following code and it neglects the offset.
var httpsPort = process.getProperty('mgt.transport.https.port');
On Sun, Oct 27, 2013 at 5:31 PM, Anjana Fernando <[email protected]> wrote:
> Hi,
>
> No, it works, basically when there is a port offset, the default URL will
> not work for data publishing in the sample, for that, the BAM samples can
> be given the URL with a Java system property, with the name "url" (also the
> "username" and "password" in the same way). So for portoffset 1, you can
> run it like:-
>
> ant -Durl="tcp://localhost:7612"
>
> Cheers,
> Anjana.
>
>
> On Sun, Oct 27, 2013 at 5:24 PM, Nirmal Fernando <[email protected]> wrote:
>
>> $subject! http://docs.wso2.org/display/BAM240/Realtime+Traffic+Monitoring
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
> *Anjana Fernando*
> Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
--
Thanks & regards,
Nirmal
Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
