• Get started
  • Documentation

Import your data

Assets Data Manager for Jira Service Management Cloud is currently rolling out in Open Beta and will be available to all Premium + Enterprise sites by end of October 2024.

This task requires Data Manager admin permissions to complete. How permissions and roles work in Data Manager.

The Import process reconciles all of the data sources associated with the object class to create Data Manager objects. It can be triggered manually, but is usually triggered by running the Cleanse and Import client from the command-line.

Import your Data manually

Before you can start an import, all the data sources associated with the object class you are importing must be Mapped and Cleansed.

To import a single data source manually from within Data Manager:

  1. From within Data Manager, select Cleanse and Import in the left menu bar.

  2. Select a single Data sources to cleanse.

  3. Select and then select Import. You will now see the results from the previous import operation.

  4. Select >>Start. The import process will begin and the results from the import will update automatically. If you leave this page, the import will not be halted but will complete in the background.

To import multiple data sources manually from within Data Manager:

  1. From within Data Manager, select Cleanse and Import in the left menu bar.

  2. Select one or more Data sources in the left menu bar.

  3. At the top of the page, select Import selected. You will now see the results from the previous import operation.

  4. Select >>Start. The import process will begin and the results from the import will update automatically. If you leave this page, the import will not be halted but will complete in the background.

You can view the results of your imported data in the Data Manager > Analysis screens, viewable as a list, chart, graph, or in many other ways.

Import your Data using the Cleanse and Import client for MacOS

While Cleansing and Importing can be done through Data Manager, you can also Cleanse and Import your data using the Cleanse and Import client from the command-line.

Before you can start an import, all the data sources associated with the object class you are importing must be Mapped and Cleansed.

Before you can run the Cleanse and Import Client, you must first have created a Cleanse and Import token, and you must have recorded your WorkspaceID.

If any parameters in your commands have spaces within them - for example my data source name as opposed to my my_data_source_name, you must encase the parameter within double quotes: "my data source name".

To run the Cleanse and Import client client for MacOS:

  1. Open a command line interface by navigating to the Finder App in Mac (Applications > Utilities > Terminal).

  2. Navigate to the location of the Data Manager clients.

    1 cd /Users/Shared/assets_data_manager
  3. Select the version of the Cleanse and Import client that matches your CPU. Pick from:

    1 2 cd osx-arm64/assets-cleanse-and-import-client cd osx-x64/assets-cleanse-and-import-client
  4. If you like, you can use the help command to find out more information about how to configure the Cleanse and Import client:

    1 ./dm-cleanseimport --help
  5. You will need the following two pieces of information to run the app:

    1. Your Workspace ID. This should look something like this:

      1 e44regc98-8d2r-3af7-011t-209p44716366
    2. Your Cleanse and Import client token. You can create this token by following the instructions here. A complete token should look something like this:

      1 ATCTT3xFrTN0U64VR99p1VfpQtLlpar7R4hq6PSkiNNaNOyk37P_7URVmROOp1Orez-ijlluMRwJA7Cw1LsgMFq
  6. Run the Cleanse and Import client app on the command line interface, replacing the placeholder text with your workspace ID and Cleanse and Import client token:

    1 ./dm-cleanseimport --run "import" --workspace-id <workspaceId> --token <your-Cleanse-and-Import-token>
  7. You can also use these optional parameters when running the app:

    1. Choose to both Import and Cleanse the data simultaneously by replacing the “import" parameter with “full”.

    2. Choose a single Data Source Type to Cleanse or Import. If your Data Source Type name includes spaces, you will have to encase it in quotes:

      1 --type "My Data Source Type Name"
    3. Choose a single Data Source to Cleanse or Import. If your Data Source name includes spaces, you will have to encase it in quotes:

      1 --ds "My Data Source"
    4. Choose a single Object Class to Cleanse or Import.

      1 --object "Compute"
    5. Choose a proxy server:

      1 --proxy "Address" or -p "Address"
    6. Choose a username to authenticate against the proxy server:

      1 --proxy-user "Username" or --proxy-user Username
    7. Choose a password to authenticate against the proxy server:

      1 --proxy-pass "Password" or --proxy-pass Password
    8. Use the default credentials to authenticate against the proxy server:

      1 --proxy-default-credentials
    9. Bypass any invalid server certificates that appear when authenticating to the proxy server:

      1 --bypass-invalid-certificate
  8. A success message should tell you when the job is complete and if any errors were encountered while the Cleanse and Import client was running.

Import your Data using the Cleanse and Import Client for Linux

While Cleansing and Importing can be done through Data Manager, you can also Cleanse and Import your data using the Cleanse and Import client from the command-line.

Before you can start an import, all the data sources associated with the object class you are importing must be Mapped and Cleansed.

Before you can run the Cleanse and Import Client, you must first have created a Cleanse and Import token, and you must have recorded your WorkspaceID.

If any parameters in your commands have spaces within them - for example my data source name as opposed to my my_data_source_name, you must encase the parameter within double quotes: "my data source name".

To import your data using the Cleanse and Import client in a Linux environment:

  1. Open a command line interface by using Cmd + Alt + T.

  2. Navigate to the location of the Data Manager clients.

    1 cd /Users/Shared/assets_data_manager
  3. Select the version of the Cleanse and Import client that matches your CPU. Pick from:

    1 2 cd linux-arm64/assets-cleanse-and-import-client cd linux-x64/assets-cleanse-and-import-client
  4. If you like, you can use the help command to find out more information about how to configure the Cleanse and Import client:

1 ./dm-cleanseimport --help
  1. You will need the following two pieces of information to run the app:

    1. Your Workspace ID. This should look something like this:

      1 e44regc98-8d2r-3af7-011t-209p44716366
    2. Your Cleanse and Import client token. You can create this token by following the instructions here. A complete token should look something like this:

      1 ATCTT3xFrTN0U64VR99p1VfpQtLlpar7R4hq6PSkiNNaNOyk37P_7URVmROOp1Orez-ijlluMRwJA7Cw1LsgMFq
  2. Run the Cleanse and Import client app on the command line interface, replacing the placeholder text with your workspace ID and Cleanse and Import client token:

    1 ./dm-cleanseimport --run "import" --workspace-id <workspaceId> --token <your-Cleanse-and-Import-token>
  3. You can also use these optional parameters when running the app:

    1. Choose to both Import and Cleanse the data simultaneously by replacing the “import" parameter with “full".

    2. Choose a single Data Source Type to Cleanse or Import. If your Data Source Type name includes spaces, you will have to encase it in quotes:

      1 --type "My Data Source Type Name"
    3. Choose a single Data Source to Cleanse or Import. If your Data Source name includes spaces, you will have to encase it in quotes:

      1 --ds "My Data Source"
    4. Choose a single Object Class to Cleanse or Import.

      1 --object "Compute"
    5. Choose a proxy server:

      1 --proxy "Address" or -p "Address"
    6. Choose a username to authenticate against the proxy server:

      1 --proxy-user "Username" or --proxy-user Username
    7. Choose a password to authenticate against the proxy server:

      1 --proxy-pass "Password" or --proxy-pass Password
    8. Use the default credentials to authenticate against the proxy server:

      1 --proxy-default-credentials
    9. Bypass any invalid server certificates that appear when authenticating to the proxy server:

      1 --bypass-invalid-certificate
  4. A success message should tell you when the job is complete and if any errors were encountered while the Cleanse and Import client was running.

Import your data using the Cleanse and Import client for Windows/DOS

While Cleansing and Importing can be done through Data Manager, you can also Cleanse and Import your data using the Cleanse and Import client from the command-line.

Before you can start an import, all the data sources associated with the object class you are importing must be Mapped and Cleansed.

Before you can run the Cleanse and Import Client, you must first have created a Cleanse and Import token, and you must have recorded your WorkspaceID.

If any parameters in your commands have spaces within them - for example my data source name as opposed to my my_data_source_name, you must encase the parameter within double quotes: "my data source name".

To import your data using the Cleanse and Import client in a Windows/DOS environment:

  1. Open a command-line interface using Ctrl + Shift + Enter (to open as an Administrator), or by clicking on the Windows icon using the mouse, then typing in “CMD” and select “Run as administrator”.

  2. Navigate to the location of the Data Manager clients.

    1 cd Users/Public/assets_data_manager
  3. Select the version of the Cleanse and Import client that matches your CPU. Pick from:

    1 2 cd win-x64/assets-cleanse-and-import-client cd win-x86/assets-cleanse-and-import-client
  1. If you like, you can use the help command to find out more information about how to configure the Cleanse and Import app:

    1 dm-cleanseimport.exe --help
  2. You will need the following two pieces of information to run the app:

    1. Your Workspace ID. This should look something like this:

      1 e44regc98-8d2r-3af7-011t-209p44716366
    2. Your Cleanse and Import client token. You can create this token by following the instructions here. A complete token should look something like this:

      1 ATCTT3xFrTN0U64VR99p1VfpQtLlpar7R4hq6PSkiNNaNOyk37P_7URVmROOp1Orez-ijlluMRwJA7Cw1LsgMFq
  3. Run the Cleanse and Import app on the command line interface, replacing the placeholder text with your Workspace ID and Cleanse and Import token:

    1 dm-cleanseimport.exe --run "import" --workspace-id <workspaceId> --token <your-Cleanse-and-Import-token>
  4. You can also use these optional parameters when running the app:

    1. Choose to both Import and Cleanse the data simultaneously by replacing the “import" parameter with “full".

    2. Choose a single Data Source Type to Cleanse or Import. If your Data Source Type name includes spaces, you will have to encase it in quotes:

      1 --type my_data_source_name
    3. Choose a single Data Source to Cleanse or Import. If your Data Source name includes spaces, you will have to encase it in quotes:

      1 --ds my_data_source
    4. Choose a single Object Class to Cleanse or Import. Currently, Data Manager supports three types of objects classes: Compute, User, and Network.

      1 --object Compute
    5. Choose a proxy server:

      1 --proxy my_proxy_server_address
    6. Choose a username to authenticate against the proxy server:

      1 --proxy-user my_username
    7. Choose a password to authenticate against the proxy server:

      1 --proxy-pass my_password
    8. Use the default credentials to authenticate against the proxy server:

      1 --proxy-default-credentials
    9. Bypass any invalid server certificates that appear when authenticating to the proxy server:

      1 --bypass-invalid-certificate
  5. A success message should tell you when the job is complete and if any errors were encountered while the Cleanse and Import client was running.

Still need help?

The Atlassian Community is here for you.