Flux 8.0 Demonstration

The following describes a general demonstration of Flux 8.0. 

Step-by-step guide


  1. Sign on to the Flux Public Staging Server as s.flux.ly admin user
  2. Review the general architecture of Flux - Engines, Agents, and Browsers.
    1. Support for Java 6, 7, and soon - Java 8.
    2. Mention database support and application server support. 
  3. Present the Flux Operations Console - home page.
    1. Role of the operations console.
    2. Status and rows of the console.
    3. Actions available from the console, e.g., pause, resume, expedite ...
    4. Filtering on rows
      1. By state (Firing, Waiting, ...)
      2. By Namespace (Delve into concept and uses of namespaces)
  4. Transition to the Security Tab
    1. Mention Active Directory and LDAP integration that Flux provides - mapping an AD Role or Group to a Flux Role or Group
    2. Briefly discuss engine, agents workflow tabs
    3. On Repository and Workflows tab delve into controlling access by namespace
    4. Very quick on Reports tab - this tab only controls clearing out logs and history
    5. Then spend a few moments on the Operations Console Tab - that control the visibility of the tabs to Operations staff
  5. Now on to the Repository tab
    1. The Flux repository is where Flux workflows, encryption keys, engine and agent configurations, and business calendars are kept.
    2. We will talk in the next section about those things that are not kept in the repository - such as the runtime configuration file.
    3. The repository is shared amongst all the Flux engines in a Flux Cluster. Repository items can be downloaded from the Repository, uploaded from the repository, even promoted from one repository to another (suchas from Development to QA to Production).
    4. Workflows in a repository can be reused - e.g., the same workflow can be submitted to a Flux engine into different namespaces. In this manner, repository workflows can be workflow templates. But the name in the repository can be the same as when the workflow is submitted to an engine.
    5. Of course, access to the repository and repository actions are controlled by Flux security.
    6. We provide a number of example workflows for importing into your repository on our examples page.
  6. Let's now pick a Repository workflow and explore it's design
    1. Select the /Paris/Billpay/ workflow
    2. First - Let's show the different kinds of Flux Triggers and Actions
      1. What's a Flux Action and a Flux Trigger - you may ask ....
    3. Go through Core, Database, Workflow, Java, Web Services, File, Enterprise Java, Notifications
    4. Now - let's look at this workflow in detail. This workflow is an example we provide
    5. It uses actions and triggers from
      1. Core
        1. Timer trigger 
        2. Console Action
      2. Workflow
        1. For Each Element in a Collection
      3. Database
        1. Insert and Update
      4. Java
        1. Validate an item
      5. File
        1. Move to the Arhive
      6. and Notification
        1. Mail notifications of errors
  7. Review of Logs, Audit, and Run History Tab
  8. Concurrency and Clustering and Failover
    1. Runtime (or dynamic) configuration
    2. Failover consideration
    3. Restart and recovery and the Flux transaction (and transaction break)
  9. What's coming in Flux - new features and enhancements. And of course, performance, reliability, and resiliency features.
  10. In closing ...
  11. Questions?
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.