Management Service API with FQDN

[peterwh]

Hello,

in our company there was a change, due to security reasons, that every computer has to be addressed by the FQDN (so with the domain name).

Now I have the problem, that I can't connect to the Management API anymore, because it's only available via hostname (without the domain name). How can I change this? I searched in the community, I tried changing the Config.xml from the QVMS, but I only get the hostname.

This is what I get in QMC (-> Setup -> Management Service -> Summary)

To connect to the API of this Management Service use: https://qlikxxx:4799/QMS/Service

But I need this:

To connect to the API of this Management Service use: https://qlikxxx.domain.com:4799/QMS/Service

Did anyone get this done?

Kind regards

Peter Hübschen

[Maria_Halley]

Hi @peterwh 

Take a look at the below articles, I think you have to edit the connection outside of Qlik.

https://community.qlik.com/t5/Official-Support-Articles/QlikView-Connecting-to-QMS-API-using-HTTPS/t...

https://community.qlik.com/t5/Official-Support-Articles/QlikView-Connect-to-QMS-API-with-Visual-Stud...

[peterwh]

Hello @Maria_Halley , 

my problem description wasn't complete. Sorry for that.

I have a powershell script which I found in the community (https://community.qlik.com/t5/Official-Support-Articles/QlikView-Call-QMS-API-with-PowerShell/ta-p/1...).

I've made my changes and at one point (I don't know where), the .wsdl-file should be loaded and the script tries to read it from "http://qlikxxx:4799/QMS/Service..." and not the configured $url. Because of the lack of the domain, the address can not be called.

It is the case if I use an alias for the server for $url (maybe "qliktest"), the script tries to contact qlikxxx (the original hostname). 

Because the hostname-address is visible in the qmc, I want to change it to a FQDN. I hope that could resolve my problem.

The same problem was described there in 2021; unfortunately without any answer.

https://community.qlik.com/t5/Integration-Extension-APIs/QMS-Backend-API-Host-Change/td-p/1871328

Kind regards
Peter

[marcus_sommer]

What happens if you don't used the name else the IP of the server?

[peterwh]

Hello @marcus_sommer, 

sorry for the delayed answer.

I've changed the script to use the ip-address, but it isn't working also. I get the following error message (first the original in german, than translated by me):

New-WebServiceProxy : Das Dokument wurde erkannt, konnte jedoch nicht verarbeitet werden.
- Das WSDL-Dokument enthält Links, die nicht aufgelöst werden konnten.
- Fehler beim Downloaden von 'http://qlikxxx:4799/QMS/Service?wsdl=wsdl0'.
- Der Remotename konnte nicht aufgelöst werden: 'qlikxxx'

New-WebServiceProxy : The document was recognized, but couldn't be processed.
- The WSDL-document contains links, that couldn't be resolved
- Error at the download from 'http://qlikxxx:4799/QMS/Service?wsdl=wsdl0'.
- The remotename (remote hostname(?)) couldn't be resolved: 'qlikxxx'

Even if I used the IP-address for "$url" in "$service = New-WebServiceProxy -Uri $url -Namespace QlikViewServer -UseDefaultCredential" it uses the machine name to get the wsdl-file.

If I copy the "http://qlikxxx:4799/QMS/Service?wsdl=wsdl0" into any browser I get the message that it couldn't connect to the specified server. If i change the address to "http://qlikxxx.foodomain.com:4799/QMS/Service?wsdl=wsdl0" I get the content of the wsdl-"file".

So where is the setting that QlikView gives the FQDN back?

Kind regards

Peter

[marcus_sommer]

I don't know and I'm not sure that there is really any setting for a FQDN respectively an implemented logic to combine the server-name and the domain - which might mean that each server-name entry in each confgig might be replaced with the FQDN.

Before going such way make sure that you have complete backup of entire services-configurations (all services has to be stopped) and ideally an image of the server because manipulating the settings may go wrong and resulting in a corrupt system.

[peterwh]

We've changed every entry in our QlikView-system to FQDN some years ago, because our IT department said that they will only allow calls with FQDN in the future. So we prepared for this situation.

Only the management service doesn't have a FQDN, because we didn't find the correct setting to modify this. Even in our "config.xml" for the management service we put the FQDNs.

Since we have a test site it is no problem if I would break our test site.

Kind regards

Peter

[marcus_sommer · Accepted solution]

Beside the program-data there are also settings within install-data, for example in:

YourInstallFolder\QlikView_Server\Management Service\QVManagementService.exe.config

and there is a setting with the comment of:

<!-- An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name. If the name is unknown, the value is the zero-length string. If left empty, it defaults to current machine name -->

I think it's worth to play with.

[peterwh]

Hello @marcus_sommer,

that did the trick. Now I can successfully execute the powershell script. Thank you very much.

I had never looked at this parameter, because it is in the SNMP-section and it is called "SNMPsysName".

In QMC there is still the machine name only, but if the script runs, this is ok.

Kind regards

Peter