Is it possible to change the url to enter QlikView AccessPoint?

[qwebnm]

When entering the current AccessPoint browser, access http://<Server IP>/qlikview/index.htm.

Can I change this url?

If there is a way, please tell me.

thank you.

[Chip_Matejowsky]

@qwebnm,

What is it that you want to change the URL to?

The default URL is typically http://<servername>/qlikview.   If you are experiencing issues using this and can only use the IP address of the QlikView Server, then you are most likely experiencing DNS issues that your company's internal server/Windows team would need to address.

Best Regards

[qwebnm]

Change the URL to http://<servername> followed by /qlikview to /arbitrarily or
Can I change /index.htm to /index.html or /arbitrarily?

Please answer me. Thank you

[Chip_Matejowsky · Accepted solution]

@qwebnm,

See Qlik Support article How to Change the QlikView AccessPoint URL.

Best Regards

[qwebnm]

Is it possible to change index.htm to index.html? 

Please answer me. Thank you

[Dan-Kenobi · Accepted solution]

If you are using QlikView Web Server

- By default, your Access Point points to http://$(server_name)/qlikview 

- This mapping is in the QMC. To allow a link to AccessPoint in the following fashion http://$(server_name)/ just add an empty entry in the WebServer/Web setting in the QMC, like so:

This should get you where you want to be.

Same trick could be used if you wanted to have something like http://$(server_name)/optimus_prime , by adding a new entry with the value os optimus_prime, pointing to c:\Program Files\QlikView\Web

Now, to change the index.htm to index.html, this is a lot easier.

First, go into the folder on the comment above. You should be able to see all of the main files for the AccessPoint Front-End

Make a duplicate of the file you want to rename, and just rename de dup. You should end up with two copies of the same file:

Now you should be able to navigate to http://$(server_name)/index.html and this should get you the AccessPoint you expect to see.

There ARE other ways to do it with different trade-offs, as well as differences if you're doing AccessPoint over IIS.

But this should give you the basics.