diff options
| author | syeshin | 2005-09-04 15:36:34 +0000 |
|---|---|---|
| committer | syeshin | 2005-09-04 15:36:34 +0000 |
| commit | a535c86f86997cf5844af3b92757a0812317de4e (patch) | |
| tree | b161613df50867d1345e4133b078f7e18a3f428f /docs | |
| parent | 5905169c233e84200fee86d620318bb4deb4a14b (diff) | |
| download | webtools.webservices-a535c86f86997cf5844af3b92757a0812317de4e.tar.gz webtools.webservices-a535c86f86997cf5844af3b92757a0812317de4e.tar.xz webtools.webservices-a535c86f86997cf5844af3b92757a0812317de4e.zip | |
adding j2ee and web services plugins
Diffstat (limited to 'docs')
82 files changed, 5385 insertions, 0 deletions
diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html new file mode 100644 index 000000000..9d6a3344b --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html @@ -0,0 +1,93 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Creating Web services with the Apache Axis run-time environment" /> +<meta name="abstract" content="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort." /> +<meta name="description" content="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/twsbeana.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tsklwsdla.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tsampappa.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="axisoverview" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating Web services with the Apache Axis run-time environment</title> +</head> +<body id="axisoverview"><a name="axisoverview"><!-- --></a> + +<h1 class="topictitle1">Creating Web services with the Apache Axis run-time environment</h1> +<div><p>This run-time environment is for users who prefer to develop for +the open Apache Axis platform. It is for non-production use only. Axis is +the third generation of the Apache SOAP implementation. It evolved from +Apache SOAP (which began at IBM<sup>®</sup> as SOAP4J) to make the SOAP engine more flexible, +configurable, and able to handle both SOAP and the upcoming XML Protocol specification +from the W3C open-source effort.</p> +<div class="section"><h4 class="sectiontitle">Overview</h4><p>Axis is based on JSR 101 Java™ APIs +for XML based RPC (also known as JAX-RPC). JSR 101 provides a single +interface to any XML-based RPC mechanism, including SOAP.</p> +<p>Web services +application server uses Axis within a servlet to process the incoming message, +extract information from the message headers, and payloads, as well as conforming +to the particular RPC semantics. </p> +<p>The level of Axis currently supported +by Rational Developer products is 1.0. For more information on Axis, +refer to <a href="http://xml.apache.org/axis" target="_blank">http://xml.apache.org/axis</a>. +The User's Guide available on this site provides more in-depth information +about using Web services with Apache Axis. The Reading Guide lists several +documents to further your understanding of Axis.</p> +<div class="note"><span class="notetitle">Note:</span> The support for +Axis in Rational Developer products is limited to validation that the application +is invoking the Axis emitters correctly. Support for other Axis issues should +be directed to <a href="http://ws.apache.org/axis" target="_blank">http://ws.apache.org/axis</a></div> +</div> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../tasks/twsbeana.html">Creating a Web service from a Java bean using the Apache Axis run-time environment</a></strong><br /> +The Web Service wizard assists you in creating a new Web service, +configuring it for deployment, and deploying the Web service to a server. +Once your Web service is deployed, the wizard assists you in generating the +client proxy and sample application to test the Web service. When you have +completed testing, you can publish your Web service to a UDDI Business Registry +using the Export wizard.</li> +<li class="ulchildlink"><strong><a href="../tasks/tsklwsdla.html">Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment</a></strong><br /> +The Web service wizard assists you in creating a skeleton bean +from an existing WSDL document. The skeleton bean contains a set of methods +that correspond to the operations described in the WSDL document. When the +bean is created, each method has a trivial implementation that you replace +by editing the bean.</li> +<li class="ulchildlink"><strong><a href="../tasks/tsampappa.html">Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment</a></strong><br /> +The Web Service Client wizard assists you in generating a Java bean +proxy and a sample application. The sample Web application demonstrates how +to code a proxy file.</li> +</ul> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html">JAX-RPC</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/ibmdita.css b/docs/org.eclipse.jst.ws.axis.ui.doc.user/ibmdita.css new file mode 100644 index 000000000..e20903960 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/ibmdita.css @@ -0,0 +1,219 @@ +.unresolved { background-color: skyblue; } +.noTemplate { background-color: yellow; } + +.sidebar {background: silver } +.toc {font-size: small; } + +.base { background-color: #ffffff; } +.breadcrumb { font-size : smaller;} +.prereq { margin-left : 20px;} +.hierarchy { display: block; border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; border-color : Silver;} + +.nested0 { margin-top : 1em;} +.nested1 { } +.nested2 { } + +.p {margin-top: 1em} + +.tableborder { margin-top: 1em; margin-bottom: 1em } +.tablenoborder { margin-top: 1em; margin-bottom: 1em } +caption { text-align: left; font-style: italic } +.simpletableborder { margin-top: 1em; margin-bottom: 1em } +.simpletablenoborder { margin-top: 1em; margin-bottom: 1em } +.choicetableborder { margin-top: 1em; margin-bottom: 1em } +.choicetablenoborder { margin-top: 1em; margin-bottom: 1em } + +.figcap { font-style: italic } +.figdesc { font-style: normal } + +.fignone {margin-top: 1em} +.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.figbottom { border-bottom : 2px solid; border-color : Silver;} +.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.synnone {margin-top: 1em} +.synborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.synsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.syntop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.synbottom { border-bottom : 2px solid; border-color : Silver;} +.syntopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.skip { margin-top: 1em } +.skipspace { margin-top: 1em; margin-bottom: 1em } +.ullinks { list-style-type: none } +.ulchildlink { margin-top: 1em; margin-bottom: 1em } +.olchildlink { margin-top: 1em; margin-bottom: 1em } +.linklist { margin-bottom: 1em } +.linklistwithchild { margin-left: 1.5em; margin-bottom: 1em } +.sublinklist { margin-left: 1.5em; margin-bottom: 1em } +.relconcepts { margin-top: 1em; margin-bottom: 1em } +.reltasks { margin-top: 1em; margin-bottom: 1em } +.relref { margin-top: 1em; margin-bottom: 1em } +.relinfo { margin-top: 1em; margin-bottom: 1em } +div.breadcrumb {margin-bottom: 1em } + +.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; } +.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; } +.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; } +.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; } +.topictitle5 { font-size: 1.17em; font-weight: bold; } +.topictitle6 { font-size: 1.17em; font-style: italic; } +.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;} +.section { margin-top: 1em; margin-bottom: 1em } +.example { margin-top: 1em; margin-bottom: 1em } + +.note { margin-top: 1em; margin-bottom : 1em;} +.notetitle { font-weight: bold } +.notelisttitle { font-weight: bold } +.tip { margin-top: 1em; margin-bottom : 1em;} +.tiptitle { font-weight: bold } +.fastpath { margin-top: 1em; margin-bottom : 1em;} +.fastpathtitle { font-weight: bold } +.important { margin-top: 1em; margin-bottom : 1em;} +.importanttitle { font-weight: bold } +.remember { margin-top: 1em; margin-bottom : 1em;} +.remembertitle { font-weight: bold } +.restriction { margin-top: 1em; margin-bottom : 1em;} +.restrictiontitle { font-weight: bold } +.attention { margin-top: 1em; margin-bottom : 1em;} +.attentiontitle { font-weight: bold } +.dangertitle { margin-top: 1em; font-weight: bold } +.danger { padding: 5px 5px 5px 5px; border: solid; border-width: thin; font-weight: bold; margin-top: 2px; margin-bottom : 1em; } +.cautiontitle { margin-top: 1em; font-weight: bold } +.caution { font-weight: bold; margin-bottom : 1em; } + +ul.simple { list-style-type: none } + +.firstcol { font-weight : bold;} + +.bold { font-weight: bold; } +.boldItalic { font-weight: bold; font-style: italic; } +.italic { font-style: italic; } +.underlined { text-decoration: underline; } +.uicontrol { font-weight: bold; } +.parmname { font-weight: bold; } +.defparmname { font-weight: bold; text-decoration: underline; } +.kwd { font-weight: bold; } +.defkwd { font-weight: bold; text-decoration: underline; } +.var { font-style : italic;} +.shortcut { text-decoration: underline; } + +.ptocH1 {font-size: x-small; } +.ptocH2 {font-size: x-small; } + +.smallCaps { text-transform: uppercase; font-size: smaller; } +.stitle { font-style: italic; text-decoration: underline; } +.nte {} + +.dlterm { font-weight: bold; } +.dltermexpand { font-weight: bold; margin-top: 1em; } +.defListHead { font-weight: bold; text-decoration: underline; } +.parmListKwd { font-weight: bold; } +.parmListVar { font-style: italic; } +.pk { font-weight: bold; text-decoration: underline; } + +*[compact="yes"]>li { margin-top: 0em;} +*[compact="no"]>li { margin-top: .53em;} +.liexpand { margin-top: 1em; margin-bottom: 1em } +.sliexpand { margin-top: 1em; margin-bottom: 1em } +.dlexpand { margin-top: 1em; margin-bottom: 1em } +.ddexpand { margin-top: 1em; margin-bottom: 1em } +.stepexpand { margin-top: 1em; margin-bottom: 1em } +.substepexpand { margin-top: 1em; margin-bottom: 1em } + +div.imageleft { text-align: left } +div.imagecenter { text-align: center } +div.imageright { text-align: right } +div.imagejustify { text-align: justify } + +pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre} + +CITE { font-style: italic; } +EM { font-style: italic; } +STRONG { font-weight: bold; } +VAR { font-style: italic; } + +/************************************************************************ + Styles added to support .NET output. Not used by standard processing. + ************************************************************************/ + +body.dotnet /* This body tag requires the use of one of the sets of banner and/or text div ids */ + { + margin: 0px 0px 0px 0px; + padding: 0px 0px 0px 0px; + background: #ffffff; + color: #000000; + width: 100%; + } + +div.nstext /* Creates the scrolling text area for Nonscrolling region topic */ + { + padding: 5px 10px 0px 22px; + } + +div.nsbanner /* Creates Nonscrolling banner region */ + { + position: relative; + left: 0px; + padding: 0px 0px 0px 0px; + border-bottom: 1px solid #999999; + } + +div.bannerrow1 /* provides full-width color to top row in running head */ + { + background-color: #99ccff; + } + +/* STYLES FOR RUNNING HEADS */ + +table.bannerparthead, table.bannertitle /* General values for the Running Head tables */ + { + position: relative; + left: 0px; + top: 0px; + padding: 0px 0px 0px 0px; + margin: 0px 0px 0px 0px; + width: 100%; + height: 21px; + border-collapse: collapse; + border-style: solid; + border-width: 0px; + background-color: #99ccff; + font-size: 100%; + } +table.bannerparthead td /* General Values for cells in the top row of running head */ + { + margin: 0px 0px 0px 0px; + padding: 2px 0px 0px 4px; + vertical-align: middle; + /*border-width: 0px 0px 1px 0px; */ + border-width: 0px + border-style: solid; + border-color: #999999; + background: transparent; + font-style: italic; + font-weight: normal; + } +table.bannerparthead td.product /* Values for top right cell in running head */ + { /* Allows for a second text block in the running head */ + text-align: right; + padding: 2px 5px 0px 5px; + } + +h1.dtH1 { + margin-left: -18px; + } +div.titlerow /* provides non-scroll topic title area (requires script) */ + { + width: 100%; /* Forces tables to have correct right margin */ + padding: 0px 10px 0px 22px; + background-color: #99ccff; + } +div.titlerow h1 + { + margin-top: 0em; + font-weight: bold; + margin-bottom: .2em + } diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml new file mode 100644 index 000000000..4cfaa46ef --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/plugin.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" ?> +<?eclipse version="3.0"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<!-- /******************************************************************************* + * Copyright (c) 2000, 2005 IBM Corporation and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * IBM Corporation - initial API and implementation + *******************************************************************************/ --> +<plugin> + + <extension point="org.eclipse.help.contexts"> + <contexts file="wsconsumptionui-f1Contexts.xml" plugin="org.eclipse.jst.ws.consumption.ui"/> + <contexts file="wscreationui-f1Contexts.xml" plugin="org.eclipse.jst.ws.creation.ui"/> + </extension> +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html new file mode 100644 index 000000000..894f1f163 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html @@ -0,0 +1,140 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Generating a Java client proxy and a sample application from a WSDL document using the Axis run-time environment" /> +<meta name="abstract" content="The Web Service Client wizard assists you in generating a Java bean proxy and a sample application. The sample Web application demonstrates how to code a proxy file." /> +<meta name="description" content="The Web Service Client wizard assists you in generating a Java bean proxy and a sample application. The sample Web application demonstrates how to code a proxy file." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/caxistover.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tsampappa" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Generating a Java client proxy and a sample application from +a WSDL document using the Axis run-time environment</title> +</head> +<body id="tsampappa"><a name="tsampappa"><!-- --></a> + +<h1 class="topictitle1">Generating a Java client proxy and a sample application +from a WSDL document using the Axis run-time environment</h1> +<div><p>The Web Service Client wizard assists you in generating a Java™ bean +proxy and a sample application. The sample Web application demonstrates how +to code a proxy file.</p> +<div class="p"><p>Prerequisites:</p> +<ol><li>If you are using the Apache Jakarta Tomcat servlet +container as your server, you must install it, configure an instance of it, +and create a Web project targeted to it as described in <a href="ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li> +<li>Discover and import a WSDL document into the Web project. You can only +use a WSDL file that contains a service element.</li> +</ol> +</div> +<div class="section">To generate a Java client proxy and a sample application +from a discovered WSDL document:</div> +<ol><li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective +> J2EE</span>).</span></li> +<li><span>In the Navigator view, select the Web project in which you want +to generate a sample application.</span></li> +<li><span>Click <span class="uicontrol">File > New > Other</span>. Select <span class="uicontrol">Web +Services</span> in order to display the various Web service wizards. +Select the <span class="uicontrol">Web Service Client</span> wizard. Click <span class="uicontrol">Next</span>.</span></li> +<li><span>Web Services page: Select the type of proxy to be generated, and +whether or not it will be tested.</span></li> +<li><span>Client Environment Configuration page: Select the run-time environment +and the server for your Web service client.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Explore Options</span> and select the +Apache Axis run-time environment and select the server on which you want to +run your Web service client.</span></li> +<li class="substepexpand"><span>Select the type and name of project in which you want the Web +service client created.</span> <ul><li> If you enter the name of an existing project, the project type field +must match that of the existing project. Ensure that the project selected +as the Client Web Project is different from the Service Web Project, or the +service will be overwritten by the client's generated artifacts.</li> +<li>If you enter a name of a project that does not already exist, the wizard +will create the project for you.</li> +<li>Note that the only project type supported for Axis and SOAP run-time clients +is a Web project. If you want the client to be created in a Java, EJB, +or Application Client project, you must select the WebSphere<sup>®</sup> run-time environment for +your client.</li> +</ul> +</li> +</ol> +</li> +<li><span>Web Service Selection page: Enter the URI to the WSDL, WSIL, or +HTML file that will be used to generate the client. You can optionally generate +a WSIL file from this file as well.</span></li> +<li><span>Web Service Proxy page: This panel shows the options for the proxy. +It lists the folder where the proxy will be generated, and you can optionally +create custom mappings between namespaces and packages.</span></li> +<li><span>Web Service Namespace to Package Mappings page: if you selected + <span class="uicontrol">Define custom mapping for namespace to package</span> on +the previous page, you can enter your custom mapping pairs on this page by +clicking <span class="uicontrol">Add</span>.</span></li> +<li><span>Web Service Client Test page: Select the test facility that you +will use to test the proxy, and the methods that you want included in the +proxy. Note that the Universal Test Client (UTC) is only compatible with Web +service clients deployed on WebSphere servers.</span></li> +<li><span>Click <span class="uicontrol">Finish</span>. If you have selected to test +the proxy, the test client will open in a browser window.</span></li> +</ol> +<div class="section"><p>The generated Java bean proxy provides a remote procedure +call interface to the Web service. The sample Web application demonstrates +how to code the proxy file.</p> +<p>Once you have generated your Java client +proxy, you may test the methods of the Web service through the proxy using +Web Services sample JSPs or the Universal test client.</p> +<ul><li>If you have selected to test the generated proxy using Web service JSPs, +the proxy is launched in a Web browser at the following URL: <samp class="codeph">http://localhost: <var class="varname">port</var>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/ <var class="varname">WebServiceName</var>/TestClient.jsp</samp> You +can use this sample application to test the Web service by selecting a method, +entering a value for the method, and clicking <span class="uicontrol">Invoke</span>. +The result of the method will display in the results pane.</li> +<li>If you have selected to test the generated proxy using the Universal Test +Client, it will be launched in a browser window at the following URL: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <span class="uicontrol">Invoke</span>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <strong>Go</strong>. The result will display in the Status pane.</li> +</ul> +<p>For more information on creating a Web project, refer to the Web application +development documentation.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html"> Web services run-time environments</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">WSDL documents</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html new file mode 100644 index 000000000..73c515fcb --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html @@ -0,0 +1,176 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Creating a Java bean skeleton from a WSDL document using the Apache Axis run-time environment" /> +<meta name="abstract" content="The Web service wizard assists you in creating a skeleton bean from an existing WSDL document. The skeleton bean contains a set of methods that correspond to the operations described in the WSDL document. When the bean is created, each method has a trivial implementation that you replace by editing the bean." /> +<meta name="description" content="The Web service wizard assists you in creating a skeleton bean from an existing WSDL document. The skeleton bean contains a set of methods that correspond to the operations described in the WSDL document. When the bean is created, each method has a trivial implementation that you replace by editing the bean." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/caxistover.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tsklwsdla" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating a Java bean skeleton from a WSDL document using the +Apache Axis run-time environment</title> +</head> +<body id="tsklwsdla"><a name="tsklwsdla"><!-- --></a> + +<h1 class="topictitle1">Creating a Java bean skeleton from a WSDL document using the Apache +Axis run-time environment</h1> +<div><p>The Web service wizard assists you in creating a skeleton bean +from an existing WSDL document. The skeleton bean contains a set of methods +that correspond to the operations described in the WSDL document. When the +bean is created, each method has a trivial implementation that you replace +by editing the bean.</p> +<div class="p"><p>Prerequisites:</p> +<ol><li id="tsklwsdla__createtomcatlink"><a name="tsklwsdla__createtomcatlink"><!-- --></a>If you are using the Apache Jakarta Tomcat servlet +container as your server, you must install it, configure an instance of it, +and create a Web project targeted to it as described in <a href="ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li> +<li>Create or import a WSDL file into the Web Content folder of the Web project. +You can only use a WSDL file that contains a service element.</li> +</ol> +</div> +<div class="section">To create a Web service from a WSDL file using the Apache Axis 1.0 +run-time environment:</div> +<ol><li class="stepexpand"><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective +> J2EE</span>).</span></li> +<li class="stepexpand"><span>In the Project Explorer view, select the WSDL file that you created +or imported into the Web Content folder of your Web project.</span></li> +<li class="stepexpand"><span>Click <span class="uicontrol">File > New > Other</span>. Select <span class="uicontrol">Web +Services</span> in order to display the various Web service wizards. +Select the <span class="uicontrol">Web Service</span> wizard. Click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>Web Services page: select <span class="uicontrol">Top down Java bean Web service</span> as +your Web service type. You can optionally choose to do the following: </span> <ul><li>Start the Web service in a Web project - if you do not select this option +you will have to manually start the Web service. You must select this option +to enable the other options on this page.</li> +<li>Launch the Web Services Explorer to publish your Web service to a UDDI +registry.</li> +<li>Generate a Java™ bean client proxy to the Web service. The Java bean +client proxy that is generated provides a remote procedure call interface +to the Web service.</li> +<li>Test the Web service - this allows you to test the Web service in the +Web Service Explorer before a proxy is generated.</li> +<li>Send the Web service traffic through the TCP/IP Monitor, which allows +you to watch the SOAP traffic generated by the Web service and to test this +traffic for WS-I compliance. Note that this is only supported for Tomcat v4.0 +and v4.1. If you are using Tomcat v5.0 and want to monitor the Web service +traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html</a></li> +</ul> +</li> +<li class="stepexpand"><span>Web Service Selection page: Enter the URI to the WSDL, WSIL, or +HTML file that will be used to generate the Java bean. If you have selected the WSDL +file before starting the wizard, this information should be prefilled. You +can optionally generate a WSIL file from this file as well.</span> Ensure +that there are no spaces at the beginning of the URI or you may generate a +null pointer exception.</li> +<li class="stepexpand"><span>Service Deployment Configuration page: specify the server and client +deployment settings.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis +run-time environment and select the server on which you want to run your Web +service and Web service client.</span></li> +<li class="substepexpand"><span>Select the Web project in which you want your Web service created. </span> The wizard will create this for you if they do not already exist.</li> +<li class="substepexpand"><span>Select the type and name of project in which you want the Web +service client created. If you enter the name of an existing project, the +project type field must match that of the existing project. If you enter a +name of a project that does not already exist, the wizard will create the +project for you. Note that the only project type supported for Axis and SOAP +run-time clients is a Web project. If you want the client to be created in +a Java, +EJB, or Application Client project, you must select the WebSphere<sup>®</sup> run-time +environment for your client.</span></li> +</ol> +</li> +<li class="stepexpand"><span>Web Services Skeleton Java Bean Configuration page: Select the +folder where the generated Java will be stored. If you want to review +or edit the mappings between packages and namespaces, select the <span class="uicontrol">Define +custom mapping for namespace to package</span> check box. Click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>Web Service Namespace to Package Mappings page: if you selected + <span class="uicontrol">Define custom mapping for package to namespace</span> on +the previous panel, you can enter your custom mapping pairs on this panel +by clicking <span class="uicontrol">Add.</span> Click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>Web Service Test page: If you selected to test the Web service, +select the test facility for the generated Web service. This will open the +Web service in the Web Services Explorer. Select the operation you want to +test, enter the required information, and click <span class="uicontrol">Go</span>. +The result will display in the Status pane. Click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>Web Service Proxy page: If you have selected to generate a proxy, +this page shows the options for the proxy. It lists the folder where the proxy +will be generated, and you can optionally create custom mappings between namespaces +and packages. Click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>Web Service Client Test page: Use this page to select the following +options: </span><ol type="a"><li><span>Select your test facility. You can test the generated proxy +in the Universal Test Client or the Web Service Explorer, or you can generate +a sample Web service JSP.</span></li> +<li><span>If you selected to test the proxy through a JSP, you can select +the folder where the JSP will be located, and you can select the methods that +will be included in the JSP.</span></li> +<li><span>Select <span class="uicontrol">Run test on server</span> to start the +server for you automatically.</span></li> +</ol> +</li> +<li class="stepexpand"><span>Web Service Publication page: If you have selected to publish your +Web service to a UDDI registry, use this page to launch the Web Services Explorer +and select the UDDI registry to which the Web service will be published. Click + <span class="uicontrol">Finish</span>.</span></li> +</ol> +<div class="section">After the Web service has been created, the following may occur depending +on the options you selected: <ul><li>If you have selected to test the generated proxy using Web service JSPs, +the proxy is launched in a Web browser at the following URL: <samp class="codeph">http://localhost: <var class="varname">port</var>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/<var class="varname">WebServiceName</var>/TestClient.jsp</samp> You +can use this sample application to test the Web service by selecting a method, +entering a value for the method, and clicking <span class="uicontrol">Invoke</span>. +The result of the method will display in the results pane.</li> +<li>If you have selected to test the generated proxy using the Universal Test +Client, it will be launched in a browser window at the following URL: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <span class="uicontrol">Invoke</span>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <strong>Go</strong>. The result will display in the Status pane.</li> +<li>If you have selected to publish the Web service, the Web Services Explorer +is launched displaying the page required to publish your Web service to the IBM<sup>®</sup> UDDI +Test Registry. Follow the instructions in <var class="varname">Publishing the Web service</var> to +complete this task.</li> +</ul> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html"> Web services run-time environments</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div> +<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">WSDL documents</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html new file mode 100644 index 000000000..10a3d3877 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html @@ -0,0 +1,75 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Creating an Apache Tomcat server and Web project" /> +<meta name="abstract" content="If you plan to create a Web service that uses Apache Jakarta Tomcat as its server, Tomcat must be installed and a server created before you begin creating your Web service." /> +<meta name="description" content="If you plan to create a Web service that uses Apache Jakarta Tomcat as its server, Tomcat must be installed and a server created before you begin creating your Web service." /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="creatinganapachetomcatserver" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating an Apache Tomcat server and Web project</title> +</head> +<body id="creatinganapachetomcatserver"><a name="creatinganapachetomcatserver"><!-- --></a> + +<h1 class="topictitle1">Creating an Apache Tomcat server and Web project</h1> +<div><p>If you plan to create a Web service that uses Apache Jakarta Tomcat +as its server, Tomcat must be installed and a server created before you begin +creating your Web service.</p> +<div class="p">Install Apache Jakarta Tomcat from this URL: <a href="http://jakarta.apache.org/tomcat" target="_blank">http://jakarta.apache.org/tomcat</a></div> +<div class="section">Once you have installed the server, create a Tomcat server in the +workbench by doing the following: </div> +<ol><li class="stepexpand"><span>From the File menu, select <span class="uicontrol">New > Other > Server > Server +> Next</span>.</span></li> +<li class="stepexpand"><span>Select Tomcat v 3.x, 4.x or v5.0 as the server type, electing the +correct version of Tomcat for your install, and click <span class="uicontrol">Next</span>.</span></li> +<li class="stepexpand"><span>On the Tomcat server page:</span><ol type="a"><li><span>Enter a server name.</span></li> +<li><span>Specify where Tomcat is installed.</span></li> +<li><span>Click <span class="uicontrol">Installed JREs</span>, click <span class="uicontrol">Add</span>, +and enter the appropriate information for the JDK you plan to use for Tomcat. +For example, for Tomcat v5.0 the JRE name would be jdk141 and the JRE home +would be the home directory for JDK 1.4.1. Click <span class="uicontrol">OK</span> twice +once you have entered this information. Ensure that the newly added JDK is +now selected in the JRE field of the Tomcat server page. Note that if you +point the server at a JRE rather than a JDK the JSPs will not properly compile +and will not be able to run on the Tomcat server.</span></li> +</ol> +</li> +<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> To see the +server you have created in the workspace, from the Window menu select <span class="uicontrol">Show +view > Other > Server > Servers > Ok.</span> </li> +</ol> +<div class="example"><p>To build a dynamic Web project that points to the Tomcat server +that you have created:</p> +<ol><li>Create the service Web project by selecting <span class="uicontrol">New > Web > Dynamic +Web project</span>. Enter the following information: <ul><li>Web Project: enter a project name</li> +<li>Servlet version: 2.3</li> +<li>Target Server: Tomcat server v3.x, 4.x or 5.x depending on the version +you installed</li> +<li>Ensure that <span class="uicontrol">Add Module to an EAR module</span> is <em>not</em> selected.</li> +</ul> +</li> +<li>Click <span class="uicontrol">Finish</span>.</li> +<li>To associate the project with the server, right-click the Tomcat server +you created in the Server view and select <span class="uicontrol">Add and remove projects</span>. +Select the service and client projects from the Available projects list and +click <span class="uicontrol">Add</span>. </li> +</ol> +</div> +</div> +<div></div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html new file mode 100644 index 000000000..896f3e499 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html @@ -0,0 +1,194 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Creating a Web service from a Java bean using the Apache Axis run-time environment" /> +<meta name="abstract" content="The Web Service wizard assists you in creating a new Web service, configuring it for deployment, and deploying the Web service to a server. Once your Web service is deployed, the wizard assists you in generating the client proxy and sample application to test the Web service. When you have completed testing, you can publish your Web service to a UDDI Business Registry using the Export wizard." /> +<meta name="description" content="The Web Service wizard assists you in creating a new Web service, configuring it for deployment, and deploying the Web service to a server. Once your Web service is deployed, the wizard assists you in generating the client proxy and sample application to test the Web service. When you have completed testing, you can publish your Web service to a UDDI Business Registry using the Export wizard." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/caxistover.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="twsbeana" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating a Web service from a Java bean using the Apache Axis +run-time environment</title> +</head> +<body id="twsbeana"><a name="twsbeana"><!-- --></a> + +<h1 class="topictitle1">Creating a Web service from a Java bean using the Apache Axis run-time +environment</h1> +<div><p>The Web Service wizard assists you in creating a new Web service, +configuring it for deployment, and deploying the Web service to a server. +Once your Web service is deployed, the wizard assists you in generating the +client proxy and sample application to test the Web service. When you have +completed testing, you can publish your Web service to a UDDI Business Registry +using the Export wizard.</p> +<div class="p"><div class="p">Prerequisites:<ol><li>If you are using the Apache Jakarta Tomcat servlet +container as your server, you must install it, configure an instance of it, +and create a Web project targeted to it as described in <a href="ttomcatserv.html">Creating an Apache Tomcat server and Web project</a></li> +<li>Create or import a bean into the Java™ source folder of the Web project.</li> +</ol> +</div> +</div> +<div class="section">To create a Web service from a bean using the Apache Axis run-time +environment:</div> +<ol><li class="stepexpand"><span>Switch to the J2EE perspective ( <span class="uicontrol">Window > Open Perspective +> J2EE</span>).</span></li> +<li class="stepexpand"><span>In the Project Explorer view, select the bean that you created +or imported into the source folder of your Web project.</span></li> +<li class="stepexpand"><span>Click <span class="uicontrol">File > New > Other</span>.</span> Select<span class="uicontrol">Web +Services</span> in order to display the various Web service wizards. +Select the <span class="uicontrol">Web Service</span> wizard. Click <span class="uicontrol">Next</span>.</li> +<li class="stepexpand"><span>Web Services page: select <span class="uicontrol">Bottom up Java bean Web service</span> as +your Web service type. You can optionally choose to do the following: </span> <ul><li>Start the Web service in a Web project - if you do not select this option +you will have to manually start the Web service. You must select this option +to enable the other options on this page.</li> +<li>Launch the Web Services Explorer to publish your Web service to a UDDI +registry.</li> +<li>Generate a Java bean client proxy to the Web service. The Java bean +client proxy that is generated provides a remote procedure call interface +to the Web service.</li> +<li>Test the Web service - this allows you to test the Web service in the +Web Service Explorer before a proxy is generated.</li> +<li>Send the Web service traffic through the TCP/IP Monitor, which allows +you to watch the SOAP traffic generated by the Web service and to test this +traffic for WS-I compliance. Note that this is only supported for Tomcat v4.0 +and v4.1. If you are using Tomcat v5.0 and want to monitor the Web service +traffic, you need to manually set up a TCP/IP monitor as described in <a href="../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html">../../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html</a></li> +</ul> +</li> +<li class="stepexpand"><span>Object selection page: select the Java bean from which the Web service will +be created.</span></li> +<li class="stepexpand"><span>Service Deployment Configuration page: specify the server and client +deployment settings.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Edit</span> and select the Apache Axis +run-time environment and select the server on which you want to run your Web +service and Web service client.</span></li> +<li class="substepexpand"><span>Select the Web project in which you want your Web service created, +and the EAR with which it will be associated. </span> The wizard will +create these for you if they do not already exist.</li> +<li class="substepexpand"><span>Select the type and name of project in which you want the Web +service client created. If you enter the name of an existing project, the +project type field must match that of the existing project. If you enter a +name of a project that does not already exist, the wizard will create the +project for you. Note that the only project type supported for Axis and SOAP +run-time clients is a Web project. If you want the client to be +created in a Java, EJB, or Application Client project, you must select +the WebSphere<sup>®</sup> run-time +environment for your client.</span></li> +<li class="substepexpand"><span>Select an existing EAR or enter a unique name to associate the +Web service client with a different EAR than the Web service EAR. <strong>Note:</strong> Selecting +different EARs for the Web service and Web service client can reduce the chance +of encountering run time errors, but will use more system resources.</span></li> +</ol> +</li> +<li class="stepexpand"><span>A message will display stating that you have made a WS-I non-compliant +selection.</span> The Apache Axis run-time environment is not WS-I compliant. +Select <span class="uicontrol">Ignore</span>.</li> +<li class="stepexpand"><span>Web Service Java Bean Identity page: the Web service +URI and WSDL name will be listed.</span> You have the following +options:<ul><li>Select the methods to expose.</li> +<li>Select the encoding style. RPC/Encoded is the recommended encoding style +for the Axis run-time environment. This encoding method is not WS-I compliant.</li> +<li>Select if you want to customize the package to namespace mappings.</li> +</ul> +Click <span class="uicontrol">Next</span></li> +<li class="stepexpand"><span>Web Service Package to Namespace Mappings page: if you selected + <span class="uicontrol">Define custom mapping for package to namespace</span> on +the previous panel, you can enter your custom mapping pairs on this panel +by clicking <span class="uicontrol">Add</span>.</span></li> +<li class="stepexpand"><span>Web Service Test page: If you selected to test the Web service, +select the test facility for the generated Web service.</span> This will +open the Web service in the Web Services Explorer. Select the operation you +want to test, enter the required information, and click<span class="uicontrol">Go</span>. +The result will display in the Status pane. Click <span class="uicontrol">Next</span>.</li> +<li class="stepexpand"><span>Web Service Proxy page: if you have selected to generate a proxy, +select if you want to customize the package to namespace mappings.</span></li> +<li class="stepexpand"><span>Web Service Client Test page: Use this page to select the following +options: </span><ol type="a"><li><span>Select your test facility. You can test the generated proxy +in the Universal Test Client or the Web Service Explorer, or you can generate +a sample Web service JSP.</span></li> +<li><span>If you selected to test the proxy through a JSP, you can select +the folder where the JSP will be located, and you can select the methods that +will be included in the JSP.</span></li> +<li><span>Select <span class="uicontrol">Run test on server</span> to start the +server for you automatically.</span></li> +</ol> +</li> +<li class="stepexpand"><span>Web Service Publication page: Select whether or not you want to +publish this Web service to a UDDI registry. Click <span class="uicontrol">Finish</span>. </span> Note: you may see a warning stating <samp class="codeph">Error in generating WSDL +from Java. ClassNotFound: <bean name></samp>. This error can be safely +ignored.</li> +</ol> +<div class="section"><div class="p">After the Web service has been created, the following may occur +depending on the options you selected: <ul><li>If you have selected to test the generated proxy using Web service JSPs, +the proxy is launched in a Web browser at the following URL: http://localhost: <var class="varname">port</var>/ <var class="varname">WebProject</var>Client/sample<em>BeanName</em>/ <var class="varname">WebServiceName</var>/TestClient.jsp You can use +this sample application to test the Web service by selecting a method, entering +a value for the method, and clicking <span class="uicontrol">Invoke</span>. The result +of the method will display in the results pane.</li> +<li>If you have selected to test the generated proxy using the Universal Test +Client, it will be launched in a browser window at the following URL: <tt class="sysout">http://localhost:9080/UTC/preload?object= <var class="varname">BeanPackage</var>. <var class="varname">BeanServiceProxy</var></tt>. In the Reference pane, +under Object References, expand the proxy stub to display the methods of the +Web service. Click the method you want to test, enter a value in the Parameters +pane, and click <span class="uicontrol">Invoke</span>. The result will be generated +below.</li> +<li>If you have selected to test the Web service using the Web Services Explorer, +the Explorer will open. Select the operation you want to test, enter the required +information, and click <strong>Go</strong>. The result will display in the Status pane.</li> +<li>If you have selected to publish the Web service, the Web Services Explorer +is launched displaying the page required to publish your Web service to the IBM<sup>®</sup> UDDI +Test Registry. Follow the instructions in <var class="varname">Publishing the Web service</var> to +complete this task.</li> +</ul> +</div> +<p> <span class="uicontrol">Important:</span> If your methods contain types, +not supported by the sample, such as arrays, indexed properties, and collections, +the methods will be omitted from the sample and you will receive a warning +message.</p> +<p>Once you have created your Web service from a bean, you may +test the methods of your Web service, using the Universal Test Client, and +then publish your Web service to a UDDI Business Registry. For more information +on publishing your Web service using the Web Services Explorer, refer to Publishing +a Web service. For more information on the Universal Test Client, refer +to the Server tools online help.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/caxistover.html" title="This run-time environment is for users who prefer to develop for the open Apache Axis platform. It is for non-production use only. Axis is the third generation of the Apache SOAP implementation. It evolved from Apache SOAP (which began at IBM as SOAP4J) to make the SOAP engine more flexible, configurable, and able to handle both SOAP and the upcoming XML Protocol specification from the W3C open-source effort.">Creating Web services with the Apache Axis run-time environment</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cruntime.html"> Web services run-time environments</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div> +<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">WSDL documents</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml new file mode 100644 index 000000000..4f5c835a3 --- /dev/null +++ b/docs/org.eclipse.jst.ws.axis.ui.doc.user/wsaxisbuild_toc.xml @@ -0,0 +1,5 @@ +<?xml version="1.0" encoding="utf-8"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<toc label="wsaxis" link_to="../com.ibm.etools.webservice.creation.doc/wscreationt1_toc.xml#wsaxis" topic="concepts/caxistover.html"> + <topic label="Creating an Apache Tomcat server and Web project" href="tasks/ttomcatserv.html"/> +</toc>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html new file mode 100644 index 000000000..cbb99c622 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html @@ -0,0 +1,122 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Universal Description, Discovery, and Integration (UDDI)" /> +<meta name="abstract" content="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services." /> +<meta name="description" content="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsdlud.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.uddi.registry.doc.user/concepts/cusercats.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cuddi" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Universal Description, Discovery, and Integration (UDDI)</title> +</head> +<body id="cuddi"><a name="cuddi"><!-- --></a> + +<h1 class="topictitle1">Universal Description, Discovery, and Integration (UDDI)</h1> +<div><p>Universal Description, Discovery, and Integration (UDDI) specification +defines a way to publish and discover information about Web services.</p> +<div class="p">UDDI has two functions: <ul><li>It is a SOAP-based protocol that defines how clients communicate with +UDDI registries.</li> +<li>It is a particular set of global replicated registries.</li> +</ul> +</div> +<p>UDDI includes an XML schema for SOAP messages that defines a set of documents +to describe business and services information, a common set of APIs for querying +and publishing information to the directories, and an API for replicating +directory entries between peer UDDI nodes.</p> +<p>For more information on UDDI refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p> +<div class="section"><h4 class="sectiontitle">UDDI registries</h4><p>UDDI manages the discovery of Web +services by relying on a distributed registry of businesses and their service +descriptions implemented in a common XML format. Before you can publish your +business entity and Web service to a public registry, you must first register +your business entity with a UDDI registry.</p> +<p>UDDI registries come in two +forms: public and private. Both types comply to the same specifications. +A private registry enables you to publish and test your internal e-business +applications in a secure, private environment. Rational<sup>®</sup> Developer +products include a private UDDI registry. </p> +<p>A public registry is +a collection of peer directories that contain information about businesses +and services. It locates services that are registered at one of its peer nodes +and facilitates the discovery of published Web services. Data is replicated +at each of the registries on a regular basis. This ensures consistency in +service description formats and makes it easy to track changes as they occur. IBM<sup>®</sup> maintains +two public registries called the IBM UDDI Business Registry and the IBM UDDI Test +Registry. The IBM UDDI +Test Registry allows you to develop your Web service and experience the UDDI +registration process without placing your Web service in an official registry. +Use the IBM UDDI +Test Registry to experiment with UDDI, and to test and validate your Web service. +For more information on the IBM's public registries, refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a> For +a list of public registries, refer to <a href="http://www.uddi.org/register.html" target="_blank">http://www.uddi.org/register.html</a></p> +<p>A private +registry allows you to publish and test your internal applications in a secure, +private environment. IBM has developed a private registry called the IBM WebSphere<sup>®</sup> UDDI +Registry. The IBM WebSphere UDDI Registry is a persistent storage +mechanism for information published in the Registry. There are two implementations +of the SOAP-based APIs - the WebSphere Studio version 5.0 and 5.1 registries +based on UDDI v2 and the Rational Developer products' registry based on UDDI +v3 - that allow programmatic publish and inquiry operations. The private registry +supports access using JDBC 2. Access using JDBC 1 is not supported. The IBM private +registry and the Web Services Explorer support user-defined custom taxonomies +in addition to the standard NAICS, UNSPSC and ISO-3166 taxonomies.</p> +<p>The +UDDI Business Registry acts as a B2B directory linking marketplaces, buyers, +and sellers. The information provided in the registry consists of three components: +white pages, yellow pages, and green pages. White pages include the business +name, contact information, and a text description of the business's services. +Yellow pages include industrial categorizations based on standard taxonomies +such as NAICS, ISO 3166, and UNSPSC. Green pages include references to specifications +for Web services and pointers to various file and URL-based discovery mechanisms. +This makes it easy for businesses to integrate across marketplaces. Because +it is registered, information is made available across all applications. For +more information on NAICS refer to <a href="http://www.naics.com" target="_blank">www.naics.com</a> For more information on UNSPSC refer +to <a href="http://www.unspsc.org" target="_blank">www.unspsc.org</a> For +more information on ISO 3166 refer to <a href="http://www.iso.org/iso/en/prods-services/iso3166ma/index.html" target="_blank">http://www.iso.org/iso/en/prods-services/iso3166ma/index.html</a></p> +<p>Businesses +populate the registry with descriptions of the services that they support. +UDDI assigns a unique identifier to each service description and business +registration. These become the service and business keys respectively. Search +engines, and applications query the registry to discover services. UDDI servers +are a directory of available services and service providers.</p> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="cwsdlud.html" title="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries.">Relationship between UDDI and WSDL</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsilud.html">Relationship between UDDI and WSIL</a></div> +<div><a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/concepts/cusercats.html">User-defined UDDI categories</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html"> Configuring a Unit Test UDDI Registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html new file mode 100644 index 000000000..d1e98aed9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html @@ -0,0 +1,136 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Relationship between UDDI and WSDL" /> +<meta name="abstract" content="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries." /> +<meta name="description" content="The Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services. UDDI has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients communicate with registries, and (2) it is a particular set of globally replicated registries." /> +<meta name="DC.Relation" scheme="URI" content="cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsdlud" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Relationship between UDDI and WSDL</title> +</head> +<body id="cwsdlud"><a name="cwsdlud"><!-- --></a> + +<h1 class="topictitle1">Relationship between UDDI and WSDL</h1> +<div><p>The Universal Description, Discovery, and Integration (UDDI) specification +defines a way to publish and discover information about Web services. UDDI +has two functions: (1) it is a SOAP-based protocol that defines how UDDI clients +communicate with registries, and (2) it is a particular set of globally replicated +registries.</p> +<p>Registering a service involves four core data structure types:</p> +<ul><li>The <tt class="sysout">businessEntity</tt> data type contains information +about the business that has a published service.</li> +<li>The <tt class="sysout">businessService</tt> data type is a description +of a Web service.</li> +<li>The <tt class="sysout">bindingTemplate</tt> data type contains technical +information for determining the entry point and construction specifications +for invoking a Web service.</li> +<li>The <tt class="sysout">tModel</tt> data type provides a reference +system to assist in the discovery of Web services and acts as a technical +specification for a Web service.</li> +</ul> +<p>For more information on the UDDI data types, refer to the related reference +topics at the end of this topic.</p> +<p>Web Services Description Language (WSDL) is an XML-based standard specification +for describing Web services. WSDL defines an XML format for describing network +services as a set of endpoints that operate on messages that contain either +document-oriented or procedure-oriented information.</p> +<p>The WSDL service description can be structured in many ways. However, to +assist with publishing and finding WSDL service descriptions in a UDDI registry, +WSDL documents consist of two main parts: </p> +<ul><li>The service interface definition describes the abstract type interface +and its protocol binding, known as the WSDL binding document</li> +<li>The service implementation definition describes the service access location +information, known as the WSDL service document</li> +</ul> +<p>When creating Web services with the IBM<sup>®</sup> SOAP run-time environment, the +tools in this product store these two main parts in three separate XML documents +when generating Web services from Java™ beans, EJBs, and URLs: the WSDL service +document, the WSDL binding document, and the WSDL interface document. When +generating Web services from DADX files, the two main parts are stored in +two separate XML documents: the WSDL binding document and the WSDL service +document. For more information on the WSDL service, binding, and interface +documents, refer to the related reference topics at the end of this topic.</p> +<p>Whe creating Web services with the WebSphere<sup>®</sup> run-time environment or +the Apache Axis run-time environment, the Web services tools create a single +WSDL document when generating Web services from Java beans or EJBs. This WSDL document contains +both the service interface and implementation documents.</p> +<p>A service interface is described by a WSDL document that contains the types, +import, message, portType, and binding elements. A service interface contains +the WSDL service definition that will be used to implement one or more services. +It is an abstract definition of a Web service, and is used to describe a specific +type of service. This document can reference another service interface document +using an import element. The Web services tools in this product generate a +service interface document that contains only the message and portType elements +that are referenced by the binding document that contains only bindings for +the portType.</p> +<p>The service implementation document contains the service elements. A service +implementation document contains a description of a service that implements +a service interface. At least one of the import elements will contain a reference +to the WSDL service interface document; however monolithic WSDL such as that +created using the Axis and WebSphere run-time environments do not have imports. +A service implementation document can contain references to more than one +service interface document.</p> +<p>A service provider hosts a Web service and makes it accessible using protocols +such as SOAP/HTTP and SOAP/JMS. The Web service is described by the WSDL documents +that are stored on the provider's server or in a special repository. The WSDL +documents are referenced by UDDI business services (service documents) and +tModels (binding documents). These pointers enable discovery of a Web service +by a service requestor.</p> +<p>Figure 1. Relationship between UDDI and WSDL.</p> +<p> <img src="../images/wsdluddi.gif" alt="Illustration of the relationship between UDDI and WSDL." /> </p> +<p>Figure 1 illustrates the relationship between UDDI and WSDL. The WSDL service +element references the WSDL binding element. The URL of the document containing +the WSDL binding element is published to the UDDI business registry as a tModel. +The URL of the document containing the WSDL service element is published to +the UDDI business registry as a businessService and contains information about +the bindingTemplate. For more information on UDDI registry data structure +types, refer to the related reference section at the end of this document. +Note that the import portion of the diagram is optional depending on the run-time +environment; monolithic WSDL such as that created using the Axis and WebSphere run-time +environments do not have imports.</p> +<p>The service implementation describes an instance of a service. The instance +is defined using a WSDL service element. The service element in a service +implementation document is used to publish a UDDI businessService. When publishing +a WSDL service description, a service interface must be published as a tModel +before a service implementation is published as a businessService.</p> +<p>A service implementation is published in a UDDI registry as part of a businessService +with one or more bindingTemplate elements. The businessService is published +by the service provider. A new businessService is created for a service element +that is defined in the service implementation document. A new bindingTemplate +element is created within a businessService for each port element that is +defined within a service element.</p> +<p>For more information on the relationship between WSDL and UDDI refer to + <a href="http://uddi.org/bestpractices.html" target="_blank">uddi.org/bestpractices.html</a>.</p> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsdl.html">Web Services Description Language (WSDL)</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/ref/rwsdl.html">Web Services Description Language (WSDL)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ibmdita.css b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ibmdita.css new file mode 100644 index 000000000..e20903960 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ibmdita.css @@ -0,0 +1,219 @@ +.unresolved { background-color: skyblue; } +.noTemplate { background-color: yellow; } + +.sidebar {background: silver } +.toc {font-size: small; } + +.base { background-color: #ffffff; } +.breadcrumb { font-size : smaller;} +.prereq { margin-left : 20px;} +.hierarchy { display: block; border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; border-color : Silver;} + +.nested0 { margin-top : 1em;} +.nested1 { } +.nested2 { } + +.p {margin-top: 1em} + +.tableborder { margin-top: 1em; margin-bottom: 1em } +.tablenoborder { margin-top: 1em; margin-bottom: 1em } +caption { text-align: left; font-style: italic } +.simpletableborder { margin-top: 1em; margin-bottom: 1em } +.simpletablenoborder { margin-top: 1em; margin-bottom: 1em } +.choicetableborder { margin-top: 1em; margin-bottom: 1em } +.choicetablenoborder { margin-top: 1em; margin-bottom: 1em } + +.figcap { font-style: italic } +.figdesc { font-style: normal } + +.fignone {margin-top: 1em} +.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.figbottom { border-bottom : 2px solid; border-color : Silver;} +.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.synnone {margin-top: 1em} +.synborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.synsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.syntop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.synbottom { border-bottom : 2px solid; border-color : Silver;} +.syntopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.skip { margin-top: 1em } +.skipspace { margin-top: 1em; margin-bottom: 1em } +.ullinks { list-style-type: none } +.ulchildlink { margin-top: 1em; margin-bottom: 1em } +.olchildlink { margin-top: 1em; margin-bottom: 1em } +.linklist { margin-bottom: 1em } +.linklistwithchild { margin-left: 1.5em; margin-bottom: 1em } +.sublinklist { margin-left: 1.5em; margin-bottom: 1em } +.relconcepts { margin-top: 1em; margin-bottom: 1em } +.reltasks { margin-top: 1em; margin-bottom: 1em } +.relref { margin-top: 1em; margin-bottom: 1em } +.relinfo { margin-top: 1em; margin-bottom: 1em } +div.breadcrumb {margin-bottom: 1em } + +.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; } +.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; } +.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; } +.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; } +.topictitle5 { font-size: 1.17em; font-weight: bold; } +.topictitle6 { font-size: 1.17em; font-style: italic; } +.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;} +.section { margin-top: 1em; margin-bottom: 1em } +.example { margin-top: 1em; margin-bottom: 1em } + +.note { margin-top: 1em; margin-bottom : 1em;} +.notetitle { font-weight: bold } +.notelisttitle { font-weight: bold } +.tip { margin-top: 1em; margin-bottom : 1em;} +.tiptitle { font-weight: bold } +.fastpath { margin-top: 1em; margin-bottom : 1em;} +.fastpathtitle { font-weight: bold } +.important { margin-top: 1em; margin-bottom : 1em;} +.importanttitle { font-weight: bold } +.remember { margin-top: 1em; margin-bottom : 1em;} +.remembertitle { font-weight: bold } +.restriction { margin-top: 1em; margin-bottom : 1em;} +.restrictiontitle { font-weight: bold } +.attention { margin-top: 1em; margin-bottom : 1em;} +.attentiontitle { font-weight: bold } +.dangertitle { margin-top: 1em; font-weight: bold } +.danger { padding: 5px 5px 5px 5px; border: solid; border-width: thin; font-weight: bold; margin-top: 2px; margin-bottom : 1em; } +.cautiontitle { margin-top: 1em; font-weight: bold } +.caution { font-weight: bold; margin-bottom : 1em; } + +ul.simple { list-style-type: none } + +.firstcol { font-weight : bold;} + +.bold { font-weight: bold; } +.boldItalic { font-weight: bold; font-style: italic; } +.italic { font-style: italic; } +.underlined { text-decoration: underline; } +.uicontrol { font-weight: bold; } +.parmname { font-weight: bold; } +.defparmname { font-weight: bold; text-decoration: underline; } +.kwd { font-weight: bold; } +.defkwd { font-weight: bold; text-decoration: underline; } +.var { font-style : italic;} +.shortcut { text-decoration: underline; } + +.ptocH1 {font-size: x-small; } +.ptocH2 {font-size: x-small; } + +.smallCaps { text-transform: uppercase; font-size: smaller; } +.stitle { font-style: italic; text-decoration: underline; } +.nte {} + +.dlterm { font-weight: bold; } +.dltermexpand { font-weight: bold; margin-top: 1em; } +.defListHead { font-weight: bold; text-decoration: underline; } +.parmListKwd { font-weight: bold; } +.parmListVar { font-style: italic; } +.pk { font-weight: bold; text-decoration: underline; } + +*[compact="yes"]>li { margin-top: 0em;} +*[compact="no"]>li { margin-top: .53em;} +.liexpand { margin-top: 1em; margin-bottom: 1em } +.sliexpand { margin-top: 1em; margin-bottom: 1em } +.dlexpand { margin-top: 1em; margin-bottom: 1em } +.ddexpand { margin-top: 1em; margin-bottom: 1em } +.stepexpand { margin-top: 1em; margin-bottom: 1em } +.substepexpand { margin-top: 1em; margin-bottom: 1em } + +div.imageleft { text-align: left } +div.imagecenter { text-align: center } +div.imageright { text-align: right } +div.imagejustify { text-align: justify } + +pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre} + +CITE { font-style: italic; } +EM { font-style: italic; } +STRONG { font-weight: bold; } +VAR { font-style: italic; } + +/************************************************************************ + Styles added to support .NET output. Not used by standard processing. + ************************************************************************/ + +body.dotnet /* This body tag requires the use of one of the sets of banner and/or text div ids */ + { + margin: 0px 0px 0px 0px; + padding: 0px 0px 0px 0px; + background: #ffffff; + color: #000000; + width: 100%; + } + +div.nstext /* Creates the scrolling text area for Nonscrolling region topic */ + { + padding: 5px 10px 0px 22px; + } + +div.nsbanner /* Creates Nonscrolling banner region */ + { + position: relative; + left: 0px; + padding: 0px 0px 0px 0px; + border-bottom: 1px solid #999999; + } + +div.bannerrow1 /* provides full-width color to top row in running head */ + { + background-color: #99ccff; + } + +/* STYLES FOR RUNNING HEADS */ + +table.bannerparthead, table.bannertitle /* General values for the Running Head tables */ + { + position: relative; + left: 0px; + top: 0px; + padding: 0px 0px 0px 0px; + margin: 0px 0px 0px 0px; + width: 100%; + height: 21px; + border-collapse: collapse; + border-style: solid; + border-width: 0px; + background-color: #99ccff; + font-size: 100%; + } +table.bannerparthead td /* General Values for cells in the top row of running head */ + { + margin: 0px 0px 0px 0px; + padding: 2px 0px 0px 4px; + vertical-align: middle; + /*border-width: 0px 0px 1px 0px; */ + border-width: 0px + border-style: solid; + border-color: #999999; + background: transparent; + font-style: italic; + font-weight: normal; + } +table.bannerparthead td.product /* Values for top right cell in running head */ + { /* Allows for a second text block in the running head */ + text-align: right; + padding: 2px 5px 0px 5px; + } + +h1.dtH1 { + margin-left: -18px; + } +div.titlerow /* provides non-scroll topic title area (requires script) */ + { + width: 100%; /* Forces tables to have correct right margin */ + padding: 0px 10px 0px 22px; + background-color: #99ccff; + } +div.titlerow h1 + { + margin-top: 0em; + font-weight: bold; + margin-bottom: .2em + } diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif Binary files differnew file mode 100644 index 000000000..48895f418 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/addfav.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif Binary files differnew file mode 100644 index 000000000..8399bb0eb --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/adduddi.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif Binary files differnew file mode 100644 index 000000000..c60abfc12 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/bindnode.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif Binary files differnew file mode 100644 index 000000000..3fdcbb0d0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/busasst.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif Binary files differnew file mode 100644 index 000000000..debfabd34 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fav.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif Binary files differnew file mode 100644 index 000000000..6dc3ebefc --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/find.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif Binary files differnew file mode 100644 index 000000000..b03233aa2 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/fswsdlicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif Binary files differnew file mode 100644 index 000000000..905e65567 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/mptwsdlicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif Binary files differnew file mode 100644 index 000000000..3e8a29557 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/opnode.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif Binary files differnew file mode 100644 index 000000000..14a11a578 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/publish2.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif Binary files differnew file mode 100644 index 000000000..31d36b735 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/pubserv.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif Binary files differnew file mode 100644 index 000000000..f5c015b0d --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/refserv.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif Binary files differnew file mode 100644 index 000000000..98082685c --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/scenario7.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif Binary files differnew file mode 100644 index 000000000..65b9c0936 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/servnode.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif Binary files differnew file mode 100644 index 000000000..7a02c09b0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddi.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif Binary files differnew file mode 100644 index 000000000..7c148a776 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiref.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif Binary files differnew file mode 100644 index 000000000..0601bc8f8 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/uddiview.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif Binary files differnew file mode 100644 index 000000000..a22eda630 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlbnddetl.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif Binary files differnew file mode 100644 index 000000000..d8ee67c1d --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdldtlicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif Binary files differnew file mode 100644 index 000000000..27f3f6948 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlexp.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif Binary files differnew file mode 100644 index 000000000..cb9d51405 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlfavicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif Binary files differnew file mode 100644 index 000000000..7b6bd28e0 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif Binary files differnew file mode 100644 index 000000000..68ef08ce7 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlnode.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif Binary files differnew file mode 100644 index 000000000..a0f370e38 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlop.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif Binary files differnew file mode 100644 index 000000000..60d7e4136 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopret.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif Binary files differnew file mode 100644 index 000000000..ff93bdd15 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlopretx.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif Binary files differnew file mode 100644 index 000000000..6c197c065 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlservdet.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif Binary files differnew file mode 100644 index 000000000..6081fa92f --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdlstatx.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif Binary files differnew file mode 100644 index 000000000..febb7d558 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsdluddi.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif Binary files differnew file mode 100644 index 000000000..789d68929 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wsilview.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif Binary files differnew file mode 100644 index 000000000..a4fe8b3c6 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/images/wswizicon.gif diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml new file mode 100644 index 000000000..94fe893b9 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/plugin.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" ?> +<?eclipse version="3.0"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<!-- /******************************************************************************* + * Copyright (c) 2000, 2005 IBM Corporation and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * IBM Corporation - initial API and implementation + *******************************************************************************/ --> +<plugin> + + <extension point="org.eclipse.help.toc"> + <toc file="wsconsumptionbuild_toc.xml""/> + <toc file="wsconsumptiont_toc.xml" /> + </extension> +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html new file mode 100644 index 000000000..4996c3556 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html @@ -0,0 +1,113 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="reference" /> +<meta name="DC.Title" content="Data structure types (UDDI registry)" /> +<meta name="abstract" content="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1." /> +<meta name="description" content="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpublish.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpublish.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="ruddi" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Data structure types (UDDI registry)</title> +</head> +<body id="ruddi"><a name="ruddi"><!-- --></a> + +<h1 class="topictitle1">Data structure types (UDDI registry)</h1> +<div><p>Once you have registered and logged in to the UDDI registry that +you want to use, you can register your Web service. Registration of +a service involves four core data structure types: business information, service +information, binding information, and information describing the specifications +for services. The relationship between these data types is described in Figure +1.</p> +<div class="section"><blockquote> <p> <span class="uicontrol">Business information.</span> Information +that is contained in a <tt class="sysout">businessEntity</tt> structure. +The <tt class="sysout">businessEntity</tt> contains information about +the business that has published the service, such as business name, description, +contacts and identifiers.</p> + <p> <span class="uicontrol">Service information.</span> Information +that describes a group of Web services. It is contained in a <tt class="sysout">businessService</tt> structure. +The <tt class="sysout">businessService</tt> contains information about +families of technical services. It groups a set of Web services related +to either a business process or group of services.</p> + <p> <span class="uicontrol">Binding +information.</span> Information represented by the <tt class="sysout">bindingTemplate</tt> structure. +The <tt class="sysout">bindingTemplate</tt> holds technical information +for determining the entry point and construction specifications for invoking +a Web service. The <tt class="sysout">bindingTemplate</tt> provides +the Web service descriptions relevant for application developers that want +to find and invoke a Web service. The <tt class="sysout">bindingTemplate</tt> points +to a service implementation descriptions, for example via a URL.</p> + <p> <span class="uicontrol">Information +describing the specifications for services.</span> Metadata about the +various specifications implemented by a given Web service represented by the + <tt class="sysout">tModel</tt>. The <tt class="sysout">tModel</tt> provides +a reference system to assist in the discovery of Web services.</p> + </blockquote> +<p>Figure +1. Relationship between data types.</p> +<p> <img src="../images/uddi.gif" alt="Figure 1 illustrates the relationship between the business entity, business service, binding template, and tmodel." /> </p> +<p>Each child structure has a unique +parent structure. This means that each <tt class="sysout">businessService</tt> structure +is owned by a specific <tt class="sysout">businessEntity</tt>. In turn, +each <tt class="sysout">bindingTemplate</tt> is owned by a specific + <tt class="sysout">businessService</tt>. Each <tt class="sysout">bindingTemplate</tt> structure +references to unique instances of <tt class="sysout">tModel</tt> structures; +however, since references can be repeated within several parent structures, +there can be many references to <tt class="sysout">tModels</tt> from +different Entity-Service-Template parents, as seen in Figure 2.</p> +<p>Figure +2. References to tModel.</p> +<p> <img src="../images/uddiref.gif" alt="Figure 2 illustrates the multiple references to a tModel." /> </p> +</div> +<div class="section"><h4 class="sectiontitle">Publisher assertions</h4><p>A publisher assertion is a +way in UDDI to associate businessEntity structures. The publisher assertion +defines a group of businessEntity structures. Many businesses are not effectively +represented by a single businessEntity. A publisher assertion allows for the +association between businessEntity structures. For example, a large company +may have several subsidiaries that have different descriptions but are still +closely coupled and want to make their relationships visible in UDDI registries.</p> +</div> +<div class="section"><h4 class="sectiontitle">Service projections</h4><p>A service projection enables +a business entity to reference a service that was published by another business +entity. By using the businessService structure as a projection to an already +published businessService, businesses can share or reuse services. Service +projections are managed centrally as part of the referencing businessEntity. +This means that any changes made to the businessService by any of the referencing +businessEntity structures are valid for all of the referencing businessEntity +structures.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html new file mode 100644 index 000000000..323b81920 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/taddreg.html @@ -0,0 +1,96 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Adding a Registry to the IBM Web Services Explorer" /> +<meta name="abstract" content="Although the Web Services Explorer comes populated with several registries, you can also add additional registries to your list of favorites." /> +<meta name="description" content="Although the Web Services Explorer comes populated with several registries, you can also add additional registries to your list of favorites." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="taddreg" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Adding a Registry to the Web Services Explorer</title> +</head> +<body id="taddreg"><a name="taddreg"><!-- --></a> + +<h1 class="topictitle1">Adding a Registry to the IBM Web Services Explorer</h1> +<div><p>Although the Web Services Explorer comes populated with several +registries, you can also add additional registries to your list of favorites.</p> +<div class="p"><div class="p">Prerequisites:<ol><li><a href="treg.html">Register with a registry</a></li> +<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> +</ol> +</div> +</div> +<div class="section"><p>When you are ready to publish your business entity and Web service, +add a production registry to the IBM<sup>®</sup> Web Services Explorer. In order to publish +your business entity and Web service to a production registry, you must first +register with the registry. The registry will provide instructions for registering. +For more information on registries, refer to <a href="treg.html">Registering +with a registry</a>.</p> +<p>The UDDI Business Registry is a +set of global replicated registries. For a list of public registries refer +to <a href="http://www.UDDI.org/register.html" target="_blank">www.uddi.org/register.html</a></p> +<p>The IBM UDDI +Business Registry is a public production registry maintained by IBM. For more +information on the IBM UDDI Business Registry refer to <a href="http://uddi.ibm.com" target="_blank">http://uddi.ibm.com</a></p> +</div> +<ol><li><span>To add a Registry to the Web Services Explorer from Favorites, +do the following:</span><ol type="a"><li><span>Click the <span class="uicontrol">Favorites</span> icon <img src="../images/fav.gif" alt="Picture of the Favorites icon." /> in the main toolbar.</span></li> +<li><span>Expand <span class="uicontrol">Favorite UDDI Registries</span>.</span></li> +<li><span>Select a registry then click the <span class="uicontrol">Add to UDDI Page</span> icon + <img src="../images/adduddi.gif" alt="Picture of the Add to UDDI Page icon." /> in the Actions pane.</span></li> +</ol> +</li> +<li><span>To add a Registry to the Web Services Explorer manually, do the +following:</span><ol type="a"><li><span>In the UDDI Navigator pane, click the <span class="uicontrol">UDDI Main</span> node.</span></li> +<li><span>In the Actions pane, enter the Registry name and Inquiry URL +of the registry you want to add.</span></li> +<li><span>Click <span class="uicontrol">Go</span>.</span></li> +</ol> +</li> +</ol> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html new file mode 100644 index 000000000..128f162b8 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html @@ -0,0 +1,91 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Managing publisher assertions" /> +<meta name="abstract" content="A publisher assertion is a way in UDDI to associate businessEntity structures. The publisher assertion defines a group of businessEntity structures. Many businesses are not effectively represented by a single businessEntity. A publisher assertion allows for associations to be formed between several businessEntity structures. For example, a large company may have several subsidiaries that have different descriptions but are still closely coupled and want to make their relationships visible in UDDI registries." /> +<meta name="description" content="A publisher assertion is a way in UDDI to associate businessEntity structures. The publisher assertion defines a group of businessEntity structures. Many businesses are not effectively represented by a single businessEntity. A publisher assertion allows for associations to be formed between several businessEntity structures. For example, a large company may have several subsidiaries that have different descriptions but are still closely coupled and want to make their relationships visible in UDDI registries." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tassert" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Managing publisher assertions</title> +</head> +<body id="tassert"><a name="tassert"><!-- --></a> + +<h1 class="topictitle1">Managing publisher assertions</h1> +<div><p>A publisher assertion is a way in UDDI to associate businessEntity +structures. The publisher assertion defines a group of businessEntity +structures. Many businesses are not effectively represented by a single businessEntity. +A publisher assertion allows for associations to be formed between several +businessEntity structures. For example, a large company may have several subsidiaries +that have different descriptions but are still closely coupled and want to +make their relationships visible in UDDI registries.</p> +<div class="p">Prerequisites:<ol><li><a href="treg.html">Register with a registry</a></li> +<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> +<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> +</ol> +</div> +<div class="section"><p>For more information on publisher assertions, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version +2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p> +<p>To +manage publisher assertions, do the following:</p> +</div> +<ol><li><span>In the Navigator pane, select the business entity for which you +want to manage referenced businesses.</span></li> +<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Publisher +Assertions</span> icon <img src="../images/busasst.gif" alt="Picture of the Manage Publisher Assertions icon." />.</span></li> +<li><span>On the Manage Publisher Assertions page you can add, remove, and +maintain relationships with other business entities.</span></li> +</ol> +<div class="section"><p> <span class="uicontrol">Important:</span> A business entity that is referenced +by another business entity must in turn reference that business entity in +order to make the publisher assertion public. A one-way reference is considered +an incomplete publisher assertion and is visible only to the owner of the +business entity.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html new file mode 100644 index 000000000..cef674238 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbkmrk.html @@ -0,0 +1,83 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tbkmrk" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Adding a registry, business entity, business service, service +interface, WSIL, or WSDL service to Favorites</title> +</head> +<body id="tbkmrk"><a name="tbkmrk"><!-- --></a> + +<h1 class="topictitle1">Adding a registry, business entity, business service, service interface, +WSIL, or WSDL service to Favorites</h1> +<div><div class="p">Prerequisite: <ul><li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> +</ul> +</div> +<div class="section"><p>To add a registry, business entity, Web service, service interface, +WSIL, or WSDL to Favorites using the Web Services Explorer:</p> +</div> +<ol><li><span>Navigate through the registry hierarchy to find the registry, business +entity, Web service, service interface or the WSIL page to find the WSIL or +WSDL service you want to add to Favorites.</span></li> +<li><span>Select the business entity, Web service, service interface, WSIL, +or WSDL service.</span></li> +<li><span>In the Actions icon bar, click the <span class="uicontrol">Add to favorites</span> icon + <img src="../images/addfav.gif" alt="Picture of the Add to favorites icon." />.</span></li> +</ol> +<div class="section"><p>Any favorites that you add are saved by the Web Services Explorer +to </p> +<p> <var class="varname">X</var>:\workspace\.metadata\.plugins\com.ibm.etools.webservice.explorer\favorites.wsil</p> +<p>Where + <var class="varname">X</var> is the directory where your workspace folder is located. +If you are migrating from an earlier version of the product, your favorites +will be automatically migrated to this location.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html new file mode 100644 index 000000000..fe2e2fcc1 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tbusproj.html @@ -0,0 +1,83 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Managing referenced services" /> +<meta name="abstract" content="A service projection enables a business entity to reference a service that was published by another business entity. By using the businessService structure as a projection to an already published businessService, businesses can share or reuse services. Service projections are managed centrally as part of the referencing businessEntity." /> +<meta name="description" content="A service projection enables a business entity to reference a service that was published by another business entity. By using the businessService structure as a projection to an already published businessService, businesses can share or reuse services. Service projections are managed centrally as part of the referencing businessEntity." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tbusproj" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Managing referenced services</title> +</head> +<body id="tbusproj"><a name="tbusproj"><!-- --></a> + +<h1 class="topictitle1">Managing referenced services</h1> +<div><p>A service projection enables a business entity to reference a service +that was published by another business entity. By using the businessService +structure as a projection to an already published businessService, businesses +can share or reuse services. Service projections are managed centrally +as part of the referencing businessEntity.</p> +<div class="p">Prerequisites:<ol><li><a href="treg.html">Register with a registry</a></li> +<li><a href="tstrtexp.html">Launch the Web Services Explorer</a></li> +<li><a href="taddreg.html">Add the registry to the Web Services Explorer</a></li> +</ol> +</div> +<div class="section"><p>For more information on referenced services, refer to the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version +2.0 Programmer's API Specification</a> and the <a href="http://www.uddi.org/specification.html" target="_blank">UDDI Version 2.0 Data Structure Specification</a>.</p> +<p>To +manage referenced services, do the following:</p> +</div> +<ol><li><span>In the Navigator pane, select the business entity for which you +want to manage referenced services.</span></li> +<li><span>In the Actions pane toolbar, click the <span class="uicontrol">Manage Referenced +Services</span> icon <img src="../images/refserv.gif" alt="Picture of the Manage Referenced Services icon." />.</span></li> +<li><span>On the Manage Referenced Services page you can add, remove, and +maintain services that are referenced by the business entity.</span></li> +</ol> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html new file mode 100644 index 000000000..0743579ae --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html @@ -0,0 +1,176 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Discovering Web Services" /> +<meta name="abstract" content="Web services can be located through a public business registry such as the IBM UDDI Business Registry, a private business registry, or a WSIL document. UDDI manages the discovery of Web services by relying on a distributed registry of businesses and their service descriptions implemented in a common XML format." /> +<meta name="description" content="Web services can be located through a public business registry such as the IBM UDDI Business Registry, a private business registry, or a WSIL document. UDDI manages the discovery of Web services by relying on a distributed registry of businesses and their service descriptions implemented in a common XML format." /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tdiscov" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Discovering and importing Web services</title> +</head> +<body id="tdiscov"><a name="tdiscov"><!-- --></a> + +<h1 class="topictitle1">Discovering Web Services</h1> +<div><p>Web services can be located through a public business registry +such as the IBM<sup>®</sup> UDDI +Business Registry, a private business registry, or a WSIL document. UDDI manages +the discovery of Web services by relying on a distributed registry of businesses +and their service descriptions implemented in a common XML format.</p> +<div class="p"><div class="p">Prerequisites:<ol><li><a href="treg.html">Register with a registry</a></li> +<li><a href="tstrtexp.html">Launch the IBM Web Services Explorer</a></li> +<li><a href="taddreg.html">Add the registry to the IBM Web Services Explorer</a></li> +</ol> +</div> +</div> +<div class="section"><p>Web Services Inspection Language (WSIL) is a service discovery +mechanism that is an alternative to UDDI as well as complementary to UDDI. +WSIL allows you to go directly to the service provider and ask for the services +it provides. For more information on the Web Services Inspection Language +specification, refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a>. + For more information on UDDI and the IBM UDDI Business registries, refer to <a href="http://www.ibm.com/services/uddi/index.html" target="_blank">www.ibm.com/services/uddi/index.html</a>.</p> +<p>You +can discover a Web service in two ways using the Web Services Explorer:</p> +</div> +<div class="section"><ul><li> <a href="#tdiscov__discover_from_uddi">Discovering a Web service from +a UDDI registry</a> </li> +<li> <a href="#tdiscov__discover_from_wsil">Discovering a Web service from +a WSIL document</a> </li> +</ul> +</div> +</div> +<div></div><div class="nested1" xml:lang="en-us" id="discover_from_uddi"><a name="discover_from_uddi"><!-- --></a><h2 class="topictitle2"> Discovering a Web Service from a UDDI Registry</h2> +<div><div class="section"><p>The registry contains URL references to Web service WSDL documents. +In order to discover a Web service the URL to the Web service WSDL document +must be resolvable. To locate Web service descriptions:</p> +</div> +<ol><li><span>Launch the Web Services Explorer</span></li> +<li><span>Click <span class="uicontrol">UDDI Main</span>.</span></li> +<li><span>In the Actions pane select a registry from the drop-down list and +click <span class="uicontrol">Go</span>.</span></li> +<li><span>In the Actions pane toolbar click the <strong>Find</strong> icon <img src="../images/find.gif" alt="A picture of the Find icon." />.</span></li> +<li><span>In the Actions pane, enter the name of the query, what you are +searching for, the type of search that you want to perform, and any query +information: </span><ol type="a"><li class="substepexpand"><span> <strong>Search for</strong> This list allows you to search for +businesses, services, or service interfaces. </span> <ul><li> <strong>Businesses</strong> Once you locate a business in the registry, use the +icons in the Action pane toolbar to do the following:<ul><li>View and edit business details</li> +<li>Get the services associated with that business</li> +<li>Publish a service</li> +<li>Manage referenced services</li> +<li>Manage publisher assertions</li> +<li>Add the business to Favorites</li> +<li>Unpublish the business</li> +</ul> +</li> +<li> <strong>Services</strong> Once you locate a service in the registry, use the icons +in the Action pane toolbar to do the following: <ul><li>View and edit service details</li> +<li>Get the business associated with that service</li> +<li>Get the service interfaces associated with that service</li> +<li>Import the service WSDL file to the Eclipse workbench</li> +<li>Import the service WSDL file to the file system</li> +<li>Launch the Web Service wizards</li> +<li>Add the service to Favorites</li> +<li>Unpublish the service</li> +</ul> +</li> +<li> <strong>Service interfaces</strong> Once you locate a service interface in the +registry, use the icons in the Action pane toolbar to do the following: <ul><li>View and edit interface details</li> +<li>Get the services associated with that service interface</li> +<li>Get the businesses associated with that service interface</li> +<li>Import the service interface WSDL file to the Eclipse workbench</li> +<li>Import the service interface WSDL file to the file system</li> +<li>Launch the Web Service wizards</li> +<li>Add the service interface to Favorites</li> +<li>Unpublish the service interface</li> +</ul> +</li> +</ul> +</li> +<li class="substepexpand"><span> <strong>Type of search</strong> These radio buttons allow you to +specify a simple or advanced search, or a search by a Universal Unique Identifier +(UUID). </span> <dl><dt class="dlterm">Simple</dt> +<dd>Type the name of the businesses, services, or service interfaces for which +you are searching. <strong>Note:</strong> The search set size is set to 100 and the +maximum number of returned results is set to 10 by default. If you would +like to override the defaults, use the Advanced search.</dd> +<dt class="dlterm">Advanced </dt> +<dd>Allows you to enter more search options to focus the scope of your search. +Select this option if you would like to search for multiple businesses or +services.</dd> +<dt class="dlterm">UUID </dt> +<dd>Allow you to enter the UUID key. The UUID key is the identifier +that is associated with the published object.</dd> +</dl> +</li> +</ol> +</li> +<li><span>Once you have searched and discovered the business service description +you desired, select the service or the service interface and click the <strong>Import</strong> icon +to: </span><ul><li>import the WSDL document into your Web project</li> +<li>import the WSDL document into the WSDL Explorer for testing</li> +<li>launch the Web Service Skeleton Creation wizard or Web Service Client +wizard directly from the Web Services Explorer.</li> +</ul> +</li> +</ol> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="discover_from_wsil"><a name="discover_from_wsil"><!-- --></a><h2 class="topictitle2"> Discovering a Web Service from a WSIL Document</h2> +<div><div class="section"><p>To locate Web service descriptions:</p> +</div> +<ol><li class="stepexpand"><span>From the Web Services Explorer toolbar, click the <strong>WSIL Page</strong> icon + <img src="../images/wsilview.gif" alt="Picture of the WSIL Page icon." />.</span></li> +<li class="stepexpand"><span>In the Navigator pane, click <strong>WSIL Main</strong>.</span></li> +<li class="stepexpand"><span>In the <strong>URL to document</strong> field of the Actions pane enter +the URL to the WSIL document or HTTP document that contains links to a WSIL +document. Details on how an HTTP file can contain links to WSIL can be found +here: http://www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</span></li> +<li class="stepexpand"><span>Once you have located the WSIL document, use the icons in the Action +pane toolbar to do the following:</span><ul><li>View WSIL document details</li> +<li>List all of the WSDL services associated with that WSIL document</li> +<li>List all of the UDDI services associated with that WSIL document</li> +<li>List all of the UDDI businesses associated with that WSIL document</li> +<li>List all of the WSIL links associated with that WSIL document</li> +<li>Import the WSIL document to the file system</li> +<li>Add the WSIL document to Favorites</li> +</ul> + <strong>Important:</strong> If the IBM Web Services Explorer does not display +the project that you would like to import your WSDL file to, ensure that you +have created the project and/or click the <strong>Refresh</strong> icon.</li> +</ol> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html new file mode 100644 index 000000000..589d3cc39 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html @@ -0,0 +1,87 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Generating a WSIL file" /> +<meta name="abstract" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. WSIL can be generated at any point in the Web service development cycle once the WSDL file for the Web service has been created." /> +<meta name="description" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. WSIL can be generated at any point in the Web service development cycle once the WSDL file for the Web service has been created." /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tgenwsil" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Generating a WSIL file</title> +</head> +<body id="tgenwsil"><a name="tgenwsil"><!-- --></a> + +<h1 class="topictitle1">Generating a WSIL file</h1> +<div><p>Web Services Inspection Language (WSIL) is a service discovery +mechanism that is an alternative to UDDI as well as complementary to UDDI. +WSIL can be generated at any point in the Web service development cycle once +the WSDL file for the Web service has been created.</p> +<div class="p"><strong>Prerequisites:</strong> In order to generate a WSIL file, you need to +know the URL to a WSDL file.</div> +<div class="section"><p>WSIL helps synchronize this process by maintaining references +to WSDL URLs. Web services tools that process WSDL documents - such as the +Web Service Client and Creation wizards - will accept a WSIL document as a +substitute for WSDL. This allows you to create a standardized WSDL reference +(WSIL) document in your project during Web service client generation, then +at a later time easily regenerate the client from that reference document. +No copies of the WSDL or WSDL URLs are required.</p> +<p>You can generate a +WSIL file from a pre-existing WSDL file or during Web service creation or +consumption.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> +</div><div class="nested1" xml:lang="en-us" id="d0e27"><a name="d0e27"><!-- --></a><h2 class="topictitle2">Generating a WSIL file though the import utility</h2> +<div><div class="section"><p>To generate a WSIL file through the import utility:</p> +</div> +<ol><li><span>Optional: Select the WSDL document for which you want to create +a WSIL file.</span></li> +<li><span>From the <strong>File</strong> menu, select <strong>Import</strong> > <strong>WSIL > +Next</strong>. The WSIL Import window opens.</span></li> +<li><span>If you have selected to perform step 1, the WSIL URI field should +be prefilled with the name of your WSDL file, where the extension has been +changed from <tt class="sysout">.wsdl</tt> to <tt class="sysout">.wsil</tt>. +The WSDL section should contain the URLs to the selected WSDL files. You can +also enter additional WSDL URLs. Alternately, you can browse to the location +of a WSIL file, or manually enter the location of the WSIL and WSDL files +in the appropriate locations.</span></li> +<li><span>Click Finish. A WSIL file will be generated in the specified location.</span></li> +</ol> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e62"><a name="d0e62"><!-- --></a><h2 class="topictitle2">Generating a WSIL file through the Web Services Explorer</h2> +<div><div class="section"><p>To generate a WSIL file through the Web Services Explorer:</p> +</div> +<ol><li><span>Open the Web Services Explorer.</span></li> +<li><span>Open the WSDL Explorer by clicking this icon: <img src="../images/wsdlicon.gif" alt="icon used to launch the web services explorer" /></span></li> +<li><span>Open a WSDL file.</span></li> +<li><span>Select the WSDL file that you have opened in the Navigator pane, +and from the available actions, choose to import a WSDL file to the workbench +by clicking this icon: <img src="../images/mptwsdlicon.gif" alt="icon used to import a file" /></span></li> +<li><span>Select <strong>Import as a service reference to a WSIL document</strong>.</span></li> +<li><span>Enter a name for the WSIL file that you want to generate, and click + <strong>Go</strong>.</span></li> +</ol> +</div> +</div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html new file mode 100644 index 000000000..3a4806eda --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpubent.html @@ -0,0 +1,123 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Publishing a business entity" /> +<meta name="abstract" content="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity." /> +<meta name="description" content="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity." /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tpubent" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Publishing a business entity</title> +</head> +<body id="tpubent"><a name="tpubent"><!-- --></a> + +<h1 class="topictitle1">Publishing a business entity</h1> +<div><p>A business entity contains information about the business that +has published a service. Before you can publish a business service, +you must publish a business entity.</p> +<div class="p">Prerequisites:<ol><li><a href="treg.html">Register with a registry</a></li> +<li><a href="tstrtexp.html">Launch the IBM<sup>®</sup> Web Services Explorer</a></li> +<li><a href="taddreg.html">Add the registry to the IBM Web Services Explorer</a></li> +</ol> +</div> +<div class="section"><p>You can publish a business entity using two different publication +formats: simple and advanced.</p> +<blockquote> <p> <span class="uicontrol">Simple</span> Allows +you to enter the minimal amount of information required to publish your business +entity. A simple publish only allows you to specify only one name and +one business description.</p> +<p> <span class="uicontrol">Advanced </span> Allows you +to enter more information about your business entity. An advanced publish +allows you to specify multiple names and descriptions for multi-lingual support.</p> + </blockquote> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> +</div><div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a><h2 class="topictitle2">Publish a business entity using the simple option</h2> +<div><div class="section"><p>To publish a business entity using the simple option:</p> +</div> +<ol><li><span>In the Web Services Explorer, select UDDI Main and select the registry +to which you want to publish the business entity.</span></li> +<li><span>In the Navigator pane, select the business entity for which +you want to publish the business service.</span></li> +<li><span>In the Actions pane toolbar, click the <strong>Publish</strong> icon <img src="../images/publish2.gif" alt="Picture of the Publish icon." />.</span></li> +<li><span>Select the <strong>Simple</strong> radio button.</span></li> +<li><span>Enter the publish URL, your user ID, password, WSDL URL, business +name, and business description in the respective fields.</span></li> +<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> +</ol> +<div class="section"><p>The IBM Web +Services Explorer is automatically updated with your published Web service. +The registry contains pointers to the URL of the WSDL service document of +the Web service. Businesses can now discover and integrate with your Web service.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a><h2 class="topictitle2">Publish a business entity using the advanced option</h2> +<div><div class="section"><p>To publish a business entity using the advanced option:</p> +</div> +<ol><li><span>In the Web Services Explorer Navigator pane, select the business +entity for which you want to publish the business service.</span></li> +<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon + <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> +<li><span>Select the <strong>Advanced</strong> radio button.</span></li> +<li><span>Enter the publish URL, your user ID, password, and WSDL URL in +the respective fields.</span></li> +<li><span>Click <strong>Add</strong> to create business names.</span></li> +<li><span>Click <strong>Add</strong> to create business descriptions.</span></li> +<li><span>Click <span class="uicontrol">Add</span> to create an identifier. For example, +an identifier for your business entity may be your business phone number. +The key name would be "Phone Number" and the key value would be your business +telephone number. </span></li> +<li><span>Click <strong>Add</strong> to create categories. Enter your business categories. +Select a category type from the drop down list. Click <strong>Browse</strong> to open +the Categories pane. Navigate through the hierarchical taxonomy and select +the appropriate classification for your business service, then exit the Categories +pane.</span></li> +<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> +</ol> +<div class="section"><p>The Web Services Explorer is automatically updated with your published +Web service. The registry contains pointers to the URL of the WSDL service +document of the Web service. Businesses can now discover and integrate with +your Web service.</p> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html new file mode 100644 index 000000000..f93733b95 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tpublish.html @@ -0,0 +1,137 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Publishing a Web service" /> +<meta name="abstract" content="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides." /> +<meta name="description" content="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides." /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tpublish" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Publishing a Web service</title> +</head> +<body id="tpublish"><a name="tpublish"><!-- --></a> + +<h1 class="topictitle1">Publishing a Web service</h1> +<div><p>The Web service, also known as the business service, describes +a Web service's endpoint and where its WSDL file resides. The WSDL file lists +the operations that service provides.</p> +<div class="p">Prerequisites:<ol><li> <a href="treg.html">Register with a registry</a>.</li> +<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li> +<li> <a href="taddreg.html">Add the registry to the Web Services Explorer</a>.</li> +<li>Create a Web service.</li> +<li>Deploy the Web service.</li> +<li> <a href="tpubent.html">Publish a Business Entity</a>.</li> +</ol> +</div> +<div class="section"><p>You can publish a business service using two different publication +formats: simple and advanced.</p> +</div> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../ref/ruddi.html">Data structure types (UDDI registry)</a></strong><br /> +Once you have registered and logged in to the UDDI registry that +you want to use, you can register your Web service. Registration of +a service involves four core data structure types: business information, service +information, binding information, and information describing the specifications +for services. The relationship between these data types is described in Figure +1.</li> +</ul> + +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> +</div><div class="nested1" xml:lang="en-us" id="d0e74"><a name="d0e74"><!-- --></a><h2 class="topictitle2">Publish a business service using the simple option</h2> +<div><div class="section"><p>To publish a Web service using the simple option:</p> +</div> +<ol><li><span>In the Web Services Explorer Navigator pane, select the business +entity for which you want to publish the business service.</span></li> +<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon + <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> +<li><span>Select the <strong>Simple</strong> radio button.</span></li> +<li><span>Enter the publish URL, your user ID, password, WSDL URL, business +name, and business description in the respective fields.</span></li> +<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> +</ol> +<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document, +since the service element is the basis for the Business Service that you will +publish. You cannot publish a Business Service using a WSDL document that +does not have service elements.</p> +<p>The Web Services Explorer is automatically +updated with your published Web service. The registry contains pointers to +the URL of the WSDL service document of the Web service. Businesses can now +discover and integrate with your Web service.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e113"><a name="d0e113"><!-- --></a><h2 class="topictitle2">Publish a business service using the advanced option</h2> +<div><div class="section"><p>To publish a Web service using the advanced option:</p> +</div> +<ol><li><span>In the Web Services Explorer Navigator pane, select the business +entity for which you want to publish the business service.</span></li> +<li><span>In the Actions pane toolbar, click the <strong>Publish Service</strong> icon + <img src="../images/pubserv.gif" alt="Picture of the Publish Service icon." />.</span></li> +<li><span>Select the <strong>Advanced</strong> radio button.</span></li> +<li><span>Enter the publish URL, your user ID, password, and WSDL URL in +the respective fields.</span></li> +<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate the +service with a business entity.</span></li> +<li><span>Click <strong>Get</strong> or <span class="uicontrol">Find</span> to associate a +specific service interface with the service.</span></li> +<li><span>Click <strong>Add</strong> to create business service names.</span></li> +<li><span>Click <strong>Add</strong> to create business service descriptions.</span></li> +<li><span>Click <strong>Add</strong> to create categories. Enter your business service +categories. Select a category type from the drop down list. Click <strong>Browse</strong> to +open the Categories pane. Navigate through the hierarchical taxonomy +and select the appropriate classification for your business service, then +exit the Categories pane.</span></li> +<li><span>Click <strong>Go</strong> to publish your business entity.</span></li> +</ol> +<div class="section"><p> <strong>Important:</strong> Ensure that you select the service document, +since the service element is the basis for the Business Service that you will +publish. You cannot publish a Business Service using a WSDL document +that does not have service elements.</p> +<p>The Web Services Explorer +is automatically updated with your published Web service. The registry contains +pointers to the URL of the WSDL service document of the Web service. Businesses +can now discover and integrate with your Web service.</p> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html new file mode 100644 index 000000000..6abe9f544 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/treg.html @@ -0,0 +1,98 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Registering with a UDDI registry" /> +<meta name="abstract" content="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use." /> +<meta name="description" content="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="treg" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Registering with a UDDI Registry</title> +</head> +<body id="treg"><a name="treg"><!-- --></a> + +<h1 class="topictitle1">Registering with a UDDI registry</h1> +<div><p>In order to publish your business entity and Web service to a UDDI +registry, you must first register with the registry that you want to use.</p> +<div class="section"><p>There are many different public and private registries with which +you can register. For a list of public registries refer to <a href="http://www.uddi.org/register.html" target="_blank">www.uddi.org/register.html</a> Since each registry is +different, the registry provider will give you instructions for registering.</p> +<p>The +following registries are automatically added to Favorites:</p> +<ul><li>IBM<sup>®</sup> UDDI +Registry</li> +<li>IBM UDDI +Test Registry</li> +<li>Microsoft<sup>®</sup> UDDI +Registry</li> +<li>Microsoft UDDI +Test Registry</li> +<li>SAP UDDI Registry</li> +<li>SAP UDDI Test Registry</li> +<li>XMethods Registry</li> +<li>NTT Communications Registry</li> +</ul> +<p>You can use any of these registries by selecting the Favorites icon +in the Web Services Explorer toolbar. All of these registries are based on +the UDDI Business Registry Version 2. Go to the following URL to obtain a +user ID and password for the IBM UDDI registry: <a href="http://www-3.ibm.com/services/uddi/" target="_blank">www.ibm.com/services/uddi/</a>. +The details page of each registry will have registration instructions.</p> +<p>The IBM UDDI +Test Registry allows you to develop your Web service and experience the UDDI +registration process without placing your Web service in an official registry. +Use the IBM UDDI +Test Registry or a private registry to experiment with UDDI, and to test and +validate your Web service. The public production registries are listed +under Favorites. The Web Services Explorer does not preload any registries +by default. You can preload registries from the favorites section of +the Web Services Explorer or by using the Unit Test UDDI wizard. You can also +preload and configure private registries using the Unit Test UDDI wizard. +On the Open Registry page of the Web Services Explorer, you can select from +public registries and registries listed in your favorites to automatically +fill in the information required to open a particular registry.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html new file mode 100644 index 000000000..31ffa4740 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tsampapp.html @@ -0,0 +1,165 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Generating a Java client proxy and a sample application from a WSDL document using the IBM SOAP run-time environment" /> +<meta name="abstract" content="The Web Service Client wizard assists you in generating a Java bean proxy and a sample application. The sample Web application demonstrates how to code a proxy file." /> +<meta name="description" content="The Web Service Client wizard assists you in generating a Java bean proxy and a sample application. The sample Web application demonstrates how to code a proxy file." /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.doc/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.doc/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.doc/ref/rdepprop.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.doc/ref/rmapprop.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.doc/ref/rwsdl.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tsampapp" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Generating a Java client proxy and a sample application from +a WSDL document</title> +</head> +<body id="tsampapp"><a name="tsampapp"><!-- --></a> + +<h1 class="topictitle1">Generating a Java client proxy and a sample application +from a WSDL document using the IBM SOAP run-time environment</h1> +<div><p>The Web Service Client wizard assists you in generating a Java™ bean +proxy and a sample application. The sample Web application demonstrates +how to code a proxy file.</p> +<div class="p">Prerequisites:<ol><li id="tsampapp__createtomcatlinks"><a name="tsampapp__createtomcatlinks"><!-- --></a>If you are using the Apache Jakarta Tomcat servlet +container as your server, you must install it, configure an instance of it, +and create a Web project targeted to it as described in <a href="../../com.ibm.etools.webservice.axis.creation.ui.doc/tasks/ttomcatserv.html">Creating a WebSphere<sup>®</sup> Server and Web project</a></li> +<li id="tsampapp__prereqcreatewsprojs"><a name="tsampapp__prereqcreatewsprojs"><!-- --></a>If you are using a WebSphere server, create a dynamic +Web project targeted to the appropriate server as described in <a href="../../com.ibm.etools.webservice.doc/tasks/twasserv.html">Creating a WebSphere Server and Web project</a>.</li> +<li>Discover and import a WSDL document into the Web project. You can only +use a WSDL file that contains a service element.</li> +</ol> +</div> +<div class="section"><p>To generate a Java client proxy and a sample application +from a discovered WSDL document:</p> +</div> +<ol><li><span>Switch to the J2EE perspective (<span class="uicontrol">Window > Open Perspective +> J2EE</span>).</span></li> +<li><span>In the Project Explorer view, select the Web project in which you +want to generate a sample application.</span></li> +<li><span>Click <span class="uicontrol">File > New > Other</span>. Select <span class="uicontrol">Web +Services</span> in order to display the various Web service wizards. +Select the <span class="uicontrol">Web Service Client</span> wizard. Click <span class="uicontrol">Next</span>.</span></li> +<li><span>Web Services panel: Select the type of proxy to be generated, and +whether or not it will be tested.</span></li> +<li><span>Client Environment Configuration page: Select the run-time environment +and the server for your Web service client.</span><ol type="a"><li class="substepexpand"><span>Click <span class="uicontrol">Explore Options</span> and select the IBM<sup>®</sup> SOAP +run-time environment and select the server on which you want to run your Web +service client.</span> If you want to use the Apache Axis 1.0 run-time +environment or the IBM WebSphere run-time environments, refer to the appropriate +task. </li> +<li class="substepexpand"><span>Select the type and name of project in which you want the Web +service client created.</span> <ul><li> If you enter the name of an existing project, the project type field +must match that of the existing project. Ensure that the project selected +as the Client Web Project is different from the Service Web Project, or the +service will be overwritten by the client's generated artifacts.</li> +<li>If you enter a name of a project that does not already exist, the wizard +will create the project for you.</li> +<li>Note that the only project type supported for Axis and SOAP run-time clients +is a Web project. If you want the client to be created in a Java, EJB, +or Application Client project, you must select the WebSphere run-time environment for +your client.</li> +</ul> +</li> +<li class="substepexpand"><span> Select an existing EAR or enter a unique name to associate +the Web service client with a different EAR than the Web service EAR. <strong>Note:</strong> Selecting +different EARs for the Web service and Web service client can reduce the chance +of encountering run time errors, but will use more system resources.</span></li> +</ol> +</li> +<li><span>Web Service Selection panel: Enter the URI to the WSDL, WSIL, or +HTML file that will be used to generate the Java bean. You can optionally generate a +WSIL file from this file as well.</span></li> +<li><span>Web Service Binding Proxy Generation panel: Select the binding +and proxy options.</span></li> +<li><span>Web Service Proxy Test panel: Select the test facility that you +will use to test the proxy, and the methods that you want included in the +proxy. Note that the Universal Test Client (UTC) is only compatible with Web +service clients deployed on WebSphere servers. Click <span class="uicontrol">Finish</span></span></li> +</ol> +<div class="section"><p>Notes<sup>®</sup>:</p> +<ul><li>When defining custom mappings ensure the bean, serializer, and deserializer +classes are on the build path of the Web project, otherwise the wizard will +not accept their class names.</li> +<li>Indexed properties that result from WSDL XSD complex Types involving more +than one occurrence of DOM Elements are not supported by the sample. SOAP +encoded methods using indexed properties are not available for invocation. +Literal XML encoded methods using indexed properties are available for invocation; +however, the inputs and outputs must be specified as Literal XML.</li> +<li>Only the following types are supported by the sample application: <ul><li>Members that use getters and setters.</li> +<li>All primitive types and corresponding Java types.</li> +<li>Java type +String.</li> +<li>org.w3c.dom.Element</li> +<li>Java beans.</li> +<li>BigDecimal, GregorianCalendar, and Date.</li> +</ul> +</li> +</ul> +<p><strong>Important:</strong> It is recommended that you select the service WSDL +document rather than the binding WSDL document in order to generate a client +proxy that contains the complete endpoint information. The service element +is the basis for the Business Service that you will publish. You cannot publish +a Business Service using a WSDL document that does not have service elements. +If you generate a proxy from a WSDL binding document, you must call the <tt class="sysout">setEndPoint()</tt> method +to set an endpoint URL before you call any other method in the proxy. +The proxy generated from a WSDL binding document is not automatically equipped +with an endpoint URL.</p> +<p>The generated Java bean proxy provides a remote procedure +call interface to the Web service. The sample Web application demonstrates +how to code the proxy file.</p> +<p>Once you have generated your Java client +proxy, you may test the methods of the Web service through the proxy using +Web Services sample JSPs or the Universal test client.</p> +<ul><li>If you have selected to test the generated proxy using Web service JSPs, +the proxy is launched in a Web browser at the following URL:<samp class="codeph"> http://localhost: <var class="varname">port</var>/WebProjectClient/sample/ <var class="varname">WebService</var>/TestClient.jsp </samp> You can use this sample application to test the +Web service by selecting a method, entering a value for the method, and clicking + <span class="uicontrol">Invoke</span>. The result of the method will display in the +results pane.</li> +<li>If you have selected to test the generated proxy using the Universal Test +Client, it will be launched in a browser window at the following URL:<samp class="codeph"> <tt class="sysout">http://localhost:9080/UTC/preload?object=proxy.soap. <var class="varname">ProxyName</var>Proxy</tt> </samp> In the Reference pane, +under Object References, expand the proxy to display the methods of the Web +service. Click the method you want to test, enter a value in the Parameters +pane, and click <span class="uicontrol">Invoke</span>. The result will be generated +below.</li> +</ul> +<p>For more information on creating a Web project, refer to the Web application +development documentation.</p> +</div> +</div> +<div> +<div class="linklist"><strong>Collected links</strong><br /> + +<div><a href="../../com.ibm.etools.webservice.doc/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../com.ibm.etools.webservice.doc/concepts/cws.html">Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html"> Developing Web services</a></div> +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../../com.ibm.etools.webservice.doc/ref/rdepprop.html">Deployment properties</a></div> +<div><a href="../../com.ibm.etools.webservice.doc/ref/rmapprop.html">Mapping properties</a></div> +<div><a href="../../com.ibm.etools.webservice.doc/ref/rwsdl.html">WSDL documents</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html new file mode 100644 index 000000000..fd227dc48 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tstrtexp.html @@ -0,0 +1,133 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Launching the Web Services Explorer" /> +<meta name="abstract" content="The Web services tools allows you to launch the Web Services Explorer in several ways." /> +<meta name="description" content="The Web services tools allows you to launch the Web Services Explorer in several ways." /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tstrtexp" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Launching the Web Services Explorer</title> +</head> +<body id="tstrtexp"><a name="tstrtexp"><!-- --></a> + +<h1 class="topictitle1">Launching the Web Services Explorer</h1> +<div><p>The Web services tools allows you to launch the Web Services Explorer +in several ways.</p> +<div class="section"><ul><li>From the main toolbar in the J2EE perspective.</li> +<li>By using the Web service wizards.</li> +<li>By using the Import wizard.</li> +<li>By using the Export wizard.</li> +<li>From the Run menu in the J2EE perspective.</li> +<li>From a WSDL file.</li> +</ul> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> +</div><div class="nested1" xml:lang="en-us" id="d0e38"><a name="d0e38"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer from the main toolbar</h2> +<div><div class="section"><p>To launch the Web Services Explorer from the main toolbar, ensure +that you are in the J2EE perspective and click the <strong>Launch the Web Services +Explorer</strong> icon <img src="../images/uddiview.gif" alt="Picture of the Launch Web Services Explorer icon." />. The Web Services Explorer opens without +any registries displayed in the Navigator pane. You can now <a href="taddreg.html">add +a registry</a> to the Web Services Explorer.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e50"><a name="d0e50"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer using the Web Services Wizard</h2> +<div><div class="section"><p>To launch the Web Services Explorer from the Web Services Wizard, +select the <strong>Test the Web Service</strong> check box in the first page of the +Web Services Wizard. Proceed with the wizard and then in the Web Service Test +Page, choose <strong>Web Services Explorer</strong> as the test facility and click +on the <strong>Launch</strong> button. If you launch the Web Services Explorer using +this method, it will automatically preload the WSDL (and its child nodes) +in the WSDL page.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e63"><a name="d0e63"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer using the Import wizard</h2> +<div><div class="section"><p>To launch the Web Services Explorer using the Import wizard, do +the following:</p> +</div> +<ol><li><span>From the main menu, click <strong>File > Import</strong>. The Import wizard +opens.</span></li> +<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web service +import wizard opens.</span></li> +<li><span>Click <strong>Finish</strong>.</span></li> +</ol> +<div class="section"><p>The Web Services Explorer opens. If you selected a registry on +the Web Service Publication page of the Web service Import wizard, you will +see the registry displayed in the Navigator pane.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e95"><a name="d0e95"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer using the Export wizard</h2> +<div><div class="section"><p>To launch the Web Services Explorer using the Export wizard, do +the following:</p> +</div> +<ol><li><span>From the main menu, click <strong>File > Export</strong>. The Export wizard +opens.</span></li> +<li><span>Select <strong>Web Service</strong> and click <strong>Next</strong>. The Web Service +Export wizard opens.</span></li> +<li><span>Click <strong>Finish</strong>. The Web Services Explorer opens.</span></li> +</ol> +<div class="section"><p>The Web Services Explorer opens. If you selected a registry +on the Web Service Publication page of the Web Service Export wizard, you +will see the registry displayed in the Navigator pane.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e127"><a name="d0e127"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer from the Run menu</h2> +<div><div class="section"><p>To launch the Web Services Explorer from the main menu, ensure +that you are in the J2EE perspective and click <strong>Run > Launch the Web Services +Explorer</strong>. The Import wizard opens. The Web Services Explorer opens. +The Web Services Explorer opens without any registries displayed in the Navigator +pane.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e134"><a name="d0e134"><!-- --></a><h2 class="topictitle2">Launching the Web Services Explorer from a WSDL file</h2> +<div><div class="section"><p>To launch the Web Services Explorer from a WSDL file, +select the WSDL file and right-click and choose <strong>Web Services > Test with +Web Services Explorer</strong> or <strong>Publish WSDL file</strong>. The Web Services +Explorer opens. The <strong>Test with Web Services Explorer</strong> action will preload +the WSDL in the WSDL page.</p> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="treg.html" title="In order to publish your business entity and Web service to a UDDI registry, you must first register with the registry that you want to use.">Registering with a UDDI registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html new file mode 100644 index 000000000..3dff1ee3c --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html @@ -0,0 +1,108 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Testing WSDL documents and Web services using the WSDL Explorer" /> +<meta name="abstract" content="WSDL documents allow developers to expose their applications as network-accessible services on the Internet. Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes. The Web Services Explorer allows you to explore, import, and test WSDL documents." /> +<meta name="description" content="WSDL documents allow developers to expose their applications as network-accessible services on the Internet. Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes. The Web Services Explorer allows you to explore, import, and test WSDL documents." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="ttestwsdl" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Using the WSDL Explorer</title> +</head> +<body id="ttestwsdl"><a name="ttestwsdl"><!-- --></a> + +<h1 class="topictitle1">Testing WSDL documents and Web services using the WSDL Explorer</h1> +<div><p>WSDL documents allow developers to expose their applications as +network-accessible services on the Internet. Through UDDI and WSIL, other +applications can discover WSDL documents and bind with them to execute transactions +or perform other business processes. The Web Services Explorer allows you +to explore, import, and test WSDL documents.</p> +<div class="p">Prerequisites: To use the WSDL Explorer:<ul><li>You must have a valid URL for a WSDL document.</li> +<li>You must launch the Web Services Explorer: <a href="tstrtexp.html">Launch +the Web Services Explorer</a></li> +</ul> +</div> +<div class="section"><p>The WSDL Explorer allows you to explore, and test WSDL documents. +For more information on exploring WSDL documents using the WSDL Explorer, +refer to <a href="twsdlexp.html">Using the WSDL Explorer</a> .</p> +<p>To +test a Web service using the WSDL Explorer:</p> +</div> +<ol><li class="stepexpand"><span>To launch the WSDL Explorer, complete the following steps:</span><ol type="a"><li><span>In the Web Services Explorer, switch to the WSDL Explorer by +clicking the icon in the upper right-hand corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />. </span></li> +</ol> +</li> +<li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing +WSDL URL in the right-hand pane, and click <strong>Go</strong>. For this example the +WSDL being used is a Web Service which returns a temperature for any entered +zip code. <br /><img src="../images/wsdlexp.gif" alt="Screen capture of the WSDL Main pane of the Web Services Explorer" /><br /> The following nodes +will be added to the WSDL tree: </span> <ul><li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li> +<li>The service node (which represents a service element within the WSDL file): + <img src="../images/servnode.gif" alt="Service node icon" /></li> +<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li> +<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li> +</ul> +</li> +<li class="stepexpand"><span>In the WSDL Binding Details pane, click the operation (in this +example the <tt class="sysout">getTemp</tt> operation) to display: </span> <ul><li>A drop-down list with the endpoints available for this operation</li> +<li>Fields for each of the parameters of this operation (in this example the + <tt class="sysout">zipcode</tt> parameter) and the type of information +the parameter is looking for (in this example <tt class="sysout">zipcode</tt> is +requesting a string). <br /><img src="../images/wsdlop.gif" alt="Invoke a WSDL Operation pane of the Web Services Explorer" /><br /> The Form view allows +you to enter the parameters for the Web service operation call. Parameters +names are displayed as links whose action is to display a dialog describing +embedded XML Schema Definition Language (XSD) information. More information +about XSD can be found here: <a href="http://www.eclipse.org/xsd/">http://www.eclipse.org/xsd/</a> + <br /><img src="../images/scenario7.gif" alt="Screen capture of the XSD Information Dialog" /><br /> </li> +</ul> +</li> +<li class="stepexpand"><span>Enter your string and click <strong>Go</strong>. The result is returned +in the Status pane. <br /><img src="../images/wsdlopret.gif" alt="Screen capture of an invoked WSDL operation showing the result in the Status pane" /><br /> </span></li> +<li class="stepexpand"><span>If you are using SOAP as your binding method, clicking Source or +Form in the upper right-hand corner will toggle the display between the Form +view (shown above) and the Source view, which displays the SOAP message in +the XML format. You can also enter the same information as in the form, only +in XML format (this is suggested for advanced users only). The Explorer does +validate the XML if you modify it, but not the parameter values you enter. + <br /><img src="../images/wsdlopretx.gif" alt="Source view of the Invoke a WSDL Operation pane." /><br /></span></li> +<li class="stepexpand"><span> If you are using SOAP as your binding type, you will also +have the option of toggling the Status pane between the Source and Form views. +The Source view shows the SOAP request and response envelopes, including the +parameters you have entered to test the service and the returned value. <br /><img src="../images/wsdlstatx.gif" alt="Screen capture of the source view of the SOAP request and response envelopes" /><br /> </span></li> +</ol> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html new file mode 100644 index 000000000..48bd735cc --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html @@ -0,0 +1,219 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Publishing Web services and business entities" /> +<meta name="abstract" content="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes." /> +<meta name="description" content="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="twsdlexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/taddreg.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpubent.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpublish.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tupdate.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tunpub.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tbusproj.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tassert.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tbkmrk.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/treg.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/taddreg.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpubent.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tpublish.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tupdate.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tunpub.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tbusproj.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tassert.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tbkmrk.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tgenwsil.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tuddiexp" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Publishing Web services and business entities with the Web Services +Explorer</title> +</head> +<body id="tuddiexp"><a name="tuddiexp"><!-- --></a> + +<h1 class="topictitle1">Publishing Web services and business entities</h1> +<div><p>Through UDDI and WSIL, other applications can discover WSDL documents +and bind with them to execute transactions or perform other business processes. </p> +<div class="section"><p>UDDI enables the discovery of Web services by providing a distributed +registry of businesses and their service descriptions, implemented in a common +XML format. In order for a service requestor to discover a service, +a service provider must first publish a business entity and at least one business +service, and service interface in a UDDI registry. The Web Services +Explorer is a Web application that supports the publication, discovery, and +maintenance of business entities, business services, and service interfaces.</p> +<p>WSIL +enables the discovery of Web services by defining a distributed service discovery +method that supplies references to service descriptions at the service provider's +point-of-offering, by specifying how to inspect a Web site for available Web +services. The WSIL specification defines the locations on a Web site +where you can look for Web service descriptions. Since WSIL focuses on +distributed service discovery, the WSIL specification complements UDDI by +facilitating the discovery of services that are available on Web sites +that may not be listed yet in a UDDI registry. The Web Services Explorer allows +you to generate and explore WSIL documents.</p> +<p>The favorites page of the +Web Services Explorer allows you to store the location of UDDI registries, +business entities, Web services, service interfaces, as well as WSIL and WSDL +documents.</p> +<p>Use the Web Services Explorer to do any of the following +tasks:</p> +<ul><li> <a href="taddreg.html">Add a registry to the Web Services Explorer</a> </li> +<li> <a href="tbkmrk.html">Adding a registry, business entity, business +service, service interface, WSIL, or WSDL service to Favorites</a> </li> +<li> <a href="tdiscov.html">Discover a Web service</a> </li> +<li> <a href="tpubent.html">Publish a business entity to a registry</a> </li> +<li> <a href="tpublish.html">Publish a business service to a registry</a> </li> +<li> <a href="tunpub.html">Remove a business entity, business service, +or service interface from a registry</a> </li> +<li> <a href="tupdate.html">Update a business entity, business service, +or service interface</a> </li> +<li> <a href="tbusproj.html">Manage referenced services</a> </li> +<li> <a href="tassert.html">Manage publisher assertions</a> </li> +</ul> +<p>Prerequisites:</p> +</div> +<ol><li class="stepexpand"><span>Before you can use the Web Services Explorer to perform any of +these functions, you must <a href="treg.html">register with a public registry</a> or <a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html"> configure a private registry</a>. There are many different +registries with which you can register.</span> </li> +<li class="stepexpand"><span>Ensure that you are using a supported Web browser.</span> The +following Web browsers and versions are supported:<ul><li>Internet Explorer: 6.0 and up</li> +<li>Mozilla: 1.2.1 and up</li> +</ul> +</li> +<li class="stepexpand"><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span></li> +</ol> +<div class="section"><div class="p"><strong>Known limitations of the Web Services Explorer:</strong><ul><li>The taxonomy categories in the Web Services Explorer are not translated +since they must match those in the standards adhered to by UDDI (ISO, UNSPSC +7.3, NAICS).</li> +<li>The Web Services Explorer will launch without the browser toolbar which +shows, amongst other things, the URL to the Web application. This URL should +only be used by users with accessibility needs. The URL to the Web Services +Explorer Web application can be obtained through the following steps:<ol><li>From the Window menu, select Preferences.</li> +<li>In the Preferences dialog, select <span class="uicontrol">Web Browser</span> in +the left pane.</li> +<li>On the right, select <span class="uicontrol">Use external Web Browser</span>.</li> +<li>In the <span class="uicontrol">Location: text</span> field, browse or type in +the full path of the Internet Explorer executable. (for example, C:\Program +Files\Internet Explorer\iexplore.exe).</li> +<li>Click <span class="uicontrol">Apply</span> followed by <span class="uicontrol">OK</span>.</li> +</ol> + Note that this preference will now apply to any browser windows that +are launched by the user or by the tools themselves (such as the Universal +Test Client). The Web Services Explorer will now launch in an external browser +and its URL should be in the Address field. This can then be pasted or opened +using am accessibility assisting browser such as IBM<sup>®</sup> Home Page Reader.</li> +<li>When performing an advanced find or publish in the UDDI page of the Web +Services Explorer, the items in the drop down list for picking a language +in conjunction with a name or description is sorted according to the operating +system's locale settings. On Windows<sup>®</sup>, this order may be managed through +the Control Panel. To do this:<ol><li>Open the Control Panel.</li> +<li>Launch the Regional Options control panel applet.</li> +<li>In the General tab of the resulting dialog, there may be a "Sorting order" +drop-down list. If so, pick a sorting order and then click <span class="uicontrol">Apply</span> followed +by <span class="uicontrol">OK</span>.</li> +<li>In the Web Services Explorer, the new sorting order comes into effect +once the page reloads. This can be accomplished by pressing the back arrow +followed by the forward arrow in the main toolbar.</li> +</ol> +Note: The instructions above apply to Windows 2000. On Windows XP, +the tab mentioned in step 3 is called "Regional Options". Beside the language +drop-down, there is a <span class="uicontrol">Customize</span> button. When this is +clicked, a new dialog appears. A sorting tab will allow users to pick the +sorting method if applicable.</li> +</ul> +</div> +</div> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../tasks/tstrtexp.html">Launching the Web Services Explorer</a></strong><br /> +The Web services tools allows you to launch the Web Services Explorer +in several ways.</li> +<li class="ulchildlink"><strong><a href="../tasks/treg.html">Registering with a UDDI registry</a></strong><br /> +In order to publish your business entity and Web service to a UDDI +registry, you must first register with the registry that you want to use.</li> +<li class="ulchildlink"><strong><a href="../tasks/taddreg.html">Adding a Registry to the IBM Web Services Explorer</a></strong><br /> +Although the Web Services Explorer comes populated with several +registries, you can also add additional registries to your list of favorites.</li> +<li class="ulchildlink"><strong><a href="../tasks/tpubent.html">Publishing a business entity</a></strong><br /> +A business entity contains information about the business that +has published a service. Before you can publish a business service, +you must publish a business entity.</li> +<li class="ulchildlink"><strong><a href="../tasks/tpublish.html">Publishing a Web service</a></strong><br /> +The Web service, also known as the business service, describes +a Web service's endpoint and where its WSDL file resides. The WSDL file lists +the operations that service provides.</li> +<li class="ulchildlink"><strong><a href="../tasks/tupdate.html">Updating a business entity, Web service, or service interface</a></strong><br /> +After you have published a business entity, Web service, or service +interface, you can update it through the Web Services Explorer.</li> +<li class="ulchildlink"><strong><a href="../tasks/tunpub.html">Removing a business entity, Web service, or service interface from a registry</a></strong><br /> +After you have published a business entity, Web service, or service +interface, you can remove or unpublish it through the Web Services Explorer.</li> +<li class="ulchildlink"><strong><a href="../tasks/tbusproj.html">Managing referenced services</a></strong><br /> +A service projection enables a business entity to reference a service +that was published by another business entity. By using the businessService +structure as a projection to an already published businessService, businesses +can share or reuse services. Service projections are managed centrally +as part of the referencing businessEntity.</li> +<li class="ulchildlink"><strong><a href="../tasks/tassert.html">Managing publisher assertions</a></strong><br /> +A publisher assertion is a way in UDDI to associate businessEntity +structures. The publisher assertion defines a group of businessEntity +structures. Many businesses are not effectively represented by a single businessEntity. +A publisher assertion allows for associations to be formed between several +businessEntity structures. For example, a large company may have several subsidiaries +that have different descriptions but are still closely coupled and want to +make their relationships visible in UDDI registries.</li> +<li class="ulchildlink"><strong><a href="../tasks/tbkmrk.html">Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites</a></strong><br /> +</li> +<li class="ulchildlink"><strong><a href="../tasks/tgenwsil.html">Generating a WSIL file</a></strong><br /> +Web Services Inspection Language (WSIL) is a service discovery +mechanism that is an alternative to UDDI as well as complementary to UDDI. +WSIL can be generated at any point in the Web service development cycle once +the WSDL file for the Web service has been created.</li> +</ul> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="twsdlexp.html">Exploring WSDL using the WSDL Explorer</a></div> +<div><a href="../../org.eclipse.jst.ws.uddi.registry.doc.user/tasks/tuddiwiz.html">Configure a private registry</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html new file mode 100644 index 000000000..d8b845ae1 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tunpub.html @@ -0,0 +1,90 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Removing a business entity, Web service, or service interface from a registry" /> +<meta name="abstract" content="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer." /> +<meta name="description" content="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tpubent.html" /> +<meta name="DC.Relation" scheme="URI" content="tpublish.html" /> +<meta name="DC.Relation" scheme="URI" content="tunpub.html" /> +<meta name="DC.Relation" scheme="URI" content="tupdate.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tunpub" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Removing a business entity, Web service, or service interface +from a registry</title> +</head> +<body id="tunpub"><a name="tunpub"><!-- --></a> + +<h1 class="topictitle1">Removing a business entity, Web service, or service interface from +a registry</h1> +<div><p>After you have published a business entity, Web service, or service +interface, you can remove or unpublish it through the Web Services Explorer.</p> +<div class="p">Prerequisites:<ol><li> <a href="tpubent.html">Publish a business entity</a>.</li> +<li> <a href="tpublish.html">Publish a Web service</a>.</li> +<li> <a href="tpublish.html">Publish a service interface</a>.</li> +<li> <a href="tstrtexp.html">Launch the IBM<sup>®</sup> Web Services Explorer</a>.</li> +</ol> +</div> +<div class="section">To unpublish a business entity, Web service, or service interface +using the Web Services Explorer:</div> +<ol><li><span>Navigate through the registry hierarchy to find the business entity, +Web service, or service interface you want to unpublish. Select the business +entity, Web service, or service interface.</span></li> +<li><span>In the Actions icon bar, click the <span class="uicontrol">Unpublish</span> icon.</span></li> +<li><span>Enter the publish URL, your user ID, and password, if necessary, +then click <span class="uicontrol">Go</span>.</span></li> +</ol> +<div class="section"><p>The business entity, Web service, or service interface is removed +from the registry and the Web Services Explorer is automatically updated with +your change.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div> +<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div> +<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div> +<div><a href="tupdate.html" title="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer.">Updating a business entity, Web service, or service interface</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html new file mode 100644 index 000000000..f4a9c456e --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tupdate.html @@ -0,0 +1,86 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Updating a business entity, Web service, or service interface" /> +<meta name="abstract" content="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer." /> +<meta name="description" content="After you have published a business entity, Web service, or service interface, you can update it through the Web Services Explorer." /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cuddi.html" /> +<meta name="DC.Relation" scheme="URI" content="tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tstrtexp.html" /> +<meta name="DC.Relation" scheme="URI" content="tpubent.html" /> +<meta name="DC.Relation" scheme="URI" content="tpublish.html" /> +<meta name="DC.Relation" scheme="URI" content="tunpub.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/ruddi.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/tuddiexp.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="tupdate" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Updating a business entity, Web service, or service interface</title> +</head> +<body id="tupdate"><a name="tupdate"><!-- --></a> + +<h1 class="topictitle1">Updating a business entity, Web service, or service interface</h1> +<div><p>After you have published a business entity, Web service, or service +interface, you can update it through the Web Services Explorer.</p> +<div class="p">Prerequisites:<ol><li> <a href="tpubent.html">Publish a business entity</a>.</li> +<li> <a href="tpublish.html">Publish a Web service</a>.</li> +<li> <a href="tpublish.html">Publish a service interface</a>.</li> +<li> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</li> +</ol> +</div> +<div class="section">To update a business entity, Web service, or service interface using +the Web Services Explorer:</div> +<ol><li><span>Navigate through the registry hierarchy to find the business entity, +Web service, or service interface you want to update. Select the business +entity, Web service, or service interface.</span></li> +<li><span>In the Actions icon bar, click the <span class="uicontrol">Details</span> icon.</span></li> +<li><span>Make any necessary changes and enter your publish URL, your user +ID, and password, if necessary, then click <span class="uicontrol">Go</span>.</span></li> +</ol> +<div class="section"><p>The business entity, Web service, or service interface is updated +in the registry and the Web Services Explorer is automatically +updated with your change.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html"> Tools for Web services development</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="tpubent.html" title="A business entity contains information about the business that has published a service. Before you can publish a business service, you must publish a business entity.">Publishing a business entity</a></div> +<div><a href="tpublish.html" title="The Web service, also known as the business service, describes a Web service's endpoint and where its WSDL file resides. The WSDL file lists the operations that service provides.">Publishing a Web service</a></div> +<div><a href="tunpub.html" title="After you have published a business entity, Web service, or service interface, you can remove or unpublish it through the Web Services Explorer.">Removing a business entity, Web service, or service interface from a registry</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="../ref/ruddi.html" title="Once you have registered and logged in to the UDDI registry that you want to use, you can register your Web service. Registration of a service involves four core data structure types: business information, service information, binding information, and information describing the specifications for services. The relationship between these data types is described in Figure 1.">Data structure types (UDDI registry)</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html new file mode 100644 index 000000000..07ded4542 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdisc.html @@ -0,0 +1,109 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Creating a Web service proxy using Faces" /> +<meta name="abstract" content="The Web Service Discovery Dialog allows you to discover a Web service that exists online or in your workspace, create a proxy to the Web service, and then place the methods of the proxy on a Faces JSP file." /> +<meta name="description" content="The Web Service Discovery Dialog allows you to discover a Web service that exists online or in your workspace, create a proxy to the Web service, and then place the methods of the proxy on a Faces JSP file." /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="creatingawebserviceproxy" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating a Web service proxy using Faces</title> +</head> +<body id="creatingawebserviceproxy"><a name="creatingawebserviceproxy"><!-- --></a> + +<h1 class="topictitle1">Creating a Web service proxy using Faces</h1> +<div><p>The Web Service Discovery Dialog allows you to discover a Web service +that exists online or in your workspace, create a proxy to the Web service, +and then place the methods of the proxy on a Faces JSP file.</p> +<div class="p">Prerequisite: You must have a Faces JSP file on which you will place +the proxy methods.</div> +<div class="section">To discover a Web service and create a proxy for it:</div> +<ol><li><span>Open your Faces JSP file in an editor by double-clicking it.</span></li> +<li><span>The Page Data view should be open below the Project Navigator. +If the Page Data view is not visible, open from the Window menu by selecting <span class="menucascade"><span class="uicontrol">Show View</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">Web</span> > <span class="uicontrol">Page Data</span></span>.</span></li> +<li><span>In the Page Data view, right-click and select <span class="uicontrol">New</span> > <span class="uicontrol">Web +Service</span>.</span></li> +<li><span>In the Web Service Discovery Dialog, select how you want to find +a Web service: </span> +<table border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="choicetableborder"> +<thead><tr><th valign="bottom" align="left" id="d0e42-option">Option</th> +<th valign="bottom" align="left" id="d0e42-desc">Description</th></tr></thead> +<tbody><tr><td valign="top" headers="d0e42-option" id="d0e49"><strong>Searching a public or private UDDI registry.</strong></td> +<td valign="top" headers="d0e42-desc d0e49">If +you select this option the UDDI Registry page displays.<ol type="a"><li>Enter the URL of a public or private UDDI registry, or select from the +registries supplied.</li> +<li>Enter the text with which you want to search the registry. This can include +either the partial or full name or key (UUID) of the service.</li> +<li>Select if you want to search by the name of the Web service, or by the +key that is associated with a published Web service, and click <span class="uicontrol">Go</span>.</li> +<li>The UDDI Services table is populated with a list of available Web services +that match your criteria, including their name, description, and a URL where +their WSDL file is located.<ul><li>To see additional information about the service, click Details. This will +launch the Web service in the Web Services Explorer. For more information +about using the Web Services Explorer, refer to <a href="ttestwsdl.html">Testing WSDL documents and Web services using the WSDL Explorer</a>.</li> +<li>Click a WSDL file to continue creating your Web service proxy. Go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> +</ul> +</li> +</ol> +</td> +</tr> +<tr><td valign="top" headers="d0e42-option" id="d0e77"><strong>From a known URL. This can include known WSDL, WSIL, DISCO, +and HTML URLs.</strong></td> +<td valign="top" headers="d0e42-desc d0e77">When you select this option, the URL page +displays. Enter the URL to a WSDL, WSIL, DISCO or HTML file that contains +a Web service, and click <span class="uicontrol">Go</span>.<ul><li>If you entered a URL to a WSIL, HMTL, or DISCO file, a list of Web services +available from the URL are displayed. Select one of the Web services by clicking +on the WSDL file, and go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> +<li>If you entered a URL to a WSDL file, go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</li> +</ul> +</td> +</tr> +<tr><td valign="top" headers="d0e42-option" id="d0e96"><strong>Selecting from Web services that are deployed and running +in your workspace.</strong></td> +<td valign="top" headers="d0e42-desc d0e96">If you selected to discover Web services +that are in your workspace, the Workspace page displays. It contains a list +of the Web services available in your workspace. Select a Web service by clicking +on the appropriate WSDL file and go to step <a href="#creatingawebserviceproxy__disc_step_5">5</a>.</td> +</tr> +</tbody></table> +</li> +<li id="creatingawebserviceproxy__disc_step_5"><a name="creatingawebserviceproxy__disc_step_5"><!-- --></a><span>Once you have selected a WSDL file, a table displays +the Web Service name and location, any documentation included in the Web service, +and lists the available ports.</span><ol type="a"><li class="substepexpand"><span>If there is more than one port, select the port for which you +want to create the proxy.</span></li> +<li class="substepexpand"><span>To test the Web service and to see additional information about +it, click Details. This will launch the Web service in the Web Services Explorer.</span> For more information about using the Web Services Explorer, refer to <a href="ttestwsdl.html">Testing WSDL documents and Web services +using the WSDL Explorer</a>.</li> +<li class="substepexpand"><span>Once you have ensured that the chosen Web service is the correct +one, click Add to Project.</span> This generates your proxy bean.</li> +</ol> +</li> +<li><span>The proxy is now listed in the list of existing proxy beans. Click <span class="uicontrol">OK</span> to +add it to your Page Data.</span></li> +<li id="creatingawebserviceproxy__ws_disc_step_7"><a name="creatingawebserviceproxy__ws_disc_step_7"><!-- --></a><span>Select the proxy method in the Page Data view, +and drag it onto your Faces JSP file Design view. You will be asked if you +want to use this bean to update fields or to display fields. Select the appropriate +choice, and if necessary add an action to the bean by clicking the Browse +button beside the Action field. Repeat for any other elements that you want +to add to the page.</span></li> +</ol> +<div class="section">The proxy for the Web service is now on a Faces JSP. Save the Faces +JSP and run it on a sever to test your Web service.</div> +</div> +<div></div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html new file mode 100644 index 000000000..31e20925f --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/twsdlexp.html @@ -0,0 +1,132 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Exploring WSDL using the WSDL Explorer" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="twsdlexp" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Exploring WSDL using the WSDL Explorer</title> +</head> +<body id="twsdlexp"><a name="twsdlexp"><!-- --></a> + +<h1 class="topictitle1">Exploring WSDL using the WSDL Explorer</h1> +<div><div class="p">Prerequisites: To use the WSDL Explorer, you must have a valid URL +for a WSDL document.</div> +<div class="section">The WSDL Explorer allows you to explore, and test WSDL documents. +The following actions are available in the WSDL Explorer:<ul><li>Import WSDL to the Workbench: <img src="../images/mptwsdlicon.gif" alt="Import WSDL to the Workbench icon" /></li> +<li>Import WSDL to your file system: <img src="../images/fswsdlicon.gif" alt="Import WSDL to your file system icon" /></li> +<li>Launch the Web Service Wizard: <img src="../images/wswizicon.gif" alt="Launch the Web Service Wizard icon" /></li> +<li>Add WSDL to Favorites: <img src="../images/wsdlfavicon.gif" alt="Add WSDL to Favorites icon" /></li> +<li>Show WSDL details: <img src="../images/wsdldtlicon.gif" alt="WSDL Details icon" /></li> +</ul> +</div> +</div> +<div></div><div class="nested1" xml:lang="en-us" id="d0e47"><a name="d0e47"><!-- --></a><h2 class="topictitle2">Launching the WSDL Explorer</h2> +<div><div class="section"><p>To launch the WSDL Explorer, complete the following steps:</p> +</div> +<ol><li><span> <a href="tstrtexp.html">Launch the Web Services Explorer</a>.</span></li> +<li><span>Switch to the WSDL Explorer by clicking the icon in the upper right-hand +corner <img src="../images/wsdlicon.gif" alt="Icon to launch the WSDL Explorer" />.</span></li> +</ol> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e64"><a name="d0e64"><!-- --></a><h2 class="topictitle2">Importing a WSDL file to your workspace</h2> +<div><div class="section"><p>To import the WSDL file to the Workbench:</p> +</div> +<ol><li><span>Click this icon: <img src="../images/mptwsdlicon.gif" alt="Import WSDL to the Workbench icon" />.</span></li> +<li><span>Select the project into which you want to import the WSDL.</span></li> +<li><span>If you want to generate a WSIL file from the WSDL, select <strong>Import +as a service reference to a WSIL document</strong>.</span></li> +<li><span>Click <strong>Go</strong>.</span></li> +</ol> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e90"><a name="d0e90"><!-- --></a><h2 class="topictitle2">Importing a WSDL file to your file system</h2> +<div><div class="section"><p>To import the WSDL file to your file system, click this icon: + <img src="../images/fswsdlicon.gif" alt="Import WSDL to your file system icon" />. Specify where you want the WSDL file saved on your system.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e96"><a name="d0e96"><!-- --></a><h2 class="topictitle2">Launching the Web services wizard</h2> +<div><div class="section"><p>To launch the Web Service Wizard, click this icon: <img src="../images/wswizicon.gif" alt="Launch the Web Service Wizard icon" />. You can select if you want to create +a Web service client or a Skeleton Web service from the WSDL file. Click <strong>Go</strong> to +launch the wizard.</p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e105"><a name="d0e105"><!-- --></a><h2 class="topictitle2">Adding a WSDL file to your favorites</h2> +<div><div class="section"><p>To add the WSDL file to Favorites, click this icon: </p> +<p>. +The Status pane displays that the WSDL was successfully added to your list +of favorites. </p> +</div> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="d0e110"><a name="d0e110"><!-- --></a><h2 class="topictitle2">Exploring WSDL documents using the WSDL Explorer:</h2> +<div><ol><li class="stepexpand"><span>Select WSDL Main in the Navigator pane, enter or browse to an existing +WSDL URL in the right-hand pane, and click <strong>Go</strong>. Note that the Explorer +will only allow you to browse for WSDL files that reside in the <samp class="codeph">WebContent/WSDL</samp> folder +of a project. To explore WSDL files stored in other locations within your +workspace, type the name of the WSDL file or select the file in the workspace, +right-click and select <span class="menucascade"><span class="uicontrol">Web Services </span> > <span class="uicontrol"> Launch +Web Services Explorer</span></span>. For this example the WSDL +being used is a Web Service which returns a temperature for any entered zip +code. <br /><img src="../images/wsdlexp.gif" alt="" /><br /> +The following nodes will be added to the WSDL tree: </span> <ul><li>The WSDL node: <img src="../images/wsdlnode.gif" alt="WSDL node icon" /></li> +<li>The service node (which represents a service element within the WSDL file): + <img src="../images/servnode.gif" alt="Service node icon" /></li> +<li>The binding node: <img src="../images/bindnode.gif" alt="Binding node icon" /></li> +<li>The operation node: <img src="../images/opnode.gif" alt="Operation node icon" /></li> +</ul> +</li> +<li class="stepexpand"><span>Clicking the Service node in the Navigator pane (in this example +this would be the <tt class="sysout">TemperatureService</tt> node) displays +all the bindings for this service, as well as their type and a brief description +of the binding if the WSDL provider has included one in the Actions pane. +Three types of bindings are supported: SOAP, HTTP Get, and HTTP Post. <br /><img src="../images/wsdlservdet.gif" alt="" /><br /> The WSDL +used in this example only has one binding, <tt class="sysout">TemperatureBinding</tt>, +which is represented as the <tt class="sysout">TemperaturePortType</tt> node +in the WSDL tree in the Navigator pane.</span></li> +<li class="stepexpand"><span>Clicking a displayed binding or its node displays the WSDL binding +details in the Actions pane. This includes the operations and endpoints available +for this service. <br /><img src="../images/wsdlbnddetl.gif" alt="" /><br /> In this view you can add or remove endpoints for the service. To +add an endpoint, click <strong>Add</strong>, enter the URL for the endpoint, and click + <strong>Go</strong>. The Status pane should say that the endpoints were successfully +updated. To remove an endpoint, select its checkbox, and click <strong>Remove</strong>.</span></li> +</ol> +<div class="section"><div class="note"><span class="notetitle">Note:</span> When the +Web Services Explorer loads WSDL files that use multiple inline schemas, warning +messages will be generated for types that are referenced across these schemas. +The warning message will be similar to: <samp class="codeph">Reference of type <<em>qualified_type_name</em>> +isn't resolved.</samp></div> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../../org.eclipse.jst.ws.doc.user/concepts/cws.html">Web services development</a></div> +<div><a href="../concepts/cuddi.html" title="Universal Description, Discovery, and Integration (UDDI) specification defines a way to publish and discover information about Web services.">Universal Description, Discovery, and Integration (UDDI)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="tuddiexp.html" title="Through UDDI and WSIL, other applications can discover WSDL documents and bind with them to execute transactions or perform other business processes.">Publishing Web services and business entities</a></div> +<div><a href="tstrtexp.html" title="The Web services tools allows you to launch the Web Services Explorer in several ways.">Launching the Web Services Explorer</a></div> +<div><a href="../../org.eclipse.jst.ws.doc.user/tasks/toverws.html"> Developing Web services</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml new file mode 100644 index 000000000..80dc86832 --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptionbuild_toc.xml @@ -0,0 +1,26 @@ +<?xml version="1.0" encoding="utf-8"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<toc link_to="../com.ibm.etools.webservice.doc/webservice_toc.xml#wsconsumptiont" label="wsconsumptiont" topic="concepts/cuddi.html"> + <topic label="Universal Description, Discovery, and Integration (UDDI)" href="concepts/cuddi.html"/> + <topic label="Relationship between UDDI and WSDL" href="concepts/cwsdlud.html"/> + <topic label="Discovering Web Services" href="tasks/tdiscov.html"/> + <topic label="Exploring WSDL using the WSDL Explorer" href="tasks/twsdlexp.html"/> + <topic label="Testing WSDL documents and Web services using the WSDL Explorer" href="tasks/ttestwsdl.html"/> + <topic label="Generating a Java client proxy and a sample application from a WSDL document using the IBM SOAP run-time environment" href="tasks/tsampapp.html"/> + <topic label="Creating a Web service proxy using Faces" href="tasks/twsdisc.html"/> + <topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html"> + <topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/> + <topic label="Registering with a UDDI registry" href="tasks/treg.html"/> + <topic label="Adding a Registry to the IBM Web Services Explorer" href="tasks/taddreg.html"/> + <topic label="Publishing a business entity" href="tasks/tpubent.html"/> + <topic label="Publishing a Web service" href="tasks/tpublish.html"> + <topic label="Data structure types (UDDI registry)" href="ref/ruddi.html"/> + </topic> + <topic label="Updating a business entity, Web service, or service interface" href="tasks/tupdate.html"/> + <topic label="Removing a business entity, Web service, or service interface from a registry" href="tasks/tunpub.html"/> + <topic label="Managing referenced services" href="tasks/tbusproj.html"/> + <topic label="Managing publisher assertions" href="tasks/tassert.html"/> + <topic label="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" href="tasks/tbkmrk.html"/> + <topic label="Generating a WSIL file" href="tasks/tgenwsil.html"/> + </topic> +</toc>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml new file mode 100644 index 000000000..28a9593ff --- /dev/null +++ b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="utf-8"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<toc label="wsconsumptiont" link_to="../com.ibm.etools.webservice.doc/webservice_toc.xml#wsconsumptiont" topic="tasks/tuddiexp.html"> + <topic label="Publishing Web services and business entities" href="tasks/tuddiexp.html"> + <topic label="Launching the Web Services Explorer" href="tasks/tstrtexp.html"/> + <topic label="Registering with a UDDI registry" href="tasks/treg.html"/> + <topic label="Adding a Registry to the IBM Web Services Explorer" href="tasks/taddreg.html"/> + <topic label="Publishing a business entity" href="tasks/tpubent.html"/> + <topic label="Publishing a Web service" href="tasks/tpublish.html"> + <topic label="Data structure types (UDDI registry)" href="ref/ruddi.html"/> + </topic> + <topic label="Updating a business entity, Web service, or service interface" href="tasks/tupdate.html"/> + <topic label="Removing a business entity, Web service, or service interface from a registry" href="tasks/tunpub.html"/> + <topic label="Managing referenced services" href="tasks/tbusproj.html"/> + <topic label="Managing publisher assertions" href="tasks/tassert.html"/> + <topic label="Adding a registry, business entity, business service, service interface, WSIL, or WSDL service to Favorites" href="tasks/tbkmrk.html"/> + </topic> +</toc>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html new file mode 100644 index 000000000..c173f6fb4 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html @@ -0,0 +1,82 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="JAX-RPC" /> +<meta name="abstract" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> +<meta name="description" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cjsr109.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cjaxrpc" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>JAX-RPC</title> +</head> +<body id="cjaxrpc"><a name="cjaxrpc"><!-- --></a> + +<h1 class="topictitle1">JAX-RPC</h1> +<div><p>JAX-RPC stands for Java™ API for XML-based RPC, also known as +JSR 101. It is a specification that describes Java Application Programming Interfaces +(APIs) and conventions for building Web services and Web service clients that +use remote procedure calls (RPC) and XML. It standardizes the Java to +WSDL and WSDL to Java mappings, and provides the core APIs for developing +Web services and Web service clients on the Java platform. Often used in a distributed +client/server model, an RPC mechanism enables clients to execute procedures +on other systems.</p> +<p>The current release of JAX-RPC requires the support of SOAP over HTTP for +interoperability purposes. The SOAP specification defines message structure, +encoding rules, and conventions for exchanging information in the RPC programming +model. These calls and responses are transmitted as SOAP messages over HTTP. +In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information +on SOAP, refer to <a href="csoap.html">Simple Object Access Protocol (SOAP)</a>.</p> +<p>Although the underlying run-time mechanisms (for example, Java to +WSDL serialization, WSDL to Java deserialization, protocol and transport) +are very complex, the API hides this complexity from the application developer. +On the server side, the developer can provide a Service Endpoint Interface +(SEI); alternately an SEI can be created using the Web services wizrds. An +SEI is an interface written in the Java programming language that specifies +the remote procedures of a Web service. The developer also provides the implementation +of a Web service, in the form of one or more Java classes that implement methods of the +same signature as those on the SEI. Client programs are also easy to code. +A client creates a proxy, a local object representing the service implementation +and the SEI, and then simply invokes methods on the proxy.</p> +<p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service +that is not running on the Java platform and vice versa. This flexibility +is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description +Language (WSDL). JAX-RPC was designed to support WS-I.</p> +<p>For more information on JAX-RPC, refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official JSR 101 specifications</a>.</p> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cjsr109.html" title="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.">JSR 109 and JSR 921- Implementing Enterprise Web services</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing +Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html new file mode 100644 index 000000000..2560ae70b --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html @@ -0,0 +1,65 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="JSR 109 and JSR 921- Implementing Enterprise Web services" /> +<meta name="abstract" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> +<meta name="description" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cjaxrpc.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cjsr109" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>JSR 109 and JSR 921- Implementing Enterprise Web services</title> +</head> +<body id="cjsr109"><a name="cjsr109"><!-- --></a> + +<h1 class="topictitle1">JSR 109 and JSR 921- Implementing Enterprise Web services</h1> +<div><p>JSR 109 and JSR 921 (Implementing Enterprise Web Services) define +the programming model and run-time architecture to deploy and look up Web +services in the J2EE environment; more specifically, in the Web, EJB, and +Client Application containers. One of its main goals is to ensure vendors' +implementations interoperate.</p> +<p>JSR 109 and JSR 921 build on top of JAX-RPC to cover the use of JAX-RPC +in a J2EE environment, as well as the implementation and deployment of Web +services to a J2EE application server. JSR 109 and JSR 921 define a set of +XML-based deployment descriptors to standardize Web services and Web service +client deployments in the J2EE environment. Rational Developer tools support +JSR 109 for J2EE 1.3 and JSR 921 for J2EE 1.4.</p> +<p>For more information, refer to: <a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR 109, "Implementing Enterprise Web Services</a> and <a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR 921: Implementing +Enterprise Web Services 1.1</a>.</p> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cjaxrpc.html" title="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems.">JAX-RPC</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing +Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html new file mode 100644 index 000000000..31412d379 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html @@ -0,0 +1,145 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Simple Object Access Protocol (SOAP)" /> +<meta name="abstract" content="Simple Object Access Protocol (SOAP) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> +<meta name="description" content="Simple Object Access Protocol (SOAP) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="csoap" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Simple Object Access Protocol (SOAP)</title> +</head> +<body id="csoap"><a name="csoap"><!-- --></a> + +<h1 class="topictitle1">Simple Object Access Protocol (SOAP)</h1> +<div><p>Simple Object Access Protocol (SOAP) is a lightweight protocol +for the exchange of information in a decentralized, distributed environment. +A SOAP message is a transmission of information from a sender to a receiver. +SOAP messages can be combined to perform request/response patterns. </p> +<p>SOAP is transport independent but is most commonly carried over HTTP in +order to run with the existing Internet infrastructure. SOAP enables +the binding and usage of discovered Web services by defining a message path +for routing messages. SOAP is used to query UDDI for Web services. Rational<sup>®</sup> Developer +products support SOAP 1.1.</p> +<p>SOAP is an XML-based protocol that defines three parts to every message:</p> +<ul><li> <span class="uicontrol">Envelope.</span> The envelope defines a framework +for describing what is in a message and how to process it. A SOAP message +is an envelope containing zero or more headers and exactly one body. +The envelope is the top element of the XML document, providing a container +for control information, the address of a message, and the message itself. +Headers transport any control information such as quality-of-service attributes. +The body contains the message identification and its parameters. Both +the headers and the body are child elements of the envelope.</li> +<li> <span class="uicontrol">Encoding rules.</span> The set of encoding rules +expresses instances of application-defined data types. Encoding rules define +a serialization mechanism that can be used to exchange instances of application-defined +data types. SOAP defines a programming language-independent data type scheme +based on XSD plus encoding rules for all data types defined according to this +model. SOAP encoding is not WS-I compliant and thus the Literal use (which +is no encoding) is suggested for interoperable Web services and required for +WS-I compliance.</li> +<li> <span class="uicontrol">Communication styles.</span> Communications can follow +a remote procedure call (RPC) or message-oriented (Document) format. +These are discussed below.</li> +</ul> +<div class="section"><h4 class="sectiontitle">Binding styles</h4><p>SOAP supports two different communication +styles:</p> +<blockquote> <p> <span class="uicontrol">Remote procedure call (RPC):</span> +Invocation of an operation returning a result. Typically used with SOAP encoding, +which is not WS-I compliant.</p> +<p> <span class="uicontrol">Document Style:</span> +Also known as document-oriented or message-oriented style. This style +provides a lower layer of abstraction, and requires more programming work +if you are using the IBM<sup>®</sup> SOAP or Apache Axis run-time environments.</p> + </blockquote> +</div> +<div class="section"><h4 class="sectiontitle">Encoding styles</h4><p>In distributed computing environments, +encoding styles define how data values defined in the application can be translated +to and from a particular protocol format. The translation process is +know as serialization and deserialization.</p> +<p>The SOAP specification defines +the SOAP encoding style:</p> +<blockquote> <p> <span class="uicontrol">SOAP encoding:</span> +The SOAP encoding style allows you to serialize/deserialize values of data +types from the SOAP data model. This encoding style is defined in the +SOAP 1.1 standard, and is not WS-I compliant.</p> + </blockquote> +<p>WSDL defines the +Literal XML encoding style:</p> +<blockquote> <p> <span class="uicontrol">Literal XML:</span> +Literal refers to the fact that the document should be read as-is, or unencoded. +The document is serialized as XMI, meaning that the message XML complies with +the Schema in the WSDL. When using Literal encoding, each message part references +a concrete schema definition. Literal encoding is WS-I compliant.</p> + </blockquote> +</div> +<div class="section"><h4 class="sectiontitle">Data model</h4><p>The purpose of the SOAP data model is +to provide a language-independent abstraction for data types used by common +programming language types. It consists of:</p> +<ul><li> <span class="uicontrol">Simple XSD types.</span> For example int, string, +and date.</li> +<li> <span class="uicontrol">Compound types.</span> There are two kinds of compound +types, <var class="varname">structs</var> and <var class="varname">arrays</var>. Structs +are named aggregate types in which each element has a unique name or XML tag. +Arrays have elements that are identified by position, not by name.</li> +</ul> +<p>All elements and identifiers comprising the SOAP data model are defined +in the namespace URI. The SOAP standard defines the rules for how data +types can be constructed. A project specific XML schema must define +the actual data types. The elements of the SOAP specification are defined +in <a href="http://schemas.xmlsoap.org/soap/envelope/" target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a> and + <a href="http://schemas.xmlsoap.org/soap/encoding/" target="_blank">http://schemas.xmlsoap.org/soap/encoding/</a></p> +</div> +<div class="section"><h4 class="sectiontitle">SOAP implementations</h4><p>Different implementations of +the SOAP protocol are available today. For example, the Apache Foundation +provides Apache SOAP, which grew out of an IBM project called SOAP4J, as well as Apache +Axis and the IBM WebSphere<sup>®</sup> run-time +environment. This release of the Web services tools in Rational Developer Tools supports Apache +SOAP 2.3, Axis 1.0, and IBM WebSphere implementations.</p> +</div> +<div class="section"><h4 class="sectiontitle">Mappings</h4><p>A mapping defines an association between +a qualified XML element name, a Java™ class name, and an encoding style. +The mapping specifies how, under the given encoding, an incoming XML element +with a fully qualified name is converted to a Java class and vice versa.</p> +<p>For more +information on Apache SOAP, refer to <a href="http://xml.apache.org/soap" target="_blank">xml.apache.org/soap</a> For more information on +SOAP refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a> For +more information on Web services and the WebSphere Application Server SOAP +run-time, refer to the WebSphere Application Server documentation.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing +Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html new file mode 100644 index 000000000..ceacc8d26 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html @@ -0,0 +1,220 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Web services overview" /> +<meta name="abstract" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> +<meta name="description" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsiover.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cws" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web services overview</title> +</head> +<body id="cws"><a name="cws"><!-- --></a> + +<h1 class="topictitle1">Web services overview</h1> +<div><p>A Web service is a set of related application functions that can +be programmatically invoked over the Internet. Businesses can dynamically +mix and match Web services to perform complex transactions with minimal programming. +Web services allow buyers and sellers all over the world to discover each +other, connect dynamically, and execute transactions in real time with minimal +human interaction.</p> +<p>Web services are self-contained, self-describing modular applications that +can be published, located, and invoked across the Web.</p> +<blockquote> <p> <span class="uicontrol">Web services are self-contained.</span> On +the client side, no additional software is required. A programming language +with XML and HTTP client support is enough to get you started. On the +server side, a Web server and servlet engine are required. The client +and server can be implemented in different environments. It is possible +to Web service enable an existing application without writing a single line +of code.</p> + <p> <span class="uicontrol">Web services are self-describing.</span> +The client and server need to recognize only the format and content of request +and response messages. The definition of the message format travels +with the message; no external metadata repositories or code generation tools +are required.</p> + <p> <span class="uicontrol">Web services are modular.</span> +Simple Web services can be aggregated to form more complex Web services either +by using workflow techniques or by calling lower layer Web services from a +Web service implementation.</p> +<p><span class="uicontrol">Web Services are platform independent.</span> Web +services are based on a concise set of open, XML-based standards designed +to promote interoperability between a Web service and clients across a variety +of computing platforms and programming languages.</p> + </blockquote> +<p>Web services might be anything, for example, theatre review articles, weather +reports, credit checks, stock quotations, travel advisories, or airline travel +reservation processes. Each of these self-contained business services is an +application that can easily integrate with other services, from the same or +different companies, to create a complete business process. This interoperability +allows businesses to dynamically publish, discover, and bind a range of Web +services through the Internet.</p> +<div class="section"><h4 class="sectiontitle">Categories of Web services</h4><p>Web services can be grouped +into three categories:</p> +<blockquote> <p> <span class="uicontrol">Business information.</span> A +business shares information with consumers or other businesses. In this case, +the business is using Web services to expand its scope. Examples of business +informational Web services are news streams, weather reports, or stock quotations.</p> + <p> <span class="uicontrol">Business +integration.</span> A business provides transactional, "for fee" services +to its customers. In this case, the business becomes part of a global network +of value-added suppliers that can be used to conduct commerce. Examples of +business integration Web services include bid and auction e-marketplaces, +reservation systems, and credit checking.</p> + <p> <span class="uicontrol">Business process +externalization.</span> A business differentiates itself from its competition +through the creation of a global value chain. In this case, the business uses +Web services to dynamically integrate its processes. An example of business +process externalization Web services is the associations between different +companies to combine manufacturing, assembly, wholesale distribution, and +retail sales of a particular product.</p> + </blockquote> +</div> +<div class="section"><h4 class="sectiontitle">Service roles and interactions</h4><p>A network component +in a Web Services architecture can play one or more fundamental roles: service +provider, service broker, and service client.</p> +<ul><li>Service providers create and deploy their Web services and can publish +the availability of their WSDL-described services through a service registry, +such as a UDDI Business Registry.</li> +<li>Service brokers register and categorize published services and provide +search services. For example, UDDI acts as a service broker for WSDL-described +Web services.</li> +<li>Service clients use broker services such as the UDDI Business Registry +to discover a needed WSDL-described service and then bind to and call the +service provider.</li> +</ul> +<p>Binding involves establishing all environmental prerequisites that +are necessary to successfully complete the services. Examples of environmental +prerequisites include security, transaction monitoring, and HTTP availability. +The relationships between these roles are described in Figure 1.</p> +<p>Figure +1. Service roles and interactions.</p> +<p> <img src="../images/roles.gif" alt="Figure 1 illustrates the interactions between the service broker, service provider, and service requestor." /> </p> +</div> +<div class="section"><h4 class="sectiontitle">Web service standards</h4><p>One of the key attributes +of Internet standards is that they focus on protocols and not on implementations. +The Internet is composed of heterogeneous technologies that successfully interoperate +through shared protocols. This prevents individual vendors from imposing a +standard on the Internet. Open Source software development plays a crucial +role in preserving the interoperability of vendor implementations of standards.</p> +<p>The +following standards play key roles in Web services: Universal Description, +Discovery and Integration (UDDI), Web Services Description Language (WSDL), +Web Services Inspection Language (WSIL), Simple Object Access Protocol (SOAP) +and Web Services Interoperability (WS-I). The relationship between these standards +is described in Figure 2.</p> +<p>The UDDI specification defines open, platform-independent +standards that enable businesses to share information in a global business +registry, discover services on the registry, and define how they interact +over the Internet. For more information on UDDI, refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p> +<p>WSIL +is an XML-based open specification that defines a distributed service discovery +method that supplies references to service descriptions at the service provider's +point-of-offering, by specifying how to inspect a Web site for available Web +services. A WSIL document defines the locations on a Web site where +you can look for Web service descriptions. Since WSIL focuses on distributed +service discovery, the WSIL specification complements UDDI by facilitating +the discovery of services that are available on Web sites that may not be +listed yet in a UDDI registry. A separate topic in this documentation +discusses the <a href="cwsilud.html">Relationship between UDDI and WSIL</a>. +For more information on WSIL, refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a></p> +<p>WSDL +is an XML-based open specification that describes the interfaces to and instances +of Web services on the network. It is extensible, so endpoints can be described +regardless of the message formats or network protocols that are used to communicate. +Businesses can make the WSDL documents for their Web services available though +UDDI, WSIL, or by broadcasting the URLs to their WSDL via email or Web sites. +WSDL is described as a separate topic in this documentation. For more information +on WSDL, refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> +<div class="p">SOAP +is an XML-based standard for messaging over HTTP and other Internet protocols. +It is a lightweight protocol for the exchange of information in a decentralized, +distributed environment. It is based on XML and consists of three parts:<ul><li>An envelope that defines a framework for describing what is in a message +and how to process it.</li> +<li>A set of encoding rules for expressing instances of application-defined +data types.</li> +<li>A convention for representing remote procedure calls and responses.</li> +</ul> +SOAP enables the binding and usage of discovered Web services by defining +a message path for routing messages. SOAP may be used to query UDDI for Web +services. For more information on SOAP, refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a></div> +<p>Figure 2. Relationships between +SOAP, UDDI, WSIL and WSDL.</p> +<p> <img src="../images/soapudws.gif" alt="Figure 2 illustrates the relationships between SOAP, UDDI, WSIL, and WSDL." /> </p> +<p>A service provider hosts a Web +service and makes it accessible using protocols such as SOAP/HTTP or SOAP/JMS. +The Web service is described by a WSDL document that is stored on the provider's +server or in a special repository. The WSDL document may be referenced by +the UDDI business registry and WSIL documents. These contain pointers to the +Web service's WSDL files.</p> +<p>The WS-I Simple SOAP Binding Profile and WS-I +Attachments Profile are outlines of requirements to which WSDL and Web service +protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. +The Web services WS-I validation tools currently support WS-I Simple SOAP +Binding Profile 1.0 and the Attachment Profile 1.0. To view the specifications, +refer to the WS-I Web site, and under <span class="uicontrol">Resources</span> select + <span class="uicontrol">Documentation</span>: <a href="http://www.ws-i.org" target="_blank">http://www.ws-i.org</a></p> +<div class="p">Several +new Web services standards are also supported by Rational<sup>®</sup> Developer products. These +include:<dl><dt class="dlterm">JAX-RPC</dt> +<dd>JAX-RPC stands for Java™ API for XML-based RPC, also known as +JSR 101. It is a specification that describes Java Application Programming Interfaces +(APIs) and conventions for building Web services and Web service clients that +use remote procedure calls (RPC) and XML. It standardizes the Java to +WSDL and WSDL to Java mappings, and provides the core APIs for developing +and deploying Web services and Web service clients on the Java platform. +For more information refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official specifications</a>.</dd> +<dt class="dlterm">JSR-109 and JSR-921</dt> +<dd>JSR-109 and JSR-921 (Implementing Enterprise Web Services) define the +programming model and run-time architecture to deploy and look up Web services +in the J2EE environment; more specifically, in the Web, EJB, and Client Application +containers. One of its main goals is to ensure vendors' implementations interoperate. +For more information, refer to the official specifications: <ul><li><a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR-109</a></li> +<li><a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR-921</a></li> +</ul> +</dd> +<dt class="dlterm">WS-S</dt> +<dd>Rational Developer +products support the OASIS Web Services Security 1.0 standard. For more information +on the various components of this standard, refer to:<ul><li><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" target="_blank">Web Services Security: SOAP Message Security +V1.0</a> </li> +<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" target="_blank">Web Services Security: Username Token Profile +V1.0</a></li> +<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf" target="_blank">Web Services Security: X.509 Token Profile V1.0</a></li> +</ul> +</dd> +</dl> +</div> +<p>For more information on Web services, refer to <a href="http://www.ibm.com/developerworks/webservices" target="_blank">www.ibm.com/developerworks/webservices</a></p> +</div> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services +interoperability (WS-I)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, DADX files, enterprise beans, WSDL files, and URLs. The Rational Developer products support the creation of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html new file mode 100644 index 000000000..786434263 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html @@ -0,0 +1,63 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Creating bottom-up Web services" /> +<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean, enterprise bean, URL, DADX file, or ISD." /> +<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean, enterprise bean, URL, DADX file, or ISD." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cwstopdown.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="/tasks/toverws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="creatingbottom-upwebservices" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating bottom-up Web services</title> +</head> +<body id="creatingbottom-upwebservices"><a name="creatingbottom-upwebservices"><!-- --></a> + +<h1 class="topictitle1">Creating bottom-up Web services</h1> +<div><p>Web services can be created using two methods: top-down development +and bottom-up development. Bottom-up Web services development involves creating +a Web service from a Java™ bean, enterprise bean, URL, DADX file, +or ISD.</p> +<p>Although bottom-up Web service development may be faster and easier, especially +if you are new to Web services, the top-down approach is the recommended way +of creating a Web service.</p> +<p>When creating a Web service using a bottom-up approach, first you create +a Java bean +or EJB bean and then use the Web services wizard to create the WSDL file and +Web service.</p> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="/tasks/toverws.html">Creating Web services</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwstopdown.html" title="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file.">Creating top-down Web +services</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html"> Developing Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html new file mode 100644 index 000000000..50ab8d008 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html @@ -0,0 +1,107 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Web Services Description Language (WSDL)" /> +<meta name="abstract" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> +<meta name="description" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../ref/rwsdl.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsdl" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web Services Description Language (WSDL)</title> +</head> +<body id="cwsdl"><a name="cwsdl"><!-- --></a> + +<h1 class="topictitle1">Web Services Description Language (WSDL)</h1> +<div><p>Web Services Description Language (WSDL) is a standard specification +for describing networked, XML-based services. It provides a simple way for +service providers to describe the basic format of requests to their systems +regardless of the underlying run-time implementation.</p> +<p>WSDL defines an XML format for describing network services as a set of + <var class="varname">endpoints</var> that operate on messages that contain either +document-oriented or procedure-oriented information. The operations and messages +are first described abstractly and then bound to a concrete network protocol +and message format in order to define an endpoint. Related concrete endpoints +are combined into abstract endpoints (services). WSDL is extensible to allow +description of endpoints and their messages, regardless of which message formats +or network protocols are used to communicate. This means that interfaces are +defined abstractly using XML schema and then bound to concrete representations +that are appropriate for the protocol.</p> +<p>WSDL allows a service provider to specify the following characteristics +of a Web service:</p> +<ul><li>The name of the Web service and addressing information</li> +<li>The protocol and encoding style to be used when accessing the public operations +of the Web service</li> +<li>The type information such as operations, parameters, and data types comprising +the interface of the Web service</li> +</ul> +<p>WSDL documents allow developers to expose their applications as network-accessible +services on the Internet. Through UDDI and WSIL, other applications can discover +WSDL documents and bind with them to execute transactions or perform other +business processes.</p> +<p>Rational<sup>®</sup> Developer +products support and encourages the development and use of WS-I compliant +WSDL. Using Rational Developer +products a business service provider can deploy Java™ beans and enterprise beans, DADX-described +queries and remote procedures, or existing URLs as a Web service and generate +a WSDL document that describes the service. They can also generate Java and +enterprise bean skeletons from an existing WSDL file. A business service client +can generate a Java proxy from a WSDL document, thereby providing an +easy-to-use Java interface to the Web service. The Java interface +hides the network communications details from the client enabling the business +service provider to focus on business and process portions of the application.</p> +<p>In addition to providing tools to create Web services, Rational Developer +products provide a WSDL editor that allows you to create WSDL files using +a graphical interface, a WSDL validator that ensures that your WSDL file is +semantically correct and optionally checks for WS-I compliance, and the Web +Services Explorer which allows you to dynamically test Web services without +requiring you to generate a proxy.</p> +<p>Rational Developer +products support WSDL 1.1. For more information on the WSDL specification, +refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../ref/rwsdl.html">Web Services Description Language (WSDL) reference</a></strong><br /> +A WSDL document defines services as collections of network endpoints, +or ports. In WSDL, the abstract definition of endpoints and messages is separated +from their concrete network deployment or data format bindings. This allows +the reuse of abstract definitions: messages, which are abstract descriptions +of the data being exchanged, and port types which are abstract collections +of operations. </li> +</ul> + +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing Web +services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html new file mode 100644 index 000000000..790f69b36 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html @@ -0,0 +1,120 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Web Services Inspection Language (WSIL)" /> +<meta name="abstract" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> +<meta name="description" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsilud.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsil" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web Services Inspection Language (WSIL)</title> +</head> +<body id="cwsil"><a name="cwsil"><!-- --></a> + +<h1 class="topictitle1">Web Services Inspection Language (WSIL)</h1> +<div><p>Web Services Inspection Language (WSIL) is a service discovery +mechanism that is an alternative to UDDI as well as complementary to UDDI. +When you discover Web services with UDDI, you go to a centralized registry. +WSIL is an alternative approach to Web service discovery. WSIL allows +you to go directly to the service provider and ask for the services it provides.</p> +<p>IBM<sup>®</sup> and +Microsoft's proposal for the WSIL specification is designed around an XML-based +model for building an aggregation of references to existing Web service descriptions, +that are exposed using standard Web server technology.</p> +<p>WSIL provides a distributed service discovery method that supplies references +to service descriptions at the service provider's point-of-offering, by specifying +how to inspect a Web site for available Web services. The WSIL specification +defines the locations on a Web site where you can look for Web service descriptions. </p> +<p>Since WSIL focuses on distributed service discovery, the WSIL specification +complements UDDI by facilitating the discovery of services that are available +on Web sites that may not be listed yet in a UDDI registry. A separate +topic in this documentation discusses the <a href="cwsilud.html">Relationship +between UDDI and WSIL</a>.</p> +<p>The WSIL specification does not define a service description language. +WSIL documents provide a method for aggregating different types of service +descriptions. Within a WSIL document, a single service can have more +than one reference to a service description. For example, a single Web +service might be referenced twice in a WSIL document: once directly via its +WSDL, and again via its businessService entry in a UDDI registry. References +to these two service descriptions should be put into a WSIL document. +If multiple references are available, it is beneficial to put all of them +in the WSIL document so that the application that uses the document can select +the type of service description that is compatible with and preferred by that +application.</p> +<p>The WSIL specification serves two primary functions:</p> +<ul><li>WSIL defines an XML format for listing references to existing service +descriptions. These service descriptions can be defined in any format, such +as WSDL, UDDI, or plain HTML. A WSIL document is generally made available +at the point-of-offering for the services that are referenced within the document. +A WSIL document can contain a list of references to service descriptions, +as well as references to other WSIL documents. <p>The ability to link a WSIL +document to one or more different WSIL documents allows you to manage service +description references by grouping them into different documents and to build +a hierarchy of WSIL documents. For example, separate WSIL documents +can be created for different categories of services, and one primary WSIL +document can link all of them together.</p> +</li> +<li>WSIL defines a set of conventions so that it is easy to locate other WSIL +documents. The WSIL specification does not limit the type of service descriptions +that can be referenced. The WSIL specification defines a set of standard +extensibility elements for both WSDL and UDDI. The WSIL specification +is the definition of locations where you can access WSIL documents. </li> +<li> Two conventions make the location and retrieval of WSIL documents easy: <ul><li> <span class="uicontrol">Fixed-name WSIL documents.</span> The fixed name for +WSIL documents is inspection.wsil. The inspection.wsil file is placed +at common entry points for a Web site. For example, if the common entry +point is http://entrypoint.com then the location of the WSIL document would +be http://entrypoint.com/inspection.wsil</li> +<li> <span class="uicontrol">Linked WSIL documents.</span> References to WSIL documents +can also appear within different content documents, such as HTML pages.</li> +</ul> + </li> +</ul> +<p>For more information on the Web Services Inspection Language specification, +refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a></p> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../concepts/cwsilud.html">Relationship between UDDI and WSIL</a></strong><br /> +The Web Services Inspection Language (WSIL) and the Universal Description, +Discovery, and Integration (UDDI) specification both address issues related +to Web service discovery. However, each specification takes a different +approach to the discovery of Web services. The two specifications can +be used separately or jointly; searching with WSIL can result in finding items +in UDDI.</li> +</ul> + +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing +Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html new file mode 100644 index 000000000..4c6d5f194 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html @@ -0,0 +1,100 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Relationship between UDDI and WSIL" /> +<meta name="abstract" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> +<meta name="description" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsil.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsil.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsilud" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Relationship between UDDI and WSIL</title> +</head> +<body id="cwsilud"><a name="cwsilud"><!-- --></a> + +<h1 class="topictitle1">Relationship between UDDI and WSIL</h1> +<div><p>The Web Services Inspection Language (WSIL) and the Universal Description, +Discovery, and Integration (UDDI) specification both address issues related +to Web service discovery. However, each specification takes a different +approach to the discovery of Web services. The two specifications can +be used separately or jointly; searching with WSIL can result in finding items +in UDDI.</p> +<p>The UDDI specification addresses Web service discovery through the use +of a centralized model. One or more repositories are created to house +information about businesses and the services they offer. Requests and +updates pertaining to the service and business related information are issued +directly against the repositories. In addition, UDDI prescribes a specific +format for a portion of the stored description information and, to facilitate +advanced (focused) searching, assumes that other description information will +be stored and registered within the system as well.</p> +<p>UDDI systems facilitate focused discovery patterns since these systems +are based on organized repositories that provide advanced searching capabilities. +This helps requestors locate potential communication partners. In order +to provide advanced functionality, however, UDDI requires the deployment and +maintenance of a certain amount of infrastructure, thus increasing the cost +of operation. In addition, unless the service descriptions are stored +only within UDDI, there is a cost associated with keeping the different versions +synchronized.</p> +<p>The WSIL specification relies on a completely distributed model for providing +service-related information. The service descriptions can be stored +at any location, and requests to retrieve the information are generally made +directly to the entities that are offering the services. The WSIL specification +does not stipulate any particular format for the service information. +It relies on other standards, including UDDI, to define the description formats. +The WSIL specification also relies on existing Web technologies and infrastructure +to provide mechanisms for publishing and retrieving its documents.</p> +<p>WSIL provides the ability to disseminate service-related information through +existing protocols directly from the point at which the service is being offered. +This enables focused discovery to be performed on a single target; however, +because of its decentralized and distributed model, WSIL is not a good mechanism +for executing focused discovery if the communication partner is unknown.</p> +<p>The UDDI and WSIL specifications should be viewed as complementary technologies +to be used either together or separately depending on the situation. +For example, a UDDI repository could be populated based on the results found +when performing a search for WSIL documents. Likewise, a UDDI repository +may itself be discovered when a requester retrieves a WSIL document that references +an entry in the repository. In environments where the advanced functionality +afforded by UDDI is not required and where constraints do not allow for its +deployment, the WSIL mechanism may provide all of the capabilities that are +needed. In situations where data needs to be centrally managed, a UDDI +solution alone may provide the best fit. The UDDI and WSIL specifications +should not be viewed as mutually exclusive.</p> +<div class="note"><span class="notetitle">Note:</span> Both UDDI and WSIL contain only references to WSDL - they do not contain +the WSDL documents themselves.</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing +Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html new file mode 100644 index 000000000..5b14bcc6c --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html @@ -0,0 +1,165 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Tools for Web services development" /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsinwsa" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Tools for Web services development</title> +</head> +<body id="cwsinwsa"><a name="cwsinwsa"><!-- --></a> + +<h1 class="topictitle1">Tools for Web services development</h1> +<div><p>Tools are provided to assist with the following aspects of Web services +development:</p> +<ul><li> <span class="uicontrol">Discover</span>. Browse the UDDI Business Registries +or WSIL documents to locate existing Web services for integration. The Web +becomes an extension of Rational<sup>®</sup> Developer products.</li> +<li> <span class="uicontrol">Create or Transform</span>. Create bottom-up Web services +from existing artifacts, such as Java™ beans, enterprise beans, URLs that +take and return data, DB2<sup>®</sup> XML Extender calls, DB2 Stored Procedures, and SQL queries. +Create top-down Web services from WSDL discovered from others or created using +the WSDL Editor.</li> +<li> <span class="uicontrol">Build</span>. Wrap existing artifacts as SOAP accessible +services and describe them in WSDL. The Web services wizards assist you in +generating a Java client proxy to Web services described in WSDL +and in generating Java bean skeletons from WSDL.</li> +<li> <span class="uicontrol">Deploy</span>. Deploy Web services into the WebSphere<sup>®</sup> Application +Server or Tomcat test environments. Secure Web services running on WebSphere Application +Server.</li> +<li> <span class="uicontrol">Test</span>. Test Web services running locally or remotely +in order to get instant feedback.</li> +<li> <span class="uicontrol">Develop</span>. Generate sample applications to assist +you in creating your own Web service client application.</li> +<li> <span class="uicontrol">Publish</span>. Publish Web services to a UDDI v2 or +v3 Business Registry, advertising your Web services so that other businesses +and clients can access them.</li> +</ul> +<div class="p">Some of the Web service tools available and their uses include the following:<ul><li>Use the Web Services Client wizard to create the Java client +to a deployed Web service and to test the Web service.</li> +<li>Use the Web Services wizard to create, deploy, test, and publish Web services +bottom-up from existing Java beans and enterprise beans, or top-down +from WSDL. The Web Services wizard supports the generation of the Java bean +proxy and a sample application.</li> +<li>Publish your Web service to a UDDI Business Registry using the Web Services +Explorer.</li> +<li>The Unit Test UDDI wizard installs, configures, and removes a Private +UDDI Registry.</li> +<li>The Java Beans for XML Schema wizard enables you to generate Java beans +from schema.</li> +<li>The IBM<sup>®</sup> Web +Services Explorer assists you in discovering and publishing your Web service +descriptions.</li> +<li>Use the WSDL validator to check for structural and semantic problems in +WSDL files.</li> +<li>WS-I compliance can be validated using several tools, such as the WSDL +validator, the Web service and client wizards, and a TCP/IP monitor.</li> +<li>The deployment settings for a Web service can be modified using the J2EE +deployment descriptor editors. Double-click any deployment descriptor to launch +the appropriate editor.</li> +</ul> + </div> +<p>Web services tooling supports the following specifications:</p> + +<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr><th valign="top" width="47.73869346733669%" id="d0e117">Technology or specification</th> +<th valign="top" width="52.26130653266332%" id="d0e119">Version or level supported</th> +</tr> +</thead> +<tbody><tr><td colspan="2" valign="top" headers="d0e117 d0e119 "><strong>Transports</strong></td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">HTTP/HTTPS</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v1.0 and v1.1</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">JMS</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 "> </td> +</tr> +<tr><td colspan="2" valign="top" headers="d0e117 d0e119 "><strong>Messaging</strong></td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">SOAP specification</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v1.1</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">SOAP Attachements</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 "> </td> +</tr> +<tr><td colspan="2" valign="top" headers="d0e117 d0e119 "><strong>Description</strong></td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">UDDI</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v2.0</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WSDL</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v1.1</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WSIL</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v1.0</td> +</tr> +<tr><td colspan="2" valign="top" headers="d0e117 d0e119 "><strong>Security</strong></td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WS-Security</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">OASIS Standard 1.0</td> +</tr> +<tr><td colspan="2" valign="top" headers="d0e117 d0e119 "><strong>Ineroperability</strong></td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WS-I Basic Profile</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">1.1.2</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WS-I Simple SOAP Binding Profile</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">1.0.3</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">WS-I Attachments Profile</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">1.0</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 "><strong>Other Standards</strong></td> +<td valign="top" width="52.26130653266332%" headers="d0e119 "> </td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">JAX-RPC</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">JSR 109</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">J2EE 1.3</td> +</tr> +<tr><td valign="top" width="47.73869346733669%" headers="d0e117 ">JSR 921</td> +<td valign="top" width="52.26130653266332%" headers="d0e119 ">J2EE 1.4</td> +</tr> +</tbody> +</table> +</div> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html">Creating Web services with the Apache Axis run-time environment</a></strong><br /> +</li> +</ul> + +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, DADX files, enterprise beans, WSDL files, and URLs. The Rational Developer products support the creation of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web +services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html new file mode 100644 index 000000000..fe465b7e5 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html @@ -0,0 +1,73 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Web services interoperability (WS-I)" /> +<meta name="abstract" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> +<meta name="description" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> +<meta name="DC.Relation" scheme="URI" content="../tasks/twsicomply.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/twsicomply.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="cwsiover" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web services interoperability (WS-I)</title> +</head> +<body id="cwsiover"><a name="cwsiover"><!-- --></a> + +<h1 class="topictitle1">Web services interoperability (WS-I)</h1> +<div><p>WS-I is an organization designed to promote Web service interoperability +across platforms, operating systems, and programming languages.</p> +<p>For more information on WS-I, refer to their Web site: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a>. +This site contains resources such as an overview of Web services interoperability, +usage scenarios, and specifications.</p> +<p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service +protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. +The Web services WS-I validation tools currently support WS-I Simple SOAP +Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and +the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer +to the WS-I Web site, and under <span class="uicontrol">Deliverables</span> select + <span class="uicontrol">Basic Profile</span>.</p> +<p>Depending on the type of Web service being created, you may or may not +want your Web service to comply with the WS-I profiles. The default level +of compliance is to generate a warning if a non WS-I SSBP complaint Web service +option is selected and to ignore any non WS-I AP compliant selections. You +can set the level of WS-I compliance at the workspace or project level. The +Web services wizards, the WebSphere<sup>®</sup> run-time environments, the WSDL editor, +and other Web services tools provided support and encourage the development +of WS-I compliance services.</p> +</div> +<div> +<ul class="ullinks"> +<li class="ulchildlink"><strong><a href="../tasks/twsicomply.html">Setting the level of WS-I compliance</a></strong><br /> +The Web services WS-I validation tools support the level of WS-I +compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding +Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You +can choose to make your Web service compliant or non-compliant, depending +on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, +and secured Web services, are not WS-I compliant.</li> +</ul> + +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/twsicomply.html" title="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.">Setting the level of WS-I compliance</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html new file mode 100644 index 000000000..608341f7c --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html @@ -0,0 +1,62 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="concept" /> +<meta name="DC.Title" content="Creating top-down Web services" /> +<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> +<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> +<meta name="DC.Relation" scheme="URI" content="cws.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="cwsbtmup.html" /> +<meta name="DC.Relation" scheme="URI" content="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="/tasks/toverws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="creatingtop-downwebservices" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Creating top-down Web services</title> +</head> +<body id="creatingtop-downwebservices"><a name="creatingtop-downwebservices"><!-- --></a> + +<h1 class="topictitle1">Creating top-down Web services</h1> +<div><p>Web services can be created using two methods: top-down development +and bottom-up development. Top-down Web services development involves creating +a Web service from a WSDL file.</p> +<p>Although bottom-up Web service development may be faster and easier, especially +if you are new to Web services, the top-down approach is the recommended way +of creating a Web service.</p> +<p>When creating a Web service using a top-down approach, first you design +the implementation of the Web service by creating a WSDL file. You can do +this using the WSDL Editor. You can then use the Web services wizard to create +the Web service and skeleton Java™ classes to which you can add the required +code.</p> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="/tasks/toverws.html">Creating Web services</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="cwsinwsa.html">Tools for Web services development</a></div> +<div><a href="cwsbtmup.html" title="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean, enterprise bean, URL, DADX file, or ISD.">Creating bottom-up Web services</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../../com.ibm.etools.webservice.creation.doc/tasks/toverws.html"> Developing Web services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ibmdita.css b/docs/org.eclipse.jst.ws.doc.user/ibmdita.css new file mode 100644 index 000000000..e20903960 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/ibmdita.css @@ -0,0 +1,219 @@ +.unresolved { background-color: skyblue; } +.noTemplate { background-color: yellow; } + +.sidebar {background: silver } +.toc {font-size: small; } + +.base { background-color: #ffffff; } +.breadcrumb { font-size : smaller;} +.prereq { margin-left : 20px;} +.hierarchy { display: block; border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; border-color : Silver;} + +.nested0 { margin-top : 1em;} +.nested1 { } +.nested2 { } + +.p {margin-top: 1em} + +.tableborder { margin-top: 1em; margin-bottom: 1em } +.tablenoborder { margin-top: 1em; margin-bottom: 1em } +caption { text-align: left; font-style: italic } +.simpletableborder { margin-top: 1em; margin-bottom: 1em } +.simpletablenoborder { margin-top: 1em; margin-bottom: 1em } +.choicetableborder { margin-top: 1em; margin-bottom: 1em } +.choicetablenoborder { margin-top: 1em; margin-bottom: 1em } + +.figcap { font-style: italic } +.figdesc { font-style: normal } + +.fignone {margin-top: 1em} +.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.figbottom { border-bottom : 2px solid; border-color : Silver;} +.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.synnone {margin-top: 1em} +.synborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.synsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} +.syntop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} +.synbottom { border-bottom : 2px solid; border-color : Silver;} +.syntopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} + +.skip { margin-top: 1em } +.skipspace { margin-top: 1em; margin-bottom: 1em } +.ullinks { list-style-type: none } +.ulchildlink { margin-top: 1em; margin-bottom: 1em } +.olchildlink { margin-top: 1em; margin-bottom: 1em } +.linklist { margin-bottom: 1em } +.linklistwithchild { margin-left: 1.5em; margin-bottom: 1em } +.sublinklist { margin-left: 1.5em; margin-bottom: 1em } +.relconcepts { margin-top: 1em; margin-bottom: 1em } +.reltasks { margin-top: 1em; margin-bottom: 1em } +.relref { margin-top: 1em; margin-bottom: 1em } +.relinfo { margin-top: 1em; margin-bottom: 1em } +div.breadcrumb {margin-bottom: 1em } + +.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; } +.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; } +.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; } +.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; } +.topictitle5 { font-size: 1.17em; font-weight: bold; } +.topictitle6 { font-size: 1.17em; font-style: italic; } +.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;} +.section { margin-top: 1em; margin-bottom: 1em } +.example { margin-top: 1em; margin-bottom: 1em } + +.note { margin-top: 1em; margin-bottom : 1em;} +.notetitle { font-weight: bold } +.notelisttitle { font-weight: bold } +.tip { margin-top: 1em; margin-bottom : 1em;} +.tiptitle { font-weight: bold } +.fastpath { margin-top: 1em; margin-bottom : 1em;} +.fastpathtitle { font-weight: bold } +.important { margin-top: 1em; margin-bottom : 1em;} +.importanttitle { font-weight: bold } +.remember { margin-top: 1em; margin-bottom : 1em;} +.remembertitle { font-weight: bold } +.restriction { margin-top: 1em; margin-bottom : 1em;} +.restrictiontitle { font-weight: bold } +.attention { margin-top: 1em; margin-bottom : 1em;} +.attentiontitle { font-weight: bold } +.dangertitle { margin-top: 1em; font-weight: bold } +.danger { padding: 5px 5px 5px 5px; border: solid; border-width: thin; font-weight: bold; margin-top: 2px; margin-bottom : 1em; } +.cautiontitle { margin-top: 1em; font-weight: bold } +.caution { font-weight: bold; margin-bottom : 1em; } + +ul.simple { list-style-type: none } + +.firstcol { font-weight : bold;} + +.bold { font-weight: bold; } +.boldItalic { font-weight: bold; font-style: italic; } +.italic { font-style: italic; } +.underlined { text-decoration: underline; } +.uicontrol { font-weight: bold; } +.parmname { font-weight: bold; } +.defparmname { font-weight: bold; text-decoration: underline; } +.kwd { font-weight: bold; } +.defkwd { font-weight: bold; text-decoration: underline; } +.var { font-style : italic;} +.shortcut { text-decoration: underline; } + +.ptocH1 {font-size: x-small; } +.ptocH2 {font-size: x-small; } + +.smallCaps { text-transform: uppercase; font-size: smaller; } +.stitle { font-style: italic; text-decoration: underline; } +.nte {} + +.dlterm { font-weight: bold; } +.dltermexpand { font-weight: bold; margin-top: 1em; } +.defListHead { font-weight: bold; text-decoration: underline; } +.parmListKwd { font-weight: bold; } +.parmListVar { font-style: italic; } +.pk { font-weight: bold; text-decoration: underline; } + +*[compact="yes"]>li { margin-top: 0em;} +*[compact="no"]>li { margin-top: .53em;} +.liexpand { margin-top: 1em; margin-bottom: 1em } +.sliexpand { margin-top: 1em; margin-bottom: 1em } +.dlexpand { margin-top: 1em; margin-bottom: 1em } +.ddexpand { margin-top: 1em; margin-bottom: 1em } +.stepexpand { margin-top: 1em; margin-bottom: 1em } +.substepexpand { margin-top: 1em; margin-bottom: 1em } + +div.imageleft { text-align: left } +div.imagecenter { text-align: center } +div.imageright { text-align: right } +div.imagejustify { text-align: justify } + +pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre} + +CITE { font-style: italic; } +EM { font-style: italic; } +STRONG { font-weight: bold; } +VAR { font-style: italic; } + +/************************************************************************ + Styles added to support .NET output. Not used by standard processing. + ************************************************************************/ + +body.dotnet /* This body tag requires the use of one of the sets of banner and/or text div ids */ + { + margin: 0px 0px 0px 0px; + padding: 0px 0px 0px 0px; + background: #ffffff; + color: #000000; + width: 100%; + } + +div.nstext /* Creates the scrolling text area for Nonscrolling region topic */ + { + padding: 5px 10px 0px 22px; + } + +div.nsbanner /* Creates Nonscrolling banner region */ + { + position: relative; + left: 0px; + padding: 0px 0px 0px 0px; + border-bottom: 1px solid #999999; + } + +div.bannerrow1 /* provides full-width color to top row in running head */ + { + background-color: #99ccff; + } + +/* STYLES FOR RUNNING HEADS */ + +table.bannerparthead, table.bannertitle /* General values for the Running Head tables */ + { + position: relative; + left: 0px; + top: 0px; + padding: 0px 0px 0px 0px; + margin: 0px 0px 0px 0px; + width: 100%; + height: 21px; + border-collapse: collapse; + border-style: solid; + border-width: 0px; + background-color: #99ccff; + font-size: 100%; + } +table.bannerparthead td /* General Values for cells in the top row of running head */ + { + margin: 0px 0px 0px 0px; + padding: 2px 0px 0px 4px; + vertical-align: middle; + /*border-width: 0px 0px 1px 0px; */ + border-width: 0px + border-style: solid; + border-color: #999999; + background: transparent; + font-style: italic; + font-weight: normal; + } +table.bannerparthead td.product /* Values for top right cell in running head */ + { /* Allows for a second text block in the running head */ + text-align: right; + padding: 2px 5px 0px 5px; + } + +h1.dtH1 { + margin-left: -18px; + } +div.titlerow /* provides non-scroll topic title area (requires script) */ + { + width: 100%; /* Forces tables to have correct right margin */ + padding: 0px 10px 0px 22px; + background-color: #99ccff; + } +div.titlerow h1 + { + margin-top: 0em; + font-weight: bold; + margin-bottom: .2em + } diff --git a/docs/org.eclipse.jst.ws.doc.user/images/roles.gif b/docs/org.eclipse.jst.ws.doc.user/images/roles.gif Binary files differnew file mode 100644 index 000000000..05e99874a --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/images/roles.gif diff --git a/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif b/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif Binary files differnew file mode 100644 index 000000000..efb42f500 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif diff --git a/docs/org.eclipse.jst.ws.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.doc.user/plugin.xml new file mode 100644 index 000000000..8d2b40334 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/plugin.xml @@ -0,0 +1,20 @@ +<?xml version="1.0" ?> +<?eclipse version="3.0"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<!-- /******************************************************************************* + * Copyright (c) 2000, 2005 IBM Corporation and others. + * All rights reserved. This program and the accompanying materials + * are made available under the terms of the Eclipse Public License v1.0 + * which accompanies this distribution, and is available at + * http://www.eclipse.org/legal/epl-v10.html + * + * Contributors: + * IBM Corporation - initial API and implementation + *******************************************************************************/ --> +<plugin> + + <extension point="org.eclipse.help.toc"> + <toc file="webservice_toc.xml" /> + </extension> + +</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html new file mode 100644 index 000000000..06d0a3a46 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html @@ -0,0 +1,94 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="reference" /> +<meta name="DC.Title" content="Web Services Description Language (WSDL) reference" /> +<meta name="abstract" content="A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations." /> +<meta name="description" content="A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations." /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> +<meta name="DC.Relation" scheme="URI" content="rsoapwsdl.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsdl.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="rwsdl" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web Services Description Language (WSDL) reference</title> +</head> +<body id="rwsdl"><a name="rwsdl"><!-- --></a> + +<h1 class="topictitle1">Web Services Description Language (WSDL) reference</h1> +<div><p>A WSDL document defines services as collections of network endpoints, +or ports. In WSDL, the abstract definition of endpoints and messages is separated +from their concrete network deployment or data format bindings. This allows +the reuse of abstract definitions: messages, which are abstract descriptions +of the data being exchanged, and port types which are abstract collections +of operations. </p> +<div class="section"><p>The concrete protocol and data format specifications for a particular +port type constitutes a reusable binding. A port is defined by associating +a network address with a reusable binding, and a collection of ports define +a service. Hence, a WSDL document uses the following elements in the definition +of network services:</p> +<ul><li> <span class="uicontrol">Types</span>: a container for data type definitions using +some type system (such as XSD).</li> +<li> <span class="uicontrol">Message</span>: an abstract, typed definition of the +data being communicated.</li> +<li> <span class="uicontrol">Operation</span>: an abstract description of an action +supported by the service.</li> +<li> <span class="uicontrol">Port Type</span>: an abstract set of operations supported +by one or more endpoints.</li> +<li> <span class="uicontrol">Binding</span>: a concrete protocol and data format specification +for a particular port type. The binding is usually SOAP and the encoding and +data formatting regulations used (also known as the style) is usually literal +(this includes document/literal, and sometimes rpc/literal).</li> +<li> <span class="uicontrol">Port</span>: a single endpoint defined as a combination +of a binding and a network address.</li> +<li> <span class="uicontrol">Service</span>: a collection of related endpoints.</li> +</ul> +<p>For more information on WSDL, refer to </p> +<p><a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> +<p>The +various WSDL elements can be structured in many ways. It can be in one single +WSDL file or in mulitple WSDL files. If the IBM<sup>®</sup> WebSphere<sup>®</sup> or AXIS 1.0 run-time environment +are selected, Rational<sup>®</sup> Developer +products generate one single WSDL file containing in-line schema. If the IBM SOAP +run-time environment is selected, Rational Developer products generate +multiple WSDL and XSD files by default.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsdl.html" title="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation.">Web Services Description Language (WSDL)</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +<div><a href="../concepts/cwsdl.html" title="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation.">Web Services Description Language (WSDL)</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing Web +services</a></div> +<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> + +<div class="linklist"><strong>Related Reference</strong><br /> + +<div><a href="rsoapwsdl.html" title="When using the IBM SOAP run-time environment, by default the Web services tools in this product store the elements in three separate XML documents when generating Web services from Java beans, EJBs, and URLs: the WSDL binding document, the WSDL service document, and the WSDL interface document. By default XSD files are also generated if non-inline complex types are used by the interface. When generating Web services from DADX files, one WSDL document is generated.">WSDL files generated by the IBM SOAP run-time environment</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html new file mode 100644 index 000000000..b73a6ee5f --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html @@ -0,0 +1,115 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="reference" /> +<meta name="DC.Title" content="Web services preferences" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsinwsa.html" /> +<meta name="DC.Relation" scheme="URI" content="../tasks/toverws.html" /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cws.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="rwspref" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Web services preferences</title> +</head> +<body id="rwspref"><a name="rwspref"><!-- --></a> + +<h1 class="topictitle1">Web services preferences</h1> +<div><div class="section"><div class="p">To set any of the Web services preferences, follow these steps:<ol><li>Click <span class="uicontrol">Window > Preferences</span> to open the Preferences +notebook.</li> +<li>Expand <span class="uicontrol">Web services</span>, and click the preference +category that you want to set</li> +<li>Select the check boxes that you want to set as the default when creating +your Web service.</li> +<li>Click <span class="uicontrol">OK</span> to apply the changes and close the Preferences +notebook.</li> +</ol> +If you require more information on any of the options, select the option +and press <span class="uicontrol">F1</span>.</div> +<p>Web services tools enable you +to define the following preferences:</p> +<dl><dt class="dlterm">Popup Dialog Selection</dt> +<dd>The Dialogs preferences enable you to determine which dialog boxes that +you want to see when running popup actions. If you have disabled any of the +dialogs by selecting "Do not show this dialog again" on the first page of +a Web services wizard, you can undo your change by clearing the check box +beside the dialog that you have chosen to hide.</dd> +<dt class="dlterm">Project Topology</dt> +<dd>The Project Topology preferences allow you to:<ul><li>Select the default client project type that the Web services wizards will +create when generating a Web service client. You can also set the order in +which the client project types will be listed in the wizard. Note that this +selection is simply a default and an alternate project type can be selected +in the wizard.</li> +<li>Select whether you want to generate the Web service and the Web service +client in the same EAR project or different EAR projects. Generating the service +and client into different EAR projects can reduce the chance of conflicts +that occur when both exist in a single EAR project, but uses more system resources.</li> +</ul> +</dd> +<dt class="dlterm">Resource Management</dt> +<dd>The Resource Management preferences enable you to determine the file and +folder creation and overwriting defaults that you want to use when creating +your Web service.</dd> +<dt class="dlterm">Scenario Defaults</dt> +<dd>The Scenario Defaults preferences enable you to set the following scenario +defaults that you want to use when creating your Web service:<ul><li>which type of Web service you want to be selected by default.</li> +<li>whether or not you want the Web service started by the wizard.</li> +<li>if you want the Web Services Explorer to launch by default so that you +can publish your Web service to a UDDI registry.</li> +<li>if you want to generate a proxy and the default type of proxy generated.</li> +<li>if you want the Web Services Explorer to launch by default so that you +can test the Web service.</li> +<li>if you want the Web service SOAP traffic routed through a TCP/IP monitor +so that you can monitor the SOAP packets and optionally test them for WS-I +compliance.</li> +</ul> +Note that all these defaults can be overridden in the wizard.</dd> +<dt class="dlterm">Server and Runtime</dt> +<dd>Select the server, Web service run-time environment, and J2EE version +that you want selected by default in the Web services wizard. Note that all +these defaults can be overridden in the wizard.</dd> +<dt class="dlterm">Test Facility Defaults</dt> +<dd>can select whether to have the wizard automatically launch a test facility, +and you can select your preferred type of test facility</dd> +<dt class="dlterm">WSDL files</dt> +<dd>When creating a WSDL file in the WSDL editor, you can set the default +target namespace. If you do not select to change the default, your WSDL file +will have http://tempuri.org as its target namespace.</dd> +<dt class="dlterm">WS-I Compliance</dt> +<dd>The WS-I Compliance preferences allow you to select your level of compliance +with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile +(AP). Note: if you change the level of WS-I compliance while WS-I incompliances +are listed in the Task view, the Task view will not be automatically updated. +The workspace must be revalidated before the warnings will be removed from +the Task view. For more information on WS-I, refer to: </dd> +</dl> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> +</div> + +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../concepts/cwsinwsa.html">Tools for Web services development</a></div></div> + +<div class="linklist"><strong>Related Tasks</strong><br /> + +<div><a href="../tasks/toverws.html"> Developing Web +services</a></div></div> +</div> +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html new file mode 100644 index 000000000..e5e3f86f2 --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html @@ -0,0 +1,85 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE html + PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html lang="en-us" xml:lang="en-us"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> +<meta name="copyright" content="(C) Copyright IBM Corporation 2005" /> +<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" /> +<meta name="security" content="public" /> +<meta name="Robots" content="index,follow" /> +<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> +<meta name="DC.Type" content="task" /> +<meta name="DC.Title" content="Setting the level of WS-I compliance" /> +<meta name="abstract" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant." /> +<meta name="description" content="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant." /> +<meta name="DC.Relation" scheme="URI" content="../concepts/cwsiover.html" /> +<meta name="DC.Format" content="XHTML" /> +<meta name="DC.Identifier" content="twsicomply" /> +<meta name="DC.Language" content="en-us" /> +<!-- All rights reserved. Licensed Materials Property of IBM --> +<!-- US Government Users Restricted Rights --> +<!-- Use, duplication or disclosure restricted by --> +<!-- GSA ADP Schedule Contract with IBM Corp. --> +<link rel="stylesheet" type="text/css" href="../ibmdita.css" /> +<title>Setting the level of WS-I compliance</title> +</head> +<body id="twsicomply"><a name="twsicomply"><!-- --></a> + +<h1 class="topictitle1">Setting the level of WS-I compliance</h1> +<div><p>The Web services WS-I validation tools support the level of WS-I +compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding +Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You +can choose to make your Web service compliant or non-compliant, depending +on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, +and secured Web services, are not WS-I compliant.</p> +<div class="section"><p>You can set the level of compliance for either the Basic Profile +and the Simple SOAP Binding Profile, or for the Attachments Profile. You can +select from three levels of compliance with WS-I specifications:</p> +<ul><li>Require WS-I compliance - this level prevents you from creating a non-compliant +Web service.</li> +<li>Suggest WS-I compliance - this level allows you to create a non-compliant +Web service, but provides a visible warning stating how the service is non-compliant.</li> +<li>Ignore WS-I compliance - this level allows you to create a non-compliant +Web service and does not notify you of non-compliance.</li> +</ul> +<p>You can set the level of WS-I compliance at the workspace +level, or at the project level.</p> +</div> +</div> +<div> +<div class="familylinks"> +<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div> +</div> +</div><div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a><h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2> +<div><div class="section"><p>To set the level of WS-I compliance for the workspace:</p> +</div> +<ol><li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span></li> +<li><span>Select <strong>Web Services</strong> from the component tree on the left-hand +side of the panel.</span></li> +<li><span>Under WS-I compliance, select the level of compliance you want +from the drop-down lists.</span></li> +<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> +</ol> +</div> +</div> +<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a><h2 class="topictitle2">Set the level of WS-I compliance for a project</h2> +<div><div class="section"><p>To set the level of WS-I compliance for a project:</p> +</div> +<ol><li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span></li> +<li><span>Select <strong>WS-I Compliance</strong> from the component tree on the left-hand +side of the panel.</span></li> +<li><span>Under WS-I compliance, select the level of compliance you want +from the drop-down lists, or select to have the project share the same level +of WS-I compliance as the workspace</span></li> +<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> +</ol> +</div> +<div> +<div class="linklist"><strong>Related Concepts</strong><br /> + +<div><a href="../concepts/cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability (WS-I)</a></div></div> +</div></div> + +</body> +</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml new file mode 100644 index 000000000..2eecd597d --- /dev/null +++ b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml @@ -0,0 +1,58 @@ +<?xml version="1.0" encoding="utf-8"?> +<?NLS TYPE="org.eclipse.help.toc"?> +<toc label="wsmaintoc" topic="concepts/cws.html"> + <topic label="Web services overview" href="concepts/cws.html"> + <topic label="Technologies"> + <topic label="Web Services Description Language (WSDL)" href="concepts/cwsdl.html"> + <topic label="Web Services Description Language (WSDL) reference" href="ref/rwsdl.html"/> + </topic> + <topic label="Simple Object Access Protocol (SOAP)" href="concepts/csoap.html"/> + <topic label="Universal Description, Discovery, and Integration (UDDI)" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html"> + <topic label="Relationship between UDDI and WSDL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html"/> + </topic> + <topic label="Web Services Inspection Language (WSIL)" href="concepts/cwsil.html"> + <topic label="Relationship between UDDI and WSIL" href="concepts/cwsilud.html"/> + </topic> + <topic label="JAX-RPC" href="concepts/cjaxrpc.html"/> + <topic label="JSR 109 and JSR 921- Implementing Enterprise Web services" href="concepts/cjsr109.html"/> + </topic> + <topic label="Workspace and tools"> + <topic label="Tools for Web services development" href="concepts/cwsinwsa.html"> + <topic label="Creating Web services with the Apache Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html"/> + </topic> + <topic label="Configuring your workspace"> + <topic label="Web services preferences" href="ref/rwspref.html"/> + <topic label="Web services interoperability (WS-I)" href="concepts/cwsiover.html"> + <topic label="Setting the level of WS-I compliance" href="tasks/twsicomply.html"/> + </topic> + <topic label="Creating an Apache Tomcat server and Web project" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html"/> + </topic> + </topic> + </topic> + <topic label="Importing and creating resources used by Web services"> + <link toc="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml"/> + </topic> + <topic label="Creating Web services" href="/tasks/toverws.html"> + <topic label="Creating top-down Web services" href="concepts/cwstopdown.html"> + <topic label="Creating a Web service and Java bean skeleton from WSDL" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html"/> + </topic> + <topic label="Creating bottom-up Web services" href="concepts/cwsbtmup.html"> + <topic label="Creating a Web service from a Java bean" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html"/> + </topic> + <topic label="Creating Web service clients"> + <topic label="Discovering and importing a Web service" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html"/> + <topic label="Generating a Java client proxy from a WSDL document using the Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html"/> + </topic> + </topic> + <topic label="Testing and validating Web services"> + <topic label="Testing WSDL documents and Web services with the WSDL Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html"/> + <topic label="Validating WSDL" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html"/> + <topic label="Testing Web services with the TCP/IP Monitor" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html"> + <topic label="Validating WS-I compliance of Web service SOAP traffic" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html"/> + </topic> + </topic> + <topic label="Publishing Web services"> + <link toc="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml"/> + <topic label="Generating WSIL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html"/> + </topic> +</toc>
\ No newline at end of file |
