CORBA 2.6 Programmer's Guide for Java

J2EE, the Bootstrap Service Daemon provides a standard interoperable protocol for resolving an
initial reference ID and for listing the supported initial reference IDs. The BSD configuration is
held in the configuration database.
Configuration database
This database is built during the installation and configuration of NonStop CORBA. It contains an
entry for the Naming Service that includes an IOR used by
ORB::resolve_initial_references. The database is used to maintain the TCP/IP
addresses for the Comm Servers and the LSD. It is also used to maintain a map table for
associations between the Comm Servers and remote client hosts. It also contains a Comm Server
load table. Finally, it is used to maintain application configurations. You modify the configuration
database directly by using the NonStop Distributed Component Console or by using the
cfgmgt tool.
Comm Servers
Comm Servers can be thought of as gateways allowing network clients to communicate with
application servers on the NonStop system. They also act as TCP/IP network resource
concentrators, mapping all connections from a client address to the same Comm Server. Comm
Servers take advantage of TS/MP capabilities and are configured as TS/MP (Pathway) server
classes. You configure Comm Servers to use various transport protocols depending upon your
application design.
Location Service Daemon (LSD)
The LSD acts as an Internet InterORB protocol (IIOP) port mapper. The LSD uses an object's
object key to determine how to forward requests. The LSD configuration is held in the
configuration database. The LSD updates the database for each new client-address/Comm-server
mapping, and it updates existing mappings daily.
Interoperable Location Service Daemon (ILSD)
The ILSD acts as a forwarding agent for the Interoperable Naming Service. Like the BSD and
LSD, ILSD uses an object's object key to determine how to forward requests. If the request is
aimed at a corbaloc URL, the ILSD forwards the request to the URL named in the key string. If
the request is aimed at a corbaname URL, the ILSD forwards the request to the reference obtained
by resolving the stringified name against the CosNaming::NamingContext specified in the
key string.
Interface Repository (IR) Daemon
The Interface Repository provides distributed access to one or more databases as persistent
storage for Interface Repository information.
Refer to the NonStop CORBA 2.6 Administration Guide for a more complete description of the above
NonStop CORBA components.
In addition to the components described above, your applications can make use of the following
Common Object Services components provided as part of NonStop CORBA (these services are
CORBA applications like any other):