Release Notes
Automatic Account Manager 3.8

Facts

Product: Automatic Account Manager (AAM)
Platform: Any supported
Revision History

Important notes when upgrading to 3.8 release

– JAVA has been upgraded to a new version, and this can mean different behaviour in some cases. So please make sure to test your current configuration before implementing in production environment.

Core updates 3.8.0 released March 31st 2016

Java 1.8

AAM is now built and bundled with java 1.8.0_77.

Action updates 2016-03-31

Value Match, version 1.9
– New Feature – The value match can be made case sensitive.

DN Manipulator, version 1.4
– New Feature – It is possible to only make the value typeless.

Base 64 Encode/Decode Attribute Values, version 1.6
– New Feature – Encode or decode Active Directory Object SID value.

Delete Object in LDAP, version 1.5
– New Feature – Delete an object and all its sub objects.

Convert Session Attribute Value to Session Object, version 1.5
– Bug Fix – The copied Session Attributes from the original Session Object will now get correct values.

Write to SQL by Prepared Statement, version 1.0
– New Action – Update or insert values in SQL database using a prepared statement.

Add Session Objects from XML, version 1.0
– New action – Create new Session Objects from data in an XML file.

Match to XML, version 1.0
– New action – Add data from an XML file by making a match with a Session Attribute value.

Upgrade of Existing Installation

Important step! Verify current configuration with new version in test environment.

If earlier versions of AAM exists, a complete reinstall of the application is required. So before doing the upgrade, please make sure to have a full backup of current installation/configuration. And 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 running 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.
– During installation, please make sure to unclick the installation of the service, because it will overwrite the current one.

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>/AAM3/license/license.dat
– <installPath>/AAM3/config.aam and if they exist, all other *.aam files. Because of new functionality, older versions of *.aam files will be upgraded during the first usage and NOT be compatible with earlier versions!
– <installPath>/AAM3/db/
– <installPath>/AAM3/ext/ if 3rd party libraries has been used.

Now, initiate an uninstall of the application. After completion delete the folder <installPath>/AAM3 and remaining files if they exists.

After installation of the new version has completed, copy config.aam to <installPath>/AAM3/.
Also, if any additional action packages, besides standard and extended actions, are used and not available as jar files, the database needs to be copied as well.

Additional guidance can be found in the installation guide.

Release Notes Automatic Account Manager 3.8