Integration with Other Applications > Integrated Software Management > Software Defect Tracking Integrations > Adapters Management for Site and Organization Administrators > Adapters Administration Utility > Working with Integrity Defects, Bugzilla, and Atlassian JIRA Adapters > Managing Context Associations and Mapping Files > Validating a Mapping File for an Adapter
  
Validating a Mapping File for an Adapter
A Site or Organization Administrator must select a Mapping File for each adapter installed in the Adapters Administration utility so that contexts can be associated to an adapter. The Associating a Context and Selecting a Mapping File for an Adapter procedure wizard includes the mapping file selection. A mapping file must be selected. If a mapping file is not selected, the administrator is unable to complete associating a context to an adapter procedure.
This procedure explains how to validate a mapping file for Integrity Defects, Bugzilla and Atlassian JIRA adapters.
1. From Site > Utilities or Organizations > Utilities select Adapters Administration in the System Administration section of the page to open the Adapters Administration window.
2. From the Adapter Definition table in the Adapters Administration window, click the Map Attributes icon to open the Adapter Associations window.
3. From Step 2, Map Attributes, in the Associate Objects window, select from the pull-down list of mapping files, the mapping file to associate with this adapter context.
4. Click Validate to determine if the selected mapping file is valid.
a. If the mapping file is valid, a message stating that the mapping file is valid displays. Click OK to exit the message. Click Finish to save and load the mapping file for the adapter. The system returns you to the Adapters Administration window.
b. If the mapping file is invalid, the system displays the invalid criteria for the mapping file. After you have noted the invalid mapping message, click OK.
* 
If the mapping file is invalid during the context association of an adapter, you cannot save the context association or its invalid mapping file for the adapter. You must abort the procedure.
▪ If the invalid mapping file is the wrong mapping file, select the appropriate mapping file from the pull-down list and click Validate.
▪ If the invalid mapping file is the intended mapping file, click Cancel to abort the procedure.
▪ If you created a new mapping file, or updated an existing mapping file and it is invalid during this procedure, correct the attributes of the mapping file. Refer to Creating or Editing a Mapping File.