Hi,
We r doing a project where Visual Basic application will be running on citrix server and will be communicating to the Unisys mainframe through TCP/IP socket connection.
The broad architechture is; around 1000 thin clients connected to 30 Metaframe Servers sitting on Windows 2000, and all the 30 Metaframe servers connected to the Unisys Mainframe. The mainframe, recognises only 30 IP addresses of Metaframe. 1000 thin clients have static IP addresses.
Data from the client contains the IP address as a part of header information.
So, we plan to build a system where data enquired from the client talks to an application on Metaframe and converts the IP address present in the header to that of Metaframe's IP address, then communicating to the mainframe.
We need to keep the connection to the mainframe persistent as many thin clients will be accessing one metaframe server to communicate to mainframe.
Our problems are :
1) how to keep a persistent connection open to the mainframe from metaframe server ?
2) how will the data be routed correctly after getting back information from mainframe to the correct thin client ? remember the IP address in the header info of the data coming from mainframe has that of metaframe server and not of thin client.
I would appreciate if anyone can tell us some better solution than what we have thought. we r still in the design phase of project. we want to capitalize on all the features of metaframe, load balancing, ISM etc keeping our limitation in mind (unisys mainframe can recognise only 30 valid IP address and can open only 30 telnet ports)
Thanks,
GS.
ph # (517)327 2674
We r doing a project where Visual Basic application will be running on citrix server and will be communicating to the Unisys mainframe through TCP/IP socket connection.
The broad architechture is; around 1000 thin clients connected to 30 Metaframe Servers sitting on Windows 2000, and all the 30 Metaframe servers connected to the Unisys Mainframe. The mainframe, recognises only 30 IP addresses of Metaframe. 1000 thin clients have static IP addresses.
Data from the client contains the IP address as a part of header information.
So, we plan to build a system where data enquired from the client talks to an application on Metaframe and converts the IP address present in the header to that of Metaframe's IP address, then communicating to the mainframe.
We need to keep the connection to the mainframe persistent as many thin clients will be accessing one metaframe server to communicate to mainframe.
Our problems are :
1) how to keep a persistent connection open to the mainframe from metaframe server ?
2) how will the data be routed correctly after getting back information from mainframe to the correct thin client ? remember the IP address in the header info of the data coming from mainframe has that of metaframe server and not of thin client.
I would appreciate if anyone can tell us some better solution than what we have thought. we r still in the design phase of project. we want to capitalize on all the features of metaframe, load balancing, ISM etc keeping our limitation in mind (unisys mainframe can recognise only 30 valid IP address and can open only 30 telnet ports)
Thanks,
GS.
ph # (517)327 2674