Alternative Alfi Installation for
Remote Viewing Via X
For performance reasons, this alternative is not recommended in
general. It should only be
used when a user cannot install and run Java locally. If a user
cannot run Java applications locally on their machine, but does have
access to a server which can run Java applications, and can display
such applications locally via X (i.e., the client's local machine is an
X-server), then this alternative installation can be used. Be
forewarned that the graphic display of Alfi remotely in this manner
will always be slower than running Alfi locally as detailed in the standard
Instructions for the
Administrator of the Remote Software Server
The first 3 steps are identical to steps 1 - 3 in the standard
installation instructions. The E2E modeler package, perl, and a
recent version of java will be required to be on the software server:
1. Find the E2E Modeler installation
on the software server if it exists already, or install it yourself.
2. Find perl on the software server.
See step 1 in
the standard installation
procedure for details. [The
installation needs to be in a reasonable location for end-users to
access. For example, the primitives directory path might be
something like /usr/local/e2e/e2e-x.x.x/AdlibMM/
3. Find java (or install it) on the software server to check that the version is recent enough.
4. Download the latest jar files
required by Alfi.
and configure the alfi_remote perl
script which is used to launch Alfi.
The two jar files required are alfi.jar
Unfortunately, these files will need to updated from time to
time. (This is one of the reasons the standard installation is
better. Java Web Start handles all updates to Alfi
automatically.) Place these jar files in a location suitable for
access by end-users, perhaps in a directory like /usr/local/e2e/alfi/
above links will always point you to the latest versions.
6. Test the installation.
Download the alfi_remote
, and configure as
- Edit the first line's path to perl on the software server (as
found in step 2 above.)
- Edit the setting of $ALFI_JAR_DIR
to be the path to the directory in which you have placed the alfi.jar
and JGo.jar files from step 4.
- Edit the setting of $JAVA
to be the path to java on the software server (as found in step 3
- Save changes and quit editor.
- % chmod +x alfi_remote
- Place alfi_remote
in a reasonable place for end-users to access (perhaps in the same
directory as the jar files.)
- Log into the remote software server from any X display in a
manner which allows X to be passed to your display.
- Create a test working directory:
- remote_server% mkdir alfi_test_dir
- remote_server% cd alfi_test_dir
- Follow the steps for the End-user as given below to check if Alfi
can be started. In setting the E2E_PATH, ignore the value
$other_E2E_box_libraries. All you will need is the following:
- remote_server% setenv E2E_PATH .:$e2e_primitives_directory
- If Alfi starts, the installation is complete.
Instructions for the End-user of
the Local X Display
The system administrator of the remote server which you will log into
to display Alfi should provide you with the following information (all
paths refer to paths when you are logged into the remote server):
Here are the steps you need to do to run Alfi.
- The path to the directory containing the files of the E2E
primitives (the .prm files.) (This value will be referred to as $e2e_primitives_directory
below.) E.g., /usr/local/e2e/e2e-2.1.1/AdlibMM/.
- The path to the alfi_remote script which is used to start Alfi
(to be referred to as $path_to_alfi_remote.) E.g., /usr/local/e2e/alfi/alfi_remote.
- Log into your account on the remote server. You may need to
ask your system administrator for help if you do not know how to log in
so that X can be displayed on your local display from the remote
server. A quick test is to try displaying something trivial like
an xterm. Try this:
- remote_server% xterm
- If an xterm window does not appear on your display, then you
need to ask your system administrator how to display X on your display
from remote_server. If the xterm does appear, go ahead and exit
- Check that the alfi_remote script exists and is executable.
- remote_server% ls -l
- Make an alias to the alfi startup script.
- remote_server% alias
- Set your E2E_PATH
environment variable. Your system administrator should give you
the value for $e2e_primitives_directory
as stated above. The value of $other_E2E_box_libraries must
include the paths to any E2E box libraries you may need.
Regarding this information, you should contact the author of the E2E
box package you are using (if any.) More details regarding the E2E_PATH are
- remote_server% setenv E2E_PATH .:$e2e_primitives_directory:$other_E2E_box_libraries
- Start Alfi.
- remote_server% alfi_remote
Please report problems and/or suggestions to Bruce Sears.
This file was updated Oct. 3, 2005. Please send questions and
comments to Bruce.