You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@juddi.apache.org by ac...@apache.org on 2003/12/08 21:14:11 UTC
cvs commit: ws-juddi/site/src/documentation/content/xdocs faq.xml index.xml lists.xml site.xml tabs.xml
acutright 2003/12/08 12:14:11
Added: site/src/documentation/content/xdocs faq.xml index.xml
lists.xml site.xml tabs.xml
Log:
Revision Changes Path
1.1 ws-juddi/site/src/documentation/content/xdocs/faq.xml
Index: faq.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
<document>
<header>
<title>jUDDI FAQ</title>
</header>
<body>
<section>
<title>JDK Requirements</title>
<p>jUDDI 0.7 requires a 1.4.x JDK. You can compile and run with
a 1.3.x JDK, if you remove the package org.apache.juddi.auth.crypt from your codebase.
</p>
</section>
<section>
<title>Using an embedded database</title>
<p >You can use the juddi.useConnectionPool property (and other
related properties) to avoid using the JNDI lookup. Here's a sample setup of
juddi.properties </p>
<p>Required JDBC DataSource properties<br>
</br>juddi.dataSource = java:comp/env/jdbc/juddiDB
required JDBC Driver properties
juddi.useConnectionPool = true<br>
</br>juddi.jdbcDriver = org.hsqldb.jdbcDriver
juddi.jdbcURL =
jdbc:hsqldb:C:/jakarta-tomcat/server/webapps/juddi/WEB-INF/hsql/juddidb
juddi.jdbcUser = sa
juddi.jdbcPassword =
# optional JDBC Driver connection pool properties
juddi.jdbcMinConnections = 3
juddi.jdbcMaxConnections = 50
juddi.jdbcMaxWaitTime = 15000
juddi.jdbcRetryInterval = 1000</p>
</section>
<section>
<title>How do I configure jUDDI to run with Tomcat, MySQL and use a JNDI DataSource?</title>
<p >A good setup is discussed here <a
href="http://sourceforge.net/mailarchive/forum.php?thread_id=2429672&forum_id=7138" target="_setup">http://sourceforge.net/mailarchive/forum.php?thread_id=2429672&forum_id=7138</a></p>
</section>
<h3><a name="_Writing_a_pluggable"></a>Writing a pluggable authentication module</h3>
<p >
You can configure jUDDI to use one of the three Authentication modules supplied or you can write your own Authenticator that integrates jUDDI with your organizations authentication mechanism. All you have to do to create your own Authenticator is:
</p>
<ul>
<li>create a class that implements the Authenticator interface (your Authenticator)</li>
<li>create a class that extends the AuthenticatorFactory abstract class (your Authenticator's Factory)</li>
<li>specify your AuthenticatorFactory in jUDDI's property file ("juddi.properties").</li>
</ul>
Example: <b>juddi.authFactory = org.apache.juddi.auth.simple.SimpleAuthenticatorFactory</b>
<p>
In the example above you'll need to replace "org.apache.juddi.auth.simple.SimpleAuthenticatorFactory" with the fully qualified name of your AuthenticatorFactory class. Take a look at the SimpleAuthenticator and SimpleAuthenticationFactory classes in the "org.apache.juddi.auth.simple" package for an example
</p>
<h3><a name="_Using_a_datastore"></a>Using a datastore without JDBC</h3>
<p >jUDDI is designed to allow different persistence (datastore)
implementations to be "plugged-in". The JDBCDataStore included with
jUDDI attempts to support as many as the mainstream RDBMS's as possible
(Oracle, DB2, Sybase, MySQL - even HSQLDB). </p>
<p>If you're interested in using something other than JDBC or if you want to
take advantages of proprietary features of your RDBMS (i.e. using stored
procedures to improve performance) then you will need to develop your own
datastore implementation. To do so you'll need to create implementations of the
DataStoreFactory and DataStore interfaces in the org.apache.juddi.datastore package
and make a change to the jUDDI properties file to use your new DataStoreFactory
implementation (i.e. the judd.dataStoreFactory property) instead of the one
supplied. </p>
<p>Check out jUDDI's JDBCDataStoreFactory and JDBCDataStore for examples. </p>
<h3><a name="_Can_I_use"></a>Which Application Servers does jUDDI support?</h3>
<p >jUDDI is known to work with a number of application
servers like Tomcat, Sybase EAServer and Borland Enterprise Server 5.2 and 6.0.
A Sybase EAServer deployment guide is available <a href="easerver.html" target="_easerver">here</a>.</p>
<p ><br />
<b><i>jUDDI FAQ Contributors:
</i></b> <em>Steve Viens</em>
<em>Anou Manavalan</em>
<em>Rupesh Ramachandran</em>
<em>Andy Cutright</em> </p>
</body>
</document>
1.1 ws-juddi/site/src/documentation/content/xdocs/index.xml
Index: index.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
<document>
<header>
<title>Welcome to jUDDI</title>
</header>
<body>
<section>
<title>Overview</title>
<p>jUDDI (pronounced "Judy") is an open source Java implementation
of the Universal Description, Discovery, and Integration (UDDI) specification
for Web Services. </p>
</section>
<section>
<title>Key jUDDI Benefits</title>
<ul>
<li>Open Source</li>
<li>Platform Independent</li>
<li>Supports for JDK 1.3.1 and later</li>
<li>UDDI version 2.0 compliant implementation</li>
<li>Use with any relational database that supports ANSI standard SQL (MySQL,
DB2, Sybase, JDataStore, etc.)</li>
<li>Deployable on any Java application server that supports the Servlet
2.3 specification (Jakarta Tomcat, WebSphere, WebLogic, Borland Enterprise Server, JRun, etc.)</li>
<li>jUDDI registry supports a clustered deployment configuration.</li>
<li>Easy integration with existing authentication systems</li>
</ul>
</section>
<section>
<title>About UDDI</title>
<p>UDDI stands for Universal Description, Discovery and Integration. The
UDDI specification enables businesses to quickly, easily, and dynamically
find and transact with one another. UDDI enables a business to (i) describe
its business and its services, (ii) discover other businesses that offer
desired services, and (iii) integrate with these other businesses. UDDI
enables companies to publish how they want to conduct business on the
web, potentially fueling growth of Web services-based electronic commerce.</p>
<p>UDDI benefits businesses of all sizes by creating a global, platform-independent,
open architecture for describing businesses and services, discovering
those businesses and services, and integrating businesses using the
Internet.</p>
<p>The UDDI project is a sweeping industry initiative. The project creates
a platform-independent, open framework for describing services, discovering
businesses, and integrating business services using the Internet, as
well as an operational registry that is available today.</p>
<p>UDDI is the first truly cross-industry effort driven by all major platform
and software providers, as well as marketplace operators and e-business
leaders. These technology and business pioneers are acting as the initial
catalysts to quickly develop UDDI and related technologies.</p>
<p>The UDDI project takes advantage of WorldWide Web Consortium (W3C)
and Internet Engineering Task Force (IETF) standards such as Extensible
Markup Language (XML), and HTTP and Domain Name System (DNS) protocols.
Additionally, cross platform programming features are addressed by adopting
early versions of the proposed Simple Object Access Protocol (SOAP)
known as XML Protocol messaging specifications found at the W3C Web
site. The UDDI protocol is the building block that will enable businesses
to quickly, easily and dynamically find and transact with one another
using their preferred applications.</p>
<p>Additional information regarding UDDI can be found at <a href="http://www.uddi.org/" target="_top">UDDI.org</a>.</p>
<p></p>
</section>
</body>
</document>
1.1 ws-juddi/site/src/documentation/content/xdocs/lists.xml
Index: lists.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.2//EN" "http://apache.org/forrest/dtd/document-v12.dtd">
<document>
<header>
<title>jUDDI Community</title>
</header>
<body>
<section>
<title>Web Services PMC</title>
<p>jUDDI is now being incubated within the Web Services PMC as part of the
to the <a href="http://incubator.apache.org/">Apache Incubator</a>. Part
of this transition involves decommissioning the lists formely hosted
on SourceForge.net including juddi-announce, juddi-users and juddi-developers.
</p>
</section>
<section>
<title>jUDDI users</title>
<p>The <STRONG>juddi-user@ws.apache.org</STRONG> mailing list
is the primary source of support for anyone using jUDDI. Use this list for
posting questions (and answers) related to the installation, configuration
and use of jUDDI.
</p>
</section>
<section>
<title>jUDDI dev</title>
<p>The <STRONG>juddi-dev@ws.apache.org</STRONG> mailing list is for
discussions about the jUDDI architecture, build process, testing and
implementation details.
</p>
</section>
<section>
<title>Archives</title>
<p><STRONG>NOTE:</STRONG> Archives for the original jUDDI lists will continue to
be available on SourceForge.net indefinitely. Click
<A href="http://sourceforge.net/mail/?group_id=42875" target="_top">here</A> to
browse them.
</p>
</section>
</body>
</document>
1.1 ws-juddi/site/src/documentation/content/xdocs/site.xml
Index: site.xml
===================================================================
<?xml version="1.0"?>
<!--
Forrest site.xml
This file contains an outline of the site's information content. It is used to:
- Generate the website menus (though these can be overridden - see docs)
- Provide semantic, location-independent aliases for internal 'site:' URIs, eg
<link href="site:changes"> links to changes.html (or ../changes.html if in
subdir).
- Provide aliases for external URLs in the external-refs section. Eg, <link
href="ext:cocoon"> links to http://xml.apache.org/cocoon/
See http://xml.apache.org/forrest/linking.html for more info
-->
<site label="jUDDI" href="" xmlns="http://apache.org/forrest/linkmap/1.0" tab="">
<about label="About">
<index label="Index" href="index.html" description="jUDDI"/>
<index label="FAQ" href="faq.html" description="FAQ"/>
<index label="Community" href="lists.html" description="Community"/>
</about>
<all>
<whole_site_html label="Whole Site HTML" href="site.html"/>
<whole_site_html label="Whole Site PDF" href="site.pdf"/>
</all>
<external-refs>
<xml.apache.org href="http://xml.apache.org/">
<forrest href="forrest/">
<validation href="validation.html"/>
<webapp href="your-project.html#webapp"/>
<document-v11 href="document-v11.html"/>
</forrest>
<cocoon href="cocoon/"/>
</xml.apache.org>
</external-refs>
</site>
1.1 ws-juddi/site/src/documentation/content/xdocs/tabs.xml
Index: tabs.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tabs PUBLIC "-//APACHE//DTD Cocoon Documentation Tab V1.0//EN" "http://apache.org/forrest/dtd/tab-cocoon-v10.dtd">
<tabs software="MyProj"
title="MyProj"
copyright="Foo"
xmlns:xlink="http://www.w3.org/1999/xlink">
<!-- The rules are:
@dir will always have '/@indexfile' added.
@indexfile gets appended to @dir if the tab is selected. Defaults to 'index.html'
@href is not modified unless it is root-relative and obviously specifies a
directory (ends in '/'), in which case /index.html will be added
If @id's are present, site.xml entries with a matching @tab will be in that tab.
-->
<tab id="" label="Home" dir="" indexfile="index.html"/>
<!-- Add new tabs here, eg:
<tab label="How-Tos" dir="community/howto/"/>
<tab label="XML Site" dir="xml-site/"/>
-->
</tabs>