Technical Resources


Flux Flux

Technical Specifications




Pure Java

Flux is written in pure Java.


JDK 1.4 or greater

JDK 1.4 or greater is required to run Flux. Flux has been tested with JDK 1.4, JDK 5, and JDK 6 from Sun Microsystems and JRockit 1.4, 5 from BEA Systems.


Optional J2EE

The J2EE features are optional. They do not need to be used.


Optional EJB 1.1 or JMS 1.0.2

Flux's J2EE features are used, minimum requirements are EJB version 1.1 or JMS version 1.0.2.


Optional JDBC

Optionally, Flux can store flow chart information to a relational database using your JDBC driver. Or Flux can store flow charts in memory.


Optional Web User Interface

If you choose to deploy the optional Flux web user interface, the Flux Operations Console, it requires Java Servlets version 2.3 and JavaServer Pages 1.2.


Optional Web Services

If you use Flux’s Web Service Action, it requires Apache Axis.


Tested Platforms

Flux has been designed to work with any database that has a stable JDBC driver and any application server that supports EJB 1.1 or JMS 1.0.2. Flux has been tested specifically on the following platforms:


  • WebLogic Server 9.2, 9.1, 8.1, 7.0, and 6.1
  • WebSphere 6.1, 6.0, 5.1, 5.0, and 4.0
  • Oracle 10, 9, and 8
  • JBoss 4.1, 4.0 and 3.2
  • Tomcat 5.5 and 5.0
  • IBM DB2 9.1, 9.0, 8.1 and 7.2
  • SQL Server 2005 with row versioning enabled using the Microsoft JDBC driver
  • Sybase ASE 12.5 using the jConnect 5.5 JDBC driver
  • Sybase ASA 9.0 using the jConnect 5.5 JDBC driver
  • MySQL 4.1 using the com.mysql.jdbc.Driver JDBC driver with InnoDB table support
  • MySQL 5.0 using the com.mysql.jdbc.Driver JDBC driver with InnoDB and MyISAM table support
  • HSQL 1.8.0. When configuring engines with the HSQL database, do not use HSQL for clustering under any circumstances. HSQL is not robust enough for clustering use.

Clustering and Failover Platforms

Clustering and Failover for Flux does not require an application server. It requires only a database server. Clustering and Failover has been specifically tested on the following databases:


  • Oracle 10, 9, and 8
  • IBM DB2 9.1, 9.0, 8.1 and 7.2
  • SQL Server 2005 with row versioning enabled using the Microsoft JDBC driver
  • Sybase ASE 12.5 using the jConnect 5.5 JDBC driver.

Other Platforms

Although formal testing procedures have not been undertaken, customers have reported success when using Flux on the following platforms:


  • Oracle9i Application Server (OC4J)
  • Sybase ASE 12.0 and 11.9.2
  • Sybase EAServer 4.1
  • Sun ONE Application Server 7 (iPlanet 7.0)
  • Informix
  • PostgreSQL
  • Oracle Rdb (Oracle for OpenVMS platforms)
  • Mckoi SQL Database
  • Resin
  • Orion Application Server

Operating Systems

Flux is known to work on Windows, Solaris, HP-UX, AIX, Linux, AS/400, and OpenVMS systems. Other systems with a JVM are likely to work too.


Performance Metrics

We run performance metrics with each minor release. Each metric shows an average time on several tested databases.


  • job submission time
  • job firing time
  • job retrieval time
  • job removal time
  • job listing time
  • message publishing time
  • message consumption time

Learn More...


Special requests? Tell us what you would like to see!


Flux Migration Policy

No changes are made to API and database schemas between maintenance releases. For example, you can safely upgrade from Flux 7.4.1 to Flux 7.4.2 without any API or database schema changes. API and database schemas could change when upgrading between major and minor releases. For example, there may be API changes or database schema changes between Flux 7.4 and Flux 7.5. Database upgrade scripts are supplied to convert the database schema when upgrading. The database upgrade scripts are straight SQL scripts.


Technical Resources