Page History

...

private String title;  // scenario title
private String description;  // scenario description
private Set<DatasetBean> dataSetsDate date = new Date();  // datasets associated with scenario date scenario created
private PersonBean creator;  // scenario creator
private RMIServiceBeanSet<DatasetBean> serviceBeandataSets;  // rmidatasets serviceassociated used to launch workflowswith scenario
private List<WorkflowBean> workflows;  // workflows associated with this scenario
private, booleanif open;possible, this //needs isto thebe scenarioable openedto or closed?
private PersonBean creator;  // scenario creator
private Date date;  // date scenario createdwrap ptpflow workflow xml files, or we need our own bean type

This scenario bean will evolve as the application framework is built and more final documentation will be put here as the design matures. The main parts of this bean are: DatasetBean's will be used to manage all of the input/output datasets , the RMIServiceBean (described later) will contain the service information and the WorkflowBean List will contain the workflows associated with this scenario. A user might extend the ScenarioBean if their application has other things that logically belong to their scenarios, but this is unlikely. Most changes will happen at the metadata level (e.g. this dataset is a mesh, a result, etc).

Dataset Bean

This section is intended to talk about the types of concepts that the Ontology needs to capture. We will break this into two parts: general framework concepts (e.g. result) and eAIRS specific (e.g. mesh). We don't anticipate any changes to the DatasetBean class that is provided as part edu.uiuc.ncsa.cet.bean plug-in.

General Framework Metadata

eAIRS Metadata

Workflows Bean

Each workflow is described in an XML file that outlines the steps in the process including which resource to run on, executables that will be launched, input files to use, etc. Initially, we will simply store the workflow information in a single WorkflowStepBean that has a reference to the file containing the xml and the DatasetBeans. Ogrescript xml files can be complex, but if we can logically separate out the steps or parts into individual beans that can be used to generate the full workflow xml file required by the HPC machines, then we can include workflow steps as separate beans and provide a UI for adding steps dynamically.

...