System requirements
FLink Designer
- Platform
- Managed 64-bit Windows workstation or notebook.
- Planning baseline
- Modern processor with four logical cores, 8 GB RAM, 2 GB free disk space and a display resolution of at least 1280 × 800.
- Java
- 64-bit JDK 21 or JDK 25 for FLink 3.3. A JRE alone is not sufficient.
FLink Service
- Platform
- Vendor-supported 64-bit Windows, Linux or Unix system.
- Planning baseline
- Four logical cores, 8 GB RAM and 2 GB free application space. Production sizing depends on workload, concurrency and data volume.
- Java
- 64-bit JDK 21 or JDK 25 for FLink 3.3, preferably the same major version throughout one environment.
FLink Team Server
- Purpose
- Central repository for shared workflows, versions, releases, licenses, users, access control and keysets.
- Database
- Oracle, IBM Db2, Microsoft SQL Server or MySQL. Confirm the intended server and JDBC-driver combination before rollout.
Deployment planning
- Validation
- Final capacity depends on workflow complexity, data volume, concurrency, retention and availability targets.
- Compatibility
- Confirm the intended operating system, database, JDBC driver and JDK combination with FRAMETEXX before production use.
Connectivity
FLink workflows can connect to the following systems and transport mechanisms:
- Database
- FTP and SFTP
- File
- HTTP
- JMS
- IBM MQ
- Socket
- Stored procedure
- Web service
- System command
- Reuters
- Temenos Transact
- SAP
Database connectivity supports Oracle and Oracle RAC, Microsoft SQL Server, MySQL, PostgreSQL, ODBC, and IBM Db2.
Data transformation
Operator packages provide reusable building blocks for gathering, validating and transforming data:
- Database operators
- ESB operators
- Conversion operators
- String operators
- XML operators
- Constant operators
- Default operators
- System operators
- Math operators
- Date and time operators
- Logical operators
- Storage operators
- Temenos Transact online operators