Return-Path: X-Original-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD3FAD298 for ; Fri, 6 Jul 2012 13:32:40 +0000 (UTC) Received: (qmail 67463 invoked by uid 500); 6 Jul 2012 13:32:40 -0000 Delivered-To: apmail-incubator-airavata-commits-archive@incubator.apache.org Received: (qmail 67414 invoked by uid 500); 6 Jul 2012 13:32:40 -0000 Mailing-List: contact airavata-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: airavata-dev@incubator.apache.org Delivered-To: mailing list airavata-commits@incubator.apache.org Received: (qmail 67406 invoked by uid 99); 6 Jul 2012 13:32:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2012 13:32:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2012 13:32:39 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id B177B238890D for ; Fri, 6 Jul 2012 13:32:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r824789 - in /websites/staging/airavata/trunk/content: ./ airavata/documentation/howto/howto.html Date: Fri, 06 Jul 2012 13:32:19 -0000 To: airavata-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120706133219.B177B238890D@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Fri Jul 6 13:32:19 2012 New Revision: 824789 Log: Staging update by buildbot for airavata Modified: websites/staging/airavata/trunk/content/ (props changed) websites/staging/airavata/trunk/content/airavata/documentation/howto/howto.html Propchange: websites/staging/airavata/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Jul 6 13:32:19 2012 @@ -1 +1 @@ -1358195 +1358197 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 Fri Jul 6 13:32:19 2012 @@ -161,27 +161,35 @@ AIRAVATA_CODE/moduels/ws-messenger/distr

Currently WS-Messenger supports Derby and Mysql databases. Users have to change AIRAVATA_HOME/standalone-server/conf/msgBox.properties to change the message Box database and AIRAVATA_HOME/standalone-server/conf/msgBroker.properties to change the message Broker database.

First create a mysql database in your server with required name (Assume name is:wsmg and username/password is : airavata/airavata).
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

Change msgBox.properties and msgBroker.properties files 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&password=airavata

broker.jdbc.driver=com.mysql.jdbc.Driver

broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&password=airavata

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.
+
First create a mysql database in your server with required name (Assume name is:wsmg and username/password is : airavata/airavata).
+
+
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
+
+
Change msgBox.properties and msgBroker.properties files 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&password=airavata
- broker.jdbc.driver=com.mysql.jdbc.Driver
- broker.jdbc.url=jdbc:mysql://localhost:3306/wsmg?user=airavata&password=airavata
+
+
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.
+

How can I run WS-Messenger without using any database.

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 -msgBroker.properties and msgBox.properties as below.

For Message Box - AIRAVATA_HOME/standalone-server/conf/msgBox.properties - msgBox.usedatabase=true

For Message Broker - AIRAVATA_HOME/standalone-server/conf/msgBroker.properties - broker.storage.type=memory

+msgBroker.properties and msgBox.properties as below. + * For Message Box - AIRAVATA_HOME/standalone-server/conf/msgBox.properties - msgBox.usedatabase=true + * For Message Broker - AIRAVATA_HOME/standalone-server/conf/msgBroker.properties - broker.storage.type=memory

How to use XBaya Arguments

XBaya can be started using AIRAVATA_HOME/bin/xbaya-gui.sh in the binary distribution. During XBaya startup you can give number of arguments for quick detail you can run xbaya-gui.sh with -help.