<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <HTML DIR="ltr"> <HEAD> <TITLE>Deploying UDDI Services</TITLE> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252"> <META HTTP-EQUIV="MSThemeCompatible" CONTENT="Yes"> <META NAME="MS.LOCALE" CONTENT="EN-US"> <LINK REL="stylesheet" MEDIA="screen" TYPE="text/css" HREF="coUA.css"> <LINK REL="stylesheet" MEDIA="print" TYPE="text/css" HREF="coUAprint.css"> <SCRIPT LANGUAGE="JScript" SRC="shared.js"></SCRIPT> </HEAD> <BODY> <DIV CLASS="UAbrand"><SPAN CLASS="webonly"><IMG SRC="UAbrand.gif" CLASS="UAbrand" ALT="Microsoft Windows Graphic"></SPAN></DIV> <H1>Deploying UDDI Services</H1> <P>To deploy a UDDI Services site, you install UDDI Services components onto one or more computers, each running a supported member of the Windows Server 2003 family, and then define the groups of individuals that can access the site. A UDDI Services site requires a complete installation of all UDDI Services components, including at least one Web server component that is connected to a database component.</P> <p>UDDI Services can be installed on any of following operating systems:</p> <ul> <LI> Windows Server 2003, Standard Edition. Supports a stand-alone installation of UDDI Services only. <LI> Windows Server 2003, Enterprise Edition. Supports stand-alone and distributed installations of UDDI Services. <LI> Windows Server 2003, Datacenter Edition. Supports stand-alone and distributed installations of UDDI Services.</LI> </ul> <H2>UDDI Services Components</H2> <ul> <LI> <b>Database components</b>. Provides database services for a UDDI Services site. Installs to a computer running a supported member of the Windows Server 2003 family and Microsoft SQL Server 2000 or Microsoft SQL Server Desktop Engine (MSDE2000). MSDE2000, included with the Windows Server 2003 family, is a Microsoft SQL Server 2000-compatible local database storage mechanism that is designed and optimized for use on smaller computer systems. MSDE2000 does not include administrative tools, and it cannot communicate across a network. For this reason, MSDE2000 can be used only in stand-alone installations of UDDI Services. <LI> <b>Web Server components</b>. Provides support for the UDDI version 1.0 and 2.0 APIs and includes a Web user interface with searching, publishing, and coordinating features that are compatible with Microsoft Internet Explorer 4.0 or later and Netscape Navigator 4.5 or later. It installs to a computer running a supported member of the Windows Server 2003 family and uses Microsoft Internet Information Services (IIS) 6.0. <li> <b>Administration Console</b>. An MMC snap-in and set of command-line tools that are used to administer local or remote UDDI Services sites and facilitate database backups. It installs on a computer running a supported member of the Windows Server 2003 family.</li> </ul> <H2>Installation Options</H2> <p> UDDI Services is designed around a scalable architecture that allows you to deploy a UDDI Services site in a stand-alone or distributed environment. A stand-alone installation is useful for developer prototyping or other low-volume scenarios that involve a limited number of simultaneous users. A distributed installation is recommended for enterprise-wide implementations or other high-volume scenarios where access times, availability, and reliability are of greater importance. </p> <h3>Stand-alone installation</h3> <p>In a stand-alone installation of UDDI Services, both the Web server and database components are installed onto a single computer running a member of the Windows Server 2003 family. The database components are installed into Microsoft SQL Server 2000 or a local MSDE2000 database instance, and the Web server components are connected to that instance. If you want to use SQL Server 2000 to host the database components, you must install it prior to beginning installation of UDDI Services. This is the only type of installation available in Windows Server 2003, Standard Edition.</p> <h3>Distributed installation</h3> <p> A distributed installation of UDDI Services, available only with Windows Server 2003, Datacenter Edition and Windows Server 2003, Enterprise Edition, provides the most fault-tolerant and responsive configuration available because it places each of the UDDI Services components onto separate servers, a server cluster, or a Web farm. How you decide to distribute UDDI Services components depends on how you choose to load balance your installation. </p> <p><b>Common distributed site configurations</b></p> <P><A ID="expand" HREF="#" CLASS="expandToggle">One SQL Server and one Web server</A></P> <DIV CLASS="expand"> <P> The UDDI Services database components are installed onto a computer running a supported member of the Windows Server 2003 family and Microsoft SQL Server 2000. The UDDI Services Web server components are installed onto another computer running a supported member of the Windows Server 2003 family and then configured to use the instance to which the UDDI Services database components are installed. </P> <p></p> <P></P> </DIV> <P><A ID="expand" HREF="#" CLASS="expandToggle">A SQL Server virtual server and one Web server</A></P> <DIV CLASS="expand"> <P> The UDDI Services database components are installed to the same instance on each node of the SQL Server 2000 virtual server hosted on a supported member of the Windows Server 2003 family. The UDDI Services Web server components are installed onto another computer running a supported member of the Windows Server 2003 family and then configured to use the instance on the virtual server to which the UDDI Services database components are installed. </P> </DIV> <P><A ID="expand" HREF="#" CLASS="expandToggle">One SQL Server and a Web farm</A></P> <DIV CLASS="expand"> <P> The UDDI Services database components are installed onto a computer running a supported member of the Windows Server 2003 family and SQL Server 2000. The UDDI Services Web server components are installed onto each of the computers in a Windows Server 2003 family Web farm. During installation, each Web server is configured to use the instance to which the UDDI Services database components are installed. </P> </DIV> <P><A ID="expand" HREF="#" CLASS="expandToggle">A SQL Server virtual server and a Web farm</A></P> <DIV CLASS="expand"> <P> The UDDI Services database component are installed to the same instance on each node of the SQL Server 2000 virtual server hosted on a supported member of the Windows Server 2003 family. The UDDI Services Web server components are installed onto each of the computers in a Windows Server 2003 family Web farm. During installation, each Web server is configured to use the instance on the virtual server to which the UDDI Services database components are installed. </P> </DIV> <P></P> <h2>Roles and Permissions</h2> After you install UDDI Services, configure the groups that define the UDDI Services roles. By default, the UDDI Services Publisher, Coordinator, and Administrator groups use the <b>Builtin\Administrators</b> group and the UDDI Services User's group uses the <b>Built-in\Users</b> group in your network. <TABLE WIDTH="100%"> <TR> <!--Column 1--><TH>Activity</TH> <!--Column 2--><TH>User</TH> <!--Column 3--><TH>Publisher</TH> <!--Column 3--><TH>Coordinator</TH> <!--Column 3--><TH>Administrator</TH> </TR> <TR> <!--Column 1--><TD>Search for providers, services, and tModels</TD> <!--User--><td align="middle">X</td> <!--Publisher--><td align="middle">X</td> <!--Coordinator--><td align="middle">X</td> <!--Administrator--><td align="middle">X</td> </TR> <TR> <TD>Publish providers, services, and tModels</TD> <!--User--><td></td> <!--Publisher--><td align="middle">X</td> <!--Coordinator--><td align="middle">X</td> <!--Administrator--><td align="middle">X</td> </TR> <tr> <TD>View server statistics and manage entity ownerships</TD> <!--User--><td></td> <!--Publisher--><td></td> <!--Coordinator--><td align="middle">X</td> <!--Administrator--><td align="middle">X</td> </tr> <tr> <TD>Manage categorization schemes</TD> <!--User--><td></td> <!--Publisher--><td></td> <!--Coordinator--><td align="middle">X</td> <!--Administrator--><td align="middle">X</td> </tr> <tr> <TD>Import data<br> </TD> <!--User--><td></td> <!--Publisher--><td></td> <!--Coordinator--><td></td> <!--Administrator--><td align="middle">X</td> </tr> <tr> <TD> Command-line tools</TD> <!--User--><td></td> <!--Publisher--><td></td> <!--Coordinator--><td></td> <!--Administrator--><td align="middle">X</td> </tr> <tr> <TD> Configure Web and database servers, assign groups to roles and configure authentication</TD> <!--User--><td></td> <!--Publisher--><td></td> <!--Coordinator--><td></td> <!--Administrator--><td align="middle">X</td> </tr> </TABLE> <hr class="iis" size="1"> <p align="center"><i><a href="colegal.htm">� 1997-2002 Microsoft Corporation. All rights reserved</a>.</i></p> </BODY> </HTML>