Login Enterprise Engine

Overview

The Login Enterprise Engine also referred to as the Target Engine, is a critical executable within the Login Enterprise platform. It is responsible for facilitating Virtual User interactions, performance measurement collection, and seamless communication with the Login Enterprise Virtual Appliance.

Functionality

Upon login by a Virtual User, the Logon Component deploys the Login Enterprise Engine to the target digital workspace environment. The Engine determines if a Test is scheduled, retrieves Test parameters, and reports Test initiation to the Login Enterprise Virtual Appliance. It then executes the following processes:

  • Runs Virtual User actions specified by the assigned workloads.
  • Loops through workloads based on the configured Test duration or iteration count.
  • Collects performance events and metrics, reporting them back to the Appliance over a secure HTTPS (port 443) connection.
  • Logs off the Virtual User after the Test session, confirming the session's completion to the Appliance.

Engine User Interface

The Engine User Interface (UI) is a minimalistic toolbar that appears at the bottom of the desktop when the Engine process is running.

Frame 779.png

This UI is not intended for direct user interaction but provides useful status information during Test execution.

Appearance and Behavior

  • Location: The Engine UI appears as a green bar at the bottom of the desktop.
  • Initial Display: When the Engine begins running, the UI displays the message "Reading configuration…" as it communicates with the Virtual Appliance to retrieve the Test configuration.
  • Interactivity: The green Engine UI toolbar is draggable, allowing you to move it around the screen.
  • Status Indicators: The Engine UI shows different status messages, such as:
    • Reading configuration: Communicating with the Virtual Appliance.
    • Workload name: The current workload being executed.
    • Logging off / Ending the Test: Indicates the Engine is concluding the Test session.

Key Information Displayed

The following details are shown in the Engine UI to keep users informed about the Test status:

  • Repeat Count: Displays the current iteration in a Load Test or Continuous Test. It indicates either the loop number or how many workload loops are configured to run.
  • Environment: Shows the name of the Test configuration being used for the current Test.
  • Account: Displays the Test user/Account that is logged in and running the Test on the Target desktop.

Pause/Play Functionality

A Pause/Play button is located on the right side of the Engine UI. By default, the Pause button is visible.

  • Pause: When clicked, the Engine pauses indefinitely and waits for the user to click Play to resume the Test. This allows for troubleshooting or manual interaction with the desktop without the Virtual User interfering.
  • Resume: Clicking Play resumes the Test, allowing the Virtual User to continue with the next steps in the Test plan.

When the Engine is paused, it will finish the current workload before pausing, and will not move on to the next action until resumed.

Additional Wait Messages

The Engine UI may also display a green wait message in the center of the screen, which is generated by the wait workload function. This message provides more specific details about the wait condition.

Engine Processes

This section highlights additional aspects of how the Engine functions during the Test execution, including its role in running executable files, collecting metrics, and executing workloads.

  • Test Discovery: At startup, the Engine opens a connection to the Appliance and requests information about the Test pending for the current domain/user in this login session. If one exists, the Engine will download the Test configuration and begin to perform the actions. Otherwise, it will report an error and log out.
  • Data Collection and Upload: The Engine gathers various performance metrics and uploads them to the Virtual Appliance for further analysis. These include:
    • Logon Process: Timing and details of the logon process.
    • App Timers: Timers for Application startup and interaction times.
    • Session Metrics: Session metrics, such as user activity and Application behavior.
  • Workload Execution: The Engine runs Virtual User actions. These actions are typically implemented as C# workload scripts, which can either be:
    • Out-Of-the-Box Workloads: Pre-configured scripts for common testing scenarios.
    • Custom Workloads: You can create your own workloads using tools like the Script Recorder, Application X-Ray, and the Script Editor to design custom Tests.

For more detailed information on the Virtual User actions, see the Scripting Functions.

Core Components

The main components of this feature include:

  • Logon Component: Acts as a bootstrapper, downloading and unzipping the Login Enterprise Engine from the Appliance. For more information, see the Logon Components.
  • Engine Executable: Facilitates the execution of Test workloads and the collection of performance metrics.

Engine Process Errors

  • User Configuration Error: After the logon executable downloads and extracts the Engine folder (which contains the engine.exe), and the engine.exe is invoked, the Engine will check if the user running the Engine is configured as a Test user in the Virtual Appliance web interface. If the user is not found, an error is generated, as shown in the screenshot below. If this error occurs, the system will automatically log you off unless you’ve clicked the Stop Engine to prevent the logout.

Frame 780.png

  • Test Assignment Error: If the user exists in the system but no Test is assigned to the user at the time of invocation, a different error occurs. This indicates that while the user is configured, no corresponding Test is available for execution at that point. In this case, the system will also log you off unless you’ve clicked the Stop Engine button to prevent the logout.

Log File Locations

Log files generated by the Login Enterprise Engine are located in:

%temp%\LoginPI\Logs\Engine*.txt

Make sure to verify additional or updated log file paths if applicable.

Key Benefits

  1. Agentless Deployment:
    The Login Enterprise Engine ensures target environments remain agentless. This approach avoids the performance impact and security hurdles associated with traditional agent-based solutions.
  2. Hands-Off Operation:
    The Engine operates without requiring user intervention, making it inherently functional as soon as a synthetic user logs in.
  3. Seamless Integration:
    Hosted on the Login Enterprise Virtual Appliance, the Engine is downloaded and executed per session, ensuring consistent operation across diverse environments.
  4. Secure Communication:
    All communication between the Engine and the Virtual Appliance occurs over HTTPS (port 443), ensuring secure data transfer.

Value

The Login Enterprise Engine is indispensable for delivering actionable performance insights. By enabling Virtual User testing without agents, it saves time, simplifies deployment, and avoids the need for complex security approvals. As a result, you benefit from a lightweight, efficient, and secure solution for monitoring and optimizing system and application performance.