diff options
Diffstat (limited to 'docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref')
| -rw-r--r-- | docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita | 73 | ||||
| -rw-r--r-- | docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html | 110 |
2 files changed, 0 insertions, 183 deletions
diff --git a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita b/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita deleted file mode 100644 index 1d63add1d..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.dita +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd"> -<reference id="ruddi" xml:lang="en-us"> -<title>Data structure types (UDDI registry)</title> -<shortdesc>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.</shortdesc> -<refbody> -<section><lq> <p> <uicontrol>Business information.</uicontrol> Information -that is contained in a <systemoutput>businessEntity</systemoutput> structure. -The <systemoutput>businessEntity</systemoutput> contains information about -the business that has published the service, such as business name, description, -contacts and identifiers.</p> <p> <uicontrol>Service information.</uicontrol> Information -that describes a group of Web services. It is contained in a <systemoutput>businessService</systemoutput> structure. -The <systemoutput>businessService</systemoutput> 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> <uicontrol>Binding -information.</uicontrol> Information represented by the <systemoutput>bindingTemplate</systemoutput> structure. -The <systemoutput>bindingTemplate</systemoutput> holds technical information -for determining the entry point and construction specifications for invoking -a Web service. The <systemoutput>bindingTemplate</systemoutput> provides -the Web service descriptions relevant for application developers that want -to find and invoke a Web service. The <systemoutput>bindingTemplate</systemoutput> points -to a service implementation descriptions, for example via a URL.</p> <p> <uicontrol>Information -describing the specifications for services.</uicontrol> Metadata about the -various specifications implemented by a given Web service represented by the - <systemoutput>tModel</systemoutput>. The <systemoutput>tModel</systemoutput> provides -a reference system to assist in the discovery of Web services.</p> </lq><p>Figure -1. Relationship between data types.</p><p> <image alt="Figure 1 illustrates the relationship between the business entity, business service, binding template, and tmodel." -href="../images/uddi.gif"></image> </p><p>Each child structure has a unique -parent structure. This means that each <systemoutput>businessService</systemoutput> structure -is owned by a specific <systemoutput>businessEntity</systemoutput>. In turn, -each <systemoutput>bindingTemplate</systemoutput> is owned by a specific - <systemoutput>businessService</systemoutput>. Each <systemoutput>bindingTemplate</systemoutput> structure -references to unique instances of <systemoutput>tModel</systemoutput> structures; -however, since references can be repeated within several parent structures, -there can be many references to <systemoutput>tModels</systemoutput> from -different Entity-Service-Template parents, as seen in Figure 2.</p><p>Figure -2. References to tModel.</p><p> <image alt="Figure 2 illustrates the multiple references to a tModel." -href="../images/uddiref.gif"></image> </p></section> -<section><title>Publisher assertions</title><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></section> -<section><title>Service projections</title><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></section> -</refbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita" scope="peer"> -<linktext> Tools for Web services development</linktext></link> -<link href="../../org.eclipse.jst.ws.doc.user/concepts/cws.dita" scope="peer"> -<linktext>Web services development</linktext></link> -</linklist> -<linklist><title>Related Tasks</title><?Pub Caret?> -<link href="../tasks/tuddiexp.dita"></link> -</linklist> -</related-links> -</reference> -<?Pub *0000005079?> 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 deleted file mode 100644 index f6ad7be7c..000000000 --- a/docs/org.eclipse.jst.ws.consumption.ui.doc.user/ref/ruddi.html +++ /dev/null @@ -1,110 +0,0 @@ -<?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 content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<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 content="reference" name="DC.Type" /> -<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 scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.doc.user/concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/tuddiexp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ruddi" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<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="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 |