Configure a Realm

If exposing diagnostic applications to the Internet you are advised to take all possible precautions to prevent their use by unauthorized persons.

Do not name any realm, "Rest" or "SQLQuery". Doing so will interfere with remote access to VTScada data.

Preparation

Before configuring a realm, the following must be in place:

Configure a Realm

Preparation

Before configuring a realm, the following must be in place:

If you plan to allow programmers and developers to access diagnostic applications such as the Source Debugger or TraceViewer from an Internet connection then you must secure those applications.

Script applications will run when accessed by an Thin Client. Do not configure them to start automatically.

If exposing diagnostic applications to the Internet you are strongly advised to take all possible precautions to prevent their use by unauthorized persons.

Steps:

  1. Open the VTScada Thin Client / Setup dialog, from the VAMClosed VTScada Application Manager.
  2. Ensure that the Realms tab is selected.
  1. Click Add in the Authorization Realms section of the dialog.

The Add Realm dialog opens.

  1. Enter a meaningful name for the realm in the Realm Name field.

Realm names should not include spaces. Use a hyphen, underscore or mixed case to indicate word boundaries (e.g. "My-Realm", "My_Realm" or "MyRealm" ).

  1. Enable the HTTP protocol.
  2. Enter the port number that connections to the server should use.

    This may vary from the port number configured in the Connection Addresses tab, depending on your network configuration.
  3. Select the number of clients.

    Some sites might allow all possible connections to the same realm while others divide their licensed connections between
  1. Click OK.

The new realm is created, and you are returned to the VTScada Thin Client / Server Setup dialog where the new realm appears in the Realm drop-down list.

  1. In the section, Applications Available on [RealmName], click the Add button.
  2. Select the VTScada application you wish to add to this realm from the Application drop-down list.
  1. Click the OK button.

    The application must be running in order for it to be found.
  2. Test using one of the three connection options.
  3. Repeat from step 9 if you intend to make multiple applications available on this realm.

    It is generally more secure to have only one application per realm, but if your site uses Active Directory credentials, it may be necessary for one realm to include all the applications to which operators might connect.

  1. Click OK.

Your application is now available to VTScada thin clients.

Test

Having successfully configured a VTScada Thin Client Server, and a Realm, you can test your work directly from the Realm configuration dialog.

It must be possible to create a local connection to the VTScada Thin Client Server to test using this dialog. If the "Local" box option is not selected in the Server Setup page of this dialog, you should review your Name Resolution service. If there is no network connection, this might be done by editing the HOSTS file in your C:\Windows\System32\Drv\ folder to configure the IP address for your computer name. Also, the application must be running.

Remove

Removes the selected realm (and the application attached to it) from the list.

You will be prompted to confirm this action before the realm is removed. (If removing an application from the realm, there is no prompt.)

In the case that you have more than one Thin Client Server, the realm will be removed from all. Any users who are connected to the realm will be disconnected immediately.

Troubleshooting:

  • Unable to connect.

Check that no other service is using the configured port.

If trying to connect using the server computer, ensure that the Local option is selected (done automatically). If not, it is likely that the domain is not being recognized.

If trying to connect remotely, check that the server is visible on the network. Firewall or proxy server configuration may be required.

Check that the VTScada Thin Client Server configuration was completed correctly.

Check that security is enabled in the application, and that your account has the Thin Client Access privilege.