gridsam-discuss Mailing List for GridSAM (Page 4)

Brought to you by: justinbradley, npch, stevecrouch

gridsam-discuss — GridSAM users and developers

You can subscribe to this list here.

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct (1)	Nov (3)	Dec (18)
2006	Jan (11)	Feb (19)	Mar (5)	Apr (9)	May (5)	Jun (1)	Jul	Aug (6)	Sep (8)	Oct	Nov (10)	Dec (1)
2007	Jan (3)	Feb (14)	Mar (8)	Apr (5)	May (5)	Jun (1)	Jul (1)	Aug	Sep	Oct (8)	Nov (3)	Dec (1)
2008	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (5)	Sep	Oct (1)	Nov (9)	Dec (7)
2009	Jan (2)	Feb (1)	Mar	Apr (8)	May (3)	Jun (2)	Jul (7)	Aug (5)	Sep	Oct (6)	Nov (1)	Dec
2010	Jan	Feb	Mar (6)	Apr (1)	May (1)	Jun (2)	Jul (3)	Aug (1)	Sep	Oct	Nov	Dec (5)
2011	Jan (2)	Feb (3)	Mar (6)	Apr	May	Jun	Jul	Aug	Sep (2)	Oct	Nov	Dec

Flat | Threaded

<< < 1 2 3 4 5 6 .. 10 > >> (Page 4 of 10)

Re: [gridsam-discuss] Question about globus job

From: Stephen M. <as...@do...> - 2008-11-19 07:55:08

Dear Yoshikazu Tanaka,

The GridSAM project is independent from the Globus jobmanager and as such is unaware of the differences between the different Globus back-ends. When you submit a job to Globus through GridSAM the standard interface to Globus is used and the endpoint that GridSAM submits to is the only indication of what back-end Globus is submitting to. As long as the Globus endpoint conforms to the normal Globus interface you should be able to submit to any Globus jobmanager.

You may also wish to consider using GridSAM to submit directly to PBS, LSF, SGE or Fork directly without the use of Globus,

steve..



田中　義一 wrote:
> I have made a mistake to send this mail gri...@li....
>
>
> I have a question about GridSAM jobmanager.
>
> I have confirmed that I can submit a job using globus(Fork)
>  via GridSAM.
>
> Can we submit a job using globus(+PBS or +SGE) jobmanger?
> I would like to know whether globus jobmanager(fork,psb,sge) is
> independent of gridsam-jobmanager(globus) or not.
>
> NAREGI(Center for Grid Research and Development)
> Yoshikazu Tanaka
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>   

-- 
------------------------------------------------------------------------
Dr A. Stephen McGough                       http://www.doc.ic.ac.uk/~asm
------------------------------------------------------------------------
Technical Coordinator, London e-Science Centre, Imperial College London,
Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK
tel: +44 (0)207-594-8409                        fax: +44 (0)207-581-8024
------------------------------------------------------------------------

[gridsam-discuss] Question about globus job

From: 田中　義一 <yt...@gr...> - 2008-11-19 04:12:01

I have made a mistake to send this mail gri...@li....


I have a question about GridSAM jobmanager.

I have confirmed that I can submit a job using globus(Fork)
 via GridSAM.

Can we submit a job using globus(+PBS or +SGE) jobmanger?
I would like to know whether globus jobmanager(fork,psb,sge) is
independent of gridsam-jobmanager(globus) or not.

NAREGI(Center for Grid Research and Development)
Yoshikazu Tanaka

[gridsam-discuss] GridSAM 2.1.1 released

From: Justin B. <jb...@ec...> - 2008-11-12 16:55:55

Hi All,

Following on from the recent GridSAM 2.1.0 release, we are pleased to  
announce a new release.

GridSAM 2.1.1 is a release intended for developers.
It is also designed to be used with OMII-UK's Campus Grid Toolkit  
1.1.2.  This is available from www.omii.ac.uk.

GridSAM 2.1.1 now includes:
- AFT, RFT and Rerun support for the Fork and Condor DRM connectors.   
These are new features supplied by ICT.
- Copyright notices have been updated in the recent code developed by  
ICT
- Is now compatible with AHE 1.0.2 as supplied with Campus Grid  
ToolKit 1.1.2.

See https://sourceforge.net/project/showfiles.php?group_id=141177&package_id=154979

--
Justin Bradley
Design & Development Team Leader
j.b...@om...
OMII-UK
Suite 3235, Zepler Building (B59)
University of Southampton

Re: [gridsam-discuss] National Grid Service & GridSAM

From: Vesselin N. <ve...@do...> - 2008-11-05 15:20:11

Arif,

Once you've imported your keys/certificate into the OMII Client JKS 
keystore, make sure
the authentication mechanism can read it. The way the system accesses 
the keystore is
by reading the configuration file 
'<omii_client_dir>/conf/crypto.properties'.
Make sure the config values in that file are correct for your keystore.

--Vesso

Shaon, ABS (Arif) wrote:
> Thanks.  I have installed the certificates as per the instructions in
> the OMII manual.  But I still get the same error.  I have just sent an
> email to the NGS to check if my NGS certificate would suffice for
> accessing the GridSam server.
>
> Thanks again.
>
> Arif
>
>
> -----Original Message-----
> From: Vesselin Novov [mailto:ve...@do...] 
> Sent: 05 November 2008 10:39
> To: Shaon, ABS (Arif)
> Cc: gri...@li...
> Subject: Re: [gridsam-discuss] National Grid Service & GridSAM
>
> Arif,
>
> The myproxy certificate is used by the GridSAM Server to submit your job
>
> to Globus.
> There is another set of certificates needed for a GridSAM Client to 
> submit to a GridSAM Server.
> This is actually the authentication mechanism of the OMII 
> Client/Container where the GridSAM Client/Server run.
> The mechanism requires valid x509 certificates/keys in the JKS keystores
>
> created during installation at '<omii_client_dir>/omii.ks'
> and '<omii_server_dir>/omii.ks'.
> It's possible that the NGS certificate you're given is to be used for 
> both GridSAM Server and Globus, check with the NGS admins.
> If this is so, check the OMII documentation on how to set/configure the 
> authentication on your client side at: 
> "http://www.omii.ac.uk/docs/3.4.2/installation_guide/omii_3_installation
> _and_setup_guide.htm"
>
> --Vesso
>
> Shaon, ABS (Arif) wrote:
>   
>> Hi List,
>>
>>  
>>
>> I am trying to use a GridSam client to submit a test sleep job to 
>> NGS.  Steps I used are as follows:
>>
>>  
>>
>> 1. Acquired a user certificate from NGS
>>
>> 2. Uploaded the certificate to myproxy using the Java tool available 
>> on the NGS site
>>
>> 3. Installed OMII and GridSAM on my machine
>>
>> 4. Tried to execute the command: gridsam-submit -myproxy -myproxyhost 
>> "myproxy.grid-support.ac.uk" -myproxyuser "username" -s 
>> "https://gridsam.besc.ac.uk:18443/gridsam-oxford/services/gridsam" -j 
>> /home/ashaon/ngs_stuff/omii-uk-client/gridsam/data/examples/sleep.jsdl
>>
>> 5. Error received:
>>
>>  
>>
>> 2008-11-03 16:24:52,746 FATAL [GridSAMSubmit] (main:) unable to submit
>>     
>
>   
>> job: failed to submit job: ; nested exception is:
>>
>>         javax.net.ssl.SSLException: Connection has been shutdown: 
>> javax.net.ssl.SSLHandshakeException: 
>> sun.security.validator.ValidatorException: PKIX path building failed: 
>> sun.security.provider.certpath.SunCertPathBuilderException: unable to 
>> find valid certification path to requested target
>>
>>  
>>
>>  
>>
>> Any help with this would be greatly appreciated.
>>
>>  
>>
>> Many thanks in advance.
>>
>>  
>>
>> Regards
>>
>> Arif
>>
>>  
>>
>>
>> -- 
>> Scanned by iCritical.
>>
>>
>>
>>     
> ------------------------------------------------------------------------
>   
>>     
> ------------------------------------------------------------------------
> -
>   
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>     
> challenge
>   
>> Build the coolest Linux based applications with Moblin SDK & win great
>>     
> prizes
>   
>> Grand prize is a trip for two to an Open Source event anywhere in the
>>     
> world
>   
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>
>>     
> ------------------------------------------------------------------------
>   
>> _______________________________________________
>> GridSAM-Discuss mailing list
>> Gri...@li...
>> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>>   
>>

Re: [gridsam-discuss] National Grid Service & GridSAM

From: Shaon, A. (Arif) <ari...@st...> - 2008-11-05 15:13:22

Thanks.  I have installed the certificates as per the instructions in
the OMII manual.  But I still get the same error.  I have just sent an
email to the NGS to check if my NGS certificate would suffice for
accessing the GridSam server.

Thanks again.

Arif


-----Original Message-----
From: Vesselin Novov [mailto:ve...@do...] 
Sent: 05 November 2008 10:39
To: Shaon, ABS (Arif)
Cc: gri...@li...
Subject: Re: [gridsam-discuss] National Grid Service & GridSAM

Arif,

The myproxy certificate is used by the GridSAM Server to submit your job

to Globus.
There is another set of certificates needed for a GridSAM Client to 
submit to a GridSAM Server.
This is actually the authentication mechanism of the OMII 
Client/Container where the GridSAM Client/Server run.
The mechanism requires valid x509 certificates/keys in the JKS keystores

created during installation at '<omii_client_dir>/omii.ks'
and '<omii_server_dir>/omii.ks'.
It's possible that the NGS certificate you're given is to be used for 
both GridSAM Server and Globus, check with the NGS admins.
If this is so, check the OMII documentation on how to set/configure the 
authentication on your client side at: 
"http://www.omii.ac.uk/docs/3.4.2/installation_guide/omii_3_installation
_and_setup_guide.htm"

--Vesso

Shaon, ABS (Arif) wrote:
>
> Hi List,
>
>  
>
> I am trying to use a GridSam client to submit a test sleep job to 
> NGS.  Steps I used are as follows:
>
>  
>
> 1. Acquired a user certificate from NGS
>
> 2. Uploaded the certificate to myproxy using the Java tool available 
> on the NGS site
>
> 3. Installed OMII and GridSAM on my machine
>
> 4. Tried to execute the command: gridsam-submit -myproxy -myproxyhost 
> "myproxy.grid-support.ac.uk" -myproxyuser "username" -s 
> "https://gridsam.besc.ac.uk:18443/gridsam-oxford/services/gridsam" -j 
> /home/ashaon/ngs_stuff/omii-uk-client/gridsam/data/examples/sleep.jsdl
>
> 5. Error received:
>
>  
>
> 2008-11-03 16:24:52,746 FATAL [GridSAMSubmit] (main:) unable to submit

> job: failed to submit job: ; nested exception is:
>
>         javax.net.ssl.SSLException: Connection has been shutdown: 
> javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException: PKIX path building failed: 
> sun.security.provider.certpath.SunCertPathBuilderException: unable to 
> find valid certification path to requested target
>
>  
>
>  
>
> Any help with this would be greatly appreciated.
>
>  
>
> Many thanks in advance.
>
>  
>
> Regards
>
> Arif
>
>  
>
>
> -- 
> Scanned by iCritical.
>
>
>
------------------------------------------------------------------------
>
>
------------------------------------------------------------------------
-
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>
------------------------------------------------------------------------
>
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>   
-- 
Scanned by iCritical.

Re: [gridsam-discuss] National Grid Service & GridSAM

From: Vesselin N. <ve...@do...> - 2008-11-05 10:39:39

Arif,

The myproxy certificate is used by the GridSAM Server to submit your job 
to Globus.
There is another set of certificates needed for a GridSAM Client to 
submit to a GridSAM Server.
This is actually the authentication mechanism of the OMII 
Client/Container where the GridSAM Client/Server run.
The mechanism requires valid x509 certificates/keys in the JKS keystores 
created during installation at '<omii_client_dir>/omii.ks'
and '<omii_server_dir>/omii.ks'.
It's possible that the NGS certificate you're given is to be used for 
both GridSAM Server and Globus, check with the NGS admins.
If this is so, check the OMII documentation on how to set/configure the 
authentication on your client side at: 
"http://www.omii.ac.uk/docs/3.4.2/installation_guide/omii_3_installation_and_setup_guide.htm"

--Vesso

Shaon, ABS (Arif) wrote:
>
> Hi List,
>
>  
>
> I am trying to use a GridSam client to submit a test sleep job to 
> NGS.  Steps I used are as follows:
>
>  
>
> 1. Acquired a user certificate from NGS
>
> 2. Uploaded the certificate to myproxy using the Java tool available 
> on the NGS site
>
> 3. Installed OMII and GridSAM on my machine
>
> 4. Tried to execute the command: gridsam-submit -myproxy -myproxyhost 
> "myproxy.grid-support.ac.uk" -myproxyuser "username" -s 
> "https://gridsam.besc.ac.uk:18443/gridsam-oxford/services/gridsam" -j 
> /home/ashaon/ngs_stuff/omii-uk-client/gridsam/data/examples/sleep.jsdl
>
> 5. Error received:
>
>  
>
> 2008-11-03 16:24:52,746 FATAL [GridSAMSubmit] (main:) unable to submit 
> job: failed to submit job: ; nested exception is:
>
>         javax.net.ssl.SSLException: Connection has been shutdown: 
> javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException: PKIX path building failed: 
> sun.security.provider.certpath.SunCertPathBuilderException: unable to 
> find valid certification path to requested target
>
>  
>
>  
>
> Any help with this would be greatly appreciated.
>
>  
>
> Many thanks in advance.
>
>  
>
> Regards
>
> Arif
>
>  
>
>
> -- 
> Scanned by iCritical.
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>

[gridsam-discuss] National Grid Service & GridSAM

From: Shaon, A. (Arif) <ari...@st...> - 2008-11-04 23:31:17

Hi List,

 

I am trying to use a GridSam client to submit a test sleep job to NGS.
Steps I used are as follows:

 

1. Acquired a user certificate from NGS

2. Uploaded the certificate to myproxy using the Java tool available on
the NGS site 

3. Installed OMII and GridSAM on my machine 

4. Tried to execute the command: gridsam-submit -myproxy -myproxyhost
"myproxy.grid-support.ac.uk" -myproxyuser "username" -s
"https://gridsam.besc.ac.uk:18443/gridsam-oxford/services/gridsam" -j
/home/ashaon/ngs_stuff/omii-uk-client/gridsam/data/examples/sleep.jsdl

5. Error received:

 

2008-11-03 16:24:52,746 FATAL [GridSAMSubmit] (main:) unable to submit
job: failed to submit job: ; nested exception is:

        javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to
find valid certification path to requested target

 

 

Any help with this would be greatly appreciated.

 

Many thanks in advance.

 

Regards

Arif

 


-- 
Scanned by iCritical.

[gridsam-discuss] GridSAM 2.1.0 released

From: Justin B. <jb...@ec...> - 2008-10-06 09:27:57

Hi All,

Following on from the recent GridSAM 2.0.2 release, we are very
pleased to announce the release of GridSAM 2.1.0.
https://sourceforge.net/project/showfiles.php?group_id=141177&package_id=154979&release_id=629983
May I also thank ICT for all their hard work in producing this new
release.
Please see the release notes below.

GridSAM 2.1.0 is a release intended for use by developers.
This release is based on 2.0.2, which the addition of several new
features implemented by ICT.

It should be noted that not all new DRM connector features are
available for all existing connectors.
For a breakdown of what is available, please see the project document:
GridSAM-DRM-features.pdf

- New PBS connector.
This is a newly developed connector, in addition to the one released
in 2.0.2.
This connector has been tested on PBS Torque and OpenPBS.
Internally it is called 'openpbs', where the previous connector is
called 'pbs'.
The new connector is recommended over the previous, as it has a more
complete feature set and is considered more reliable.
This is with the exception of when used in conjunction with the
Application Hosting Environment (AHE), where some problems have been
observed.
See Feature tracker item 2007701.

- New LSF connector.
This new connector shares the majority of its implementation with
the new PBS connector.
See Feature tracker item 2007746.

- Pool accounts and access to working directories.
This new feature allows jobs to be run as one of a number of
registered local users.
Staged files are owned and are secured as the user by which they are
submitted.
By default if this new feature is not configured, jobs are run as
the user running the container as before.
Access to the job working directories is also available.
See Feature tracker items 2007660 and 2007782.

- Asynchronous and Reliable data transfer.
This allows files to be staged in more efficiently and reliably.
Partially staged files can now have their transmission resumed or
restarted.
See Feature tracker items 2007776 and 2007775.

- Job rerun.
This allows jobs to re-executed without re-staging the associated
input files.
See Feature tracker item 2007784.

Documentation updates to support the new features will follow in due
course.

--
Justin Bradley
Design & Development Team Leader
j.b...@om...
OMII-UK
Suite 3235, Zepler Building (B59)
University of Southampton

[gridsam-discuss] Hi all, how about the job rerun feature of gridsam

From: hopesophite <hop...@gm...> - 2008-08-29 14:58:17

Hi all,

A discussion about job rerun has been add to sourceforge. Here is the URL: http://sourceforge.net/forum/message.php?msg_id=5206076

The content is as follows.

========================================

Here is a quick start of rerun, and I want to know your opinions. 
 
What’s rerun? 
Job rerun is re-execution a previous job within the same working directory from a specified stage. 
 
Why we need rerun? 
The job re-run feature request tells us why we need rerun. 
http://sourceforge.net/tracker/index.php?func=detail&aid=2007784&group_id=141177&atid=748735 
“In GridSAM, when something wrong happens to a job in the processing pipeline, then the job state will be immediately advanced to “Failed”, and the only way to retry is to resubmit the same job, then a new working directory will be generated. For example, after 2 days of hard computing, your job finally output a lot of result files, and GridSAM is ready to stage them out. Unfortunately, the FTP URL you specified for staging out is wrong. Then GridSAM will advance your job state to “Failed”, and you will never get the output results which have been successfully generated.” 
 
What should be done to add this new feature? 
1) A client command gridsam-rerun to rerun a job. 
It will need three parameters: 
parentJobID: the ID of the job to be rerun and the job is called the parent job.  
startJobState: Which state should the rerun start from? It can be pending, staged-in and executed. 
JSDL: the new JSDL for this rerun. If omitted, the JSDL of the parent job will be used. 
 
If success, it will start a new job and return the jobID. 
 
2) The gridsam-rerun command will pass the rerun request to the gridsam server. 
 
3) DRMConnector should support the re-run. 
 
What’s our solution? 
1) It is simple and needs no discussion. 
 
2) A new web service operation called rerun should be added. 
It's not easy to add such an operation. And the “new” client with “old” server will fail to find the operation. 
 
3) We add several new ProgressCriteria to decide whether the given DRMConnector should be executed or skipped for a rerun job. Any DRMConnectors want to support rerun MUST use the newly provided ProgressCriteria. 
 
What’s the current status and plan of the rerun? 
Now an initial version of rerun is under testing with PBSDRMConnectors. 
This feature will be released with GridSAM 2.0.3. 

============================================================




hopesophite
2008-08-29

Re: [gridsam-discuss] GridSAM news and gsiftp urls

From: Jos K. <jko...@st...> - 2008-08-25 06:48:49

Hi.

The reason I used absolute URLs for GSIFTP is because that is the way  
most other modules in the Apache VFS work. I thought it would be  
confusing for users if SFTP and FTP use one URL scheme and GSIFTP  
would use another.

I think for GridSAM (and my own project 'Rapid') the best way forward  
would ideally be a standard-based one(i.e. according to section 3.2.2  
of RFC 1738). So URLs would be relative to the users' home directory  
unless the path starts with a %F2 character.

The problem is that that would probably mean changing the SFTP, FTP  
and GSIFTP modules to make them consistent.

SFTP and FTP do support an option 'setUserDirIsRoot', but I found this  
restricts a user to their home directory (and its subdirectories). So  
resolving 'sftp://my.host.ac.uk/..' will throw an exception. Neither  
SFTP or FTP can handle the '%F2' character.

Jos Koetsier


Quoting Justin Bradley <jb...@ec...>:

> Hi All,
>
> For those who don't know me, my name is Justin Bradley and I have
> taken over from Hugo Mills as the release manager for GridSAM.
>
> I have now tagged version 2.0.2 in the sourceforge subversion
> repository.  This version contains all the main fixes and enhancements
> to date as well as the Globus status patch as supplied by Jos
> Koetsier.  I'll publicise builds for this over the coming days.
>
> The second patch from Jos is still pending, the patch works as
> designed, but it has the effect of changing the default interpretation
> of the gsiftp urls.
> These are the gsiftp urls as supplied in the JSDL files as used by
> GridSAM, when Globus is being used as a back end.
> The change is that by default the path component is now interpreted as
> being an absolute file reference, whereas previously is was considered
> to be relative to the home directory of the user in question.
>
> For example: gsiftp://machine.com/dir/file.txt is now interpreted as
> being /dir/file.txt rather than for example /home/user/dir/file.txt
>
> We have a proposed change to make to this new behaviour, and would
> like feedback from the community on this.
>
> This would be to revert the default to the way it was before, but
> ensure that a reference can explicitly be made absolute or relative,
> and these explicit styles would be encouraged.
>
> gsiftp://machine.com/dir/file.txt - would be relative to the user's
> home directory
> gsiftp://machine.com//dir/file.txt - would be an absolute reference,
> note the double slash
> gsiftp://machine.com/~/dir/file.txt - would be a relative reference,
> as per the first case
>
> This would be consistent with the suggestions from Bruno Harbulot, see:
> http://blog.distributedmatter.net/?post/2006/12/08/gsiftp-URI-madness
>
> Feedback appreciated,
> 	Justin
> --
> Justin Bradley
> Design & Development Team Leader
> j.b...@om...
> OMII-UK
> Suite 3235, Zepler Building (B59)
> University of Southampton



-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

[gridsam-discuss] GridSAM news and gsiftp urls

From: Justin B. <jb...@ec...> - 2008-08-21 18:13:01

Hi All,

For those who don't know me, my name is Justin Bradley and I have  
taken over from Hugo Mills as the release manager for GridSAM.

I have now tagged version 2.0.2 in the sourceforge subversion  
repository.  This version contains all the main fixes and enhancements  
to date as well as the Globus status patch as supplied by Jos  
Koetsier.  I'll publicise builds for this over the coming days.

The second patch from Jos is still pending, the patch works as  
designed, but it has the effect of changing the default interpretation  
of the gsiftp urls.
These are the gsiftp urls as supplied in the JSDL files as used by  
GridSAM, when Globus is being used as a back end.
The change is that by default the path component is now interpreted as  
being an absolute file reference, whereas previously is was considered  
to be relative to the home directory of the user in question.

For example: gsiftp://machine.com/dir/file.txt is now interpreted as  
being /dir/file.txt rather than for example /home/user/dir/file.txt

We have a proposed change to make to this new behaviour, and would  
like feedback from the community on this.

This would be to revert the default to the way it was before, but  
ensure that a reference can explicitly be made absolute or relative,  
and these explicit styles would be encouraged.

gsiftp://machine.com/dir/file.txt - would be relative to the user's  
home directory
gsiftp://machine.com//dir/file.txt - would be an absolute reference,  
note the double slash
gsiftp://machine.com/~/dir/file.txt - would be a relative reference,  
as per the first case

This would be consistent with the suggestions from Bruno Harbulot, see:
http://blog.distributedmatter.net/?post/2006/12/08/gsiftp-URI-madness

Feedback appreciated,
	Justin
--
Justin Bradley
Design & Development Team Leader
j.b...@om...
OMII-UK
Suite 3235, Zepler Building (B59)
University of Southampton

[gridsam-discuss] run-time '...JobDefinition not found ...' bug

From: Vesso N. <ve...@do...> - 2008-08-01 19:17:30

There's a problem with certain GridSAM Client installations.

Symptoms:
Using CLI from the Client side to send a valid JSDL through 
gridsam-submit results in an error returned with the message:
"No jsdl:JobDefinition element can be found in the request. Please check 
your input and the namespace declarations."

Reason:
In the file GridSAMService.java the call to
"...
if(pRequest.selectPath(GridSAMSupport.XPATH_NAMESPACES_DECLARATION 
+          
"/gridsam:submitJob/gridsam:JobDescription/jsdl:JobDefinition").length 
== 0){
..."

fails as the XPath evaluation fails even though the JSDL is valid and 
the JobDefinition element is present.

The failure is caused by the Body part of the SOAP message sent from the 
Client side containing duplicated 'sumbitJob' XML elements
- i.e.  effectively changing the path to the JobDefinition element:

incorrect SOAP:
"
<soapenv:Body wsu:Id="id-29263633" 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <submitJob xmlns="http://www.icenigrid.org/service/gridsam">
      <submitJob>
        <submitJob startSuspended="false" 
xmlns:grid="http://www.icenigrid.org/service/gridsam">
          <JobDescription>
            <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl">
              <JobDescription>
                <Application>
                  <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix">
                    <Executable>/bin/echo</Executable>
                    <Argument>hello world</Argument>
                  </POSIXApplication>
                </Application>
              </JobDescription>
            </JobDefinition>
          </JobDescription>
        </submitJob>
      </submitJob>
    </submitJob>
  </soapenv:Body>
"

correct SOAP:
"
<soapenv:Body wsu:Id="id-4347715" 
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <grid:submitJob startSuspended="false" 
xmlns:grid="http://www.icenigrid.org/service/gridsam">
      <grid:JobDescription>
        <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl">
          <JobDescription>
            <Application>
              <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix">
                <Executable>/bin/echo</Executable>
                <Argument>hello world</Argument>
              </POSIXApplication>
            </Application>
          </JobDescription>
        </JobDefinition>
      </grid:JobDescription>
    </grid:submitJob>
  </soapenv:Body>
"

Cause:
Undetermined yet!

Fix:
Not until the exact cause is determined!
> --
> --------------------------------------------------------------------------------------------------------
> Vesso A. Novov                                   --   Research 
> Assistant   --
> --------------------------------------------------------------------------------------------------------
> London e-Science Centre              http://www.lesc.doc.ic.ac.uk
> Imperial College London, Department of Computing
> 180 Queen's Gate, London SW7 2RH, UK
> tel: +44 (0)207-594-8399                       fax: +44 (0)207-581-8024
> ---------------------------------------------------------------------------------------------------------
>
>

[gridsam-discuss] developer branch SVN updates

From: Vesso N. <ve...@do...> - 2008-08-01 18:38:59

I've committed some of my ongoing work into the LeSC's SVN branch.
NOTE: The code committed is build-able but has not been properly tested:

* Updates/additions/broken-link fixes to the project's web site/user docs.

* Support for the BES-Management Port's two methods.
Note: At the last telecon call we discussed possible security issues with
the open access to this port - I've inserted calls to the GridSAM' 
Athorization system and
I've updated the user docs with an example of how to restrict the access 
to the port's two
methods using '../WEB-INF/classes/authorisaion.xml' config file.


* Support for the latest BES Interface (Factory and Management ports):
 - on the Client side - added new classes to the command-line 
interface/lib, updated to latest
changes of the BES - added Windows .bat scripts for all BES methods.
- on the Server side - support for BES to all DRMs.
- still trying to find a easy way to support BES's getFactoryResource - 
unlike any other it needs to be
executed synchronously - either I need to duplicate a lot of the code or 
find a way to use the existing
but make it switch from asynch to synch just for that method call ???

* Maven pom file updates for XmlBeans 2.3.0 plus needed Saxon parsers; 
JDK 1.5-level build; automatic
build-time Internet download for all .xsd files(so far all needed xsd 
files where included in the source bundle) -
a potential problem source considering Maven 'temper' some time.


* ... there may have been something else I can't recall...

--
--------------------------------------------------------------------------------------------------------
Vesso A. Novov                                   --   Research 
Assistant   --
--------------------------------------------------------------------------------------------------------
London e-Science Centre              http://www.lesc.doc.ic.ac.uk
Imperial College London, Department of Computing
180 Queen's Gate, London SW7 2RH, UK
tel: +44 (0)207-594-8399                       fax: +44 (0)207-581-8024
---------------------------------------------------------------------------------------------------------

Re: [gridsam-discuss] GridSAM to gLite?

From: A.S.McGough <as...@do...> - 2007-12-18 13:01:33

Sorry for the late reply...

There currently is a plan to do a GridSAM DRM connector for gLite. 
Hopefully sometime in the new year it will appear.

steve..

Stefan Zasada wrote:
> Hi,
>
> Is there any way to get GridSAM to submit jobs to gLite? If not, is  
> there any plan to create a gLite DRM connector?
>
> Cheers,
>
>
> Stefan.
>
> --
> Stefan Zasada <ste...@uc...>
> Centre for Computational Science
> Chemistry Department, University College London,
> 20 Gordon Street, London, WC1H 0AJ, UK.
> Tel: +44 (0)20 7679 5300
>
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>   


-- 
------------------------------------------------------------------------
Dr A. Stephen McGough                       http://www.doc.ic.ac.uk/~asm
------------------------------------------------------------------------
Technical Coordinator, London e-Science Centre, Imperial College London,
Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK
tel: +44 (0)207-594-8409                        fax: +44 (0)207-581-8024
------------------------------------------------------------------------

[gridsam-discuss] GridSAM to gLite?

From: Stefan Z. <ste...@uc...> - 2007-11-30 16:18:58

Hi,

Is there any way to get GridSAM to submit jobs to gLite? If not, is  
there any plan to create a gLite DRM connector?

Cheers,


Stefan.

--
Stefan Zasada <ste...@uc...>
Centre for Computational Science
Chemistry Department, University College London,
20 Gordon Street, London, WC1H 0AJ, UK.
Tel: +44 (0)20 7679 5300

Re: [gridsam-discuss] look forward to your help: alway can not submit job to the GridSAM Service

From: Vesselin N. <ve...@do...> - 2007-11-07 17:41:35

Hi there,

It looks the cause of the problem is clearly stated in the log messages:
"
. . .

java.lang.ClassNotFoundException: uk.ac.omii.security.wss4j.handler.WSOutboundHandler

. . .
"
Your environment is not set properly and when you run the gridsam-submit 
shell script
this class(which is within one of the omii*..*jar files in 
OMIICLIENT/lib/) can not be found.
Make sure all *.jar files inside OMIICLIENT/lib directory are on the 
Java -classpath

-Vesso

uk...@st... wrote:

>Hi dear all,
>I have been fighting with Gridsam for days.
>But even still can not submit a helloworld job.
>
>I have tried installing all the software in my local PC.
>But the problem is the same.
>
>OMMII Server: 3.4
>OMII CLIENT: 3.4
>Gridsam Server: 2.0.1
>Gridsam Client: 2.0.1
>
>The following are the Error informations!
>Mega thanks for your help.
>best regards,
>Tian
>PS: Erro Informations:
>zhang@IWR-LIZHE1:~/OMIICLIENT/gridsam/bin> ./gridsam-submit -s 
>https://141.52.7.106:18443/gridsam/services/gridsam?wsdl -j 
>../data/examples/helloworld.jsdl
>
>2007-11-05 21:06:57,928 FATAL [GridSAMSubmit] (main:) unable to submit 
>job: failed to submit                                  job: ; nested 
>exception is:
>        org.apache.axis.ConfigurationException: 
>java.lang.ClassNotFoundException: uk.ac.omii                            
>      .security.wss4j.handler.WSOutboundHandler
>java.lang.ClassNotFoundException: 
>uk.ac.omii.security.wss4j.handler.WSOutboundHandler
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
>        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableIte                                 
>m.java:353)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
>Item.java:295)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
>va:473)
>        at 
>org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
>)
>        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
>        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
>        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>        at org.apache.axis.client.Call.invoke(Call.java:2748)
>        at org.apache.axis.client.Call.invoke(Call.java:1784)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
>idSAMClientSupport.java:337)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
>upport.java:137)
>        at 
>org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
>anager.java:237)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)
>
>org.apache.axis.ConfigurationException: 
>java.lang.ClassNotFoundException: uk.ac.omii.securit                    
>              y.wss4j.handler.WSOutboundHandler
>java.lang.ClassNotFoundException: 
>uk.ac.omii.security.wss4j.handler.WSOutboundHandler
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
>        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableIte                                 
>m.java:353)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
>Item.java:295)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
>va:473)
>        at 
>org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
>)
>        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
>        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
>        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>        at org.apache.axis.client.Call.invoke(Call.java:2748)
>        at org.apache.axis.client.Call.invoke(Call.java:1784)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
>idSAMClientSupport.java:337)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
>upport.java:137)
>        at 
>org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
>anager.java:237)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)
>
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
>Item.java:297)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
>tem.java:274)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
>.java:260)
>        at 
>org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
>va:473)
>        at 
>org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
>)
>        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
>        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
>        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
>        at org.apache.axis.client.Call.invoke(Call.java:2748)
>        at org.apache.axis.client.Call.invoke(Call.java:1784)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
>idSAMClientSupport.java:337)
>        at 
>org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
>upport.java:137)
>        at 
>org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
>anager.java:237)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
>        at 
>org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>_______________________________________________
>GridSAM-Discuss mailing list
>Gri...@li...
>https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>  
>

[gridsam-discuss] look forward to your help: alway can not submit job to the GridSAM Service

From: <uk...@st...> - 2007-11-05 20:17:30

Hi dear all,
I have been fighting with Gridsam for days.
But even still can not submit a helloworld job.

I have tried installing all the software in my local PC.
But the problem is the same.

OMMII Server: 3.4
OMII CLIENT: 3.4
Gridsam Server: 2.0.1
Gridsam Client: 2.0.1

The following are the Error informations!
Mega thanks for your help.
best regards,
Tian
PS: Erro Informations:
zhang@IWR-LIZHE1:~/OMIICLIENT/gridsam/bin> ./gridsam-submit -s 
https://141.52.7.106:18443/gridsam/services/gridsam?wsdl -j 
../data/examples/helloworld.jsdl

2007-11-05 21:06:57,928 FATAL [GridSAMSubmit] (main:) unable to submit 
job: failed to submit                                  job: ; nested 
exception is:
        org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: uk.ac.omii                            
      .security.wss4j.handler.WSOutboundHandler
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableIte                                 
m.java:353)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
Item.java:295)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
va:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
idSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
upport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
anager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: uk.ac.omii.securit                    
              y.wss4j.handler.WSOutboundHandler
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableIte                                 
m.java:353)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
Item.java:295)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
va:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
idSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
upport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
anager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployable                                 
Item.java:297)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableI                                 
tem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem                                 
.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.ja                                 
va:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269                                 
)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(Gr                                 
idSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientS                                 
upport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobM                                 
anager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

[gridsam-discuss] [gridsam] ask for help: can not submit job to the GridSAM Service

From: <uk...@st...> - 2007-10-30 23:00:43

Hi dear all,
I am tring submitting a Job to the GridSam service by following 
"GridSam Quick Start Guide". But failed.
The Error informations are in the last paragraph of this email.

The content of the "submithello.jsdl" file is as following: 
----------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl">
    <JobDescription>
        <Application>
            <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/11/jsdl-posix">
                <Executable>/bin/echo</Executable>
                <Argument>hello world</Argument>
            </POSIXApplication>
        </Application>
    </JobDescription>
</JobDefinition>
-----------------------------------------------------------------------

Thanks for your help.
best regards,
Tianle Zhang

PS: The Error informations:
./gridsam-submit -s 
"http://141.52.7.106:18080/gridsam/services/gridsam" -j 
/home/zhang/submithello.jsdl


2007-10-30 23:40:38,035 FATAL [GridSAMSubmit] (main:) unable to submit 
job: failed to submit job: ; nested exception is:
        org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:353)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:295)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(GridSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientSupport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobManager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
java.lang.ClassNotFoundException: 
uk.ac.omii.security.wss4j.handler.WSOutboundHandler
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:186)
        at java.security.AccessController.doPrivileged(Native Method)
        at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
        at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:353)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:295)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(GridSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientSupport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobManager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:297)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
        at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
        at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
        at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
        at org.apache.axis.client.Call.invoke(Call.java:2748)
        at org.apache.axis.client.Call.invoke(Call.java:1784)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.invokeRemoteOperation(GridSAMClientSupport.java:337)
        at 
org.icenigrid.gridsam.client.common.GridSAMClientSupport.submitJob(GridSAMClientSupport.java:137)
        at 
org.icenigrid.gridsam.client.common.ClientSideJobManager.submitJob(ClientSideJobManager.java:237)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.run(GridSAMSubmit.java:170)
        at 
org.icenigrid.gridsam.client.cli.GridSAMSubmit.main(GridSAMSubmit.java:292)

[gridsam-discuss] Omii + Apache Muse

From: <PO...@gm...> - 2007-10-29 22:48:19

Hello

I try to integrate Apache Muse http://ws.apache.org/muse/ in OMII and try to run the example of the muse tutorial. I deploy the project as a war file, but I cannot access the service. Its because of the security configuration. I dont know how to configure the security issues. I hope someone can help me.

best regards pod
-- 
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! 
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer

Re: [gridsam-discuss] ask for help: can not Run the GridSAM Service

From: Steve C. <s.c...@om...> - 2007-10-25 11:14:37

Hi Tianle,

The scripts Vesso mention are located in the OMII/bin directory.

Cheers
Steve

Vesselin Novov wrote:
> Tianle,
> The files to start and stop the container are:
> 'startomii.sh' and 'stopomii.sh'
>
> -Vesso
>
> uk...@st... wrote:
>
>   
>> Hi, it is me again.
>> forgot to say: OMII Server and Client are verion 3.4.0
>> Gridsam server and client are version 2.0.1
>> thanks for help
>> regards,
>> Tianle Zhang
>>
>>
>>
>>
>> Quoting uk...@st...:
>>
>>     
>>> dear all,
>>> I have installed the OMII Server and Client, Gridsam Server and 
>>> Client by following the steps of "GridSAM Quick Start Guide".
>>> But I can not run the Gridsam service.
>>> The following are shown in the steps "GridSAM Quick Start Guide"-> 
>>> "Running the GridSAM Service":
>>> -----------------------------------------------------------------
>>> Running the GridSAM Service
>>> Restart the OMII container after the installation has completed.
>>>
>>> $> cd ${OMII_HOME}/jakarta-tomcat-5.0.25/bin
>>> $> ./start_base.sh
>>> Starting up tomcat
>>> Using CATALINA_BASE:   /usr/local/OMII/jakarta-tomcat-5.0.25
>>> Using CATALINA_HOME:   /usr/local/OMII/jakarta-tomcat-5.0.25
>>> Using CATALINA_TMPDIR: /usr/local/OMII/jakarta-tomcat-5.0.25/temp
>>> Using JAVA_HOME:       /usr/local/jdk1.4
>>> Waiting....!....!.... Started.
>>> $>
>>> ------------------------------------------------------------------
>>>
>>> But I have not found the file "start_base.sh".
>>> The other file "startup.sh" was already been tried, but the Gridsam 
>>> service still seemed to be deployed unsuccessfully.
>>>
>>>
>>> How can I deploy and run the GridSam serive.
>>>
>>> Thanks for your help.
>>> best regards,
>>> Tianle Zhang
>>>
>>>
>>>
>>>
>>>       
>>
>>
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >> http://get.splunk.com/
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> GridSAM-Discuss mailing list
>> Gri...@li...
>> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>>  
>>
>>     
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>   

-- 
--
Dr Stephen Crouch
Technology & Commissioned Software Team Leader
Open Middleware Infrastructure Institute UK (OMII-UK)
Suite 6005, Building 21 (Faraday)
University of Southampton
S017 1BJ
Email: s.c...@om...
WWW  : http://www.ecs.soton.ac.uk/~stc

Re: [gridsam-discuss] ask for help: can not Run the GridSAM Service

From: Vesselin N. <ve...@do...> - 2007-10-25 11:08:15

Tianle,
The files to start and stop the container are:
'startomii.sh' and 'stopomii.sh'

-Vesso

uk...@st... wrote:

> Hi, it is me again.
> forgot to say: OMII Server and Client are verion 3.4.0
> Gridsam server and client are version 2.0.1
> thanks for help
> regards,
> Tianle Zhang
>
>
>
>
> Quoting uk...@st...:
>
>> dear all,
>> I have installed the OMII Server and Client, Gridsam Server and 
>> Client by following the steps of "GridSAM Quick Start Guide".
>> But I can not run the Gridsam service.
>> The following are shown in the steps "GridSAM Quick Start Guide"-> 
>> "Running the GridSAM Service":
>> -----------------------------------------------------------------
>> Running the GridSAM Service
>> Restart the OMII container after the installation has completed.
>>
>> $> cd ${OMII_HOME}/jakarta-tomcat-5.0.25/bin
>> $> ./start_base.sh
>> Starting up tomcat
>> Using CATALINA_BASE:   /usr/local/OMII/jakarta-tomcat-5.0.25
>> Using CATALINA_HOME:   /usr/local/OMII/jakarta-tomcat-5.0.25
>> Using CATALINA_TMPDIR: /usr/local/OMII/jakarta-tomcat-5.0.25/temp
>> Using JAVA_HOME:       /usr/local/jdk1.4
>> Waiting....!....!.... Started.
>> $>
>> ------------------------------------------------------------------
>>
>> But I have not found the file "start_base.sh".
>> The other file "startup.sh" was already been tried, but the Gridsam 
>> service still seemed to be deployed unsuccessfully.
>>
>>
>> How can I deploy and run the GridSam serive.
>>
>> Thanks for your help.
>> best regards,
>> Tianle Zhang
>>
>>
>>
>>
>
>
>
>
>------------------------------------------------------------------------
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >> http://get.splunk.com/
>
>------------------------------------------------------------------------
>
>_______________________________________________
>GridSAM-Discuss mailing list
>Gri...@li...
>https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>  
>

Re: [gridsam-discuss] ask for help: can not Run the GridSAM Service

From: <uk...@st...> - 2007-10-24 19:51:46

Hi, it is me again.
forgot to say: OMII Server and Client are verion 3.4.0
Gridsam server and client are version 2.0.1
thanks for help
regards,
Tianle Zhang




Quoting uk...@st...:

> dear all,
> I have installed the OMII Server and Client, Gridsam Server and 
> Client by following the steps of "GridSAM Quick Start Guide".
> But I can not run the Gridsam service.
> The following are shown in the steps "GridSAM Quick Start Guide"-> 
> "Running the GridSAM Service":
> -----------------------------------------------------------------
> Running the GridSAM Service
> Restart the OMII container after the installation has completed.
>
> $> cd ${OMII_HOME}/jakarta-tomcat-5.0.25/bin
> $> ./start_base.sh
> Starting up tomcat
> Using CATALINA_BASE:   /usr/local/OMII/jakarta-tomcat-5.0.25
> Using CATALINA_HOME:   /usr/local/OMII/jakarta-tomcat-5.0.25
> Using CATALINA_TMPDIR: /usr/local/OMII/jakarta-tomcat-5.0.25/temp
> Using JAVA_HOME:       /usr/local/jdk1.4
> Waiting....!....!.... Started.
> $>
> ------------------------------------------------------------------
>
> But I have not found the file "start_base.sh".
> The other file "startup.sh" was already been tried, but the Gridsam 
> service still seemed to be deployed unsuccessfully.
>
>
> How can I deploy and run the GridSam serive.
>
> Thanks for your help.
> best regards,
> Tianle Zhang
>
>
>
>

[gridsam-discuss] ask for help: can not Run the GridSAM Service

From: <uk...@st...> - 2007-10-24 19:33:24

dear all,
I have installed the OMII Server and Client, Gridsam Server and Client 
by following the steps of "GridSAM Quick Start Guide".
But I can not run the Gridsam service.
The following are shown in the steps "GridSAM Quick Start Guide"-> 
"Running the GridSAM Service":
-----------------------------------------------------------------
Running the GridSAM Service
Restart the OMII container after the installation has completed.

$> cd ${OMII_HOME}/jakarta-tomcat-5.0.25/bin
$> ./start_base.sh
Starting up tomcat
Using CATALINA_BASE:   /usr/local/OMII/jakarta-tomcat-5.0.25
Using CATALINA_HOME:   /usr/local/OMII/jakarta-tomcat-5.0.25
Using CATALINA_TMPDIR: /usr/local/OMII/jakarta-tomcat-5.0.25/temp
Using JAVA_HOME:       /usr/local/jdk1.4
Waiting....!....!.... Started.
$>
------------------------------------------------------------------

But I have not found the file "start_base.sh".
The other file "startup.sh" was already been tried, but the Gridsam 
service still seemed to be deployed unsuccessfully.


How can I deploy and run the GridSam serive.

Thanks for your help.
best regards,
Tianle Zhang

Re: [gridsam-discuss] Question on Gridsam/Globus and POSIXApplicationType

From: A.S.McGough <as...@do...> - 2007-10-22 01:07:24

Dear Peter,

Here is a link 
[http://gridsam.sourceforge.net/2.0.1/gridsam-service/deploymentguide.html] 
to the GridSAM deployment guide which includes a whole section on using 
it with Globus 2.4.3. I'm afraid you'll need to look at the Globus 
website for info on installing Globus. I'm not surprised you had 
problems finding this page - it took me a while to find it and I knew it 
was there.

Vesso - any idea why this isn't in the main menu?

The POSIXapplication is a sub-element of the Application element - to be 
exact it fits into the xsd#amy element of Application. First you need to 
create an Application element and place this in the JobDescription 
element and then create a POSIXapplication element and place this into 
the Application element.

As for CVS access look at :

http://gridsam.sourceforge.net/2.0.1/gridsam-client/source-repository.html

Hope this helps,

steve..

PO...@gm... wrote:
> Hello
>
> - I installed Omii and I read that its possible to use gsiftp and gram of globus toolkit. What do I have to install/configure to use this? Is there a any faq where its described step by step what to do?
>
> - I try to create a jsdl with java but I dont know how I can add the POSIXApplicationType to the JobDescriptionType is this not supported? JobDescriptionType expects an  ApplicationType and a cast from POSIXApplicationType to ApplicationType fails. 
> I am also looking for the source code of these files but I couldnt find them are they available somewhere at http://gridsam.cvs.sourceforge.net?
>
> thank you peter
>
>
>
>   

-- 
------------------------------------------------------------------------
Dr A. Stephen McGough                       http://www.doc.ic.ac.uk/~asm
------------------------------------------------------------------------
Technical Coordinator, London e-Science Centre, Imperial College London,
Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK
tel: +44 (0)207-594-8409                        fax: +44 (0)207-581-8024
------------------------------------------------------------------------

[gridsam-discuss] Question on Gridsam/Globus and POSIXApplicationType

From: <PO...@gm...> - 2007-10-19 16:27:54

Hello

- I installed Omii and I read that its possible to use gsiftp and gram of globus toolkit. What do I have to install/configure to use this? Is there a any faq where its described step by step what to do?

- I try to create a jsdl with java but I dont know how I can add the POSIXApplicationType to the JobDescriptionType is this not supported? JobDescriptionType expects an  ApplicationType and a cast from POSIXApplicationType to ApplicationType fails. 
I am also looking for the source code of these files but I couldnt find them are they available somewhere at http://gridsam.cvs.sourceforge.net?

thank you peter



-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

2 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 2 3 4 5 6 .. 10 > >> (Page 4 of 10)