Because we do not have the same access in QA/Production/Build as we do in the lower level environments installing a license file is a bit different compared to development, test, stage (any environment within the supplemental scope)
In order to deploy this license file to production or QA we need to do the following. It is good to note that creating this package is not environment specific. Meaning you can create this package on dev and deploy to prod or create on test and push it is QA or stage. It is just a set of pre-defined scripts which is why it doesn’t matter.
Any AOS server:
Windows Explorer > \AOSService\PackagesLocalDirectory\Bin\CustomDeployablePackage
*usually C:\AOSService\PackagesLocalDirectory\Bin\CustomDeployablePackage or on the K-drive*
In here you will find the file ImportISVLicense.zip
Make a copy of this zip file and open it up. Then browse to the following location: ImportISVLicense.zip\AosService\Scripts\License
Copy the license .txt file into this folder and save the zip.
NOTE: During my first try of this I extracted the zip, copied the file into it and zipped it back up. However during the next steps below that allow the license file to be applied I received an error message saying it has an invalid HotfixInstallationInfo.xml even though I did not touch this file. If you modify the zip directly LCS has no issues with the file so I would recommend not extracting the zip file but rather just using the default one as a template and copy the zip somewhere else and make the change there.
It is also good to note that you can put multiple license files in single package. But it is good note that it will import from alphabetically
LCS > Open the AX project in which you wish to apply the license to which in this case is the QA environment which means we need to open the implementation project. Then go to Asset library
Go to software deployable package > Click on the add button and fill out the info regarding the file being uploaded and select our zip file we created in the steps above
You will need to give it a couple of minutes before the "valid" box has a check mark. You will not be able to apply this file until the instance is marked as valid.
Once the instance has been marked as valid we need to apply it to the system.
Go to full details page for the specific environment we need to apply this to and click on the Maintain option > Apply updates
From this window we need to choose the asset we just created and click on apply
After this the system will process the request and trigger emails whenever the process starts and completes.
Whenever you open the main page you will also see the current status of the import itself as well.
From this point we can choose to either A. Do nothing and allow people to test or B. can mark the asset was as release candidate.
You should now be able to log back onto the environment and see that the isv solution is now there
And that the license configuration page now has the license checked.
Reference: D365FO - Maintenance mode / Importing License File (ISV/VAR Add-on License import) (importing via command line)
No comments:
Post a Comment