What's New in DataFlux Data Management Server

DataFlux Data Management Server can now be configured to manage HTTPS connections in a manner that complies with the Federal Information Processing Standard 140-2. FIPS compliance is required by various industries and government agencies.

You can now use any of three application programming interfaces to access the DataFlux Data Management Server. The APIs are installed by default on the server host. The APIs enable your client applications to execute batch jobs, real-time data services, and real-time process services. For further information about the APIs, refer to the DataFlux Data Management Server: Rest API Reference (http://support.sas.com/documentation/onlinedoc/dfdmserver/2.7/dmpdmsrvrestref/Default.htm).

You can now choose to upgrade your DataFlux Data Management Server software using one of two available upgrade processes. One upgrade process eliminates manual migration. The other upgrade process requires manual migration, but does not require you to immediately stop your existing server. Both of the upgrade processes use new automation and documentation. For further information, see Post-Installation Tasks.

The SAS Metadata Server is now required to be the authentication provider for the DataFlux Data Management Server. The DataFlux Authentication Server is no longer supported as an alternative to the SAS Metadata Server.

To migrate users and groups from a DataFlux Authentication Server to a SAS Metadata Server, you run PROC ASExport on the DataFlux Authentication Server. After migration, you run the dftool utility on the DataFlux Data Management Server. In the security files on the DataFlux Data Management Server, the dftool utility replaces DataFlux Authentication Server IDs with SAS Metadata Server IDs. The migration process and dftool run during installation. You can run migration and dftool after installation as needed to complete the migration of users and groups.