CORBA 2.6.1 Administration Guide

With this configuration the single port can be serviced by up to 16 actual processes with only one Comm Server pool and only one configuration
database entry. Similarly, up to 16 Location Service Daemon (LSD) processes can be configured to avoid a potential LSD bottleneck.
The GIOP over TS/MP protocol can be used in combination with Parallel Library TCP/IP to provide two different dimensions of scalability. As
shown in Figure 1–8, Parallel Library TCP/IP provides scalability by allowing multiple processes to listen at one port. If you configure multiple
ports (using multiple ServerNet adapters), TS/MP provides scalability by allowing you to configure one process per port.
For more information about the architecture and features of Parallel Library TCP/IP, see the TCP/IP (Parallel Library) Configuration and
Management Manual, particularly the section on configuring Parallel Library TCP/IP for complex and heavy-use environments.
Location Service Daemon (LSD)
The Location Service Daemon (LSD) is a component that often acts as a first point of contact for network clients. The LSD uses NonStop
CORBA configuration information along with information in the request to redirect the request to the correct server or Comm server. Following
the initial interaction with the LSD, subsequent client requests should not require interactions with the LSD. When the LSD determines that a
Comm server should handle the request, the LSD selects an appropriate Comm server. Selection of a Comm server is made based on several
factors including:
The IP address of the client making the request
The number of available Comm servers
The current load being handled by each Comm server
Configuration decisions made by the system administrator
Once an association is made between a particular client IP address and a Comm server, the same association is used for subsequent requests
from the same client.
Interoperable Location Service Daemon (ILSD)
The Interoperable Location Service Daemon (ILSD) is a component of the Interoperable Naming Service. The ILSD services requests for name
resolution for names in the Uniform Resource Locator (URL) format. When the ILSD receives such a request, it returns a forwarding reply
containing the object reference of the named object. For requests involving names that use the
corbaloc style of URL, the ILSD returns the
object reference based on locally stored object references. For requests involving names that use the
corbaname style of URLs, the ILSD enlists
support of the Interoperable Naming Service to produce the object reference that is returned to the caller.
Bootstrap Daemon (BSD)
The Bootstrap Daemon (BSD) is a component of the Interoperable Naming Service. The BSD is needed for interoperability with other ORBs
using the Bootstrap protocol. The BSD protocol provides operations for resolving an initial object reference and for listing the supported initial
reference ids. Interoperable client ORBs send a request to an initialization agent. The agent replies to the client ORB with the requested
information. The IDL interface provides two operations, a
get(), which accepts an ObjectId and a list(), which accepts no arguments. The IDL
interface for the two operations is as follows: