Starting the GUI: start ADFjobs¶
We will assume that you have installed the full ADF package on your machines.
The most convenient way to start the GUI is to first start ADFjobs, one of the GUI modules. Using the SCM menu in ADFjobs you can next start any other GUI module that you have a license for.
Make sure your firewall does not block TCP/IP communication between the GUI modules and scm... processes.
The GUI modules only use TCP/IP traffic within your local computer, with the optional exception of license installation.
Depending on your platform, you start ADFjobs in a slightly different way:
UNIX (such as Linux) users¶
In this tutorial we will assume that you have added $ADFBIN to your PATH. We advise you to do this if you have not already done so. If you do not wish to add $ADFBIN to your PATH, you must start the utilities using
instead of just
On all UNIX platforms the GUI modules are XWindow (X11) programs.
If you are running on a remote UNIX machine you will need to use a tool that will display the remote screen on your local machine. Many GUI modules use OpenGL3.x, and that will not work with X11 (not even using GLX). We advise to use VirtualGL to run on a remote UNIX machine. In the Installation manual you can find details.
In this tutorial we will assume that you have installed the ADF package using the Installer with all the options set to default.
You can start the GUI (adfjobs) by double-clicking its icon on the desktop.
Macintosh users have several easy ways of starting the GUI modules: just like on any other UNIX system (thus, using the command line), or using the ADF2017.xxx program.
The easiest way is using the ADF2017.xxx program. When you start it (for example by double clicking), ADFjobs will be started automatically. Next you can use the SCM menu to start the other ADF-GUI modules.