[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-developer
Subject:    Re: [jacorb-developer] specifying IP address for use in IOR generation?
From:       alex agranov <agranov () redconnect ! net>
Date:       2000-01-12 20:50:12
Message-ID: 387CE904.14EC17A5 () redconnect ! net
[Download RAW message or body]

Gerald,

Thanks for the indepth explanation.  The OAIAddr property should come in
very handy indeed (I had not seen it in the docs?).  As for the Imr
information and how it affects IOR creation, that too should be very
useful.  I haven't had a chance to play with the Appligator yet, but I'm
sure it's quite nice.  The firewall issues are revisited in Corba 3
anyway, I suppose...

thanks again,
alex

Gerald Brose wrote:

> Hello,
>
> there are two answers to this question. The first addresses simple
> address and port selection while the second has to do with
> "proxyfying" IORs.
>
> First, JacORB accepts two properties that affect the IP address and
> port number the server process accepts requests on. If set, this
> address and port number are of course also used for the addressing
> information embedded in IORs generated in that server process.
>
> These two properties are OAPort and OAIAddr and can can be
> set in the properties file, on the command line or in the Properties
> argument to ORB.init(). OAIAddr is used to select an address on a
> multi-homed host. OAPort can be used to make sure a server comes up
> on the same port every time it is started.
>
> Second, the ORB automatically inserts different server addresses in
> IORs in the following cases:
>
> - the POA generating the reference has a persistent life time
>   policy *and* the Implementation Repository is up and running.
>   In this case, the ORB automatically registers the POA with the
>   ImR and embeds the ImR's address rather than the servers address
>   in the IOR. (To make the server come up on demand, a startup
>   command has to be registered with the ImR)
>
> - For an applet *client*, all IORs must be and are automatically
>   proxified to an Appligator running on the applet host because
>   otherwise applets are preventing from connecting to target objects
>   by browser security managers. This has, of course, nothing to do
>   with IOR generation, just with usage.
>
> For firewall usage, additional addressing information would have
> to be embedded in special IOR component profiles, but this is not
> currently supported or recognized by JacORB.
>
> Hope this helps, Gerald Brose.
>



[prev in list] [next in list] [prev in thread] [next in thread]