May 2023 changes to ServiceConfiguration.xml

[bryce_leinan]

In the May 2023 version of Qlik Replicate, there is a note in the docs that ServiceConfiguration.xml is no longer supported. Our Replicate and UI services are on the same server, however, for security reasons, our UI access sits behind a shared load balancer.  I currently have these entries in our ServiceConfiguration.XML file:

ServiceConfiguration allowUnsafeProtocols="false" url="https://physicalservername:443/attunityreplicate;http://physicalservername:80/attunityreplicate;http..."/>

How do I make sure the https://loadbalancedurl:443/attunityreplicate shows up in the system?  I was reading through the repuictl commands, and was not sure how to add this... 

Thanks

[Steve_Nguyen]

@bryce_leinan 

your current serviceconfiguration

ServiceConfiguration allowUnsafeProtocols="false" url="https://physicalservername:443/attunityreplicate;http://physicalservername:80/attunityreplicate;http..."/>

this should have not works , as you have two https try on 443.

if your  UI access sits behind a shared load balancer ,, then for the 2023.5 kit you just need to run

repuictl configuration set --address loadbanacedurl

if you are on HA then 

https://help.qlik.com/en-US/replicate/May2023/Content/Replicate/Main/Clusters/enable_diff_console_co...

repuictl configuration set --address primary-machine-name:primary-machine-address failover-machine-name:failover-machine-address

[bryce_leinan]

@Steve_Nguyen , we have two HTTPS entries so we can connect to Replicate from the physical server if needed, and one if we connect to the console through the loadbalanced URL. The prefered method is connecting from the loadbalanced URL. 

Thanks,

Bryce

[Steve_Nguyen]

@bryce_leinan ,, it seems that the correct method is to set the repuictl to the loadbalanced URL,

id you have issue doing that ?

[bryce_leinan]

Steve... I don't understand your reply... so, I am guessing you're saying I would take the non-loadbalanced URL out?

[Steve_Nguyen]

@bryce_leinan , the new setting to configure the URL is still the same as with the serviceconfiguration.xml

it is now just in the sqlite file . 

so you should set both the https and http for the loadbalancer URL.

[bryce_leinan]

I'll do that, but my question about accessing from localhost / local machine still isn't answered.  Do I need to put that in at all, or will it work without?  It's important for our entity to have both working. 

[Steve_Nguyen · Accepted solution]

@bryce_leinan in a Cluster Replicate setup, the URL should always pointing to the client access point,..

so that the it point back to which ever nodes is active. 

---

if you are on locally / your url should till should be the client access point / load balancer url ,, it this does not work from the local server, then you have some DNS issue.

[bryce_leinan]

It's not a DNS issue, it is how our environment is setup. Without delving into too many details, we need both URLs to work. I take it there's absolutely no way to make it work the way it is now?

[Steve_Nguyen · Accepted solution]

@bryce_leinan it do not see a way to configure the same as the old serviceconfiguration , 

look to be a feature request.