[teiid-users] Teiid host resolution change after the M3

[Ramesh Reddy]

On Mon, 2010-04-19 at 10:24 -0400, Ken Johnson wrote:
> So by default, the server will not be able to accept remote JDBC 
> connections?  I see the security benefits of this behavior but also 
> end-user inconvenience.  
Yes, I agree that this is little inconvenience to the users out of the
box. The primary driving factors were

1) Security
2) Align the host resolution to be similar to the JBoss AS, so that
users are not given two different choices in configuring the bind
address.

The logic changed *if* the host name resolves "localhost" (mostly
developer machines), however like in any typical shared server
environment would have their host name specified, so they will resolve
to proper LAN address that will be reachable by the known name. 

> Does the hostname or IP specified with -b have 
> to match *exactly* with the hostname string in the JDBC URL used by 
> client applications?  Or will it work as long as it resolves down to
> the 
> same IP address (I assume the latter but just checking)?
> 
If they resolve to same IP that would be enough. If the sever is started
with "0.0.0.0" then any resolved IP on that machine will be fine. Also,
note that user could still provide the host name/ip in the Teiid
configuration to override the default behavior.

> Also, how will this impact Teiid firewall configuration and dynamic
> IP 
> environments like Amazon EC2 where internal and external addresses
> differ? 
I do not know. Do these offer IP forwarding services may be?

Ramesh..