DevOps and System Administration Blogs
Explore DevOps and system administration blog posts. Stay current with best practices, tools, and insights into efficient IT management strategies.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

Note: This is mainly applicable for Native HANA scenarios with XSA.

After installing SAP HANA 2.x or upgrading from HANA 1.x to 2.x especially after the introduction of XS Advanced, SAP HANA generates multiple URLs for different applications within XSA. In HANA as you are aware of, there are 2 modes of routing available.

  1. Port based routing

  2. Hostname based routing

When you are using port-based routing, the application URLs will be pointing to different port numbers.

When you are using hostname-based routing, the application URLs will be pointing to same port number, but the domain name changes based on the application.

You will choose either one of the above options while installing SAP HANA 2.x with XSA.

Since the URLs are generated based on the cloud default domain name, the URL will have the following challenges:

  1. The URLs will be lengthy

  2. It is complex or near to impossible to remember the entire URL for both technical & business users (unless you bookmark your URLs)

  3. Sometimes, if you wanted to share it with business users are 3rd party users, they may find it difficult to open the URL

  4. It would be highly impossible to make it as an external URL and not meeting the standards, as it might expose the internal domain names which is a security threat.

In this scenario, customer wants to use the URL with their domain name, instead of the default cloud domain URL. This same is application to the On-prem URLs as well.

In case if you are using HANA clusters it is more difficult to point the URLs. With SAP HANA in System Replication mode ( will have 2 HANA servers setup as primary and secondary, will be accessed by a common URL for the end users).

In general, you will point the IP of the server to the domain in Cloud DNS/Route53 in the cloud console. Hence the HANA URLs will be generated as:


You may not be able to rename the server or change it in /etc/hosts.

HANA server picks up the domain name from the above cloud DNS settings of the cloud console.


You may point the cloud default dnsname to the domain name or CNAME of the customer.

Below are the steps:

  1. Install and configure SAP HANA with the cloud default Hostname

  2. System should be ready to setup SSL

  3. Copy all the possible URLs generated by the HANA server by using the command:

xs apps

It will list all the app urls. ( you may get around 35 URLs)

  1. If it is in a cluster environment, break the sap hana cluster and do it in each individual system.

  2. Use the Common name ( for ex: if & , create a common name and map the common name to all the URLs

  3. In general, the domain names are configured and mapped by the windows domain controller team. Take the help of this team to map all the 35 URLs to the common name as mentioned in step 6.

  4. Ensure that the cname mapping to default domainname in command prompt.

  5. Set that commonname ( as the default domain name in xscontroller.ini

  6. XSA restart - restart and restage all the apps

  7. Restart the HANA DB server

  8. Execute the following commands:

xs version - to check the version

xs apps - list the xs apps

xs env xsa-cockpit - check the environment variables for xsa-cockpit

xs services - list all the xs services

xs unbind-service xsa-cockpit-uaa xsa-cockpit - unbing the xsa service

xs us xsa-cockpit xsa-cockpit-uaa –

xs bs --help

xs bs xsa-cockpit xsa-cockpit-uaa

xs restart xsa-cockpit

xs env


xs rebind-services --help

xs rebind-services

xsuaa -f - unbind and rebind the xs services forcefully


You should be able to logon with xs-admin-login using the XSA_ADMIN user. When executing the xs apps command, it should display all the URLs in the above-mentioned format.


Please provide your comments and feedback to improve this content.
Labels in this area
Top kudoed authors