Re: Tunneling the Oracle native Protocol through HTTP

[Quoted] Jörg Werner wrote in message <3587D868.D84120C7_at_intershop.de>...
>Consider the following scenario:
>
>A database client talks to a database server using the
>native database protocol. Now we want to separate both
>client and server and put them at different internet
>sites which are each protected by a firewall. Let us
>assume the HTTP protocol is - by administration - the
>only trusted protocol to get through the firewalls.
>
>Are there any products/tools out there which allow
>the native database protocol to be tunneled within
>HTTP packets? If not, do you have any idea how we can
>successfully do it ourselves (certainly the native
>protocol is non-public)?
>
>Thanks in advance for all your help.
>

[Quoted] I don't think that HTTP would be a good choice. Why HTTP???????? What advantages ?
[Quoted] [Quoted] In my opinion there's no real need to do that. SQL*Net 2 (or 8) which is native Oracle network protocol may be tunneled between networks much much easier.
For example by simply forwarder as a proxy. I've tested plug-gw from TIS Firewall Toolkit against sqlnet listener on screened unix machine and that works fine.
Yeah, in your case you'll need another open TCP port on firewall except of HTTP, but if you want to connect inside machine via one of them it simply does not matter. That's much easier and works with no sophisticated software.

Piotr

--
 Piotr Kolodziej
 <pkol_at_otago.gda.pl>
 * My voice. My private opinion. *