VISULOX 5 Documentation
5.0.3 5.0.2 5.0.1
5.0.3 5.0.2 5.0.1

Application Configuration Quick Guide

VISULOX 5 | Application Administration

Scope

This guide describes SSH, RDP and Direct application types and the administrative procedure for creating an application from an existing configuration.

It is intended for administrators who manage application servers, applications and user profile assignments.


Use the separate Operational Checks document for service status, integrity, Portal health, database and HA checks, and functional application tests.

Policy configuration is outside the scope of this guide.

Application Types

SSH Applications

For an SSH application, duplicate an existing SSH application and assign the intended target server. Review the inherited connection and launch settings before assigning the application to a user profile.

No additional SSH field values are described in this guide.

RDP Applications

RDP applications start an RDP client locally on a Portal Server. The client connects to a Windows Terminal Server. An RDP application must always reference a Windows application server.

  • Windows desktop: Leave the Command field empty.

  • Dedicated Windows application: Enter the application or its alias in the Command field. The application must be published as a RemoteApp on the Windows Terminal Server.

Without SSO, the credentials dialog is displayed. With SSO, the system attempts to authenticate the user with their VISULOX credentials. Verify the selected behaviour during the application test.

Application Types

Direct Applications

Direct applications run locally on the Portal Servers. Local authentication uses the provided VISULOX transit users vlx000-vlx099.

Local execution usually uses vlxshell, which can launch different clients. Examples supplied for this environment include xterm, firefox and chromium.

Required application server assignment: Always select Default Application Server Group for a Direct application.

This group contains all Portal Servers. Sessions are distributed according to server availability and the number of running sessions. The system selects an available Portal Server for application execution.

Transit User Environment

The transit-user environment is reset after every session. Each new session starts with a clean environment. Browser settings are not retained, and SSH host keys must be confirmed again when applicable.

Do not rely on files or settings in the transit-user environment remaining available for a later session.

Application Server Assignment Summary

  • SSH: Assign the intended target server using the existing SSH application as the configuration reference.

  • RDP: Always assign a Windows application server.

  • Direct: Always assign Default Application Server Group.

Creating a New Application

Create a new application by duplicating an existing application of the same type. Review inherited settings so that the new application points to the intended server and provides the intended access.

Step 1 Open Server Management

From the Dashboard, navigate to Server Management > Server.

Step 2 Create the Server Entry

For a new SSH or RDP target, create a server entry using its DNS name or IP address. For RDP, the entry must represent the intended Windows application server.

For a Direct application, use the existing Default Application Server Group for the application assignment; a remote target server does not replace this group.

Step 3 Duplicate an Existing Application

Select an existing application of the required type - SSH, RDP or Direct - and duplicate it. Give the new application a clear, distinct name and review the copied settings.

Step 4 Assign the Application Server

Assign the newly created target server to the SSH or RDP application. For a Direct application, always assign Default Application Server Group.

For RDP, also verify the Command field: leave it empty for a desktop or enter the published RemoteApp application or alias for a dedicated application.

Step 5 Assign a User Profile

Assign the intended user profile to the application. Save the configuration using the controls provided in the administration interface.

Step 6 Validate the Application

Log in with an assigned test user. Confirm that the application is visible, launches against the intended target and terminates cleanly. For RDP, verify desktop or RemoteApp behaviour and authentication. For Direct applications, verify local execution and the expected clean environment.

Follow Section 5 Functional Application Checks in the separate Operational Checks document. If the application fails, review its server assignment, launch settings and user profile assignment before repeating the test.