An example would be using SUM (if the firewall ports are blocked) or SWPM to perform an installation, or if you're running an AS Java system, the offline editor (configtool).
If you're already using PuTTY to get into the remote system via SSH, then you are already part way there.
In this post, I will show you how to dynamically adjust the PuTTY and Linux configuration so that you can use MobaXterm (or any other X-client) to connect into the Linux using X11 (X-Windows).
This is not the same as using the standard method of ticking the X-11 forwarding option, because this option must be ticked prior to establishing the connection into the server.
Instead of exiting from your session and re-connection, you can simply use standard port forwarding to enable your X-client connection over SSL.
Step 1 – Connect into Linux using PuTTY.
You should ideally already be connected into the remote system using SSH and PuTTY (that is the aim of this post).
If you're not already connected, then open your PuTTY session as normal.
Step 2 – Open X-Client on your PC/virtual server.
Open your X-Client on your local PC. Ideally it will default to display 0.
The "0" simply refers to a subset of a port range. It's a virtual display.
In our example, we used the free MobaXterm tool to provide X-client capability. Mainly because the tool is free and integrated into one nice binary that can be placed on a USB stick for easy access.
In MobaXterm, hover the mouse over the "X" in to top right frame of the window.
It should be green, and if so, it will display the current IP and display port it has been configured with.
Step 3 – Adjust Linux SSH configuration.
The Linux SSH configuration may not be setup to enable X11 forwarding.
This is usually performed by the Linux administrator at a global level in the ssh daemon configuration file.
However, it is possible to adjust the config for individual users only.
As your Linux user (in an SAP system this would usually be the <sid>adm user account), enable the X-11 forwarding:
echo "ForwardX11 yes" > $HOME/.ssh/configThe above command simply enables the current user to forward X11 connections over the SSH connection.
It puts this config into a file called "config" within the .ssh directory of the current Linux user's home directory.
Step 4 – Setup the port forwarding.
Since this tutorial is going to show the setup of X11 dynamically, with an already established SSH connection, from within your already established PuTTY session, select the Windows window menu from the top left of the PuTTY window and select "Change Settings…":
Expand the "Connection -> SSH -> Tunnels" settings area on the left hand tree menu:
(Notice there is no option to enable or disable the usual X-11 forwarding option)
It is telling PuTTY to establish a listening port on the Linux server, listening on port 6000 (the port for display "0.0").
The port is "remote" because it is remote to the PuTTY session (i.e. not on the computer where you are running PuTTY).
We're telling PuTTY to only consider IPv4 because we don't use IPv6 and have no interest in having it listen for an IPv6 connection.
If you were to run "netstat -an | grep 6000" on the Linux server, you would see one port in status LISTEN.
Now the port forwarding is established, all we need to do is configure our Linux session to make use of the display setting.
Step 5 – Configure DISPLAY
In your Linux session, set the DISPLAY variable appropriately.
In a C-shell you would use:
> setenv DISPLAY localhost:0.0In a Bash, Bourne or Korn shell you would use:
$ export DISPLAY=localhost:0.0From within the Linux session you should now be able to run an X11 application and see the window on your PC/virtual server.
You can use the standard "xeyes" or "xclock" to perform the test, however sometimes on Linux installs these do not get installed.
I've found that it's generally possible to call "firefox" or "totem" to perform an X11 test.
Alternatively, just call your intended SAP X11 application as discussed at the beginning.