Altova FlowForce Server

Rp1

Description

Automate Data Transformation, Report and Document Generation, and More

Altova FlowForce Server is a highly-customizable workflow engine for efficient automation of enterprise-level data integration tasks.

FlowForce Server automates workflows for XML and XBRL processing, data transformation, report and document generation, and many other tasks executed on dedicated servers, virtual machines, or workstations scaled for the scope of the project

Workflow Automation Tool

FlowForce Server employs a Web interface to conveniently implement, manage, and modify data transformation jobs in a busy data processing environment. FlowForce Server can administer multiple transformation jobs simultaneously, lets users define and adjust a variety of job triggers and actions on the fly, performs housekeeping tasks like moving output files or cleaning up intermediate work, and much more.

FlowForce Server continuously checks for trigger conditions, starts and monitors job execution, and records detailed logs of all activity.

FlowForce Server Highlights:

Cross-platform Support:

  • Windows Server: 2008 R2 SP1 with Platform Update, 2012, 2016, 2019
  • Windows: Windows 7 SP1 with Platform Update, Windows 8, Windows 10
  • Linux: CentOS 7 & 8, RedHat 7 & 8, Debian 8, 9 & 10, Ubuntu 16.04, 18.04 & 20.04
  • macOS: 10.13 and above

FlowForce Server Jobs

Steps define what the FlowForce Server job must actually do. In its simplest form, a job step is an operation that executes a function and reports either a successful or failed outcome. Structures can be defined to execute job steps conditionally or in a loop. Nesting is possible, since one step can execute an entire separate job. A job may include as many steps as required, and they are executed in the defined sequence.

Built-in Operations

FlowForce Server includes built-in functions for common file system operations – copy, delete, move, etc., an FTP client, a mail function to send customizable event notifications, a command line shell, and more. Job steps can be defined to execute any built-in function, empowering users to efficiently perform routine housekeeping steps associated with data transformation and reporting tasks.

Job Automation

FlowForce Server can automate many common server processes, since one type of job step is an operating system command line with all its required parameters.

Jobs as HTTP Services

Triggers

Time triggers start one-time or repetitive job execution, file system triggers start jobs when a change is detected in a file or folder, or HTTP triggers poll a URI for changes.

Multiple triggers may be defined per job and several triggers can be active simultaneously. Whenever any trigger is fired, all execution steps of the job are processed.

Active Triggers

The Home screen of the Web interface lists all active triggers that will start future execution of FlowForce Server jobs along with the date and time of the next run for time-based triggers.

Another section of the Home screen displays all currently running jobs, with activation times and further details.

Time Triggers

Time triggers offer options to schedule execution by start and end time on days of the week, dates in the month, and more. You can schedule jobs to repeat at specified intervals, and even run multiple instances simultaneously if workflow requires.

Trigger Files and Execution Steps

FlowForce Server lets you capture the names of new files that arrive in a watched folder. Each trigger file name can be defined as an input parameter for job execution steps, including data mappings executed by MapForce Server or transformations performed by StyleVision Server.

Result Caching

Caching is especially beneficial for FlowForce Server enterprise-level data transformation jobs that work with large amounts of data, require complex database queries, or consume Web services where the performance of an external system may not be predictable.

Caching is supported for jobs that use parameters and combinations of multiple parameters. In the job configuration dialog, administrators specify multiple cache entries to match the number of possible parameter combinations that are expected in typical day-to-day usage.

The Refresh Cache timer triggers FlowForce Server to automatically run the job again in the background, using the same parameters, to update the cache. Instead of the typical stale cache expiry, you get automatically refreshed cache entry and can fine-tune the exact performance load on your back-end systems.

The same behavior applies for each possible combination of parameters, corresponding to each individual cache entry. Each parameter combination is seeded the very first time it runs, then, based on the Refresh timer, it is continuously updated.

Security

Administrators can configure security features to permit multiple departments or user teams to share use of a single powerful physical server without compromising each other’s server objects or private data stores anywhere on the network.

Users and Roles

All access to the FlowForce Server starts by logging in with a valid user name and password. System administrators create new user accounts and assign user privileges. Users are also assigned to one or more operating roles within the system.

Roles can be defined in a structure where one role is a member of another role and inherits all the wider role’s privileges. In addition, the narrower role can confer unique privileges. For instance, a role might be called Director of Manufacturing and be a member of the Manufacturing Department role, which in turn is a member of the Employees role.

This system allows administrators to easily configure groups users with identical privileges and creates a hierarchical organization of powers and responsibilities.

Containers

A container is similar to a folder in a file system. FlowForce Server containers create a hierarchical structure for storing configuration objects and even other containers. Administrators define access to containers by assigning access permissions for each role, and roles are in turn assigned to users.

Two predefined containers exist in FlowForce Server: /system contains built in system functions to allow FlowForce Server jobs to copy, move, or rename files, create directories, etc., and /public is the default container for mappings deployed from MapForce and stylesheets uploaded from StyleVision.

Administrators may create additional containers as needed, for example to isolate the resources of departments or other groups of users.

Credentials

A credential is a stored operating system login used to execute FlowForce Server jobs.

FlowForce Server jobs start automatically when a defined job trigger condition is met. FlowForce Server runs the job using a specific operating system user account, ensuring that job steps may not access unauthorized data, either accidentally or intentionally.

Every FlowForce Server job MUST have an assigned credential for the job steps to be executed. Additionally, the operating system user referenced by the credential must have sufficient access permissions to directories holding FlowForce Server components.

Credentials can be defined as standalone objects and assigned to multiple FlowForce Server jobs, or a credential can be manually entered for any specific job.

RaptorXML/XBRL Server

A FlowForce Server job can combine RaptorXML Server functions with MapForce Server data mappings, StyleVision Server report generation, and built-in file system operations to create a complete automated, high-performance solution for data transformation and reporting for XML, XBRL, database, flat file, EDI, Excel, and Web Service data sources.

MapForce Server

StyleVision Server

Web Interface

While FlowForce Server is running, the Web interface job log view provides a detailed history of all system activity and the job definition view provides intuitive access to all job definition options and functionality.

The Web interface enhances functionality in cross-platform environments since the interface can be displayed in any Web browser on any workstation on the network. Access to administrative resources and other server objects is defined by the log-in profile for each user.

Initial installation of FlowForce Server on any supported platform is simplified with a default configuration setup page. The full HTML help system with complete step-by-step instructions is just a click away.

FlowForce Server Advanced Edition

FlowForce Server Advanced Edition includes support for the AS2 specification for transporting data securely and reliably over the internet. AS2 is intended to improve upon existing file transfer protocols with increased security and includes an option feature to further encrypt data. Every transfer can also generate a return message to the sender identifying whether the transfer completed successfully or failed. AS2 was developed in conjunction with users who routinely transfer EDI, financial information, and other business data. AS2 support is a critical feature for enterprises that need to exchange EDI and XML data with partners in a secure way.

FlowForce Server Advanced Edition supports sending and receiving AS2 messages, and as such can act as both an AS2 client and server.

Advanced Edition also supports job distribution across multiple servers. Load sharing provides excellent scalability, with a group of computers sharing heavy data processing jobs. At the same time, this allows for high-availability: if one of the secondary computers stops functioning, the system will still continue to process FlowForce jobs.