Niklas Integration Platform
Niklas is the affordable and scalable Enterprise Service Bus for all your Enterprise Application Integration and Business-to-Business Integration. The platform enables organisations to easily exchange fully automated electronic information with internal applications, other organisations and a variety of cloud services.
Fast data processing
Niklas places a strong emphasis on fast data processing, scalability and ‘supportability’. The platform supports transformations between different types of data and data sources that enable the quick and easy setup of data streams, regardless of data format or communication protocol.
Niklas is a highly versatile integration platform. Depending on the requirements, it can be configured to work as a ‘ single server ‘ application or as a multi-server distribution environment. The functionality Niklas offers can be divided across multiple instances and a number of specific processes (called ‘engines’) can be configured, for each instance. It is possible to divide all processes or part of the Niklas processes across one or more instances which allows for a very flexible approach.
No vendor lock-in
For data transformations (mappings) Niklas is able to use any mapping tool, provided this tool is capable of generating code in either Java or XSLT. As a result, there’s no so-called ‘vendor lock-in’ in terms of the direction of a private mapping tool, which can be a stumbling block for many organisations.
Monitoring & controle
Niklas’ extensive logging mechanism allows administrators to monitor the flow of messages right down to the lowest level. Niklas uses different logs for this:
- Message log
- Transport log
- System log
- Content log
- Scheduler log
- Event log
Niklas is a modern Enterprise Service Bus and has access to a large set of adapters for data communication. Using these adapters, both synchronous and asynchronous sessions can be set up in a secured way. Below you will find a list of the adapters that are included with Niklas:
- FTP, SFTP
- EMAIL (POP3, POP3S, IMAP, IMAPS, SMTPS)
- JMS (IBM MQ, ActiveMQ)
- HTTP, HTTPS
We have a number of off-the-shelf interfaces available, including:
- Google Merchant Center
- De Buren collection center
- Various transport companies
Niklas supports multiple layers of exception handling. The most specific layer is that of the outgoing transport because it supports the ‘retry’ functionality. The retry functionality ensures that, when a message can not be delivered the first time, Niklas will try again later. The frequency and interval of the retry functionality can be configured at transport level and when the maximum number of retries is reached, the case will be passed on to error handling.
Once an exception occurs while processing a message, this will be handled by the exception handler of the Agreement. This handles all errors for an Agreement such as sending email alerts to administrators or forwarding erroneous messages to another Agreement to further process the message there.
The Archiver is a component that can be used in Agreements and takes care of archiving the content and meta-data messages. The Archiver can be configured very extensively, from simple to highly complex. An additional advantage of the Archiver is that the messages that gave been archived, can be accessed from the logs in the Niklas user interface, so that users can view and download messages at various stages of an Agreement. The Archiver offers the ability to resend messages.
The Splitter is used to split the payload of a message (provided that it is a collection) into multiple messages that can subsequently be processed separately. For example, the Splitter can be used to split a great article file into more small posts and feed this – whether or not multithreaded – to the API of a webshop.
Message Identification is the process of recognising a message, which happens immediately after the message is received. Based on the contents of a message (Content Based Routing) or on the basis of criteria such as, for example, the filename being correlated to a Trading Partner, the message can then be sent to a specific Agreement. Niklas supports the following recognition methods;
- Based on the filename
- On the basis of envelope data (for example, Edifact or X12 messages)On the basis of envelope data (for example, Edifact or X12 messages)
Organisations that exchange electronic documents with one another, in EDI terminology, are known as ‘Trading Partners’. Trading Partners make agreements on issues such as what type of data can be exchanged and how this should be done. Trading Partners can be set up using Niklas and applied in Agreements.
A Trading Partner can be associated with different identifiers and there can also be multiple contacts. For example, when an exception occurs in an Agreement for a specific Trading Partner, an email alert will be sent to the appropriate contact person.
Niklas uses a real-time configuration model for the deployment of integrations. Any change in the configuration is implemented directly, without the need to restart the server. The change is effective immediately.
Niklas administrators can easily deploy new mappings in Niklas. The environment (TST, ACC, PROD) the mapping should be deployed to can also be set.
Niklas has a special engine for planning and performing different tasks: the Scheduler. The Scheduler can be configured to periodically perform certain tasks on certain (or multiple) Processing engines. The Scheduler can be used, for example, to start communication sessions, to retrieve data from a database or for different maintenance tasks.
How can we help you?
Contact us and we will get back to you as soon as possible!