Lomnido In Action

Excel To HTTP

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.

Receiving Emails

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.

HTTP Error Handling

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 [...]

Fail Fast, Succeed Faster

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 [...]

Use Case Trigger Pull Connector via Webservice

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

The Lomnido Workflow

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 [...]

Delivery Models

Both SIAM and SPIDER Lomnido platforms are available in 3 different delivery models, you can choose which one suits you best. Private Cloud - our hardware in our data centers On-premises (hardware) Cluster - our hardware in your data center Virtual Appliance - your hardware in your data center Private Cloud - hosted by Lomnido You get your own single tenant Lomnido Platform as a Service. Each platform is almost completely independent and shares only our bare metal and data center resources! Each Lomnido Private Cloud Instance runs on its own full GNU/Linux stack, hosting all data and programs isolated from other instances. Each instance gets its own dedicated public IPv4 and you decide how it will be accessible from the outside world! Our Private Cloud Instances do run only on our own hardware! We do not rent any computational nor storage resources. Both actively handled data and data at rest are under our control. Our Private Cloud instances are hosted in 2 geo-redundant data centers in 2 different EU member states and we do not store any active or backup data outside of EU. You keep control over your network even by using a Lomnido Private Cloud Instance. You [...]

Lomnido QA Process and Update Options

The Lomnido software delivery process follows an "Rolling Release" concept and has a continuous deployment pipeline that enables frequent and rapid deployment. The QA process is highly automated. Build Phase As soon as a developer has committed new code, the build server starts building the artifacts and runs the Unit Tests.  If no error occurs, the newly created version is provided to a "Test Runner" and three test environments. Automated Test Phase The automated tests consist of three different types: GUI Tests The GUI tests are based on Selenium and executed with a Google Chrome and a Firefox browser. Since the Lomnido user interface (UI) is mainly intended for administrators, we focus on this two browsers. There are currently 121 GUI test cases available. All tests together cover the entire graphical user interface. Each test case is recorded and enables errors to be found very quickly. Here is an example of an recorded GUI test case: API & Workflow Tests The main component of Lomnido is the workflow engine. With many workflow tests, we ensure that all types of connectors and workflow options are tested and that new functions are fully backwards compatible. As soon as a new feature is implemented, the [...]

Use Case Receive SOAP Messages

Of course Lomnido can receive SOAP messages. The only thing you need is a Workflow with an "Wait for HTTP" Inbound Connector and a Inbound Processor that expects XML. Optional you can define a Dataformat to deliver a more detailed WSDL definition. In this video you can see how such a SOAP workflow can be configured and be tested with an external tool like SOAP UI. It takes only 2 minutes to configure and test the Workflow!

Use Case CSV to HTTP

This example shows the basic structure of a Lomnido workflow to get an idea how things are done. In this example we upload a CSV file to the Lomnido Spider appliance. The workflow takes the csv, splits up the csv file into single records and sends out the records to a HTTP server. The data attribute mapping is done with a Drag & Drop interface. You do not need a single line of code. If you want to know more about the Lomnido SPIDER - just get in touch and order a free webinar. Your Name (required) Your Email (required) Subject Your Message

Lomnido Spider – the enhancement for SIAM Broker

In the world of SIAM you need not only to synchronize your processes, you need also to replicate or synchronize at least parts of your configuration management databases with your helpdesk tool and your provider organizations too.