Import data into Jira Service Management

Import data into Jira Service Management Cloud

Configure Assets in Jira Service Management Cloud

1. If you have not already created an object schema, create one now.
   We recommend the ITSM template for this as it contains all the common object types used by Discovery.

2. In your object schema, create a new import configuration.

   1. In the Import type screen, select Discovery Import.

   2. In the Define structure screen, select the file created by Assets Discovery (above).
      The import connection should automatically create a structure and configuration for the data it receives from Assets Discovery.
      In some cases, the import connection might fail to create a structure and configuration automatically. If this occurs, you may have to create both the structure and configuration manually.

3. Back in the Import configuration screen, select the cogwheel at the far right of the import configuration you have just created and select Generate token.

4. Copy the token created by Assets.

Synchronize Assets Discovery with Assets in Jira Service Management Cloud

1. Configure Assets Discovery.
2. Select the Export tab.
3. Select Export Type and change from None to Cloud.
4. In the Auth token field, paste the token you copied from Assets earlier.
5. Exit Assets Discovery configuration.
6. Review your results. Your object schema should now contain object types, objects, and attributes imported from Assets Discovery.

Now that Assets Discovery is configured to export directly to Assets, the results of any Assets Discovery scans - either manual or scheduled - will automatically upload, import, and synchronise with Assets.

If you are using Assets Discovery 3.1.3 or later, you can have multiple imports of the same import structure queued at the same time

Import data into Jira Service Management Data Center

Configure Assets in Jira Service Management Data Center

1. If you have not already created an object schema, create one now. How to create object schemas
   We recommend the Create sample IT asset schema template for this as it contains all the common object types used by Discovery.
2. Navigate to the Import section in the object schema configuration.
3. Once you install the Discovery app, you'll see a new import type, Discovery import, in Assets.
   You need to use this type to create an import configuration before you can start importing your data.
4. Use the Discovery import type and create an import configuration.
   In the Directory field, select the folder that’ll contain the scan results from Discovery.
5. To automatically synchronize data, make sure to select the Automatically synchronize checkbox in the Scheduling tab and set up fields such as, Synchronizing account and Cron expression.

Synchronize Assets Discovery with Assets in Jira Service Management Data Center

At the end of the import configuration, you can also choose to automatically create the predefined structure and predefined configuration — this will create all object types with attributes and relationships in the schema, as well as set up all object type mappings in your import configuration.

1. Enable the import configuration you created earlier.
2. Make sure to configure the Export type (either SFTP or FileCopy) in Discovery and that the directory you configured in your import configuration earlier, contains the scan results from Discovery and can be accessed by Jira Service Management Data Center. How to configure export type
3. From the cog icon of the import configuration, select Synchronize.  

Assets will import data collected by Discovery at the scheduled interval.

Importing data for the first time

As the initial import include a lot of data and takes more time than the subsequent imports, we recommend the following steps:

1. Configure the import in an empty object schema.

2. Configure the import to exclude applications, application services, virtual guests, and patches in your first import.
   This way, Assets will import only hosts and basic corresponding data, which should make the import faster. 

3. Enable and sync your import. Assets will import only hosts and basic corresponding data, which should make the import faster.

4. Include applications in the second import.

5. Include application services in the third import.

6. Include virtual guests and patches in the subsequent imports.

Import type settings

Date patterns

You don't need to specify the date pattern in the general import configuration settings. You can choose to specify them to improve the import performance. Here's some examples:

• Date Format: dd/MM/yyyy
• Date/Time Format: dd/MM/yyyy hh:mm

Module specific configuration

Fetch data strategy

Assets Discovery import will import the data in the configured Directory folder. However, on each import, it will only import the oldest data grouped by date. Assets looks into the filename to recognize the date, not the modification date on the disk.

For example, if you have the following data in the directory:

-rw-r--r--@  1 mathias  staff    52719 Oct 23 08:50 4D268_2017-01-05_1129.zip
-rw-r--r--@  1 mathias  staff  1724595 Oct 23 08:50 67A4A_2017-06-10_0023.zip
-rw-r--r--@  1 mathias  staff  1724595 Oct 23 08:50 57G4K_2017-06-10_0242.zip
-rw-r--r--@  1 mathias  staff  1724711 Oct 23 08:50 67A4A_2017-08-24_1958.zip

Imports will be executed in the following order:

1. The first import execution will only import the 4D268_2017-01-05_1129.zip since it's the oldest one.
2. Then next run will import the 67A4A_2017-06-10_0023.zip and the 57G4K_2017-06-10_0242.zip since they have the same date.
3. The last one will be 67A4A_2017-08-24_1958.zip

So in order to import these four(4) files, you will have to run the import multiple times (in this case three (3) times)

Child directories

Some directories will be automatically created.

corrupt_data_files

history_imported_data

latest_imported_data

Good to know

This is important to understand since the Discovery import type consider the data for the same date as a complete set of infrastructure data. So let's say you have configured "Missing Objects", then you need to make sure all data in your complete infrastructure to be available for the same date, otherwise Assets will trigger on the "Missing Object" configuration.

If you know that you have configured the discovery scanner on different parts of your network, and on different days. Then you need to either turn off the "Missing Object" configuration, or if you still want to have "Missing Object" configured, you will have to separate the different parts of data to different Import configurations, so create one Import configuration for each part of your network. Make sure to have different Discovery folders configured for each Import configuration!