Installing a jump server in Windows is one of the ways in which one can configure transparent login to applications in remote servers for which no easy way of filling the necessary data is available.

Setting up the transparent login in this situation requires to initiate the learning tool, open the target application in the windows jump server, and selecting the reference of the different windows components shown on screen. In general, by hovering over the actual window opened, the reference to the windows class and instance is shown, and this may be used to configure the transparent login script.

There are times, however, when moving over the application window does not provide a class and instance reference that may be used as a means of configuring the final transparent login script. This occurs- typically- with java based applications.

This document shows how to overcome this problem by means of the mouseclick and keystroke features of the learning tool

Instructions:

We will illustrate the example with the HP Device Manager Application, which we would like to fill up with a server ip and username.

As seen below, trying to determine the window element id by using the learning tool is not possible since no window id or class is shown in the controlviewer window when trying to move over the HP Device Manager popup window

In this case what we need to do is to use the mouseclick (mouse icon in the Learning Tool window) and choose the option to click on a Window Position. Then, move to the position in the Window we want to fill up and click the OK. This means, basically, than on bringing up the application at transparent login time, the cursor will position itself automatically on the given coordinate and it will click the mouse, in practice making that position active.

Next we need to indicate to the application what kind of text we want to write there. To do that we choose the text tool (the written paper sheet in the Learnint Tool window) and we choose as element type Keystrokes. This means that whatever we write afterwards will be "written" to the position that the cursor is in during transparent login.

We repeat the process for the rest of the elements in the window until we have "filled in" all necessary fields. For instance, here we would be positioning ourselves in the Server address field and we would be filling it with "10.1.1.1", and next we would be moving to the username field and we would be filling it with the text "testusr"

After this, saving the application script, we should be able to do transparent login.

This procedure has one possible caveat: since the filling of the fields is based upon position, there may be times when the positions at login time are different from the ones we see during the learning process. This occurs, typically, when, for instance, the learning process is done with full screen and the final users choose a lower resolution, or when the windows toolbar is configured not to hide automatically. In such cases, the testing the script during the learn process will work, but it will seem not to work during production.