Configure Telnet Connection Settings
Once you configure and verify your telnet log-in sequence, access the Telnet Connections frame and specify telnet connection settings. These settings define the maximum and minimum number of telnet connections available to the associated user.
Telnet Connections
Maximum
This value specifies:
• The maximum number of concurrent embedded telnet screen connections this user can have open per session.
• The maximum number of detached windows running HTML programs allowed for the user. If a specific record does not exist for a user with this setting defined, that user can continue opening detached windows until the maximum number of sessions allowed for the entire pool is reached.
This setting applies separately to HTML telnet sessions and standard telnet sessions in the Desktop UI. For example, if Maximum Telnet Settings is 5, a user can have 5 maintenance programs running and 5 telnet programs running in one Desktop session before an error displays.
Note: The maximum number of concurrent browses is determined by Max Web Connections in User Option Telnet Maintenance. Valid values are:
• Unlimited: The associated user can have an unlimited number of concurrent telnet connections open.
• Disabled: The associated user cannot log in through Desktop. Until you create a log-in script to initiate telnet sessions for this user, you cannot set this field to any value other than Disabled.
• Any numerical value between 1 and 99.
Minimum
Enter a value between 0 and 9 to indicate the minimum number of telnet connections to be available to the associated user at all times.
Set this value to the number of telnet programs the user is likely to run simultaneously. Specifying a value here can dramatically reduce the wait time for these programs to display in the Desktop UI. However, setting this value too high depletes system resources.
QAD recommends that you set Minimum to 0 (zero) for most users, including the generic user—defined with an asterisk (*). If users access Desktop telnet maintenance programs extensively, set Minimum to 2.
8 Press Go to save the record.
Sample Scripts
Review the following sample log-in scripts to become familiar with the configuration process. Then create your log-in sequence based on your environment. For reference purposes record your scripts in the table provided. View the QAD Standard Edition field help for additional field-specific details.
Note: Windows log-in scripts typically include the log-in domain. Domain names should adhere to the Internet Engineering Task Force (IETF) published standards. For more information, refer to document RFC1035 found at the following URL:
Sample Windows Script Values illustrates sample script lines for a Windows system.
Sample Windows Script Values
Seq | Script Pattern | Script Value | Script Status | Notes |
1 | login: | user1 | Logging In | This ID must correspond to a local user account on the Windows server. |
2 | password: | pswd | Supply Password | Enter the password assigned to the user ID specified in step 1. |
3 | domain: | domain1 | Supply Domain | Enter your Windows telnet server’s domain, if required. |
4 | > | c:\telnet\user1 | Start GTNTS as user1 | Enter the user- or group-specific directory below the telnet directory. |
5 | > | telnetProd.bat | Launching script to connect to Prod | This is the telnet script generated by MFG/UTIL. |
Sample UNIX Script Values illustrates sample script lines for a UNIX system. Record your log-in script values in
Telnet Log-In Script Information.
Sample UNIX Script Values
Seq | Script Pattern | Script Value | Script Status | Notes |
1 | login: | user1 | Logging In | This ID must correspond to a local user account on the UNIX server. |
2 | password: | pswd | Supply Password | Enter the password assigned to the user ID specified in step 1. |
3 | $ | cd /qad/eB2/ | Accessing DBServer Dir | Change directories to the MFG/PRO database server administration directory. Depending on how you set up your UNIX telnet environment, the response you enter varies. For example, for maximum security, you might enter a command to change to a restricted shell before changing to the directory containing the telnet script. See UNIX Telnet Environment Security Issues. |
4 | $ | ./telnet.Prod | Launching script to connect to Prod | |
Use
Telnet Log-In Script Information to record your telnet server log-in information.
Telnet Log-In Script Information
Seq | Script Pattern | Script Value | Script Status |
1 | | | |
2 | | | |
3 | | | |
4 | | | |
5 | | | |
Your completed table for the telnet script should be similar to
Sample Telnet Log‑In Script.
Sample Telnet Log‑In Script
Seq | Script Pattern | Script Value | Script Status |
1 | Login | UserID | Logging in |
2 | Password | UserPassword | Supply the password |
3 | $ | cd /qad/eB2/ | Accessing DBServer Dir |
4 | $ | ./telnet.Prod | Launching Prod telnet connect script |
