TAO/docs/ORBEndpoint.html

   1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
   2
   3 <!--  -->
   4
   5 <html>
   6   <head>
   7     <title>-ORBListenEndpoints Details</title>
   8     <!-- Changed by: , 12-Jun-2002 -->
   9   </head>
  10
  11   <body text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
  12     <h1><A HREF="Options.html#-ORBListenEndpoints">-ORBListenEndpoints</A> Details</h1>
  13     <P>
  14     <UL>
  15       <LI><A HREF="#Overview">Overview</A></LI>
  16       <LI><A HREF="#Options">Endpoint-Specific Options</A></LI>
  17       <LI><A HREF="#IIOP">IIOP Endpoints</A></LI>
  18       <LI><A HREF="#SHMIOP">SHMIOP Endpoints</A></LI>
  19       <LI><A HREF="#UIOP">UIOP Endpoints</A></LI>
  20       <LI><A HREF="#DIOP">DIOP Endpoints</A></LI>
  21       <LI><A HREF="#SSLIOP">SSLIOP Endpoints</A></LI>
  22     </UL>
  23
  24     <hr>
  25     <P><h2><A NAME="Overview">Overview</A></h2>
  26       Tells the ORB to listen for requests on the interface specified
  27       by <I><EM>endpoint</EM></I>.  Endpoints are specified using a
  28       URL style format.  An endpoint has the form:
  29     <blockquote><CODE>
  30         protocol://V.v@addr1,...,W.w@addrN
  31       </CODE></blockquote>
  32     where <CODE>V.v</CODE> and <CODE>W.w</CODE> are optional protocol
  33     versions for each address.  An example of an IIOP endpoint is:
  34     <blockquote><CODE>
  35         iiop://<I><EM>hostname</EM></I>:<I><EM>port</EM></I>
  36       </CODE></blockquote>
  37     Sets of endpoints may be specified using multiple
  38     <CODE>-ORBListenEndpoints</CODE> options or by delimiting endpoints with
  39     a semi-colon (;).  For example:
  40     <blockquote><CODE>
  41         -ORBListenEndpoints iiop://localhost:9999 -ORBListenEndpoints uiop:///tmp/mylocalsock -ORBListenEndpoints shmiop://10002
  42       </CODE></blockquote>
  43     is equivalent to:
  44     <blockquote><CODE>
  45         -ORBListenEndpoints 'iiop://localhost:9999;uiop:///tmp/mylocalsock;shmiop://10002'
  46       </CODE></blockquote>
  47     Notice the single quotes (') in the latter option specification.
  48     Single quotes are needed to prevent the shell from interpreting
  49     text after the semi-colon as another command to run.
  50     <P>
  51       If an endpoint is specified without an <CODE>addr</CODE> such as
  52       the following:
  53     <blockquote><CODE>
  54         -ORBListenEndpoints uiop:// -ORBListenEndpoints shmiop://
  55       </CODE></blockquote>
  56     then a default endpoint will be created for the specified protocol.
  57     <P>
  58       This is a server side option.
  59
  60     <hr>
  61     <P>
  62     <h2><A NAME="Options">Endpoint-Specific Options</A></h2>
  63     <P>
  64       The <CODE>-ORBListenEndpoints</CODE> options can accept
  65       endpoint-specific options.  Specifically, such options will only
  66       apply to the endpoint for which they were specified.
  67     <P>
  68       An endpoint-specific option is used as follows:
  69     <BLOCKQUOTE>
  70       <CODE>
  71         -ORBListenEndpoints iiop://foo:1234/option=value
  72       </CODE>
  73     </BLOCKQUOTE>
  74     <P>
  75       Additional options can be specified by separating each option
  76       with an ampersand '<CODE>&amp;</CODE>' as follows:
  77     <BLOCKQUOTE>
  78       <CODE>
  79         -ORBListenEndpoints 'iiop://foo:1234/option1=value1&option2=value2'
  80       </CODE>
  81     </BLOCKQUOTE>
  82     <P>
  83       Notice that the address and the endpoint-specific options are
  84       separated by a forward slash '<CODE>/</CODE>' in this case,
  85       i.e. for IIOP endpoints.  This character may differ for other
  86       types of pluggable protocol endpoints.  For example, UIOP
  87       endpoint-specific options are separated from the address by a
  88       vertical bar '<CODE>|</CODE>'.  Also note that when using more
  89       than option, quotes should be used to prevent the shell from
  90       interpreting the ampersand '<CODE>&amp;</CODE>' as a command to
  91       tell the shell to backgroup a job.
  92
  93     <hr>
  94     <P>
  95     <h2><A NAME="IIOP">IIOP Endpoints</A></h2>
  96     TAO's IIOP pluggable protocol utilizes TCP/IP as its underlying
  97     transport mechanism.
  98     <P>
  99     <h3>IIOP Endpoint Overview</h3>
 100     <P>
 101       IIOP endpoints in TAO have the form:
 102     <BLOCKQUOTE>
 103       <P>
 104         <CODE>
 105           -ORBListenEndpoints iiop://V.v@hostname1:port1,...,W.w@hostname2:port2
 106         </CODE>
 107     </BLOCKQUOTE>
 108     <P>
 109       Where "<CODE>V.v</CODE>" and "<CODE>W.w</CODE>" are the IIOP
 110       protocol versions associated with the given address
 111       (hostname:port pair).  Currently supported versions are
 112       <CODE>1.0</CODE>, <CODE>1.1</CODE>, and <CODE>1.2</CODE>.
 113
 114     <P>
 115       Options are separated from the addresses by a forward slash
 116       '<CODE>/</CODE>'.  For instance, if an IIOP endpoint should have
 117       a property foobar of 50 associated with it, then the following
 118       endpoint specification could be used
 119     <BLOCKQUOTE>
 120       <P>
 121         <CODE>
 122           -ORBListenEndpoints iiop://hostname:port/foobar=50
 123         </CODE>
 124     </BLOCKQUOTE>
 125     <P>
 126     <h3>IIOP Address Format</h3>
 127     <P>
 128       IIOP addresses are comprised of a hostname (or an IP address)
 129       and a TCP port the server should listen on.  The hostname is
 130       used to select which network interface to set up the endpoint
 131       on.  It is <STRONG>not</STRONG> used to set the hostname that
 132       goes into the generated IOR.  This is especially useful if the
 133       endpoint should be setup on a specific network interface other
 134       than the default network interface.
 135     <P>
 136       Suppose a host has the following network interfaces:
 137     <UL>
 138       <LI>eth0: foo1.bar.baz <FONT COLOR=RED>(DEFAULT)</FONT></LI>
 139       <LI>eth1: foo2.bar.baz</LI>
 140     </UL>
 141     <P>
 142       To set up an endpoint on the second network interface "eth1,"
 143       the following endpoint specification could be used:
 144     <BLOCKQUOTE>
 145       <P>
 146         <CODE>
 147           -ORBListenEndpoints iiop://foo2
 148         </CODE>
 149     </BLOCKQUOTE>
 150     or:
 151     <BLOCKQUOTE>
 152       <P>
 153         <CODE>
 154           -ORBListenEndpoints iiop://foo2.bar.baz
 155         </CODE>
 156     </BLOCKQUOTE>
 157     <P>
 158       TAO will attempt to ensure that the fully qualified domain name is
 159       embedded in the IOR.
 160     <P>
 161       In the above example, an available port will be chosen by TAO
 162       (actually the operating system kernel), which will then be
 163       placed into the IOR.
 164     <P>
 165       To set up an endpoint on a specific port, simply use an endpoint
 166       of the form:
 167     <BLOCKQUOTE>
 168       <P>
 169         <CODE>
 170           -ORBListenEndpoints iiop://foo2:1234
 171         </CODE>
 172     </BLOCKQUOTE>
 173     <P>
 174       where <CODE>1234</CODE> is the TCP port the endpoint will be
 175       opened on.  In this case, an endpoint will be opened on the
 176       network interface associated with the hostname <CODE>foo2</CODE>
 177       on port <CODE>1234</CODE>.
 178     <P>
 179       Port <I>names</I> are also accepted.  For example, suppose a
 180       UNIX installation has a service called "my_protocol" associated
 181       with port 1234 in the service database in
 182       <CODE>/etc/services</CODE>, then the following would cause an
 183       endpoint to be opened on the port associated with that service:
 184     <BLOCKQUOTE>
 185       <P>
 186         <CODE>
 187           -ORBListenEndpoints iiop://foo2:my_protocol
 188         </CODE>
 189     </BLOCKQUOTE>
 190     <P>
 191       Port numbers range from <CODE>0</CODE> (causes port to be chosen
 192       by operating system) to <CODE>65355</CODE>.  Port numbers less
 193       than <CODE>1024</CODE> on UNIX systems are considered
 194       privileged, and require super-user privileges to access them.
 195       Also be aware that some ports may already be in use by other
 196       applications.
 197     <P>
 198       Suppose an endpoint should be created on each network
 199       interface.  To do so, simply omit the address from the endpoint
 200       specification as follows:
 201     <BLOCKQUOTE>
 202       <P>
 203         <CODE>
 204           -ORBListenEndpoints iiop://
 205         </CODE>
 206     </BLOCKQUOTE>
 207     <P>
 208       In this case, an endpoint will be set up on each network
 209       interface detected by TAO.  The port for each opened endpoint
 210       will be chosen automatically.  The chosen port will be the same
 211       for all endpoints.  Each endpoint will be represented in
 212       generated IOR as a separate profile.
 213     <P>
 214       Note that network interface detection only work on platforms
 215       that support this feature.  If network interface detection isn't
 216       supported, then the default network interface will be chosen.
 217     <P>
 218       Now suppose that an endpoint should be created on each detected
 219       network interface, but with a specific port.  This can be
 220       achieved by using an endpoint specification of the form:
 221     <BLOCKQUOTE>
 222       <P>
 223         <CODE>
 224           -ORBListenEndpoints iiop://:1234
 225         </CODE>
 226     </BLOCKQUOTE>
 227     <P>
 228       This will create endpoints on each detected network interface,
 229       each with the TCP port <CODE>1234</CODE>.  Notice that there is
 230       a colon '<CODE>:</CODE>' preceeding the port number
 231       <CODE>1234</CODE>.  That colon is necessary to make TAO
 232       interpret <CODE>1234</CODE> as a port.  Without the colon, TAO
 233       would interpret <CODE>1234</CODE> as a hostname associated with
 234       a given network interface.
 235
 236     <P>
 237     <P>
 238       The hostname part of an endpoint can also be specified as a literal
 239       IP address in 'dotted decimal address' form for IPv4 addresses:
 240     <BLOCKQUOTE>
 241       <P>
 242         <CODE>
 243           -ORBListenEndpoints iiop://192.168.10.24:1234
 244         </CODE>
 245     </BLOCKQUOTE>
 246
 247       For IPv6 addresses a special form is required to specify decimal IP
 248       addresses since the decimal separator for IPv6 addresses is identical
 249       to the separator used for port numbers; i.e. a colon (':').
 250       To be able to distinguish an endpoint specification for host 01ef::1
 251       and port 123 and one for host 01ef::1:123 and no port number IPv6
 252       decimal addresses need to enclosed by square brackets ('[' and ']'):
 253     <BLOCKQUOTE>
 254       <P>
 255         <CODE>
 256           -ORBListenEndpoints iiop://[01ef::1]:123
 257           -ORBListenEndpoints iiop://[01ef::1:123]
 258         </CODE>
 259     </BLOCKQUOTE>
 260
 261       <B>NOTE:</B>
 262       Since IPv6 endpoint are supported only for GIOP/IIOP versions >= 1.2
 263       it is <FONT color='RED'>illegal</FONT> to combine version numbers
 264       &lt; 1.2 and IPv6 decimal addresses:
 265     <BLOCKQUOTE>
 266       <P>
 267         <CODE>
 268           -ORBListenEndpoints iiop://1.1@[01ef::1]:123 <B><FONT color='RED'>--> ILLEGAL</FONT></B>
 269         </CODE>
 270     </BLOCKQUOTE>
 271     <P>
 272     <h3>IIOP Endpoint-Specific Options</h3>
 273     <P>
 274     TAO supports the following endpoint-specific options that apply only
 275     to IIOP endpoints:
 276
 277       <TABLE BORDER="2" CELLSPACING="2" CELLPADDING= "0">
 278         <TR>
 279           <TH>Option</TH>
 280           <TH>Availability</TH>
 281           <TH>Description</TH>
 282         </TR>
 283         <TR>
 284           <TD>
 285             <CODE>portspan</CODE>
 286           </TD>
 287           <TD>
 288             <CODE>TAO 1.1.15</CODE>
 289           </TD>
 290           <TD>
 291             The <CODE>portspan</CODE> option specifies that an IIOP endpoint
 292             should be opened on the first available port within a
 293             specified span of port numbers, beginning with a specified
 294             initial port.  This option is useful when one or more servers
 295             may be restricted to using ports within a given range.  The
 296             intention is that the behavior should be similar to using
 297             ephemeral ports except within a restricted user-defined
 298             range.
 299             <P>
 300             The format for <CODE>ORBListenEndpoints</CODE> with the
 301             <CODE>portspan</CODE> option is:
 302             <BLOCKQUOTE>
 303               <CODE>-ORBListenEndpoints iiop://[</CODE><I>hostname</I><CODE>]:</CODE><I
 304 >initialPort</I><CODE>/portspan=</CODE><I>span</I>
 305             </BLOCKQUOTE>
 306             where <I>initialPort</I> is the initial port number in the
 307             range of allowable ports, and <I>span</I> is an integer
 308             value indicating the size of the span of allowable ports.
 309             Valid values for <I>initialPort</I> include any valid port
 310             number.  Valid values for <I>span</I> are in the
 311             range <CODE>1</CODE> to <CODE>65535</CODE>.  The
 312             <I>hostname</I> (in <CODE>[ ]</CODE>)is optional.
 313             <P>
 314             The server's ORB will attempt to create a listening endpoint
 315             beginning with the initial port.  If that fails, it will try
 316             the next port in the range.  It will continue to try each
 317             port in the range until it
 318             is able to successfully open one for listening or until it                      has exhausted the range
 319             <CODE>[initialPort:initialPort+span-1]</CODE> at which point it                 fails with a <CODE>CORBA::BAD_PARAM</CODE> system exception.
 320           </TD>
 321         </TR>
 322         <TR>
 323           <TD>
 324             <CODE>hostname_in_ior</CODE>
 325           </TD>
 326           <TD>
 327             <CODE>TAO 1.2.4</CODE>
 328           </TD>
 329           <TD>
 330             The <CODE>hostname_in_ior</CODE> option allows one to
 331             specify the hostname that is inserted into the generated
 332             IOR.  This option overrides the default (local) hostnames
 333             that TAO normally inserts.  This can be useful in
 334             environments where the hostname in use is one whose IP
 335             address changes dynamically.
 336             <P>
 337             The format for <CODE>ORBListenEndpoints</CODE> with the
 338             <CODE>hostname_in_ior</CODE> option is:
 339             <BLOCKQUOTE>
 340               <CODE>-ORBListenEndpoints iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
 341 >port</I><CODE>/hostname_in_ior=</CODE><I>overridden_hostname</I>
 342             </BLOCKQUOTE>
 343             where <I>local_hostname</I> and <I>port</I> are specified
 344             as normal, and <I>overridden_hostname</I> is the hostname
 345             that should be put into generated IORs.
 346             </TD>
 347         </TR>
 348         <TR>
 349           <TD>
 350             <CODE>reuse_addr</CODE>
 351           </TD>
 352           <TD>
 353             <CODE>TAO 1.4.8</CODE>
 354           </TD>
 355           <TD>
 356             Available in IIOP & SSLIOP the <CODE>reuse_addr</CODE> option allows one to
 357             set the SO_REUSEADDR socket option on an endpoint. Doing so bypasses
 358             the TCP TIME_WAIT and can be used to open an endpoint
 359             on a port still in TIME_WAIT state. Use caution using this option. Its not
 360             recommended for the general use-case. Setting
 361             SO_REUSEADDR has been observed to cause unexpected side-effects on some
 362             platforms (e.g. Solaris 5.7 x86 allows programs run as same or different
 363             users to bind to the same port when SO_REUSEADDR is set by all users).
 364             <P>
 365             The format for <CODE>ORBListenEndpoints</CODE> with the
 366             <CODE>reuse_addr</CODE> option is:
 367             <BLOCKQUOTE>
 368               <CODE>-ORBListenEndpoints iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
 369 >port</I><CODE>/reuse_addr=[0|1]</CODE>
 370             </BLOCKQUOTE>
 371             </TD>
 372         </TR>
 373       </TABLE>
 374
 375     <P>
 376     <h3>IIOP Endpoint Examples</h3>
 377     <P>
 378       Here are some additional examples of IIOP endpoints:
 379     <UL>
 380       <LI><CODE>-ORBListenEndpoints iiop://1.0@foo1:0</CODE>
 381       <LI><CODE>-ORBListenEndpoints iiop://1.0@foo:0,1.1@bar,baz:3456</CODE>
 382       <LI><CODE>-ORBListenEndpoints iiop://1.0@foo:0,1.1@bar,baz:3456/foobar=300</CODE></LI>
 383       <LI><CODE>-ORBListenEndpoints iiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
 384       <LI><CODE>-ORBListenEndpoints iiop://:2020/foobar=12345</CODE>
 385       <LI><CODE>-ORBListenEndpoints iiop://1.1@</CODE>
 386       <LI><CODE>-ORBListenEndpoints iiop://1.1@:1234</CODE>
 387       <LI><CODE>-ORBListenEndpoints iiop://1.1@,1.0@:1234,1.1@</CODE>
 388       <LI><CODE>-ORBListenEndpoints iiop://1.1@foo:2020/portspan=30</CODE>
 389       <LI><CODE>-ORBListenEndpoints iiop://foo:2020 -ORBListenEndpoints iiop://foo:10020 </CODE> </CODE>
 390     </UL>
 391
 392     <hr>
 393
 394     <P>
 395     <h2><A NAME="SHMIOP">SHMIOP Endpoints</A></h2>
 396     TAO's SHMIOP pluggable protocol utilizes shared memory as its
 397     underlying transport mechanism.
 398     <P>
 399     <h3>SHMIOP Endpoint Overview</h3>
 400     <P>
 401       SHMIOP endpoints in TAO have the similar form to IIOP endpoints:
 402     <BLOCKQUOTE>
 403       <P>
 404         <CODE>
 405           -ORBListenEndpoints shmiop://V.v@port1,...,W.w@port2
 406         </CODE>
 407     </BLOCKQUOTE>
 408     <P>
 409       Where "<CODE>V.v</CODE>" and "<CODE>W.w</CODE>" are the SHMIOP
 410       protocol versions associated with the given address
 411       (port).  Currently supported versions are <CODE>1.0</CODE>,
 412       <CODE>1.1</CODE>, and <CODE>1.2</CODE>.
 413
 414     <h3>SHMIOP Address Format</h3>
 415     <P>
 416       SHMIOP addresses are comprised of a port number that the server
 417       should listen on.
 418     <P>
 419       Port numbers range from <CODE>0</CODE> (causes port to be chosen
 420       by operating system) to <CODE>65335</CODE>.  Port numbers less
 421       than <CODE>1024</CODE> on UNIX systems are considered
 422       privileged, and require super-user privileges to access them.
 423       Also be aware that some ports may already be in use by other
 424       applications.
 425     <P>
 426       To have TAO automatically choose an address for a given SHMIOP
 427       endpoint, simply omit the address from the endpoint
 428       specification as follows:
 429     <BLOCKQUOTE>
 430       <P>
 431         <CODE>
 432           -ORBListenEndpoints shmiop://
 433         </CODE>
 434     </BLOCKQUOTE>
 435     <P>
 436       In this case, an SHMIOP endpoint will be set up on a port chosen
 437       by TAO.
 438
 439     <P>
 440     <h3>SHMIOP Endpoint Examples</h3>
 441     <P>
 442       Here are some additional examples of SHMIOP endoints:
 443     <UL>
 444       <LI><CODE>-ORBListenEndpoints shmiop://1.0@0</CODE>
 445       <LI><CODE>-ORBListenEndpoints shmiop://1.0@0,3456</CODE>
 446       <LI><CODE>-ORBListenEndpoints shmiop://1.0@0,3456/foobar=300</CODE></LI>
 447       <LI><CODE>-ORBListenEndpoints shmiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
 448       <LI><CODE>-ORBListenEndpoints shmiop://2020/foobar=12345</CODE>
 449       <LI><CODE>-ORBListenEndpoints shmiop://1.1@</CODE>
 450       <LI><CODE>-ORBListenEndpoints shmiop://1.1@1234</CODE>
 451       <LI><CODE>-ORBListenEndpoints shmiop://1.1@,1.0@1234,1.1@</CODE>
 452     </UL><p>
 453
 454     You <font color="red">must specify the hostname</font>, however,
 455     when using SHMIOP with <a href="INS.html">Interoperable Naming
 456     Service</a> as you would with IIOP.  This is because SHMIOP uses
 457     the hostname to determine the validity of an endpoint.  That is,
 458     it will not try to connect to a remote SHMIOP endpoint locally.
 459     For examples:<p>
 460     <BLOCKQUOTE>
 461       <P>
 462         <CODE>
 463           -ORBInitRef MyService=corbaloc:shmiop:1.1@hostname:port/service_name
 464         </CODE>
 465     </BLOCKQUOTE>
 466
 467     <hr>
 468
 469     <P>
 470     <h2><A NAME="UIOP">UIOP Endpoints</A></h2>
 471     TAO's UIOP pluggable protocol utilizes local IPC (aka UNIX domain
 472     sockets) as its underlying transport mechanism.
 473     <P>
 474     <h3>UIOP Endpoint Overview</h3>
 475     <P>
 476       UIOP endpoints in TAO have the form:
 477     <BLOCKQUOTE>
 478       <P>
 479         <CODE>
 480           -ORBListenEndpoints uiop://V.v@rendezvous_point1,...,W.w@rendezvous_point2
 481         </CODE>
 482     </BLOCKQUOTE>
 483     <P>
 484       Where "<CODE>V.v</CODE>" and "<CODE>W.w</CODE>" are the UIOP
 485       protocol versions associated with the given rendezvous point.
 486       Currently supported versions are <CODE>1.0</CODE> and
 487       <CODE>1.1</CODE>.
 488
 489     <P>
 490       Options are separated from the addresses by a vertical bar
 491       '<CODE>|</CODE>'.  For instance, if an UIOP endpoint should have
 492       a property foobar of 50 associated with it, then the following
 493       endpoint specification could be used
 494     <BLOCKQUOTE>
 495       <P>
 496         <CODE>
 497           -ORBListenEndpoints 'uiop://1.0@/tmp/my_rendezvous_point|foobar=50'
 498         </CODE>
 499     </BLOCKQUOTE>
 500     <P>
 501       Notice that the endpoint is quoted to prevent the shell from
 502       interpreting the vertical bar '<CODE>|</CODE>' as the shell
 503       "pipe" character.
 504     <P>
 505     <h3>UIOP Address Format</h3>
 506     <P>
 507       UIOP addresses are comprised of a rendezvous point the server
 508       should listen on.  The rendezvous point is generally the
 509       <I>full</I> path to the desired UNIX domain socket filename.
 510       Relative paths can be used, their use is discourages.  The
 511       maximum length of the rendezvous point is 108 characters, as
 512       dictated by the POSIX.1g specification for local IPC rendezvous
 513       points.  TAO will truncate any rendezvous point name longer than
 514       108 characters.
 515     <P>
 516       An UIOP endpoint with a rendezvous point with an <I>absolute</I>
 517       path could be:
 518     <BLOCKQUOTE>
 519       <P>
 520         <CODE>
 521           -ORBListenEndpoints uiop:///tmp/foobar
 522         </CODE>
 523     </BLOCKQUOTE>
 524     In this example, the optional protocol version and
 525     endpoint-specific options have been omitted.  The rendezvous point
 526     <CODE>/tmp/foobar</CODE> will be created, in this case.
 527     <P>
 528       An UIOP endpoint with a rendezvous point with a <I>relative</I>
 529       path could be:
 530     <BLOCKQUOTE>
 531       <P>
 532         <CODE>-ORBListenEndpoints uiop://foobar</CODE> <FONT COLOR=RED>(DISCOURAGED)</FONT>
 533     </BLOCKQUOTE>
 534     <P>
 535       Again, rendezvous points with relative paths are discouraged
 536       since it is possible that other rendezvous points with the same
 537       basename exist on a given system, giving rise to potential
 538       ambiguities.
 539     <P>
 540       To make TAO choose a rendezvous point automatically, simply omit
 541       the rendezvous point from the endpoint specification as follows:
 542     <BLOCKQUOTE>
 543       <P>
 544         <CODE>
 545           -ORBListenEndpoints uiop://
 546         </CODE>
 547     </BLOCKQUOTE>
 548     <P>
 549       This will cause an endpoint to be setup in system temporary
 550       directory.  Rendezvous points chosen by TAO are prepended with
 551       "<CODE>TAO</CODE>."  TAO will always choose rendezvous points
 552       with absolute paths.
 553
 554     <P>
 555     <h3>UIOP Endpoint Examples</h3>
 556     <P>
 557       Here are some additional examples of UIOP endoints:
 558     <UL>
 559       <LI><CODE>-ORBListenEndpoints uiop://1.0@/tmp/foo1</CODE>
 560       <LI><CODE>-ORBListenEndpoints uiop://1.0@/tmp/foo,1.1@/home/bar/baz</CODE>
 561       <LI><CODE>-ORBListenEndpoints 'uiop://1.1@/tmp/bar|foobar=300'</CODE></LI>
 562       <LI><CODE>-ORBListenEndpoints 'uiop://|foobar=2'</CODE>
 563       <LI><CODE>-ORBListenEndpoints uiop://1.1@</CODE>
 564       <LI><CODE>-ORBListenEndpoints uiop://1.1@,1.0@/tmp/foo,1.1@</CODE>
 565     </UL>
 566     <hr>
 567
 568
 569     <P>
 570     <h2><A NAME="DIOP">DIOP Endpoints</A></h2>
 571     TAO's DIOP pluggable protocol utilizes UDP sockets instead TCP
 572     sockets (IIOP) as its underlying transport mechanism.  This
 573     protocol supports unreliable datagram communication, which has
 574     certain <A
 575     HREF="../examples/PluggableUDP/DIOP/README">limitations</A>.
 576     <P>
 577     <h3>DIOP Endpoint Overview</h3>
 578     <P>
 579       Since DIOP endpoints in TAO have the same form as
 580       <A HREF="#IIOP">IIOP</A> endpoints, a detailed description is
 581       therefore omitted.
 582     <P>
 583       We recommend explicitly setting port numbers for endpoints
 584       since TAO does not support automatic selection of free endpoints for
 585       UDP sockets.  Instead, the ORB will try to use the same default port
 586       number in every case.
 587     <P>
 588
 589     <h3>DIOP Endpoint-Specific Options</h3>
 590     <P>
 591     TAO supports the following endpoint-specific options that apply only
 592     to DIOP endpoints:
 593
 594       <TABLE BORDER="2" CELLSPACING="2" CELLPADDING= "0">
 595         <TR>
 596           <TH>Option</TH>
 597           <TH>Availability</TH>
 598           <TH>Description</TH>
 599         </TR>
 600         <TR>
 601           <TD>
 602             <CODE>portspan</CODE>
 603           </TD>
 604           <TD>
 605             <CODE>TAO 2.5.12</CODE>
 606           </TD>
 607           <TD>
 608             The <CODE>portspan</CODE> option works identically to the
 609             <A HREF="#IIOP">IIOP</A> <CODE>portspan</CODE> option documented above.
 610             <P>
 611             The format for <CODE>ORBListenEndpoints</CODE> with the
 612             <CODE>portspan</CODE> option is:
 613             <BLOCKQUOTE>
 614               <CODE>-ORBListenEndpoints diop://[</CODE><I>hostname</I><CODE>]:</CODE><I
 615 >initialPort</I><CODE>/portspan=</CODE><I>span</I>
 616             </BLOCKQUOTE>
 617           </TD>
 618         </TR>
 619       </TABLE>
 620     </P>
 621
 622     <h3>DIOP Endpoint Examples</h3>
 623     <P>
 624       Here are some additional examples of DIOP endoints:
 625     <UL>
 626       <LI><CODE>-ORBListenEndpoints diop://1.0@foo1:2345</CODE>
 627       <LI><CODE>-ORBListenEndpoints diop://1.1@:1234</CODE>
 628       <LI><CODE>-ORBListenEndpoints diop://1.1@foo:2020/portspan=30</CODE>
 629     </UL>
 630
 631     <hr>
 632     <P>
 633     <h2><A NAME="SSLIOP">SSLIOP Endpoints</A></h2>
 634     TAO's SSLIOP pluggable protocol facilitates CORBA request
 635     invocation over TLS (formerly known as SSL), and is a drop-in
 636     replacement for the <A HREF="#IIOP">IIOP</A> pluggable protocol.
 637     <P>
 638       The SSLIOP pluggable protocol will actually create two
 639       endpoints: one which is meant to accept plain IIOP requests, and
 640       another meant to accept SSLIOP requests.  As security measure,
 641       IIOP requests will be rejected by default unless the server is
 642       configured to accept them (See the
 643       <A HREF="Security/SSLIOP-USAGE.html">SSLIOP documentation</A> for
 644       additional details).
 645     <P>
 646     <h3>SSLIOP Endpoint Format</h3>
 647     <P>
 648       SSLIOP endpoints basically have the same format as
 649       <A HREF="#IIOP">IIOP</A> endpoints.  The only difference between
 650       the two is that SSLIOP endpoints accept an additional option
 651       that allows one to select the port which will accept TLS
 652       requests.  To make a server open a SSLIOP endpoint on a specific
 653       port use the <CODE>ssl_port</CODE> endpoint option:
 654
 655     <UL>
 656       <LI><CODE>-ORBListenEndpoints iiop://foo:1234/ssl_port=1235</CODE>
 657     </UL>
 658
 659     In this case, an <A HREF="#IIOP">IIOP</A> endpoint would be opened
 660     on port <CODE>1234</CODE> and a SSLIOP endpoint on port
 661     <CODE>1235</CODE>.  If no <CODE>ssl_port</CODE> option is
 662     supplied, a port will automatically be chosen in the same way a
 663     port is automatically chosen for an <A HREF="#IIOP">IIOP</A>
 664     endpoint.
 665
 666     <P>
 667       Note that the protocol label in the above example is
 668       <CODE>iiop</CODE>, <EM>not</EM> <code>ssliop</code>.
 669       Regardless, a SSLIOP endpoint will be opened if the SSLIOP
 670       pluggable protocol was loaded.  Furthermore, the
 671       <CODE>ssl_port</CODE> endpoint option is only valid if the
 672       SSLIOP pluggable protocol is used.
 673
 674     <hr>
 675     <address><a href="mailto:ossama@dre.vanderbilt.edu">Ossama Othman</a></address>
 676   </body>
 677 </html>