You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@juddi.apache.org by ks...@apache.org on 2014/02/05 20:29:45 UTC
svn commit: r1564891 [22/39] - in /juddi/cms-site/trunk/content/docs/3.2: ./
juddi-client-guide/ juddi-client-guide/html/ juddi-client-guide/html/css/
juddi-client-guide/html/images/ juddi-client-guide/html/images/community/
juddi-client-guide/html/ima...
Added: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch05.html
URL: http://svn.apache.org/viewvc/juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch05.html?rev=1564891&view=auto
==============================================================================
--- juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch05.html (added)
+++ juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch05.html Wed Feb 5 19:29:33 2014
@@ -0,0 +1,159 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 5. jUDDI Server Configuration (juddiv3.xml)</title><link rel="stylesheet" type="text/css" href="css/jbossorg.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><link rel="home" href="index.html" title="Apache jUDDI Guide"/><link rel="up" href="index.html" title="Apache jUDDI Guide"/><link rel="prev" href="ch04.html" title="Chapter 4. Administration"/><link rel="next" href="ch06.html" title="Chapter 6. UDDI Seed Data"/><link rel="copyright" href="ln-d5e27.html" title="Legal Notice"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></
p><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch06.html"><strong>Next</strong></a></li></ul><div class="chapter" title="Chapter 5. jUDDI Server Configuration (juddiv3.xml)"><div class="titlepage"><div><div><h2 class="title"><a id="jUDDIServerConfig"/>Chapter 5. jUDDI Server Configuration (<code class="literal">juddiv3.xml</code>)</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="ch05.html#_authentication">5.1. Authentication</a></span></dt><dt><span class="section"><a href="ch05.html#_startup">5.2. Startup</a></span></dt><dt><span class="section"><a href="ch05.html#_email">5.3. Email</a></span></dt><dt><span class="section"><a href="ch05.html#_query_properties">5.4. Query Properties</a></span></dt><dt><span class="section"><a href="ch05.html#_rmi_proxy">5.5. RMI Pro
xy</a></span></dt><dt><span class="section"><a href="ch05.html#_key_generation_and_cryptography">5.6. Key Generation and Cryptography</a></span></dt><dt><span class="section"><a href="ch05.html#_subscription">5.7. Subscription</a></span></dt><dt><span class="section"><a href="ch05.html#_custody_transfer">5.8. Custody Transfer</a></span></dt><dt><span class="section"><a href="ch05.html#_validation">5.9. Validation</a></span></dt><dt><span class="section"><a href="ch05.html#_deploying_two_or_more_juddi_server_on_the_same_application_server">5.10. Deploying two or more jUDDI server on the same application server</a></span></dt><dt><span class="section"><a href="ch05.html#_juddi_gui_configuration">5.11. jUDDI GUI Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#_juddi_client_uddi_xml_settings">5.12. jUDDI Client uddi.xml Settings</a></span></dt><dt><span class="section"><a href="ch05.html#_encryption_keys">5.13. Encryption Keys</a></span></dt><dt><span class="se
ction"><a href="ch05.html#_customizing_the_juddi_gui">5.14. Customizing the juddi-gui</a></span></dt></dl></div>
+
+<p>jUDDI will look for a <code class="literal">juddiv3.xml</code> file on the root of the classpath. In the <code class="literal">juddiv3.war</code> you can find it in <code class="literal">juddiv3.war/WEB_INF/classes/juddiv3.xml</code>.</p>
+<pre class="screen">Since 3.2 the jUDDI server now uses an XML file for configuration. Previous versions uses a properties file.</pre>
+
+<div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h2>Important</h2>
+<p>When referring to configuration <span class="emphasis"><em>properties</em></span>, we are really referencing the XPath to specified setting.</p>
+</div>
+
+<div class="section" title="5.1. Authentication"><div class="titlepage"><div><div><h2 class="title"><a id="_authentication"/>5.1. Authentication</h2></div></div></div>
+
+<div class="table"><a id="d5e1317"/><p class="title"><strong>Table 5.1. Authentication properties that can be referenced in the juddiv3.xml file</strong></p><div class="table-contents">
+
+
+ <table summary="Authentication properties that can be referenced in the juddiv3.xml file" border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/auth/authenticator/class</em></span></p></td><td align="left" valign="top"><p>The jUDDI authenticator class to use. See Chapter <add ref> of the Userguide for the choices provided.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>org.apache.juddi.v3.auth.JUDDIAuthenticator</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/aut
h/Inquiry</em></span></p></td><td align="left" valign="top"><p>This flag determines whether authentication (the presence of a getAuthToken) is required on queries invoking the Inquiry API. By default, jUDDI sets this to false for ease of use.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/auth/token/Timeout</em></span></p></td><td align="left" valign="top"><p>Time in minutes to expire tokes after inactivity.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>15</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/auth/token/Expiration</em></span></p></td><td align="left" valign="top"><p>As of 3.1.5 Duration of time for tokens to expire, regardless of inactivity.</p></td><td align="left" valign="top"><p>N</p></td><td alig
n="left" valign="top"><p><span class="emphasis"><em>15</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/auth/token/enforceSameIPRule</em></span></p></td><td align="left" valign="top"><p>As of 3.2 This setting will enable or disable the auth token check to ensure that auth tokens can only be used from the same IP address that they were issued to..</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>true</em></span></p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.2. Startup"><div class="titlepage"><div><div><h2 class="title"><a id="_startup"/>5.2. Startup</h2></div></div></div>
+
+<div class="table"><a id="d5e1388"/><p class="title"><strong>Table 5.2. Startup properties that can be referenced in the <span class="emphasis"><em>juddiv3.xml</em></span> file</strong></p><div class="table-contents">
+
+
+ <table summary="Startup properties that can be referenced in the juddiv3.xml file" border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/server/baseurl</em></span></p></td><td align="left" valign="top"><p>Token that can be accessed in accessPointURLs and resolved at runtime. Currently this is only used during the Installation process (seeding root data)</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em><a class="ulink" href="http://localhost:8080">http://localhost:8080</a></em></span></p></td></tr><tr><td align="left"
valign="top"><p><span class="emphasis"><em>juddi/root/publisher</em></span></p></td><td align="left" valign="top"><p>The username for the jUDDI root publisher. This is usually just set to "root".</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>root</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/seed/always</em></span></p></td><td align="left" valign="top"><p>Forces seeding of the jUDDI data. This will re-apply all files with the exception of the root data files. Note that this can lead to losing data that was added to the entities that are re-seeded, since data is not merged.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/server/name</em></span></p></td><td align="left" valign="top"><p>This token is referenced
in the install data. Note that you can use any tokens, and that their values can be set here or as system parameters..</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/server/port</em></span></p></td><td align="left" valign="top"><p>This token is referenced in the install data. Note that you can use any tokens, and that their values can be set here or as system parameters..</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/nodeId</em></span></p></td><td align="left" valign="top"><p>The Node ID uniquely identifies this server. Use caution when changing the Node ID after jUDDI has been started, you may not be able to edit any existing entities! ..</p></td><td align=
"left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>uddi:juddi.apache.org:node1</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi//load/install/data</em></span></p></td><td align="left" valign="top"><p>This property allows you to cancel loading of the jUDDI install data.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>false</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/locale</em></span></p></td><td align="left" valign="top"><p>The default local to use. This currently is not used.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>en_US</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/operatorEmailAddress</em></span></p></td><td align="left" valign="top"><p>The UDDI Operator Contact Email Address. This currently is not use
d.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>admin@juddi.org</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/persistenceunit.name</em></span></p></td><td align="left" valign="top"><p>The persistence name for the jUDDI database that is specified in the persistence.xml file.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>juddiDatabase</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/configuration/reload/delay</em></span></p></td><td align="left" valign="top"><p>The time in milliseconds in which juddiv3.xmlis polled for changes.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>5000</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+<div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="caution" style="margin-left: 0.5in; margin-right: 0.5in;"><h2>Caution</h2>
+<p>Take caution in changing the jUDDI Node ID. If jUDDI has already been started at least once and the Node ID is changed, an existing records will not be editable. If you want to change from the default value, do so before you first start jUDDI by editing the configuration file.</p>
+</div>
+
+</div>
+<div class="section" title="5.3. Email"><div class="titlepage"><div><div><h2 class="title"><a id="_email"/>5.3. Email</h2></div></div></div>
+
+<div class="table"><a id="d5e1526"/><p class="title"><strong>Table 5.3. As of 3.1.5, jUDDI supports Email delivery options for Subscription API functions. Email properties can be referenced in the <span class="emphasis"><em>juddiv3.xml</em></span> file</strong></p><div class="table-contents">
+
+
+ <table summary="As of 3.1.5, jUDDI supports Email delivery options for Subscription API functions. Email properties can be referenced in the juddiv3.xml file" border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/from</em></span></p></td><td align="left" valign="top"><p>The Operatorâs Email address</p></td><td align="left" valign="top"><p>Y</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>jUDDI@example.org</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/host</em></span></p></td><td alig
n="left" valign="top"><p>The hostname of the SMTP server</p></td><td align="left" valign="top"><p>Y</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>localhost</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/port</em></span></p></td><td align="left" valign="top"><p>The portname of the SMTP server</p></td><td align="left" valign="top"><p>Y</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>25</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/socketFactory.class</em></span></p></td><td align="left" valign="top"><p>If set, specifies the name of a class that implements the <span class="emphasis"><em>javax.net.SocketFactory interface</em></span>. This class will be used to create SMTP sockets.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top">Â </td></tr><tr><td align="left" valign="top"><p><span class="emp
hasis"><em>juddi/mail/smtp/socketFactory/fallback</em></span></p></td><td align="left" valign="top"><p>If set to true, failure to create a socket using the specified socket factory class will cause the socket to be created using the <span class="emphasis"><em>java.net.Socket</em></span> class. Defaults to true.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>true</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/starttls/enable</em></span></p></td><td align="left" valign="top"><p>f true, enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection before issuing any login commands. Note that an appropriate trust store must configured so that the client will trust the serverâs certificate. Defaults to false.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span clas
s="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/socketFactory/port</em></span></p></td><td align="left" valign="top"><p>Specifies the port to connect to when using the specified socket factory. If not set, the default port will be used.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>465</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/auth</em></span></p></td><td align="left" valign="top"><p>If true, attempt to authenticate the user using the AUTH command. Defaults to false.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>false</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/user</em></span></p></td><td align="left" valign="top"><p>Username used to authenticate to
the SMTP server</p></td><td align="left" valign="top"><p>Y, if <span class="emphasis"><em>juddi/mail/smtp/auth</em></span> is true</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>juddi@apache.org</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/password</em></span></p></td><td align="left" valign="top"><p>Username used to authenticate to the SMTP server</p></td><td align="left" valign="top"><p>Y, if <span class="emphasis"><em>juddi/mail/smtp/auth</em></span> is true</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>secret</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/mail/smtp/password@encrypted</em></span></p></td><td align="left" valign="top"><p>If the password is encrypted, the setting juddi/cryptor is the Cryptographic provider used to decrypt at runtime.</p></td><td align="left" valign="top"><p>Y, if <span class="emphasis"><em>juddi/
mail/smtp/auth</em></span> is true</p></td><td align="left" valign="top"><p>false</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.4. Query Properties"><div class="titlepage"><div><div><h2 class="title"><a id="_query_properties"/>5.4. Query Properties</h2></div></div></div>
+
+<div class="table"><a id="d5e1666"/><p class="title"><strong>Table 5.4. Query properties that can be referenced in the <span class="emphasis"><em>juddiv3.xml</em></span> file</strong></p><div class="table-contents">
+
+
+ <table summary="Query properties that can be referenced in the juddiv3.xml file" border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxBusinessesPerPublisher</em></span></p></td><td align="left" valign="top"><p>The maximum number of UDDI Businesses that can be registered per publisher. A value of <span class="emphasis"><em>-1</em></span> indicates any number of businesses is allowed (These values can be overridden at the individual publisher level)</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>-1</p></td></tr><tr><td align="left" valign
="top"><p><span class="emphasis"><em>juddi/maxServicesPerBusiness</em></span></p></td><td align="left" valign="top"><p>The maximum number of UDDI BusinessServices allowed per Business. A value of <span class="emphasis"><em>-1</em></span> indicates any number of artifacts is valid (These values can be
+# overridden at the individual publisher level).</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>-1</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxBindingsPerService</em></span></p></td><td align="left" valign="top"><p>The maximum number of UDDI TemplateBindings allowed per BusinessService. A value of <span class="emphasis"><em>-1</em></span> indicates any number of artifacts is valid (These values can be overridden at the individual publisher level).</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>-1</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxTModelsPerPublisher</em></span></p></td><td align="left" valign="top"><p>The maximum number of TModels allowed per publisher. A value of <span class="emphasis"><em>-1</em></span> indicates any number of artifacts is valid (These values can be overridden at the individual publisher level).</p>
</td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>-1</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxInClause</em></span></p></td><td align="left" valign="top"><p>The maximum number of "IN" clause parameters. Some RDMBS limit the number of parameters allowed in a SQL "IN" clause.</p></td><td align="left" valign="top"><p>Y</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>1000</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxNameElementsAllowed</em></span></p></td><td align="left" valign="top"><p>The maximum name size and maximum number of name elements allows in several of the <span class="emphasis"><em>FindXxxx</em></span> and <span class="emphasis"><em>SaveXxxx</em></span> UDDI functions</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>5</em></span>]</p></td></tr><tr><td align="left
" valign="top"><p><span class="emphasis"><em>juddi/maxNameLength</em></span></p></td><td align="left" valign="top"><p>The maximum name size of name elements</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>255</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/maxRows</em></span></p></td><td align="left" valign="top"><p>The maximum number of rows returned in a find_* operation. Each call can set this independently, but this property defines a global maximum. This is related to the <span class="emphasis"><em>maxInClause</em></span> setting (the same?).</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>1000</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.5. RMI Proxy"><div class="titlepage"><div><div><h2 class="title"><a id="_rmi_proxy"/>5.5. RMI Proxy</h2></div></div></div>
+
+<p title="These properties are used to bring up RMI server socket. The settings allow for registering this service to JNDI.">
+<strong>These properties are used to bring up RMI server socket. The settings allow for registering this service to JNDI. </strong>
+RMI Proxy properties that can be referenced in the <span class="emphasis"><em>juddiv3.xml</em></span> file and is only used by RMITransport.
+</p>
+<div class="informaltable">
+
+ <table border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/proxy/factory/initial</em></span></p></td><td align="left" valign="top"><p>JNDI Contect Facory</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>org.jnp.interfaces.NamingContextFactory</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/proxy/provider/url</em></span></p></td><td align="left" valign="top"><p>JNDI Provider Address</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<
span class="emphasis"><em>jnp://localhost:1099</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/proxy/factory/url/pkg</em></span></p></td><td align="left" valign="top"><p>JNDI Naming Convention</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>org.jboss.naming</em></span>]</p></td></tr></tbody></table>
+</div>
+
+</div>
+<div class="section" title="5.6. Key Generation and Cryptography"><div class="titlepage"><div><div><h2 class="title"><a id="_key_generation_and_cryptography"/>5.6. Key Generation and Cryptography</h2></div></div></div>
+
+<div class="table"><a id="d5e1825"/><p class="title"><strong>Table 5.5. UDDI Key generation properties that can be referenced in the <code class="literal">juddiv3.xml</code> file.</strong></p><div class="table-contents">
+
+
+ <table summary="UDDI Key generation properties that can be referenced in the juddiv3.xml file." border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/cryptor</em></span></p></td><td align="left" valign="top"><p>jUDDI Cryptor implementation class that jUDDI will use to encrypt and decrypt password settings</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>org.apache.juddi.cryptor.DefaultCryptor</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/keygenerator</em></span></p></t
d><td align="left" valign="top"><p>Key generator implementation that jUDDI will use to create UDDI keys if no key is passed in by the user.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>org.apache.juddi.keygen.KeyGenerator</em></span></p></td></tr><tr><td align="left" valign="top"><p>_juddi/uuidgen _</p></td><td align="left" valign="top"><p>UUID generator implementation that jUDDI will use to create UUIDs.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>org.apache.juddi.uuidgen.DefaultUUIDGen</em></span></p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.7. Subscription"><div class="titlepage"><div><div><h2 class="title"><a id="_subscription"/>5.7. Subscription</h2></div></div></div>
+
+<div class="table"><a id="d5e1874"/><p class="title"><strong>Table 5.6. Subscription properties that can be referenced in the <span class="emphasis"><em>juddiv3.xml</em></span> file.</strong></p><div class="table-contents">
+
+
+ <table summary="Subscription properties that can be referenced in the juddiv3.xml file." border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/subscription/expiration/days</em></span></p></td><td align="left" valign="top"><p>Days before a subscription expires</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>30</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/subscription/chunkexpiration/minutes</em></span></p></td><td align="left" valign="top"><p>Minutes before a "chunk
ed" subscription call expires</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>5</em></span>]</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/interval</em></span></p></td><td align="left" valign="top"><p>Specifies the interval at which the notification timer triggers. This is the upper boundary set by the registry. Between the user defined endDate of a Subscription and this value, the registry will pick the earliest date.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>3000000</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/start/buffer</em></span></p></td><td align="left" valign="top"><p>Specifies the amount of time to wait before the notification timer initially fires</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>
20000</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/acceptableLagtime</em></span></p></td><td align="left" valign="top"><p>Specifies the amount of time (in ms) from which to determine if the server is overload and to skip notifications. Notifications during this cycle will not be repeated (i.e. never be delivered)</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>10000</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/maxTries</em></span></p></td><td align="left" valign="top"><p>Specifies the number of times to attempt the delivery of messages to subscribers.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>3</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/maxTriesResetInterval</em></span></p></td><td align="left" valign="top"><p>Once the maximum delivery attempts have been
made, the server will add that endpoint to an ignore list, which is reset every N ms.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>600000</p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/notification/sendAuthTokenWithResultList</em></span></p></td><td align="left" valign="top"><p>Sends a valid authentication token for the owning user of the subscription in the subscription notification result message. Unless it is specifically needed, this is recommended to be set to false.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>false</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.8. Custody Transfer"><div class="titlepage"><div><div><h2 class="title"><a id="_custody_transfer"/>5.8. Custody Transfer</h2></div></div></div>
+
+<div class="table"><a id="d5e1974"/><p class="title"><strong>Table 5.7. Transfer properties that can be referenced in the _juddiv3.xml file.</strong></p><div class="table-contents">
+
+
+ <table summary="Transfer properties that can be referenced in the _juddiv3.xml file." border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/transfer/expiration/days</em></span></p></td><td align="left" valign="top"><p>Days before a transfer request expires.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>3</em></span>]</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.9. Validation"><div class="titlepage"><div><div><h2 class="title"><a id="_validation"/>5.9. Validation</h2></div></div></div>
+
+<div class="table"><a id="d5e2001"/><p class="title"><strong>Table 5.8. These settings are for validating the data that users store in jUDDI. They can be referenced in the _juddiv3.xml file.</strong></p><div class="table-contents">
+
+
+ <table summary="These settings are for validating the data that users store in jUDDI. They can be referenced in the _juddiv3.xml file." border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>juddi/validation/enforceReferentialIntegrity</em></span></p></td><td align="left" valign="top"><p>As of 3.1.5 This setting will force referential integrity for all tModels (except keyGenerators), category bags, bindingTemplate/AccessPoint/hostingRedirector (referencing another host), tModelInstanceParms and anything else that references a KeyName default value is true. Set to false for backwards c
ompatibility or for a more lax registry.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p>[<span class="emphasis"><em>true</em></span>]</p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.10. Deploying two or more jUDDI server on the same application server"><div class="titlepage"><div><div><h2 class="title"><a id="_deploying_two_or_more_juddi_server_on_the_same_application_server"/>5.10. Deploying two or more jUDDI server on the same application server</h2></div></div></div>
+
+<div class="orderedlist" title="It is possible to deploy one or more jUDDI servers to the same application server. You will need copy the juddiv3.war archive (letâs say you copied it to juddiv3a.war), and change the following settings to have it connect to a different database:"><p class="title"><strong>It is possible to deploy one or more jUDDI servers to the same application server. You will need copy the juddiv3.war archive (letâs say you copied it to juddiv3a.war), and change the following settings to have it connect to a different database:</strong></p><ol class="orderedlist" type="1"><li class="listitem">
+edit the <code class="literal">juddiv3a/META-INF/context.xml</code> (and <code class="literal">conf/Catalina/localhost/juddiv3a.xml</code>) to use the <span class="emphasis"><em>jdbc/JuddiADS</em></span> datasource, and add <span class="emphasis"><em>a</em></span> to the url: <code class="literal">url="jdbc:derby:target/juddi-derby-test-db-v3a;create=true"</code>
+</li><li class="listitem">
+edit the <span class="emphasis"><em>juddiv3a/WEB-INF/classes/META-INF/persistence.xml</em></span> to use <code class="literal"><non-jta-data-source>java:comp/env/jdbc/JuddiADS</code> and <code class="literal">persistence-unit name="juddiADatabase"</code>
+</li><li class="listitem">
+edit the <span class="emphasis"><em>juddiv3a/WEB-INF/classes/juddiv3.xml</em></span> to have
+<code class="literal"><persistenceunit><name>juddiADatabase</name></persistenceunit></code>
+</li></ol></div>
+
+<p>This will create a new jUDDI server under the <a class="ulink" href="http://localhost:8080/juddiv3a">http://localhost:8080/juddiv3a</a> url which connects to the juddi-derby-test-db-v3a Derby database.</p>
+</div>
+<div class="section" title="5.11. jUDDI GUI Configuration"><div class="titlepage"><div><div><h2 class="title"><a id="_juddi_gui_configuration"/>5.11. jUDDI GUI Configuration</h2></div></div></div>
+
+<p>The jUDDI GUI (juddi-gui.war) has one place for configuration settings, the jUDDI Client config file.</p>
+</div>
+<div class="section" title="5.12. jUDDI Client uddi.xml Settings"><div class="titlepage"><div><div><h2 class="title"><a id="_juddi_client_uddi_xml_settings"/>5.12. jUDDI Client uddi.xml Settings</h2></div></div></div>
+
+<p>Defined in WEB-INF/classes/META-INF/uddi.xml, there are many settings to configure. All of these are clearly defined by the jUDDI Client Configuration Guide. The juddi-gui, uses things a bit differently, so here are the relevant parts to use. Note: this is xpath notation.</p>
+<div class="itemizedlist"><ul class="itemizedlist"><li class="listitem">
+uddi/client/nodes/properties, not used
+</li><li class="listitem">
+uddi/client/clerks, not used
+</li><li class="listitem">
+uddi/client/nodes/node, all URLs except juddiApiUrl (not used)
+</li><li class="listitem">
+uddi/client/signature, all validation related settings
+</li><li class="listitem">
+uddi/client/subscriptionCallbacks, not used
+</li><li class="listitem">
+uddi/client/XtoWsdl, not used
+</li></ul></div>
+
+<p>In addition, there a special section added just for the juddi-gui.war</p>
+<div class="table"><a id="d5e2068"/><p class="title"><strong>Table 5.9. jUDDI GUI Configuration</strong></p><div class="table-contents">
+
+
+ <table summary="jUDDI GUI Configuration" border="1"><colgroup><col width="25*" class="col_1"/><col width="25*" class="col_2"/><col width="25*" class="col_3"/><col width="25*" class="col_4"/></colgroup><thead><tr><th align="left" valign="top">Property Name</th><th align="left" valign="top">Description</th><th align="left" valign="top">Required</th><th align="left" valign="top">Default Value or [Example Value]</th></tr></thead><tbody><tr><td align="left" valign="top"><p><span class="emphasis"><em>uddi/config/props/authtype</em></span></p></td><td align="left" valign="top"><p>This controls the authentication mode to connect to a UDDI server. Most implementations of UDDI use the security service, however others use HTTP based authentication. In this case, us the value of <span class="emphasis"><em>HTTP</em></span>, otherwise <span class="emphasis"><em>UDDI_AUTH</em></span></p></td><td align="left" valign="top"><p>Y</p></td><td align="left" valign="top"><p><span class="emphasis"><em>UD
DI_AUTH</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>uddi/config/props/enableAutomaticLogouts</em></span></p></td><td align="left" valign="top"><p>This flag determines whether automatic logouts is enabled. By default, jUDDI-gui sets this to false for ease of use. (true/false)</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>false</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>udddi/config/props/enableAutomaticLogouts/duration</em></span></p></td><td align="left" valign="top"><p>Time in milliseconds to force an automatic logout after inactivity.</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>900000</em></span></p></td></tr><tr><td align="left" valign="top"><p><span class="emphasis"><em>uddi/config/props/configLocalHostOnly</em></span></p></td><td align="left" valign="top"><p>
If false, the configuration page will be available from anywhere. If true, it will only be accessible from the server hosting juddi-gui. (true/false)</p></td><td align="left" valign="top"><p>N</p></td><td align="left" valign="top"><p><span class="emphasis"><em>true</em></span></p></td></tr></tbody></table>
+</div></div><br class="table-break"/>
+
+</div>
+<div class="section" title="5.13. Encryption Keys"><div class="titlepage"><div><div><h2 class="title"><a id="_encryption_keys"/>5.13. Encryption Keys</h2></div></div></div>
+
+<p>By default, the juddi-gui will use a randomly generated AES encryption key to help protect user credentials stored in the session object. This key is generated using the "StartupServlet" defined in the web.xml file of juddi-gui.war/WEB-INF/web.xml and then it is stored at the path juddi-gui.war/META-INF/config.properties@key.</p>
+<p>If the start up servlet fails to start, any authenticate operation of the juddi-gui will fail.</p>
+<div xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h2>Important</h2>
+<p>The user account that the container for juddi-gui runs as must have write access to the file juddi-gui.war/META-INF/config.properties.</p>
+</div>
+
+</div>
+<div class="section" title="5.14. Customizing the juddi-gui"><div class="titlepage"><div><div><h2 class="title"><a id="_customizing_the_juddi_gui"/>5.14. Customizing the juddi-gui</h2></div></div></div>
+
+<p>The juddi-gui has a mechanism that you can use to alter the appearance of every page. This is typically used for organizations that require legal notifications, banners or warnings on every page for one reason or another. To add your own html to every page, edit the file in</p>
+<pre class="screen">juddi-gui/user/banner.jsp</pre>
+
+</div>
+</div><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch04.html"><strong>Prev</strong>Chapter 4. Administration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch06.html"><strong>Next</strong>Chapter 6. UDDI Seed Data</a></li></ul></body></html>
\ No newline at end of file
Propchange: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch05.html
------------------------------------------------------------------------------
svn:executable = *
Added: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch06.html
URL: http://svn.apache.org/viewvc/juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch06.html?rev=1564891&view=auto
==============================================================================
--- juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch06.html (added)
+++ juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch06.html Wed Feb 5 19:29:33 2014
@@ -0,0 +1,108 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 6. UDDI Seed Data</title><link rel="stylesheet" type="text/css" href="css/jbossorg.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><link rel="home" href="index.html" title="Apache jUDDI Guide"/><link rel="up" href="index.html" title="Apache jUDDI Guide"/><link rel="prev" href="ch05.html" title="Chapter 5. jUDDI Server Configuration (juddiv3.xml)"/><link rel="next" href="ch07.html" title="Chapter 7. How to deploy jUDDI To?"/><link rel="copyright" href="ln-d5e27.html" title="Legal Notice"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</stro
ng></a></p><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch07.html"><strong>Next</strong></a></li></ul><div class="chapter" title="Chapter 6. UDDI Seed Data"><div class="titlepage"><div><div><h2 class="title"><a id="chapter-UDDISeedData"/>Chapter 6. UDDI Seed Data</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="ch06.html#_seed_data_files">6.1. Seed Data Files</a></span></dt><dt><span class="section"><a href="ch06.html#_tokens_in_the_seed_data">6.2. Tokens in the Seed Data</a></span></dt><dt><span class="section"><a href="ch06.html#_customer_seed_data">6.3. Customer Seed Data</a></span></dt></dl></div>
+
+<p>This information is relevant for both understanding how jUDDIâs default data is set when jUDDI first runs (i.e. to a new database). Itâs also useful for scripting or automating the deployment of a jUDDI server within your organization which will enable you to prepopulate the data.</p>
+<p>As of UDDI v3, each registry need to have a "root" publisher. The root publisher is the owner of the UDDI services (inquiry, publication, etc). There can only be one root publisher per node. JUDDI ships some default seed data for the root account. The default data can be found in the juddi-core-3.x.jar, under juddi_install_data/. By default jUDDI installs two Publishers: "root" and "uddi". Root owns the root partition, and uddi owns all the other seed data such as pre-defined tModels.</p>
+<div class="section" title="6.1. Seed Data Files"><div class="titlepage"><div><div><h2 class="title"><a id="_seed_data_files"/>6.1. Seed Data Files</h2></div></div></div>
+
+<p>For each publisher there are four seed data files that will be read the first time you start jUDDI:</p>
+<pre class="screen"><publisher>_Publisher.xml
+<publisher>_tModelKeyGen.xml
+<publisher>_BusinessEntity.xml
+<publisher>_tModels.xml</pre>
+
+<p>For example the content of the root_Publisher.xml looks like</p>
+<pre class="screen"><publisher xmlns="urn:juddi-apache-org:api_v3" authorizedName="root">
+ <publisherName>root publisher</publishername>
+ <isAdmin>true</isadmin>
+</publisher></pre>
+
+<p>Each publisher should have its own key generator schema so that custom generated keys cannot end up being identical to keys generated by other publishers. It is therefor that the each publisher need to define their own KenGenerator tModel. The tModel Key Generator is defined in the file root_tModelKeyGen.xml and the content of this file is</p>
+<pre class="screen"><tModel tModelKey="uddi:juddi.apache.org:keygenerator" xmlns="urn:uddi-org:api_v3">
+ <name>uddi-org:keyGenerator</name>
+ <description>Root domain key generator</description>
+ <overviewDoc>
+ <overviewURL useType="text">
+ http://uddi.org/pubs/uddi_v3.htm#keyGen
+ </overviewurl>
+ </overviewdoc>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:types"
+ keyName="uddi-org:types:keyGenerator"
+ keyValue="keyGenerator" />
+ </categorybag>
+</tmodel></pre>
+
+<p>This means that the legal format of keys used by the root publisher need to be in the form uddi:juddi.apache.org:<text-of-chioce></text-of-chioce> The use of other types of format will lead to an <span class="emphasis"><em>illegal key</em></span> error. The root publisher can only own one KeyGenerator while any other publisher can own more then one KeyGenerator. KeyGenerators should not be shared unless there is a good reason to do so. If you want to see your publisher with more then just the one KeyGenerator tModel, you can use the <publisher></publisher>_tModels.xml file.
+Finally, in the <publisher></publisher>_BusinessEntity.xml file can be used to setup Business and Service data. In the root_BusinessEntity.xml we specified the ASF Business, and the UDDI services; Inquiry, Publish, etc.:</p>
+<pre class="screen"><businessEntity xmlns="urn:uddi-org:api_v3" xmlns:xml="http://www.w3.org/XML/1998/namespace" businessKey="uddi:juddi.apache.org:businesses-asf">
+ <!-- Change the name field to represent the name of your registry -->
+ <name xml:lang="en">An Apache jUDDI Node</name>
+ <!-- Change the description field to provided a brief description of your registry -->
+ <description xml:lang="en">This is a UDDI v3 registry node as implemented by Apache jUDDI.</description>
+ <discoveryURLs>
+ <!-- This discovery URL should point to the home installation URL of jUDDI -->
+ <discoveryURL useType="home">${juddi.server.baseurl}/juddiv3</discoveryURL>
+ </discoveryURLs>
+ <categoryBag>
+ <keyedReference tModelKey="uddi:uddi.org:categorization:nodes" keyValue="node" />
+ </categoryBag>
+ <businessServices>
+ <!-- As mentioned above, you may want to provide user-defined keys for these (and the services/bindingTemplates below. Services that you
+ don't intend to support should be removed entirely -->
+ <businessService serviceKey="uddi:juddi.apache.org:services-inquiry" businessKey="uddi:juddi.apache.org:businesses-asf">
+ <name xml:lang="en">UDDI Inquiry Service</name>
+ <description xml:lang="en">Web Service supporting UDDI Inquiry API</description>
+ <bindingTemplates>
+ <bindingTemplate bindingKey="uddi:juddi.apache.org:servicebindings-inquiry-ws" serviceKey="uddi:juddi.apache.org:services-inquiry">
+ <description>UDDI Inquiry API V3</description>
+ <!-- This should be changed to the WSDL URL of the inquiry API. An access point inside a bindingTemplate will be found for every service
+ in this file. They all must point to their API's WSDL URL -->
+ <accessPoint useType="wsdlDeployment">${juddi.server.baseurl}/services/inquiry?wsdl</accessPoint>
+ <tModelInstanceDetails>
+ <tModelInstanceInfo tModelKey="uddi:uddi.org:v3_inquiry">
+ <instanceDetails>
+ <instanceParms>
+ <![CDATA[
+ <?xml version="1.0" encoding="utf-8" ?>
+ <UDDIinstanceParmsContainer xmlns="urn:uddi-org:policy_v3_instanceParms">
+ <defaultSortOrder>
+ uddi:uddi.org:sortorder:binarysort
+ </defaultSortOrder>
+ </UDDIinstanceParmsContainer>
+ ]]>
+ </instanceParms>
+ </instanceDetails>
+ </tModelInstanceInfo>
+ </tModelInstanceDetails>
+ <categoryBag>
+ <keyedReference keyName="uddi-org:types:wsdl" keyValue="wsdlDeployment" tModelKey="uddi:uddi.org:categorization:types"/>
+ </categoryBag>
+ </bindingTemplate>
+ </bindingTemplates>
+ </businessService>
+<!-- snip -->
+</businessService></pre>
+
+<p>Note that the seeding process only kicks off if no publishers exist in the database. So this will only work with a clean database, unless you set juddi/seed/always to true. Then it will re-apply all files with the exception of the root data files. Note that this can lead to losing data that was added to entities that are re-seeded, since data is not merged.</p>
+</div>
+<div class="section" title="6.2. Tokens in the Seed Data"><div class="titlepage"><div><div><h2 class="title"><a id="_tokens_in_the_seed_data"/>6.2. Tokens in the Seed Data</h2></div></div></div>
+
+<p>You may have noticed the tokens in the root_BusinessEntity.xml file (${juddi.server.baseurl}. The value of this tokens can set in the juddiv3.xml file. The value substitution takes place at runtime, so that different nodes can do the substitution with their own value if needed.</p>
+</div>
+<div class="section" title="6.3. Customer Seed Data"><div class="titlepage"><div><div><h2 class="title"><a id="_customer_seed_data"/>6.3. Customer Seed Data</h2></div></div></div>
+
+<p>In your deployment you probably do not want to use the Seed Data shipped with the default jUDDI install. The easiest way to overwrite this data is to add it to a directory call juddi_custom_install_data in the juddiv3.war/WEB-INF/classes/ directory. That way you donât have to modify the juddi-core-3.x.jar. Additionally if your root publisher is not called "root" you will need to set the juddi/root/publisher property in the juddiv3.xml file to something other then</p>
+<pre class="screen">juddi/root/publisher=root</pre>
+
+<p>The juddiv3.war ships with two example data directory. One for the Sales Affiliate, and one for the Marketing Affiliate. To use the Sales Seed Data, in the juddiv3.war/WEB-INF/classes/, rename the directory</p>
+<pre class="screen">*nix
+mv RENAME4Sales_juddi_custom_install_data juddi_custom_install_data
+Win*
+ren RENAME4Sales_juddi_custom_install_data juddi_custom_install_data</pre>
+
+<p>before you start jUDDI the first time. It will then use this data to populate the database. If you want to rerun you can trash the database it created and restart tomcat. Donât forget to set the tokens in the juddiv3.xml file.</p>
+</div>
+</div><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch05.html"><strong>Prev</strong>Chapter 5. jUDDI Server Configuration (juddiv3.xm...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch07.html"><strong>Next</strong>Chapter 7. How to deploy jUDDI To?</a></li></ul></body></html>
\ No newline at end of file
Propchange: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch06.html
------------------------------------------------------------------------------
svn:executable = *
Added: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch07.html
URL: http://svn.apache.org/viewvc/juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch07.html?rev=1564891&view=auto
==============================================================================
--- juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch07.html (added)
+++ juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch07.html Wed Feb 5 19:29:33 2014
@@ -0,0 +1,266 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 7. How to deploy jUDDI To?</title><link rel="stylesheet" type="text/css" href="css/jbossorg.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><link rel="home" href="index.html" title="Apache jUDDI Guide"/><link rel="up" href="index.html" title="Apache jUDDI Guide"/><link rel="prev" href="ch06.html" title="Chapter 6. UDDI Seed Data"/><link rel="next" href="ch08.html" title="Chapter 8. Extending UDDI"/><link rel="copyright" href="ln-d5e27.html" title="Legal Notice"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><ul xmlns:d="ht
tp://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch06.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch08.html"><strong>Next</strong></a></li></ul><div class="chapter" title="Chapter 7. How to deploy jUDDI To?"><div class="titlepage"><div><div><h2 class="title"><a id="chapter-HowToDeployjUDDITo"/>Chapter 7. How to deploy jUDDI To?</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="ch07.html#_tomcat">7.1. Tomcat</a></span></dt><dd><dl><dt><span class="section"><a href="ch07.html#_openjpa_and_cxf">7.1.1. OpenJPA and CXF</a></span></dt><dt><span class="section"><a href="ch07.html#_hibernate_and_cxf">7.1.2. Hibernate and CXF</a></span></dt><dt><span class="section"><a href="ch07.html#_openjpa_and_axis2">7.1.3. OpenJPA and Axis2</a></span></dt></dl></dd><dt><span class="section"><a href="ch07.html#_jboss">7.2. JBoss</a></span></dt><dd><dl><dt
><span class="section"><a href="ch07.html#_jbossas_6_0_0_ga">7.2.1. JBossAS 6.0.0.GA</a></span></dt><dt><span class="section"><a href="ch07.html#_jbossas_7_x_jbosseap_6_x">7.2.2. JBossAS 7.x/JBossEAP-6.x</a></span></dt></dl></dd><dt><span class="section"><a href="ch07.html#_deploying_to_glassfish">7.3. Deploying to Glassfish</a></span></dt><dd><dl><dt><span class="section"><a href="ch07.html#_glassfish_jars">7.3.1. Glassfish jars</a></span></dt><dt><span class="section"><a href="ch07.html#_configure_the_juddi_datasource">7.3.2. Configure the JUDDI datasource</a></span></dt><dt><span class="section"><a href="ch07.html#_add_juddiv3_cxf_war">7.3.3. Add juddiv3-cxf.war</a></span></dt><dt><span class="section"><a href="ch07.html#_run_juddi">7.3.4. Run jUDDI</a></span></dt></dl></dd></dl></div>
+
+<p>The jUDDI distribution ships preconfigured on Tomcat - it runs out of the box. All you have to do in go into the <code class="literal">juddi-distro-<version>/juddi-tomcat-<version>/bin</code> directory and start up Tomcat. All of this just as described in <a class="xref" href="ch02.html" title="Chapter 2. Getting Started">Chapter 2, <em>Getting Started</em></a>.</p>
+<p>By default the <code class="literal">juddiv3.war</code> is configured to use OpenJPA and CXF. If you want to change your JPA or WS provider, or youâd like to run on a different container then this chapter may come in handy, as there a number of scripted <span class="emphasis"><em>profiles</em></span> to change the configuration and dependencies in the <code class="literal">juddiv3.war</code>. To run these maven based scripts you need to go into <code class="literal">juddi-distro-<version>/juddiv3-war</code> directory.</p>
+<div class="section" title="7.1. Tomcat"><div class="titlepage"><div><div><h2 class="title"><a id="_tomcat"/>7.1. Tomcat</h2></div></div></div>
+
+<div class="section" title="7.1.1. OpenJPA and CXF"><div class="titlepage"><div><div><h3 class="title"><a id="_openjpa_and_cxf"/>7.1.1. OpenJPA and CXF</h3></div></div></div>
+
+<p>Target platform Tomcat and Derby using OpenJPA and CXF. Both OpenJPA and CXF are packaged up in the juddiv3.war.</p>
+<pre class="screen">mvn clean package -P openjpa</pre>
+
+<p>Then copy the <code class="literal">target/juddiv3.war</code> to the <code class="literal"><tomcat>/webapps</code> directory.</p>
+</div>
+<div class="section" title="7.1.2. Hibernate and CXF"><div class="titlepage"><div><div><h3 class="title"><a id="_hibernate_and_cxf"/>7.1.2. Hibernate and CXF</h3></div></div></div>
+
+<p>Target platform Tomcat and Derby using Hibernate and CXF. Both Hibernate and CXF are packaged up in the juddiv3.war.</p>
+<pre class="screen">mvn clean package -P hibernate</pre>
+
+<p>Then copy the <code class="literal">target/juddiv3.war</code> to the <code class="literal"><tomcat>/webapps</code> directory.</p>
+</div>
+<div class="section" title="7.1.3. OpenJPA and Axis2"><div class="titlepage"><div><div><h3 class="title"><a id="_openjpa_and_axis2"/>7.1.3. OpenJPA and Axis2</h3></div></div></div>
+
+<p>Target platform Tomcat and Derby using OpenJPA and Apache Axis2. Both Hibernate and Axis2 are packaged up in the juddiv3.war.</p>
+<pre class="screen">mvn clean package -P axis2</pre>
+
+<p>Then copy the <code class="literal">target/juddiv3.war</code> to the <code class="literal"><tomcat>/webapps</code> directory.</p>
+</div>
+</div>
+<div class="section" title="7.2. JBoss"><div class="titlepage"><div><div><h2 class="title"><a id="_jboss"/>7.2. JBoss</h2></div></div></div>
+
+<div class="section" title="7.2.1. JBossAS 6.0.0.GA"><div class="titlepage"><div><div><h3 class="title"><a id="_jbossas_6_0_0_ga"/>7.2.1. JBossAS 6.0.0.GA</h3></div></div></div>
+
+<p>This section describes how to deploy juddi to JBoss 6.0.0.GA.</p>
+<p>First, download jboss-6.0.0.GA - the zip or tar.gz bundle may be found at <a class="ulink" href="http://www.jboss.org/jbossas/downloads/">http://www.jboss.org/jbossas/downloads/</a>. Download the bundle and uncompress it.</p>
+<div class="section" title="7.2.1.1. Hibernate and JBossWS-Native"><div class="titlepage"><div><div><h4 class="title"><a id="_hibernate_and_jbossws_native"/>7.2.1.1. Hibernate and JBossWS-Native</h4></div></div></div>
+
+<p>Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-native. The juddiv3.war relies on Hibernate and JBossWS-native in the appserver.</p>
+<pre class="screen">mvn clean package -P hibernate-jbossws-native</pre>
+
+<p>Then copy the <code class="literal">target/juddiv3.war</code> to the <code class="literal"><jboss>/server/default/deploy</code> directory.</p>
+</div>
+<div class="section" title="7.2.1.2. Hibernate and JBossWS-CXF"><div class="titlepage"><div><div><h4 class="title"><a id="_hibernate_and_jbossws_cxf"/>7.2.1.2. Hibernate and JBossWS-CXF</h4></div></div></div>
+
+<p>Target platform JBoss-6.x and HSQL using Hibernate and JBossWS-cxf. The juddiv3.war relies on Hibernate and JBossWS-cxf in the appserver.</p>
+<pre class="screen">mvn clean package -P hibernate-jbossws-cxf</pre>
+
+<div class="variablelist" title="KNOWN ISSUES"><p class="title"><strong>KNOWN ISSUES</strong></p><dl><dt><span class="term">Issue 1</span></dt><dd>
+<pre class="screen">15:14:37,275 SEVERE [RegistryServlet] jUDDI registry could not be started. org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file: org.apache.commons.configuration.ConfigurationException: org.apache.commons.configuration.ConfigurationException: java.util.zip.ZipException: error in opening zip file</pre>
+
+<p class="simpara">Workaround: deploy juddiv3.war as a directory (not a zip file).</p>
+</dd><dt><span class="term">Issue 2</span></dt><dd>
+<p class="simpara">JBoss-5.x Note that configuration 3 and 4 will also run on JBoss-5.x, but you may run into the following</p>
+<pre class="screen">ERROR [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] (main) [domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve]::Message=src-resolve: Cannot resolve the name ns1:Signature to a element declaration component.</pre>
+
+<p class="simpara">Workaround: Unzip the deployers/jbossws.deployer/jbossws-native-core.jar and add the xmldsig-core-schema.xsd in the schema directory,</p>
+<pre class="screen">10293 Fri May 27 14:40:40 EDT 2011 schema/xmldsig-core-schema.xsd</pre>
+
+<p class="simpara">Edit the file META-INF/jbossws-entities.properties by adding a line at the bottom saying:</p>
+<pre class="screen">http\://www.w3.org/2000/09/xmldsig#=schema/xmldsig-core-schema.xsd</pre>
+
+</dd></dl></div>
+
+<p>Copy juddiv3.war to server/default/deploy and unpack it.</p>
+<p>Insert jboss-web.xml into the juddiv3.war/WEB-INF directory , should look like the following :</p>
+<pre class="screen"><?xml version="1.0" encoding="ISO-8859-1"?>
+
+<!DOCTYPE jboss-web PUBLIC
+ "-//JBoss//DTD Web Application 2.3V2//EN"
+ "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd">
+
+<jboss-web>
+
+ <resource-ref>
+ <res-ref-name>jdbc/JuddiDS</res-ref-name>
+ <jndi-name>java:JuddiDS</jndi-name>
+ </resource-ref>
+ <depends>jboss.jdbc:datasource=JuddiDS,service=metadata</depends>
+
+</jboss-web></pre>
+
+</div>
+<div class="section" title="7.2.1.3. Change web.xml"><div class="titlepage"><div><div><h4 class="title"><a id="_change_web_xml"/>7.2.1.3. Change web.xml</h4></div></div></div>
+
+<p>Replace the WEB-INF/web.xml with the jbossws-native-web.xml within docs/examples/appserver.</p>
+</div>
+<div class="section" title="7.2.1.4. Configure Datasource"><div class="titlepage"><div><div><h4 class="title"><a id="_configure_datasource"/>7.2.1.4. Configure Datasource</h4></div></div></div>
+
+<p>The first step for configuring a datasource is to copy your JDBC driver into the classpath. Copy your JDBC driver into ${jboss.home.dir}/server/${configuration}/lib, where configuration is the profile you wish to start with (default, all, etc.). Example :</p>
+<pre class="screen">cp mysql-connector-java-5.0.8-bin.jar /opt/jboss-5.1.0.GA/server/default/lib</pre>
+
+<p>Next, configure a JBoss datasource file for your db. Listed below is an example datasource for MySQL :</p>
+<pre class="screen"><?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>JuddiDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/juddiv3</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name>root</user-name>
+ <password></password>
+ <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
+
+ <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
+ <metadata>
+ <type-mapping>mySQL</type-mapping>
+ </metadata>
+ </local-tx-datasource>
+</datasources></pre>
+
+<p>Next, make a few changes to the juddiv3.war/classes/META-INF/persistence.xml. Change the "hibernate.dialect" property to match the database you have chosen for persistence. For MySQL, change the value of hibernate.dialect to "org.hibernate.dialect.MySQLDialect". A full list of dialects available can be found in the hibernate documentation (<a class="ulink" href="https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html">https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html</a>). Next, change the <jta-data-source> tags so that it reads <non-jta-data-source>, and change the value from java:comp/env/jdbc/JuddiDS to java:/JuddiDS.</p>
+</div>
+</div>
+<div class="section" title="7.2.2. JBossAS 7.x/JBossEAP-6.x"><div class="titlepage"><div><div><h3 class="title"><a id="_jbossas_7_x_jbosseap_6_x"/>7.2.2. JBossAS 7.x/JBossEAP-6.x</h3></div></div></div>
+
+<p>This section describes how to deploy juddi to JBossAS 7, WildFly and JBossEAP 6</p>
+<div class="section" title="7.2.2.1. Hibernate and JBossWS-CXF"><div class="titlepage"><div><div><h4 class="title"><a id="_hibernate_and_jbossws_cxf_2"/>7.2.2.1. Hibernate and JBossWS-CXF</h4></div></div></div>
+
+<p>This profile is not yet scripted as there is an issue with Hibernate, see JUDDI-587.</p>
+</div>
+<div class="section" title="7.2.2.2. OpenJPA and JBossWS-CXF"><div class="titlepage"><div><div><h4 class="title"><a id="_openjpa_and_jbossws_cxf"/>7.2.2.2. OpenJPA and JBossWS-CXF</h4></div></div></div>
+
+<p>Target platform using HSQL using OpenJPA and JBossWS-CXF. The juddiv3.war relies on the openjpa and cxf modules in the appserver.</p>
+<pre class="screen">mvn clean package -P openjpa-jboss7up</pre>
+
+<p>Then copy the <code class="literal">target/juddiv3.war</code> to the <code class="literal"><jboss>/standalone/deployments</code> directory.</p>
+<p>Not all the JBoss appservers mentioned above shipped a module for openjpa. If it did not then you can create it:</p>
+<p>In your appserver create the following directory structure <code class="literal"><jboss>/modules/system/layers/base/org/apache/openjpa/main</code> and the following files:</p>
+
+<pre class="literallayout">module.xml openjpa-2.2.1.jar serp-1.13.1.jar</pre>
+
+
+<p>where the contents of the modules.xml should look like</p>
+
+<pre class="literallayout"><module xmlns="urn:jboss:module:1.1" name="org.apache.openjpa">
+ <resources>
+ <resource-root path="openjpa-2.2.1.jar"/>
+ <resource-root path="serp-1.13.1.jar"/>
+ </resources>
+ <dependencies>
+ <module name="javax.persistence.api"/>
+ <module name="javax.transaction.api"/>
+ <module name="javax.validation.api"/>
+ <module name="org.apache.commons.lang"/>
+ <module name="org.apache.commons.collections"/>
+ <module name="org.apache.log4j"/>
+ </dependencies>
+</module></pre>
+
+
+<p>Next create the directory structure <code class="literal"><jboss>/modules/system/layers/base/org/jboss/as/jpa/openjpa/main</code> with the files:</p>
+
+<pre class="literallayout">jboss-as-jpa-openjpa-7.1.1.Final.jar module.xml</pre>
+
+
+<p>where the contents of the modules.xml should look like</p>
+
+<pre class="literallayout"><?xml version="1.0" encoding="UTF-8"?>
+<!-- contains the JPA integration classes for OpenJPA 2.x -->
+<module xmlns="urn:jboss:module:1.1" name="org.jboss.as.jpa.openjpa">
+ <properties>
+ <property name="jboss.api" value="private"/>
+ </properties>
+
+ <resources>
+ <resource-root path="jboss-as-jpa-openjpa-7.1.1.Final.jar"/>
+ <!-- Insert resources here -->
+ </resources>
+
+ <dependencies>
+ <module name="javax.annotation.api"/>
+ <module name="javax.persistence.api"/>
+ <module name="javax.transaction.api"/>
+
+ <module name="org.jboss.as.jpa.spi"/>
+ <module name="org.jboss.logging"/>
+ <module name="org.jboss.jandex"/>
+
+ <module name="org.apache.openjpa" optional="true"/> <!-- org.apache.openjpa:main must be created manually with OpenJPA jars -->
+ </dependencies>
+</module></pre>
+
+
+<p>and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml
+add dependency</p>
+
+<pre class="literallayout"><module name="org.jboss.as.jpa.openjpa"/></pre>
+
+
+</div>
+</div>
+</div>
+<div class="section" title="7.3. Deploying to Glassfish"><div class="titlepage"><div><div><h2 class="title"><a id="_deploying_to_glassfish"/>7.3. Deploying to Glassfish</h2></div></div></div>
+
+<p>This section describes how to deploy juddi to Glassfish 2.1.1. These instructions will use CXF as a webservice framework.</p>
+<p>First, download the glassfish-v2.1.1 installer JAR. Once downloaded,install using the JAR and then run the ant setup script :</p>
+<pre class="screen">java -jar glassfish-installer-v2.1.1-b31g-linux.jar
+cd glassfish
+ant -f setup.xml</pre>
+
+<div class="section" title="7.3.1. Glassfish jars"><div class="titlepage"><div><div><h3 class="title"><a id="_glassfish_jars"/>7.3.1. Glassfish jars</h3></div></div></div>
+
+<p>Copy the following JARs into domains/domain1/lib/ext. Note that for the purposes of this example, we have copied the MySQL driver to domains/domain1/lib/ext :</p>
+<pre class="screen">antlr-2.7.6.jar
+cglib-nodep-2.1_3.jar
+commons-collections-3.2.1.jar
+commons-logging-1.1.jar
+dom4j-1.6.1.jar
+hibernate-3.2.5.ga.jar
+hibernate-annotations-3.3.0.ga.jar
+hibernate-commons-annotations-3.0.0.ga.jar
+hibernate-entitymanager-3.3.1.ga.jar
+hibernate-validator-3.0.0.ga.jar
+javassist-3.3.ga.jar
+jboss-common-core-2.0.4.GA.jar
+jta-1.0.1B.jar
+mysql-connector-java-5.0.8-bin.jar
+persistence-api-1.0.jar</pre>
+
+</div>
+<div class="section" title="7.3.2. Configure the JUDDI datasource"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_the_juddi_datasource"/>7.3.2. Configure the JUDDI datasource</h3></div></div></div>
+
+<p>First, using the asadmin administration tool, import the following file :</p>
+<pre class="screen"><?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE resources PUBLIC "-//Sun Microsystems Inc.//DTD Application Server 9.0 Domain//EN" "*<install directory>/lib/dtds/sun-resources_1_3.dtd*">
+<resources>
+<jdbc-connection-pool name="mysql-pool" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" res-type="javax.sql.DataSource">
+<property name="user" value="juddi"/>
+<property name="password" value="juddi"/>
+<property name="url" value="jdbc:mysql://localhost:3306/juddiv3"/>
+</jdbc-connection-pool>
+<jdbc-resource enabled="true" jndi-name="jdbc/mysql-resource" object-type="user" pool-name="mysql-pool"/>
+</resources></pre>
+
+<pre class="screen">asadmin add-resources resource.xml</pre>
+
+<p>Then use the Glassfish administration console to create a "jdbc/juddiDB" JDBC datasource resource based on the mysql-pool Connection Pool.</p>
+</div>
+<div class="section" title="7.3.3. Add juddiv3-cxf.war"><div class="titlepage"><div><div><h3 class="title"><a id="_add_juddiv3_cxf_war"/>7.3.3. Add juddiv3-cxf.war</h3></div></div></div>
+
+<p>Unzip the juddiv3-cxf WAR into domains/domain1/autodeploy/juddiv3.war .</p>
+<p>Add a sun-web.xml file into juddiv3.war/WEB-INF. Make sure that the JNDI references matches the JNDI location you configured in the Glassfish administration console.</p>
+<pre class="screen"><?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE sun-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD
+Application Server 9.0 Servlet 2.5//EN'
+'http://www.sun.com/software/appserver/dtds/sun-web-app_2_5-0.dtd'>
+<sun-web-app>
+<resource-ref>
+<res-ref-name>jdbc/juddiDB</res-ref-name>
+<jndi-name>jdbc/juddiDB</jndi-name>
+</resource-ref>
+</sun-web-app></pre>
+
+<p>Next, make a few changes to juddiv3.war/WEB-INF/classes/META-INF/persistence.xml . Change the "hibernate.dialect" property to match the database that you have chosen for persistence. For MySQL, change the value of hibernate.dialect to "org.hibernate.dialect.MySQLDialect". A full list of dialects available can be found in the hibernate documentation (<a class="ulink" href="https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html">https://www.hibernate.org/hib_docs/v3/api/org/hibernate/dialect/package-summary.html</a>). Next, change the <jta-data-source> change the value from java:comp/env/jdbc/JuddiDS to java:comp/env/jdbc/JuddiDB.</p>
+</div>
+<div class="section" title="7.3.4. Run jUDDI"><div class="titlepage"><div><div><h3 class="title"><a id="_run_juddi"/>7.3.4. Run jUDDI</h3></div></div></div>
+
+<p>Start up the server :</p>
+<pre class="screen">cd bin
+asadmin start-domain domain1</pre>
+
+<p>Once the server is deployed, browse to <a class="ulink" href="http://localhost:8080/juddiv3">http://localhost:8080/juddiv3</a></p>
+</div>
+</div>
+</div><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch06.html"><strong>Prev</strong>Chapter 6. UDDI Seed Data</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch08.html"><strong>Next</strong>Chapter 8. Extending UDDI</a></li></ul></body></html>
\ No newline at end of file
Propchange: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch07.html
------------------------------------------------------------------------------
svn:executable = *
Added: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch08.html
URL: http://svn.apache.org/viewvc/juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch08.html?rev=1564891&view=auto
==============================================================================
--- juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch08.html (added)
+++ juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch08.html Wed Feb 5 19:29:33 2014
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Chapter 8. Extending UDDI</title><link rel="stylesheet" type="text/css" href="css/jbossorg.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"/><link rel="home" href="index.html" title="Apache jUDDI Guide"/><link rel="up" href="index.html" title="Apache jUDDI Guide"/><link rel="prev" href="ch07.html" title="Chapter 7. How to deploy jUDDI To?"/><link rel="next" href="ch09.html" title="Chapter 9. Digital Signatures"/><link rel="copyright" href="ln-d5e27.html" title="Legal Notice"/><meta xmlns:d="http://docbook.org/ns/docbook" xmlns:rf="java:org.jboss.highlight.XhtmlRendererFactory" http-equiv="Content-Type" content="text/html; charset=UTF-8"/></head><body><p xmlns:d="http://docbook.org/ns/docbook" id="title"><a href="http://www.jboss.org" class="site_href"><strong>JBoss.org</strong></a><a href="http://docs.jboss.org/" class="doc_href"><strong>Community Documentation</strong></a></p><ul xmlns:d
="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch07.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch09.html"><strong>Next</strong></a></li></ul><div class="chapter" title="Chapter 8. Extending UDDI"><div class="titlepage"><div><div><h2 class="title"><a id="_extending_uddi"/>Chapter 8. Extending UDDI</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="section"><a href="ch08.html#_authentication_modules">8.1. Authentication modules</a></span></dt><dt><span class="section"><a href="ch08.html#_subscription_notification_handlers">8.2. Subscription Notification Handlers</a></span></dt><dt><span class="section"><a href="ch08.html#_keyedreference_value_set_validation_services">8.3. KeyedReference Value Set Validation Services</a></span></dt><dt><span class="section"><a href="ch08.html#_cryptographic_providers">8.4. Cryptographic Providers</a></span></dt><dt
><span class="section"><a href="ch08.html#_juddi_client_transport">8.5. jUDDI Client Transport</a></span></dt></dl></div>
+
+<p>jUDDI has extensively uses the Interface/Factory pattern to enable configuration runtime options and to provide you, the developer easy insertion points to customize the behavior of jUDDI. The remaining sections of this chapter outline the different technology insertion points.</p>
+<div class="section" title="8.1. Authentication modules"><div class="titlepage"><div><div><h2 class="title"><a id="_authentication_modules"/>8.1. Authentication modules</h2></div></div></div>
+
+<p>Authentication modules are used when the UDDIâs AuthToken is utilized on the Security web service. Itâs function is to point to some kind of user credential store to validate users. See the User Guide for details on whatâs available out of the box.</p>
+<p>All of the provided classes implement the interface .org.apache.juddi.v3.auth.Authenticator.. So, if you wanted something a bit more functional than whatâs provided out of the box. youâll need to implement your own Authenticator. To wire it in, edit the juddiv3.xml file, specifying your class name as the value to the property "juddi/auth/authenticator/class" and then add the class or jar containing your implementation to juddiv3.war/WEB-INF/classes or judiv3.war/WEB-INF/lib respectively.</p>
+</div>
+<div class="section" title="8.2. Subscription Notification Handlers"><div class="titlepage"><div><div><h2 class="title"><a id="_subscription_notification_handlers"/>8.2. Subscription Notification Handlers</h2></div></div></div>
+
+<p>Subscription Notification Handlers are used to asynchronously notify users that something has changed in UDDI. In order to do this, a UDDI Subscription is created that references a specific Binding Template key which represents the service that will be called whens something changes. jUDDI comes with support for Email delivery and the UDDI Subscription Listener Web Service (HTTP) delivery. In addition, jUDDI comes with an example for publishing to an Apache Qpid AMQP pub/sub server, which can be used to further disseminate the change. The following is an exert from the jUDDI Blog posting on this.</p>
+<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+Make a new Java library projects in your IDE of choice. Reference the juddi-core, and uddi-ws projects or JAR files or the Maven dependency equivalent
+</li><li class="listitem">
+Create a class of your own within the following package name: org.apache.juddi.subscription.notify
+</li><li class="listitem">
+The class name MUST follow this pattern: PROTOCOLNotifier Where PROTOCOL is the prefix of whatever URL you want users to be able to use. Hereâs an example using Apache Qpid. Example URL: amqp://guest:guest@client1/development?brokerlist=<span class="emphasis"><em>tcp://localhost:5672</em></span> Class Name: AMQPNotifier. The Notification class basically takes the protocol of the Access Pointâs value, splits it on the character ":" and then grabs the first token "amqp" and converts to upper case. Using this pattern you should be able to insert anything you want.
+</li><li class="listitem">
+Our new shinny class, AMQPNotifier, must implement the interface org.apache.juddi.subscription.notify.Notifier. From there, all you need to do is to add in the jars necessary for your transport mechanism and wire in your own code.
+</li><li class="listitem">
+Deployment is simple. Add your PROTOCOLNotifier jar and its dependencies to the juddiv3.war/WEB-INF/lib folder.
+</li></ol></div>
+
+<p>Note: be careful and watch for conflicting jar file versions. In general, usually moving up a version is ok, but moving down may cause the services to fail unexpectedly.</p>
+<p>To test, create a Service with the BindingTemplateâs Access Pointâs value equal to whatever you need.
+Next, setup a subscription and reference the BindingTemplate key that represents your call back handlerâs end point. Finally, change an item that is covered by the subscriptionâs filter and monitor the log files. Hopefully, you wonât see an unexpected errors.</p>
+</div>
+<div class="section" title="8.3. KeyedReference Value Set Validation Services"><div class="titlepage"><div><div><h2 class="title"><a id="_keyedreference_value_set_validation_services"/>8.3. KeyedReference Value Set Validation Services</h2></div></div></div>
+
+<p>Reserved for future discussion for jUDDI v3.3</p>
+</div>
+<div class="section" title="8.4. Cryptographic Providers"><div class="titlepage"><div><div><h2 class="title"><a id="_cryptographic_providers"/>8.4. Cryptographic Providers</h2></div></div></div>
+
+<p>jUDDI provides cryptographic functions via (Java) juddi-client.jar/org.apache.juddi.v3.client.cryptor and implement the Cryptor interface which provides two simple functions, encrypt and decrypt. (Note: .NET has similar functionality).</p>
+</div>
+<div class="section" title="8.5. jUDDI Client Transport"><div class="titlepage"><div><div><h2 class="title"><a id="_juddi_client_transport"/>8.5. jUDDI Client Transport</h2></div></div></div>
+
+<p>The juddi-clientâs Transport class is an abstract class that you can you alter the transport mechanism used by jUDDIâs client APIs. Included is what would be used in most cases, such as JAXWS, RMI, and InVM (Embedded mode). This can be extended to use whatever you may need.</p>
+</div>
+</div><ul xmlns:d="http://docbook.org/ns/docbook" class="docnav"><li class="previous"><a accesskey="p" href="ch07.html"><strong>Prev</strong>Chapter 7. How to deploy jUDDI To?</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch09.html"><strong>Next</strong>Chapter 9. Digital Signatures</a></li></ul></body></html>
\ No newline at end of file
Propchange: juddi/cms-site/trunk/content/docs/3.2/juddi-guide/html/ch08.html
------------------------------------------------------------------------------
svn:executable = *
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@juddi.apache.org
For additional commands, e-mail: commits-help@juddi.apache.org