Ambica, I will answer your last question first. Yes, WSO2 ESB can be used with text, POX or binary messages. Please see http://synapse.apache.org/Synapse_Samples.html#Sample250
Now going in the order of your questions, 1. What you want is to create a client to send requests isn't it? In that case if you have a WSDL of the back end service then life is easy. You can publish the WSDL in your proxy service (see: http://synapse.apache.org/Synapse_Configuration_Language.html#proxy). WSO2 ESB will automatically change the endpoint URL of the WSDL to reflect your proxy service inside the WSO2 ESB. If you are not using a WSDL then you will somehow have to create the XML payload (I am assuming you are using SOAP here). Then you can use TCPMonitor (http://ws.apache.org/commons/tcpmon/download.cgi) to send that payload to your proxy service. 2. Your proxy service is exposed under the URL http://localhost:8280/soap/your_proxy_name. I have mentioned this in my previous mail as well. 3. You need to select the XSLT folder in the integrated registry window to save your file inside that folder. Is this what you were expecting? In general think of the registry as a simple file system (this is just to make things clear). So if you want to add something to a folder you first have to select it. Then what ever you add will go to that folder. If you can share your synapse.xml then I will be able to assist you more. Thanks, Saliya ambica sona wrote: > Thank you very much Saliya. > I think now i have understood a lot (your explanation was very > simple). I feel it is veryyyy good as it has GUI like datapower. As > you told i have created XSLT (hope its not a problem if we have more > than one XSLT in inSequence and outSequence because i have to use more > than one transformation) and modified synapse.xml according to my > requirement.( Here this endpoint will be the service where i need to > route my request after transformations ). Till this its perfect. How > can i send request to test which will pass to this? and how to expose > this as s service(means what will be the URL of my service?). and i > have a doubt that when i add XSLT using ESB GUI will it not b stored > in ".....wso2esb-1.7.1\registry\XSLT" folder? and one more thing u r > always mentioning the word soap so cant WSO2 b used for a text or > binary request? (hope it will) > > > On 9/3/08, *Saliya Ekanayake* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi, > > As mentioned by me and others the solution is to come up with a proxy > service. As an example say you are trying to expose this proxy service > by the name MyProxyService, then the URL will be > http://hostname:8280/soap/MyProxyService. > > Here's a rough procedure on how you can continue. > > 1. Create the two required XSL files you want. One is to transform the > incoming message to the proxy service from client. The other to > transform the response coming from the back end service before sending > to the client. > > 2. Startup the WSO2 ESB using the wso2server.sh or wso2server.bat that > you find inside the "bin" directory of the ESB home. > > 3. Go to the ESB console by typing the URL https://localhost:9444/esb > The default user name and password are admin and admin. > > 4. In the console click on the Integrated Registry menu on the left. > Then you will get the ESB's internal registry. Select the XSLT folder > from there. Then click on the "New" button on the bottom right > box. Then > in the pop up window give a name to your XSL and paste the content of > it. Then click "Save". You will now see that your XSL is added inside > the XSLT folder. Do the same for the other XSL file as well. Note: If > your XSL files are x1 and x2 then their keys (the key you used to > retrieve them) will be XSLT/x1 and XSLT/x2. > > 5. Stop the ESB server and open the synapse.xml inside the > webapp/WEB-INF/classes/conf directory using a text editor and add the > following inside the <syn:definitions> element. > > <syn:proxy name="MyProxyService" startOnLoad="true"> > <syn:target> > <syn:endpoint> > <syn:address > uri="*http://localhost:9000/axis2/SimpleStockQuoteService*"/> > </syn:endpoint> > <syn:inSequence> > <syn:xslt key="*XSLT/x1*"/> > </syn:inSequence> > <syn:outSequence> > <syn:xslt key="*XSLT/x2*"/> > </syn:outSequence> > </syn:target> > </syn:proxy> > > Note: the bold faced content may have to be changed based on your back > end service URL and XSL keys. You can do this using the ESB console > without writing XML by hand. It provides a nice UI to do so, but > to make > it clear to you in the steps I chose the manual way. > > The operation of this proxy service will be to transform the SOAP body > of the incoming message based on the x1 XSL and to send it to the > service hosted at http://localhost:9000/axis2/SimpleStockQuoteService > and then to transform the SOAP body of the response based on the > x2 XSL > and return it to the client. > > Thanks, > Saliya > > > ambica sona wrote: > > Hi to all, > > > > I understood the execution of samples which we have in the download > > but not getting an idea on how to start a new one. Sorry to say this > > but i am unable to proceed. I have worked on mule, service mix and > > jboss ESB but i heard from some one and got from search pages that > > WSO2 is the best among all so interested in working this. May b my > > mind set is like as other ESB s and this i am feeling little > > confusing. I need some clarifications still. For example, i have run > > sample8 and got the response. As it is using XSLT s i want to > know on > > which req these XSLT s been applied? and in return i got the stock > > quote price but i want to see the response after these XSLT s have > > been applied. and the mani thing is how can i expose this as a > service > > so that my clinets can send request to this service(want to know > > something like what will be the URL to which my clients will post > > request). Please answer me ASAP so that i can continue. > > > > On 9/2/08, *Saliya Ekanayake* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > Hi Ambica, > > > > The axis2Server folder contains necessary > software/configuration to > > start the sample back end services. The most of the samples > that are > > explained in the WSO2 ESB Samples guide [1] require you to have > > back end > > services which actually contain the business logic. Look > into the > > "src" > > directory of the axis2Server and you will find a set of services > > in six > > different folders. You can use Ant to build and host these > services > > inside the provided Web service container, Apache Axis2. > After hosting > > the services you can start Axis2 using the axis2server.sh > (or the .bat > > version) inside the axis2Server folder. Note: please refer > to the > > sample > > guide to see which service is required for which sample. > > > > After setting up the services you need to configure the ESB to > > suit your > > scenario. The client comes into play afterwards. The axis2Client > > folder > > contains the necessary client code to call the ESB. You can > again use > > Ant to build and run the client. The parameters you need to > specify > > depends on the particular sample that you are testing. > Again, please > > refer to the samples guide for more information. > > > > Please note that these clients and services have nothing to do > > with the > > ESB except in providing additional resources for the samples. > > > > [1] http://wso2.org/project/esb/java/1.7.1/docs/ESB_Samples.html > > > > Regards, > > Saliya > > > > <http://wso2.org/project/esb/java/1.7.1/docs/ESB_Samples.html> > > ambica sona wrote: > > > Thankyou for all for your quick responses. > > > under the samples i have 2 floders one is Server and other is > > Client. > > > Both are related to each other right? > > > > > > > > > On 9/2/08, *Saliya Ekanayake* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>> wrote: > > > > > > Hi Ambica, > > > > > > Thanks for the suggestion, but may be you have not > seen the rest > > > of the > > > samples (I am assuming this as you have mentioned that > you got > > > only one > > > sample). Please try downloading a clean one from > > > http://wso2.org/downloads/esb/ > > > > > > Anyway regarding the issue at hand, the obvious > solution is to > > > implement > > > a simple proxy service. A proxy service basically > means that you > > > expose > > > a service interface to the outside world without actually > > having the > > > business logic with you. You configure the proxy service > > such that you > > > do whatever with the incoming message and send it to the > > real back end > > > service, then do whatever with its response and then send > > back the > > > response. WSO2 ESB gives you the support to perform XSLT > > transforms > > > using the entity known as the XSLT mediator. > > > > > > Regards, > > > Saliya > > > > > > ambica sona wrote: > > > > > > > > Hi to all, > > > > > > > > I am new to WSO2. for our project we are going to use an > > ESB. i got > > > > information that WSO2 is the one which has so many > features. > > > > So we thought of implementing that. When i download > i got > > only one > > > > sample. but i am not cleared by looking in to that > sample. > > > > Actually my requirement is a request will come as an > HTTP > > Request. I > > > > need to apply some transformation rules on that > request using > > > some xsl > > > > file and route to a URL which will send the response > back > > to me and > > > > then to this response i need to apply few > transformations > > again and > > > > send the response back as an HTTP response. > > > > i am not understanding at all how to start, how to > send the > > > request or > > > > how to get the response. how can i get an ESB > application > > developed > > > > using WSO2 as a service or a web application??? > > > > can some one help me out in this. > > > > and my small suggession is its better to add an HTTP > request- > > > response > > > > processing flow sample as an example in download... > > > > > > > > > > > > Waiting eagerly for a reply. > > > > > > > > Thank you > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > > > Esb-java-dev mailing list > > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> > > > > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > > > > > > > _______________________________________________ > > > Esb-java-dev mailing list > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > <mailto:[email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>>> > > > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Esb-java-dev mailing list > > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > > > _______________________________________________ > > Esb-java-dev mailing list > > [email protected] <mailto:[email protected]> > <mailto:[email protected] <mailto:[email protected]>> > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Esb-java-dev mailing list > > [email protected] <mailto:[email protected]> > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > _______________________________________________ > Esb-java-dev mailing list > [email protected] <mailto:[email protected]> > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-dev mailing list > [email protected] > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > _______________________________________________ Esb-java-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
