topic Re: [resolved] REST service proxy route in Talend Studio

[resolved] REST service proxy route

Anonymous — Sat, 16 Nov 2024 12:43:36 GMT

Hello!
Using Talend ESB, I want to proxy my REST service that is deployed, for example, on: http://hostnameA:8080/web_app to http://hostnameB:8085/web_app. That means, when I want to invoke the service (http://hostnameA:8080/web_app), I need to invoke them on: http://hostnameB:8085/web_app. It is just a simple proxy route.
I tried to do this using TOS and Talend ESB Studio, but without result. I tried something similar with Axis web services and works fine. My configuration for this case was:
Part of camel-config.xml file

address="http://proxy_hostname:8090/application/service/TokenService"
endpointName="service"
serviceName="s:TokenService"
wsdlURL="etc/TokenService.wsdl"
xmlns:s="http://tempo.intalio.org/security/tokenService/"/>

serviceName="serviceNS:TokenService"
endpointName="serviceNService" address="http://hostname:8080/axis2/services/TokenService">

....

Can someone help me?
Thanks in advance!

Re: [resolved] REST service proxy route

Anonymous — Tue, 23 Aug 2011 10:58:42 GMT

Can anyboby, please help me?

Re: [resolved] REST service proxy route

Anonymous — Tue, 23 Aug 2011 14:29:30 GMT

Hi,
Can you give us a little bit more details on what is not working actually ?
Thanks,
Bahaaldine

Re: [resolved] REST service proxy route

Anonymous — Tue, 23 Aug 2011 14:59:25 GMT

Hi,
I have a REST service deployed on http://hostname:8080/alfresco/service/service_name/process/{instanceId}/doctypes/{doctype} with,as you can see, 2 parameters. I want to publish this service on Talend ESB and proxy them on different hostname and (or) port.
I've tried with a job that call this service using the tREST component, exported them as an OSGi bundle for ESB and deployed on ESB. When I invoke them with "job:start job_name" command it works fine. Shows the expected response (link in string format). I think this is not a right solution to proxy a REST service.
How can I invoke this job remotely from another application? Is there any other better solutions to proxy a REST service using Talend ESB? Can I use the Route Builder within Talend ESB Studio to create a simple proxy route? If yes, how? Is there any example?
Thanks

Re: [resolved] REST service proxy route

Anonymous — Tue, 23 Aug 2011 16:20:55 GMT

Hi
You can probably just use simpler Camel HTTP or Jetty components for a simple proxying.
I'm not sure if you can use CXF components in the from: mode when WSDL2 is used to describe a RESTful endpoint.
Alternatively please also consider using to:cxfrs:uri, instead of just to:uri, though to:uri should work, the problem seems to be on the from: end

Re: [resolved] REST service proxy route

Anonymous — Tue, 23 Aug 2011 16:24:23 GMT

Hi,
I think you can do it directly on the RouteBuilder :
- Create a cMessagingEndpoint, set the URI as follow :
"cxf://http://KarafHostName:KarafPort/webserviceEndpoint?wsdlURL=file:///pathToMyWSDL/file.wsdl&dataFormat=MESSAGE"
This messaging endpoint is the proxy service entry point.
- Create a cMessagingEndpoint, set the URI to your REST Web service :
"cxf://http://RESTHostName:RestPortt/RestWebserviceEndpoint?dataFormat=MESSAGE"

Connect the two cMessagingEndpoint and run.

Bahaaldine

Re: [resolved] REST service proxy route

Anonymous — Wed, 24 Aug 2011 02:37:38 GMT

@ bahaaldine: if using TESB 4.2.0, maybe a patch about CXF is needed to make the Route work. And in the next release of TESB, Route with CXF will run without any workaround.

Re: [resolved] REST service proxy route

Anonymous — Wed, 24 Aug 2011 15:01:29 GMT

Hi bahaaldine,
should I implement a service and write a WSDL for my REST service which I will expose on ESB or? I don't understand.
I tried with this configuration:
First cMessagingEndpoint:
"cxf://http://localhost:18081/applicationName/service/serviceName/process?dataFormat=MESSAGE"
Second cMessagingEndpoint:
"cxf://http://mashina:8080/applicationName/service/serviceName/process?dataFormat=MESSAGE"
The error I get is: "Failed to create route cMessagingEndpoint_1: Route[[From[cxf://http://localhost:18081/alfresco/service/ab... because of Failed to resolve endpoint: cxf://http://localhost:18081/alfresco/service/abitecm/process?dataFormat=MESSAGE due to: No component found with scheme: cxf" (Error within Talend Route Builder when I press Run)
Then I have tried without "cxf" prefix in uri. No errors.
When I invoke the endpoint: http://localhost:18081/applicationName/service/serviceName/process/{parameter1}/doctypes/{parameter2}
nothing happens (Firefox REST client)
KarafHostName: localhost
KarafPort: 18081
I deployed the route on Talend ESB and invoked again the endpoint. The error I get then is:
"

<META http-equiv="Content-Type" content="text/html;charset=ISO-8859-1" />
<TITLE>Error 404 Not Found</TITLE>

HTTP ERROR: 404

Problem accessing /applicationName/service/serviceName/process/28/doctypes/doctypeName. Reason:

    Not Found

<SMALL>Powered by Jetty://</SMALL>"
I do not know if I have well explained what I need?!

Re: [resolved] REST service proxy route

Anonymous — Thu, 25 Aug 2011 11:07:21 GMT

Hi,
I want to have this functionality for the REST service using Talend ESB:
http://www.mulesoft.org/web-service-proxy

Re: [resolved] REST service proxy route

Anonymous — Thu, 25 Aug 2011 13:45:47 GMT

Hi,
can anyone help me to solve this problem? I have a deadline next Monday.
I have tried various solutions like:
http://camel.apache.org/cxfrs.html
http://camel.apache.org/http.html
but without result 😞

Re: [resolved] REST service proxy route

Anonymous — Thu, 25 Aug 2011 14:02:25 GMT

Hi,
I have a another question..
If I have a job deployed on Talend ESB and the job calls a REST service using tREST or tHttpRequest component with 2 parameters (http://mashina:8080/applicationName/service/serviceName/process/{parameter1}/doctypes/{parameter2} - REST service endpoint), how can I invoke this job remotely from another application and read (or store) the response?
The KarafHostName is: localhost and KarafPort is: 18081
Thanks in advance!

Re: [resolved] REST service proxy route

Anonymous — Fri, 26 Aug 2011 17:40:08 GMT

Hi ipercinlic, i'm also new to talend esb, camel, ... but i think you can solve this error "The error I get is: "Failed to create route cMessagingEndpoint_1: Route[[From[cxf://http://localhost:18081/alfresco/service/ab... because of Failed to resolve endpoint: cxf://http://localhost:18081/alfresco/service/abitecm/process?dataFormat=MESSAGE due to: No component found with scheme: cxf" (Error within Talend Route Builder when I press Run)" if you set the Camel component dependency to 'cxf' of the cMessagingEndpoint_1 component (Look under "Advenced settings" of the component cMessagingEndpoint_1). What i don't understand is that CXF has a special prefix for REST CXF Web Services (CXFRS, http://camel.apache.org/components.html) and how to import that prefix. May be you can import the prefix CXFRS when you import the corresponding .jar (Look under "Advenced settings" of the component cMessagingEndpoint_1 + "Use a custom component").
If i then try to run the example directly in the studio i get some "NoClassDefFoundError" errors. I believe that some camel / spring jars are missing in the studio runtime environment. But you can export the route and try to "import" these route in the talend esb (karaf). Unfortunately is in my example no proxy ws under the url http://KarafHostName:KarafPort/webserviceEndpoint reachable but may be you find a solution for this problem or it helps you to go further.
Good Luck!!!

Re: [resolved] REST service proxy route

Anonymous — Mon, 29 Aug 2011 10:55:09 GMT

Hi frankEichholz, I tried your suggestion. When I run the route in the Talend ESB console, I get the error: "karaf@tesb> Failed to create Producer for endpoint: Endpoint. Reason: org.apache.camel.RuntimeCamelException: java.lang.NullPointerException".
I have a simple requirement - just want to expose my REST service on Talend ESB and I can't believe that there is no (simple) way to do it?! Or?
Talend Team?
Can anybody answer my question how can I run (call) a talend Job deployed on Talend ESB (as OSGi bundle for ESB) from another application?
Thanks in advance!

Re: [resolved] REST service proxy route

Anonymous — Mon, 29 Aug 2011 15:25:32 GMT

Hi ipercinlic, me again.
I believe that you have to set some more cxf options.
bahaaldine mentioned that you have to set the wsdlURL option too.
"cxf://http://KarafHostName:KarafPort/webserviceEndpoint?wsdlURL=file:///pathToMyWSDL/file.wsdl&dataFormat=MESSAGE"
In my example (that currently does not work) i set the following options. I think it mainly depends on your wsdl.
"cxf://http://localhost:8080/webservices/TransportOrderService?wsdlURL=file:///C:/Temp/talend/TransportOrderService.wsdl&dataFormat=MESSAGE&portName={http://salt-solutions.de/logbase/transportorder/}TransportOrderServiceSoap"
Did you tried the "CXFRS" prefix and imported the corresponding jar ( http://camel.apache.org/cxfrs.html)?
Sorry that i can not help you more but as i said i'm new to the technology.

Re: [resolved] REST service proxy route

Anonymous — Tue, 30 Aug 2011 18:15:15 GMT

hi,
For the Proxy Web server, can you try the following in ESB Studio
Create the HTTP listener for http://hostnameA:8080/web_app
1. Create a MessageEndpoint to listen for your HTTP requests (ProxyService)
2. In the Component panel, "Basic Settings" set the URL to "jetty:http://hostnameA:8080/web_app"
3. In the "Advanced Settings" click the + to add a dependency. Select 'jetty'
Forward request to http://hostnameB:8085/web_app (InternalService)
1. Create a MessageEndpoint
2. In the Component panel, under "Basic Settings" set the URL to http://hostnameB:8085/web_app
Create Proxy Service (Proxify)
You need to connect the inbound message and proxy the request to the service on hostnameB, _and_ connect the response messages on the outbound
1. Add a cProcessor
2. In Basic Settings of the Component add the following
//Print Request headers
System.out.println("> " + exchange.getIn().getHeaders());
//Create response message
exchange.getOut();

The first part is just for logging the request, so you can see something happening. The second line though is what connects the responses.

Certainly this works for me.
Hope this helps,
Ciaran

Re: [resolved] REST service proxy route

Anonymous — Wed, 31 Aug 2011 14:07:54 GMT

Hi cdynes,
I tried your proposed solution, but when I invoke the REST service deployed on hostnameB I didn't get the response.
The expected response of my REST service is an url (in string format).
I tried with this configuration:
First cMessageEndpoint (HTTP listener) url: (Proxy service) "jetty:http://mashina:8085/alfresco/service/service_name/process/28/doctypes/banka.odobravanjeKredita.gotovinski.kreditniZahtjev"
Second cMessageEndpoint url: (Real web service)
"http://mashina:8080/alfresco/service/service_name/process/28/doctypes/banka.odobravanjeKredita.gotovinski.kreditniZahtjev?throwExceptionOnFailure=false"
The response that I get is: "Message: "
Look for the screenshots.
I checked the servers access logger and the request that commes to my service is fine:
"GET /alfresco/service/service_name/process/28/doctypes/banka.odobravanjeKredita.gotovinski.kreditniZahtjev HTTP/1.1" 200 119
I am using Jboss as an application server.

Re: [resolved] REST service proxy route

Anonymous — Fri, 02 Sep 2011 14:36:55 GMT

Hi,
You shouldn't need the second cProcessor.
http://www.screencast.com/users/CiaranDynes/folders/Talend/media/85e24eb4-356e-46b0-a34d-26673bc7affb

Ciaran

Re: [resolved] REST service proxy route

Anonymous — Mon, 05 Sep 2011 10:02:36 GMT

Hi cdynes, when I use the cSetHeader component to set the "Authorization" header (because my internal service needs an authentication), the proxy route works fine. In my test route, the cSetHeader component is configured with these parameters:
Header: "Authorization"
Language: Constant
Expression: "Basic value for username and password (fixed)"
How should I configure the cSetHeader component or the entire route to use the authorization parameters which are coming with a request?
I use the Firefox REST Client to test my route.
Thanks a lot for your help!

Re: [resolved] REST service proxy route

Anonymous — Mon, 05 Sep 2011 13:33:34 GMT

Hi,
Good to hear!
Not sure I understand the setHeader() question. Is it that you need to add a new header for the internal REST service?

Ciaran
http://camel.apache.org/http.html

Re: [resolved] REST service proxy route

Anonymous — Mon, 05 Sep 2011 14:17:16 GMT

Hi,
Because my REST Internal service needs the authentication, when I invoke the Proxy service I need also to send the authentication parameters (username, password). Using the Firefox REST client plugin, I've set the header "Authorization" and the corresponding value for username and password (Authorization=Basic someValue). When I want to invoke the service, I always get the dialog to enter the username and password although I have the "Authorization" header set.
But, when I use the cSetHeader component with these parameters:
Header: "Authorization"
Language: Constant
Expression: "Basic value for username and password (fixed)"
the service works fine.
I don't want to use fixed authentication parameters but parameters which I will send when I invoke the Proxy service. The question is - how can I proxy my authentication parameters to my REST internal service?