Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

254 lines
10 KiB

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
  2. <HTML DIR="ltr">
  3. <HEAD>
  4. <TITLE>Deploying UDDI Services</TITLE>
  5. <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252">
  6. <META HTTP-EQUIV="MSThemeCompatible" CONTENT="Yes">
  7. <META NAME="MS.LOCALE" CONTENT="EN-US">
  8. <LINK REL="stylesheet" MEDIA="screen" TYPE="text/css" HREF="coUA.css">
  9. <LINK REL="stylesheet" MEDIA="print" TYPE="text/css" HREF="coUAprint.css">
  10. <SCRIPT LANGUAGE="JScript" SRC="shared.js"></SCRIPT>
  11. </HEAD>
  12. <BODY>
  13. <DIV CLASS="UAbrand"><SPAN CLASS="webonly"><IMG SRC="UAbrand.gif" CLASS="UAbrand" ALT="Microsoft Windows Graphic"></SPAN></DIV>
  14. <H1>Deploying
  15. UDDI&nbsp;Services</H1>
  16. <P>To deploy a
  17. UDDI&nbsp;Services
  18. site, you install
  19. UDDI&nbsp;Services
  20. components onto one or more computers, each running a supported member of the
  21. Windows&nbsp;Server 2003
  22. family, and then define the groups of individuals that can access the site. A
  23. UDDI&nbsp;Services site requires a complete installation of all
  24. UDDI&nbsp;Services
  25. components, including at least one Web server component that is connected to a
  26. database component.</P>
  27. <p>UDDI Services can be installed on any of following operating systems:</p>
  28. <ul>
  29. <LI>
  30. Windows Server 2003, Standard Edition. Supports a stand-alone installation
  31. of UDDI Services only.
  32. <LI>
  33. Windows Server 2003, Enterprise Edition. Supports stand-alone and
  34. distributed installations of UDDI Services.
  35. <LI>
  36. Windows Server 2003, Datacenter Edition. Supports stand-alone and
  37. distributed installations of UDDI Services.</LI>
  38. </ul>
  39. <H2>UDDI&nbsp;Services
  40. Components</H2>
  41. <ul>
  42. <LI>
  43. <b>Database components</b>.&nbsp;&nbsp; Provides database services for a UDDI
  44. Services site. Installs to a computer running a supported member of the
  45. Windows&nbsp;Server 2003 family and Microsoft SQL&nbsp;Server&nbsp;2000 or
  46. Microsoft SQL&nbsp;Server Desktop Engine (MSDE2000). MSDE2000, included with
  47. the
  48. Windows&nbsp;Server 2003
  49. family, is a Microsoft SQL&nbsp;Server&nbsp;2000-compatible local database
  50. storage mechanism that is designed and optimized for use on smaller computer
  51. systems. MSDE2000 does not include administrative tools, and it cannot
  52. communicate across a network. For this reason, MSDE2000 can be used only in
  53. stand-alone installations of
  54. UDDI&nbsp;Services.
  55. <LI>
  56. <b>Web Server components</b>.&nbsp;&nbsp; Provides support for the UDDI
  57. version&nbsp;1.0 and 2.0&nbsp;APIs and includes a Web user interface with
  58. searching, publishing, and coordinating features that are compatible with
  59. Microsoft Internet Explorer&nbsp;4.0 or later and Netscape Navigator&nbsp;4.5
  60. or later. It installs to a computer running a supported member of the
  61. Windows&nbsp;Server 2003 family and uses Microsoft Internet Information
  62. Services (IIS) 6.0.
  63. <li>
  64. <b>Administration Console</b>.&nbsp;&nbsp; An MMC snap-in and set of
  65. command-line tools that are used to administer local or remote
  66. UDDI&nbsp;Services
  67. sites and facilitate database backups. It installs on a computer running a
  68. supported member of the Windows&nbsp;Server 2003 family.</li>
  69. </ul>
  70. <H2>Installation Options</H2>
  71. <p>
  72. UDDI&nbsp;Services
  73. is designed around a scalable architecture that allows you to deploy a
  74. UDDI&nbsp;Services
  75. site in a stand-alone or distributed environment. A stand-alone installation is
  76. useful for developer prototyping or other low-volume scenarios that involve a
  77. limited number of simultaneous users. A distributed installation is recommended
  78. for enterprise-wide implementations or other high-volume scenarios where access
  79. times, availability, and reliability are of greater importance.
  80. </p>
  81. <h3>Stand-alone installation</h3>
  82. <p>In a stand-alone installation of
  83. UDDI&nbsp;Services, both the Web server and database components
  84. are installed onto a single computer running a member of the
  85. Windows&nbsp;Server 2003
  86. family. The database components are installed into Microsoft SQL
  87. Server&nbsp;2000 or a local MSDE2000 database instance, and the Web server
  88. components are connected to that instance. If you want to use SQL
  89. Server&nbsp;2000 to host the database components, you must install it prior to
  90. beginning installation of
  91. UDDI&nbsp;Services. This is the only type of installation
  92. available in
  93. Windows&nbsp;Server 2003, Standard Edition.</p>
  94. <h3>Distributed installation</h3>
  95. <p>
  96. A distributed installation of
  97. UDDI&nbsp;Services, available only with
  98. Windows&nbsp;Server
  99. 2003, Datacenter Edition
  100. and
  101. Windows&nbsp;Server 2003, Enterprise Edition, provides the
  102. most fault-tolerant and responsive configuration available because it places
  103. each of the
  104. UDDI&nbsp;Services
  105. components onto separate servers, a server cluster, or a Web farm. How you
  106. decide to distribute
  107. UDDI&nbsp;Services
  108. components depends on how you choose to load balance your installation.
  109. </p>
  110. <p><b>Common distributed site configurations</b></p>
  111. <P><A ID="expand" HREF="#" CLASS="expandToggle">One SQL Server and one Web server</A></P>
  112. <DIV CLASS="expand">
  113. <P>
  114. The
  115. UDDI&nbsp;Services
  116. database components are installed onto a computer running a supported member of
  117. the Windows Server 2003 family and&nbsp;Microsoft SQL
  118. Server&nbsp;2000. The
  119. UDDI&nbsp;Services
  120. Web server components are installed onto another computer running a supported
  121. member of the Windows&nbsp;Server 2003 family and then configured to use
  122. the instance to which the UDDI&nbsp;Services database components are installed.
  123. </P>
  124. <p></p>
  125. <P></P>
  126. </DIV>
  127. <P><A ID="expand" HREF="#" CLASS="expandToggle">A SQL Server virtual server and one Web
  128. server</A></P>
  129. <DIV CLASS="expand">
  130. <P>
  131. The
  132. UDDI&nbsp;Services
  133. database components are installed to the same instance on each node of the SQL
  134. Server 2000 virtual server hosted on a supported member of the
  135. Windows&nbsp;Server 2003 family. The
  136. UDDI&nbsp;Services
  137. Web server components are installed onto another computer running a supported
  138. member of the Windows&nbsp;Server 2003 family&nbsp;and then configured to
  139. use the instance on the virtual server to which the UDDI&nbsp;Services database
  140. components are installed.&nbsp;
  141. </P>
  142. </DIV>
  143. <P><A ID="expand" HREF="#" CLASS="expandToggle">One SQL Server and a Web farm</A></P>
  144. <DIV CLASS="expand">
  145. <P>
  146. The
  147. UDDI&nbsp;Services
  148. database components are installed onto a computer running a supported member of
  149. the Windows Server 2003 family and SQL Server&nbsp;2000. The
  150. UDDI&nbsp;Services
  151. Web server components are installed onto each of the computers in a
  152. Windows&nbsp;Server 2003
  153. family Web farm. During installation, each Web server is configured to use the
  154. instance to which the UDDI&nbsp;Services database components are installed.
  155. </P>
  156. </DIV>
  157. <P><A ID="expand" HREF="#" CLASS="expandToggle">A SQL Server virtual server and a Web
  158. farm</A></P>
  159. <DIV CLASS="expand">
  160. <P>
  161. The
  162. UDDI&nbsp;Services
  163. database component are installed to the same instance on each node of the SQL
  164. Server 2000 virtual server hosted on a supported member of the
  165. Windows&nbsp;Server 2003 family. The
  166. UDDI&nbsp;Services
  167. Web server components are installed onto each of the computers in a
  168. Windows&nbsp;Server 2003
  169. family Web farm. During installation, each Web server is configured to use the
  170. instance on the virtual server to which the UDDI&nbsp;Services database
  171. components are installed.
  172. </P>
  173. </DIV>
  174. <P></P>
  175. <h2>Roles and Permissions</h2>
  176. After you install
  177. UDDI&nbsp;Services, configure the groups that define the UDDI
  178. Services roles. By default, the
  179. UDDI&nbsp;Services
  180. Publisher, Coordinator, and Administrator groups use the <b>Builtin\Administrators</b>
  181. group and the
  182. UDDI&nbsp;Services
  183. User's group uses the <b>Built-in\Users</b> group in your network.
  184. <TABLE WIDTH="100%">
  185. <TR>
  186. <!--Column 1--><TH>Activity</TH>
  187. <!--Column 2--><TH>User</TH>
  188. <!--Column 3--><TH>Publisher</TH>
  189. <!--Column 3--><TH>Coordinator</TH>
  190. <!--Column 3--><TH>Administrator</TH>
  191. </TR>
  192. <TR>
  193. <!--Column 1--><TD>Search for providers, services, and tModels</TD>
  194. <!--User--><td align="middle">X</td>
  195. <!--Publisher--><td align="middle">X</td>
  196. <!--Coordinator--><td align="middle">X</td>
  197. <!--Administrator--><td align="middle">X</td>
  198. </TR>
  199. <TR>
  200. <TD>Publish providers, services, and tModels</TD>
  201. <!--User--><td></td>
  202. <!--Publisher--><td align="middle">X</td>
  203. <!--Coordinator--><td align="middle">X</td>
  204. <!--Administrator--><td align="middle">X</td>
  205. </TR>
  206. <tr>
  207. <TD>View server statistics and manage entity ownerships</TD>
  208. <!--User--><td></td>
  209. <!--Publisher--><td></td>
  210. <!--Coordinator--><td align="middle">X</td>
  211. <!--Administrator--><td align="middle">X</td>
  212. </tr>
  213. <tr>
  214. <TD>Manage categorization schemes</TD>
  215. <!--User--><td></td>
  216. <!--Publisher--><td></td>
  217. <!--Coordinator--><td align="middle">X</td>
  218. <!--Administrator--><td align="middle">X</td>
  219. </tr>
  220. <tr>
  221. <TD>Import data<br>
  222. </TD>
  223. <!--User--><td></td>
  224. <!--Publisher--><td></td>
  225. <!--Coordinator--><td></td>
  226. <!--Administrator--><td align="middle">X</td>
  227. </tr>
  228. <tr>
  229. <TD>
  230. Command-line tools</TD>
  231. <!--User--><td></td>
  232. <!--Publisher--><td></td>
  233. <!--Coordinator--><td></td>
  234. <!--Administrator--><td align="middle">X</td>
  235. </tr>
  236. <tr>
  237. <TD>
  238. Configure Web and database servers, assign groups to roles and&nbsp;configure
  239. authentication</TD>
  240. <!--User--><td></td>
  241. <!--Publisher--><td></td>
  242. <!--Coordinator--><td></td>
  243. <!--Administrator--><td align="middle">X</td>
  244. </tr>
  245. </TABLE>
  246. <hr class="iis" size="1">
  247. <p align="center"><i><a href="colegal.htm">� 1997-2002 Microsoft Corporation. All rights
  248. reserved</a>.</i></p>
  249. </BODY>
  250. </HTML>