Table of Contents

Interoperation of GridWay with BES

The OGSA-BES specification defines Web Services interfaces for creating, monitoring, and controlling computational entities such as UNIX or Windows processes, Web Services or parallel programs, called activities, within a defined environment. A BES implementation executes each activity that it accepts on an appropriate computational resource. This document describes how to install and configure GridWay to submit jobs to BES endpoints.

Two implementations of BES have been tested:

Installation

Configuration of Drivers

The GridWay Configuration Guide provides complete information about configuration of the meta-scheduler. Next steps describe the specific configuration to interface with BES endpoints.

   # MADs for OGSA-BES
   IM_MAD = static:gw_im_mad_static:-l etc/BES_hosts.list:dummy:bes
   EM_MAD = bes:GW_em_mad_bes::jsdl

GridSAM can use GridFTP, so add also this line:

   TM_MAD = dummy:gw_tm_mad_dummy:-u gsiftp\://<hostname>

However, UNICORE only works with an insecure GASS server, so add this one:

   TM_MAD = dummy:gw_tm_mad_dummy:-i
  <hostname1> etc/<hostname1>.machine
  <hostname2> etc/<hostname2>.machine
  <hostname3> etc/<hostname3>.machine
  ...

The files /usr/etc/<hostname>.machine contain static information about each node where you want to send jobs. In particular, LRMS_NAME should contain “gridsam” or “unicore” to identify the target implementation. Please refer to the configuration guide for more details.

   Defaults>GWUSERS env_keep="GW_LOCATION GLOBUS_LOCATION"
   #GridWay entries (OGSA-BES MAD)
   gwadmin ALL=(GWUSERS) NOPASSWD: /usr/bin/GW_em_mad_bes *
   gwadmin ALL=(GWUSERS) NOPASSWD: /usr/bin/gw_tm_mad_dummy *

Using GridWay

The functionality and interfaces provided by GridWay are independent from the underlying Grid infrastructure. Please refer to the guides (user's guide, command reference, programming guide…) available at the Documentation section.