CORBA 2.6.1 Programmer's Guide for Java

Alternatively, you can specify a file containing an event-channel object reference. This file could, for example, be created by another program
that created an event channel. If you use a file-based IOR for the event service, the event channel can be on any accessible system. After you
have chosen the event channel to administer, the
esadmin tool displays the Event Channel Status window.
esadmin Tool Commands
You can use the following commands in the esadmin tool GUI:
Admin/Preferences
Admin/Policies
Admin/Trace
File/New
The Event Channel Status window displays statistics for the specified event channel. The statistics displayed are updated periodically. To adjust
the update interval, go to the Admin menu and click Preferences. Set the desired update interval using the dialog displayed.
To display and alter event channel policies, go to the Admin menu and click Policies. This command displays the current policy values. You can
modify these values directly, causing the policies for the event channel to be updated accordingly.
To enable or disable tracing for the specified event channel, go to the Admin menu and click Trace. This command will place a check next to the
menu item, which indicates that tracing is enabled for all selected event channels. When the Trace menu item is checked, tracing is enabled and
the output is directed to the destination specified in the NonStop CORBA Event Service configuration. By default, trace information is written to
the
$NSD_ROOT/log/es.log file, as specified by your NonStop CORBA system configuration. Be sure to use tracing only when needed; leaving
tracing enabled for long periods can result in unnecessarily large trace logs.
To administer additional event channels, go to the Admin menu and click New. From the dialog displayed, select the additional event channels
you want to monitor.
Viewing the Naming Service
You can use the NonStop Distributed Component Console or the ns_browse tool to look at the entries stored in the Naming Service database.
The Naming Service database can be viewed as a tree of naming contexts. A naming context is an object that contains a set of name
bindings. A binding is a name-to-object association. Because a context is like any other object, it can also be bound to a name in another
naming context. This arrangement allows for the creation of a tree that has nodes as contexts (or objects) and leaves as names. When NonStop
CORBA is installed, a default naming tree gets created. The root of this naming tree is called the root naming context.
A node in the naming tree can be identified by a sequence of names relative to a given parent node. The
ns_browse tool uses the node name (a
context-name when the node is a context or an object-name when the node is an object) as input to some of the tool's operations.
Each component of the name sequence (a tree leaf) is a CosNaming Name consisting of an id string and a kind string. Thus a context-name or
object-name is specified as a list of
id and kind string pairs, for example, id1 kind1 id2 kind2. Note that the kind string can be specified as a
empty string ("") to indicate no kind specified.
The Naming Service does not store an actual object in the binding. Instead, it stores an object reference. Object references input to and output
by the
ns_browse tool are string representations of these object references. These string references are called "stringified interoperable object
references" or stringified IORs, and they can be displayed by using
showior.
Using the Console to View the Naming Service
The Console allows you to perform the following tasks for the Naming Service: