Specifications OSR11gR1ProductDocumentation

• UDDI Version 2 Specification [http:www.oasis-open.orgcommitteesuddi-specdoctcspecs.htmuddiv2] • UDDI Version 3 Specification [http:www.oasis-open.orgcommitteesuddi-specdoctcspecs.htmuddiv3] • Technical Note Using WSDL in a UDDI Registry, Version 2.0 [http:www.oasis-open.orgcommitteesuddi-spec doctnuddi-spec-tc-tn-wsdl-v2.htm]

5. Document Conventions

This section describes conventions used in this document. The syntax of operating system commands. We use square brackets [ ] to indicate optional parameters, a vertical bar | to indicate a choice of parameters, ... to indicate that the parameter is repeatable and {} to indicate that at least one repeatable parameter must be included. For example: Enter this command to start the UserStore tool: UserStoreTool {[-t target_server ] | [--file userstore_file ]...} [option...] Command syntax Operating system commands and other user input that you can type on the command line and press Enter to invoke. These may be contained within text, as in this example: The command java -jar server.jar does not work on some encodings. If you have any problems starting the installer, try running java -classpath server.jar Install --installation_option instead. The command line may be separated, in which case it has a screen background: java -jar server.jar --help Command instances Filenames, directory names, paths and package names. For example: Run the install.bat or install.sh script from the bin directory of the new distribution. Filename XML element and attribute names. For example: use ref=customSerialization XML tags Program source code. For example: package examples.helloWorld; public interface HelloWorldProxy { String hello String message; } Code block A combination of keystrokes. Press the indicated keys simultaneously. For example: Press Ctrl-Alt-Del to reboot your computer. Key -Key A label, word or phrase in a GUI window, often clickable. For example: To edit a servers attributes, click on the servers link in the Security Domain Tree or click on Detail in the servers row in the Managed Servers form. GUI buttons have a special icon, for example: Click on the Save Configs button to save your changes after editing any Domain or Server properties. GUI elements For example: Select Property-Add property A menu selection Page 7

5. Document Conventions

We use the following formatting elements to draw your attention to certain pieces of information: Note A Note indicates information that emphasizes or supplements points within the main text. Typically, a note provides information that may apply only in specific situations. Tip A Tip provides a helpful hint concerning procedures described in the text. It may suggest alternative methods or provide useful information about the capabilities of the product. Important An Important note provides critical information for the completion of a task. Do not disregard an Important note. Caution A Caution describes a situation where failure to take or avoid a specified action could result in a loss of data.

6. Legal

6.1. Third Party Licenses

6.1.1. The Apache XML Security License, Version 1.1

The Apache Software License, Version 1.1 Copyright c 1999 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation andor other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation http:www.apache.org. Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names WebSig and Apache Software Foundation must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apacheapache.org. 5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION HOWEVER Page 8

6.1.1. The Apache XML Security License, Version 1.1