Hi Neha,

First of all, I haven't seen anyone working on workflow simulation in Eclipse before. Your work is very interesting. May I know why you want to do it? I guess you are not just replacing Kepler GUI with another GUI, right?

The code of master-slave module is done long time ago. So my information on the interfaces below is just my best guess. You have to verify its correctness.

1) How do I add slaves? At the construction function of org.kepler.distributed.MasterController class, it tries to read available slaves.

2) How do I allow/deny Access? The function processUserInACL() in org.kepler.distributed.SlaveController class will check whether the user is allowed or denied.


Best wishes

Sincerely yours

Jianwu Wang, Ph.D.
[email protected]
http://users.sdsc.edu/~jianwu/

Assistant Project Scientist
Scientific Workflow Automation Technologies (SWAT) Laboratory
San Diego Supercomputer Center
University of California, San Diego
San Diego, CA, U.S.A.


On 3/5/12 4:18 AM, Neha Sharma wrote:

Hi,

I have successfully implemented the remote workflow using Kepler's GUI. I am now trying to implement the remote workflow by writing a simple Java code in Eclipse.

The reason of doing so is that I want to create a new User Interface and not use the existing swing UI. When writing the code to create the remote workflow I face the following problems:

1.How do I add slaves? (In Kepler I could do this by clicking Tools->Distributed Computing Options)

2. How do I allow/deny Access? (Clicking Tools->Distributed User Access Configuration helped me with the access configurations in Kepler.)

Which API’s should I use to add slaves and configure their access? I intend to simulate the entire workflow in Eclipse. Please help.

Regards,

Neha Sharma

DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.



_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev

Reply via email to