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

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

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources  on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src >  request for a different domain as 'domain-b.com' to get an image via an API request.  For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as  XMLHttpRequest  or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to  note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers from which these resources getting need to handl

[WSO2 AM] APIStore User Signup as an approval process

In previous versions of WSO2 APIManager before 1.6.0, it was allowed any user who's accessible the running APIStore come and register to the app.But there will be requirement like,without allowing any user to signup by him/her self alone,first get an approve by a privileged user and then allow to complete app registration.Same requirement can be apply to application creation and subscription creation as well.To fulfill that,we have introduced workflow extension support for  WSO2 APIManager  and you can find the introductory post on this feature from my previous blog post on " workflow-extentions-with-wso2-am-160 " . From this blog-post,I'll explain how to achieve simple workflow integration with default shipped resources with  WSO2 APIManager 1.6.0 and WSO2 Business Process Server 3.1.0 with targeting "user-signup" process. Steps First download the WSO2 APIManager 1.6.0[AM] binary pack from product download page . Extract it and navigate to