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/03 20:34:37 UTC
svn commit: r1564021 [2/5] - in /juddi/docs/trunk: ./ ClientGuide/
ClientGuide/en-US/ Guide/ Guide/Guide/ Guide/en-US/ images/ images/community/
Added: juddi/docs/trunk/ClientGuide/en-US/ClientGuideUsingthejUDDIGUI.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/ClientGuideUsingthejUDDIGUI.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/ClientGuideUsingthejUDDIGUI.asciidoc (added)
+++ juddi/docs/trunk/ClientGuide/en-US/ClientGuideUsingthejUDDIGUI.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,425 @@
+[[chapter-UsingTheJUDDIGUI]]
+== Using the jUDDI GUI
+
+Starting with jUDDI v3.2, a nearly full featured UDDI v3 compliant web user interface is included called the jUDDI Graphical User Interface, or jUDDI GUI. It is also referred to as the jUDDI Console, or jUDDI User Console. The jUDDI GUI is a web application that can run in most web servlet containers, such as Tomcat and can be deployed along side of the jUDDI Web Services war (juddiv3.war). From the jUDDI GUI, users can browse, search, create, update, digitally sign and delete most UDDI entities, as well as preform custody transfers, configure subscriptions.
+
+As of version 3.2, the jUDDI GUI supports the complete functionality of the following UDDI services
+
+* Inquiry
+* Publish
+* Security
+* Custody Transfer
+* Subscription
+
+
+=== Requirements
+The jUDDI GUI needs two things in order to operate.
+
+* UDDI v3 compliant services
+* A J2EE application server, such as Tomcat, Jboss, Jetty or maybe even in Winstone
+* Optionally, a container level authentication mechanism that supports role based authentication (for remote configuration)
+
+=== Tasks
+The following sections detail how to perform basic tasks using the jUDDI GUI. Hopefully, the user interface is intuitive enough that thorough guidance isn't necessary.
+
+==== Your first sign on
+Typically, the jUDDI GUI is accessed via a URL in a web browser, such as this: http://localhost:8080/juddi-gui. This URL will probably be different from this if someone else set up jUDDI GUI for you (such as a system administrator), in which case, you'll want to ask them for the correct URL. Once loading the page, you should see something similiar to this.
+
+
+[[figure-Using the jUDDI GUI-Welcome]]
+.Welcome to jUDDI, Please select a language.
+image::images/juddi-gui-welcome.png[Welcome to jUDDI, Please select a language]
+
+
+Select a language, then click the button labeled "Go".
+
+TIP: Would you like to see the jUDDI-GUI in a different language that the one's listed and want to offer some translation help? Please contact us!
+
+IMPORTANT: The juddi-gui stores your language preference as a cookie. No personally identifiable information is stored there.
+
+After clicking on "Go", you should see something similar to the next two screen shots.
+
+TIP: Why would it be different? The jUDDI GUI is based on the Twitter Bootstrap API and is designed to automatically rearrange the user interface based on screen size and resolution. Small form factor devices, such as tablets and smart phones generally function as normal, except that the upper navigation bar becomes condensed into a single button.
+
+[[figure-Using the jUDDI GUI-fullmenu]]
+.Full menu bar for computers or large displays.
+image::images/juddi-gui-fullbootstrap-menu.png[Full menu bar for computers or large displays.]
+
+[[figure-Using the jUDDI GUI-tabletmenusmall]]
+.Tablet/Mobile menu bar for small displays.
+image::images/juddi-gui-tabletbootstrap-menu.png[Tablet/Mobile bar for small displays.]
+
+For now, let's just focus on the menu or navigation bar.
+
+=== The Menu Bar
+
+[[figure-Using the jUDDI GUI-menubar]]
+.The Menu Bar.
+image::images/juddi-gui-menu.png[The Menu Bar]
+
+
+The menu bar is designed to make navigation simple and intuitive.
+
+* Home - This sub-menu contains links towards information that is tailored towards you, such as all the businesses you own, subscriptions, custody transfer, and publisher assertion (business relationships)
+* Browse - This sub-menu makes it simple to find stuff in UDDI by letting you flip the pages of the directory.
+* Create - This sub-menu makes it simple to create new UDDI entities, such as businesses, services, tModels, import from WSDL/WADL and some advanced operations.
+* Settings - This page is typically access controlled and enables administrators to remotely configure the juddi-gui.
+* Help - Contains links to the Internet for more help with jUDDI and source code access
+* Login/Logout - many registries require authentication. These buttons support both HTTP and UDDI Auth Token style of authentication.
+
+
+=== Logging in to UDDI Services
+
+Assuming that your UDDI services require authentication, you'll probably want to login with your username and password. This is done using the Login/Logout section the Menu bar (top right of the screen).
+
+[[figure-Using the jUDDI GUI-loginwarn]]
+.Login Warning.
+image::images/juddi-gui-login-warning.png[Login Warning]
+
+
+CAUTION: If you happen to notice that a warning symbol next to the Login button, use caution! Your password may be exposed if you proceed.
+
+TIP: The Warning symbol on the Login portion of the Menu bar will be present unless the following conditions are met: Communication from your browser to juddi-gui is encrypted using SSL/TLS AND the communication from juddi-gui to the UDDI services is encrypted using SSL/TLS.
+
+=== Logging Out
+
+Once logged in, just "Welcome <username>" button to log out.
+
+=== Discover (Browse UDDI)
+
+All of the Browse pages support pagination, that is you can flip through the pages of the database, as if it were a phone book.
+
+In addition, search results can be filtered by language. On each Discover page, you will see the following
+
+[[figure-Using the jUDDI GUI-browseoptions]]
+.Browse Options.
+image::images/juddi-gui-browse-options.png[Browse Options]
+
+
+Click on "Click to Edit", enter your desired language code, then either press enter, or click "Ok" and the results will be filtered automatically. See "Language Codes" for more information.
+
+==== Business Browser
+
+To browse for a UDDI Business, simply click on the word 'Discover' from the top navigation bar and select Businesses.
+
+[[figure-Using the jUDDI GUI-browsebusiness]]
+.Browse Business.
+image::images/juddi-gui-browse-business.png[Browse Business]
+
+When clicking on "Show XX" (XX is the number of services that business has)
+
+
+[[figure-Using the jUDDI GUI-browsebusiness2]]
+.Browse Business Zoomed in.
+image::images/juddi-gui-browse-business2.png[Browse Business Zoomed in]
+
+
+The (+) Plus button will enable you to add a new service that belongs to the business on the same table row.
+
+==== Service Browser
+
+To browse for a UDDI Service, simply click on the word 'Discover' from the top navigation bar and select Services. Clicking on the Name of the service, will bring you to the Service Editor page. Click on the owning Business key to bring you to the Business Editor page.
+
+[[figure-Using the jUDDI GUI-servicebrowser]]
+.Service Browser.
+image::images/juddi-gui-browse-services.png[Service Browser]
+
+
+==== tModel Browser
+
+To browse for a UDDI tModel simply click on the word 'Discover' from the top navigation bar and select tModel. Clicking on the Key of the tModel, will bring you to the tModel Editor page.
+
+[[figure-Using the jUDDI GUI-tmodelbrowser]]
+.tModel Browser.
+image::images/juddi-gui-browse-tmodel.png[tModel Browser]
+
+==== Search
+
+Searching UDDI provides you with the capabilities to make both simple and complex queries. To search, simply click on the word 'Discover' from the top navigation bar and select 'Search'.
+
+[[figure-Using the jUDDI GUI-search]]
+.Search.
+image::images/juddi-gui-search.png[Search]
+
+You first need to select what you're looking for. You can either search a Business, Service, Binding Template, or tModel.
+
+TIP: Not all combinations are valid. For instance, you can't search for a Binding Template by Name because UDDI's binding templates do not have names.
+
+IMPORTANT: UDDI offers a wider, richer search capability. The juddi-gui's search page is in comparison, limited. If you have the need for more complex searches, you'll probably have to write some code to do so.
+
+TIP: When using the wildcards (%, ?), you have to add the find qualifier, approximateMatch.
+
+=== Creating new Entities
+
+The jUDDI GUI has the ability to create and register new UDDI entities.
+
+==== Create a tModel
+
+From the menu, select Create, then tModel. For tModels, the only required item is the Name element.
+
+==== Create a tModek Key Generator (Partition)
+
+IMPORTANT: If you want to create your own UDDI keys (recommended) rather than use the not so user friendly server generated GUID values, then you'll have to make a Key Generator first! Read on!
+
+A tModel Key Generator is a special kind of tModel that enables you to define your own keys (for anything in UDDI) for your own "domain". A "domain" is similar to the Domain Name System used by the Internet to resolve user friendly names, such as www.apache.org, to an IP address. This effectively allows you to define any arbitrary UDDI key prefix that you want. For example, if you wanted a UDDI key defined as "uddi:www.mycompany.com:salesbusiness1", you would first have to create a tModel key generator (partition) with the value of "uddi:www.mycompany.com:keygenerator". TModel keys must start with "uddi:" and end with ":keygenerator". This is part of the UDDI specification and acts as a governance mechanism. You can also create a tModel Key Generator by using the Create tModel menu option and by adding the appropriate settings (assuming you know the secret sauce) or you can simply click on the word 'Create' from the top navigation bar and select 'tModel Partition (Key Generator)'.
+
+[[figure-Using the jUDDI GUI-keypart]]
+.Create a tModel Key Generator (Partition).
+image::images/juddi-gui-tmodel-keygen.png[Create a tModel Key Generator (Partition)]
+
+TIP: You can also use nested partitions such as "uddi:www.mycompany.com:keygenerator" and "uddi:www.mycompany.com:sales:keygenerator". UDDI uses the colon ":" as a separator for partitions. This will enable you to make UDDI keys such as "uddi:www.mycompany.com:biz1" and "uddi:www.mycompany.com:sales:biz2".
+
+TIP: UDDI key names can be at MOST 255 characters long!
+
+==== Create a Business
+
+The UDDI Business entity enables you to define and advertise your business with a variety of ways. To create a new business, simply click on the word 'Create' from the top navigation bar and select 'Business'.
+
+TIP: The "Create", "Business" page is also the same page to use when editing an existing business.
+
+[[figure-Using the jUDDI GUI-createbiz]]
+.Create Business.
+image::images/juddi-gui-create-business.png[Create a Business]
+
+Businesses in UDDI only require you to define at least one name. All of fields are optional. Business entities can have 0 or more of just about everything. For now, let's just make a Name, give it a Value and then save our new business. To add a new Name, click the "+" button next to the "Name". Then click on "Click to edit" next to "Value". If you make a mistake or wish to remove the "Name" or any other element, click on the trash can.
+
+[[figure-Using the jUDDI GUI-createbiz3]]
+.How to Add and Delete items.
+image::images/juddi-gui-create-business3.png[How to Add and Delete items]
+
+If you read the previous section on tModel Key Generators, then you know all about UDDI keys. This is your one and only chance to get it right. Once your done, click "Save". Congrats! You've just made your first UDDI business!
+
+IMPORTANT: When working with UDDI entities, you cannot change the UDDI key after it has been created.
+
+The Business Editor/Creator web page, along with the other editor/creator pages, has a ton of other interesting things that you can do. Since there's way too much stuff to look at, we broke them up into logical sections.
+
+[[figure-Using the jUDDI GUI-createbiz2]]
+.Business Editor's Section.
+image::images/juddi-gui-create-business2.png[Business Editor's Section]
+
+In case you can't see the picture above:
+
+* General - Names and Descriptions
+* Discovery URLs - Usually a link to a web page
+* Contacts - Points of Contact, such as Sales, Tech Support, etc
+* Categories - These reference tModels and act as a way to categorize your business.
+* Identifiers - Can be used for Tax IDs, DUNS Number, or anything else that you can think of.
+* Services - This is the meat and potatoes of UDDI, advertising all the great services that your business provides.
+* Signatures - Digital Signatures prevent tampering
+* Operational Info - Who created it and when
+* Related Businesses - This is where people can find out if you have a business relationship with someone else. It's also called Publisher Assertions.
+
+TIP: Clicking on each tab will supply additional information.
+
+TIP: If a business, service, or tModel is signed, the juddi-gui will automatically attempt to validate the signature. You'll see a thumbs up or thumbs down icon to let you know.
+
+==== Create a Service
+
+Creating a new service is simple so long as you remember that a service must be attached to a business. There are a few ways to create a new business.
+
+The first option is to locate the business that you wish to add a service to via the Business Browser and then click the Plug button.
+
+[[figure-Using the jUDDI GUI-createservice1]]
+.Add a Service via Business Browser.
+image::images/juddi-gui-service-add1.png[Add a Service via Business Browser]
+
+The second option is to bring up the Business Editor for the business you want to add a service to, then click on the Services tab, then "Add a Service".
+
+[[figure-Using the jUDDI GUI-createservice2]]
+.Add a Service via Business Editor.
+image::images/juddi-gui-service-add2.png[Add a Service via Business Editor]
+
+TIP: Services require at least one name. Everything else is considered optional.
+
+==== Import from WSDL or WADL
+
+The jUDDI client provides programmatic access to convert a WSDL or WADL document into UDDI Service and tModel entries. The juddi-gui takes advantage of this and provides a simple to use interface to quickly and easily import your SOAP and REST services into UDDI.
+
+From the Create menu, select Register Services from WSDL or WADL.
+
+The process is pretty straight forward.
+
+1.Provide the location of the WSDL or WADL file. It must be web accessible from the server hosting juddi-gui.war. If it is password protected (such as Digest, Basic or NTLM) provide a password to access the WSDL or WADL. Your credentials will not be saved anywhere.
+1.The key domain. The imported UDDI service, binding, and tModels will all use this key partition/domain for key generation. The juddi-gui will populate this field with the domain of the URL entered in step 1. If you don't like, go ahead and change it. One will be automatically created for you.
+1.Pick a business to attach the imported data to.
+1.Review and Approve. The Preview button will do all of the processing except saving the content, so it is a good way to get a preview of what will happen. Save will do the processing and save it.
+
+[[figure-Using the jUDDI GUI-importwsdl]]
+.Importing a Service from WSDL or WADL.
+image::images/juddi-gui-import-wsdl.png[Importing a Service from WSDL or WADL]
+
+=== Custody Transfers
+
+Custody Transfers are used to give away ownership and edit permission for UDDI business and tModels. It's not used very often, but the workflow is simple.
+
+1.Two business representatives agree to transfer either a business(s) or tModel(s) from business A to business B.
+1.Business A creates a transfer token
+1.Business A gives the transfer token data to Business B's representative (perhaps via email?)
+1.Business B accepts the token and transfers the ownership over.
+
+All of these actions are processed at the Transfer Ownership page from the Home menu.
+
+[[figure-Using the jUDDI GUI-custodytransfer]]
+.Custody Transfer.
+image::images/juddi-gui-transfer.png[Custody Transfer]
+
+=== Publisher Assertions
+
+Publisher Assertions are how two different businesses can setup a UDDI Business Relationship. This essentially means that other users can see that this is a relationship between business A and B and that they can perform queries based on the relationship.
+
+[[figure-Using the jUDDI GUI-publisherassertion]]
+.Publisher Assertion.
+image::images/juddi-gui-publisherassertion.png[Publisher Assertion]
+
+
+=== Subscriptions
+
+Subscriptions in UDDI are used to easily detect when changes are made to a UDDI node.
+
+==== Create a new subscription
+
+To create a new subscription, you must first be logged in. Click on Home, then Create Subscription.
+
+Subscriptions can either be for a set of specific items or for search results.
+
+[[figure-Using the jUDDI GUI-createsub1]]
+.Create a Subscription, Specific Item or Search Results.
+image::images/juddi-gui-subscription1.png[Create a Subscription, Specific Item or Search Results]
+
+In our example, we've selected a set of specific items.
+
+[[figure-Using the jUDDI GUI-createsub2]]
+.Create a Subscription, Select Items.
+image::images/juddi-gui-subscription2.png[Create a Subscription, Select Items
+
+To add an item to the list, click on Add. The item chooser will appear. Check each item to add them to the list. To remove, select the item, then click remove.
+
+[[figure-Using the jUDDI GUI-createsub3]]
+.Create a Subscription, Add an item using the chooser.
+image::images/juddi-gui-subscription3.png[Create a Subscription, Add an item using the chooser]
+
+Specific items are added by entity keys.
+
+[[figure-Using the jUDDI GUI-createsub4]]
+.Create a Subscription, Item Added.
+image::images/juddi-gui-subscription4.png[Create a Subscription, Item added]
+
+Next is the delivery mechanism. The UDDI node can deliver the notifications to you if you have your own implementation of the UDDI Subscription Listener service. (The juddi-client contains this for you if you were looking to develop a solution). In addition, the UDDI node can email the results to you (in XML format).
+
+The other option is to periodically poll the UDDI server and get your subscription results (see the News Feed).
+
+Here, we've selected the, I'll pick them up, option.
+
+[[figure-Using the jUDDI GUI-createsub5]]
+.Create a Subscription, Delivery Mechanism.
+image::images/juddi-gui-subscription5.png[Create a Subscription, Delivery Mechanism]
+
+The final slider provides subscription options.
+* Expiration - a date where the subscription expires
+* Notification Interval - this is only used when the UDDI node sends the notifications to you via the Subscription Listener Service
+* Brief - If true, the UDDI node will only tell you which items have changed, not what the change was.
+
+[[figure-Using the jUDDI GUI-createsub6]]
+.Create a Subscription, Options.
+image::images/juddi-gui-subscription6.png[Create a Subscription, Options]
+
+==== View My Subscriptions
+
+To view, edit, and delete existing subscriptions, click on Home, then View Subscriptions.
+
+[[figure-Using the jUDDI GUI-viewsub]]
+.View Subscriptions.
+image::images/juddi-gui-subscription-view.png[View Subscriptions]
+
+==== View the News Feed
+
+The New Feed is a simple page designed to show you subscription results for the past 24 hrs. To view the news feed, click on Home, then News Feed.
+
+[[UsingDigitalSignatures]]
+=== Using Digital Signatures in juddi-gui
+
+The juddi-gui makes working with digital signatures simple and enables you do digitally sign and protect entities right from the web browser. It allows you to sign business, services and tModels.
+
+TIP: Digital signatures are performed using the jUDDI Digital Signature Applet which requires a Java plugin for your web browser, as well as a digital certificate (X509).
+
+TIP: You also need to have an X509 Certificate installed in either your Windows My/Current User Certificate Store or your MacOS Key Chain certificate store.
+
+==== Sign a Business, Service or tModel
+
+[[figure-Using the jUDDI GUI-sign1]]
+.Select an entity, then click Digitally Sign.
+image::images/juddi-gui-sign1.png[Select an entity, then click Digitally Sign]
+
+[[figure-Using the jUDDI GUI-sign2]]
+.Java Plugin Warnings.
+image::images/juddi-gui-sign2.png[Java Plugin Warnings]
+
+Select a certificate, then if you're ready to sign, click on "Digitally Sign". This will automatically generate the signature and save it in the UDDI server.
+
+[[figure-Using the jUDDI GUI-sign3]]
+.Select a Signing Certificate.
+image::images/juddi-gui-signerpanel1.png[Select a Signing Certificate]
+
+Click on Certificate Info will display the following panel. This is useful if you have a few certificates that are similarly named.
+
+[[figure-Using the jUDDI GUI-sign4]]
+.Certificate Details.
+image::images/juddi-gui-signerpanel3.png[Certificate Details]
+
+The settings tab gives you a number of options for advanced users. We recommend that you leave the defaults as is.
+
+[[figure-Using the jUDDI GUI-sign5]]
+.Signature Settings.
+image::images/juddi-gui-signerpanel2.png[Signature Settings]
+
+==== Verify a signed UDDI entity
+
+Once an entity is signed, the juddi-gui will always attempt to validate the signature and will notify you if its signed and whether or not its valid.
+
+In the following example, the business was signed.
+
+[[figure-Using the jUDDI GUI-validate]]
+.Valid Signed Entity.
+image::images/juddi-gui-signed-valid.png[Valid Signed Entity]
+
+IMPORTANT: UDDI entities are hierarchical. A signed business entities includes all of the data for its services and binding templates. Any change to a service or binding template will cause the business's signature to be invalid. TModels are not affected by this.
+
+In the following example, one of the services own by the business was changed. Note that the signature is now invalid due to the alteration.
+
+[[figure-Using the jUDDI GUI-invalid]]
+.Invalid Signed Entity.
+image::images/juddi-gui-signed-invalid.png[Invalid Signed Entity]
+
+
+=== Configuration
+
+The configuration page is usually restricted to system administrators. There are many fields that are displayed. Some of the are editable, others are not. In general, the following settings can be changed (the others are just for troubleshooting and informational purposes).
+
+Details on configuration is located in chapter, jUDDI Server Configuration.
+
+WARNING: Saving updates to the console configuration in _juddi-gui/WEB-INF/classes/META-INF/uddi.xml_ will only work if the juddi-gui is deployed as a folder.
+
+=== Language Codes
+
+The Language Code is a field supported by UDDI that is inherited from the errata for XML Schema, which references RFC 3066, which can be read here: http://www.ietf.org/rfc/rfc3066.txt/. In general, Language Codes are either 2 or 5 characters but can by up to 26 characters. Here's a few examples
+
+* en
+* en_US
+* es_US
+
+More can be found here: http://www.i18nguy.com/unicode/language-identifiers.html
+
+=== Switching Nodes
+
+The jUDDI GUI supports connectivity to multiple UDDI nodes. A UDDI Node is simple a collection of UDDI services that are all connected to the same data source. Another way to put it this, 'a UDDI server'. Each browser session to the jUDDI GUI has the ability to select the current Node connection. The current Node select is always saved as a cookie. To avoid any potential confusion, the currently selected Node is available both from the drop down Settings menu, and on the bottom of every page.
+
+To switch nodes, simply select the desired node from the Settings menu.
+
+IMPORTANT: When switching nodes, any unsaved work that you have will be lost. You will also be logged out of the old node if you were signed in.
+
+[[figure-Using the jUDDI GUI-noswitcher]]
+.Node Switcher.
+image::images/juddi-gui-nodeswitcher.png[Node Switcher]
+
+TIP: Administrators can define the default node via the Setting, Configuration page.
+
Added: juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientConfigurationGuide.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientConfigurationGuide.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientConfigurationGuide.asciidoc (added)
+++ juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientConfigurationGuide.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,171 @@
+jUDDI Client Configuration Guide
+--------------------------------
+
+Introduction
+~~~~~~~~~~~~
+The jUDDI Java and .NET clients use an XML configuration file that dictates settings and behaviors.
+This guide provides an overview of the settings. Both .NET and jUDDI use the same configuration file schema. This schema is located within the source tree and with the client distribution packages of jUDDI.
+
+Client Settings
+~~~~~~~~~~~~~~~
+The root XML node for the jUDDI client configuration file is always "uddi".
+----
+<!-- applies to Java clients only -->
+uddi/reloadDelay
+----
+
+Multiple clients can be defined in each configuration file.
+----
+uddi/client@name="someName"
+----
+
+Nodes
+~~~~~
+At least one node is required per client. A node represents a one logical UDDI server (or cluster of servers). Each UDDI node should host at least the inquiry service. A client using the jUDDI client package can be configured to access multiple nodes at the same time.
+----
+<!-- if isHomeJUDDI is true, then this node is loaded by default, when no node is specified in client code -->
+uddi/client/nodes[]/node@isHomeJUDDI=true/false
+<!-- the name of the node is referenced in client code -->
+uddi/client/nodes[]/node/name
+<!-- the description of the node -->
+uddi/client/nodes[]/node/description
+<!-- the properties section defines HTTP style credentials and a runtime tokenizer for URLs -->
+uddi/client/nodes[]/node/properties
+<!-- The transport represents the class name of the transport mechanism that the client will use to connect
+to the UDDI node. The most commonly used is org.apache.juddi.v3.client.transport.JAXWSTransport, however
+RMITransport, InVMTransport and JAXWSv2TranslationTransport are also defined -->
+uddi/client/nodes[]/node/proxyTransport
+
+<!-- endpoint URLs -->
+uddi/client/nodes[]/node/custodyTransferUrl
+uddi/client/nodes[]/node/inquiryUrl
+uddi/client/nodes[]/node/publishUrl
+uddi/client/nodes[]/node/securityUrl
+uddi/client/nodes[]/node/subscriptionUrl
+uddi/client/nodes[]/node/subscriptionListenerUrl
+<!-- note: this is for jUDDI v3.x servers only and is not part of the UDDI standard -->
+uddi/client/nodes[]/node/juddiApiUrl
+----
+
+==== Transport Options
+The Proxy Transport defines which mechanism is used for 'on the wire' transport of the UDDI XML messages. JAXWS Transport is the most commonly used and assumes SOAP messaging protocol over HTTP transport layer.
+
+RMI Transport using the Java Remote Method Invocation for transport. It's more commonly used for communicating within a J2EE container, but could be used in other cases. It's not required by the UDDI specification and is considered a jUDDI add on.
+
+InVM Transport is for hosting jUDDI services without a J2EE container.
+
+JAXWSv2TranslationTransport is a bridge for accessing UDDIv2 web services using the UDDIv3 data structures and APIs. Only the Inquiry and Publish services are required and they must point to SOAP/HTTP endpoints for a UDDI v2 node.
+
+Clerks
+~~~~~~
+Clerks are responsible for mapping stored user credentials to a Node and for automated registration.
+----
+<!-- if true, the contents of the child node xregister are registered when the UDDIClient object is created, using the credential and node reference.-->
+uddi/client/clerks/registerOnStartup=true/false
+----
+
+Clerk
+~~~~~
+Clerks store credentials and map to a specific node.
+----
+<!-- the name is a reference to the Node that these credentials apply to-->
+uddi/client/clerks[]/clerk@node - This is reference to uddi/client/node/name, it must exist
+uddi/client/clerks[]/clerk@name - This is a unique identifier of the clerk
+uddi/client/clerks[]/clerk@publisher - This is the username
+uddi/client/clerks[]/clerk@password
+uddi/client/clerks[]/clerk@isPasswordEncrypted=true/false
+uddi/client/clerks[]/clerk@cryptoProvider=(see Crypto providers)
+----
+
+Credentials can be encrypted using the included batch/bash scripts and then appended to the configuration. Example with encryption:
+----
+<clerk name="default" node="default" publisher="root" password="(cipher text removed)"
+ isPasswordEncrypted="true" cryptoProvider="org.apache.juddi.v3.client.cryptor.AES128Cryptor" />
+----
+
+Clerks also have settings for the automated cross registration of Businesses and Services on start up.
+----
+uddi/client/clerks[]/xregister/service@bindingKey
+uddi/client/clerks[]/xregister/service@fromClerk
+uddi/client/clerks[]/xregister/service@toClerk
+----
+
+Digital Signatures
+~~~~~~~~~~~~~~~~~~
+The Signature section contains settings that map to the Digital Signature Utility that makes working with UDDI digital signatures simple. The section contains all of the settings for both signing and validating signatures.
+
+----
+uddi/client/signature/signingKeyStorePath
+uddi/client/signature/signingKeyStoreFilePassword
+uddi/client/signature/signingKeyStoreFilePassword@isPasswordEncrypted
+uddi/client/signature/signingKeyStoreFilePassword@cryptoProvider
+uddi/client/signature/signingKeyPassword
+uddi/client/signature/signingKeyPassword@isPasswordEncrypted
+uddi/client/signature/signingKeyPassword@cryptoProvider
+uddi/client/signature/signingKeyAlias
+uddi/client/signature/canonicalizationMethod
+uddi/client/signature/signatureMethod=(default RSA_SHA1)
+uddi/client/signature/XML_DIGSIG_NS=(default http://www.w3.org/2000/09/xmldsig#)
+uddi/client/signature/trustStorePath
+uddi/client/signature/trustStoreType
+uddi/client/signature/trustStorePassword
+uddi/client/signature/trustStorePassword@isPasswordEncrypted
+uddi/client/signature/trustStorePassword@cryptoProvider
+<!-- checks signing certificates for timestamp validity -->
+uddi/client/signature/checkTimestamps
+<!-- checks signing certificates for trust worthiness -->
+uddi/client/signature/checkTrust
+<!-- checks signing certificates for revocation -->
+uddi/client/signature/checkRevocationCRL
+uddi/client/signature/keyInfoInclusionSubjectDN
+uddi/client/signature/keyInfoInclusionSerial
+uddi/client/signature/keyInfoInclusionBase64PublicKey
+<!-- default is http://www.w3.org/2000/09/xmldsig#sha1 -->
+uddi/client/signature/digestMethod
+----
+
+Subscription Callbacks
+~~~~~~~~~~~~~~~~~~~~~~
+The subscriptionCallbacks section defines settings uses by the subscription callback API. This enables developers to create capabilities that need to be notified immediately when something in UDDI changes through the use of subscriptions.
+----
+uddi/client/subscriptionCallbacks/keyDomain
+uddi/client/subscriptionCallbacks/listenUrl this is the URL that is used for callbacks, should be externally resolvable
+uddi/client/subscriptionCallbacks/autoRegisterBindingTemplate=true/false
+uddi/client/subscriptionCallbacks/autoRegisterBusinessServiceKey=(key) append callback endpoint to this service
+uddi/client/subscriptionCallbacks/signatureBehavior=(AbortIfSigned,Sign,DoNothing,SignOnlyIfParentIsntSigned), default DoNothing. Applies when auto registering the endpoint to a business or service that is already signed.
+----
+
+XtoWsdl
+~~~~~~~
+XtoWsdl represents configuration parameters for importing WSDL or WADL files. Currently, the only setting is for ignoring SSL errors when fetching remote WSDL or WADL files.
+----
+uddi/client/XtoWsdl/IgnoreSSLErrors=true or false
+----
+
+Embedded jUDDI server
+~~~~~~~~~~~~~~~~~~~~~
+jUDDI has the ability to run in embedded mode. This means that the jUDDI services can operate without a web servlet container, such as Tomcat or JBoss. Typically, this is something that application developers would use for more advanced scenarios and for operation without network connectivity.
+
+Requirements
+^^^^^^^^^^^^
+A database server, if one is not available, the embedded Derby engine can be used.
+
+Changes in configuration compared to non-embedded
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+* META-INF/embedded-uddi.xml needs to contain the connection settings for InVmTransport.
+....
+ <!-- In VM Transport Settings -->
+ <proxyTransport>org.apache.juddi.v3.client.transport.InVMTransport</proxyTransport>
+ <custodyTransferUrl>org.apache.juddi.api.impl.UDDICustodyTransferImpl</custodyTransferUrl>
+ <inquiryUrl>org.apache.juddi.api.impl.UDDIInquiryImpl</inquiryUrl>
+ <publishUrl>org.apache.juddi.api.impl.UDDIPublicationImpl</publishUrl>
+ <securityUrl>org.apache.juddi.api.impl.UDDISecurityImpl</securityUrl>
+ <subscriptionUrl>org.apache.juddi.api.impl.UDDISubscriptionImpl</subscriptionUrl>
+ <subscriptionListenerUrl>org.apache.juddi.api.impl.UDDISubscriptionListenerImpl</subscriptionListenerUrl>
+ <juddiApiUrl>org.apache.juddi.api.impl.JUDDIApiImpl</juddiApiUrl>
+....
+* The serverside config file juddiv3.xml needs to be added to the classpath.
+* A META-INF/persistence.xml needs to be added.
+* Add the juddi-core (UDDI server) and derby (Embedded Database) dependencies to the pom. Use the juddi-core-openjpa jar for OpenJPA.
+
+See also the hello-world-embedded example.
Added: juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientforNET.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientforNET.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientforNET.asciidoc (added)
+++ juddi/docs/trunk/ClientGuide/en-US/ClientGuidejUDDIClientforNET.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,81 @@
+== jUDDI Client for NET
+
+Since 3.2, the majority of the functions in the jUDDI Client for Java have been ported to .NET. This guide will show you how to use it and integrate it with your own .NET based applications.
+
+=== Procedure
+. Add a reference to jUDDI-Client.NET.dll
+. Add a reference to System.Web.Services
+. Add a reference to System.ServiceModel
+. Add a reference to System.Xml
+. Add a reference to System.Runtime.Serialization
+. Add a reference to System.Configuration
+. Add a reference to System.Security
+. Add a copy of the sample uddi.xml file. Modify it to meet your environment and operational needs.
+. Note, many of the settings are identical to the Java jUDDI-client. The APIs are also nearly identical, so example code should be easily portable from one language to another.
+
+Sample Code
+
+----
+
+/*
+ * Copyright 2001-2013 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+using org.apache.juddi.v3.client;
+using org.apache.juddi.v3.client.config;
+using org.apache.juddi.v3.client.transport;
+using org.uddi.apiv3;
+using System;
+using System.Collections.Generic;
+using System.Text;
+
+
+namespace juddi_client.net_sample
+{
+ class Program
+ {
+ static void Main(string[] args)
+ {
+ UDDIClient clerkManager = new UDDIClient("uddi.xml");
+ UDDIClientContainer.addClient(clerkManager);
+ Transport transport = clerkManager.getTransport("default");
+
+ org.uddi.apiv3.UDDI_Security_SoapBinding security = transport.getUDDISecurityService();
+ org.uddi.apiv3.UDDI_Inquiry_SoapBinding inquiry = transport.getUDDIInquiryService();
+
+ UDDIClerk clerk = clerkManager.getClerk("default");
+
+
+ find_business fb = new find_business();
+ fb.authInfo = clerk.getAuthToken(security.Url);
+ fb.findQualifiers = new string[] { UDDIConstants.APPROXIMATE_MATCH };
+ fb.name = new name[1];
+ fb.name[0] = new name(UDDIConstants.WILDCARD, "en");
+ businessList bl = inquiry.find_business(fb);
+ for (int i = 0; i < bl.businessInfos.Length; i++)
+ {
+ Console.WriteLine(bl.businessInfos[i].name[0].Value);
+ }
+ Console.Read();
+
+ }
+ }
+}
+
+----
+
+The sample code above should print out a list of all businesses currently registered in the registry. If credentials are stored in the uddi.xml file and are encrypted, they will be decrypted automatically for you.
+
+Within the jUDDI Source Tree, there are many different examples of how to use the jUDDI Client for .NET. They are available here: http://svn.apache.org/repos/asf/juddi/trunk/juddi-client.net/juddi-client.net-sample/
Added: juddi/docs/trunk/ClientGuide/en-US/Guardfile
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/Guardfile?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/Guardfile (added)
+++ juddi/docs/trunk/ClientGuide/en-US/Guardfile Mon Feb 3 19:34:34 2014
@@ -0,0 +1,13 @@
+require 'asciidoctor'
+require 'erb'
+require 'fileutils'
+
+FileUtils.mkdir_p('build')
+FileUtils.cp_r('../../images','build')
+FileUtils.cp_r('asciidoctor.css','build')
+
+guard 'shell' do
+ watch (/^.*\.asciidoc$/) {|m|
+ Asciidoctor.render_file(m[0], :to_dir => "build" )
+ }
+end
Propchange: juddi/docs/trunk/ClientGuide/en-US/Guardfile
------------------------------------------------------------------------------
svn:executable = *
Added: juddi/docs/trunk/ClientGuide/en-US/_Sidebar.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/_Sidebar.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/_Sidebar.asciidoc (added)
+++ juddi/docs/trunk/ClientGuide/en-US/_Sidebar.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,15 @@
+.Contents
+****
+link:ClientGuideSimplePublishingUsingthejUDDIAPI[Simple Publishing] +
+link:ClientGuidejUDDIClientConfigurationGuide[Configuration] +
+link:ClientGuideKeyFormatTemplates[Key Format] +
+link:ClientGuideUsingthejUDDIGUI[Using the jUDDI GUI] +
+link:ClientGuideMappingWADLandWSDLtoUDDI[WSDL to UDDI] +
+link:ClientGuideUsingUDDIAnnotationstoAutomateRegistration[UDDI Annotations] +
+link:ClientGuideUDDIv2Services[UDDI v2] +
+link:ClientGuideUDDIMigrationTool[UDDI Migration Tool] +
+link:ClientGuideUsingjUDDIRestServices[REST Services] +
+link:ClientGuidejUDDIClientforNET[.NET Client] +
+link:ClientGuideTCKRunner[TCK]
+****
+link:GuideReadme[Readme] +
Added: juddi/docs/trunk/ClientGuide/en-US/asciidoctor.css
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/en-US/asciidoctor.css?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/en-US/asciidoctor.css (added)
+++ juddi/docs/trunk/ClientGuide/en-US/asciidoctor.css Mon Feb 3 19:34:34 2014
@@ -0,0 +1,80 @@
+@import url("documentation.css");
+@import url("docnav.css");
+@import url("reports.css");
+@import url("extensions.css");
+@import url("codehighlight.css");
+
+body {
+ background-image:url(../images/community/bkg_gradient.gif);
+ background-repeat:repeat-x;
+ margin:0 auto;
+ font-family:'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ padding:0em 2em;
+ color:#333;
+ line-height:150%;
+ text-align:justify;
+}
+
+/* Links */
+
+a:link {color:#0066cc;}
+
+a:visited {color:#6699cc;}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+/* Headings */
+
+h1, h2, h3, h4, h5, h6 {
+ color:#4a5d75;
+ line-height:130%;
+ margin-top:0em;
+ font-family:'Lucida Grande', Geneva, Verdana, Arial, sans-serif;
+ background-color:transparent;
+}
+
+h1 {
+ background-image:url(../images/community/title_hdr.png);
+ background-repeat:no-repeat;
+ border-top:1px dotted #CCCCCC;
+ line-height:1.2em;
+ color:#182737;
+ font-size:2em;
+ padding:1.5em;
+}
+
+h2 {font-size:1.6em;}
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+/* Element rules */
+
+hr {
+ border-collapse:collapse;
+ border-style:none;
+ border-top:1px dotted #ccc;
+ width:100% !important;
+}
+
+sup {color:#999;}
Added: juddi/docs/trunk/ClientGuide/pom.xml
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/ClientGuide/pom.xml?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/ClientGuide/pom.xml (added)
+++ juddi/docs/trunk/ClientGuide/pom.xml Mon Feb 3 19:34:34 2014
@@ -0,0 +1,194 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+ <modelVersion>4.0.0</modelVersion>
+ <parent>
+ <groupId>org.apache.juddi.juddi-docs</groupId>
+ <artifactId>juddi-guide-parent</artifactId>
+ <version>3.2.0-SNAPSHOT</version>
+ </parent>
+ <artifactId>juddi-client-guide</artifactId>
+ <packaging>jdocbook</packaging>
+ <name>jUDDI Client Guide</name>
+ <description>The documentation for the Apache jUDDI Client and the UDDI TCK</description>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.asciidoctor</groupId>
+ <artifactId>asciidoctor-maven-plugin</artifactId>
+ <version>0.1.4</version>
+ <executions>
+ <execution>
+ <id>output-docbook</id>
+ <phase>generate-resources</phase>
+ <goals>
+ <goal>process-asciidoc</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <sourceDirectory>en-US</sourceDirectory>
+ <outputDirectory>target/docbook/en-US</outputDirectory>
+ <imagesDir>.</imagesDir>
+ <backend>docbook5</backend>
+ <doctype>book</doctype>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <version>2.3.8</version>
+ <extensions>true</extensions>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss.pressgang</groupId>
+ <artifactId>pressgang-xslt-ns</artifactId>
+ <version>3.0.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss.pressgang</groupId>
+ <artifactId>pressgang-jdocbook-style</artifactId>
+ <type>jdocbook-style</type>
+ <version>3.0.0</version>
+ </dependency>
+ </dependencies>
+ <configuration>
+ <sourceDocumentName>ClientGuide.xml</sourceDocumentName>
+ <sourceDirectory>target/docbook/</sourceDirectory>
+ <imageResource>
+ <directory>${project.parent.basedir}/</directory>
+ <includes>
+ <include>images/*</include>
+ <include>images/community/*</include>
+ </includes>
+ </imageResource>
+
+ <formats>
+ <format>
+ <formatName>html</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/xhtml.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+ <format>
+ <formatName>html_single</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/xhtml-single.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+
+ <format>
+ <formatName>pdf</formatName>
+ <stylesheetResource>classpath:/xslt/org/jboss/pressgang/pdf.xsl</stylesheetResource>
+ <finalName>jUDDI_Guide.pdf</finalName>
+ </format>
+ </formats>
+ <options>
+ <xincludeSupported>true</xincludeSupported>
+ <xmlTransformerType>saxon</xmlTransformerType>
+ <docbookVersion>1.72.0</docbookVersion>
+ <transformerParameters>
+ <property>
+ <name>javax.xml.parsers.DocumentBuilderFactory</name>
+ <value>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</value>
+ </property>
+ <property>
+ <name>javax.xml.parsers.SAXParserFactory</name>
+ <value>org.apache.xerces.jaxp.SAXParserFactoryImpl</value>
+ </property>
+ </transformerParameters>
+ </options>
+ </configuration>
+ </plugin>
+ </plugins>
+ <pluginManagement>
+ <plugins>
+ <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the
+ Maven build itself. -->
+ <plugin>
+ <groupId>org.eclipse.m2e</groupId>
+ <artifactId>lifecycle-mapping</artifactId>
+ <version>1.0.0</version>
+ <configuration>
+ <lifecycleMappingMetadata>
+ <pluginExecutions>
+ <pluginExecution>
+ <pluginExecutionFilter>
+ <groupId>org.asciidoctor</groupId>
+ <artifactId>asciidoctor-maven-plugin</artifactId>
+ <versionRange>[0.1.1,)</versionRange>
+ <goals>
+ <goal>process-asciidoc</goal>
+ </goals>
+ </pluginExecutionFilter>
+ <action>
+ <ignore />
+ </action>
+ </pluginExecution>
+ <pluginExecution>
+ <pluginExecutionFilter>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <versionRange>[2.3.8,)</versionRange>
+ <goals>
+ <goal>generate</goal>
+ <goal>resources</goal>
+ </goals>
+ </pluginExecutionFilter>
+ <action>
+ <ignore />
+ </action>
+ </pluginExecution>
+ </pluginExecutions>
+ </lifecycleMappingMetadata>
+ </configuration>
+ </plugin>
+ </plugins>
+ </pluginManagement>
+ </build>
+ <profiles>
+ <!-- START SNIPPET: release-profile -->
+ <!-- this is borrowed from an nov 2009 apache-7 pom release attempt-->
+ <profile>
+ <id>apache-release</id>
+ <build>
+ <plugins>
+ <!-- Create a source-release artifact that contains the fully buildable
+ project directory source structure. This is the artifact which is
+ the official subject of any release vote. -->
+ <plugin>
+ <artifactId>maven-assembly-plugin</artifactId>
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.apache.resources</groupId>
+ <artifactId>apache-source-release-assembly-descriptor</artifactId>
+ <version>1.0.1</version>
+ </dependency>
+ <dependency>
+ <!-- NOTE: The fix for PLXUTILS-120 is crucial for the new assembly descriptor -->
+ <groupId>org.codehaus.plexus</groupId>
+ <artifactId>plexus-utils</artifactId>
+ <version>2.0.1</version>
+ </dependency>
+ </dependencies>
+ <executions>
+ <execution>
+ <id>source-release-assembly</id>
+ <phase>package</phase>
+ <goals>
+ <goal>single</goal>
+ </goals>
+ <configuration>
+ <runOnlyAtExecutionRoot>true</runOnlyAtExecutionRoot>
+ <descriptorRefs>
+ <descriptorRef>${sourceReleaseAssemblyDescriptor}</descriptorRef>
+ </descriptorRefs>
+ <tarLongFileFormat>gnu</tarLongFileFormat>
+ </configuration>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
+ </build>
+ </profile>
+ <!-- END SNIPPET: release-profile -->
+ </profiles>
+</project>
Added: juddi/docs/trunk/Guide/en-US/Guardfile
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/Guardfile?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/Guardfile (added)
+++ juddi/docs/trunk/Guide/en-US/Guardfile Mon Feb 3 19:34:34 2014
@@ -0,0 +1,14 @@
+require 'asciidoctor'
+require 'erb'
+require 'fileutils'
+
+FileUtils.mkdir_p('build')
+FileUtils.cp_r('../../images','build')
+FileUtils.cp_r('asciidoctor.css','build')
+
+guard 'shell' do
+ watch (/^.*\.asciidoc$/) {|m|
+ Asciidoctor.render_file(m[0], :to_dir => "build" )
+ FileUtils.cp_r('../../images','build')
+ }
+end
Propchange: juddi/docs/trunk/Guide/en-US/Guardfile
------------------------------------------------------------------------------
svn:executable = *
Added: juddi/docs/trunk/Guide/en-US/Guide-docinfo.xml
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/Guide-docinfo.xml?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/Guide-docinfo.xml (added)
+++ juddi/docs/trunk/Guide/en-US/Guide-docinfo.xml Mon Feb 3 19:34:34 2014
@@ -0,0 +1,56 @@
+ <authorgroup>
+
+Â <author>
+Â Â <firstname>Kurt</firstname>
+Â Â <surname>Stam</surname>
+ <othername role='mi'>T</othername>
+ <affiliation>
+ <shortaffil>RedHat</shortaffil>
+ <jobtitle>Enterprise Integration Magician (EIM)</jobtitle>
+ <orgname>Red Hat, Inc.</orgname>
+ <orgdiv><ulink url="http://www.jboss.org/overlord">SOA Governance</ulink></orgdiv>
+ <authorblurb>
+ <para>
+ Open Source, written by domain experts.
+ </para>
+ </authorblurb>
+
+ </affiliation>
+
+Â </author>
+
+ <author>
+ Â Â <firstname>Alex</firstname>
+ Â Â <surname>O'Ree</surname>
+ <affiliation>
+ <shortaffil>Apache Software Foundation (ASF)</shortaffil>
+ <orgname>Apache Software Foundation (ASF), http://juddi.apache.org</orgname>
+ </affiliation>
+ Â </author>
+
+ </authorgroup>
+
+ <copyright>
+ Â <year>2003-2014</year>
+ <holder>The Apache Software Foundation</holder>
+ </copyright>
+
+ <legalnotice>
+ <simpara>
+Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+</simpara>
+<simpara>
+ You may obtain a copy of the License at
+
+ <ulink url="http://www.apache.org/licenses/LICENSE-2.0">http://www.apache.org/licenses/LICENSE-2.0</ulink>
+</simpara>
+<simpara>
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+ </simpara>
+</legalnotice>
+
Added: juddi/docs/trunk/Guide/en-US/Guide.asciidoc
URL: http://svn.apache.org/viewvc/juddi/docs/trunk/Guide/en-US/Guide.asciidoc?rev=1564021&view=auto
==============================================================================
--- juddi/docs/trunk/Guide/en-US/Guide.asciidoc (added)
+++ juddi/docs/trunk/Guide/en-US/Guide.asciidoc Mon Feb 3 19:34:34 2014
@@ -0,0 +1,105 @@
+Apache jUDDI Guide
+==================
+:doctype: book
+:backend: docbook5
+:docinfo:
+
+[dedication]
+Dedication
+----------
+We'd like to dedicate this guide to Steve Viens and Andy Cutright who started this project back in 2003.
+
+[preface]
+Preface
+-------
+The jUDDI project maintains a UDDIv3 registry that can be deployed to most modern JEE application servers. The jUDDI project is part of the Apache Software Foundation and encourages participation. It is easy to participate and if you discover a simple typo or would like to contribute to this guide in general please read the README page (add link).
+
+include::GuideUDDIRegistryIntroduction.asciidoc[]
+
+include::GuideGettingStarted.asciidoc[]
+
+include::GuideArchitecture.asciidoc[]
+
+include::GuideAdministration.asciidoc[]
+
+include::GuideConfigurationServer.asciidoc[]
+
+include::GuideRootSeedData.asciidoc[]
+
+include::GuideHowToDeployjUDDITo.asciidoc[]
+
+include::GuideExtendingUDDI.asciidoc[]
+
+include::GuideUsingDigitalSignaturesinUDDI.asciidoc[]
+
+include::GuideTroubleshootingjUDDI.asciidoc[]
+
+include::GuideContributingtojUDDI.asciidoc[]
+
+
+:numbered!:
+
+////
+/* commenting out till we need it */
+[appendix]
+Example Appendix
+----------------
+One or more optional appendixes go here at section level 1.
+
+Appendix Sub-section
+~~~~~~~~~~~~~~~~~~~
+Sub-section body.
+////
+
+[bibliography]
+Bibliography
+------------
+
+[bibliography]
+.Books
+- [[[graham-Davis-et-all]]] Steve Graham, Doug Davis et all.
+'Building Web Services with Java - Making sense of XML, SOAP, WSDL, and UDDI'. Second Edition. Sams Publishing. 2005.
+ISBN 0-672-32641-8.
+- [[[stam-oree]]] Kurt Stam, Alex O'Ree et all.
+'jUDDI Client and GUI Guide'. 2014.
+
+[bibliography]
+.Articles
+- [[[uddi-v3]]] OASIS. 'https://www.oasis-open.org/standards#uddiv3.0.2'. 2003.
+
+[bibliography]
+.WebSites
+- [[[uddi-xml-org]]] UDDI XML.org Editorial Board. 'http://uddi.xml.org/'. 2014.
+- [[[uddi-oasis-open-org]]] OASIS. 'https://www.oasis-open.org/standards#uddiv3.0.2'. 2003.
+
+
+////
+/* commenting out till we need it */
+[glossary]
+Example Glossary
+----------------
+Glossaries are optional. Glossaries entries are an example of a style
+of AsciiDoc labeled lists.
+
+[glossary]
+A glossary term::
+The corresponding (indented) definition.
+
+A second glossary term::
+The corresponding (indented) definition.
+
+
+[colophon]
+Example Colophon
+----------------
+Text at the end of a book describing facts about its production.
+
+////
+
+[index]
+Index
+-----
+////////////////////////////////////////////////////////////////
+The index is normally left completely empty, it's contents being
+generated automatically by the DocBook toolchain.
+////////////////////////////////////////////////////////////////
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@juddi.apache.org
For additional commands, e-mail: commits-help@juddi.apache.org