10.1 Enabling Terminal Emulator Applications

You can configure terminal emulators for SSO in the application definition editor in the Administrative Management utility, in the SecureLogin Client Utility, and the Terminal Launcher tool.

To enable a terminal emulator for SSO, you must run the terminal launcher application (tlaunch.exe), and link the emulator definition to the terminal emulator application definition.

Terminal Launcher allows you to configure emulator definitions for use with SecureLogin.

NOTE:Contact NetIQ Support for information about using a ViewNow terminal emulator.

In the following sections, Eicon Aviva is used. Although these procedures apply to most terminal emulators, the application definition and other configuration information might differ for each emulator application. Contact Support for help.

10.1.1 Creating and Saving a Terminal Emulator Session File

Prior to enabling any terminal emulator for SSO, include or create a session file that provides all the required settings for the server connection and any other parameters required for deployment to users. Terminal Launcher should be configured to run this session file when launching the emulator.

Any modifications to the session must be saved to this file. The session file can be saved locally or on the server.

In most environments, the session file exists and you need to configure Terminal Launcher to point to the relevant file.

  1. Start the terminal emulator application.

  2. Connect to the required host.

  3. Change the terminal emulator settings as required.

  4. Save the session. The default directory is usually the application’s installation directory.

  5. On the Connection menu, click Disconnect.The session file remains loaded, but you are disconnected from the host.

  6. On the File menu, click Save [session name] to save changes to the session file.

  7. Exit the terminal emulator application.

10.1.2 Building a Terminal Emulator Application Definition

  1. Open the SecureLogin Client Utility of SecureLogin by double-clicking, or by selecting Start > Programs > NetIQ SecureLogin > NetIQ SecureLogin.

  2. Select File > New > Application. The New Application dialog box is displayed.

  3. Select New Application Definition.

  4. In the Type list, click Terminal Emulator.

  5. In the Name field, specify a name for the application definition (in this example, Eicon Aviva), then click OK. The new application definition is added to the Applications pane.

  6. Select the new application definition. The Details tab is displayed.

  7. Click the Definition tab. The application definition editor is displayed.

  8. Delete the default text: # place your application definition here

  9. In this example for Attachmate, type the following in the text box:

    WaitForText "WELCOME TO ATTACHMATE"
Type @E
WaitForText "ENTER USERID -"
Type $Username
Type @E
WaitForText "Password  ===>"
Type $Password
Type @E
WaitForText " Welcome to Attachmate"
WaitForText "***"
Delay 1000
Type @E

    You must type the screen syntax accurately in the application definition editor. Else, it will fail to operate. Wherever possible, copy the text directly from the emulator screen to the editor.

  10. Click the Details tab.

  11. Ensure that the Enabled option is selected.

  12. Click OK.

10.1.3 Running a Terminal Launcher

Terminal applications are invoked by the terminal launcher when configured properly. After you create the application definition in the management utility, you must use Terminal launcher to link it with the appropriate emulator definition.

By setting tlaunch to point to the new application and the emulator definition, you can click the Create Shortcut button to create a shortcut that links everything together. Clicking the shortcut tlaunch launches the emulator with the configured session file. When tlaunch can communicate with the emulator, it invokes the application definition to interact with the host session.

IMPORTANT:For successfully using Terminal Launcher on Windows XP SP3, the screen resolution must be 1024 by 768 pixels.

  1. Select Start > Programs > NetIQ SecureLogin > Terminal Launcher. The Terminal Launcher dialog box is displayed.

    This release of NetIQ SecureLogin provides two Terminal Launcher shortcuts: one each for 32-bit and 64-bit. To launch Terminal Launcher 32 or Terminal Launcher 64, click Start > All Programs > NetIQ SecureLogin > Terminal Launcher 32 or Terminal Launcher 64.

    Use Terminal Emulator 32 to interact with 32-bit emulators. Use Terminal Emulator 64 to interact with 64-bit emulators.

  2. In the Available applications list, click the required application definition (in this example, Eicon Aviva).

  3. Click Add to move the selected application to the Login to list.

  4. Click Edit Available Emulators. The Available Emulators dialog box is displayed.

    If you launch Terminal Launcher as a normal user on Microsoft Windows Vista or higher, the Edit Available Emulator button is dimmed. You must have administrator rights to edit the TLaunch.ini file. To edit the TLaunch.ini file:

    1. Click Start > All Programs > NetIQ SecureLogin, select Terminal Emulator 32 or Terminal Launcher 64.

    2. Right-click on Terminal Launcher 32 or Terminal Launcher 64, then select Run as administrator.

  5. In Available Emulators, click your emulator definition. In this example, Eicon Aviva.

  6. Click Edit. The HLLAPI Emulator Configuration dialog box is displayed.

  7. In the Emulator Path field, specify the emulator executable’s location.

  8. In the Home Directory field, specify the emulator’s home directory.

  9. In the HLLAPI DLL field, specify the file name and path.

  10. In the Session Files field, select and delete the current session files.

  11. Click Add. The Emulator Session File dialog box is displayed.

  12. Browse and select the configured session file.

  13. Click OK to close the Emulator Session File dialog box.

  14. Click OK to close the HLLAPI Emulator Configuration dialog box.

  15. Click Done to close the Available Emulators dialog box.

  16. In the Terminal Launcher window, ensure that Eicon Aviva is selected in Emulator.

  17. Save the changes and click Launch.

You can start emulator applications from within Terminal Launcher; however, users might not have access to Terminal Launcher or you might need to create multiple definitions for different hosts or sessions. To simplify this process for users, create a desktop shortcut by using Create Shortcut.

For SecureLogin to interact with the emulator, the emulator must be invoked by tlaunch. tlaunch launches the emulator and invokes the NSL script to interact with the terminal session. If a user were to launch the emulator directly then tlaunch would not be running and no interaction would occur.

10.1.4 Creating a Terminal Emulator Desktop Shortcut

  1. Select Start > Programs > NetIQ SecureLogin > Terminal Launcher.

  2. Click Create Shortcut.

  3. Select Location > Desktop.

  4. Select the appropriate options from Options. > Quiet mode and Suppress errors are the default options.

  5. In the Command Line field, ensure that the following parameters are included (in this example, /auto /e"Attachmate" /pAttachmate /q /s):

    Parameter

    Description

    /auto

    Indicates to Terminal Launcher that the following is a parameter requesting the execution of a terminal emulator application that is configured for SSO.

    This parameter is mandatory.

    /e[application name]

    Initiates the execution of the terminal emulator.

    /p[Terminal Launcher config name]

    Initiates execution of the application created in Terminal Launcher.

    /q

    Quiet mode (no Cancel dialog box).

    /s

    Suppress errors.

  6. Add additional parameters as required. For more information, see Section 10.1.5, Setting Terminal Launcher Command Line Parameters

  7. Click Create. The shortcut is created on the desktop. You can deploy it to users in the preferred mode for your organization.

  8. Click Close to close the Terminal Launcher dialog box.

  9. Double-click the short cut.

  10. In the Enter login credentials fields, specify your username and password.

  11. Click OK.

SecureLogin stores the user's login credentials and uses them to log in to the host through the emulator session. Subsequently, double-clicking the desktop shortcut logs the user directly on to the host without any further user interaction.

10.1.5 Setting Terminal Launcher Command Line Parameters

To run the required terminal emulator, Terminal Launcher command line parameters are included in the desktop shortcut command. See Creating a Terminal Emulator Desktop Shortcut.

Table 10-1 Terminal Launcher Command Line Parameters

Parameter

Description

/auto

Indicates to Terminal Launcher that the following is a parameter requesting the execution of a terminal emulator application that is configured for SSO.

For example: C:\<....>\TLaunch.exe /auto /pApplication1

NOTE:This parameter is mandatory.

/p[platform/application/Application Definition name]

Initiates the execution of the terminal emulator as listed in Terminal Launcher Login to.

To run multiple applications from the same command, add /p[TL application/Application Definition name]

You can run up to 15 applications simultaneously from the shortcut command line.

For example: C:\<....>\TLaunch.exe /auto /eAttachmate /pApplication1 /pApplication2

NOTE:You must type the emulator name exactly as it appears in the Terminal Launcher Available Emulators drop-down list.

/b

Specifies the background authentication mode.

/c

Allows the application to close in case of any errors.

For example: C:\<....>\TLaunch.exe /auto /c /Application

Application refers to the terminal emulator application configured for SSO.

/e[emulator name]

The parameter /e[Terminal Launcher config name] initiates the execution of the terminal emulator as listed in Terminal Launcher Available Emulators.

NOTE:You must type the emulator name exactly as it appears in the Terminal Launcher Available Emulators list.

/h[hllapi short name]

Commands TLaunch.exe to connect to the specified HLLAPI session.

/k[executable name]

Quits the specified executable prior to launching the terminal emulator.

/l

Disables the terminal emulator execution. This parameter is required when multiple instances of terminal emulator are running and you want to disable a few selected instances.

/m

Enables multiple concurrent connections to specified sessions. This parameter is required for background authentication.

/n

Starts the selected terminal emulator without executing a SecureLogin application definition.

For example: C:\<....>\TLaunch.exe /auto /n

NOTE:This parameter does not function with VBA emulators.

It overrides /p option.

/n[number 1-15]

Starts the specified number of terminal emulator sessions without executing SecureLogin application definition.

For example: C:\<....>\TLaunch.exe /auto /n3

NOTE:This parameter does not function with VBA emulators.

It overrides /p option.

/q

Quiet Mode (no Cancel dialog bSox).

For example: C:\<....>\TLaunch.exe /auto /q

/s

Suppress errors.

/t

Unlimited timeout during connection.

For example: C:\<....>\TLaunch.exe /auto /eAttachmate /pBackground /b /t /m /hA /s /q

/w

Allows terminal emulator to wait for an application or process to complete before executing the next process.

/x [Shared Access Rights]

Setting EHLLAPI shared access for read and write permission between multiple EHLLAPI sessions.

For example: C:\<....>\TLaunch.exe /auto /eAttachmate /pBackground /b /t /m /hA/s /q /xSUPER_WRITE

/hwnd

Use this parameter to pass an application handle to the terminal launcher. This parameter indicates the application window the terminal launcher should interact with.

For example: This is an application definition script that uses GetHandle command to get the handle and passes it to TLaunch.exe using the /hwnd parameter.

GetReg "HKLM\Software\Microsoft\Windows\CurrentVersion\App Paths\SLProto.exe\Path" ?SLLocation
If ?SLLocation eq "<NOTSET>"
EndScript
EndIf

GetHandle ?PuttyHWND
Strcat ?TLaunch ?SLLocation "tlaunch.exe"
Strcat ?TLaunchHWND "/hwnd" ?PuttyHWND
Run ?TLaunch "/auto" "/ePutty" "/l" "/pPutty - Detection and
Login" "/t" "/q" "/s" ?TLaunchHWND

Table 10-2 List of session options for EHLLAPI shared access support

Parameter

Description

/xWRITE_WRITE

By default the application has write access and allows only supervisory application to concurrently connect to its presentation space (WRITE_SUPER). Using WRITE_WRITE parameter allows other applications with predictable behavior to share the presentation space.

For example: C:\<....>\auto /e"Attachmate" /Tlaunch_script /q /s /xWRITE_WRITE

/xSUPER_WRITE

Allows other applications to have write access permissions, while the originating application may only perform supervisory functions.

/xWRITE_SUPER

Allows other applications to perform supervisory functions, while the originating application has complete control of the session.

/xWRITE_READ

Allows other applications that perform read-only functions to share their session, while the originating application has complete control of the session.

/xWRITE_NONE

Does not allow any other applications to share the presentation space.

/xREAD_WRITE

Allows other applications to write to the session, while the originating application has read-only access.