Configure Telnet Connection Settings
Once you configure and verify your telnet login sequence, access the Telnet Connections frame and specify the telnet connection settings. These settings define the maximum and minimum number of telnet connections available to the associated user.
The recommended settings are 10 or more for Maximum; 1 for Minimum.
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 maintenance 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.
Minimum
Enter a value from 0 to 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 QAD .NET 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, who is defined with an asterisk (*).
6 Select Go to save the record.
Sample Scripts
Review the following sample login scripts to become familiar with the configuration process. Then create your login sequence based on your environment. For future reference, record your scripts in the table provided. View the field help for additional field-specific details.
Note: Windows login scripts typically include the login domain. QAD recommends that the domain names follow published Internet Engineering Task Force (IETF) standards. For more information, refer to RFC1035 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 | If necessary, enter your Windows telnet server’s domain. |
4 | > | c:\telnet\user1 | Start GTNTS as user1 | Enter the user- or group-specific directory below the telnet directory. |
5 | > | telnet-us-Prod.bat | Launching script to connect to Prod | This value is the telnet script that QDT generates. |
Sample Linux and UNIX Script Values illustrates sample script lines for a Linux/UNIX system. Record your login script values in
Telnet Login Script Information.
Sample Linux and 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 Linux or UNIX server. |
2 | Password: | pswd | Supply Password | Enter the password assigned to the user ID specified in step 1. |
3 | $ | cd /qad/EE/ | Accessing DBServer Dir | Change directories to the database server administration directory. Your response varies depending on how you set up your Linux or UNIX telnet environment. For example, for maximum security, you can enter a command to change to a restricted shell before changing to the directory containing the telnet script. |
4 | $ | ./telnet-us.Prod | Launching script to connect to Prod | Launch the telnet connection script. |
Use
Telnet Login Script Information to record your telnet server login information.
Telnet Login Script Information
Seq | Script Pattern | Script Value | Script Status |
1 | | | |
2 | | | |
3 | | | |
4 | | | |
5 | | | |
Your completed table for the telnet script looks similar to
Sample Telnet Login Script for Linux and UNIX.
Sample Telnet Login Script for Linux and UNIX
Seq | Script Pattern | Script Value | Script Status |
1 | Login | UserID | Logging in |
2 | Password | UserPassword | Supply the password |
3 | $ | cd /qad/EE/ | Accessing DBServer Dir |
4 | $ | ./telnet-us.Prod | Launching Prod telnet connect script |
