Launch application on AVEVA Web Client
- Last UpdatedJul 09, 2026
- 3 minute read
Note: Before launching the application, ensure you have configured System Management Server (SMS), InTouch HMI Identity Manager, AVEVA Web Client Settings, and AVEVA Web Client Role Management in the Configurator. WindowViewer must be opened before the Web Alarm Control in the Web Client. Otherwise, alarms will not be displayed. If opened in the wrong order, refresh the web browser.
Launch standalone application
-
Open the AVEVA Application Manager.
-
Go to the Web Client tab.
-
From the Current application, select the application you would like to launch.
-
Select Launch.
The application is launched on the browser.
Launch Managed InTouch application
-
From the Galaxy containing the managed InTouch application, add the InTouch ViewApp to the View Engine.
-
Deploy the View Engine. After deploying, the application is displayed in AVEVA Application Manager.
-
Open the AVEVA Application Manager.
-
Go to the Web Client tab.
-
From the Current application, select the managed InTouch application you would like to launch.
-
Select Launch.
By default, the application is displayed exactly according to the dimensions defined in the designer. It is not resized to fit the browser. For example, if the application is designed at 1920×1080, it will appear at that size, and scroll bars will be shown if the browser viewport is smaller or larger to accommodate the difference.
Alternatively, you can access the application from browser through localhost/<Website name>. The <Website name> corresponds to the name you configured in the AVEVA Web Client - Settings plugin in the Configurator. The Web Client can also be accessed using its machine name or its Fully Qualified Domain Name (FQDN) instead of localhost.
Launch Web Client through WindowMaker
In the Configurator, under AVEVA Web Client, configure the plugin.

InTouch application deployment behavior in AVEVA Web Client
At any given time, only one InTouch application can be deployed and accessible through the AVEVA Web Client at https://<FQDN>/avevaweb.
For example, if you initially launch a standalone application such as NewApp_001 using the Application Manager, the application will be deployed and available in the Web Client. If you subsequently open NewApp_002 in WindowMaker and select View in Web Client, NewApp_002 becomes the active deployed application and replaces NewApp_001 in the Web Client.
To access NewApp_001 again through https://<FQDN>/avevaweb, you must redeploy or relaunch NewApp_001 using either:
-
AVEVA Application Manager, or
-
WindowMaker (by opening the application and launching it in the Web Client)
This behavior is by design, as the AVEVA Web Client supports only a single active InTouch application deployment at a time.
Behavior when undeploying WebViewEngine
If InTouch Web Client and OMI Web Client are running on the same node and you have launched the InTouch Web Client, then undeploying the WebViewEngine impacts the InTouch Web Client. Any previously launched InTouch Web Client session becomes non-functional and must be relaunched.
This behavior occurs every time the WebViewEngine is undeployed while the InTouch Web Client has been launched; it is not limited to the first occurrence.
This does not affect InTouch Desktop or OMI Desktop applications.