Purpose:
The purpose of this document is to describe how we can deploy automated builds to different Dynamics AX pre-production environments so that newly developed features could be rolled-out for UAT. The document also illustrates how version controlling by TFS and data migration activities fit into the big picture.
Business requirement:
Ability to release, deploy automated builds to different Dynamics AX pre-production environments to roll-out newly developed features, bug fixes for testing.
Assumptions:
- Dynamics AX Management Utilities have been installed and configured.
- Build scripts have been installed and configured.
AX pre-production servers topology:
Process:
- ISV model server (Optional)
- Only applicable when an ISV model needs to be updated in the next build.
- TFS Force sync.
- Export ISV model.
- Build server
- Must have 2 AOS instances, build and deploy. Both must not be connected to TFS.
- Copy ISV model to file system.
- Uninstall existing ISV model from build instance.
- Uninstall existing ISV model from deploy instance.
- Install new ISV model to build instance.
- Install new ISV model to deploy instance.
- Restart AOS service of build instance.
- Restart AOS service of deploy instance.
- Perform full compile, full CIL, DB synchronization on build instance.
- Perform full compile, full CIL, DB synchronization on deploy instance.
- Run build command, buildax.ps1, on build instance.
- Output is CUS model file created on the file system.
- Run deploy command, deployax.ps1 on deploy instance.
- Output is modelstore file created on the file system.
- ConsTest server
- Copy modelstore file to file system.
- Import modelstore file via powershell.
- Restart AOS service.
- Perform full compile, full CIL, DB synchronization.
- Document newly developed features and bug fixes in release notes.
- Email the notification and release notes to business stake holders.
