[omniORB] A question on NameService.

[Mohan]

Thanks for the information. It worked for me by adding hostname & port no.
in the registry of the computers(windows) where the client is running.
----- Original Message -----
From: "Ulf Stoermer" <kz_ulf@emi.yamaha.co.jp>
To: "Mohan" <rmohan@ice-com.com>
Sent: Friday, July 26, 2002 5:39 AM
Subject: RE: [omniORB] A question on NameService.


> Hi Ram,
>
> that what you want is possible, all you need to
> do is setup the client correctly.
>
> The name service just needs to run once on
> a network and can be either on Unix/Linux or
> even Windows, doesn't matter.
>
> But in order to let the client contact the name
> service without the command line option you
> need to tell the client where to find the name
> service via some kind of configuration.
> E.g. under Linux you have to create a config
> file on a known location on the client machine.
> The readme file says:
> <in>
> You need to tell other omniORB programs where to find the Naming service.
> With omniORB 3 and later, you use the interoperable naming service. Create
a
> file omniORB.cfg containing:
> ORBInitRef NameService=corbaname::my.host.name
>
> where my.host.name is the name of the machine running omniNames. If you
have
> specified a non-default port, use something like
>
> ORBInitRef NameService=corbaname::my.host.name:12345
>
> Set the environment variable OMNIORB_CONFIG to contain the full path name
of
> the file omniORB.cfg. For example,
> OMNIORB_CONFIG=/wib/wob/omniORB.cfg; export OMNIORB_CONFIG
> <out>
>
> If you have a Windows client then the same
> information is stored in the registry. The readme
> for Windows says:
> <in>
> Start the tool REGEDT32.EXE (on NT) or REGEDIT.EXE (on Windows '95).
Select
> the key HKEY_LOCAL_MACHINE\SOFTWARE\ORL\omniORB\2.0 (or create it if it
> doesn't exist). Add a string value (known as a REG_SZ data type when using
> REGEDT32) called ORBInitRef , and give it the value
>
> NameService=corbaname::my.host.name
>
> where my.host.name is the name of the machine running omniNames. If you
have
> specified a non-default port, use something like
>
> NameService=corbaname::my.host.name:12345
>
> The registry entries must be duplicated on all machines that will run
> omniORB programs. It is only necessary to run one instance of omniNames on
> your network.
> <out>
>
> Cheers
>
> Ulf
>
> > -----Original Message-----
> > From: omniorb-list-admin@realvnc.com
> > [mailto:omniorb-list-admin@realvnc.com]On Behalf Of Mohan
> > Sent: Thursday, 25 July 2002 8:19 PM
> > To: omniorb-list@realvnc.com
> > Subject: [omniORB] A question on NameService.
> >
> >
> > Hi,
> >
> > I am able to write a client/server programs communicate thru name
> > service, I
> > followed the example eg3_clt, eg3_impl for it to work.
> > The problem I am facing is while I run client & server in 2 different
> > machines on the network my client program is not able to resolve
> > the initial
> > reference unless I pass -ORBInitialhost=<hostname>
> > -ORBInitialPort=12345 in
> > the command line. . But if I run the client program on the same machine
> > where I run server, I dont need these info, it works fine without any
> > command line arguments.
> > This kind of procedure will not work for my project. I should be
> > able to run
> > the client program with no command line arguments and no configurations
in
> > the target machine where the client program will be running. I should be
> > able to specify all of the required nameservice configurations on
> > one single
> > machine (may be on the server) and should be able to run the
> > client program
> > in different machines on the network. Can this be achieved? Please help.
I
> > need this information very URGENTLY.
> >
> > Thanks
> > Ram
> >
> > _______________________________________________
> > omniORB-list mailing list
> > omniORB-list@realvnc.com
> > http://www.realvnc.com/mailman/listinfo/omniorb-list
> >
>
>