[omniORB] echo examples

Brecht Vermeulen Brecht.Vermeulen@rug.ac.be
Sun, 17 Sep 2000 16:48:11 +0200 (MET DST)


Walter,

> 
> No. I will check the doc's when I can and verify that it points to the
> right places.

in /etc/omniORB.cfg you have to put :
ORBInitialHost hostname (where hostname is the hostname where your
nameservice is running)
ORBInitialPort 8088   (or other port depending your config)

> 
> I thought -- hoped - that the port number was the important part.  How
> will a remote client find out the information if a file in /etc has it? 

Well each client needs its own configuration of course (e.g. for omniORB
it is the /etc/omniORB.cfg file pointing to the Naming Service)
You can compare it with DNS (Domain Name System), you also have to
configure your computer to know the IP address of the DNS server which can
tehn provide the IP-hostname translation for you.

> Ultimately I am trying to develop an iiop application and will need to
> develop the connections without prior knowledge of specifics.
> 
> Perhaps I am misunderstanding the iiop's interface and should develop a
> socket server to give out the ior to any clients -- then they can have the
> port number and other via a handshake.

The Name Service is constructed for this. But if you did this with a
socket server, you also would have to configure the IP address of theis
socket server, so it remains the same.

> But I had hoped -- I haven't yet found a clear doc on iiop implementation
> that details features and functions -- that iiop was transparently
> handling the connection information and that (in this case) the name
> service would be found by a default set of globally know information which
> again I was assuming was known by the name service.
>

This would be strange, the name service would be found by information
which would be present in the name service. Kind of deadlock situation
:-).


best regards;
Brecht

> >On 15 Sep 2000, David Walter wrote:
> >
> >> 
> >> 
> >> After an initial compile and build on Debian/GNU/Linux I am trying to
> >> test the installation with the examples.
> >> 
> >>  eg1.cc        okay
> >>  eg2_clt.cc    okay
> >>  eg2_impl.cc   okay
> >>  eg3_clt.cc    oops*
> >>  eg3_impl.cc   "
> >>  eg3_tieimpl.cc"
> >> 
> >> 
> >>  ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809 &
> >> Fri Sep 15 15:29:55 2000:
> >> 
> >> Starting omniNames for the first time.
> >> 
> >> Fri Sep 15 15:29:56 2000:
> >> 
> >> Wrote initial log file.
> >> Read log file successfully.
> >> Root context is IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000001000000000000002b000000010100000f0000003132382e3233302e3230392e37310000f90a00000b0000004e616d6553657276696365
> >> Checkpointing Phase 1: Prepare.
> >> Checkpointing Phase 2: Commit.
> >> Checkpointing completed.
> >> 
> >> ps aux | grep -i omni
> >> 
> >> root     11402  0.0  2.7  2616 1724 pts/11   S    15:29   0:00 ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809
> >> root     11403  0.0  2.7  2616 1724 pts/11   S    15:29   0:00 ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809
> >> root     11404  0.0  2.7  2616 1724 pts/11   S    15:29   0:00 ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809
> >> root     11405  0.0  2.7  2616 1724 pts/11   S    15:29   0:00 ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809
> >> root     11406  0.0  2.7  2616 1724 pts/11   S    15:29   0:00 ../../../bin/i586_linux_2.0_glibc2.1/omniNames -start 2809
> >> root     11504  0.0  0.7  1112  444 pts/11   S    15:39   0:00 grep -i omni
> >> 
> >> It looks as if the name service is running.
> >> 
> >> but:
> >> 
> >> $ ./eg3_impl
> >> Caught CORBA::SystemException.
> >> 
> >> 
> >> Is there something that I am missing?
> >> 
> >> ../../../bin/i586_linux_2.0_glibc2.1/nameclt -ior IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000001000000000000002b000000010100000f0000003132382e3233302e3230392e37310000f90a00000b0000004e616d6553657276696365 list
> >> 
> >> gives nothing back.
> >> 
> >> The ior seems correct
> >> 
> >> ../../../bin/i586_linux_2.0_glibc2.1/catior  IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578744578743a312e30000001000000000000002b000000010100000f0000003132382e3233302e3230392e37310000f90a00000b0000004e616d6553657276696365 
> >> Type ID: "IDL:omg.org/CosNaming/NamingContextExt:1.0"
> >> Profiles:
> >> 1. IIOP 1.0 128.230.209.71 2809 "NameService"
> >> 
> >> Thanks so much in advance for any assistance.
> >> 
> >> David
> >> 
> >> 
> >
> >
> >
> 
> --
> Respectfully:
>                                       David Walter
> Karma: Whenever you are there you go. dwalter@syr.edu
> Office: CST::1-236                    Phone: (315) 443 3046
> 
> 
> 
>