The following article describes a connectivity issue that some users may face after a successful installation of the driver.
The driver communicates with jBASE system via telnet protocol. Due to a variety of configurations, some jBASE setups may not be able to connect with default parameters of the driver. As a result, users get “Connection timeout” exceptions while attempting to connect to jBASE server. This can be solved by altering one or more parameters of the negotiation protocol in Administrator tool.
The driver comes with a set of negotiation parameters. These parameters are located in the [Parameters] tab and their values can be modified for each alias definition. The values are used by driver to “negotiate” with jBASE, and represent text keywords that are either sent by jBASE as output text for display, or expected by jBASE as input commands. Find below their brief descriptions.
login_key
Output text that unix/windows OS displays at login prompt. The entire line at input prompt must be set in this parameter.
password_key
Output text (or part of it) that unix/windows OS displays at password prompt.
unix_pwd_error
Output text (or part of it) displayed by unix/windows OS after unsuccessful login attempt.
unix_pwd_expired_key
Output text (or part of it) that unix/windows OS displays when the current password expires and requests an input for a new password.
account_key
(Optional) Output text (or part of it) displayed by the script requesting to input T24 environment.
start_globus_key
(Optional) Output text (or part of it) displayed by the script requesting a “Y” or “N” answer to the question whether to perform automatic login to T24 or not. The driver will reply “N” or “” (empty value). Important! Make sure any of the above answers will bring the driver to jShell prompt.
jbase_shell_key
Output text (or part of it) that marks jShell prompt.