The naming service

DIET uses a standard CORBA naming service for translating an user-friendly string-based name for an object into an Interoperable Object Reference (IOR) that is a globally unique identifier incorporating the host and port where the object can be contacted. The naming service in omniORB is called omniNames and it must be launched before any other DIET entities. DIET entities can then locate each other using only a string-based name and the host:port of the name server.

To launch the omniORB name server, first check that the path of the omniORB libraries is in your environment variable LD_LIBRARY_PATH, then specify the log directory, through the environment variable OMNINAMES_LOGDIR (or, with omniORB 4, at compile time, through the -with-omniNames-logdir option of the omniORB configure script). If there are no log files in this directory, omniNames needs to be intialized. It can be launched as follows:

~ > omniNames -start

Tue Jun 28 15:56:50 2005:

Starting omniNames for the first time.
Wrote initial log file.
Read log file successfully.
Root context is IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e61
6d696e67436f6e746578744578743a312e300000010000000000000060000000010102000d0000003134
302e37372e31332e34390000f90a0b0000004e616d655365727669636500020000000000000008000000
0100000000545441010000001c0000000100000001000100010000000100010509010100010000000901
0100
Checkpointing Phase 1: Prepare.
Checkpointing Phase 2: Commit.
Checkpointing completed.

This sets an omniORB name server which listens for client connections on the default port 2809. If omniNames has already been launched once, ie there are already some log files in the log directory, using the -start option causes an error. The port is actually read from old log files:

~ > omniNames -start

Tue Jun 28 15:57:39 2005:

Error: log file '/tmp/omninames-toto.log' exists.  Can't use -start option.

~ > omniNames  

Tue Jun 28 15:58:08 2005:

Read log file successfully.
Root context is IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e61
6d696e67436f6e746578744578743a312e300000010000000000000060000000010102000d0000003134
302e37372e31332e34390000f90a0b0000004e616d655365727669636500020000000000000008000000
0100000000545441010000001c0000000100000001000100010000000100010509010100010000000901
Checkpointing Phase 1: Prepare.
Checkpointing Phase 2: Commit.
Checkpointing completed.