viflow logoknowledge base

Contact Us

Menu
en de
  • viflow product page
  • Support request

Contact Us

  • viflow knowledge base
  • Instructions
  • WebModel
  • Operate viflow on Microsoft Azure
WebModel

Operate viflow on Microsoft Azure

Applies to: viflow (subscription | 9 | 8 | 7) | Article: 1343380 | Updated on 07.05.2024

The following services in Microsoft Azure can currently be used from viflow 7:

WebModel on Azure – App Service (Web App to host the WebModel)

WebModel on Azure – App Service (Web App to host the WebModel)

Delete

System Requirements

  • .NET Core 6.0 must be installed
  • Azure platform: 64 bit / BASIC plan
  • The WebModel must be exported with viflow 8, version 8.0.4007 or higher
  • The WebModel must be exported with viflow 7 from version 7.0.3789
  • One web app service is required per WebModel
Delete

.NET Core 6.0 – Enable compatibility mode (only viflow 8)

In order for the viflow WebModel to work with the version ››› ASP.NET Core Runtime 6.0, the "compatibility mode" must be activated in it.

We have summarized instructions and the technical background for this in the following article:
'››› Enable compatibility mode in WebModel – .NET 6.0

Hosting the viflow WebModel on Microsoft Azure

  1. In the Azure portal, open the Home – Create Resource – Create Web App page.

  2. Now enter the name {{1}}, select the application .NET Core 6.0 LTS {{2}} in the field Runtime stack {{2}} and activate the option Windows {{3}} under Operating system.

  3. Since there is no connection to Active Directory (AD), only anonymous login to the WebModel is possible.
    To do this, Windows authentication must be deactivated on the web server and the appsettings.json file modified.
    The procedure is described in detail in the chapter Deactivating the login (without cockpit/personalization in the WebModel) of the article ››› Turn off the login dialog when opening the WebModel.

  4. Now the WebModel can be uploaded using an FTP tool (e.g. Filezilla, WinSCP etc. – select binary transfer type!). The login data for the FTP tool can then be found in the Azure web interface.
    The WebModel must be placed on Azure in the automatically created folder wwwroot.

Delete

Azure SQL – Use viflow process model as SQL database

Azure SQL – Use viflow process model as SQL database

The viflow process model can also be stored on Azure in an SQL environment as a database and edited by several users at the same time.

Delete

Learn more about SQL and viflow

In the article ››› viflow Team Modeling – Working with multiple users on SQL Server you will find all information on this topic.

Please pay particular attention to the required authorizations on the SQL server:

  • dbcreator to create a new process model and open or save an existing process model
  • db_datareader to open an existing process model
  • db_datawriter to save an existing process model
  • db_owner to the existing process model (if the database changeset needs to be updated after a viflow update)
Delete

Azure Virtual Desktop – operation as on physical system

Azure Virtual Desktop – operation as on physical system

You can use Azure like a normal PC or system and run viflow on it and host the WebModel on a web server. This applies to both Windows and Linux systems:

  • Windows – install viflow, host WebModel via web server/Internet Information Services (IIS).
  • Linux – Host WebModel via Apache web server ("Reverse Proxy" required)

If you have detailed questions on this topic, please contact your IT administration or our support team at ››› support@viflow.de.

Delete


All articles in WebModel

  • Use of the hosting service viflow cloud for your web model
  • Improve the performance of the WebModel
  • Deploying the viflow WebModel with IIS (Internet Information Services)
  • Installation of IIS (Internet Information Services) for viflow WebModels
  • Disable caching for viflow WebModels
  • Turn off the login dialog when opening the WebModel
  • Opening the WebModel via HTTPS
  • Operate viflow on Microsoft Azure
  • Open local viflow WebModel
  • Enable single sign-on (SSO) for different browsers
  • Error "HTTP Error 500.37 - ANCM Failed" when starting the WebModel
  • Error "HTTP Error 500.19" when starting the WebModel
  • Error "HTTP Error 500.30 - ANCM" when starting the WebModel
  • Processes are blocked by prohibition signs in the WebModel
  • Calling up documents on a file server via a web server (IIS)
  • Open local/external documents from the WebModel
  • Process Model cannot be exported as WebModel
  • Enable compatibility mode in WebModel – .NET 6.0
  • Open local viflow WebModel as preview
  • Replace WebModel manually on web server
  • Restrict access to WebModel directly on web server
  • Direct linking to specific processes in the WebModel
  • Adjust the name of the viflow WebModel
  • Azure AD connection for the WebModel on IIS
  • Administer WebModel – Set up permissions
  • Changing the viflow cloud password
  • Long loading time when calling up the WebModel
Quicklinks
  • viflow international
  • viflow functions
  • Trainings
  • viflow life cycle
  • viflow system requirements
  • Remote support
  • viflow updates
SUBMIT SUPPORT REQUEST

Couldn't find a solution? Make a support request.

Submit a support request


FOLLOW US

We inform you regularly about current developments, trends and news around viflow. Just choose the format that's right for you.

Newsletter subscription
vilfow auf facebook ViCon auf Xing ViCon auf Linkedin vilfow auf youtube
Contact Central office

+49 511 696048-0

Sales

+49 511 696048-20

Support support@viflow.de
  • Contact
  • T&Cs
  • Conditions of Use
  • Privacy Statement
  • Legal Info

Copyright © 2003 – 2025 ViCon GmbH | viflow knowledge base | All rights reserved.

info@vicon.biz +49 511 696048-0
Knowledge Base Software powered by Helpjuice

Definition by Author

0
0
  • Kontakt
  • AGB
  • Nutzungsbedingungen
  • Datenschutz
  • Impressum

Copyright © 2003 – 2021 ViCon GmbH | Funktionen | Alle Rechte vorbehalten.

info@vicon.biz +49 511 696048-0
Expand