Mendix Data Hub is a product for integrating app development with the data available from the many applications in an organization. It is the central hub in an organization for find and connecting to the relevant shared datasets. It also ensures consistency in the data used throughout the organization. Data Hub enables reliable data sources to be managed centrally from one point and for users to connect to them through it.
To use the Mendix Data Hub a license is required, with also includes the integration of Data Hub in Studio Pro, in order to discover shared assets in you organization and consume the shared data for building apps.
Follow the journey for building an app using available entities from the Data Hub home page, or try building a quick app by following How to Share Data Between Apps Using Mendix Data Hub.
2 Overview of Mendix Data Hub
Mendix Data Hub has components to enable the flexible sharing of entities. The following diagram shows how these components enable app development using shared entities:
- Published apps and other software expose entities in OData services that can be used to provide a consistent and reliable network of shared data. The data is maintained in the respective source apps.
- In Studio Pro, published OData services exposing entities connecting to the available data are automatically registered in the Data Hub Catalog. Other OData services can also be manually registered. For each service, structural and descriptive metadata and the location of the entities is registered in the Data Hub Catalog. Curation of registered services and entities is done by Owners of the service, Data Hub Admin and Data Curators.
- Search in the Data Hub Catalog or use the integrated Data Hub in Studio Pro to find suitable shared data assets to use in your app development.
- Consume exposed entities connecting to the shared data in Studio Pro to create new apps.
- Upon deployment of an app in Studio Pro, registered services are updated in the Data Hub Catalog to show published dependencies and consumed dependencies, and a connection is established to the shared data sources.
- The consuming application directly connects to the source system (as defined in the published service metadata) to use the data associated with the consumed entity.
- The Data Hub Landscape enables users to see the dependencies between components and the relevance of data and to ascertain data lineage.
3 Roles in Data Hub
In Mendix Data Hub, governance is the cornerstone. Curation of shared assets is essential for defining how the shared data assets can be used, identifying the relevance to users, ensuring that the resources can be found by the right users, and managing the accessibility, security and confidentiality levels of the shared data.
3.1 Data Hub Users
The typical Mendix user is able to use the Data Hub Catalog to search and use registered services. Users can also register new services through published OData services, and as owners, users are able to have curation rights over their OData services.
Data Hub users can do the following:
- Publish services and register them in the Data Hub Catalog from Studio Pro
- Register published OData V4 Services for non-Mendix apps manually
- Update the metadata such as descriptions, tags, and contact information of their own registered services
- Owners can set the discoverability of their services, thereby publishing the service and the exposed entities for use by other users
- See all the discoverable services and entities registered in their organization’s Data Hub Catalog and connect to the data by using the published entities as external entities in their apps in the Mendix Studios
A user who publishes an OData service is the technical owner of the service and thereby has a Data Hub Curator role over their own services. If they have registered services which are not published and are non-discoverable, only they will be able to find and consume these services.
3.2 Data Hub Admin
The Data Hub Admin role can carry out Data Hub operations and governance in collaboration with the organization’s data stewards, security officers, and security architects.
The Data Hub Admin can do the following:
- Act as a technical administrator of the organization’s Data Hub
- Assign Data Hub Curator roles
- Curate the Data Hub according to the organization’s data governance policy
- Access all the registered assets in the Data Hub Catalog for the organization
The Data Hub Admin for the current release of Data Hub is assigned by Mendix Support: please contact Mendix Support to set this up.
Admin tasks are described in Data Hub Admin Functions.
3.3 Data Hub Curator
The Data Hub Curator curates registered services in the Data Hub Catalog to ensure that registered services are visible to the relevant users and to enrich the information on registered assets. An organization can have several Data Hub Curators.
Curators are assigned by the the Data Hub Admin and they perform the following functions:
- Maintain registered OData services and manage versions
- Ensure the discoverability of their entities by the relevant users
- Enrich the metadata of registered services and entities – for example descriptions, tags, and contact information
4 Guide Categories
The Data Hub Guide is divided into the following categories: