Note: If you require a license file please request one here: Click here!

This article will outline the requirements for a successful implementation of Login Enterprise.

• Login Enterprise Virtual Appliance
• Login Enterprise Launcher Machine(s)
• Digital Workspace
• Connectivity and permissions

To find out how the different components interact with each other we have an architecture overview here.

Login Enterprise virtual appliance

The Login Enterprise virtual appliance is delivered as a fully configured virtual machine. This virtual machine is now delivered as an OVA or VHD(X) file. 

Hypervisor

Login Enterprise supports the following hypervisors:

More information about the installation of the virtual appliance can be found here.

Hardware configuration

To enable Login Enterprise to do its job correctly it is important that the virtual appliance has the correct hardware requirements configured. 

Note: We recommend that the appliance is not configured on a heavily used hypervisor to eliminate external performance influences.

With the recommended configuration we can support a maximum of 2000 concurrent Load test users. For Continuous tests we support a maximum of 250 concurrent users, this also requires an External Database. 

More information about how we reached and test these numbers can be found here.

SQL Database (optional)

By default the Login Enterprise appliance is delivered using an Internal database. With the release of Login Enterprise 4.3 we have the option of adding an external SQL database. We recommend using the External Database function when you plan to run tests with more than 75 Concurrent Continuous Test users or more than 1000 concurrent Load test users. 

More about the external Database configuration can be found here.

Certificates

Login Enterprise Launcher machine(s)

The Login Enterprise Launcher Machine is used to initiate sessions to the target environment. The machine must be a separate virtual or physical machine. 

Note: A launcher has a maximum capacity of 30 concurrent sessions. If using custom connectors the maximum capacity may vary. Additionally, the launcher requires that it run in an interactive session.  This is to ensure that the appropriate client software is capable of being executed and graphic content from the protocol displayed.

Operating systems

For running the launcher software we support the following Launcher operating systems.

For more information about each launcher platform and how to configure them you can click each respective entry.

Software

To make sure the launcher is working correctly there needs to be certain software available on the launcher. All launchers need their respective vendor specific connector in order to connect to the test platform.

Windows

• Microsoft .NET Framework 4.6.1 or higher
• Citrix Receiver / Citrix Workspace
• VMware Horizon Client

Linux

• Curl
• XDOTool
• OpenSSL
• Free RDP
• Citrix Receiver / Citrix Workspace
• VMware Horizon Client

More information about installation and configuration can be found on their own respective pages. You can find the links in the table above.

Hardware configuration

For the launchers to work correctly we have some minimum requirements for the hardware used.

Best practices

There are also best-practices that we recommend you configure on the launcher to ensure the optimal form and availability of the launchers. More about these best-practices can be found here.

Digital Workspace

The digital workspace is the virtual or physical machine that you want to performance test. 

Operating systems

For running the target environment software we support the following operating systems.

Software

To make sure the target environment is working correctly there needs to be certain software available on the platform. 

• Microsoft .NET Framework 4.6.1 or higher

Connectivity and Permissions

In order for all Login Enterprise components to work correctly there are a few other things that are required.

Login Enterprise Appliance

The Login Enterprise appliance must be reachable by the Login Enterprise Launcher and the Digital Workspace via HTTPS traffic, i.e. port 443. 

For login and access to the Login Enterprise appliance an AD authentication can be setup. If this is desired the Login Enterprise appliance must be able to connect to the AD. You can find out more about this feature here.

Login Enterprise Launcher

The launcher must have HTTPS (port 443) access to the Login Enterprise Appliance. Next to that it requires access to the connection broker of your vendor when connecting to a remote machine. I.e. When a Citrix Virtual Apps and Desktops deployment has been chosen, the Launcher must be able to reach the StoreFront server.

Login Enterprise (virtual) users

The users that have been configured for Login Enterprise and log in to the Digital Workspace must be able to:

• Log on to the Digital Workspace
• Run the logon script 
• Connect to the Login Enterprise Appliance on the following ports: 443 (HTTPS)
• Full access to the users %temp% directory
• Be able to start and have the required licenses for the to-be-tested applications for automation i.e. Office 365 licenses etc.
• For some situations exclusions must be made for automation to be successful. More information about file / AV exclusions can be found here

Questions

If there are items that are not clear to you or you want to know the requirements for specific configurations please contact us at support@loginvsi.com.