| Contact | Customer Login

Flink-ESB Integration Platform

Tools to develop and run applications in production

This site is built using Flink-ESB Editor and runs on Flink-ESB Runtime Environment
Front End Applications

It takes just couple of seconds to create HTTP server in Flink-ESB Editor and start programming resources on top of that
>> Check tutorial about adding HTTP server to the project

You can add one or multiple routes which trigger on incoming request to the URIs and method you define
>> Check tutorial on creating route processing HTTP request

You can add Resource Manager to provide access to file system folder over HTTP
>> Check tutorial on creating HTTP file resource manager

You can import Web Application Archive

Protect resources with security

And all other things you would need to develop front end applications

This site is built using Flink-ESB Editor and runs on Flink-ESB Runtime Environment

Read more about Flink-ESB >>

Middleware, SOA, ESB, Microservices

Flink-ESB supports out of the box many dozens of enterprise integration patterns and communication protocols. You can work with HTTP (both server and client) using SOAP, REST, JSON etc., talk to databases, FTP servers, LDAP servers, JMS servers, TCP or UDP sockets, send or receive emails and many many other things

You can write within seconds a route which would read data from Database, translate it to any format, post it over HTTP to remote server and write an email confirming that job is done

You can define your routes in a way, that they can be called in a number of different ways (using plain HTTP, SOAP, REST, JSON, JMS etc.)

Read more about Flink-ESB >>

Back End Applications

Flink-ESB offers an outstanding support for talking to different kinds of back ends.

If you need a tool to create an application that would take data in some format, transform it and persist to some storage - Flink-ESB is the right tool for that

With Flink-ESB you don't need to take care of any format or protocol translations, Flink-ESB does it for you

Read more about Flink-ESB >>

Business Processes and Workflows

Business Processes and/or Workflows of any complexity can be easily designed with Flink-ESB Editor

Most software vendors either provide software for online processes or workflow engine. Different tools and totally different languages are used to program them

It is different with Flink-ESB. The same window within the same Editor is used to program both online processes and workflows. It is your desision whether a process will become a workflow. You define what parts of the workflow should be persisted, when and under what conditions

Read more about Flink-ESB >>

Batch Applications

You need an application that would perform some steps on regular bases, or triggered by some external or internal event? Probably interacting with the local machine and calling different shell scripts?

Flink-ESB offers all intruments you would need to build such an application with little efforts. You can test all the functionality right in the Editor, without having to install anything else

Read more about Flink-ESB >>

ETL Applications

With Flink-ESB you can design ETL processes within very short period of time

Flink-ESB offers many components for working with big amounts of data: writing in a batch to the databases or other storages, reading or writing huge amount of data over HTTP , reading or writing to the files, FTP etc.

Any process can be designed in stream mode to support working with big amount of data without consuming process memory

Any formats of data are supported

Read more about Flink-ESB >>

Front End Applications

It takes just couple of seconds to create HTTP server in Flink-ESB Editor and start programming resources on top of that
>> Check tutorial about adding HTTP server to the project

You can add one or multiple routes which trigger on incoming request to the URIs and method you define
>> Check tutorial on creating route processing HTTP request

You can add Resource Manager to provide access to file system folder over HTTP
>> Check tutorial on creating HTTP file resource manager

You can import Web Application Archive

Protect resources with security

And all other things you would need to develop front end applications

This site is built using Flink-ESB Editor and runs on Flink-ESB Runtime Environment

Read more about Flink-ESB >>

Middleware, SOA, ESB, Microservices

Flink-ESB supports out of the box many dozens of enterprise integration patterns and communication protocols. You can work with HTTP (both server and client) using SOAP, REST, JSON etc., talk to databases, FTP servers, LDAP servers, JMS servers, TCP or UDP sockets, send or receive emails and many many other things

You can write within seconds a route which would read data from Database, translate it to any format, post it over HTTP to remote server and write an email confirming that job is done

You can define your routes in a way, that they can be called in a number of different ways (using plain HTTP, SOAP, REST, JSON, JMS etc.)

Read more about Flink-ESB >>

Back End Applications

Flink-ESB offers an outstanding support for talking to different kinds of back ends.

If you need a tool to create an application that would take data in some format, transform it and persist to some storage - Flink-ESB is the right tool for that

With Flink-ESB you don't need to take care of any format or protocol translations, Flink-ESB does it for you

Read more about Flink-ESB >>

Business Processes and Workflows

Business Processes and/or Workflows of any complexity can be easily designed with Flink-ESB Editor

Most software vendors either provide software for online processes or workflow engine. Different tools and totally different languages are used to program them

It is different with Flink-ESB. The same window within the same Editor is used to program both online processes and workflows. It is your desision whether a process will become a workflow. You define what parts of the workflow should be persisted, when and under what conditions

Read more about Flink-ESB >>

Batch Applications

You need an application that would perform some steps on regular bases, or triggered by some external or internal event? Probably interacting with the local machine and calling different shell scripts?

Flink-ESB offers all intruments you would need to build such an application with little efforts. You can test all the functionality right in the Editor, without having to install anything else

Read more about Flink-ESB >>

ETL Applications

With Flink-ESB you can design ETL processes within very short period of time

Flink-ESB offers many components for working with big amounts of data: writing in a batch to the databases or other storages, reading or writing huge amount of data over HTTP , reading or writing to the files, FTP etc.

Any process can be designed in stream mode to support working with big amount of data without consuming process memory

Any formats of data are supported

Read more about Flink-ESB >>

for Development: Flink-ESB Editor
for IT Operations: Flink-ESB Admin Console
Use Flink-ESB Editor to create different kinds of applications
Create multiple projects at the same time in the same editor
Build complicated routes with no programming experience
Start projects in the editor and test their functionality
Interact with Flink-ESB cluster instances
Use Flink-ESB Admin Console to monitor applications
Check runtime statistics of all applications in cluster
View routes, route nodes and their parameters same way as in Editor
Have Flink-ESB analyze your applications and show you bottlenecks
Be able to call any route or bean on any cluster instance
for Development: Flink-ESB Editor
Use Flink-ESB Editor to create different kinds of applications
Create multiple projects at the same time in the same editor
Build complicated routes with no programming experience
Start projects in the editor and test their functionality
Interact with Flink-ESB cluster instances
Read more about Flink-ESB Editor >>
for IT Operations: Flink-ESB Admin Console
Use Flink-ESB Admin Console to monitor applications
Check runtime statistics of all applications in cluster
View routes, route nodes and their parameters same way as in Editor
Have Flink-ESB analyze your applications and show you bottlenecks
Be able to call any route or bean on any cluster instance
Read more about Flink-ESB Admin Console >>
Develop your Project with Flink-ESB Editor

Flink-ESB Editor is the only tool you need to develop all kinds of applications

You don't need to install any other software, like Web- or Application Servers

You can develop multiple projects at the same time using the same Editor, you can start them, check the functionality, try integration with already installed applications

Read more about Flink-ESB >>

Test the Project in the Editor

Flink-ESB Editor allows you to test every part of the project

If you code java classes and define them as beans in the project, you can start the project and call every method of such beans, try different arguments, and see whether they return what you expect

Try calling Routes using different payloads, properties and headers

Flink-ESB Editor comes with preinstalled Flink-ESB Admin Console. As soon as you start one or multiple projects in the Editor, you can use Admin Console to verify behaviour of different parts of the projects

Projects started in the Editor behave exactly as application installed in Flink-ESB Runtime Environment would behave. Test interaction with other applications. See how application reacts on different internal or external events or outages. Simulate outages or mistakes to verify application's behaviour

Read more about Flink-ESB >>

Install the Project in Flink-ESB Runtime Environment

Installing Flink-ESB application into Flink-ESB Runtime Environment is very quick and simple task, and can be achieved in different ways

Just drop an application jar into a certain folder, where Flink-ESB Runtime will pick it up and install

or copy it to any folder you wish and use SSH console to deploy it from there

You can also use Flink-ESB Admin Console to administer installation tasks

Read more about Flink-ESB >>

Use Flink-ESB Admin Console to monitor

Flink-ESB offers API to get different monitoring statistics from the running instances. This API is accessible to authorised users over HTTP from any machine. Format of output is either JSON or CSV, which allows to extract portion of data you would like to use in your custom monitoring script

Flink-ESB outputs statistics about all instances running in the cluster, or just instances / applications / routes you would like to have statistics for

You can also use Flink-ESB Admin Console to have all performance, error and runtime statistics in user friendly graphical format

Read more about Flink-ESB >>

Let Flink-ESB show your application‘s weak spots and bottleneckes

Flink-ESB protocols every call. The longer you use it, the more information it will show you on strong and weak spots of your application

You can see what errors were thrown, what kind of errors and on what places within your business processes exactly

Flink-ESB collects also performance statistics and shows you this information on Admin Console. You can see exactly what processes are to slow, on what place they are slow, and what exactly is done on that place

Just let Flink-ESB collect the information, and check it on Admin Console every now and then

Read more about Flink-ESB >>

Fix the Project in the Editor and reinstall it

Use Flink-ESB Admin Console or SSH Console to redeploy updated application

No restart of the process instance is needed for this

Read more about Flink-ESB >>

What is special about Flink-ESB?

There are many tools for developpers that simplify development process. We offer one of them

But our main goal is to make life of IT operation teams easy

No matter how complicated applications and processes would be, applications administrators will always know exactly what is going on in production

It is difficult to develop "bad applications" with Flink-ESB

Hard to believe that? As soon as "bad application" is installed on some environment, Flink-ESB will start gathering runtime statistics about it

No more blackboxes. Flink-ESB will collect all needed data and present it to admins in a very user friendly way. So at any time admins will know what part of applications are performing good, and what exactly is throwing errors or causing performance problems

Since Flink-ESB Admin Console shows every Process graphically exactly the same way developer sees it in Flink-ESB Editor, administrator will be able to recognize logical errors or inefficient processes

Just lean back and let Flink-ESB analyse your applications for you and suggest an improvement

Flink-ESB Message Gateway

You want to expose your internal services to the outside world?
You want to add a frontend layer to your existing services and have them reachable over one URL? Or you want to be able to group your services in a custom way?
You want to add a security and/or transformation layer to your existing services?
You want to add another protocol to your existing services, for example call your existing JMS Web Services over HTTP REST?
You are looking for a solution to migrate your services to cloud?
You want to be able to transfer huge files over HTTP or other protocols to some other host?
Define Façade Entries (URI where the service can be reached)

Use Message Gateway Config Console or SQL scripts to define façade entries

These entries contain: URIs you want Message Gateway to handle requests on; HTTP method (GET, POST, PUT or DELETE); security roles (you can define no roles, which means no authentication needed, or one or multiple roles - to protect this URL); group: one or multiple strings, which help to group services

You can define URI as regular expression, like "/.*". In this case all requests hitting Message Gateway will be handled by this channel

Mark façade entry as "stream_mode" to handle huge files without using internal memory (files bigger than 500 GB are supported)

Mark façade entry as "disabled" to disable entry (for example temporarily) without having to delete it completely. You can reenable it any time later, or delete it

Read more about Flink-ESB Message Gateway >>

Define Validation Rules you might apply to incoming requests

Use Message Gateway Config Console or SQL scripts to define validation rules

These are rules you might want to apply to incoming requests to check their validity. There are two types of rules: SCHEMA and CUSTOM

With SCHEMA rule type define URL of XSD schema file (can be on file system, HTTP URL or FTP URL). Message gateway will parse incoming requests against this schema file, if that rule is assigned to façade entry. If parsing against schema file fails - request is rejected

With CUSTOM rule type define any MVEL expression, which should return either "true" or "false". If it returns "false" - request is considered failed validation and is rejected. Using this rule type you can apply any kind of checks. MVEL expression is either static or dynamic. Dynamic means it can give different results based on incoming message content

You can assign zero or multiple validation rules to every façade entry. Request succeeds validation only if all relevant validation rules succeed

Define a custom exception message (if you want) for some rules, and it will be returned to the caller if that rule fails

Read more about Flink-ESB Message Gateway >>

Define Transformation Rules you might apply to requests or responses

Use Message Gateway Config Console or SQL scripts to define message transformation rules. These rules can be assigned to requests and/or responses

There are three types of transformation rules: XSLT, TEMPLATE and CUSTOM

Use XSLT transformation rule if a message is expected to be in XML format, which can be converted to some other format using XSLT. Define URL of XSLT file (can be on file system, HTTP or FTP)

Use TEMPLATE transformation to convert message of any format to any other format. For example you can easily transform XML into JSON, JSON into HTTP, or REST GET URL into message of any format

Use CUSTOM to define MVEL expressions to convert message. MVEL expression is either static or dynamic. Dynamic means it can give different results based on content of request and/or response or any other parameter

You can apply zero or one transformation rule on request or response messages

Read more about Flink-ESB Message Gateway >>

Define Message Properties you might add as HTTP Headers or JMS Properties to requests or responses

Use Message Gateway Config Console or SQL scripts to define message properties. These properties can be added to requests and/or responses as HTTP headers or JMS properties

Define message property name (static string value) and value expression, which is either static or dynamic MVEL expression. Dynamic means it can give different results based on content of request and/or response or any other parameter

You can assign zero or multiple message properties to any request / response

Read more about Flink-ESB Message Gateway >>

Define Destinations where the final service should be reached

Use Message Gateway Config Console or SQL scripts to define destinations. These are HTTP URLs or JMS queues, where a service you are exposing via Message Gateway URI is internally available

Destination could be either HTTP/HTTPS URL, or JMS queue. For HTTP/HTTPS select HTTP method among GET, POST, PUT or DELETE. For JMS select between REQUEST_REPLY or REQUEST_ONLY

Define user/password for destinations that require authentication

If HTTP/HTTPS destination is only reachable via proxy, you can assign proxy to relevant destinations. You can add/modify/remove any number of proxies if needed

Read more about Flink-ESB Message Gateway >>

Assign Validation Rules, Transformation Rules, Message properties, Destinations to Façade Entries

Use Message Gateway Config Console or SQL scripts to assign validation and/or transformation rules,message properties and destinations to façade entries

Assign zero or multiple validation rules to façade entries. Define "Condition" as MVEL expression to apply a rule only if that condition returns "true". Set "Ranking" to the rules to define order of their application. If needed, you can enable/disable any assignment without having to delete assignment or rule

Assign zero or multiple transformation rules to façade entries (only zero or one rule is applied, chosen by matching "Condition" and/or "Ranking"). You can separately assign rules for requests and response. Define "Condition" as MVEL expression to apply a rule only if that condition returns "true". Set "Ranking" to the rules to define which rule should be applied. If needed, you can enable/disable any assignment without having to delete assignment or rule

Assign zero or more message properties to façade entries. You can separately assign message properties for requests and response. Define "Condition" as MVEL expression to add a message property only if that condition returns "true". For requests if destination is HTTP destination - message properties will be added as HTTP headers, for JMS - as JMS properties. For responses message properties are added as HTTP headers. If needed, you can enable/disable any assignment without having to delete assignment or property

Assign one or more destinations to façade entries. You can assign destinations of different types (JMS and HTTP) to the same façade entry. Destination is chosen based on "Condition" and/or "Ranking". If needed, you can enable/disable any destination without having to delete assignment or destination

Read more about Flink-ESB Message Gateway >>

Publish configuration to running Message Gateway instances

Use Message Gateway Config Console to publish config changes to all running instances or use Flink-ESB Admin Console to reinitialize on every instance separately

Changes applied via Config Console or SQL scripts are reflected right away on running instances of Message Gateway without restarting them

Read more about Flink-ESB Message Gateway >>

Why should you choose Flink-ESB Message Gateway?

Use Flink-ESB Message Gateway Config Console or SQL scripts to quickly configure instances of Gateway

Any number of Message Gateway instances can be started from one DB configuration

Use different config groups to have different running instances handling different URIs

Clone configuration on multiple environments just by running SQL scripts. No adjustments in the database needed to create more environments from existing one

Any environment specific data in the database can and should be replaced by project variables

Apply changes to configuration and post them to running instances with no downtime

100% flexibility on defining your rules for validating requests, transforming requests/responses and selecting destinations

Despite its flexibility it is very fast and is able to handle any traffic

Quickly apply security policies to selected entries. Following authentication mechanisms are supported: LDAP, Database or File. With LDAP authentication you can enhance it by using a custom route, so that you can authenticate users with your corporate LDAP, but still have flexibility of assigning user roles in a way that fits your needs

Transform any message format to any message format. No exceptions to that rule. For example have rules for receiving REST GET requests, converting them to SOAP and sending to JMS queue, setting any custom JMS properties

Easily convert between transports HTTP / HTTPS / JMS

If needed provide credentials (user/password) to reach destinations

If not possible to reach some destinations directly, define and assign any number of different proxies to be used

Work with huge data (> 500 GB) without consuming internal memory for this

Legal Disclosure Contact Copyright (C) Verbundo GmbH - All Rights Reserved