You should definitely run through this whole process in your testing environment, at least once, to smooth out all the things that can go wrong, so it's good to see you doing that. Basically when you start the AOS, it notices that the model store is a newer version than the data store, and offers you the menu that includes all of the various options, i.e. Code upgrade, Data upgrade, etc. It can't know which one is appropriate, but it can tell that there's a mismatch that needs fixing. You can get to this point by applying hotfix updates, or by simply bringing together a business database and a model store in a variety of ways. One of the way is to provide the new model store when running through the installation wizard, but a backup/restore as well as an AXUTIL restore all achieve approximately the same end result. Once the Data upgrade cockpit is launched, is analyzes all scripts that can be run, and discards ones that have already been run. There are version number checks involved, but there's also a table that tracks which ones are completed. What you should get as a list of proposed scripts is only what is necessary to bridge the gap between the current version of the business database and the target version to match the model store. Note that per your original question, you can apply kernel updates and upon starting the new AOS version have no upgrade tasks at all. It's the model store that contains the scripts and the version information. The client and even the AOS to some degree are dependent upon the model store version, with some flexibility that isn't all that well documented, but I've seen AX ignore some pretty badly mismatched versions and go about crashing frequently or behave stupid when I, as a system administrator, would really have preferred the AOS reject connections from a down-level client altogether. Fortunately this is something you can achieve yourself, if it's critical to you, because the client's binary version is provided to the AOS as part of login, and can be found on the user log table. None of this includes considering for EP or Retail steps at all. I'm just discussing the binary, business database, and model store steps.
↧