Lomnido In Action

Lomnido supports emails and parsing Excel files. How this works is demonstrated in a short video.

The complete workflow is set up in a minute and needs no scripting knowledge. Everything is configures with a few clicks.

There’s life in the old dog – email is still a topic – also in today’s IT data integration projects. Therefore also the Lomnido SIAM Broker and the Lomnido Spider are supporting reading incoming emails.

Pushing messages to a remote (legacy) system over internet including VPN/IPSec tunnels is still a shaky thing. Connection timeouts, read timeouts, proxy failures, network issues, expired certificates (YES! Really!) and webservices that respond with weird http status codes. Queuing message and having control over the messages at a very detailed level is very important. Lomnido therefore provides out of the box concepts that can be configured with just a few clicks. FIFO Queue, Error Handling and Retry Read the article Fail Fast - Succeed Faster - there the messages queuing and error handling are already explained there. HTTP Push Error Handling The most used Connector is the HTTP Push Connector. By default, an HTTP message is marked as delivered, when the remote web server answers with a HTTP 2xx response code. But sometimes it is not as easy. Sometimes you also have to analyze the response headers and body. Imagine a web service that returns HTTP 200 but you have to handle error messages in the body. Or you would like to mark also messages as delivered if the server returns HTTP 404 with a special text in the response body. HTTP Response Rules Therefore, you can configure HTTP Response [...]

Failing of automated IT processes is unfortunately inevitable. Failing VPN tunnelns, servers in planned or urgency  maintenance, timeouts because of heavy traffic, changed APIs and so on. But failing is not the problem - the problem at all is not finding such failures or finding them very late! Therefore Lomnido has a lot of concepts how to handle failures, expected failures and unexpected failures. Failures on remote systems or failures in the Lomnido Workflows. Here are some of the key features. Integrate into your enterprise monitoring Lomnido is not a black box. Of course, you can integrate the Lomnido appliance into your monitoring. No matter if Nagios, Opsview, Zabbix, ...... Everything that is described in this article is possible to be monitor from an external monitoring tool. Connector Status, Alerthandler, ... everything is accessible with rest webservices or SNMP Traps. Connector Status A Connector in a Lomnido Workflow is the technical part that fetches or pushes a message from/to a connected system. Lomnido has HTTPS, (S)FTP, SQL, File Share, .... and a lot of more Connectors. Running or Stopped A connector can be running or be stopped. Running means that the Connector is waiting for messages to be pushed or [...]

Lomnido has of course Pull Connectors to pull data from different kind of sources. HTTP, SQL, files via (S)FTP, Windows File Share, .... Let us assume that we want to pull person records from a SQL database belonging to a certain organization and send them as CSV via email. The pull request should be triggered from an external client that provides also the organization ID of the desired users from the SQL database. In Lomnido you create a Workflow with an Inbound SQL Pull Connector and an Outbound Email Push Connector. Webservice Trigger Settings We activate the Webservice Trigger in the Pull Connector so that the pull request can be triggered by a web service request. Pull SQL Query The configured SQL query is like: SELECT * from persons where organization_id = ${msg.triggerMsg.ORGANIZATION_ID} Now, the external client can access the trigger webservice with a parameter like this: GET https://lomnidourl/lomnido/webservice/production/PullPersons?ORGANIZATION_ID=4711 When Lomnido retrieves such a webservice call, the Pull Connector starts pulling from the SQL database with the given ORGANIZATION_ID. Interested in a demo? Give us a call, order a demo session and talk about your special use cases. Your Name (required) Your Email (required) Subject Your Message

A workflow describes the flow and transformation of incoming data into outgoing data. It all begins with an inbound connector and an inbound data processor. Between the inbound data processors and the outbound data processors there is a data routing element. After the routing element there can be 0 to N outbound data processors and it all ends with outbound connectors. However, this is obviously not the end of a workflow! Workflows can be connected to other workflows. Connector A connector is the actual data transport interface from/to an external system. A connector is also used to transport data between workflows on the same platform. Processor A processor is a data processing element in which the main logic of the workflow is exectuted. Workflow Steps An Inbound Connector creates a message object called the "payload" for the workflow. This payload goes through the workflow and each workflow step can manipulate the payload. The manipulation can be done via settings that are configured in the GUI, Javascript or XSLT. And you can combine all of these things. No matter what data an Inbound Connector creates, the data is converted internally to a JSON dataformat. In the screenshot you can see an [...]

Easy staging processes are a major step in successful IT projects. Staging between Dev, Test and Production environments is done regularly. Lomnido has a very easy mechanism of doing this.