Hi, There is no such thing as a default jobmanager in ws-gram in the 4.0 series, even if e.g. globusrun-ws seems to pretend there is one: If you don't specify it when you use globusrun-ws, globusrun-ws will use Fork as job manager, and the factory endpoint in the call to ManagedJobFactoryService will actually contain Fork as resource key to the factory endpoint. So from the ManagedJobFactoryService's view all job managers are the same, the client has to specify one in all calls to the ManagedJobFactoryService. If the client does not specify a ResourceID element in the factory endpoint, the request cannot be handled.
In the 4.2 series, a default job manager can be configured on the server-side, and if the client does not specify a job manager in the factory endpoint used in the call to the ManagedJobFactoryService, this default job manager will be used. So if you wanted to backport this to the 4.0 series, you'd have to make changes to both clients and the server. Here's a bugzilla entry that describes the changes on the server-side. It doesn't cover the multi job related code details very well though: http://bugzilla.globus.org/globus/show_bug.cgi?id=5744 Martin Löhnhardt, Benjamin wrote: > Hi, > > is it possible to set another jobmanager than fork as default in Globus > 4.0.8? I have read here > http://www.mail-archive.com/[email protected]/msg00981.html that it is > only possible with code changes. Are these changes documented? > > Best regards, > Benjamin > > -- > > Benjamin Löhnhardt > > UNIVERSITÄTSMEDIZIN GÖTTINGEN > GEORG-AUGUST-UNIVERSITÄT > Abteilung Medizinische Informatik > Robert-Koch-Straße 40 > 37075 Göttingen > Briefpost 37099 Göttingen > Telefon +49-551 / 39-22842 > [email protected] > www.mi.med.uni-goettingen.de > >
