If your Telnet server does not support TLS, and if you
are running the
Host On-Demand server on one of the operating systems
on which the Redirector supports secure sessions (see
Operating systems supported by the Redirector), you can configure the
Host On-Demand Redirector
to provide the TLS support.
Table 1. Tip |
Many Telnet servers support TLS
(for example, IBM Communications Servers on zSeries, IBM System i,
AIX, or NT). If your Telnet server supports TLS, we strongly recommend
using your Telnet server. If your Telnet server does not support TLS,
the Communications Server for AIX Redirector offers a more scalable
alternative to the Host On-Demand Redirector. |
The Redirector acts as a transparent Telnet proxy that uses port
remapping to connect the
Host On-Demand server to other Telnet servers.
Each defined server can configure a set of local-port numbers. Instead
of connecting directly to the target Telnet server, a client connects
to the server and port number. The Redirector maps the local-port
number to the host-port number of the target and makes a connection.
Table 2. Recommendation |
The recommended solution for a Telnet proxy
is to use Load Balancer, a feature of WebSphere Application Server's
Edge Components, or a similar product that provides address translation
as part of the overall firewall solution, instead of the Host On-Demand Redirector. |
