Novell Home

Configuring SecureLogin to Work with HLLAPI

Novell Cool Solutions: Feature
By David Guest

Digg This - Slashdot This

Posted: 5 May 2005
 

One of the benefits to using Novell Nsure Securelogin is the ability to pass identity information into applications that are not Windows-based. These can be Web-based or use a terminal emulator. This document deals with the specifics of setting up a specific type of emulator, HLLAPI. While much has been written about configuring generic style emulators, there is little written about HLLAPI emulators.

What is HLLAPI?

HLLAPI (pronounced Hullapy) is an acronym for High Level Language Application Programming Interface. This was defined by IBM in the days when terminals were king, and the PC was a big beige box with a green and black monitor stuck on top of it.

Since HLLAPI was introduced, many terminal emulation companies have adopted it and implemented the API within their S/370 and 5250 emulators. For emulators like Attachmate, Rumba, and IBM PC Communicator it is still there. Many other emulators also include HLLAPI support (Glink, for example) so it may be possible to use HLLAPI configuration with emulators other than the standard IBM types.

Why use HLLAPI?

One of the issues with terminal emulators is the screen scrape that has to be done. This causes the screen to "blink" as the screen is read. This really means that the script/connector/application definition (depends on the version you have) cannot cope with any change of the user ID and password within the application, only with ID and password changes which occur at the initial login.

Using HLLAPI allows the system to read specific portions of the screen without the screen blinking for each read and test. This is accomplished by using the ReadText command and specifying the location to be read. This means that it can work in a manner very similar to the Win32 systems used everyday.

Configuring HLLAPI

The configuration of HLLAPI should be straightforward, but it may not be. There are a number of things to consider:

  • HLLAPI type (32 or 16)
  • Long Session Name
  • Short Session Name

The HLLAPI type and the location of the HLLAPI file are used to ensure that Tlaunch can locate the interface. The short and long session names tell Nsure SecureLogin where to read and write the information.

Example

As an example, the following shows the specific configuration required for Attachmate Personal Edition to work with Secure Login. These settings are required for the script and communication to work.

1. Define a session. This is normally done though a wizard and defines the terminal type and the Host address that will be contacted.

2. Save the session as a session file (Session1).

3. Within the live Attachmate session, choose options and then Global Preferences.

Figure 1: Choosing Global Preferences

4. Click the Advanced Tab to display a list of the HLLAPI short names.

Figure 2: HLLAPI short names

5. Select session identifier A to link it with the active session in the emulator. This tells the HLLAPI to insert any commands into the correct session identifier.

6. Click Browse to correctly identify the session as the current running session (Session1).

Figure 3: Selecting the session

7. Click Open, and the session will appear within the Global Preferences.

Figure 4: Linking the short name and session document

8. Click OK to save the information. Now the SecureLogin TLAUNCH system will be able to interact with the emulator correctly.

Configuring Tlaunch

Once the sessions are configured correctly, you need to configure Tlaunch to use the correct session details.

1. Start Tlaunch (start the application from the menu).

Figure 5: SecureLogin Terminal Launcher

2. Click the Edit Available Emulators button.

Figure 6: Available Emulators

3. Click New.

4. Enter a name for the emulator and set the emulator type to WinHLLAPI.

5. Complete the following dialog with the correct details, as detailed below.

Figure 7: HLLAPI Emulator Configuration dialog

  • Emulator Path should be the path to the executable to run the emulator (such as C:\Program Files\E!PC\EXTRA.exe).
  • Home Directory should be the lcoation where the application is to be run from, the same as the default directory on a windows shortcut.
  • HLLAPI DLL is the path and .DLL file for the HLLAPI function. For Attachmate Personal this is C:\Program Files\E!PC\ehlapi32.dll.
  • HLLAPI Function should always be HLLAPI.
  • Session Files should point to the locations and files that are used to define the sessions in use by the emulator. These are the same as those configured while inside the emulator (see the Configuring HLLAPI section).

Summary

Using the procedures in this article, you should be able to configure any HLLPAI emulator to function correctly with Nsure SecureLogin.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell