Child pages
  • automaIT 2.2 Release Notes

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

2.2.2 -



Major Bugfixes

  • NP-1314: Fixed issue not assigning return values when execNative fails.
  • NP-1316: Fixed issue not displaying a variable set in paginator. 

2.2.1 - 2014-09-29

Major Bugfixes

  • NP-1286: Adapted automatically generated name from "Copy of OldVarSetName" to "OldVarSetName-copy" if copying a variable set, because whitespaces are not allowed in variable set names. 
  • NP-1294: Fixed an issue that instance variables has not been displayed in component instance details dialog.
  • NP-1295: Fixed LazyInitializationException which occures while undeployRessource.
  • NP-1293: Fixed IllegalArgumentException occured on updating install variables.
  • NP-1283: Fixed NullPointerException occured in support mode while replaying a job that contains a ProcessStep without a return value.
  • NP-1297: Fixed number of allowed parameters in abstract components.
  • NP-1302: Fixed DuplicateKeyException which occurs while installing a component during update of a ComponentInstanceVariableSet. 
  • NP-1287: Fixed LazyInitializationException which occured when displaying component instance details if the log level for "org.springframework" is set to DEBUG.
  • NP-1307: Groups of external (LDAP) users will now be mapped correctly to internal groups. This solved problems with allow/deny access to per "Access Management" configured business objects.


The release 2.2 is fully upgradable from previous versions of automaIT, but please consider the changes marked with a warning before upgrading: (warning).

New Features

  • NP-561: Physical hosts can be deleted recursively including all child virtual hosts, component instances, and component instance dependencies. This allows the deletion of (unused) hosts without executing any uninstallation code.
    However, component instances cannot  be deleted if there are dependencies or nested references from component instances which are not installed on one of the hosts currently being deleted.
  • NP-254: Plug-ins can be deleted completely including all plug-in owned plans, components, folders, host sets, host searches, host types, and all associated elements. The plug-ins cannot be deleted if there are component instances or the plug-in owned elements are referenced from outside the plug-in.
  • NP-1072, NP-1183: "Job Replay" provides a mechanism to replay a previously executed job or subjob. All selected and configured values of the last execution will be restored and displayed in the appropriate execution dialogue. Passwords cannot be restored correctly and will therefore be restored with an empty string. A warning message is displayed if replaying a job with at least one password parameter.
  • NP-1155: The element createDependency supports the attribute strictness.
    Value HARD: Component instances ("dependees") which are referenced by hard dependencies cannot be overwritten by subsequent installations (Default and previous behaviour).
    Value SOFT: Component instances ("dependees") which are referenced by soft dependencies may be overwritten by subsequent installations.
  • NP-987: The assignment of variables' values is protocolled for the following elements: var, assign (standalone and embedded in call and extension statements), and execNative (assignOutput, assignError, assignStatus). The maximal length displayed in the protocol may be configured using the property ui.variable.output.max.size.
  • NP-916: Physical hosts can be created and initialized using the element createPhysicalHost. The host name and its connection parameters must be specified. Description, host function, host type, and host type variables are optional.
  • NP-918: Virtual hosts can be created using the element createVirtualHost. The host name and its parent must be specified. Description, host type and host type variables are optional.
  • NP-1226: Physical and virtual hosts can be deleted using the element deleteHost.
  • NP-1069: Components support multiple resources which are identified by name, e.g. <deployResource><resource name="myResourceName"/></deployResource> . Existing resources are migrated with the name "default". All resources of a component can be referenced using the element allResources, e.g. <deployResource><allResources/></deployResource>.
    (warning) The substitution sys.rsrcInstallPath is no longer supported.

  • NP-1145: Resources can be downloaded in the web UI of component details. Directories are provided as a zip archive.
  • NP-1241: Multiple automaIT instances can be distinguished by setting the property individually for each instance. The application name is shown in the browser's title and in the maintenance view.  
  • NP-935: Access Control Lists can be used for more gradual administration of user permissions on model objects. See User Authorization (Access Control Lists) for more information.


    Before installing this version of automaIT, you should check whether the "plpgsql" language is defined in your PostgreSQL database. The "plpgsql" language is used to create db triggers.

    To check whether the required language is already defined, execute the following statement on your db: "select count(*) from pg_language where lanname = 'plpgsql';". If the result of the select is equals to one, everything is fine.

    If not, you must check whether the language is already supported by your db. This can be done with: "select count(*) from pg_pltemplate where tmplname = 'plpgsql';". If the result of the select is equals to one, your db support the language and can be defined with: "create language plpgsql;". After this the count select on 'pg_language' table should deliver a value equals to one.

  • NP-972, NP-1023: The component instances are preselected on method execution and uninstall.
  • NP-1148: Variable sets exported by older automaIT versions are now automatically transformed to the current data namespace during import.
  • NP-1172, NP-1174: automaIT server may now be started in stand-alone mode (without PostgreSQL and Tomcat) for easier testing in demo environments. Stand-alone automaIT server can now be initialized based on so-called "scenario"-files for demo environments.