# Connect to VTScada – Adding a Web Application

- Link: https://www.agilicus.com/anyx-guide/connect-to-vtscada-adding-a-web-application/
- Published: 2024-05-14T00:23:59+00:00
- Author: Don Bowman

1. [Home](https://www.agilicus.com/)
 2. Connect to VTScada – Adding a Web Application

![vtscada logo](https://www.agilicus.com/www/60b03ce4-vtscada-1024x220.png)

Sample Setup

---

## Connect to VTScada – Adding a Web Anywhere Client Application

The following guide outlines the steps for creating a VTScada Anywhere Client application
in the Agilicus platform. These instructions are intended for VTScada deployments
with version v12.1.30+ on Windows, Linux, and Android devices.

[CONTACT](https://www.agilicus.com/contact-us/)

## Overview

The following guide outlines the steps for creating a VTScada web application in
the Agilicus platform.

These instructions are intended for VTScada v12.1.30+ deployments.

For configuration on older versions which require installation of a local certificate,
please [**contact us**](https://www.agilicus.com/contact-us/).

## Step 1: Create the Application

From the left sidebar, expand **Applications** and select **New**:

 1. Application name. The chosen name will also be required to configure the VTScada
    Server list later in the instructions.
 2. a description of the application.

[⌊Adding a VTScada web application connection in AnyX. The AnyX user interface shows
VTScada configuration options, including the URL, credentials, and security settings.
Use AnyX to securely connect to VTScada web applications.⌉⌊Adding a VTScada web 
application connection in AnyX. The AnyX user interface shows VTScada configuration
options, including the URL, credentials, and security settings. Use AnyX to securely
connect to VTScada web applications.⌉[

Click on **Next** to get to the “**Hostname Aliases**” section and accept the proposed
Hostname, or specify a different one. (If different, will need to be applied to 
the VTScada Server address list)

[⌊Connecting VTScada to AnyX: Web Application Configuration - This screenshot shows
the AnyX interface where a new web application connection to VTScada is being configured.
Key settings include the application name, the VTScada server address, and authentication
details. Users can specify the data to be accessed and control permissions for secure
integration. This allows VTScada data to be seamlessly accessed and managed within
the AnyX platform, enhancing data accessibility and control.⌉⌊Connecting VTScada
to AnyX: Web Application Configuration - This screenshot shows the AnyX interface
where a new web application connection to VTScada is being configured. Key settings
include the application name, the VTScada server address, and authentication details.
Users can specify the data to be accessed and control permissions for secure integration.
This allows VTScada data to be seamlessly accessed and managed within the AnyX platform,
enhancing data accessibility and control.⌉[

Select the first option of “**I access via NAME-OF-APP.subdomain.domain.name**” 
and click on **next**.

First under “**My application is accessed**” select “**from my site via an onsite
connector**”

 * Within “**Set up web application firewall**” select “**My application expects
   to receive requests using its internal hostname**”

Under “My application hosts all or most of its pages under a common path prefix”,
enter your VTScada Realm name (eg: /Default) that is the default Path we will allow
authenticated users to navigate. Other path exceptions will be created later in 
the Firewall ruleset.

![image](https://www.agilicus.com/www/e8c9970b-image-1024x501.png)

From the “**Select a connector**” drop down, pick the connector that you had previously
created. 

![image](https://www.agilicus.com/www/429c9d5a-image-1024x203.png)

[⌊6b25c787-image⌉⌊6b25c787-image⌉[

Within the “**Enter the hostname**” field, type in the hostname of the server that
is hosting your VTScada web portal. This should be the same as your VTScada thick
client.

In this configuration, the VTScada Server Setup and “Default” Realm server / and
URLs point to an IP address of 192.168.10.15, and a TCP port of 80, with no SSL (
Secure).

[⌊9aec56e8-image⌉⌊9aec56e8-image⌉[

 

Click on **Next** to be taken to the “**Authentication section”**:

Select “**is authentication by a proxy**” and type in “**/logout**” (without the
double quotes) into the “**Enter the logout url**” field.

We will also use the Optional **“Enter the redirect after signin path**” URL to 
redirect to the VTScada Server Realm page once users perform Authentication. Therefore,
fill the value of the field with the name of the Realm ( eg: /Default )

Select “**has named users with a single role (I will assign users later)**” and 
click on **Next**:

[⌊deaf4bd9-image⌉⌊deaf4bd9-image⌉[

Select the **APPLY** button to finish off this section of the setup.

## Step 2: Configure the Application

Click on “**Overview**” within the **Applications** section and **select the Actions
icon** in the very far right hand side of the screen for the VTScada application
that we just created:

[⌊830b4ba9-image⌉⌊830b4ba9-image⌉[

After clicking on “**Configure Application**”, select the **Proxy** section

[⌊d30aeba9-image⌉⌊d30aeba9-image⌉[

Within the **Proxy** section select the “**Common Path Prefix**” and input the Realm
name. This will limit the Anywhere Client to the desired realm path unless allowed
by the Firewall rules in the following steps. In this case, we use the path /Default
which is our VTScada realm.

Click on “**Rewrite Common Media Types**” checkbox.

Next, select the **“Security”** section and scroll to the **“Firewall Rules”**

![image](https://www.agilicus.com/www/f0b0821b-image-1024x424.png)

In the Firewall section, we will enter rules that will allow Authenticated Users
with permissions to the “Self” role to access specific paths within the VTScada 
Anywhere Client. These specific path are explicit in order to match valid content
within the VTScada Realm that may fall outside of the “Path Prefix” set in the previous
step ( eg: /Default ). These paths contain various web objects such as Icons, CSS
files, Images, Anywhere Client scripts, and specific paths to the Server realm GUUID.

If using Website uptime monitoring, we recommend making the standard website browser
icon “favicon.ico” available without authentication so that Web monitoring software
can easily test end to end website uptime and availability by fetching this object.

The following rules are recommended:

 1. ` ^/vts.`
 2. `^/.*VIC01663918`
 3. `^/Default/[0-9a-fA-F]{8}-([0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}` ( USE YOUR ACTUAL
    REALM NAME )
 4. `^/VTScada(Light)?Branding.*`
 5. `^/favicon.ico` (allow access from Anyone to monitor uptime)

Explainer:

 1. This rule matches the top level files that are necessary to load the landing page.
    They include vts.css, vts.js

2. This rule matches the Anywhere Client and Internet Client script path

3. This rule matches Realm Name and the GUUID path pattern used in VTScada Anywhere
Client. You must change the realm name from “Default” to the one in use.

[⌊a237fca9-image⌉⌊a237fca9-image⌉[

4. This rule matches the VTScada path for images and objects for both the Full and
Light version of the server

5. This rule matches the standard favicon.ico website icon , we recommend allowing
Anyone to access if in need to monitor webpage uptime.

We have now completed setting up your VTScada resource within the Agilicus platform.
At this point you would want to create the appropriate Role Based Access Control
permissions per the steps below:

## Step 3: Add Permissions

 1. _Select _**_Access_ -> Resource Permissions**
 2. Grant Firewall Role (self) Permission of the application name (VTS) to the required
    Identity

## Step 4: Configure VTScada

From the **VTScada Application Manager**, select the **Server Setup** dialog:

[⌊195362c6-image⌉⌊195362c6-image⌉[

Select the **“Connection Addresses”** tab, select the “**+**” icon to create a connection
address entry.

**Enter the matching Agilicus Application name FQDN exactly as created** in the “**
Connection Address**” dialog, select port **443** and check “**Secure**“

[⌊b5de77b9-image⌉⌊b5de77b9-image⌉[

Click “**Apply**” to submit the new address. This will allow VTScada Anywhere Client
to present a list of valid hostnames where the Anywhere Client is allowed to connect.
Since the FQDN is the one we configured through the Agilicus platform, the VTScada
Anywhere Client will be permitted to browse via the newly created service.

---