StayLinked as a company has spent decades providing hosted terminal emulation solutions to our customers including some of the most recognized company names in the world. With version 17 of StayLinked SmartTE, we’re now pleased to offer a new connection alternative within SmartTE, directly from the mobile device to the telnet host.
While this goes against our history of reliability-centric server architecture, it does offer flexibility. Regardless of the situation, simplicity, reduced overhead, short implementation schedule, anything that the situation demands, you can now use the same SmartTE client to connect to a host, reliable SmartTE server or go from the same client directly to a telnet host.
As it always has, Direct connections are going to necessitate a fast and reliable network and dropped sessions can still cause record locks. If that’s an issue, we have a solution and you can always rely on a SmartTE server to host and manage those session to deliver screen updates to the mobile devices that will remotely control those session and pick up where they left off when packets are dropped and WiFi roams at just the wrong moment.
StayLinked can’t provide session reliability in a direct-to-host session, because that was never part of the terminal emulation design. Never has been.
Want to use Direct all the time? No problem. Utilizing the same architecture as SmartBrowser, Direct can use SmartHub to check in and get a long-term license, show up in your asset control, check in for updated configuration, or upload any load log files. If you want, it can just keep the long-term license and stay on its own. SmartHub v3.0 is required in support for SmartTE Direct for standalone installations.
Hosted – Traditional Reliable StayLinked SmartTE
When reliability is required and centralized configuration, management, and visibility improves overall business efficiency. Terminal emulation sessions exist between the SmartTE server and emulation host with mobile devices acting as remote control devices. Mobile devices get remote-desktop like controls and network interruptions, device reboots, and wireless roaming are not related to terminal emulation traffic.
Direct – No SmartTE Server Required
From the mobile device the SmartTE client connects directly to the terminal emulation host. If your host application provides session persistence based on user accounts, or uses the device's IP from the TCP packet header for application functions, direct may be all you need.
If your direct sessions experience session drops, you can always add the SmartTE server at any time at no cost to take advantage of session reliability and other features it can provide.
Licensing and Configuration
Direct sessions will rely on SmartHub just as SmartBrowser does. Utilizing SmartHub for licensing and configuration. Simple telnet configuration is available on the client, while a more detailed subset of telnet configuration is available with the release of SmartHub v3.0. The SmartTE Server handles all licensing and configuration for SmartTE clients in a Hosted session environment.
The SmartTE Administrator v17 release will provide options for package exports enabling a majority of SmartTE standard features for Direct sessions, available for import at the device level or for distribution by SmartHub.
Share the post "SmartTE Connections Hosted vs Direct"