Network Scenarios

The following section contains three different Session Persistence Server implementation scenarios. Each scenario contains a network diagram, configuration parameters, and a brief discussion about the scenario.

Scenario 1: Multiple Clients to a Single Host

In this model, clients connect to a single host through a proxy server. This example is based on VT emulation with no reconnect string.

Configure the parameters in the Session Persistence Server configuration file as follows:

proxyservice proxy1
listen 10.50.0.200:4430
server VT

 

hostservice VT

connect 10.50.0.250:23

Configure the host profile on the client to direct terminal emulation traffic to 10.50.0.200:4430.

Scenario 2: Multiple Clients to Multiple Hosts

In this model, clients can connect to one of three different hosts through a single proxy server. This example is based on VT emulation with no reconnect string.

Configure the parameters of the Session Persistence Server configuration file as follows:

proxyservice proxy1
listen 192.168.1.25:4430
server vt1, vt2, vt3

 

hostservice vt1
connect 192.168.1.50:23

 

hostservice vt2
connect 192.168.1.100:23

 

hostservice vt3
connect 192.168.1.150

 

proxy //proxy entry for connection to Host 1
listen 192.168.1.25:2301
server 192.168.1.50:23

Add three host profiles in the client. Specify the Session Persistence Server in the TermProxy 1 tab of each host profile if you are using the TE Client, or on the Security tab if you are using the Velocity Console.

Scenario 3: Multiple Clients to Proxy Server/Host

In this model, several clients connect to a system that hosts the Telnet service and the Session Persistence Server application.

Configure the parameters of the Session Persistence Server configuration file as follows:

proxyservice proxy1
listen 10.50.0.250:4430
server as400

hostservice as400
connect 10.50.0.250:23
reconnect-string F3
codeset EBCDIC

Configure the host profile to direct session traffic to 10.50.0.250:4430.