About the Catalog module
As part of dataminer.services, the Catalog module allows Skyline customers and DataMiner Strategic Partners to browse and deploy available DataMiner connectors, packages, Visio drawings, Automation scripts, dashboards, and more.
DataMiner Catalog in DataMiner 10.4.6
Accessing the Catalog module
There are several ways to access the Catalog module:
Go directly to https://catalog.dataminer.services/.
Go to https://dataminer.services, sign in, and click Catalog on the landing page.
In DataMiner Cube, go to Apps > Catalog (from DataMiner 10.2.9/10.3.0 onwards).
Note
While you do not have to sign in to view Catalog items, not all functionality will be available if you are not signed in. To sign in, click the button in the top-right corner of the Catalog UI.
About Catalog items
A Catalog item is a small package that contains one or more artifacts that can be deployed on a DataMiner System. Different types of Catalog items are supported. For example, an item could be a single connector, or it could be an application package containing multiple dashboards, Automation scripts, and connectors.
At present, the following types of Catalog items are supported:
| Type | Description |
|---|---|
| Connector | Contains a DataMiner XML connector, integrating a specific third-party product with DataMiner for monitoring and control of that third-party product. Deploying the component will make it available on the target DataMiner System, where it can be used to create new elements. Connectors provided by Skyline are subject to updates. If you want to benefit from these updates, you should therefore not alter these connectors. |
| Scripted Connector | Contains a DataMiner scripted connector, enabling DataMiner to extract data from a third-party product for monitoring purposes. Deployment of the component will make it available on the target DataMiner System, where it can be used to create new elements. Scripted connectors provided by Skyline are subject to updates. If you want to benefit from these updates, you should therefore not alter these scripted connectors. |
| Ad Hoc Data Source | Contains a DataMiner ad hoc data source integration, which allows you to make data from third-party products and various data sources available for ad hoc display in DataMiner low-code apps and dashboards. Data from an ad hoc data source is not continuously extracted from the third-party product, so it cannot be used for fault management, performance management, and various other background functions in DataMiner. Deploying the component will make it available on the target DataMiner System. Ad hoc data sources provided by Skyline are subject to updates. If you want to benefit from these updates, you should therefore not alter these ad hoc data sources. |
| Data Transformer | Contains a data transformer, which allows you to transform data queried from DataMiner through a GQI data query prior to serving it to users in low-code apps or dashboards. Deployment of the component will make it available on the target DataMiner System, where it can be used as is, as part of your GQI data queries, or where you can further adjust it to meet your specific needs. |
| Data Query | Contains a GQI data query to extract data from DataMiner, to transform it, and to serve it to users in low-code apps or dashboards. Deploying the component will make it available on the target DataMiner System, where it can be used as is, or where you can further adjust it to meet your own specific needs. |
| Automation | Contains a general-purpose DataMiner Automation script to execute automation routines, triggered either on demand by users, based on a time schedule, or based on specific events that occur. Deploying the component will make it available on the target DataMiner System, where it can be used as is, or where you can further adjust it to meet your own specific needs. |
| User-Defined API | Contains a user-defined API, which adds a new endpoint to your DataMiner System tailored to a specific use case, and which enables third-party applications to consume selective data from your DataMiner System. Deploying the component will make it available on the target DataMiner System, where it can be used as is, or where you can further adjust it to meet your own specific needs. You will then have to make that new user-defined API accessible by generating and sharing a token with the intended party. |
| Dashboard | Contains a DataMiner dashboard. This can be a standard out-of-the-box dashboard or a sample dashboard, which can for example be used for training and reference purposes or to serve as a quick start template. Deploying the component will make it available on the target DataMiner System, where it can be used as is, or where you can further adjust it to meet your own specific needs. |
| Visual Overview | Contains a Microsoft Visio design, intended to be used for the DataMiner Visual Overview bubble-up and drill-down graphical UI. Deploying the component will make it available on the target DataMiner System, where it then needs to be assigned to the desired views, elements, or services. Optionally, you can further adapt or evolve the design to your own specific needs or preferences. |
| ChatOps Extension | Contains a ChatOps extension, which provides new custom commands to be used in Microsoft Teams ChatOps, enabling users to interact with DataMiner through chat. Deploying the component will make it available on the target DataMiner System, where it can be used as is, or where you can further adjust it to meet your own specific needs. |
| Product Solution | Vendor-specific integration, leveraging the DataMiner platform to provide superior value and centralized control. |
| Standard Solution | Standard solutions are DataMiner Solutions that are out-of-the-box solutions for specific use cases or applications. They are designed to require as little configuration and setup work as possible. Standard solutions are typically owned and managed by a Product Owner, who will release updates and evolutions of the standard solutions. If you want to benefit from those future updates and new versions, you should therefore not alter or change standard solutions. |
| Custom Solution | Flexible solution tailored for unique requirements, enabling adaptation to specific operational needs. |
| Learning & Samples | Educational resources and examples to explore or demonstrate DataMiner features. |
| DevTools | Tools for advanced customization, debugging, and optimization of your DataMiner environment. |
| System Health | Components to monitor performance, detect issues, and maintain system reliability. |
Public and private Catalog items
Public Catalog items are items that are available for anyone within the community to use.
Private Catalog items are items that are only available within your own organization. This gives users the possibility to develop app packages, Automation scripts, or any type of Catalog item and redeploy them within their organization on various systems.
Versioning of Catalog items
Catalog items can have multiple versions. To make sure that the versioning of items is easy to understand for everyone, semantic versioning is recommended. Extra labels can be assigned to versions to indicate that a certain version is not an official release (e.g. 1.2.3-alpha).
For Catalog items that follow semantic versioning, versions are grouped by range. A range is defined by the first three indicators of a version (e.g. 7.1.2.33).
Tags can be assigned to specific versions and ranges, for instance to indicate the main range of a connector. If you are a member of the organization that published an item, you can manage these tags via the 
button for each item.
The Catalog will recommend certain versions based on the following conditions:
- The latest version of a range that is tagged as the "Main" version (visualized in green).
- The latest version of a range that is tagged with a custom tag (visualized in gray).
- If neither of the above apply, the latest version of the highest active range will be recommended.
Note
Versions and ranges that are not supported (i.e. deprecated ranges and versions marked as pre-release or unlisted) are not shown by default. To view these, use the Unsupported versions toggle button.