What’s New in AAM 3.7.1


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

Version 3.7.1 released February 2016

Read former release notes for AAM 3.3 here.
Read former release notes for AAM 3.4 here.
Read former release notes for AAM (Provisioning Service) 3.5 here.
Release 3.6 was an internal version, never released.
Read former release notes for AAM 3.7 here.

What’s New

The new version of AAM includes a number of improvements and new features.

Core updates 3.7.1


– In the internal database, log entries for the policies are saved. The log includes information of transaction number, time for execution, number of processed object etc. It is now possible to configure AAM to automatically remove log entries that are older than a given number of days. The configuration is made in Tools -> Database Utilities.


– The installation is now made using Install4j.
– The AAM service name has been changed to PhenixID AAM Service.
– The AAM default installation folder has been changed to PhenixID/AAM3/.
– It is no longer possible to log the output in AAM Studio to the console. Instead, two separate log files are created for standard output and standard error. The files for AAM Service are named AAMServiceStdout.log and AAMServiceStderr.log, and for AAM Studio they are named AAMStudioStdout.log and AAMStudioStderr.log.

Bug fixes

– The lock file for AAM Studio is renamed to AAMStudio.lck.

Action updates 2016-02-03

Generate Email Address, version 1.2
– Improvement – The parameter LDAP Search Filter now has support for SESSION().

Launch Application, version 2.0
– Improvement – The action now supports both ” and ‘ around the parameters in the launch command.

Powershell, version 1.6
– New feature – The action is added to the standard action package.
– New feature – It is now possible to configure a success string and a failure string, to receive a status attribute telling if the action succeeded.

Write to File, version 2.0
– New feature – It is now possible to insert a tab in the text.
– Improvement – It is now possible to use the encoding UTF-8 without a BOM in the beginning of the file.

Important notes when upgrading to 3.7.x release

– Behavior in some scenarios might be different as JAVA has been upgraded to a newer version. Please make sure to test your current configuration before implementing in production environment.

– With the new JAVA, SMTP behavior has been changed. Please see document:

– New feature, “LDAP connection pooling” has been added to version 3.7. It’s disabled by default. Please make sure to read the solution document below, before implementing this feature.

Upgrade of Existing Installation

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

If earlier versions of AAM exists, a complete re-install of the application is required. Before doing the upgrade, please make sure to have a full backup of current installation/configuration. Also verify, in test environment, that current configuration works well with the new version.

If for some reason, verification in a test environment not is 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/

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.
Read more in the installation guide.

Modifying java parameters

AAM 3.7.1 comes with a new installer, Install4j. To modify the java parameters in a Windows environment (like memory setting) please update the .vmoptions files that are located in the <installPath>/AAM3 folder.