This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Data Management

BMC strongly recommends that you read and understand all of the topics under the Data Management section before you start to use the Data Management utility.

This page contains the following information:

Introducing Data Management concepts 

The following video provides an introduction to Data Management concepts.

Introduction to the Data Management component

The Data Management component is a web-enabled tool to use when loading data from earlier versions of BMC Remedy, or from legacy systems, into the current release of BMC Remedy ITSM Suite.

You can also use the Data Management component to update the following levels of data:

  • foundation
  • process setup
  • transactional

For more information about these levels of data, see Levels of BMC Remedy ITSM Suite data.

The dataload tool provides a job-based framework that supports job-based data loads. You can use the tool to import data for:

  • Foundation (which contains the common forms and data that are needed to support the BMC Remedy ITSM Suite of applications)
  • BMC Change Management (and Release Management)
  • BMC Asset Management (and Software License Management)
  • BMC Service Desk
  • BMC Knowledge Management

Note

 BMC Service Level Management does not support SVT or SLA import through Data Management (DM). It only supports transaction data through DM.

You can also use the dataload tool to import data for BMC Service Request Management. Be aware, however, that the tool uses a different method to import data into the BMC Service Request Management application than it does for BMC Remedy ITSM. For more information about importing data into BMC Remedy Service Management, see Importing SRDs, PDTs, and supporting data in the BMC Service Request Management documentation space.

The job-based framework provides support for:

Automated job scheduling

Multiple users performing multiple simultaneous dataloads

Multi-tenancy, which means users can create dataload jobs and templates that can be restricted to specific companies

Centralized error handling

Case insensitivity correction and alias replacement during validation

Loading data from various sources; for example:

  • Lightweight Directory Access Protocol (LDAP) source files
  • AR Export (ARX) files
  • Extensible Markup Language (XML) files
  • databases using Java Database Connectivity (JDBC)
  • Microsoft Excel spreadsheets

Note

Microsoft Excel spreadsheets formatted with the .xlsx extension have the following limitations:

Worksheet size: 1,048,576 rows by 16,384 columns

Number of characters in a cell: 32,767
If your data load operations could exceed these limitations, consider customizing the data loads using Atrium Integrator transformations as described in Managing customizations.

Data load customization options include:

(Recommended) Modifying or creating new Atrium Integrator transformations or jobs that load directly from the data source to the associated load forms. This is accomplished using one of the many out of the box input adapters in Atrium Integrator,for example JDBC. With this option, you can use the spreadsheets as a source of information on the target forms.

Adding extra cells that you can concatenate if the cell length is exceeded.

If the row length could exceed the spreadsheet limitation, another option (which does not require customization) is to split the load into multiple spreadsheets. This method, however, requires you to perform multiple loads.

Data Management provides out-of-the-box job templates, spreadsheets, and staging form mappings for your use.

Note

Starting with BMC Remedy ITSM 8.0, Data Management does not provide sample data spreadsheets.

Data Management also provides a data wizard for modifying foundation data throughout all applicable BMC Remedy ITSM Suite forms. The Data Wizard also modifies configuration item (CI) records in BMC Atrium CMDB. For more information about the data wizard, see Using the data wizard to modify data.

Note

Do not run the Data Management tool and the data wizard at the same time. This can cause data integrity issues.


Data Management usability enhancements

Starting with BMC Remedy ITSM 8.0, Data Management adopted the following usability enhancements:

To improve the user experience, BMC provides a web-enabled dataload tool that replaces the Data Management tool which had to be installed. File handling is now centralized using a network share that you must configure.

To improve application performance, system administrators can configure system messages from filters and servers to appear in a message bar instead of in pop-up windows.

To improve overall system performance, consoles and forms now open inside a single view area, instead of in individual windows.

To make navigation through the BMC Remedy ITSM Suite of applications easier, a more consistent navigation model is used on the IT Home Page, consoles, and forms. For example, the application menu that appeared on the IT Home page in earlier releases of the BMC Remedy ITSM Suite of applications is now used on all of the application consoles and main forms.

To make required fields more obvious, when you save a record a red box outlines mandatory fields that do not contain valid information.

The following video describes the data management enhancements in this release of BMC Remedy IT Service Management.

How to use the Data Management console

The following recorded webinar provides an introduction to the Data Management console and other Data Management concepts.

You can also connect with other users for related discussions on the BMC Community.

Job-based framework terminology

The following terms are used when describing the job-based framework:

Data Management job

A Data Management job (also referred to as job in this documentation) is an executable unit of work that is composed of a number of steps and their relationships and is used to run the dataload processes. A job is specific to one user and one company. Data Management jobs call Atrium Integrator jobs.

Step

A step defines a unique process within each Data Management job, for example: a validate step, or a promote step.

Transformation

A transformation defines a data flow sequence. The transformation integrates source and target data stores by:

Reading data from the source data store.

Transforming it according to the rules that you specify.

Storing it in the target data store.

Atrium Integrator job

An Atrium Integrator job is the core construct required by the job-based framework. It is composed of one or more transformations.

Where to go next

A good topic to read next is Overview of the data load process.

Other topics provided in the Data Management documentation include:

Related topics

In addition to the information provided in the Data Management online documentation, there is a BMC Communities blog posting about managing your data load with BMC IT Service Management applications.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Bruno Muniz

    Is there a place here where I can download the spreadsheets or do I need to have access to an instance of the application in order to get them?

    Oct 03, 2014 03:45
    1. Bruce Cane

      Hi Bruno, 

      You need to access an instance of the application to receive the spreadsheets. The spreadsheets are specific to the version of the application that you are running, so to ensure that our customers are using only the spreadsheet appropriate for their version, we ask you to access it from the application.

      Oct 07, 2014 08:23
  2. David k Hill

    The UDM Video associated with this document page is very nice.

    One word of caution when defining the Job Name in the Job Creation process.  Be sure to specify a fairly short name and DO NOT USE SPACES.  There  is no validation for length of name used and no validation for spaces.  The job name appears to be used behind the scenes to build the job steps and can error out when a template is selected AND when the job name is too long.  I have several instances where the job name I used match the name of the name of the foundation data load spreadsheet file for tracking.

     

     

    Apr 20, 2016 03:15
    1. Sirisha Dabiru

      Thanks David k Hill for sharing this info. Will get back to you on this soon.

      Murali Viswanathan

       

      Apr 21, 2016 12:15
      1. Sirisha Dabiru

        Hi David k Hill,

        I have updated step 3a of Creating a job to incorporate your suggestion.

         

        Regards,

        Sirisha

        May 17, 2016 06:05
  3. David k Hill

    Thank You.  Looks good!

    May 19, 2016 10:41