Flux – File Orchestration Platform

Flux Road Map

Flux 8.0

Latest Version: Flux 8.0.7 is now generally available.

(2014) Flux 8.0 Releases

  1. Provisioning and Onboarding: On starting a workflow from the repository, prompt the user for necessary data that is called for from within the workflow. Allows an operator to supply critical information to a new workflow when it starts or at any critical point in the running of a workflow.
  2. Usability Improvements: Continuing improvements to the user interface including improved ease of use and targeted enhancements, such as allowing bulk operations (e.g., start, pause, ...) within the Operations Console.
  3. Example Workflows: Provide a set of best practice workflows to accelerate the introduction and deployment of Flux for enterprise file transfer and file orchestration.
  4. Performance: Continued performance improvements.

Flux 8.0 Feature Enhancements from Prior Releases

The following new features and improvements have been incorporated into Flux 8.0:

  1. Flux 8.0 supports installation under Java 7 in addition to Java 6.
  2. Windows installer supports installing onto machines with a 64 Windows JVM installed.
  3. Native PGP encryption, decryption, and key management is now available. This feature is visually configurable and managed through the Web-based Flux Operations Console.
  4. Native file ZIP and UNZIP operations are now supported and can be easily configured in the Web-based Flux Operations Console.
  5. Flux 8.0 retires RMI (i.e., Java's remote method invocation) as Flux's internal networking and remoting capability and replaces it with REST to simplify the network configuration for creating remotely accessible engines and agents,. This simplifies network configuration and remote access for Flux engines, agents, and the Operations Console.
  6. Visual workflow design features previously unavailable in the Web-based workflow designer have been added. This includes support in the Operations Console for creating and editing Business Intervals and for storing them in the Repository.
  7. Automated visual workflow layout is available in the Workflow Designer in the Operations Console to allow a visual and structural re-organization of workflows.
  8. The size of the action and trigger property editors has been increased visually in the Web-based Designer, allowing easier editing of triggers and actions.
  9. Configuring file triggers and actions has been simplified. The "Simple File Source", "Simple File Target", "File Criteria" and "File Criteria Pair" settings are now combined into a single File Criteria interface, simplifying configurations for file triggers and actions and making it easier than ever to configure managed file transfer operations. New data mapping features allow triggers and actions to easily pick up source files from previous triggers and actions.
  10. A test button has been added to the file triggers and actions properties dialog to allow you to test your file host settings during workflow design time, ensuring that no unexpected errors will arise at execution time.
  11. The Sub Flow Chart Action has been removed, replaced with the Flow Chart Action, which allows better flexibility and a greater degree of operator control. The Flow Chart Action has been improved to support copying variables from the parent's flow context.
  12. The File Transform Action has been removed. This was very infrequently used, and is easily replaced with Java custom actions.
  13. The error message that users receive when a Flux client uses a different version of Flux than the Flux engine has been made more understandable.
  14. Agent support for the File Copy Action, File Move Action and File Exist Trigger has been added.
  15. Agent log file names are now configurable.
  16. Flux Agents can now run and connect to engines without requiring the opening of ports for listening.
  17. Support has been added for configuring using host names in a Flux cluster (instead of IP addresses), allowing users to specify the host names Flux will use to communicate between engines on the cluster.
  18. All the provided Flux examples have been updated, validated, and tested on Flux 8.0.

Key Considerations in Migrating to Flux 8.0

  1. The workflow XML structure has changed between Flux 7.11 and 8.0. A migration tool is provided for migrating existing Flux 7.11.x workflows to the new 8.0 format.
  2. The database schema for the Flux tables has also changed. As always, database migration scripts are provided with this release.
  3. The standalone Java Swing desktop designer will be retired in Flux 8.0 since it is now redundant to the web based designer. For those users requiring a stand-alone instance of the workflow designer either for their desktop or laptop, the installation download allows one to install an embedded web application server to host a local instance of the Flux Operations Console for workflow design and testing.

Overview of scheduled features for upcoming Flux versions, as well as a look at what's coming on the long-term road map.

Contact Us!
  • *
  • *
  • *
  • *