Deploying MATLAB® Production Server™ on Azure® creates several resources in your resource group. An architecture diagram and a description of resources follows.
The following Azure resources are created in your resource group at the time of deployment.
|Resource Name||Resource Name in Azure||Description|
MATLAB Production Server cloud console and License Manager virtual machine
Virtual machine (VM) that hosts the MATLAB Production Server cloud console and License Manager. Use the cloud console to:
For more information about the cloud console, see Use MATLAB Production Server Cloud Console.
|MATLAB Production Server cloud console public IP|
Public IP address to connect to MATLAB Production Server cloud console.
The address provides an HTTPS endpoint to the cloud console 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 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 cloud console 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 enables resources to communicate with each other.|
|Azure Cache for Redis™|
Redis cache that enables caching of data between calls to MATLAB code running on a server instance.
For information on how to configure Azure Cache for Redis, see Azure documentation.
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.