How do I get the URL passed in the tRESTClient

[Anonymous]

Hi Talend Community,

I have a rest service using tRESTClient that send parameters (header and body) via a REST GET call.

How can I see the URL being executed in its total string format.

tLogRow only shows the result set returned

Thanks

[Anonymous]

I don't have an example to hand, but I can talk you through exactly what you have to do...
1) Create a new context variable called "URL". Do this in the "Contexts" tab below your job.
2) Assign the URL context variable the url that you currently have in your tRestClient. Replace the URL there with the new context variable.
3) In your tMap click on the output table (on the right) so that it turns yellow. At the bottom of the screen you will see the schema. Click the green + (at the bottom of the page on the right) and add a String column called "URL" (or anything you think is appropriate).
4) You will see this new column appears in the output table (which turned yellow). Add.....

context.URL

... to the column called URL. Do not use quotes.

Now when you run your job you should see the URL column appear in the tLogRow with the other output columns.

[Anonymous]

Thank you got the URI, 

Is there a way to see the headers also?

[Anonymous]

Are these dynamic headers or are you hardcoding them?

[Anonymous]

I have defined the items as below, but still do not get the URI

tMap

context:

[Anonymous]

I explained how to do this in my other post. Follow the instructions step by step. Go to the section where I talk about creating a column in the yellow output table

[Anonymous]

Hard coded headers,

But I think I have a problem in translation:

I have a Authorization tag that needs to contain: Token token="729f70f8-67dd-86b9-0296-23d3a387a19e"

I have it configured as such: 

I need to see the complete URI output to ensure Talend is parsing the parameters correctly and sending the correct URI 

[Anonymous]

Your token is almost certainly formatted wrong and this is a different question. It is not a great idea to ask further questions on the same thread because it leads to useful answers being lost.

Raise another question about the headers and include the specification you are working from. We will need to see the requirements of the web service you are using. Trying to solve this question without seeing this will be like literally searching for a needle in a haystack..... in a collection of fields in a random country.  

[Anonymous]

will do thanks

[Anonymous]

I have create as I understood your explanation but still have no output