Galaxy Communicator Tutorial:

Getting Started

License / Documentation home / Help and feedback

The tutorial portion of the Galaxy Communicator documentation makes a few assumptions about you, your Galaxy Communicator installation, and your computing environment.  We've already noted that there are special instructions for installing the distribution so that the tutorial can be run, on Unix and Windows. In the remainder of this document, we'll describe what else you need to do to get yourself started.

Reference environment

We believe that the training course should work on any Unix environment on which the Galaxy Communicator installation can be installed. However, for reference purposes, here is the configuration of our primary development environment for the tutorial:

Unix 

Windows

If your behavior differs from ours, it may be due to a difference in environment.

Start up X windows (Unix)

The Unix version of the  tutorial assumes that you're running X. Since you're reading this documentation, you're almost certainly in X already if you're on a Unix machine.

Set up your shell environment

You'll need to modify your shell environment to reflect the location of the root of the Galaxy Communicator installation, as well as some of the executables you'll be using. On all platforms, the tutorial is started up from a shell. Note that in all cases, you must run the tutorial from a writeable directory, since some of the logging exercises will try to write logs to the current working directory.

Unix csh/tcsh

% setenv GC_HOME <root_of_GC_distro>
% setenv PATH $GC_HOME/contrib/MITRE/tools/bin:$PATH
% cd <some_writeable_directory>

Unix sh/bash

$ GC_HOME=<root_of_GC_distro>; export GC_HOME
$ PATH=$GC_HOME/contrib/MITRE/tools/bin:$PATH; export PATH
$ cd <some_writeable_directory>

Windows MS-DOS

C:\> set GC_HOME=<root_of_GC_distro>
C:\> set PATH=<location_of_Python.exe>;%PATH%
C:\> set PM_DIR=%GC_HOME%\contrib\MITRE\tools\src\process_monitor
C:\> chdir <some_writeable_directory>

If you add these settings to your shell startup file, you can run the examples from any shell. Otherwise, you will only be able to run the examples in the shelll in which you make these settings, because the PATH value you'll set in the next step is usually overwritten when you start up a new shell.

Next: The basics: how the Hub and server communicate, and what they say

License / Documentation home / Help and feedback
Last updated August 16, 2002