svn commit: r793679 - in /websites/production/airavata: ./ content/airavata/docs/registry/xregistry.html

[ra...@apache.org]

Author: raminder
Date: Wed Aug  3 20:23:12 2011
New Revision: 793679

Log:
formatting 

Modified:
    websites/production/airavata/   (props changed)
    websites/production/airavata/content/airavata/docs/registry/xregistry.html

Propchange: websites/production/airavata/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Aug  3 20:23:12 2011
@@ -1 +1 @@
-/websites/staging/airavata/trunk:790685-793675
+/websites/staging/airavata/trunk:790685-793678

Modified: websites/production/airavata/content/airavata/docs/registry/xregistry.html
==============================================================================
--- websites/production/airavata/content/airavata/docs/registry/xregistry.html (original)
+++ websites/production/airavata/content/airavata/docs/registry/xregistry.html Wed Aug  3 20:23:12 2011
@@ -83,20 +83,25 @@ Descriptions, Service Descriptions Abstr
 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>Download code comes with embadded Apache Derby database configrations. To build and run follow these steps</p>
+<div class="codehilite"><pre><span class="n">mvn</span> <span class="n">clean</span> <span class="n">install</span>
+<span class="n">cd</span> <span class="n">target</span><span class="o">/</span><span class="n">dist</span><span class="o">-</span><span class="n">bin</span>
+<span class="o">./</span><span class="n">xregistry</span><span class="o">.</span><span class="n">sh</span> <span class="n">xregistry</span><span class="o">.</span><span class="n">properties</span>
+</pre></div>
+
+
 <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>
+<div class="codehilite"><pre><span class="n">more</span> <span class="n">xregistry</span><span class="o">.</span><span class="nb">log</span>
+</pre></div>
+
+
 <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>
+<div class="codehilite"><pre><span class="nb">kill</span> <span class="sb">`cat xregistry.pid`</span>
+</pre></div>
+
+
 <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>