Proxy for an HTTP request WSO2 ESB - wso2

I wonder if it is possible to send an HTTP request throuht WSO2 ESB. I have an integration with a system that consist only in invoking an URL... it would be like a kind of redirection.
Can I do that in WSO2 ESB?
Regards

I have found this link about restfull services in WSO2 ESB:
http://wso2.org/library/articles/2012/10/implementing-restful-services-wso2-esb
I think this is a better way to handle http requests & responses in wso2 esb, rather than the way they are treated in the links you provide. What do you think about that?

Below links will be help you to find a solution to your question.
http://wso2.org/library/knowledge-base/2011/03/handling-httpget-request-invoking-external-web-service-wso2-esb
http://docs.wso2.org/wiki/display/ESB451/Handling+HTTP-get+Requests+from+WSO2+ESB+and+Calling+an+External+Web+Service

Related

Can WSO2 MB handle HTTP requests?

I've been working with WSO2 Message Broker in order to publish and consume messages through jms and other clients. I've gone through the official documentation including the samples.
What I want to know is that, is it possible for WSO2 MB to handle http requests directly instead of jms. Yes you can do something like this, by converting http to jms through WSO2 ESB which seems like a long process.
ie: I mean having http as the end point or the transport to publish and consume messages directly in WSO2 Message Broker.
In order to achieve this, you will have to use ESB + MB set up as explained at [1]. What you can do is to use ESB to wrap JMS functionality using a HTTP client. It is recommended to use ESB externally in a separate JVM when using this setup.
[1] http://wso2.com/library/articles/2013/03/configuring-wso2-esb-wso2-message-broker/
Regards,
Pubudu.

How to decompress gzip http response in wso2 ESB?

I have a base service which returns gzipped response which wso2 esb is unable to understand. So when i create a pass through proxy of the above web service and when i try to run the service in soapUI, the result that esb shows me is the wsdl file of the above service. I am unable to find out how to decompress the response sent from the base service in wso2 esb. is there any way to do it? Looking forward to your solutions. Thanks in advance.

Call WSO2 DSS service using ajax?

I have one data service in WSO2 DSS. And also its possible to call using browsers.But i can't make a request using ajax to call this service.I think CORS issue is occurring.So i want to add Access-Control-Allow-Origin parameter to response header.How this is possible in WSO2 DSS ,Any suggestion ?
I think you can put a custom headers by adding axis2 custom out flow handler.
http://shivendra-tripathi.blogspot.com/2010/04/adding-handler-in-axis2.html?m=1
http://shivendra-tripathi.blogspot.com/2010/04/adding-soap-header-in-axiom.html?m=1

WSO2 ESB : Invoking selective operation of an endpoint?

I have created a WSO2-DS SOAP service with three operations, want to invoke a selective operation of that endpoint from a REST API ESB service.
Looks like the endpoint does not provide option to filter further based on operation.
Any help appreciated..
Thanks,
Wajid
Header mediator should work ... header name="Action" value="soap action"

More than 1500 proxyes with JMS transport, WSO2 ESB 4.0.3 and Activemq

Is there developers who have been succeeded deployed to wso2 esb more than 1500 proxy services
with jms transport without any problems?
Criteria:
deploying process must be very fast
wso2esb use activemq client libraries and activemq brocker
someone please help me!
This should be possible. There is no limitation on the number of proxies that an ESB can have.
You may try this with using the hot deployment capabilities of WSO2 ESB.
You may create a bunch of proxy services and place them inside:
/repository/deployment/server/synapse-config/default/proxy-services
Then the proxies with get automatically deployed..
eg:
proxy_1.xml, proxy_2.xml, proxy_3.xml,..., proxy_1500.xml etc.
However, having this number of proxy services, gives some indication of some anti-pattern in your SOA. Please review whether you need this much of proxy services in your solution architecture.