Wish you all a Very Happy New Year and Hope you had a rocking start to 2016!
A few weeks ago, I posted the steps to provision a Dynamics AX 7 Environment on Azure here.
Few days back, I got a chance to explore the new AX 7 Virtual Machine and thought to share some interesting findings with you.
AX 7 Virtual Machine Configuration:
It's a pretty powerful machine built on Windows Server 2012 64-bit having 56GB RAM and running on 8 cores.
Key Tools/Software included in the box:
Visual Studio 2015 (for AX Development)
SQL Server 2016
Dynamics AX Server Configuration:
Things have changed on how the AOS Server Configuration is managed. In previous versions of AX, AOS Service was managed as a windows service and we had a Server Configuration Utility under Control Panel to configure and manage AOS instances.
Now with AX 7, All AOS Configurations are stored in IIS
Location of AX 7 packages, source code, and other AOS configurations:
On a Dynamics ‘AX 7’ VM, you can find most of the Dynamics ‘AX 7’ application configuration by opening the web.config file of the AOS Web app.
- Open Internet Information Service (IIS).
- Go to Sites > AOSService.
- Right-click and select Explore, this will open File explorer.
- Find the web.config file and open it in Notepad (or another text editor).
Web config Path inside Virtual Machine - I:\AosService\WebRoot\web.config
The following keys are of interest to many developers and administrators:
Aos.MetadataDirectory – This key points to the location of the ‘AX 7’ packages folder that contains ‘AX 7’ platform and application binaries as well as source code (Source code is only available on development environments.)
Path to packages in the VM - I:\AosService\PackagesLocalDirectory.
Aos.AppRoot – This key points to the root folder of the AOS web application.
DataAccess.Database – This key holds the name of the Dynamics AX 7 database.
Infrastructure.HostURL - This key holds the Host URL for AX 7
Restarting AOS Web App
If you simply want to restart the AOS (without redeploying), run iisreset from an Administrator command prompt or restart the AosService Web App from Internet Information Services (IIS).