Understanding your Data Architecture

As you use Oomnitza’s Connectors to manage increasingly large amounts of asset information, and create a single pane of glass, it becomes more and more critical that you understand your information architecture. Having a strong understanding of your information architecture allows for high confidence in the data in your Oomnitza system, prevents the creation of erroneous data, and helps drive good data hygiene practices.

The following steps will help you maintain a clear view of your data, and prepare you for the  process of bringing in new data.

Review your overall information architecture

Before setting up a new integration and bringing new information into Oomnitza, it’s vital to understand your existing information. Before adding a new integration, you should Identify the systems of record for all objects in Oomnitza (e.g. Macs from Jamf, PCs from SCCM, Users from LDAP, etc). Additionally, it’s important to understand what information is being pulled from these systems.

It’s important to understand that the “System of Record” is the origin of information for a given object or piece of information, and usage of that information in another location is a copy of this data. For example, Jamf may be your the system of record for hardware information on Mac Based Devices, Active Directory may be the source for all user information, and Oomnitza may be the source of information for User Assignments for devices, and for Asset Lifecycle information on these devices. 

Identify New Systems of Interest

In addition to identifying existing integrations, it’s important to identify the information you want to bring into Oomnitza. After reviewing your existing information, review the other systems you use regularly, including those that Oomnitza doesn’t currently integrate with. 


Oomnitza’s Holistic Integration update gives us the ability to quickly and easily integrate with external systems, and if you have a system you’d like to retrieve data from, you can learn how to request it here: https://oomnitza.zendesk.com/hc/en-us/articles/360056773473


More information on identifying these systems and creating a single pane of glass can be found here: https://oomnitza.zendesk.com/hc/en-us/articles/360057111234

Identify Stakeholders and Gain Access to New Systems

Now that you’ve identified the systems you want to integrate with Oomnitza who is the Business owner of the information in each system of record, so that individual can grant you access to that system. 

While this step is likely obvious, it can be a major hurdle towards setup, and is one of the most common reasons we at Oomnitza see integrations get delayed. 

Oomnitza’s Holistic Integration update adds The Credentials Table which makes the utilization of secrets within Oomnitza easy, while avoiding security risks and secret spread. 

Once the request has been approved, it’s important to take note of the details around the new credentials

  • Note the method of authentication to each system (Username/Password, API Token, or Oauth).
  • Note if a service account is being used.
  • Note if the password will expire.

Identify Information from your new systems

Once systems of record have been identified, identify which attributes you would like to pull into Oomnitza, how that data will be identified, and if it needs to be formatted within Oomnitza.

Identify attributes to pull in: This can be done through the Mapping page for a given integration within Oomnitza. 

Specify how those objects will be identified: When importing objects into Oomnitza, a “Sync Field” must be specified. This serves to identify how existing objects are differentiated from new ones, allowing for objects to be updated instead of created. This matching will prevent duplicates from being created, and when pulling data from a variety of sources, is vital in ensuring that objects sync effectively between these systems.

Identify Fields that must be transformed: Certain fields may need to be transformed to match existing information in Oomnitza. These fields, and their transformations should be identified. These might include transforming MB to GB, Computer Names into Serial Numbers, emails into Usernames, and other similar changes. 

Identify Bidirectional Candidates - Oomnitza’s API Workflow Block and API Presets allow for bidirectional integration of fields. When syncing a device with Oomnitza, there may be beneficial information about that device to send back to the system or origin. Those should be identified as well. 

Prepare for Integration

Now that you have a solid understanding of your integration landscape and have prepared you’re ready to begin adding your additional integrations. If you want to add information from systems Oomnitza doesn’t currently support, now’s a great time to make these requests. Otherwise, you can begin connector set up.

Identify order of operations when running connectors

It’s important to consider the order in which you set up integrations, especially when doing initial setup or integrating a large number of systems at once. In Oomnitza, the User and Location field types require the existence of Users and Locations in order to sync successfully. This, connectors should typically be set up in the following order:

  1. Manually create or Import Locations.
  2. Set Up User Connectors.
  3. Set Up Asset Connectors.

Install your Connectors

You’re finally ready to start setting up your connectors. This process varies by connector, but you can find instructions for each type of connector here: https://oomnitza.zendesk.com/hc/en-us/sections/360009017513



Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk