CORBA 2.6 Administration Guide

Test %1 %2 %3
172.26.27.80 is the host IP address, 4506 is the BSD port number. NonStop CORBA does not use the BSD default port of
900, but uses a port dynamically assigned during installation. The port number can be altered using the Console or the
cfgmgt utility to modify the bsd1@ORB entity.
Interface Repository Database
The Interface Repository (IR) is a set of files that contain definitions of object interfaces hosted on your NonStop CORBA
application servers. Information in the IR can be used by clients that access servers using the Dynamic Invocation Interface
(DII), as defined by the CORBA specifications. You access the IR database programmatically through the interface defined
in the CORBA Interface Repository specification.
The Common Object Services
NonStop CORBA implements the following CORBA services:
Naming Service●
Event Service●
Transaction Service●
Naming Service
The NonStop CORBA Naming Service implements the Naming Service based on the OMG Naming Service Specification
1.2, with one minor exception as noted in the NonStop CORBA 2.6 Programmer's Reference. The Naming Service provides a
repository for the names and locations of NonStop CORBA application objects.
The Naming Service enables developers to register object names at runtime. In the Naming Service database, naming
contexts and their associated object references are organized into a hierarchical namespace. Client applications can then use
the Naming Service to discover the names and object references for objects they wish to use.
The NonStop CORBA Naming Service is fully and transparently integrated with TS/MP and the Transaction Management
Facility (TMF), making the Naming Service fully scalable, reliable, and performance-oriented.
The Naming Service consists of the Naming Server executable program (deployed as a server pool) and its respective
Naming Service database along with the Interoperable Naming Service Daemon (ILSD). The Naming Server maintains the
Naming Service database using key-sequenced Enscribe files. Applications can bind names to objects and retrieve them by
using the CORBA-defined object interface to the Naming Service.
Event Service
The NonStop CORBA Event Service is implemented based on the OMG CORBA Event Service specification version 1.1.
The Event Service provides asynchronous communication among CORBA objects.
The Event Service allows supplier objects to communicate through an event channel, notifying any number of consumer
objects when events they subscribe to take place.
The Event Service consists of the Event Service executable, which is also deployed as a server pool. Applications interact
with this server pool by using the CORBA-defined object interfaces to the Event Service.
Transaction Service
The NonStop CORBA Transaction Service (OTS) is implemented based on the OMG Transaction Service specification
version 1.1. The Object Transaction Service is an object-oriented, transaction processing system. Using HPs proven