Overview of the data load process
You can use the Data Management tool to import data into your BMC Remedy ITSM applications. The section walks you through the activities that you need to perform for loading data.
Configuring Data Management
This section provides information about configuring Data Management prior to using it. For details, see Configuring Data Management
Planning activities
Before you start to populate the data management spreadsheets, run through the planning activities that are outlined in this section. Performing these activities up front, ensures that you thoroughly understand the nature of the data load jobs you will be running and their specific needs.
The planning activities discussed in this section include:
Identifying forms
Data for BMC Remedy ITSM applications is stored on three types of forms, depending on the type of data they contain:
- Foundation forms
- Process setup forms
- Transactional forms
Before you create a data load job, you need to identify which data form types are involved in the data load. Familiarizing yourself with the types of data that you are loading helps you to better understand the nature of the data load and its need. This kind of familiarity with the data load job is important in later steps.
Identifying data creation and update use cases
Ensure that you understand the forms and spreadsheets that your data load job will use to:
- add information to the database, if any.
- update information in the database, if any.
Important
Preparing for bulk data loads
Bulk data loads can present troubleshooting and performance challenges when the data quality cannot be guaranteed or if your system resources are not sufficient to run the data load processes. If you are running bulk data loads, keep the following points in mind when planning the data load jobs, to reduce the impact of any issues associated with data quality or performance.
- If you are unsure of the quality of the data you are loading, BMC recommends that you load the data in smaller, manageable chunks. Loading bulk data in chunks makes it easier to troubleshoot the data load job if it encounters issues with data quality or formatting during the validate step. You cannot move on to the promote step step until all of the data that you are importing is valid.
- Review the Performance benchmarking to ensure your system has the required resources to run the data load jobs efficiently:
Identifying customizations
The data load spreadsheets that BMC ships with the Data Management feature are designed to work with an out-of-the-box BMC Remedy ITSM system. If you have customized the database for the specific needs of your organization by adding fields to the data forms, you must account for these custom fields when planning the data load jobs. If you don't, the data load job will not pick up the data from the customized fields.
Important
Tip
Creating a test plan
Always test your dataload jobs before you run them on live data. Create a test plan that takes into account the following considerations:
- the forms into which you will be loading data
- the volume of data you are loading
- your system performance and resources (memory, processing speed, network bandwidth, database capabilities, and so on)
- the number of threads configured for CAI
- UDM performance on the server.
When you finish drafting the test plan, review it with stakeholders and experts on the various system areas that your plan touches on.
Populating the data spreadsheets
When all of the prerequisites are in place and you have completed your test plan, you can start to work with the data load spreadsheets.
Important
When providing source data using, for example, dataload spreadsheets, LDAP source, ARX files, or XML files, BMC Remedy ITSM requires that you provide the following data at a minimum:
Data | Out-of-the-box spreadsheets | Out-of-the-box job templates |
---|---|---|
Company | Company.xlsx | Company |
Organization | PeopleOrg.xlsx | People Organization |
Location | Location.xlsx | Location |
Support Group | SupportGroup.xlsx | Support Group |
People | People.xlsx | People |
For instructions about how to work with spreadsheets, see Locating and managing the dataload spreadsheets.
Identifying spreadsheets
- Identifying the spreadsheets for your use case Spreadsheets provided and target form mapping
- Using CTM_LoadPeopleModification tab on the People.xls:
- You can create a template with all support group associations and permissions that you would like to give a user or a login id. Specify the newly created template name and login id in the spreadsheet to load those support group associations or user permissions groups. Update the Group list in the BMC Remedy AR System User form with the support group associations and permissions.
- A deadlock in the database happens if same person or login ID is repeated in a spreadsheet and the duplicate records are processed in different threads or processes in the database. To prevent the deadlock in the database, BMC recommends you to have one template with all support group associations, people permissions, and functional roles to apply to all users in one job. If multiple templates need to be added to a single person, divide the job per template rather than dividing a job per user.
Identifying templates
Using the templates that BMC provides with the Data Management utility, you can quickly create data load jobs. You can use the data load templates as provided, or you can create custom templates for each Data Management user that based on the type of data loads the user will be performing.
Example
The following example describes how to create a custom template based on the People template, which is one of the BMC template types.
- From the Application menu on the BMC Remedy ITSM Home page, select Data Management > Job console.
- In the navigation pane of Job console, choose Other Functions > Search template.
- In the Template Name field, type People, then click Search. The system shows the People template details.
- Click Copy Template.
- Provide a name for the new template that you are creating and select a template category from the Category menu.
In the Steps section of the window, remove any steps that you do not need in the template. To do this, highlight the steps that you do not need and from the top of the Steps section, click Delete.
Important
The job dependency and sequencing within the steps that remain are adjusted by the built-in UDM sequencing and dependency logic.
- Click Save.
Ensuring data quality
If the validate step of the data load job encounters missing required or conditionally required fields, unexpected null values, data formatting issues, and so on, it will not run successfully. Before running that data load job, you need to manually review the data in the spreadsheets to ensure that the data that they contain is free from these types of errors.
If you find errors, you must address them in the spreadsheet before you create the data load job. In some cases, you might need to address the data errors in the database and then generate a new set of spreadsheets.
Data quality application preferences
If you are unsure of your data quality, consider setting the Job Wait preference to "Manual Validate - Manual Promote" . This preference causes the the job to wait at the validate step so that you can review the data before the validation runs and gives you the opportunity proactively troubleshoot data issues. BMC recommends setting this user preference especially when loading bulk data in which data quality is uncertain.
Important
You also have the option of setting the Wait flag on individual steps in any given data load job directly on the Job console, by highlighting the job step and clicking Enable Wait. Use this option if you don't want every job step to wait for manual verification, only the ones that you choose.
Creating and running data load jobs
When you have ensured that the pre-requisites are met, completed the planning activities, and populated the spreadsheets, you are ready to work with the data load jobs.
Important
Each data load job has the following steps:
- The load step imports your data from your source files to the dataload staging forms. This step leverages Atrium Integrator jobs, which integrate source and target data stores with data transformation based on specific rules.
- The validate step ensures that the data that was loaded during the load step does not contain fatal errors. Each Validate step represents the validation of data for one staging form. Note that during this step, if errors are found you will need to address the data errors.
- The promote step either automatically or manually pushes all staging form records that are valid to their respective target forms within the BMC Remedy ITSM applications, based on the option selected for each Promote step within the job.
Important
You might need to run these steps iteratively until all of the data passes the Validate step and can be promoted.
Data load job overview
You can use the dataload tool to import data into your BMC Remedy ITSM Suite of applications.
The main procedures of the dataload process are described in the following list:
Create a job using the Data Management Job Console.
For instructions, see Creating a job.- Select a job template that includes a set of steps.
For instructions on using a template supplied by BMC, see Creating a job using out-of-the-box templates. For information about customizing templates, see Creating customized job templates. - Run the job. Choose one of the following methods to run your job:
- Schedule a job by using the Job Scheduler Console to run at a future date and time
For instructions, see Scheduling jobs.
Running a job includes loading, validating, and promoting data. For more information, see Completing steps. - Run the job manually and immediately instead of scheduling the job
For instructions, see Running a job.
- Schedule a job by using the Job Scheduler Console to run at a future date and time
Important
If you have customized BMC Remedy ITSM Suite, see Managing customizations.
Troubleshooting and Best Practices
The following links provide valuable information about troubleshooting the Data Management feature and Data Management Best Practices.
Comments