Skip to main content

WSO2 ESB Proxy Services


If you are have ever try-out WSO2 ESB[1],you are quite familiar with WSO2 ESB proxy services.
A proxy service is a some kind of virtual service,which fronts an existing actual service end-point and which is hosted under WSO2 ESB.

Clients can send requests for proxy services hosted in ESB,as the client sees that service hosted in ESB without knowing of actual service end-point.Such proxy service has own WSDL which can be view from '?wsdl' parameter.

Advantage of such a proxy service is that proxy services can mediate the sending messages to the actual service,before they are delivered to the actual end-point and can mediate the responses before those reach the client.

There are several templates for proxy services as below and you can get more info on proxy services from [2].
  • Pass Through Proxy- Create a simple proxy service on a specified endpoint. This proxy service does not perform any processing on the messages that pass through the proxy.
  • Secure Proxy-Create a proxy service with WS-Security engaged in-order to expose an existing service with WS-Security.
  • WSDL Based Proxy-Create a proxy service from a WSDL of an existing web service.Endpoint information is extracted from such remotely hosted WSDL of an actual service.
  • Log and Forward Proxy-Create a proxy service which logs all the incoming requests and forwards them to a given end-point.[If necessary responses coming back from back-end service can be logged before routing them to the client.]
  • Transformer Proxy-Create a proxy service, which can transform requests and responses based on a specified XSLT configurations,where user is trying to expose a scenario from an existing service in a different message format.
  • Custom Proxy-Create a proxy service in which customize each aspects of a proxy including sequences,endpoints,transports.

The reason why I wrote this blog is to highlight a property which used in each proxy service template definitions.That's property.

In WSO2 ESB UI,when adding a new proxy service as in the image ,you'll see that you have to add proxy service name,the end-point of relevant actual service and then add publish WSDL options.

In this 'publish WSDL options', you can keep without pointing to any wsdl while setting that option 'none' or pointing to a wsdl url either from registry[keep option as 'Pick from Registry'] or from browser[keep option as 'Specify source url'] or adding to a inline wsdl[keep option as 'Specify in-line'].Once you set this 'publish WSDL options' from UI,you'll see the entry corresponding to wsdl options has defined in the proxy service source view definition accordingly as below.






The use of the above WSDL option is that,if a user likes to publish the actual back-end service WSDL into proxy service wsdl without hiding it,you can set above WSDL options with pointing to the url of actual service's WSDL.If a user don't want to publish the actual back-end service's wsdl from proxy service,that user can keep the wsdl options as 'none',without pointing to any wsdl.

[1] http://wso2.com/products/enterprise-service-bus/
[2]http://wso2.org/project/esb/java/4.0.3/docs/samples/proxy_samples.html




Comments

Post a Comment

Popular posts from this blog

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html
2 comments
Read more

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint.  Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as  below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...
3 comments
Read more

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...
7 comments
Read more