Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Hi everyone,

in the last post of this series, we talked about logging in at XS advanced using the xs cli. This time, we're going to start exploring the system and the first task is to get a system overview by means of the xs cli command system-info. Please note, that you need to have XS advanced administrator permissions to be allowed to execute this command:

$ xs system-info

Getting system infrastructure information...

Several sections about the components of an XS advanced landscape are displayed. We will go through each individual section individually:

Execution Agents

The first section displays information about the execution agents that are currently connected to the XS Controller:

Execution agents:
created at Dec 14, 2017 9:10:23 AM
port range 50000-50499
os.arch amd64 Linux
java.vendor SAP AG
java.version 1.8.0_144
os.version 3.12.62-60.62-default 64
version v1.0.72

created at Dec 14, 2017 9:11:24 AM
port range 50000-50499
os.arch amd64 Linux
java.vendor SAP AG
java.version 1.8.0_144
os.version 3.12.62-60.62-default 64
version v1.0.72

In this example, 2 execution agents on "" and "" are connected to schedule application instances on. For each execution agent, additional information is displayed like:

  • The host on which the execution agent runs on

  • The date at which the execution agent was started

  • The port range the execution agent uses for applications on it's host

  • The platform and version of the SAP JVM that is running the execution agent

  • The version of the execution agent

Note: For application scale-out, you can add additional execution agents to a SAP HANA system by adding additional HANA hosts with role "xs_worker", see also System Concepts for XS Advanced Runtime Installations in the SAP HANA Installation Guide.


Next up is information about the XS Controller, for example:

Controller server version information:
name XS Controller
build v1.0.72
api version 1
software version
content version
installation state READY
description SAP XS Runtime on premise
controller endpoint
authorization endpoint
accept encoding gzip, x-gzip
usage apps: 8, routes: 8, services: 16
instances: 0 starting, 6 running, 3 stopped, 1 crashed, 0 timed out
database type HANA_MULTI
database info HDB

In detail, the following information is displayed for the XS Controller:

  • name: The name of the component

  • support: The URL to approach in support cases

  • build: The version of the XS Controller

  • api version: The version of the REST interface provided by the XS Controller

  • software version: The installed version of the XS advanced system components

  • content version: The installed version of the XS Advanced core applications package (e.g. deploy-service and product-installer). In a sane installation, both numbers must match.

  • installation state:

    • READY in case XS advanced is installed correctly

    • UPDATE_PENDING in case the installation is not yet completed

  • description: A description of the component

  • controller endpoint: The REST endpoint for requests to the XS Controller API (also called API URL)

  • authorization endpoint: The REST endpoint for authorization requests

  • usage: Information about the number of applications and application instances

  • database type: The type of the underlying SAP HANA database:

    • HANA_MULTI: SAP HANA multiple database container system

    • HANA_SINGLE: SAP HANA single database container system

  • database info: The version of the underlying SAP HANA database

Service URLs

Applications may maintain a service URL during installation to publish their application endpoint:

Registered service URLs:

We're going to cover maintaining service urls in one of the upcoming blog posts.

Application Overview

The next section provides statistics about the deployed applications in the system:

Deployed applications: 8
Running applications: 6
Stopped applications: 2

Organizations And Spaces

The last section provides statistics about the distribution of applications across organizations and spaces:

Organizations and spaces:
Organization Space Number of apps User
|- PROD 0 abcxsa
|- SAP 8 sapabcxsa

In this example, the organization "myorg" contains two spaces named "PROD" and "SAP". In addition to the number of deploy application in each space, the operating system user as which application instances are started is displayed.


Using the command xs system-info, you can get an overview about the connected execution agents, the deployed applications, the organization and space structure. In the next blog-post, we're going to describe how to navigate through organizations and spaces.