Skip to main content
Top
Review meshIQ Products (G2.com)

What are the databases used by the management applications?

Some of the content described in this article is available in meshIQ Manage versions 12.1 and greater. 
For a quick overview of what's new or changed, visit the meshIQ Highlights page for a version-by-version breakdown.  

Jump to Section:
Version 12.x and Later
Version 11.3 and Earlier

Version 12.x and Later

The meshIQ platform uses separate schemas to manage configuration, runtime data, and security across its management applications. The diagram below represents the current architecture as of version 12.0.x, highlighting the relationship between WorkGroup Servers (WGS), management GUIs, and supporting databases:

meshiq_db.drawio 2.png

 

Database Details

meshiq_apwmq

The meshiq_apwmq schema stores the WorkGroup Server (WGS) definitions, data collected from the managed systems, events, statistics, and audit information. This schema can store data from multiple WGS instances. The size of this schema depends on the amount of data collected.

meshiq_permitsv3

The meshiq_permitsv3 schema stores Manage definitions such as settings, viewlets, and dashboards. The data is designed to be shared across multiple environments. The size of this schema depends on the number of definitions but is typically much smaller than meshiq_apwmq.

meshiq_core_permits

The meshiq_core_permits schema stores Control Center (CC) security definitions such as users, groups, and roles. This data is also designed to be shared across multiple environments. Similar to meshiq_permitsv3, this schema is typically much smaller than meshiq_apwmq.

Overlap in Usage

There is limited overlap in usage across these schemas. The following are the only exceptions:

  • When the WGS loads the security definitions, these come from PermitsExpert using meshiq_core_permits tables.

  • When a user logs in (e.g., when importing users and roles), the WGS updates are performed via PermitsExpert against meshiq_core_permits tables.

  • When running a Manage statistics report, the queries directly access the meshiq_apwmq schema.

  • When using the PermitsExpert ControlCenter REST API, either directly or from the ControlCenter GUI, the system interacts with meshiq_core_permits.

  • When running a WGS audit report from ControlCenter GUI, the request is routed through PermitsExpert, which pulls data from meshiq_apwmq.

_______________________________________________________________________________________________________________

Version 11.3 and Earlier

The management applications (meshIQ Manage and Navigator) use an SQL database to contain a variety of information.  There are several types of data stored in 2 database schemas.  Note that schema means slightly different things in different database engines, but for this article, it uses the basic definition of a data store.

There are 2 unique schemas based on their primary usage.  These can be shared by multiple Workgroup Servers (WGS) and/or management GUI instances as long as all of them are at the same schema level.  Attempting to run a mismatched schema version will generate a warning message when logging in and in the WGS monitoring policy. 

  • The nastel_apwmq schema stores the Workgroup Server (WGS) definitions, data collected from the managed systems, events, statistics and audit information.  This schema can store data from multiple WGS. The size of this schema is dependent on the amount of data collected.  
  • The nastel_permv3 stores Web Security Manager (WSM) security definitions such as users groups and roles as well as management definitions such as settings, viewlets and dashboards. The data stored here is designed to be shared across multiple environments.  This size of this schema is dependent on the number of definitions but it typical much smaller than nastel_apwmq.

mceclip0.png

There is limited overlap in usage.  For example, the following are the only exceptions

  • When the WGS loads the security definitions, these come from nastel_permv3 tables 
  • When a user logs in (using import users and roles), the WGS updates the nastel_permv3 tables 
  • When running a statistics report, the queries directly access the nastel_apwmq
  • When using the WSM REST API either directly or from navxwsm
  • When running an WGS audit report in apodwsm 

The schemas are upgraded with each major release, as covered in How do I upgrade the database tables?.