Identity Provisioning Upgrade Guide to 5.0.0 from 4.3.0 or earlier
Installation media is provided through PhenixID support together with required license.
IMPORTANT STEP! Verify current configuration with new version in test environment.
If earlier versions of Identity Provisioning exists, a complete reinstall of the application is required! Before doing the upgrade, please make sure to have a full backup of current installation/configuration. Please also verify, in test environment, that current configuration works well with the new version.
If for some reason, verification in a test environment is not possible, an installation on current machine can be done, BUT, the reservations below must be addressed. The recommended way is still to use a separate environment for test.
Reservations when TESTING on the same machine as current installation/version:
– The port for the internal database must be changed, adding the parameter DBPortNr=3105 in config.aam. Make sure to change the port number to something other than current port number. Default port number is 3105.
– During installation, please make sure to unclick the installation of the service, because it will overwrite the current one.
Make sure to have the service configured to run the new version of the product.
Revert the port number for the internal database to the default value.
Uninstall the previous version of the product.
Upgrade/Install of new version
Before uninstalling, make sure that you have a backup of current installation/configuration according to instructions above, where the most important files and folders are:
– <installPath>/Provisioning/config.aam and if they exist, all other *.aam files. Because of new functionality, *.aam files from version 3.8.0 or earlier will be upgraded during the first usage and NOT be compatible with the earlier versions afterwards!
– <installPath>/Provisioning/ext/ if 3rd party libraries have been used.
Now, initiate an uninstall of the application. After completion delete the folder <installPath>/Provisioning and remaining files if they exists.
After installation of the new version has completed, paste all the previously copied files and folders back to their places.
Lastly, follow the instructions in PSD1127 to handle that the action packages have moved out from the database to the file system.