Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

services high availibility on ESB runtime architecture (virtual serveur and service locator)

Hi,

I have installed the 7.1.1 Talend Data services version in 2 Talend runtime .

I create a demo services with no specific endpoint  and service locator and name space used in the tRestRequest component.

I deploy the service in cluster mode with   virtual server.

I see the service in the 2 serveurs with 2 different endpoints IP1:8040/services/customers and IP2:8040/services/customers.

How can I configure the HA to call the service:

- use name space

- setup / fixed the endpoint IP0683p000009MAB6.pngort but how can call them on my network architecture 

- other solution

 

Regards

 

Labels (3)
3 Replies
Anonymous
Not applicable
Author

I
Somebody can to help me with some way of search ?
Regards
Anonymous
Not applicable
Author

Helloo jdelodel,

 

on the server side you did all things right (reading through the things you did). From your description it looks like you have two instances of your service, they both register to the Service Locator and they both are active. 

Means it looks like the missing piece is the client side in your question. For pure ESB clients you can use tRESTClient (or cREST) with the Service Locator option enabled and using the same 'logical' service name as you defined on the provider side. By this, the clients will automatically find the Service and all available endpoints. If one provider stops the client will automatically switch to the other one (without a failure on the client side) and if you bring more provider up in future the clients will automatically make use out of them.

 

That said, non-ESB Clients (plain REST Clients) would still need a load balancer in front of your providers where you can either use a Route with cLoadBalancer or a route with a cREST (acting as provider) connected to a cREST (acting as a SL enabled client) or you go with a 3rd party load balancer (software or hardware).

 

HTH,

Dietmar

Anonymous
Not applicable
Author

Hi Dietmar,

 

Thanks for your answer. It is very helpfull and complete my mindset.
About using Service locator with SOAP services, how can I implement them.

 

Regards

Jérémie DELOBEL