This documentation supports the 9.1 version of Remedy Action Request System.

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

Metadata mappings and BMC Remedy ITSM

The BMC Remedy Migrator CLI provides support for BMC Remedy ITSM through XML documents that enable mapping to an entry ID as the foreign key, and the ability to inject data during migrations.

Warning

Using BMC Remedy Migrator CLI with BMC Remedy ITSM applications might introduce inconsistencies in the application data. Instead, BMC recommends that you use the Data Management Tool with BMC Remedy ITSM applications to ensure consistency.

XML mapping documents for BMC Remedy ITSM

The following BMC Remedy ITSM mapping documents are available:

  • ItsmMetaData.xml
  • ItsmMetaDataEnableDelete.xml

A configuration file, ItsmConfiguration.xml, is also available, with the Group Data Merge option set to Replace.

The COM:Company form serves as the root in the BMC Remedy ITSM mapping document. The following table outlines the forms handled by the BMC Remedy ITSM mapping document.


Forms and BMC Remedy ITSM mapping

Form

Target form

Mapping type

Local field ID

Foreign field ID

COM:Company

n/a

n/a

n/a

n/a

COM:CompanyAlias

COM:Company

one to one

1000000072

1

FIN:ConfigCost CentersRepository

COM:Company

many to one

1000000001

1000000001

FIN:CostCenterUDA Associations

COM:Company

many to one

490009000

179

CTM:Region

COM:Company

many to one

1000000001

1000000001

SIT:SiteCompanyAssociation

COM:Company

many to one

1000000001

1000000001

SIT:Site

SIT:SiteCompany Association

one to many

1

1000000074

SIT:SiteAlias

SIT:Site

one to one

1000000074

1

SIT:SiteGroup

COM:Company

many to one

1000000001

1000000001

CTM:People

COM:Company

many to one

1000000001

1000000001

CTM:People

SIT:Site

one to one

1000000074

1

CTM:LoginID

CTM:People

many to one

1000000080

1

User

CTM:People

one to many

101

4

CTM:SupportGroup FunctionalRole

CTM:People

many to one

4

1

CTM:SupportGroup Association

CTM:People

many to one

4

4

CTM:PeoplePermissionGroups

CTM:People

many to one

1000000080

1

CTM:LoginID

CTM:People

many to one

1000000080

1

CTM:PeopleWallet

CTM:People

many to one

1000000080

1

CTM:PeopleHRAttendance Mgmt

CTM:People

many to one

1000000080

1

CTM:PeopleHR TimeManagement

CTM:People

many to one

1000000080

1

CTM:PeopleHR TimeManagement

CTM:PeopleHR AttendanceMgmt

many to one

1000002139

1

CTM:PeopleEducation

CTM:People

many to one

1000000080

1

CTM:PeopleTravelProfile

CTM:People

many to one

1000000080

1

CTM:PeopleBenefitInfo

CTM:People

many to one

1000000080

1

CTM:PeopleITSkills

CTM:People

many to one

1000000080

1

CTM:PeopleWorkLog

CTM:People

many to one

1000000080

1

NTE:CFG-Notification Events

CTM:People

many to one

1000000080

1

CTM:PeopleOrganization

COM:Company

many to one

1000000001

1000000001

PCT:ProductCatalog

PCT:Product Company Association

one to many

1

1000000097

PCT:ProductCompany Association

COM:Company

many to one

1000000001

1000000001

PCT:ProductCompany Association

PCT:ProductCatalog

many to one

1000000097

1

CTM:SupportGroup

COM:Company

many to one

1000000001

1000000001

CTM:SupportGroupAlias

CTM:SupportGroup

many to one

1000000079

1

CTM:SupportGroup Assignments

CTM:SupportGroup

many to one

1000000079

1

CTM:SYSAccessPermission Groups

COM:Company

many to one

1000000001

1000000001

PCT:ProductAlias

PCT:ProductCatalog

many to one

1000000097

1

PCT:ProductModel-Version

PCT:ProductCatalog

many to one

1000000097

1

PCT:ProductCatalogAlias MappingForm

PCT:ProductCatalog

one to many

1

1

CFG:GenericProdService Assoc

PCT:ProductCatalog

many to one

1000000097

1

CFG:GenericProdServiceAssoc

PCT:ProductModel Version

many to one

1000000799

1

CFG:GenericCompany ModuleAssoc

COM:Company

many to one

1000000001

1000000001

CFG:ServiceCatalog

CFG:ServiceCatalog Assoc

one to many

1

1000000096

CFG:ServiceCatalogAssoc

COM:Company

many to one

1000000001

1000000001

CFG:ServiceCatalogAssoc

CFG:ServiceCatalog

many to one

1000000096

1

CTM:PeopleTemplateSG

CTM:SupportGroup

many to one

1000000097

1

CTM:PeopleWorkLog

CTM:People

one to many

1000002674

1

CTM:PeopleWorkLog

CTM:People

many to one

1000000080

1

NTE:CFG-NotificationEvents

CTM:SupportGroup

many to one

1000000079

1

Mapping to a foreign entry ID field

When BMC Remedy Migrator migrates or compares data based on the mapping document, it checks the entry ID maps on a per-form basis if the foreign field ID is an entry ID. If BMC Remedy Migrator finds an entry for that entry ID value in the source entry, it obtains the destination value from the map, and replaces the field value in the entry being migrated or compared.

Injecting data

In the mapping document, you can define characters to inject into each entry being migrated or compared for the mapping item. This injection can be added within the <insert-value-fields > element, as shown.

<form name="COM:Company" unique-field-id="179" type="update" disable-related-workflow="false">
<insert-value-fields>
<field-value id="1000000076" value="LOAD"/>
</insert-value-fields>
<name-fields>
<!--Company Name-->
<field id="1000000001"/>
<!--Company ID-->
<field id="260000032"/>
</name-fields>
</form>



Child elements can be added within the <insert-value-fields > element to specify field ID and value pairs to insert into an entry before that entry is modified or compared on the destination.

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

Comments