Kalido-Heritage Products and Magnitude Software

I’ve worked with the Kalido heritage products since the late nineties. Sometimes I’m asked how being part of Magnitude has helped our products like Magnitude DIW and Magnitude MDM. One of the first examples was using the Noetix METL connectors to automatically build the semantic layer for some of the business intelligence tools. We used to use another method to do this that we had to pay extra for and didn’t fully control. If a customer asked us to change something, we had to raise the issue with the provider we used and then were at the mercy of their schedule to implement it (and in the worst case, sometimes denied the request). Fast forward to using METL, we now control the end to end process and could take advantage of other BI tools that METL supports in the future.

In 2016, Magnitude acquired the connectivity gurus at Simba Technologies. The benefit to the Kalido heritage products was immediate as Simba has a huge number connectors to relational, NoSQL and SAAS sources with more being added all the time. This greatly added to the number of systems that MDM and DIW could source from.

simplified access to data

How does this look from within DIW? Because Simba exposes sources using standard ODBC and JDBC, DIW can seamlessly access the data using the native ODBC connectivity. Let’s take Concur or Salesforce as an example. These Cloud-based Software as a Service systems generally expose their data via web services. The Simba drivers translate those web services and exposes them as what looks like ‘tables’. Let’s take a look at reading directly from Concur. First, setup an ODBC connection as you normally would. Then use the DIW Universal Load Controller wizard to access it.

You can either select the ‘table’ you want:

Or use the SQL Wizard to browse and select specific fields:

sql wizard

Browse the available ‘tables’ in the standard way:

browse concur tables

Then you can select the items you want. In this case, I’ve selected Reports:

select concur reports

This will then generate a SQL statement:

concur_SQL

Which you can then preview from within the Wizard:

concur results preview

Then you just save the job and either load the data immediately (in Dev) or schedule the job as often as you like in production. It’s just that easy! For a live look at this driver in action with DIW, please see the video below. If you have any questions, or want to learn more, simply contact us here!