[kepler-users] Globus jobs/Grid FTP on Kepler

Christopher Brooks cxh at eecs.berkeley.edu
Mon Nov 13 07:37:30 PST 2006


BTW There is some makefile code for signing jars in ptII/mk/jnlp.mk

The commands to create the keystore are:

   "/usr/bin/keytool" -genkey \
	-dname "CN=Claudius Ptolemaus, OU=Your Project, O=Your University, L=Your Town, S=Your State, C=US " \
	-keystore ptKeystore \
	-alias claudius \
	-storepass this.is.the.storePassword,change.it \
	-keypass this.is.the.keyPassword,change.it

   "/usr/bin/keytool" -selfcert \
	-keystore ptKeystore \
	-alias claudius \
	-storepass this.is.the.storePassword,change.it \
	-keypass this.is.the.keyPassword,change.it

   "/usr/bin/keytool" -list \
	-keystore ptKeystore \
	-storepass this.is.the.storePassword,change.it

To sign a jar:

"/usr/bin/jarsigner" \
		-keystore ptKeystore \
		-storepass this.is.the.storePassword,change.it \
		-keypass this.is.the.keyPassword,change.it \
		foo.jar claudius

_Christopher
--------

    Yeah, as I said in my earlier email, I didn't think these actors were 
    working. Looks like the jars need to be signed, but I'm not sure how it 
    works -- not something I've focused on. The folks at NMI that developed 
    the actor haven't updated them, while others have developed grid support 
    for some of the newer globus releases.  I think Jagan from the Griddles 
    project might have developed something more recent.  Hopefully either 
    Jagan or Ilkay can comment on whether there are Globus 4 actors available.
    
    Good luck,
    Matt
    
    Terry.Rankine at csiro.au wrote:
    > Hi Matt
    > 
    > I downloaded the sample workflow you sent me.
    > 
    > It looks like a globus 2 job - I was hoping for a globus 4 (ws based)
    > example.
    > 
    > I also get these errors when I try and launch the job.
    > 
    > Terry Rankine
    > 
    > 
    > ptolemy.kernel.util.IllegalActionException:   in
    > .nmiworkflow-example.manager
    > Because:
    > JCE cannot authenticate the provider BC
    > 	at ptolemy.actor.Manager.execute(Manager.java:386)
    > 	at ptolemy.actor.Manager.run(Manager.java:987)
    > 	at ptolemy.actor.Manager$3.run(Manager.java:1028)
    > Caused by: java.lang.SecurityException: JCE cannot authenticate the
    > provider BC
    > 	at javax.crypto.Cipher.getInstance(DashoA12275)
    > 	at javax.crypto.Cipher.getInstance(DashoA12275)
    > 	at org.globus.gsi.OpenSSLKey.getCipher(OpenSSLKey.java:341)
    > 	at org.globus.gsi.OpenSSLKey.decrypt(OpenSSLKey.java:208)
    > 	at org.globus.gsi.OpenSSLKey.decrypt(OpenSSLKey.java:187)
    > 	at edu.sdsc.globusproxy.ProxyInitTool.loadKey(Unknown Source)
    > 	at edu.sdsc.globusproxy.ProxyInitTool.createProxy(Unknown
    > Source)
    > 	at org.nmiworkflow.GlobusProxy.fire(GlobusProxy.java:187)
    > 	at ptolemy.actor.AtomicActor.iterate(AtomicActor.java:327)
    > 	at
    > ptolemy.actor.sched.StaticSchedulingDirector.fire(StaticSchedulingDirect
    > or.java:170)
    > 	at ptolemy.actor.CompositeActor.fire(CompositeActor.java:330)
    > 	at ptolemy.actor.Manager.iterate(Manager.java:613)
    > 	at ptolemy.actor.Manager.execute(Manager.java:322)
    > 	... 2 more
    > Caused by: java.util.jar.JarException:
    > file:/C:/kepler-1.0.0beta2/lib/jar/jce-jdk13-117.jar is not signed.
    > 	at javax.crypto.SunJCE_d.b(DashoA12275)
    > 	at javax.crypto.SunJCE_d.a(DashoA12275)
    > 	at javax.crypto.SunJCE_d.a(DashoA12275)
    > 	at javax.crypto.SunJCE_b.b(DashoA12275)
    > 	at javax.crypto.SunJCE_b.a(DashoA12275)
    > 	... 15 more
    > Caused by: java.lang.SecurityException: JCE cannot authenticate the
    > provider BC
    > 	at javax.crypto.Cipher.getInstance(DashoA12275)
    > 	at javax.crypto.Cipher.getInstance(DashoA12275)
    > 	at org.globus.gsi.OpenSSLKey.getCipher(OpenSSLKey.java:341)
    > 	at org.globus.gsi.OpenSSLKey.decrypt(OpenSSLKey.java:208)
    > 	at org.globus.gsi.OpenSSLKey.decrypt(OpenSSLKey.java:187)
    > 	at edu.sdsc.globusproxy.ProxyInitTool.loadKey(Unknown Source)
    > 	at edu.sdsc.globusproxy.ProxyInitTool.createProxy(Unknown
    > Source)
    > 	at org.nmiworkflow.GlobusProxy.fire(GlobusProxy.java:187)
    > 	at ptolemy.actor.AtomicActor.iterate(AtomicActor.java:327)
    > 	at
    > ptolemy.actor.sched.StaticSchedulingDirector.fire(StaticSchedulingDirect
    > or.java:170)
    > 	at ptolemy.actor.CompositeActor.fire(CompositeActor.java:330)
    > 	at ptolemy.actor.Manager.iterate(Manager.java:613)
    > 	at ptolemy.actor.Manager.execute(Manager.java:322)
    > 	at ptolemy.actor.Manager.run(Manager.java:987)
    > 	at ptolemy.actor.Manager$3.run(Manager.java:1028)
    > Caused by: java.util.jar.JarException:
    > file:/C:/kepler-1.0.0beta2/lib/jar/jce-jdk13-117.jar is not signed.
    > 	at javax.crypto.SunJCE_d.b(DashoA12275)
    > 	at javax.crypto.SunJCE_d.a(DashoA12275)
    > 	at javax.crypto.SunJCE_d.a(DashoA12275)
    > 	at javax.crypto.SunJCE_b.b(DashoA12275)
    > 	at javax.crypto.SunJCE_b.a(DashoA12275)
    > 	... 15 more
    > 
    > 
    > -----Original Message-----
    > From: kepler-users-bounces at ecoinformatics.org
    > [mailto:kepler-users-bounces at ecoinformatics.org] On Behalf Of Matthew
    > Jones
    > Sent: Friday, 10 November 2006 1:07 AM
    > To: M Chandrasekaran
    > Cc: kepler-users at ecoinformatics.org
    > Subject: Re: [kepler-users] Globus jobs/Grid FTP on Kepler
    > 
    > Hi,
    > 
    > The globus actors have to be used in a particular sequence, which is 
    > demonstrated in the test workflow 
    > "workflows/test/nmiworkflow-example.xml".  This file is only available 
    > in the development version of Kepler, not in the beta releases. (You can
    > 
    > also get it fro the web here:
    > http://cvs.ecoinformatics.org/cvs/cvsweb.cgi/~checkout~/kepler/workflows
    > /test/nmiworkflow-example.xml?content-type=text/plain 
    > 
    > 
    > If you open that file, you'll see that the Globus proxy actor is 
    > connected to the globus job actor and the grid ftp actor (and provides 
    > the proxy credentials).  You have to configure the proxy actor to 
    > provide your proxy certificate information, which has to be locally 
    > available on the local host (in the configuraiton dialog, it asks you to
    > 
    > browse to your cert files).  The proxy actor output is connected to the 
    > input string of the globus actor (providing the proxy certificate).
    > 
    > One caveat is that I am not sure if these actors are working at all. 
    > There are new versions of the globus libraries and I'm not sure what 
    > version is being used here -- if it works for you I'd really like to 
    > know about it.  Thanks.
    > 
    > Matt
    > 
    > M Chandrasekaran wrote:
    >> Hello friends,
    >>
    >> I'm new to Kepler, and have been able to generate workflows using web
    >> services. I need help in using the Globus job actor and Grid ftp.
    >>
    >> I donot understand the inputs, like for globus job actor whats a
    > trigger
    >> and whats the other string input for.
    >>
    >> I get this message as an output from globus actor :
    >>
    >> Caught exception : GSSException: Defective credential detected [Root
    > error
    >> message: No certificates loaded] [Root exception is
    >> org.globus.gsi.GlobusCredentialException: No certificates loaded]
    >>
    >>
    >> I gave the globus-hostname as rsl string and gave the hostname. I have
    > my
    >> certificate in that host.
    >>
    >> What arer the string and trigger inputs ?
    >>
    >> Please direrct me to examples of globus and grid ftp .
    >>
    >> Regards,
    >> M Chandrasekaran
    >>
    >> +^^^+^^^+^^^+^^^+^^^+
    >> The superior man is modest in his speech but exceeds in his actions.
    >> --Confucius
    >>
    >>
    >>
    >>
    > _______________________________________________
    > Kepler-users mailing list
    > Kepler-users at ecoinformatics.org
    > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-use
    > rs
    > 
    > 
    _______________________________________________
    Kepler-users mailing list
    Kepler-users at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
--------



More information about the Kepler-users mailing list