airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r829721 - in /websites/staging/airavata/trunk/content: ./ airavata/architecture/ws-messenger.html airavata/community/people.html airavata/documentation/howto/howto.html
Date Wed, 22 Aug 2012 17:41:01 GMT
Author: buildbot
Date: Wed Aug 22 17:41:01 2012
New Revision: 829721

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html
    websites/staging/airavata/trunk/content/airavata/community/people.html
    websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Aug 22 17:41:01 2012
@@ -1 +1 @@
-1375975
+1376153

Modified: websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html (original)
+++ websites/staging/airavata/trunk/content/airavata/architecture/ws-messenger.html Wed Aug
22 17:41:01 2012
@@ -128,13 +128,13 @@ subscriptions and notifications which wi
 <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 
+<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.

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 Wed Aug 22 17:41:01
2012
@@ -106,7 +106,9 @@
 
   <div id="content">
     <h1 class="title">Airavata Contributors </h1>
-    <p>Apache Airavata is a community developed project. The list below is a partial
list of contributors to the project (sorted by last name), for a complete list you'd haveto
look at all contributors to our issue tracker, mailing list and version control.</p>
+    <p>Apache Airavata is a community developed project. The list below is a partial
list of contributors to the project
+(sorted by last name), for a complete list you'd have to look at all contributors to our
issue tracker, mailing list
+and version control.</p>
 <p><strong>Committers:</strong></p>
 <ul>
 <li><a href="http://lahiru.org">Lahiru Gunathilake</a></li>

Modified: websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html (original)
+++ websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html Wed Aug
22 17:41:01 2012
@@ -184,18 +184,26 @@ database and AIRAVATA_HOME/standalone-se
 </ul>
 </li>
 <li>
-<p>Change msgBox.properties and msgBroker.properties files with database driver name
and database urls as below.</p>
+<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>broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata
+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 this. </li>
 </ul>
 </li>
-<li>
-<p>Change the driver class name based on your driver and copy your driver to AIRAVATA_HOME/standalon-server/lib
directory and start the server.. You are ready to go with 
-   Mysql database.</p>
-</li>
+</ol>
+<h1 id="for-mysql-datbase">For mysql datbase</h1>
+<p>msgBox.jdbc.driver=com.mysql.jdbc.Driver
+msgBox.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&amp;password=airavata</p>
+<h1 id="default-derby-database">Default derby database</h1>
+<h1 id="msgboxjdbcdriverorgapachederbyjdbcembeddeddriver">msgBox.jdbc.driver=org.apache.derby.jdbc.EmbeddedDriver</h1>
+<h1 id="msgboxjdbcurljdbcderbywsmgcreatetrueuserairavatapasswordairavata">msgBox.jdbc.url=jdbc:derby:wsmg;create=true;user=airavata;password=airavata</h1>
+<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>
 </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



Mime
View raw message