1. Documentation
2. 2024.0 (Latest) 10.3 10.2 10.1 10.0 9.10 9.9 9.8 9.7 9.6 9.5 9.4 9.3 9.2 9.1 9.0 8.2 8.1 8.0 7.6
3. Server
4. Releases
5. 7.1

What's New in RapidMiner Server 7.1?

This page describes the new features of RapidMiner Server 7.1 as well as its enhancements and bug fixes.

Update / migration

• RapidMiner Server 7.1 drops the AdHoc reporting feature. Please note that your AdHoc projects are not lost upon upgrading, any existing projects will remain in the repository but can no longer be used going forward. If you heavily rely on that feature then please do not upgrade to Server 7.1.
• RapidMiner Server 7.1 includes an upgraded underlying application server (JBoss EAP 6.4) for new installations. Existing installations will continue to work with JBoss EAP 6.1, but we encourage performing a full upgrade.
• Server now works with Java 8 when JBoss EAP 6.4 is used, thus no longer requires Java 7. Upgrading to Java 8 is not mandatory though, as Java 7 support is still available in this release. Please be aware that the next release of RM Server may require an upgrade to Java 8 for both security and performance reasons!

LDAP / Active Directory integration

With RapidMiner Server 7.1, administrators can set up Server to use LDAP / Active Directory for user authentication. This eliminates the need to manually manage users inside RapidMiner Server. Instead, new employees can be assigned to the proper groups in Active Directory and then those users get instant access to RapidMiner Server. Also, RapidMiner Server rights can be tied to Active Directory group memberships, so administrators can centrally control even granular access rights from Active Directory.

More details are available in the LDAP documentation.

High Availability

RapidMiner Server 7.1 can be set up for cold-swap failover. Whenever the primary server goes down (e.g due to a hardware failure) then a secondary RapidMiner Server can be started on another machine. This can use the same backend database as the primary server and continue operations after up to a minute of downtime. All state of the failed server is transitioned to the new server, but running processes are not re-executed automatically.

More details are available in the High Availability guide.

OData web services for improved Tableau integration

RapidMiner 7.0 added support for exporting TDE files that can be imported into Tableau. RapidMiner 7.1 takes a step further in automating data exchange with Tableau. RapidMiner Server 7.1 provides an OData output format for its webservice integration. OData webservices can be added in Tableau as a new data source and can be refreshed manually or at scheduled intervals. With this mechanism, Tableau users can get the latest predictive results in a streamlined fashion without regularly switching back to RapidMiner.

QlikView integration guide

Many customers are using RapidMiner and QlikView together, but the integration best practices have been anecdotal so far. With this release, we have also released a step-by-step guide on how to integrate QlikView with RapidMiner Server web services. Dynamic variables can be defined in QlikView which affect the predictive analytics performed and delivered by RapidMiner Server.

More details are available in the QlikView integration guide.

Enhancements and bug fixes

The following improvements and bug fixes are part of RapidMiner Server 7.1:

Enhancements

• Repository speed greatly increased when storing example sets with nominal attributes in case of many different nominal values.
• HTML5 Charts and HTML5 Maps have become extremely customizable: They now have expert parameters to allow almost full access to the entire HighCharts/HighMaps JSON API. See http://api.highcharts.com/highcharts and http://api.highcharts.com/highmaps for details.
• If the underlying database of RapidMiner Server goes down, RapidMiner Server will now automatically recover once the database comes back up again. For this to work, a fresh installation of RM Server is required.
• Changing Server settings no longer requires a restart of RapidMiner Server.
• Improved message upon login error as well as added debug logging to the server which can be enabled to see detailed reasons for denied login requests in the log.
• Added button to navigate from the App Designer back to the Web Interface in the same place as the navigation button from the Web Interface to the App Designer is.
• Editing your own account details is now more easily accessible by clicking on your name in the top right header.
• Improved general navigation flow and redirect logic. Users are no longer trapped in places for which they lack proper permissions.
• Added new public healthcheck REST service (e.g. for high availability setups) for RM Server which can be found at: http://SERVER_URL:SERVER_PORT/api/rest/public/healthcheck
• When browsing the repository and stumbling upon a folder which has already been deleted or you lack permissions, there is now a link to navigate back to the home folder.
• Downloading zip archives or single files from the repository via the web interface now produces proper file endings for the files.
• Stopped processes no longer look like a failed process in the scheduler web UI.
• The installer now updates the default port when switching database systems.
• Increased default session timeout from 30 minutes to two hours.

Bugfixes

• Storing data in the root folder of the Server repository no longer causes strange errors.
• Scheduled processes can now make use of multiple and potentially long process result port locations.
• Returning example sets as JSON via web services now works even if the data contains missing values.
• Fixed a rare bug that caused a server error 500 to keep showing up when editing a certain app visualization component.
• System load monitor is now available after a fresh installation without a Server restart.
• The server log on the System Information page is no longer sometimes cut off at arbitrary characters.
• Fixed broken URLs for exported services in case of whitespaces in the process name.
• Fixed broken URLs which accessed repository resources with the old URL schema.
• In case of an empty user display name, the header profile link will now still be visible.
• Max memory setting in the installer can now no longer be less than 2 GB.
• When trying to select a JDBC driver from a different partition during installation, a warning is displayed.
• Removed many useless logging messages.