Proxy Hosting Blog

As its name suggests a Proxy Service is a virtual service that hides the real service. When defining a Proxy Service in the WSO2 ESB you could provide a inSequence, outSequence, faultSequence and a butt endpoint (Not all of these are essential).

A system as its name suggests send the thought through a system of mediations. Therefore users could go mediation on requests bearing into a Proxy Service (by the inSequence) as well as responses it receives (by the outSequence).

When an endpoint is certain in a Proxy Service, messages that are directed to it goes through the inSequence previous to been sent to the real endpoint.

Now that we’ve covered a few basic dreams on the stipulations used in Proxy Air force lets go ahead and start one. Its always advisable to declare entities in your configuration as reusable components (Just as you do it in OOP). Therefore lets mark out our sequences and endpoints as reusable entities and use them in the foundation of the Proxy Service.

For this develop I would be making a proxy service for the digit2image service which can be found on mooshup.com (The union site of the WSO2 Mashup Server).

1. Lets start our endpoint. An Endpoint can be produced by visiting the Endpoints link (Located under Deal with).

   Here are four distinct kind of endpoints, Please give up the documentation on endpoints for here top. For this develop I will start a simple Address Endpoint.

   
   When making a address endpoint I simple disorder its name and an Address (Having a look at the wsdl of our real service, I find that the endpoint URL is http://mooshup.com/air force/system/digit2image.SOAP12Endpoint/

2. Lets start a system. A system can be produced by visiting the Sequences link (Located under Deal with)

   

   When it comes to sequences, you could start complex sequences by one or more of the inbuilt disinterested party or by your own custom disinterested party. For simplicity I will be making a system with a simple Log negotiator. All it does is log the thought to the console.

   

3. Now that we have our reusable components in house its time to start the real Proxy Service. This can be done by visiting the Proxy Service link (Located Under Add).

   
   This will take you through a 3 step wizard.

   1. In the initially step I provide a name for my service. Additionally I could configure several properties on a Proxy Service, for simplicity I will be sticking to the defaults. You could give up the documentation on Proxy Service foundation for more details.

      

   2. step 2 questions for an Insiquence and a targetEndpoint. Its mandatory that you have at-least one of these. You could optionally have both as well. In our develop lets use the system we produced in Step 2 (DemoSequence) as the inSequence and the endpoint we produced in Step 1 (digit2ImageServiceEndpoint) as our butt endpoint.

      

   3. step 3 questions us for an outSequence and a faultSequence, both of which are discretionary. So lets use the default of none.

      

   Once you’ve done hit close. Now we have produced our new Proxy Service on WSO2 ESB 2.0.

Note : If you want this proxy service to be saved dont not remember to go to the synapse link and hit save so that this Proxy will be void when you regenerate the server.

Comments Off , Pings Off.