Import/export of services

ADCM offers the import and export of services. For a service, import is essentially a transfer of the specific service settings. The service settings being imported are listed in the product bundle, precisely, in the import section of the service description.

The settings that are available for import are called exported settings. The exported settings for a service are listed in the export section of the service description.

Import defines what settings a service is able to receive from other services. Hence, no service is imported or exported physically. Only the settings are being transferred.

For instance, let us have a hadoop cluster that contains a ranger service as able to be imported from another cluster. Then the ranger service will contain the exported settings in the export section of the ranger service description. Those settings become available for the ranger service when it is imported into other clusters and can now be accessed at configuration level.

Imports are product-specific and are not included into a product by default. Imports are present in a product only if imports are explicitly declared in the product bundle.

Everything that concerns the import and export of services is also true for clusters.

Import tab

You can view the cluster imports at the Import tab.

import 1
Import tab

To change the set of service settings that are being imported, click a checkbox in the relevant service. To save the changes, click Save.

The export of services is not represented in the ADCM interface. You can view the service’s exported settings in the service description. The descriptions contains sections and configurations that are being exported.

Mandatory imports

If a service requires some imports, those imports are called the mandatory imports.

For instance, let us create a cluster and add the monitoring service to it. The monitoring client inside a cluster is useless by itself — the client is able to accumulate data, yet it doesn’t know where to send it. To send data, the monitoring client needs the information from an external service, that, essentially, what an import is.

The main idea behind the import of services is to allow the re-use of service settings. ADCM might contain a lot of clusters and for them not to contain the similar services physically, we allow the import of just their settings.

For example, there are some common services, such as the monitoring service or the ranger service, that are frequently needed. Those services become candidates for re-use, so a standalone monitoring cluster is created for all other clusters to access. This allows you to avoid the clusters containing the services they don’t directly need.


Let us have the ADH cluster that contains various services. We’d like the ADH cluster to receive configurations from another cluster — that might be useful for migration tasks or to integrate with some external services. To do this, we need the graphite or grafana settings to be imported.

In order to change the set of settings that is being imported, do the following:

  1. Navigate to the cluster page and select the Import tab.

    import 2
    The first step of changing imports
  2. The Import tab shows the settings (along with the versions) that are available for import. You can change what is being imported by clicking a checkbox. To save the changes, click Save.

    import 3
    The second step of changing imports
  3. If a service contains nothing that is available for import, the settings are not shown (registry, http, and ranger in the above images).

Found a mistake? Seleсt text and press Ctrl+Enter to report it