TPS/TN3270 Server

The architecture of TPS/TN3270 Server comprises several key components designed for high availability and scalability. The core component is the TN3270 Server process, which listens for incoming TN3270 client connections on a configurable port. The configuration manager handles the loading and saving of configuration settings, typically stored in text-based configuration files.

These files define parameters such as port numbers, host addresses, security settings, and logging levels. The session manager is responsible for creating, maintaining, and terminating user sessions. Each session represents a connection between a TN3270 client and the mainframe host.

The logging module records server activities, including connection attempts, user actions, and security events. Logs are essential for monitoring and security analysis. Communication between components is primarily internal, using shared memory and inter-process communication (IPC) mechanisms.

The server uses the TN3270 protocol over TCP/IP for communication with clients and the host. Security is ensured through TLS/SSL encryption. Authentication is handled through user ID and password, with options for LDAP and Kerberos integration.

The server does not use a database for persistent storage; configuration is stored in text files. Network requirements include an open port for TN3270 traffic (typically port 23) and the ability to reach the mainframe host. The CLI provides commands for starting, stopping, and configuring the server.

Example CLI commands include `start_server`, `stop_server`, `configure_connection`, and `show_status`. The architecture is designed to be modular, allowing for future enhancements and integrations.