svn commit: r793559 - /websites/staging/airavata/trunk/content/airavata/docs/registry/xregistry.html

[bu...@apache.org]

Author: buildbot
Date: Mon Aug  1 15:49:03 2011
New Revision: 793559

Log:
Staging update by buildbot

Modified:
    websites/staging/airavata/trunk/content/airavata/docs/registry/xregistry.html

Modified: websites/staging/airavata/trunk/content/airavata/docs/registry/xregistry.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/docs/registry/xregistry.html (original)
+++ websites/staging/airavata/trunk/content/airavata/docs/registry/xregistry.html Mon Aug  1 15:49:03 2011
@@ -73,9 +73,8 @@
 
   <div id="content">
     <h1 class="title">XRegistry</h1>
-    <p>XRegistry is a dcument registry with persistant web service interface, The service supports user
-management, resurcive groups and sharing docuements. With Airavata, the registry provides 
-support for specific document types for Compute and Service Host Descriptions, Application Deployment
+    <p>Airavata XRegistry is a document registry with persistent web service interface, The service supports user
+management and sharing documents. The registry provides support for specific document types like Service Host Descriptions, Application Deployment
 Descriptions, Service Descriptions Abstract and Concrete WSDLs.</p>
 <p>XRegistry's three major capabilities include:
 <em> Registry of Xml documents- Supporting Add, Delete, Get and find documents.
@@ -83,6 +82,25 @@ Descriptions, Service Descriptions Abstr
 * Capability Registry - users can define capability rules saying resource "A" is accessible to User 
 or Group "B". Also given a resource and a User, Xregistry can be asked "Does user have access to 
 the resource?"</p>
+<p><strong>Build and Install</strong></p>
+<p>Download code comes with embadded Apache Derby database configrations. To build and run follow these steps
+ mvn clean install
+ cd target/dist-bin
+ ./xregistry.sh xregistry.properties</p>
+<p>The service will be available on https://{your.host.machine}:6666/xregistry. You can view the WSDL at the URL https://{your.host.machine}:6666/xregistry?wsdl. Check this URL to make sure the service started correctly. The startup scripts first make sure any previously started xregistry has been stopped. Log messages are written to xregistry.log in the dist-bin directory. To see logs </p>
+<blockquote>
+<p>more xregistry.log</p>
+</blockquote>
+<p>Check this log file to make sure the service started with no errors. dist-bin dir is created while at build time and can be copied to any other server with similar configurations. </p>
+<p><strong>Stop XRegistry</strong></p>
+<p>The UNIX process ID for the XRegistry service is located in the file target/dist-bin/xregistry.pid. To stop the service, use the command </p>
+<blockquote>
+<p>kill <code>cat xregistry.pid</code></p>
+</blockquote>
+<p><strong>Setup MySQL</strong></p>
+<p>For production services we recommend MySQL server as Xregistey backend. You can handle this at build or distribution time. </p>
+<p><strong>Build time:</strong> Un-comment mysql dependency in pom.xml. Change databaseDriver and databaseUrl in pom.xml and follow Build and Install steps</p>
+<p><strong>Distribution time</strong> Download the mysql driver "mysql-connector-java" and copy it to target/dist-bin/lib. Update xregistry.properties for jdbcDriver and databaseUrl and restart Xregistry.</p>
   </div>
 
   <div id="footer">