Release Notes
Automatic Account Manager 3.8.1

Facts

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

Core updates 3.8.1 released May 30th 2016

HyperSQL DataBase

The internal database, HSQLDB, has been updated to version 2.3.3. The jdbc drivers for the internal database can be found in hsqldb-2.3.3.jar in /lib folder.

Standard Out Log Files

The logfiles AAMStudioStdout.log and AAMServiceStdout.log has been removed.

Action updates 2016-05-30

Manage LDAP Object Members, version 1.5
– New Feature – The search base for this action can now be configured.

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.