Deploying MATLAB® Production Server™ bring your own license (BYOL) on Azure® creates several resources in your resource group. The following sections describe the architecture of MATLAB Production Server and the Azure resources that the deployment provisions.
The MATLAB Production Server deployment in Azure creates the following resources in your resource group.
|Resource Name||Resource Name in Azure||Description|
MATLAB Production Server dashboard virtual machine
Virtual machine (VM) that hosts the MATLAB Production Server dashboard. Use the dashboard to:
For more information about the dashboard, see Manage MATLAB Production Server (BYOL).
|MATLAB Production Server dashboard public IP|
Public IP address to connect to MATLAB Production Server dashboard.
The address provides an HTTPS endpoint to the dashboard for managing server instances.
If you choose to not use public IP addresses during deployment, the ARM template does not create this resource.
|Virtual machine scale set|
Number of identical VMs to be deployed. Each VM runs an instance of MATLAB Production Server that in turn runs multiple MATLAB Production Server workers.
For information on how to change the number of VMs, see Change the Number of Virtual Machines.
Load balancer for routing traffic to MATLAB Production Server instances.
The MATLAB Production Server dashboard retrieves the HTTPS endpoint for making requests to the server from the application gateway resource. Clients use the HTTPS endpoint for making requests to the server.
Storage account where the deployable archives (CTF files) created by MATLAB Compiler SDK™ are stored. The deployable archives are stored in an Azure file share.
|Virtual network||Virtual network that consists of the deployed resources.|
|Azure Cache for Redis™|
Redis cache that enables caching of data between calls to MATLAB code running on a server instance.
For more information on using a data cache, see Use Data Cache to Persist Data.
Application performance management service that enables storing and viewing of all logs associated with deployment.
For information on how to view the logs, see View Logs.