CORBA 2.3.3 Programmer's Guide for Java

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.3 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):
Naming Service (implemented as a server pool or NonStop TS/MP server class). NonStop
CORBA implements the Interoperable Naming Service specified in the CORBA 2.4 specifications,
with the exception that the Resolve Initial References (RIR) URL is not supported.
●
Event Service. A standard application service (one of the OMG Common Object Services) for
asynchronous communication among objects
●
Transaction Service. NonStop CORBA implements the Transaction Service by means of
components that collaborate with the Transaction Management Facility (TMF) on the NonStop
Himalaya system. These components include special language-specific client stubs, a Transaction
Service process that can run as a TS/MP server pool, and a singleton transaction ID broker process.
The Java client stub (JTS) supports the Java Transaction Service (JTS) API.
●
You can configure and monitor NonStop CORBA components by using the NonStop Distributed
Component Console, a GUI-based configuration tool. For some application-specific configuration
settings you also use a command-line interface as described later in this manual.
For more information about the NonStop CORBA architecture, see Architectural Walkthrough in this
guide and the architecture section of the NonStop CORBA 2.3 Administration Guide.
NonStop CORBA Programming Environments
You can develop applications on the NonStop Himalaya system directly. Alternatively, you can use
JORB Lite to develop and test on a workstation, then move the tested application to the NonStop
Himalaya system (JORB Lite is not supported for production use). For more information on JORB Lite,