Starting the Global Listener and/or Installation-Specific X Servers 
On Microsoft Windows, the SAP MaxDB installation program registers the global listener and all X servers as services, sets their Startup Type to Automatic, and starts them. From then on, they are automatically started at system startup. You do not have to start them manually.
On Unix and Linux, the global listener and the X servers are not installed as services. You have to start the global listener manually or create a startup script for it. You can configure the startup behavior of the installation-specific X servers in the Installations.ini file using the XserverAutostart flag (system default: YES). When the global listener is started, it starts all installations-specific X servers for which XserverAutostart=YES. For more information, see Database Administration, Configuration Files. The global listener also automatically starts the NI and NISSL servers.
Note
If an installation-specific X server is not running, it is not started automatically when a request to a database belonging to that installation arrives.
Procedure
Starting the Global Listener
<global_programs_path>\bin\sdbgloballistener start
The global listener then automatically starts all other X servers on the database computer.
Note
If the global listener is already running, and you issue this command, the other X servers are not started automatically.
You can display the global programs path using the dbm_getpath DBM command:
dbmcli dbm_getpath GlobalProgPath
For more information, see Database Manager CLI, dbm_getpath.
Option |
Description |
|---|---|
-D <debugging_level> |
You can specify values from 0 (no debugging information is written) to 9 (maximum debugging information). The default value is 0. |
-F |
If you set this option, the program does not determine the computer name of the application logging on to the DNS server (no reverse DNS lookup). If it is taking a long time to connect to a remote database, restart the program with this option. Like this, you can find out whether the DNS server is responsible for the slow connection. |
-S <tcp_port>[,N:<ni_port][,E:<ssl_port>] |
Only starts the installation-specific X server with the corresponding port number Note that to specify NI and SSL port numbers, you must use the sdbgloballistener program (not the x_server program). |
-V |
Displays the version of the global listener and the X servers. |
-w |
On Unix and Linux, only in SAP systems Restricts the command to the SAP NISSL connection |
-W |
On Unix and Linux, only in SAP systems Suppresses automatic use of SAP NISSL |
-y |
On Unix and Linux, only in SAP systems Restricts the command to the SAP NI connection |
-Y |
On Unix and Linux, only in SAP systems Suppresses automatic use of SAP NI and SSL |
-Z <file_size> |
Specifies the size of the xserver_<computer_name>.prt log file (in KB). <computer_name> is the name of the computer on which the global listener is running. More information: Database Administration, Log Files |
Starting Installation-Specific X Servers
<installation_path>\bin\x_server -S <tcp_port> [<options>] start
Scope |
Default Port |
Function of the X Server |
Protocol |
Protocol Identifier |
|---|---|---|---|---|
All installations on the database computer |
7210 |
Global listener |
TCP/IP |
remote:// |
7269 |
Global listener with SAP networtk protocol NI (for connections via SAPRouter, only available in SAP systems) |
NI (based on TCP/IP) |
sapni:// |
|
7270 |
Global listener with SAP networtk protocol NI and SAP encryption library (for connections via SAPRouter, only available in SAP systems) |
SSL/TLS NISSL (based on TCP/IP) |
remotes:// sapnis:// |
|
First installation <installation_1> on the database computer |
7200 |
X server for <installation_1> |
TCP/IP |
remote:// |
Second installation <installation_2> on the database computer |
7203 |
X server for <installation_2> |
TCP/IP |
remote:// |
Separate Database Studio installation |
7299 |
X server for the separate Database Studio installation, only used by the system to access the local user management database .UMDB |
TCP/IP |
remote:// |
Option |
Description |
|---|---|
-D <debugging_level> |
You can specify values from 0 (no debugging information is written) to 9 (maximum debugging information). The default value is 0. |
-F |
If you set this option, the program does not determine the computer name of the application logging on to the DNS server (no reverse DNS lookup). If it is taking a long time to connect to a remote database, restart program with this option. Like this, you can find out whether the DNS server is responsible for the slow connection. |
-S <tcp_port> |
Only starts the installation-specific X server with the corresponding port number |
-V |
Displays the version of the installation-specific X server. |
-Z <file_size> |
Specifies the size of the xserver_<computer_name>.prt log file (in KB). <computer_name> is the name of the computer on which the X server is running. More information: Database Administration, Log Files |
Example
In the following example, the global listener was not running. Upon startup, it starts the installation-specific X servers of the Installation_2009_07–21 installation and the DatabaseStudio installation.
sdbgloballistener start
INF 19720 XServer on port 7200 started
INF 20010 installation Installation_2009-07-21 - path: C:\Program Files\sdb\ Installation_2009-07-21
INF 19720 XServer on port 7299 started
INF 20010 installation DatabaseStudio - path: C:\Program Files\sdb\DatabaseStudio
INF 19720 sdbgloballistener on port 7210 started
In the following example, only the X server of the Installation_2009_07–21 installation (TCP port 7200) is started.
x_server -S 7200 start
INF 19720 XServer on port 7200 started
INF 20010 installation Installation_2009-07-21 - path: C:\Program Files\sdb\ Installation_2009-07-21