[
https://issues.apache.org/jira/browse/AIRAVATA-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13612408#comment-13612408
]
Subho Banerjee commented on AIRAVATA-798:
-----------------------------------------
Hi,
I have been studying this topic (in view of making a proposal at GSoC'13) and
peeking into some of the Airavata code that might be relevant. I see a solution
to the problem as decomposed into the following -
1. An interpreter for WSDL, so the code which we write integrates directly with
the API which XBaya is using right now. There is freedom to choose to do this
either purely in Javascript(frontend) or with a Java/Scala based backend built
with something similar to the http://www.playframework.com/.
2. The actual HTML5 based frontend which is used to design and deploy
workflows. As Andun pointed out, there are some nice alternatives to pick from
(jQueryUI and jsPlumb seems a good alternative), or maybe something that uses
the HTML5 Canvas itself like RaphaelJS (http://raphaeljs.com/)
3. Add any new calls to the Airavata API as required by the new frontend. Also
side - by - side look at methods of expressing the workflow slightly
differently from what it is now using a series of messages based off WSDL. To
maybe a more abstract(JSON/REST) which makes design of the frontend a little
easier. So, the backend from (1) can probably translate from the WSDL
representation to the new one and back again.
Am I missing something here? Or can some more features be added to this?
> [GSoC] Web based Workflow Composer for Airavata
> ------------------------------------------------
>
> Key: AIRAVATA-798
> URL: https://issues.apache.org/jira/browse/AIRAVATA-798
> Project: Airavata
> Issue Type: New Feature
> Components: Workflow Interpreter, XBaya
> Reporter: Suresh Marru
> Labels: gsoc2013, mentor
>
> Apache Airavata users construct workflows by chaining together set of
> applications and web services resulting in a graphical representation of
> workflows. These workflows composed by drag and drop features build a
> abstract and high lever workflow languages.Currently Airavata XBaya services
> these needs and is implemented in Java Swing. Similarly XBaya was also
> implemented in Flex.
> This project focuses on developing a web based version of the workflow
> composition and monitoring interface similar in functionality to XBaya.
> Currently XBaya WSDL operations and message type definition determines both
> the number of input/output parameters that the component has and the data
> type of each parameter. Messages are general XML and can have deeply-nested
> structures. However, XBaya treats the child elements of the root of a
> message as independent parameters. The type of each parameter can be any
> simple type (string, integer, etc.), array, or a complex type. The potential
> student can evaluate the use of WSDL and come up with alternatives.
> The student for this task has to be prepared to work extensively in java
> script to build the drag drop interface. WSDL knowledge will be preferred but
> not mandatory, that can be acquired.
> User community & Impact of the software: Airavata is a general purpose
> distributed systems software. It is used to build science gateways supporting
> research and education in chemistry, life sciences, biophysics, environmental
> sciences, geosciences astronomy and nuclear physics. The goal of airavata is
> to enhance productivity of these gateways to utilize cyberinfrastructure of
> resources (e.g., local lab resources, the Extreme Science and Engineering
> Discovery Environment (XSEDE), the Open Science Grid (OSG), University
> Clusters, Academic and Commercial Computational Clouds like FutureGrid &
> Amazon EC2). By using open community based software components and services
> like Airavata, gateways will be able to focus on providing additional
> scientific capabilities and to expanding the number of supported users. The
> capabilities of these gateways will offer clear benefits to society.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
