One Star

declared endpoint is surcharged by default endpoint "8040/services"

Hi
I use TOS ESB 5.1.0.
1 - I build a service with the studio, and I declare an endpoint : "http://localhost:8181/myWebService"
2 - Then, I build a simple job : tESBProviderRequest - tXMLMap - tESBProviderResponse
3 - When I export the service in the Runtime Karaf, the endpoint becomes : "http://localhost:8040/services/myWebService".
(Executed with the studio, the endpoint do not change !)
The problem is that I need to expose all the services with different endpoints and ports.
So, is it possible for a service to keep the endpoint declared in the studio ??
Thanks for your help.
Greg
7 REPLIES
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

Is it possible to change the port of an exposed service in Karaf ??
Must I use the default port ?
Help !
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

Hi Greg,
when you deploy your job service to the runtime, web service endpoint will use already deployed bundles for CXF and Jetty (by default set to http://localhost:8040/services). So your services will be distinguished by their endpoint URI (here it's the service name).
But - do you really need to have different ports? (security can be achieved another way) You could use different ports by using Camel routes (mediation routes) specifying absolute URI on cCXF endpoint (e.g. jetty://http://localhost:8181/myService), but to make your life easier I'd advice that you try to fit into default 8040 port and do not fight against the tool.
Axecuting WS in studio I consider (it's my assumption) only for testing purposes and another port is defined not to collide with an eventually running runtime.
Good luck
Gabriel
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

Thanks for your response.
This confirms my view but that did not facilitate the task. This is indeed to replace existing services whose endpoints are difficult to modify.
I'll probably pourvuivre using mediation.
Greg
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

Hi,
this is a simple route serving as a proxy to another port, simple end fast
from : "jetty:http://localhost:9090/endpoint1?bridgeEndpoint=true"
to: "http://localhost:8040/services/ws2"
Carpe diem
Gabriel
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

additional info :
> Is it possible to change the port of an exposed service in Karaf ??
indeed, theres a file etc/org.ops4j.pax.web.cfg where you can change the Karaf jetty default port
I like it where it is, because you can put a tomcat or Apache http in front of the ESB and have more fine-grained security there
Gabriel
Community Manager

Re: declared endpoint is surcharged by default endpoint "8040/services"

Hi
If you really want to change the default port of endpoint, to do so:
1. Go to <Talend runtime install dir>\container\scripts, open the configureC0.sh and edit the following properties:
HTTP_Port=8040
to
HTTP_Port=other port
2. Save the file.
3. Launch talend runtime (Karaf), and execute the following command to use the modification on configureC0.sh.
karaf>source ./scripts/configureC0.sh
Best regards
Shong
----------------------------------------------------------
Talend | Data Agility for Modern Business
One Star

Re: declared endpoint is surcharged by default endpoint "8040/services"

On versions prior to 5.0 Talend BSE, it was possible to deploy a web service on any port, and on several at once. Too bad it can no longer be.
I will use the work around of a mediation service to expose the data integration made.
Thank you very much for your help.
Cordially.