Using OmniORB for component distribution

Hi,

I am trying to use the OmniORB implementation to distribute my components.

While TAO was quite easy to configure (just starting the Naming_Service, and defining the NameServiceIOR variable), I have not found any "accessible" information on how to configure omniORB...

Could anyone tell me how to configure omniORB?
What are the useful options of omniNames?
How to tell the deployer-corba where the NameService is located?

Thanks.

Charles

Using OmniORB for component distribution

On Mar 18, 2009, at 06:16 , charles [dot] lesire [..] ... wrote:

> Hi,
>
> I am trying to use the OmniORB implementation to distribute my
> components.
>
> While TAO was quite easy to configure (just starting the
> Naming_Service, and defining the NameServiceIOR variable), I have
> not found any "accessible" information on how to configure omniORB...
>
> Could anyone tell me how to configure omniORB?
> What are the useful options of omniNames?
> How to tell the deployer-corba where the NameService is located?

Mine worked out of the box with the no change to my environment from
ACE/TAO. This was on Ubuntu with the packaged OmniORB, which starts
its naming service automatically.

Set your same environment variable to set the IOR data re host:port
(same as ACE/TAO) : ie in bash

export NameServiceIOR=corbaloc:iiop:localhost:2809/NameService

The Ubuntu OmniORB package does

/usr/bin/omniNames -errlog /var/log/omniorb4-nameserver.log

HTH
S