Skip to end of metadata
Go to start of metadata

The following describes a general demonstration of Flux 8.0. 

  1. Setup 
    1. Open browser tabs to the 
      1. Console Page
      2. Monitor Page
      3. Example Workflows
      4. Log File Viewer  
    2. Open the Flux Architecture Depiction in the Flux Solutions Architecture Document
  2. (Opening) Flux orchestrates files. Our unique architecture integrates workflow, managed file transfer, monitoring, job scheduling, and error handling.
    1. Distinguishing Features -  Integration of workflow and managed file transfer. Entire interface is browser-based. Command-line and REST APIs. Triggers based on web service calls, database conditions. flle existence and non-existence, and timer expressions.
  3. (Supported Platforms) Sign on to the Flux Public Staging Server as s.flux.ly admin user
    1. Windows, Linux, Unix, and AIX Support
    2. Support for Java 6, 7, and starting with Flux 8.0.10 - Java 8. Will stop supporting Java 6 in Flux 8.0.11 (but only impacts the embedded web server)
    3. Mention database support and application server support. 
      1. Flux comes with an embedded web application server. Also runs within Weblogic, Websphere, JBoss, and Tomcat.
      2. SQL Server, DB2, Oracle, Postgres, MySQL, and Derby
  4. (Architecture) Review the general architecture of Flux - Engines (1 or many), Browsers, Workflows, and optionally, Agents. All of these components are managed through the Flux Repository.
  5. (Flux Repository) 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 (such as 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. (Flux Workflows) Let's now pick a Repository workflow and explore it's design
    1. Select the /Paris/Billpay/ workflowFirst - Let's show the different kinds of Flux Triggers and Actions
      1. What's a Flux Action and a Flux Trigger - you may ask ....
    2. Go through Core, Database, Workflow, Java, Web Services, File, Enterprise Java, Notifications
    3. Now - let's look at this workflow in detail. This workflow is an example we provideIt uses actions and triggers from Core
      1. Timer trigger 
      2. Console Action
      Workflow
      1. For Each Element in a Collection
      Database
      1. Insert and Update
      Java
      1. Validate an item
      File
      1. Move to the Archive and Notification
      1. Mail notifications of errors
  7. (Flux Operations) 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)
  8. (Flux Security) 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. Then spend a few moments on the Operations Console Tab - that control the visibility of the tabs to Operations staff
  9. (Logs and Audit and Reports) Review of Logs, Audit, and Run History Tab
  10. Concurrency and Clustering and Failover
    1. Runtime (or dynamic) configuration
    2. Failover consideration
    3. Restart and recovery and the Flux transaction (and transaction break)
  11. What's coming in Flux 
    1. New features and enhancements. New monitor and updated designer
    2. Provisioning and onboarding interactions
    3. And of course, performance, reliability, and resiliency features.
  12. Questions?