Hi Sumedha,
you can use the ESB documentation at [1]. You can get important system
information as mentioned in [2].
Ex: You can extract the system time at the start and end of the API and
send them to BAM such that you can use those values to calculate the
response time.
[1]. http://docs.wso2.
Hi Chanaka,
Thanks for the quick response.
Will first try with BAM Mediator. Is there a sample configuration that I
can use which extracts important data..?
Thanks
SumedhaS
On Fri, Feb 14, 2014 at 4:56 PM, Chanaka Fernando wrote:
> Hi Sumedha,
>
> Currently ESB is not publishing the statisti
Hi Sumedha,
Currently ESB is not publishing the statistics for REST APIs defined in it.
One way is to use the BAM mediator as you mentioned. That will not have a
considerable impact on the response time but you need to use it carefully.
You need to publish all the required data with a single BAM m
Hi all,
Is there a way to enable statistics for REST APIs in ESB. ?
For proxy services, sequences etc we can enable statistics and publish them
to BAM. AFAIU only way to do this for APIs is to use the BAM Mediator. Is
there any other way to achieve this
Will this have a significant impact on the
Hi Shenavi,
Is there any particular reason for converting the data in Excel sheets to a
CSV file. It is possible to expose the data in Excel sheet directly as
explained in [1].
Can you explain more on your requirement..?
[1] http://docs.wso2.org/display/DSS311/Excel
Thanks
SumedhaS
On Wed, Feb
---
Developer Studio > Eclipse-Tools > #1441 failed.
---
This was manually triggered by Maheshika Goonetilleke.
No failed tests found, a possible compilation erro
Hi
Can you try following then use call mediator as above, no need to use
javascript for encoding purpose.
On Thu, Feb 13, 2014 at 6:34 PM, Jay wrote:
> Hi,
>
> I need to pass an Url encoded value
> (Ex:http://www.linkedin.com/pub/-/87/998/935) to an endpoint as a
> part of the Ur
Hi Susinda,
GET http://192.168.2.1:8280/test?type=crust
in short term should work
On Fri, Feb 14, 2014 at 8:49 PM, Amila Maha Arachchi wrote:
> According to your first mail, you have used query.param.val, but it
> should be query.param.Symbol. That might be the place where you went
> wrong.
>
According to your first mail, you have used query.param.val, but it should
be query.param.Symbol. That might be the place where you went wrong.
On Fri, Feb 14, 2014 at 8:12 PM, Susinda Perera wrote:
> Yes it worked, thanks, Dnt know where i have gone wrong.
>
>
> On Fri, Feb 14, 2014 at 8:00
The following works fine. Please check again.
GET http://192.168.2.1:8280/test?type=crust
http://ws.apache.org/ns/synapse"; name="Test" context="/test">
On Fri, Feb 14, 2014 at 6:46 PM, Susinda Perera wrote:
> I tried to acces
Yes it worked, thanks, Dnt know where i have gone wrong.
On Fri, Feb 14, 2014 at 8:00 PM, Kasun Indrasiri wrote:
> The following works fine. Please check again.
>
> GET http://192.168.2.1:8280/test?type=crust
>
> http://ws.apache.org/ns/synapse"; name="Test" context="/test">
>
>
>
I tried to access query parameters using property mediators in
both query.param and uri.var ways, but only uri.var gives me an output.
What i thought was syntax like
use uri.var
and syntax like
uses
query.param but i was not able to use query.param in second syntax
Neither
nor
syntax gave me
Hi,
I'm currently looking into implementing clustering support for Stratos Load
Balancer and found that the current Synapse SALSession implementation does
not distribute the session information in a clustered environment.
I would like to propose to implement this functionality using the caching
f
13 matches
Mail list logo
