Greg McChesney

1

Task Initiation Panel for SORCER Environment

• Greg McChesney
• Communication Networks
• Computer Science, TTU
• Greg.mcchesney_at_ttu.edu

2
Overall Presentation Goal or Primary Purpose
Create a user interface which allows the user to
create a task or job. The interface will allow
the user to modify the context prior to launching
the job.
Beginning
3
Learning Objectives

• As a result of this presentation, you will be
  able to
• Modify a context in SORCER
• Launch a service in SORCER
• View returned context from the service

Beginning
4
Speakers Qualifications

• Greg McChesney is a graduate student at TTU
• Greg McChesney is planning to graduate in May of
  2009 with a Masters in Computer Science
• Greg McChesney thesis is on Cataloger and
  creating contexts and jobs in SORCER

Beginning
5
Did you know?
There are currently not GUI tools, in SORCER, for
creating Task, Jobs or Contexts.
Beginning
6
Presentation Agenda

• Why do we need a Task Editor?
• What is a Context?
• Why edit the context before launching the Task?
• Outcome of a Task
• Implementation Issues Encountered
• Demo
• Future Additions Planned

Beginning
7
Need for a Task Editor

• No common graphical method of creating tasks in
  SORCER
• Each provider must have own GUI interface
• Users must learn each providers interface
• Provide easier development of new services
• No method for creating Jobs
• No method for saving and reusing Jobs.

Middle
8
All About Contexts

• A Context is a set of instructions for a
  provider.
• The context various depending on the provider and
  the method being executed.
• Contexts can specify anything about a provider
• Example
• The context for makeDeposit in the AccountTester
  is deposit/amountamount

9
Edit the Context?

• Why would we want to edit the Context before we
  launch the Task?
• The Context can often described input variables
  that are not static, editing it allows us to
  change them.
• Example The AccountTester would be useless if
  you could not specify how much you were
  depositing or withdrawing.

10
Output of the Task

• Tasks return a Context for their output
• In the case of a simple Task the output is
  returned the user
• In a Job the output is used as input for the next
  Task

11
Implementation Issues

• Due to various time constraints and
  implementation issues some sections do not work.
• List View didnt get time to finish it
• Launch Service doesnt actually launch it Bug
  in ServiceTask.exert where provider is not found,
  disabled the exert code to show what it would
  look like if it worked.

12
(No Transcript)
13
Future Additions Planned

• Fix Launch Service
• Create section to make, save and load a Job
• Fix List View
• Add save Context
• Code cleanup and documentation
• Separate from Cataloger Service

14
Summary

• Benefits of Task Creation Panel
• Simplified user interface
• Less work for new provider creators
• In combination with new Cataloger will provide
• Complete Context Management
• Task Initiation
• Job Initiation

End
15
(No Transcript)