airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835834 - in /websites/staging/airavata/trunk/content: ./ about/ architecture/ development/ documentation/ documentation/system/
Date Tue, 23 Oct 2012 02:54:44 GMT
Author: buildbot
Date: Tue Oct 23 02:54:43 2012
New Revision: 835834

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/about/downloads.html
    websites/staging/airavata/trunk/content/architecture/overview.html
    websites/staging/airavata/trunk/content/development/release-management.html
    websites/staging/airavata/trunk/content/documentation/deployment.html
    websites/staging/airavata/trunk/content/documentation/system/airavata-in-10-minutes.html
    websites/staging/airavata/trunk/content/documentation/system/airavata-in-5-minutes.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Oct 23 02:54:43 2012
@@ -1 +1 @@
-1393198
+1401146

Modified: websites/staging/airavata/trunk/content/about/downloads.html
==============================================================================
--- websites/staging/airavata/trunk/content/about/downloads.html (original)
+++ websites/staging/airavata/trunk/content/about/downloads.html Tue Oct 23 02:54:43 2012
@@ -112,14 +112,14 @@
 <li>
 <p>Source: </p>
 <ul>
-<li><a href="http://archive.apache.org/dist/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip">airavata-0.3-incubating-source-release.zip</a>
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip">airavata-0.3-incubating-source-release.zip</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/airavata-0.3-incubating-source-release.zip.md5">md5</a>]</li>
 </ul>
 </li>
 <li>
 <p>Binaries:</p>
 <ul>
-<li><a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz">apache-airavata-0.3-incubating-bin.tar.gz</a>
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz.md5">md5</a>]</li>
-<li><a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip">apache-airavata-0.3-incubating-bin.zip</a>
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz">apache-airavata-0.3-incubating-bin.tar.gz</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.tar.gz.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip">apache-airavata-0.3-incubating-bin.zip</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.3-incubating/apache-airavata-0.3-incubating-bin.zip.md5">md5</a>]</li>
 </ul>
 </li>
 </ul>
@@ -128,14 +128,14 @@
 <li>
 <p>Source: </p>
 <ul>
-<li><a href="http://archive.apache.org/dist/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip">airavata-0.2-incubating-source-release.zip</a>
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip">airavata-0.2-incubating-source-release.zip</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/airavata-0.2-incubating-source-release.zip.md5">md5</a>]</li>
 </ul>
 </li>
 <li>
 <p>Binaries:</p>
 <ul>
-<li><a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz">apache-airavata-0.2-incubating-bin.tar.gz</a>
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz.md5">md5</a>]</li>
-<li><a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip">apache-airavata-0.2-incubating-bin.zip</a>
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz">apache-airavata-0.2-incubating-bin.tar.gz</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.tar.gz.md5">md5</a>]</li>
+<li><a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip">apache-airavata-0.2-incubating-bin.zip</a>
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip.asc">asc</a>]
[<a href="http://archive.apache.org/dist/incubator/airavata/0.2-incubating/apache-airavata-0.2-incubating-bin.zip.md5">md5</a>]</li>
 </ul>
 </li>
 </ul>

Modified: websites/staging/airavata/trunk/content/architecture/overview.html
==============================================================================
--- websites/staging/airavata/trunk/content/architecture/overview.html (original)
+++ websites/staging/airavata/trunk/content/architecture/overview.html Tue Oct 23 02:54:43
2012
@@ -90,23 +90,12 @@
 
   <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 primarily 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>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 primarily 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 Web service instance created by the Generic Facory
Service. </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>
+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="/architecture/airavata.png" title="Airavata
Overview" /></p>
 <h2 id="airavata-features">Airavata Features</h2>
 <ul>
@@ -129,8 +118,7 @@ implements the WS-Eventing and WS-Notifi
 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>
+<li>Registry-API: A thick client registry API for Airavata to put and get documents.
Current registry implementation is on top of derby or MySQL.</li>
 </ul>
   </div>
 

Modified: websites/staging/airavata/trunk/content/development/release-management.html
==============================================================================
--- websites/staging/airavata/trunk/content/development/release-management.html (original)
+++ websites/staging/airavata/trunk/content/development/release-management.html Tue Oct 23
02:54:43 2012
@@ -90,22 +90,15 @@
 
   <div id="content">
     <h1 class="title">Release Process</h1>
-    <p>Releases are crucial aspects for an apache project and following the guidelines
is very important.
-The <a href="http://www.apache.org/dev/release.html">Release FAQ</a> describes
the foundation wide policies. The <a href="http://incubator.apache.org/guides/releasemanagement.html">Incubator
Release Management</a>
-describes incubator project specific release process. The following instructions walkthrough
Airavata specific release steps. </p>
+    <p>Releases are crucial aspects for an apache project and following the guidelines
is very important. The <a href="http://www.apache.org/dev/release.html">Release FAQ</a>
describes the foundation wide policies. The following instructions walkthrough Airavata specific
release steps. </p>
 <p><a name="release-setup"></a></p>
 <h3 id="one-time-release-management-setup">One time release management setup</h3>
-<p>This section describes release management configuration steps, if you have previously
configured these steps, 
-jump directly to <a href="#release-process">Release Process</a>.</p>
+<p>This section describes release management configuration steps, if you have previously
configured these steps, jump directly to <a href="#release-process">Release Process</a>.</p>
 <p>Performing a release will require:</p>
 <ul>
-<li>Access to people.apache.org to stage builds, verify access by following these <a
href="#access-people">instructions</a>.</li>
 <li>Generate, sign and upload gpg key, you can follow these <a href="#gpg-key">gpg
instructions</a>.</li>
 <li>Configure Maven and get access to Nexus Repo, more <a href="#maven-nexus-setup">maven
&amp; nexus instructions</a>.</li>
 </ul>
-<p><a name="access-people"></a></p>
-<h4 id="access-to-peopleapacheorg">Access to people.apache.org</h4>
-<p>Ensure you can access the apache gateway server by <code>ssh &lt;asfid&gt;@people.apache.org</code>.
If you have any trouble with your ASF LDAP, you can change or reset your password at <a
href="https://id.apache.org/">Apache Account Utility Page</a>.</p>
 <p><a name="gpg-key"></a></p>
 <h4 id="generate-gpg-key">Generate GPG key</h4>
 <p>The releases have to be signed by public key cryptography signatures. Detailed instructions
on why releases have to be signed are provided on <a href="http://www.apache.org/dev/release-signing.html">Release
Signing</a> page.
@@ -116,7 +109,7 @@ The popular software used Open Pretty Go
 <li>Export the public key: <code>gpg --list-sigs &lt;Real Name&gt; &amp;&amp;
gpg --armor -- export &lt;Real Name&gt;</code></li>
 <li>Upload the public key to <a href="http://pgp.surfnet.nl:11371/">SURFNET PGP</a>
or <a href="http://pgp.mit.edu/">MIT PGP</a> servers.</li>
 <li>Have your key signed by atleast three apache commiters, <a href="http://www.apache.org/dev/release-signing.html#key-signing-party">key
signing</a> and <a href="http://people.apache.org/~henkp/trust/">Henk Penning</a>
websites provide instructions.</li>
-<li>Add the signed public key to the KEYS file on <a href="https://dist.apache.org/repos/dist/release/incubator/airavata/">Airavata
Dist SVN</a>.</li>
+<li>Add the signed public key to the KEYS file on <a href="https://dist.apache.org/repos/dist/release/airavata/">Airavata
Dist SVN</a>.</li>
 </ul>
 <p><a name="maven-nexus-setup"></a></p>
 <h4 id="maven-configuration-nexus-setup">Maven Configuration &amp; Nexus Setup</h4>
@@ -256,7 +249,7 @@ For c shell: <code>setenv MAVEN_OPTS "-X
 <li>Create a VOTE email thread on dev@ to record votes as replies, like <a href="release-vote.txt">this</a></li>
 <li>Create a DISCUSS email thread on dev@ for any vote questions, <a href="release-discuss.txt">this</a></li>
 <li>
-<p>Perform a review of the release and cast your vote. For elaborate instructions,
please consult <a href="http://www.apache.org/dev/release.html">Apache Release FAQ</a>
and <a href="http://incubator.apache.org/guides/releasemanagement.html">Incubator Release
Management</a> Guides.</p>
+<p>Perform a review of the release and cast your vote. For elaborate instructions,
please consult <a href="http://www.apache.org/dev/release.html">Apache Release FAQ</a>
and [Incubator Release Management][inc-release-mgmt] Guides.</p>
 </li>
 <li>
 <p>A -1 vote does not necessarily mean that the vote must be redone, however it is
usually a good idea to rollback the release if a -1 vote is received. See - Recovering from
a vetoed release</p>

Modified: websites/staging/airavata/trunk/content/documentation/deployment.html
==============================================================================
--- websites/staging/airavata/trunk/content/documentation/deployment.html (original)
+++ websites/staging/airavata/trunk/content/documentation/deployment.html Tue Oct 23 02:54:43
2012
@@ -91,25 +91,41 @@
   <div id="content">
     <h1 class="title"></h1>
     <h3 id="how-to-start-airavata-system-and-what-is-the-order-to-start-each-component">How
to start Airavata System and what is the order to start each component.</h3>
-<p>To start Airavata system users have to use the scripts provided in AIRAVATA_HOME/bin/
and if you are running all the components 
-with default setup you have to start the components in the following order.</p>
+<p>To start Airavata system users have to use the scripts provided in <AIRAVATA_HOME>/bin/.
Here we define <AIRAVATA_HOME> as the location where
+you extract apache airavata binary. If you are running all the components with default setup,
you have to start the components in the following order:</p>
 <ol>
 <li>
-<p>jackrabbit-server.sh - This is the Jackrabbit server startup script, before starting
any other component, you have to start the
-                          registry instance first because all the components are communicating
with Registry.</p>
-</li>
-<li>
-<p>airavata-server.sh   - This starts the WS-Messenger components and GFac service
in Apache Axis2 Container. This is pointing to the
-                          Registry started in previous step and use the Registry URL is localhost:8081,
if you are starting in a
-                          different URL, you have to change AIRAVATA_HOME/standalone-server/conf/repository.properties
file.</p>
+<p>airavata-server.sh -   This starts the WS-Messenger component and the GFac service
in the Apache Axis2 Container and points to the default
+                          derby database server, which runs on port "1527". If you are starting
with a different registry URL, you have to make
+                          the corresponding change in the <AIRAVATA_HOME>/standalone-server/conf/airavata-server.properties
file.</p>
 </li>
 <li>
 <p>xbaya-gui.sh         - Now you have available GFac Service running with a Registry,
so its time for you to start XBaya and run
-                          your Applications. But if you want XBaya to run with normal Web
services, not with GFac Service you do not
-                          have to start Airvata Service, you can simply use Xbaya alone,
if you require provenance, you have to start
-                          Registry.</p>
+                          your Applications. For that copy "<AIRAVATA_HOME>/standalone-server/conf/airavata-server.properties"
+                          file into "<AIRAVATA_HOME>/bin" folder. But if you want XBaya
to run with normal Web services, not with GFac
+                          Service you do not have to start Airvata Service, you can simply
use Xbaya alone, if you require provenance,
+                          you have to start Registry.</p>
 </li>
 </ol>
+<h3 id="how-to-start-the-airavata-system-components-with-mysql">How to start the Airavata
System Components with MySQL</h3>
+<p>By default, Airavata is running using Apache Derby as the backend database. You
can use MySQL database instead of default derby database if
+you wish. Here we define <AIRAVATA_HOME> as the location where you extract Apache Airavata
binary.</p>
+<ol>
+<li>Create a new user called airavata with password airavata in running MySQL instance</li>
+<li>Create a mysql database in your server with required name for user airavata (Assume
name is:persistent_data)</li>
+<li>Copy mysql driver jar (mysql-connector-java-5.1.6.jar) to <AIRAVATA_HOME>/standalone-server/lib</li>
+<li>Edit jdbc connection URLs at airavata-server.properties file that resides in <AIRAVATA_HOME>/standalone-server/conf.
+You can achieve this by just un-commenting out parameters under "configuration for mysql"
section and commented-out the default
+derby configurations.
+         registry.jdbc.url=jdbc:mysql://localhost:3306/persistent_data
+         registry.jdbc.driver=com.mysql.jdbc.Driver</li>
+<li>Go to <AIRAVATA_HOME>/bin and start the script airavata-server.sh. Now Airavata
server will start with MySQL database
+(in this case persistent_data database).
+When starting XBaya, it should also point to the same database that we specified when starting
Airavata server. In order to do that,
+copy the same airavata-server.properties file that you have edited in the 2nd step, to <AIRAVATA_HOME>/bin
folder. Now you are ready
+to start XBaya. To start XBaya, go to <AIRAVATA_HOME>/bin folder and run the script
xbaya-gui.sh. Now XBaya will start with the
+same database that used to start Airavata server.</li>
+</ol>
 <h3 id="how-to-deploy-airavata-on-tomcat">How to Deploy Airavata on Tomcat</h3>
 <p>Airavata services depends on Apache Axis2 as a Web Service engine. Each service
component in Airavata can be packed as Axis2 Archive (.aar).
 In order to deploy Airavata system on Tomcat, you need to install Apache Axis2 on Tomcat
first. This will be handled by the setup script.
@@ -161,37 +177,26 @@ database and AIRAVATA_HOME/standalone-se
 <p>First create a mysql database in your server with required name (Assume name is:wsmg
and username/password is : airavata/airavata).</p>
 </li>
 <li>
-<p>Create a tables in the above database using the following scripts.</p>
-<ul>
-<li>AIRAVATA_HOME/standalone-server/bin/database_scripts/mgsBox-mysql.sql</li>
-<li>AIRAVATA_HOME/standalone-server/bin/database_scripts/msgBroker-mysql.sql</li>
-</ul>
+<p>Create a tables in the above database using the following scripts.
+      AIRAVATA_HOME/standalone-server/bin/database_scripts/mgsBox-mysql.sql
+      AIRAVATA_HOME/standalone-server/bin/database_scripts/msgBroker-mysql.sql</p>
 </li>
 <li>
-<p>Change msgBox.properties and msgBroker.properties files located at AIRAVATA_HOME/standalone-server/conf
with database driver name and database urls as below.</p>
-<ul>
-<li>msgBox.jdbc.driver=com.mysql.jdbc.Driver</li>
-<li>msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</li>
-<li>broker.jdbc.driver=com.mysql.jdbc.Driver</li>
-<li>broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</li>
-<li>For mysql datbase add following entries.<ul>
-<li>msgBox.jdbc.driver=com.mysql.jdbc.Driver</li>
-<li>msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</li>
-</ul>
-</li>
-<li>For default derby database add following entries.<ul>
-<li>msgBox.jdbc.driver=org.apache.derby.jdbc.EmbeddedDriver</li>
-<li>msgBox.jdbc.url=jdbc:derby:wsmg;create=true;user=airavata;password=airavata</li>
-</ul>
-</li>
-</ul>
+<p>Change msgBox.properties and msgBroker.properties files located at AIRAVATA_HOME/standalone-server/conf
with database driver name and
+database urls as below.
+      msgBox.jdbc.driver=com.mysql.jdbc.Driver
+      msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata
+      broker.jdbc.driver=com.mysql.jdbc.Driver
+      broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
 </li>
 </ol>
 <p>Once you update the parameters, make sure that you have commented-out default derby
values and uncommented-out mysql values.
 Now your msgBox.properties file would look like above.</p>
 <p>In the similar manner update the msgBroker.properties file as well.</p>
 <ol>
-<li>Change the driver class name based on your driver and copy your driver(in this
case, it is mysql-connector-java-5.1.13-bin.jar) to AIRAVATA_HOME/standalon-server/lib directory
and start the server. To start the server, go to AIRAVATA_HOME/bin folder and run the script
airavata-server.sh/airavata-server.bat. Now you are ready to go with Mysql database.</li>
+<li>Change the driver class name based on your driver and copy your driver(in this
case, it is mysql-connector-java-5.1.13-bin.jar) to
+AIRAVATA_HOME/standalon-server/lib directory and start the server. To start the server, go
to AIRAVATA_HOME/bin folder and run the script
+airavata-server.sh/airavata-server.bat. Now you are ready to go with Mysql database.</li>
 </ol>
 <h3 id="how-can-i-run-ws-messenger-without-using-any-database">How can I run WS-Messenger
without using any database.</h3>
 <p>Yes, WS-Messenger supports in-memory messaging. If you want to change message broker
or message box to be in memory you simply have to change the appropriate property in

Modified: websites/staging/airavata/trunk/content/documentation/system/airavata-in-10-minutes.html
==============================================================================
--- websites/staging/airavata/trunk/content/documentation/system/airavata-in-10-minutes.html
(original)
+++ websites/staging/airavata/trunk/content/documentation/system/airavata-in-10-minutes.html
Tue Oct 23 02:54:43 2012
@@ -123,8 +123,6 @@ Note: Currently Airavata will work with 
 <li>Extract the distribution archive (the rest of this document assumes the path to
extracted directory is AIRAVATA_HOME)</li>
 <li>Now Run the following scripts in the given order below to start the components
of Airavata.
 <br></br>
-AIRAVATA_HOME/bin/jackrabbit-server.sh - This will start Jackrabbit repository on port 8081.
-<br></br>
 AIRAVATA_HOME/bin/airavata-server.sh - This will start SimpleAxis2Server on port 8080
 <br></br>
 AIRAVATA_HOME/bin/xbaya-gui.sh - This will start XBaya GUI application.
@@ -135,14 +133,10 @@ register this application and wrap it as
 <ul>
 <li>
 <p>First, we will register a Host Description using menu XBaya -&gt; Add Host.
-  If Registry location is unknown, there will be a popup asking for a Registry URL.
+  There will be a popup asking for a credentials used to connect to the Registry.
   In the popup give the following values to the parameters and click Ok (keep the default
values as it is.)
 <table border="1">
     <tr>
-        <td><b>URL</b></td>
-        <td>http://localhost:8081/rmi</td>
-    </tr>
-    <tr>
         <td><b>Username</b></td>
         <td>admin</td>
     </tr>

Modified: websites/staging/airavata/trunk/content/documentation/system/airavata-in-5-minutes.html
==============================================================================
--- websites/staging/airavata/trunk/content/documentation/system/airavata-in-5-minutes.html
(original)
+++ websites/staging/airavata/trunk/content/documentation/system/airavata-in-5-minutes.html
Tue Oct 23 02:54:43 2012
@@ -129,14 +129,12 @@
 <li>Extract the Airavata binary distribution to some path in the file system (say <code>AIRAVATA_HOME</code>)<ol>
 <li>If you built from source then your binary is in modules/distribution/target</li>
 <li>If you are using Windows + Cygwin you need to set permissions on some files with
"chmod 755 bin/*.sh"<ul>
-<li>we don't currently provide bat scripts for the following actions - patches welcome</li>
+<li>we provide bat scripts for the following actions as well.</li>
 </ul>
 </li>
 </ol>
 </li>
 <li>Start airavata:<br><ul>
-<li>Start Airavata repository on port 8081<br>
-        <tab><code>$ AIRAVATA_HOME/bin/jackrabbit-server.sh</code></li>
 <li>Start SimpleAxis2Server on port 8080<br>
         <code>$ AIRAVATA_HOME/bin/airavata-server.sh</code> </li>
 <li>Start XBaya<br>
@@ -157,10 +155,6 @@
 <p>If you are using the default Jackrabbit server from Airavata use the following information,
 <table border="1">
     <tr>
-        <td width="100"><b>URL</b></td>
-        <td>http://localhost:8081/rmi</td>
-    </tr>
-    <tr>
         <td><b>Username</b></td>
         <td>admin</td>
     </tr>



Mime
View raw message