Niklas Integration Platform

Niklas Integration Platform is an enterprise service bus (ESB) developed by Copernicus Interchange Technology. The platform enables organizations to automatically exchange electronic data between internal applications (EAI), other organizations and several cloud services.
Features
Monitoring & Control
The extensive logging mechanism enables administrators to monitor the message flow on all levels. Niklas has the following logs available for its users:
* Message log
* Transport log
* System log
* Content log
* Scheduler log
* Event log
Error & Exception Handling
Niklas supports multiple layers of exception handling. The most specific layer is that of the outgoing transports because of the support of a “retry” functionality. This ensures that in the situation a message cannot be delivered, Niklas will try again at a later time. The frequency and interval of this “retry” functionality is configurable on the transport level. When a maximum of retries is reached, a notification will be sent to error handling.
As soon as an exception occurs during the processing of a message, this will be handled by the exception handler of the Agreement. This tackles all errors for an Agreement such as sending email alerts to the administrators or sending error messages to another Agreement for further processing.
Archiver
The archiver is a component which is used in Agreements and takes care of archiving the content and meta-data of messages. The archiver is highly configurable, from very straightforward to highly complex. Additionally, archived messages can be reached from the logs in the user interface of Niklas. This enables users to view messages and download during different the different stages of an Agreement. The Archiver also makes it possible to retransmit a message.
Splitter
The Splitter is used to split the payload of a message up into several messages, which can than be processed separately. A typical use of the Splitter is to split a sizable article file into several smaller messages and push it - whether of not multithreaded - to the API of a webshop.
Content Based Routing
Message Identification is the process of recognizing a message directly after it’s received. Based on the content of a message (Content Based Routing) or on certain criteria such as filename the message can be correlated to a Trading Partner and send to a specific Agreement.
Niklas supports the following methods of recognition:
* Based on filename
* XPath
* Based on envelope data (such as with Edifact or X12 messages)
Trading Partner Management
Organizations who exchange electronic documents with each other are called “Trading Partners” in EDI terminology. Trading Partners agree on which data must be exchanged and which method should be used for the exchange. In Niklas, Trading Partners, can be set up for use in Agreements.
Several identifiers and contact can be connected to a Trading Partner. In the situation where an exception occurs in an Agreement for a specific Trading Partner, an email alert will be send to the contact which is connected to the Trading Partner.
Deployment
Niklas uses a real-time configuration model for the deployment of integrations. All changes to the configuration will be carried out immediately without having the restart the server. The change will be effective immediately.
Niklas administrators can easily deploy new mappings. Additionally, the user can declare on which environment (TST, ACC, PROD) the mapping should be deployed.
Scheduler
Niklas has a special engine for the planning and execution of several different tasks: the Scheduler. The Scheduler can be configured to periodically perform specific tasks on one or several processing engines. Typical uses of the Scheduler include starting communication sessions, data retrieval from a database or performing several maintenance tasks.
Communication
Niklas is a modern enterprise service bus and features a sizable set of adapters for data communication. Using these adapters both synchrone and asynchrone sessions can be set up in a secure way. Niklas includes the following adapters:
* File
* FTP, SFTP
* EMAIL (POP3, POP3S, IMAP, IMAPS, SMTPS)
* JMS (IBM MQ, ActiveMQ)
* HotFolder
* HTTP, HTTPS
* REST
* WebServices
* AS2
* TCP
 
< Prev   Next >