You're at least partway there, depending on what you installed.
globus-job-run and globusrun-ws go through different interfaces. You
at least have an SGE jobmanager that GRAM2 can use. Look for "SEG
SGE globus" (not a type, SEG is the scheduler-event-generator that
GRAM4 uses) and you should find some adapters that work with GRAM4
from either the London e-Science Center or APAC. Not sure how to
answer your Java API question, but you'll know you've got the whole
thing when "globusrun-ws -F host -Ft SGE -submit -c /bin/date" works.
So, given that, I assume "SGE" is the right capitalization, but that
you might not have the required GRAM4 piece. I believe that shows up
under $GL/etc/gram-service-SGE.
Charles
On Jul 20, 2007, at 2:04 PM, Francois Hornoy wrote:
Hi,
I downloaded a piece of code: a Java GRAM Client that submits
jobs. From IBMDevelopersWorks (code attached). It works perfectly,
i succeed in submitting a job on a "globus server", and the job
finished successfully.
But it uses the factoryType
ManagedJobFactoryConstants.FACTORY_TYPE.FORK. And as it's a
RocksCluster with SGE installed, i would like to use SGE as job
manager. So, there is no constant "SGE" in FACTORY_TYPE, so i try
to put factoryType="SGE"; directly, but it does not work, raising
an unknown exception (and no error message on the server side).
I guess SGE is well installed. Indeed, i can run: globus-job-run
localhost/jobmanager-sge /bin/hostname many times, and i can see
with "qstat -f" that jobs are dispatched correctly on the different
nodes, and the results looks good.
So my questions are:
is it wrong to put "SGE" as the factoryType?
is it a problem of SGE installation (missing packets that i
must manually install?)
do you know where the problem can be? ;-)
Cheers,
Francois.
