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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>

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 >>