[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.hyades] Q: Hyades Data Collector and firewalls

We have problems with way how Hyades Data Collector works with connections. Our client needs to connect to RAC through firewall. The problem is that HDC attempts to connect back to client and fails because of firewall.

We are currently investigating possibility of developing patch to LTA and possibly HDC. LTA will use single BEEP connection to connect to HDC. BEEP is a transport protocol that allows organizing several virtual connections through one TCP connection, and these virtual connections might be initiated by either party. See http://www.beepcore.org/ for references to specifications and implementations.

The way that we currently see is the following:

1. Add preference page on which it is possible to specify BEEP proxy for specific RAC host.

2. Create proxy process that receives the single connection and open/closes server ports according to commands from client. Incoming input connections are forwarded to LTA. This process is supposed to be run in the same security domain as HDC.

3. Patch LTA code to use abstract access to RAC sockets and wrap real sockets into it.

4. If hostname matches one specified in proxy preferences, use BEEP based implementation instead.

We would like to know if this solution is feasible and what difficulties are expected with its implementation. We would also like to know about places to watch in the implementation.

Constantine