topic Re: How to Map the Endpoint in Talend Studio

How to Map the Endpoint

user19 — Fri, 15 Nov 2024 23:04:06 GMT

I am trying to create a Rest route in Talen ESB open studio. I have an endpoint which has multiple methods inside.I access my API from Metadata. how can I reroute each endpoint according to its method. lets say endpoint is http://Example/api/version/Method/operation. it has four methods Rawdata, balancing, customdata and final data. all these methods has multiple operations. http://Example/api/version/Rawdata/getRawdata

http://Example/api/version/Rawdata/getdatafromfields

http://Example/api/version/balancing/getfiltereddata

How can I tell talend that when I call Rawdata in Soapui send this endpoint. which components i can use or can Java code can do it? Any help would be appreciated.

Re: How to Map the Endpoint

Anonymous — Fri, 01 Apr 2022 14:02:50 GMT

Sorry about the delay in getting back to you here. I had to play around to figure this out. You may need to calculate your endpoint (in vs out) using some code in the cProcessor, but this is how you can switch them in the cREST_2.

Use the Relative Path to set the endpoint using a header. The way I tested this was as follows...

My cREST_1 has 2 methods. They are "/employees" and "/employee/{number}". These methods are included in the "CamelHttpPath" header of the Exchange. When the "/employees" method is called, that is set to the header, when the "/employee/{number}" is called, that is set to the header. This is where you may need to manipulate yours if your input methods are not the same as the methods you are wanting to call.
Then in my cREST_2 component, I simply set the Relative Path value to be simple("${header.CamelHttpPath}")

Give that a go and see what you think.

Re: How to Map the Endpoint

user19 — Mon, 04 Apr 2022 07:27:06 GMT

@Richard Hall how you added these methods in "CamelHttpPath"?

Re: How to Map the Endpoint

user19 — Mon, 04 Apr 2022 08:30:47 GMT

I was trying to get the query parameter from the header.

Re: How to Map the Endpoint

Anonymous — Mon, 04 Apr 2022 09:49:23 GMT

The CamelHttpPath header is automatically set with the path you are calling which you've specified for the method. In the code above you appear to be looking for the CamelHttpQuery header.

Re: How to Map the Endpoint

user19 — Mon, 04 Apr 2022 11:18:00 GMT

@rhall it is throwing HTTP/1.1404 Not found

Probably it can't identify the method. can you please guide me how can to calculate endpoint (in vs out) using some code in the cProcessor. I mean any example?

Re: How to Map the Endpoint

Anonymous — Mon, 04 Apr 2022 12:44:20 GMT

I made sure that my methods were structured in exactly the same way as the methods of the API I am calling (just to keep it simple). So my methods look like this in my config......

The code in my cProcessor is just this.....

System.out.println(exchange.getIn().getHeader("CamelHttpPath"));

I am just using it to check the value of the header.

It produces the following. See that they match the methods I set up (apart from there being an actual number instead of the "{number}"....

/employees

/employee/1

/employee/2

In your cProcessor, you will need to get this value, compute the String you need for the API you care calling and set it to a new header value. Then use that header in the Relative Path of the cREST_2, as I showed the post above.

Re: How to Map the Endpoint

user19 — Tue, 05 Apr 2022 08:27:56 GMT

@Richard Hall I am able to deploy the route and call the methods. I have swagger specification in this route. I can see list of operations in my http://localhost:9001/services/api/swagger.json if I try to get some data then I get response code 404 no content. Since I used simple("${header.CamelHttpPath}") for my route and now swagger is not getting any parameters. Is there any way to pass the parameters to swagger?

Re: How to Map the Endpoint

Anonymous — Tue, 05 Apr 2022 10:52:26 GMT

If you're talking about query parameters (parameters provided in the URL with ? and &, etc), you can see these in the CamelHttpQuery header. If you need to use these, I suspect that there will be some String manipulation required.

Re: How to Map the Endpoint

user19 — Tue, 05 Apr 2022 11:12:05 GMT

@Richard Hall thank you for the response. yes I am talking about query parameter. but now where can I specify query parameter for swagger? in my CREST2 in Relative path I am already using simple("${header.CamelHttpPath}" + context.relativePath)

Re: How to Map the Endpoint

user19 — Tue, 05 Apr 2022 11:59:37 GMT

@Richard Hall or if I uncheck the box

still there is swagger in services list

how can disable it?

Re: How to Map the Endpoint

Anonymous — Tue, 05 Apr 2022 13:36:43 GMT

I'm afraid you are not giving enough information. Why would you want to disable exposing the Swagger specification? It won't change how the API is called. In order to know how to call your API, we would need to know the specification of your API.

Re: How to Map the Endpoint

user19 — Wed, 06 Apr 2022 06:56:52 GMT

I can call the API using the route but I can't call the API using swagger exposed by talend, so I think it's better to Remove Swagger because API will work fine, but even I can't remove it after unchecking the box.

Re: How to Map the Endpoint

Anonymous — Wed, 06 Apr 2022 14:10:26 GMT

If that is not working, you will need to raise a Support case.

Re: How to Map the Endpoint

user19 — Wed, 13 Apr 2022 12:14:04 GMT

@Richard Hall I want to make the Resource case insensitive. by using simple("${header.CamelHttpPath}") it iscase sensitive. s I tried

String Path = (String)exchange.getIn().getHeader("HTTP_PATH");

String LCPath = Path.toLowerCase();

String apiParams = (String)exchange.getIn().getHeader("QUERY_STRING");

String LCapiParams = apiParams.toLowerCase();

context.relativePath = LCPath.concat(LCapiParams);

but it is returning null.

I also tried StringHandling.DOWNCASE(("${header.CamelHttpPath}" )+ context.RelativePath) but nothing works.

Do you have any dea how can we convert it into lowercase so it canbe case Insensitive?

Re: How to Map the Endpoint

Anonymous — Wed, 13 Apr 2022 14:38:37 GMT

You need to find out precisely where the null is coming from. Between each line of code add a System.out.println() to show the value that has been set. This should give you some clues as to where the issue is.

Also, where is context.relativePath being used? Context variables in Routes behave different to how they behave in Jobs. Once an endpoint has been initialised, you cannot dynamically change configurations. So this could be a cause of this.