Configuring Data Management
Action | Reference |
|---|---|
To define users and administrators for Data Management | |
To configure the load file path for the BMC Remedy AR System attachments and spreadsheets repository | |
To configure Data Management application preferences | |
To load a parent group through Unified Data Management and Onboarding Wizard | |
To define aliases for data types |
Staging forms dependencies
Application administrators are responsible for creating a sequence for all staging forms in the staging form dependency table (in the DMT:SYS:StagingFormDependency form). The sequence is the order of steps.
When you add new records to the staging form dependency table, the sequencing engine determines how new staging forms fit into the existing sequence.
When you create a job, the existing sequence records are compared with the records in DMT:SYS:StagingFormDependency form and SHR:SchemaNames form to determine whether the existing sequence records are the latest records. If newer records exist in either of these two forms, a new sequence is generated before the job is created.
For information about what happens when a job runs, see Running-and-monitoring-data-load-jobs.
Recommendations for configuring data management
Recommendations to be followed while configuring Unified Data Management in the following scenarios:
Scenario | Forms to be updated |
|---|---|
Server group environment: A server group environment consists of two or more servers that share the same database and are designated as part of a server group. Server groups are designed to provide failover operations for crucial operations. | |
Non-server group environment: In a non-server group environment, a single server exists. | Important: As the non-server environment contains a single AR server, you need not rank the AR server. Jobs run on this server by default. |
Database restore: You must verify and update the server name references in the UDM forms if you want to perform testing before making the server as new production server. |