Service Manager

Home 

Exporting Data From Service Manager to Ivanti HEAT Discovery Release 9.x

About Exporting Data From Service Manager

Setting Up the Data Export

Exporting Multiple Records

About Exporting Data From Service Manager

To export data from Service Manager to Discovery Release 9.x, you must first set up an export connection from the Configuration Console for the quick action that you create to use. After you set up and test the export connection, set up a quick action to export records.

Setting Up the Data Export

Use the following steps to set up your export:

1.From the Configuration Console, click Extend > Data Export Connections to open the Data Export workspace. use the Data Integration Wizard to create and define your own connection.

2.From the Configuration Console, click Build > Automation Tools > Quick Actions to open the Actions Manager workspace.

3.Select Add/Edit action for the configuration item to create a quick action for data exports to Discovery Release 9.x. See Discovery 9.x Export Quick Action for more information. You use this quick action to schedule data exports.

Once created, the quick action (for example: Discovery Data Export) appears in Your Actions tab > Configuration Management.

4.To run the quick action that you configured, highlight a record (such as an item from the CI workspace), then select Action Menu > Configuration Management > Discovery_export_quick_action_name.

The application displays an XML file that contains information about the selected record in the server path location entered in the Configuration Console.

Exporting Multiple Records

To export multiple records (such as configuration item records) you must create a Run for Search Workflow item that connects all the pieces needed to export multiple records. You must select records for export. You can run the workflow at regularly scheduled intervals. The resulting data (one XML file per record) appears in the location defined in the data export connection. You must already have created a Data Export connection and a Quick Action for Data Exports before creating the Saved Search.

Use the following steps as a guide to creating a workflow item to export multiple records:

1.Configure an export connection. See also From the Configuration Console, click Extend > Data Export Connections to open the Data Export workspace. use the Data Integration Wizard to create and define your own connection.

2.Create a quick action. See also From the Configuration Console, click Build > Automation Tools > Quick Actions to open the Actions Manager workspace.

3.Create a saved search that identifies the type of records to export and limits them to the ones that were changed during a specific time frame, such as the previous day or the previous week.

See Creating a Saved Search for information about creating a new saved search. For information on finding and editing a default saved search to use as a baseline, see Default Saved Searches. For example, to find and export records about Computers you can edit the Computer CIs default saved search.

4.Create a schedule to use in the workflow. For information on how to edit an existing schedule or on how to create a new schedule, see About the Schedule Entry and Scheduled Jobs Workspaces.

For a list of default schedules, see Default Schedules.

5. Create a Run for Search workflow to specify a search that triggers a quick action. To create a workflow that is linked to a schedule, see Creating a Workflow, Creating a Scheduled Workflow,

6.Trigger the workflow by using the Configuring a Trigger procedure. At the Trigger Definition tab ensure that you select the schedule that you created.

7.Publish the workflow. See Publishing, Editing, and Locking Workflow Versions.

If your data exceeds 10,000 records you may need to create multiple saved searches using different filters (such as region, location, and so on), and schedule these searches to run separately.

You can modify the Run for Search field to use criteria such as "LastScanDate" Greater than "CurrentDate" - <ScheduleInterval>, where ScheduleInterval is the data export schedule interval, such as 1 for daily export, 7 for weekly export, 30 for monthly, and so on.


Was this article useful?