airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r796560 - in /websites/staging/airavata/trunk/content/airavata: ./ about/ architecture/ community/ community/governance/ development/ documentation/gfac/ documentation/messenger/ documentation/registry/ documentation/system/ documentation/w...
Date Tue, 04 Oct 2011 17:48:44 GMT
Author: buildbot
Date: Tue Oct  4 17:48:43 2011
New Revision: 796560

Log:
Staging update by buildbot

Added:
    websites/staging/airavata/trunk/content/airavata/architecture/
    websites/staging/airavata/trunk/content/airavata/architecture/airavata-registry.png   (with props)
    websites/staging/airavata/trunk/content/airavata/architecture/airavata.png   (with props)
    websites/staging/airavata/trunk/content/airavata/architecture/messenger-overview.png   (with props)
    websites/staging/airavata/trunk/content/airavata/architecture/overview.html
    websites/staging/airavata/trunk/content/airavata/architecture/registry.html
    websites/staging/airavata/trunk/content/airavata/architecture/workflow-suite.png   (with props)
    websites/staging/airavata/trunk/content/airavata/architecture/workflow.html
    websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html
Modified:
    websites/staging/airavata/trunk/content/airavata/about/history.html
    websites/staging/airavata/trunk/content/airavata/about/license.html
    websites/staging/airavata/trunk/content/airavata/community/get-involved.html
    websites/staging/airavata/trunk/content/airavata/community/governance/consensusBuilding.html
    websites/staging/airavata/trunk/content/airavata/community/governance/lazyConsensus.html
    websites/staging/airavata/trunk/content/airavata/community/governance/voting.html
    websites/staging/airavata/trunk/content/airavata/community/mailing-lists.html
    websites/staging/airavata/trunk/content/airavata/community/people.html
    websites/staging/airavata/trunk/content/airavata/development/build.html
    websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html
    websites/staging/airavata/trunk/content/airavata/development/source.html
    websites/staging/airavata/trunk/content/airavata/documentation/gfac/gfac.html
    websites/staging/airavata/trunk/content/airavata/documentation/messenger/ws-messenger.html
    websites/staging/airavata/trunk/content/airavata/documentation/registry/xregistry.html
    websites/staging/airavata/trunk/content/airavata/documentation/system/overview.html
    websites/staging/airavata/trunk/content/airavata/documentation/workflow/xbaya.html
    websites/staging/airavata/trunk/content/airavata/index.html
    websites/staging/airavata/trunk/content/airavata/tools/devtools.html

Modified: websites/staging/airavata/trunk/content/airavata/about/history.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/about/history.html (original)
+++ websites/staging/airavata/trunk/content/airavata/about/history.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>
@@ -92,7 +93,7 @@ Cyberinfrastructure systems to enable fa
 LEAD goals required to create a dynamically adaptive, on-demand, grid-enabled workflow system 
 supporting long running applications and on-demand computing. LEAD has subsequently produced close 
 to 450 research publications combined in all disciplines. The resulting software framework was built 
-on the concepts of service oriented architectures powering the LEAD Gateway Portal~cite{leadportal}. </p>
+on the concepts of service oriented architectures powering the LEAD Gateway Portal.</p>
 <h2 id="open_gateway_computing_environments">Open Gateway Computing Environments</h2>
 <p>The <a href="http://ogce.org">Open Gateway Computing Environments (OGCE)</a> adopted the LEAD workflow suite 
 generalized, enhanced, tested and maintained the software evolving into the OGCE workflow suite. 

Modified: websites/staging/airavata/trunk/content/airavata/about/license.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/about/license.html (original)
+++ websites/staging/airavata/trunk/content/airavata/about/license.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Added: websites/staging/airavata/trunk/content/airavata/architecture/airavata-registry.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/airavata/trunk/content/airavata/architecture/airavata-registry.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/airavata/trunk/content/airavata/architecture/airavata.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/airavata/trunk/content/airavata/architecture/airavata.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/airavata/trunk/content/airavata/architecture/messenger-overview.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/airavata/trunk/content/airavata/architecture/messenger-overview.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/airavata/trunk/content/airavata/architecture/overview.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/overview.html (added)
+++ websites/staging/airavata/trunk/content/airavata/architecture/overview.html Tue Oct  4 17:48:43 2011
@@ -0,0 +1,143 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <link href="/airavata/css/airavata.css" rel="stylesheet" type="text/css">
+  <title>Airavata Gateway Framework</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="banner">
+    <img id="logo" alt="Apache airavata (Incubating)" src="/airavata/images/airavata-logo.png"/>
+    <div id="bannertext">
+      <img id="logo-text"  alt="Apache airavata (Incubating)" src="/airavata/images/airavata-text.png" />
+      </div><br />
+  </div>
+  
+  <div id="navigation">
+  <h1 id="about_airavata">About Airavata</h1>
+<ul>
+<li><a href="/airavata/index.html">Home</a></li>
+<li><a href="http://incubator.apache.org/projects/airavata.html">Incubator Page</a></li>
+<li><a href="/airavata/about/license.html">License</a></li>
+<li><a href="/airavata/about/history.html">History</a></li>
+</ul>
+<h1 id="architecture">Architecture</h1>
+<ul>
+<li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/airavata/community/get-involved.html">Get Involved</a></li>
+<li><a href="/airavata/community/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/airavata/community/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/airavata/development/source.html">Source Code</a></li>
+<li><a href="/airavata/development/build.html">Build Instructions</a></li>
+<li><a href="https://issues.apache.org/jira/browse/airavata">Issue Tracker</a></li>
+<li><a href="/airavata/development/roadmap.html">Road Map</a></li>
+<li><a href="/airavata/tools/devtools.html">Dev Tools</a></li>
+<li><a href="/airavata/development/edit-cms-website.html">Editing Website</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/airavata/documentation/system/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/documentation/messenger/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/documentation/workflow/xbaya.html">XBaya</a></li>
+<li><a href="/airavata/documentation/gfac/gfac.html">GFac</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+    <a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/airavata/images/apache-incubator-logo.png" width="150"/>
+    </a>
+  </div>
+
+  <div id="content">
+    <h1 class="title">Airavata Gateway Framework</h1>
+    <p>Apache Airavata is a software toolkit with features to compose, manage, execute, and monitor small
+to large scale applications and workflows on computational resources ranging from local clusters to 
+national grids and computing clouds. </p>
+<p>Airavata builds on general concepts of service oriented computing, distributed messaging, and 
+workflow composition and orchestration. The services primarly communicate using SOAP messages. 
+In addition to the basic Web services specifications like SOAP and WSDL, the Web services also 
+support WS-Addressing and WS-Messaging. WS-Addressing is used to provide an asynchronous 
+communication mechanism for the services to communicate. All the communication channels are secured 
+using https as the transport layer.</p>
+<p>Airavata features Dynamic Service Binding where in a proxy service accepts an input message intended
+to a target application Web service instance invoked by a workflow engine. The proxy service binds 
+an appropriate running Web service instance by looking up in XRegistry. When no Web service 
+instances are available, a new instance of the GFac service is created.</p>
+<p>Airavata's primary goal is to support long running applications and workflows on distributed computational resources. 
+The architecture is designed to be modular, componentized 
+software framework as illustrated in the following Figure. The goal of the Airavata framework is minimalist 
+architectural design (i.e., a thin layer), a conceptually simple to understand architecture; and easier to install, 
+maintain and use. Its salient feature includes using components by themselves or as an integrated solution.</p>
+<p><img alt="Airavata Overview" src="/airavata/architecture/airavata.png" title="Airavata Overview" /></p>
+<h2 id="airavata_features">Airavata Features</h2>
+<ul>
+<li>desktop tools and browser-based web interface components for managing applications, workflows and generated data. </li>
+<li>sophisticated server-side tools for registering and managing scientific applications on computational resources. </li>
+<li>graphical user interfaces to construct, execute, control, manage and reuse of scientific workflows.</li>
+<li>interfacing and interoperability with with various external (third party) data, workflow and provenance management tools.</li>
+</ul>
+<h2 id="airavata_components">Airavata Components</h2>
+<ul>
+<li>XBaya Workflow Suite - includes a GUI for workflow composition and monitoring. The workflows can be 
+interpreted at each step providing dynamic interactive capabilities. The composed workflow can be 
+exported to various workflow languages like BPEL, SCUFL, Condor DAG, Jython and Java. 
+The defacto workflow enacting engine used is Airavata Workflow Engine. In the future, it will be Apache ODE.</li>
+<li>GFac - an application wrapper service that can be used to wrap command line-driven science 
+applications and make them into robust, network- accessible services. This component is build on 
+Axis2 web service stack. 
+and constructed workflows.</li>
+<li>WS-Messenger - a publish-subscribe based message broker implemented on top of Apache Axis2 web 
+services stack. It implements the WS-Eventing and WS-Notifications specifications and incorporates 
+a message box component that facilities communications with clients behind firewalls and overcomes 
+network glitches. As an example, the workflow execution engine sends out events in various stages,
+including start, end, failure, successful invocation, of its workflow execution.</li>
+<li>Registry-API: A thick client registry API for Airavata to put and get documents. Current JCR implementation is supported by Jack-Rabbit.</li>
+</ul>
+  </div>
+
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/airavata/trunk/content/airavata/architecture/registry.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/registry.html (added)
+++ websites/staging/airavata/trunk/content/airavata/architecture/registry.html Tue Oct  4 17:48:43 2011
@@ -0,0 +1,123 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <link href="/airavata/css/airavata.css" rel="stylesheet" type="text/css">
+  <title>Information and Data Registry</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="banner">
+    <img id="logo" alt="Apache airavata (Incubating)" src="/airavata/images/airavata-logo.png"/>
+    <div id="bannertext">
+      <img id="logo-text"  alt="Apache airavata (Incubating)" src="/airavata/images/airavata-text.png" />
+      </div><br />
+  </div>
+  
+  <div id="navigation">
+  <h1 id="about_airavata">About Airavata</h1>
+<ul>
+<li><a href="/airavata/index.html">Home</a></li>
+<li><a href="http://incubator.apache.org/projects/airavata.html">Incubator Page</a></li>
+<li><a href="/airavata/about/license.html">License</a></li>
+<li><a href="/airavata/about/history.html">History</a></li>
+</ul>
+<h1 id="architecture">Architecture</h1>
+<ul>
+<li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/airavata/community/get-involved.html">Get Involved</a></li>
+<li><a href="/airavata/community/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/airavata/community/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/airavata/development/source.html">Source Code</a></li>
+<li><a href="/airavata/development/build.html">Build Instructions</a></li>
+<li><a href="https://issues.apache.org/jira/browse/airavata">Issue Tracker</a></li>
+<li><a href="/airavata/development/roadmap.html">Road Map</a></li>
+<li><a href="/airavata/tools/devtools.html">Dev Tools</a></li>
+<li><a href="/airavata/development/edit-cms-website.html">Editing Website</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/airavata/documentation/system/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/documentation/messenger/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/documentation/workflow/xbaya.html">XBaya</a></li>
+<li><a href="/airavata/documentation/gfac/gfac.html">GFac</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+    <a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/airavata/images/apache-incubator-logo.png" width="150"/>
+    </a>
+  </div>
+
+  <div id="content">
+    <h1 class="title">Information and Data Registry</h1>
+    <p>Airavata provides capabilities for an integrated workflow and data management system. The information and data has to be persisted into a registry 
+service. To adhere to the philosophies of Airavata for layering over existing stable third party components, Airavata usage is consolidated into a 
+thick-client API. This API allows the pluggability of the infrastructure and avoids locks in into any specific registry architectures. 
+This follwing figure summerizes the use of the registry.</p>
+<p><img alt="Airavata Registry Usage" src="/airavata/architecture/airavata-registry.png" title="Airavata Registry Usage" /></p>
+<h2 id="jcr_specification">JCR Specification:</h2>
+<p>The Content Repository for Java Technology specification, developed under the Java Community Process JSR-170, 
+aims to standardize Java API to repositiries. The specification provides a unified API under the javax.jcr namespace that allows you to
+access any specification-compliant repository implementation in a vendor-neutral manner. A major advantage of JSR-170 is that it is not 
+tied to any particular underlying architecture. The back-end data storage for a JSR-170 implementation, for instance, may be a filesystem, 
+a WebDAV repository, an XML-backed system, or even an SQL database. Furthermore, the export and import facilities of JSR-170 allow an integrator
+to switch seamlessly between content back ends and JCR implementations. Finally, the JCR provides a straightforward interface that can be layered 
+on top of a wide variety of existing content repositories, while simultaneously standardizing complex functionality such as versioning, 
+access control, and searching. There are open source implementations of JSR-170 such as Apache Jackrabbit, Alfresco and WSO2 Registry.</p>
+<h2 id="airavata_registry_api">Airavata Registry API</h2>
+<p>When implementing registry functionality to store data and retrieve data we did not want to have locking for any custom API's to content 
+repository implementations. Airavata tried to integrate with existing repositories without having to re-invent the wheel. 
+JCR-2.0 specification and the JSR-170 implementation is plugged in to Apache Airavata system. The Airavata specific API layers over 
+the generic JCR API and is integrated with Apache Jackrabbit implementation. The API is modularized as a common component reused by XBaya and 
+GFac components to store and retrieve data. In addition to the service information, the registry is used to catalog workflow consumed inputs
+and generated output data. The registry is also used to advertise and retrieve persistent service information. The use of the registry for 
+GFac service registration allows for late service binding and supporting large number of applications provided by the inherent load balance 
+capabilities. </p>
+  </div>
+
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/airavata/trunk/content/airavata/architecture/workflow-suite.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/airavata/trunk/content/airavata/architecture/workflow-suite.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: websites/staging/airavata/trunk/content/airavata/architecture/workflow.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/workflow.html (added)
+++ websites/staging/airavata/trunk/content/airavata/architecture/workflow.html Tue Oct  4 17:48:43 2011
@@ -0,0 +1,151 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <link href="/airavata/css/airavata.css" rel="stylesheet" type="text/css">
+  <title>Airavata Workflow Suite</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="banner">
+    <img id="logo" alt="Apache airavata (Incubating)" src="/airavata/images/airavata-logo.png"/>
+    <div id="bannertext">
+      <img id="logo-text"  alt="Apache airavata (Incubating)" src="/airavata/images/airavata-text.png" />
+      </div><br />
+  </div>
+  
+  <div id="navigation">
+  <h1 id="about_airavata">About Airavata</h1>
+<ul>
+<li><a href="/airavata/index.html">Home</a></li>
+<li><a href="http://incubator.apache.org/projects/airavata.html">Incubator Page</a></li>
+<li><a href="/airavata/about/license.html">License</a></li>
+<li><a href="/airavata/about/history.html">History</a></li>
+</ul>
+<h1 id="architecture">Architecture</h1>
+<ul>
+<li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/airavata/community/get-involved.html">Get Involved</a></li>
+<li><a href="/airavata/community/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/airavata/community/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/airavata/development/source.html">Source Code</a></li>
+<li><a href="/airavata/development/build.html">Build Instructions</a></li>
+<li><a href="https://issues.apache.org/jira/browse/airavata">Issue Tracker</a></li>
+<li><a href="/airavata/development/roadmap.html">Road Map</a></li>
+<li><a href="/airavata/tools/devtools.html">Dev Tools</a></li>
+<li><a href="/airavata/development/edit-cms-website.html">Editing Website</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/airavata/documentation/system/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/documentation/messenger/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/documentation/workflow/xbaya.html">XBaya</a></li>
+<li><a href="/airavata/documentation/gfac/gfac.html">GFac</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+    <a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/airavata/images/apache-incubator-logo.png" width="150"/>
+    </a>
+  </div>
+
+  <div id="content">
+    <h1 class="title">Airavata Workflow Suite</h1>
+    <p>Airavata XBaya workflow system provides a programming model that allows the scientist to program experiments using 
+service-oriented architecture that would abstract the complexities of the underlying middleware. 
+Airavata XBaya provides interfaces for composition, execution and monitoring of the workflows as illustrated in the following Figure. 
+Airavata XBaya consist of convenient GUI interface for workflow composition, workflow enactment 
+engine/interface for workflow enactment and workflow monitoring module. </p>
+<p><img alt="Airavata Workflow Suite" src="/airavata/architecture/workflow-suite.png" title="Airavata Workflow Suite" /></p>
+<h2 id="workflow_composition">Workflow Composition</h2>
+<p>Airavata XBaya by design decouples composition and monitoring from the orchestration of the workflow although it does provide an embedded workflow 
+enactment engine integrated with the workbench. As a scientific workflow suite XBaya is often expected to run long running computations thus it 
+often delegates the workflow execution to a persistent orchestration engine and XBaya workbench can monitor the progress of the workflow asynchronously. The workbench provides a convenient drag and drop GUI for SOA based service composition along with other functionalities like service discovery, registry lookup and workflow experiment management.</p>
+<h2 id="workflow_orchestration">Workflow orchestration</h2>
+<p>XBaya provides a unique pluggable architecture for selecting the orchestration engine. When a user composes a workflow using XBaya workbench 
+it builds an abstract Directed Acyclic Graph (DAG) which is independent of any workflow runtime. There are pluggable compiler modules that are 
+capable of producing workflow execution scripts for target runtimes. The above Figure illustrated how the DAG can compiled into different runtimes. 
+Currently XBaya supports BPEL 2.0 and Apache ODE; SCUFL and Taverna; DAGMAN and Pegasus; Jython scripts and XBaya Interpreter Service.</p>
+<p>Each of these workflow runtimes have their own strengths, for example, Apache ODE is a robust SOA based workflow orchestration engine well suited 
+for long running applications. Pegasus workflow system is well suited for parametric sweeps whereas XBaya Interpreter engine is strong in dynamic 
+and user interactive workflow execution. It is also capable of generating a Jython script that can be executed in any Jython runtime independent 
+of any of the workflow infrastructure.</p>
+<h2 id="workflow_interpreter">Workflow interpreter</h2>
+<p>XBaya provides a inbuilt workflow enactment engine that provides extremely dynamic and interactive workflow execution. 
+As the name suggests the workflow interpreter provides an interpreted workflow execution framework rather than the compiled workflow execution 
+environments. In this context the interpreted workflow means at that execution framework executed tasks in the XBaya DAG as and when the tasks 
+become runnable. Once the user composes the workflow and launches the workflow the workflow interpreter will start executing the workflow DAG. 
+Topological sort of the DAG provides execution ordering of the tasks which allow the identification of the initial ready task set and incrementally 
+adding new tasks to the ready list as previous tasks finish execution. What is unique about this type of execution model is it allows the user 
+to pause the execution of the workflow as necessary and update the DAG’s execution states or even the DAG itself and resume execution and the 
+changes are immediately picked up by the workflow interpreter.</p>
+<p>Workflow interpreter can be used as an embedded workflow enactment engine within XBaya GUI or as an interpreter service that may run as a persistent 
+service. The functionality provided by the workflow interpreter allows fine gain control over the workflow execution which translates into following 
+functionalities.
+<em> Static workflow interactions
+</em> Dynamic change workflow inputs, workflow rerun.
+<em> Stop, pause, resume execution of the workflow. Pause workflow at a particular (debug) point
+</em> Dynamic change in point of execution, workflow smart rerun.
+<em> Fault handling and exception models  <br />
+</em> Dynamic workflow interactions
+<em> Reconfiguration of workflow activity
+</em> Dynamic addition of activities to the DAG.
+* Dynamic remove or replace of activity to the DAG.</p>
+<h2 id="workflow_monitoring">Workflow monitoring:</h2>
+<p>XBaya workbench allows the user to monitor the progress of the workflow in real-time. Monitoring includes the services which are currently executing, 
+those that are done. It also provides state of the job submissions to the batch job queues and status of the data transfer. Workflow monitoring in 
+XBaya workbench work in two modes; synchronous mode and asynchronous mode. The synchronous mode only applies when XBaya interpreter runs embedded in 
+the workbench. This allows the execution engine to be aware of which task are ready, running, finished and waiting and thus accordingly update the 
+DAG execution state. But when the workflow execution is delegated to a persistant service like Apache ODE serve or XBaya interpreter service, 
+it is necessary to have asynchronous monitoring. This is achieved using the WS-Eventing based notification messages published by different components 
+of the workflow  system. If a user launches a workflow instance a unique topic will be associated with that instance and all the workflow components
+like workflow engine, Factory service will publish status notification about the workflow to the event bus using the topic assigned to the workflow 
+instance. This asynchronous monitoring is truly asynchronous where the user can launch the workflow, start monitoring, loose internet connectivity and
+once reconnected the XBaya workbench will bring back the monitoring to the current execution state of the workflow.</p>
+  </div>
+
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Added: websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html (added)
+++ websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html Tue Oct  4 17:48:43 2011
@@ -0,0 +1,155 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<!--
+
+    Licensed to the Apache Software Foundation (ASF) under one or more
+    contributor license agreements.  See the NOTICE file distributed with
+    this work for additional information regarding copyright ownership.
+    The ASF licenses this file to You under the Apache License, Version 2.0
+    (the "License"); you may not use this file except in compliance with
+    the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE- 2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+-->
+  <link href="/airavata/css/airavata.css" rel="stylesheet" type="text/css">
+  <title>WS-Messenger System</title>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+</head>
+
+<body>
+  <div id="banner">
+    <img id="logo" alt="Apache airavata (Incubating)" src="/airavata/images/airavata-logo.png"/>
+    <div id="bannertext">
+      <img id="logo-text"  alt="Apache airavata (Incubating)" src="/airavata/images/airavata-text.png" />
+      </div><br />
+  </div>
+  
+  <div id="navigation">
+  <h1 id="about_airavata">About Airavata</h1>
+<ul>
+<li><a href="/airavata/index.html">Home</a></li>
+<li><a href="http://incubator.apache.org/projects/airavata.html">Incubator Page</a></li>
+<li><a href="/airavata/about/license.html">License</a></li>
+<li><a href="/airavata/about/history.html">History</a></li>
+</ul>
+<h1 id="architecture">Architecture</h1>
+<ul>
+<li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
+</ul>
+<h1 id="community">Community</h1>
+<ul>
+<li><a href="/airavata/community/get-involved.html">Get Involved</a></li>
+<li><a href="/airavata/community/mailing-lists.html">Mailing Lists</a></li>
+<li><a href="/airavata/community/people.html">People</a></li>
+</ul>
+<h1 id="development">Development</h1>
+<ul>
+<li><a href="/airavata/development/source.html">Source Code</a></li>
+<li><a href="/airavata/development/build.html">Build Instructions</a></li>
+<li><a href="https://issues.apache.org/jira/browse/airavata">Issue Tracker</a></li>
+<li><a href="/airavata/development/roadmap.html">Road Map</a></li>
+<li><a href="/airavata/tools/devtools.html">Dev Tools</a></li>
+<li><a href="/airavata/development/edit-cms-website.html">Editing Website</a></li>
+</ul>
+<h1 id="documentation">Documentation</h1>
+<ul>
+<li><a href="/airavata/documentation/system/overview.html">Airavata Overview</a></li>
+<li><a href="/airavata/documentation/messenger/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/documentation/workflow/xbaya.html">XBaya</a></li>
+<li><a href="/airavata/documentation/gfac/gfac.html">GFac</a></li>
+</ul>
+<h1 id="asf">ASF</h1>
+<ul>
+<li><a href="http://www.apache.org">Apache Software Foundation</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">Thanks</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">Become a Sponsor</a></li>
+<li><a href="http://www.apache.org/security/">Security</a></li>
+</ul>
+    <a alt="Apache Incubator" href="http://incubator.apache.org">
+      <img id="asf-logo" alt="Apache Incubator" src="/airavata/images/apache-incubator-logo.png" width="150"/>
+    </a>
+  </div>
+
+  <div id="content">
+    <h1 class="title">WS-Messenger System</h1>
+    <p>Airavata WS-Messenger is a Web Services-based Messaging System for Service-Oriented Computing and is
+an implementation of <a href="http://www.oasis-open.org/committees/wsn/">WS-Notification</a> and <a href="http://www.w3.org/Submission/WS-Eventing/">WS-Eventing</a> specifications. The message format 
+can be automatically converted between the two specifications. The subscription request type
+(Ws-Notification or WS-Eventing) for a listener determines the message format that the notification 
+consumer will receive. If WS-Notification subscription request is received by the broker, it will 
+send WS-Notification messages to the listener. Similarly, if WS-Eventing subscription is received 
+by the broker, the broker will produce WS-Eventing messages for that listener. The publisher can 
+publish messages in either format. The consumers will recieve messages in the format they subscribed 
+irrespective of the format the message is published.</p>
+<p>The WS-Messenger guarantees scalable, reliable and efficient message delivery. WS-Messenger contains 
+sub-components of Message broker, Message box and WS-Messenger client libraries. 
+WS-Messenger acts like the nervous system within Airavata infrastructure but can very well be integrated 
+into any WS-Eventing/WS-Notification standard compliant infrastructures. The Messenger is deployed as a 
+Axis2 service providing inherent support for different transports including HTTP 1.0, HTTP 1.1 and JMS. 
+Custom transport protocols can be plugged in using the Axis2 framework's transport plug-ins. 
+WS-Messenger is integrated with Mysql and Apache Derby database implementations. 
+The embedded Derby database is deployed within the same Java process. The system also supports persistent 
+subscriptions and notifications which will tolerate failures and restarts of the application server. </p>
+<p>The following figure illustrates the high level overview of the WS-Messenger 
+<img alt="WS Messenger Overview" src="/airavata/architecture/messenger-overview.png" title="WS Messenger Overview" /></p>
+<h2 id="ws-messenger_modules">WS-Messenger Modules</h2>
+<ol>
+<li>Message Broker: The broker handles filtering/delivering messages to even sinks and subscription management. 
+WS-Messenger support filtering messages based on XPath expression and topic expression. Message broker is implemented on 
+Web services specifications and provide the mediation between WS-Eventing Specification and WS-Notification Specifications. 
+WS-Eventing and WS-Notification specifications are two competing specifications defining the interfaces for Web services-based 
+publish/subscribe systems.  The Web Services interfaces and the notification message formats defined in these two 
+specifications are fundamentally different. WS-Messenger provides a mediation approach facilitating interoperability with supported services. 
+WS-Messenger can automatically convert the notification message formats to makes sure that the message “on the wire” can be understood by the 
+event consumers. For example, a WS-Notification  consumer can receive notification messages published by a WS-Eventing publisher and vice versa. 
+The event consumer type is determined by the subscription request message type. Here we assume that the subscribers and the event 
+consumers use the same specification. This is a valid assumption for most cases since the subscribers needs to know the location of the event consumers.
+The message delivering schema is implemented by consumer blacklisting to minimize the overhead of message delivering failures. 
+Message delivering performance has been implemented with a parallel message delivering sub system. The blocking I/O overhead is reduced 
+configuring the NIO transport. WS-Messenger uses the NIO transport provided by Apache Synapse project to enable non-blocking I/O in Axis2. </li>
+<li>Message Box: WS-Messenger decouples the consumer tolerating network failures and firewalls. 
+The Message box acts like an intermediate notification storage between broker and the event sink. Users can simply create a message box and 
+provide the message box URL as the event sink URL during the subscription. When messages are publishing to message broker notifications will 
+send to the message box and it stores the incoming messages in to database or keep them in memory based on the WS-Messenger configuration. 
+Message box Service has operations  to pull the messages from the message box so whenever actual event sink is ready to pull the messages out 
+from message box they simply have to invoke the message Pulling API and take the notifications. When the message box is no longer needed, 
+the subscriber can send another web service request to destroy the message box.This is a useful feature in a scenario where event source cannot 
+send notifications directly to even sink running behind the firewall. This deployment is a very common firewall configuration between DMZ and green zone 
+in an enterprise deployment.provide a web service interface for subscribers behind the firewalls.</li>
+</ol>
+<h2 id="airavata_usage_of_the_ws-messenger">Airavata Usage of the WS-Messenger</h2>
+<p>Within Airavata, the WS-Messenger is used for user and system communications between GFac, XBaya and Workflow Intepreter. 
+XBaya in monitoring mode subscribes to a pre-specified topic to which Workflow Engine and GFac are publishing status notifications. 
+XBaya is instrumented to react to the messages to illustrate workflow progress by means of color coding of tasks being executed.</p>
+<p>The following steps illustrates the usage in detail:
+<em> XBaya creates a message Box, subscribes to it and then invokes a workflow, with the created message box EPR passed in context.<br />
+</em> Then XBaya sends a subscription request to WS-Messenger with a particular topic and message box URL received as the event sink. 
+<em> Then workflow notifiers in XBaya send the notifications using the same topic to the message broker.
+</em> Individual application services created by GFac are instrumented to publish detailed status and send progress to the EPR received in workflow execution context.
+* XBaya translates the messages into graphical colors and input and output extractions.</p>
+  </div>
+
+  <div id="footer">
+    <div class="copyright">
+      <p>
+        Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+        the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+        <br />
+        Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+      </p>
+    </div>
+  </div>
+
+</body>
+</html>

Modified: websites/staging/airavata/trunk/content/airavata/community/get-involved.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/get-involved.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/get-involved.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/community/governance/consensusBuilding.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/governance/consensusBuilding.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/governance/consensusBuilding.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/community/governance/lazyConsensus.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/governance/lazyConsensus.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/governance/lazyConsensus.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/community/governance/voting.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/governance/voting.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/governance/voting.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/community/mailing-lists.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/mailing-lists.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/mailing-lists.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/community/people.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/community/people.html (original)
+++ websites/staging/airavata/trunk/content/airavata/community/people.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/development/build.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/development/build.html (original)
+++ websites/staging/airavata/trunk/content/airavata/development/build.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html (original)
+++ websites/staging/airavata/trunk/content/airavata/development/edit-cms-website.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/development/source.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/development/source.html (original)
+++ websites/staging/airavata/trunk/content/airavata/development/source.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/gfac/gfac.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/gfac/gfac.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/gfac/gfac.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/messenger/ws-messenger.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/messenger/ws-messenger.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/messenger/ws-messenger.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/registry/xregistry.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/registry/xregistry.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/registry/xregistry.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/system/overview.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/system/overview.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/system/overview.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/workflow/xbaya.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/workflow/xbaya.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/workflow/xbaya.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/index.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/index.html (original)
+++ websites/staging/airavata/trunk/content/airavata/index.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>

Modified: websites/staging/airavata/trunk/content/airavata/tools/devtools.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/tools/devtools.html (original)
+++ websites/staging/airavata/trunk/content/airavata/tools/devtools.html Tue Oct  4 17:48:43 2011
@@ -42,9 +42,10 @@
 <h1 id="architecture">Architecture</h1>
 <ul>
 <li><a href="/airavata/architecture/overview.html">Airavata Overview</a></li>
-<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
-<li><a href="/airavata/architecture/workflow/xbaya.html">XBaya</a></li>
 <li><a href="/airavata/architecture/gfac/gfac.html">GFac</a></li>
+<li><a href="/airavata/architecture/workflow.html">Workflow Suite</a></li>
+<li><a href="/airavata/architecture/ws-messenger.html">WS Messenger</a></li>
+<li><a href="/airavata/architecture/registry.html">Registry API</a></li>
 </ul>
 <h1 id="community">Community</h1>
 <ul>



Mime
View raw message