Software AG Runtime audit, debug, JAAS, JMX, port, security, single-sign on, watchdog, and Web Services Stack configurations.

User repository and password store.

Log4j 2 settings, as follows:

Upgrade from 10.4 and earlier: The utility migrates any custom non-default loggers and the org.apache.log4j.RollingFileAppender and org.apache.log4j.ConsoleAppender appenders from the old log_config.xml file to the new log4j2.properties file.

Upgrade from 10.5 and later: The utility migrates the entire contents of the old log4j.properties file to the new log4j2.properties file.

Java Service Wrapper customizations you made in the old custom_wrapper.conf files, including #include directives and comments (but not associated properties).

Users, groups, and roles.

Proxy configuration files for proxy types HTTP, HTTPS, FTP, and SOCKS. The utility migrates files for proxies that are not already configured in the new installation.

Starting in 10.0, Software AG Security Infrastructure no longer supports SSX or SSX LoginModules. The migration utility migrates LoginContexts that do not contain SSX LoginModules. However, if an old LoginContext contains SSX LoginModules, the migration utility does the following:

If LoginContext exists in old and new release, the utility adds a comment to the new LoginContext that no migration was performed.

If LoginContext exists in old release but not in new release, the utility adds an empty LoginContext to the new release with comment that no migration was performed. This is to prevent software that used the old LoginContext from failing because of missing context.