docs/org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tassert.html - webservices/webtools.webservices - Git at Google

 <?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="task" name="DC.Type" />
 <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 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="../concepts/cuddi.html" />
 <meta scheme="URI" name="DC.Relation" content="tuddiexp.html" />
 <meta scheme="URI" name="DC.Relation" content="tstrtexp.html" />
 <meta scheme="URI" name="DC.Relation" content="treg.html" />
 <meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" />
 <meta content="XHTML" name="DC.Format" />
 <meta content="tassert" 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>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="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>
	<?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="task" name="DC.Type" />
	<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 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="../concepts/cuddi.html" />
	<meta scheme="URI" name="DC.Relation" content="tuddiexp.html" />
	<meta scheme="URI" name="DC.Relation" content="tstrtexp.html" />
	<meta scheme="URI" name="DC.Relation" content="treg.html" />
	<meta scheme="URI" name="DC.Relation" content="../ref/ruddi.html" />
	<meta content="XHTML" name="DC.Format" />
	<meta content="tassert" 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>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="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>