Download Instructions
The detailed instructions for downloading and installing gLite
can be looked up in the gLite
Installation Guide (1.4). The installation
guide is published for each release of gLite, so be careful to select
the correct version through the gLite
home page. As it is explained in the install guide, there are
basically two ways to download gLite:
- Through the Advanced
Package Tool apt (preferred). The instructions
on how to use apt
on Scientific Linux for gLite can be found here,
including the lines you need to put into your /etc/apt/sources.list
file. . If you're using apt, you only
need to run apt-get
update as usual and then fetch one of the
three packages(depending on what you want to download). In
summary,
- Set up your apt, see
instructions here and then execute either one of
- apt-get install glite-file-transfer-service-config
- apt-get install glite-file-transfer-agents-config
- apt-get install glite-file-transfer-service-client-config
- Through the glite installer scripts:
Just download the script and execute it. It assumes a Scientific Linux environment.
- Release 1.4: gLite Installer script: SERVER AGENTS CLIENT
- Release 1.5*: gLite Installer script: SERVER AGENTS CLIENT
*1.5 is only available as a pre-release, its official release is planned for
early 2006
Additional downloads:
- Binary distribution: This is the 'tarball' distribution. For
gLite 1.4, the binaries can be found here.
Just pick the most recent version of
- glite-data-transfer-fts (for the web service)
- glite-data-transfer-agents and glite-data-transfer-url-copy
(for the agents)
- glite-data-transfer-cli and glite-data-transfer-url-copy
(for the command line tool)
- glite-data-transfer-api-c, glite-data-transfer-api-java,
glite-data-transfer-api-perl (for the client libraries).
for the dependencies, see below.
- Source: Source distributions can be downloaded for version
1.4 here. Again,
you need everything that starts with glite-data-transfer.
- CVS.
Additional Details
First you need to know what part of the FTS you
have to download and install. Do you have to set up a whole server
or do you only need the client? The FTS comes in three components
(see the architecture
overview). Depending on what you need, you need to install
different packages.
| FTS Client |
If you just want to use the FTS
as a client, you only need the client packages.
If you use APT or the gLite
installers, then all the dependencies will be updated automatically
for you. This is by far the easiest way to proceed. For APT,
just invoke
apt-get install
glite-file-transfer-service-client-config
For the gLite installer, just download the necessary script,
make it executable (chmod +x) and run it.
If you have to do it 'manually', you will need
the following additinal
packages (some are optional):
- glite-data-util-c
- glite-data-transfer-api-c
- glite-service-discovery-api-c
- glite-service-discovery-file-c
- glite-service-discovery-bdii-c
- glite-security-voms-api-c
- vdt (globus) security clients
- libcgsi_gsoap_2.6
- libcrypto
- glib2
|
| FTS Server |
In order to run an FTS, you need three
components: The Web Server, the FTS Agents and a database.
The FTS Server
is the Web Service component, i.e. the one to
which all clients will connect. Therefore it needs to be
reachable by the potential clients of the software (which
is usually
over the wide area network). So make sure that the machine
you choose to run this on is on the network and reachable.
The port can be configured (see below). If you use APT, just
invoke
apt-get install
glite-file-transfer-service-config
For the gLite installer,
just download the necessary script,
make it executable (chmod +x) and run it.
For the manual installation, you need
- tomcat5
- oracle jdbc or mysql jdbc depending on what db backend
you intend to use
- glite-data-common
- glite-security-trustmanager
- glite-security-util-java
|
| FTS Agent |
The FTS Agent is the actual workhorse of the FTS. It will
scan the entries in the FTS DB and perform all the tasks necessary
to perform the transfers. The Agents come as a separate module
as they can be deployed on many boxes (in order to scale to
many channels and VOs supported by a single FTS instance).
It is of course possible (and the default setup) to run the
agents and the server on the same node. The FTS Agent can be
downloaded very easily using APT:
apt-get install
glite-file-transfer-agents-config
For the gLite installer, just download the necessary script,
make it executable (chmod +x) and run it.
For the manual installation, you need
- glite-data-util-c
- glite-data-config-service
- glite-data-srm-api-c
- glite-data-transfer-url-copy
- glite-data-srm-cli
- log4cpp
- xalan, xalanMsg, xerces-c
- myproxy
- vdt (globus) security and transfer libs
- mysql or oracle clients to connect to the db
|
|
Release Notes
The release notes for the FTS Server, Agents and Client can be
directly downloaded for the corresponding gLite release from the
gLite Website (follow the link
to download packages, choose the release version - the release notes
are available for each module separately). In addition, after installation,
each component puts additional release
notes
into the
$GLITE_LOCATION/share/doc/<module>/RELEASE_NOTES file.
GLITE_LOCATION is
usually set to /opt/glite.
For Release 1.4, the full list of release notes for the FTS is:
In addition, there is a Wiki
page for the LCG Service Challenge 3 setup explaining the changes
from Release 1.3 to 1.4.
The automatically
generated documentation pages will contain the
most recent link to the release notes and readme files. |
Installation and Configuration
Instructions
The installation instructions of the FTS are part of the gLite
Installation Guide. As mentioned above, this guide is updated
for each release. It contains a separate chapter on the FTS server
and
clients, and on the FTS Agents. For gLite 1.4, this is at
The Installation of the Service Challenges mandated additional
pages that are kept in the Wiki space of LCG, as it is a specific
installation and configuration instruction in that context. So those
should be read with that premise, that they are instructions for
a very well defined environment and may not necessarily be ported
to other environments. There are Service Challenge pages for
|
|
