SAPConsole and Georgia Softworks Telnet server

Georgia Softworks Telnet server has session saver option which will hold the session in the event that the RF device loses connection. To do this it requires each RF device user to sign in to the RF Device twice. First they have to authenticate to the telnet server then to the SAP system. To authenticate to the Telnet server the user must have either a local account on the server or a domain account with local login rights. It seems like this requires a lot of account management. Does this seem right? Is there a better way to maange the Telnet accounts or to interface an RF wireless device into SAP?

Popular White Paper On This Topic

Hello Johnathan,
Yes, you can bypass a double login routine by users. There is a GS_Logon.txt file where you are able to add single or ranges of IP addresses to autologin, with one standard name and password.
Regards,
Richard

I wish it was that simple, I am aware of the autologin but that eliminates the ability to use the session saver feature by_userID which is something warehouse management would like to take advantage of. Any ideas?

We use Pragma for our telnet client. There is no need to have dual log in's.It does not seem right, but I have never used Georgia Softwarks.
Also stick with SAPConsole if you have no plans for a GUI screen... it is proven. SAP Console is on the 6.20 GUI SAP install disk.
Web console was a failure and SAP is going to dump that product. You can use the Dynopro if you want web based screens. We have been converting our sites to voice using SAPconsole and have not had any performance issues.

Hi Johnnathan, we are using RFT guns in our manufacturing warehouse with Naurtech on the client (Symbol MC9090-Windows CE) and Georgia Softworks on the centralised WW SAPConsole Server. We are using this feature to have a local windows user hardcoded in the gs_logon.txt file to ease this account management thing. I don't know about the session saver feature. We had a problem with Connection Broken in a program because RFT users had LOCL as their pronter and our RFT program was printing automatically a Putaway document. For now we did change all printers in the RFT user profiles but does anybody encountered such an issue and find a better solution?
Thanks - Philippe