Microsoft Azure is an ever-expanding set of cloud services.
Due to the number of Azure services available there are many ways in which DriveWorks can be hosted.
This topic documents the most common services DriveWorks can utilize.
All DriveWorks modules are supported on Azure Windows Server based Virtual Machines.
Once a Virtual Machine has been provisioned it can be accessed remotely (using Remote Desktop Connection, or similar), and the required DriveWorks software can be downloaded and installed.
Azure does provide an Azure File Storage service, but our tests have found this to currently have a detrimental effect on the performance of an implementation..
Any other third party software (SOLIDWORKS, Office, etc.) can be installed as required on an Azure VM, as long as the prerequisites of the application are met.
When DriveWorks Pro Server is hosted on an Azure VM, the following ports require to be added to the Windows Firewall exceptions:
Once the exceptions have been added, the same ports are required to be configured in the networking options for that VM.
These ports can be further configured to decide who has access to them.
We recommend leaving it on anyone initially, to test the connection, and then locking it down from there.
The Azure SQL Database is fully supported by DriveWorks.
Once a database has been provisioned you will be given the server address to the database.
This address should be entered in the Server field of DriveWorks Pro Server.
We recommend using SQL Server Authentication for connecting to an Azure SQL Database.
Use the login details entered when the Azure SQL Database was provisioned.
Once DriveWorks Pro Server is connected to the Azure SQL Database you can:
Please see Known Issues for more information.
All DriveWorks database functionality is fully supported with Azure SQL Databases. This includes:
The Azure SQL Database server address should be included in the connection string when using this functionality.
Files related to the implementation, e.g. DriveWorks Project files, SOLIDWORKS models and documents can be stored in Azure File Storage.
Ensure the service is configured to premium, for the fastest read/write speeds.
Every machine in the implementation, e.g. Autopilot and Live will need access to these files.
Connect the machines to the file share over SMB. Azure provide a PowerShell script to enable this connection inside the portal (found under "connect" when viewing the file share). Execute this PowerShell script on the machines in the implementation.
Azure offers services to connect cloud and on-premises infrastructure, such as:
DriveWorks works with these services exactly like it would with any other network.
Azure offers a very comprehensive monitoring service.
See Azure Monitor - Overview for more information.
This is very useful for monitoring virtual machines, databases, load balancers, and any other Azure service.
It provides email alerts when problems occur and metrics to better understand your services.
It is not possible to host DriveWorks Live with an Azure web application. This is because web apps do not allow 3rd party software to be installed.
DriveWorks Live must be ran from a virtual machine where the DriveWorks Live module can be installed and licensed.
Microsoft Azure allows seamless integration between on-premises and cloud-based applications, data and processes through its API.
Combined with the DriveWorks Pro SDK you can make full use of all Azure services within your DriveWorks implementation.
|Knowledge Base Article Ref:||KB19020401|