Overview

 This page contains information about the web client connection checklist.

On this page:

Introduction

Remote Access

Make sure the License and other installation requirements were met..

More information at the pages:

Check if the Guest user can access the project

When starting a client display — either RichClient, SmartClient, or WebClient — you can specify the username to log in on the server. Usually, this is not necessary, as the default user GUEST has access to the server.

However, it is possible that the configuration was changed within your project settings.

You need to check if the GUEST user has access to run the application or specify a username at the command line when starting the clients.

To verify the guest permissions:

  1. Go to Security → Permissions and check which permissions are set for the Guest username. The Guest user is, by default, associated with the GUEST group.
  2. Ensure that the "CLIENT START" or the unrestricted option is enabled, as shown in the image below.

License 

The remote connection requires "Runtime Clients" enabled. Go to LICENSE tab and make sure the number of RUNTIME WEB CLIENTS is one or greater number.

Running the Server process

The Web Clients (according to the FrameworX version) will connect with the TServer.exe process in the server. Verify if the Server.exe process is running, and which PORT it is running. The TServer.Exe port must be used on the web client URL, or in the parameter for the TRichClient.

Open the browser locally

It is quite common to have firewall preventing the remote access of the application. So, before accessing remotely, try to open a local copy of the browser locally at the server. That means run the server and the client at the same computer, before trying the remote access. 

Check the Web Server Port

If it is running locally, but not remotely, it is very likely to be a firewall restriction or a proxy setting.

Test the Rich and Smart Clients

In order to find if there is a specific problem with the web, you may want to run the Rich or Smart clients. Remember that it is necessary to have user, licence, RichClient too, since the license web is different than RichClient.

FrameworX Update

We are continuously enhancing the product, as well as diagnostics messages, it a good procedure to update the system to latest update.

Check the Web Server Port

The default port for the TWebServices (port 10108), and for Solution execution is 3101, but those ports can be changed. Verify the your url and command connections are using the correct IPs and Ports.

In this section:

  • No labels