Field mappings
This topic provides information about field mappings from BMC BladeLogic Automation System to BMC Remedy Change Management.
Job details from BMC BladeLogic Automation System | BMC Atrium Orchestrator interface parameters | Change service interface parameters | Fields in the Infrastructure Change form | Fields in the TMS:Task form |
|---|---|---|---|---|
Product code needed by BMC Atrium Orchestrator to communicate back to the product and get a correct adapter | ProductCode | Not provided in Change Management interface | NA | NA |
Unique Identification for the source that creates Request For Change (RFC) | HostName/Source | SourceID | NA | Source ID under the Job Details tab |
Blade Job ID | JobID | JobID | NA | Job ID under the Job Details tab |
Schedule ID for the job | ScheduleID | JobInstanceID | NA | Job Instance ID under the Job Details tab |
Type of Job | JobType | JobType | NA | Job Type under the Job Details tab |
Job Name | JobName | JobName | NA | Name |
Job description given to Blade (Job Summary) | JobDesc | Summary | Summary | Summary |
Detailed description of job including Job Name, Job Type, Schedule, Priority and so on. | Job Detailed Description | JobDetailedDescription | NA | Notes |
List of CI IDs for which the change is to be implemented | CI_IDs | CIReconIDList | CIs get associated to the change in CHG:Associations form. | CIs gets associated to the task in the TMS:Relationships form. |
Names of CI for which the change is to be implemented | CI_Names | CINameList | CIs get associated to the change in CHG:Associations form. | CIs gets associated to task in the TMS:Relationships form. |
Additional notes about the change to be implemented | Notes | AdditionalNotes | Detailed Description | Notes |
Change urgency | Priority | Urgency | Urgency | NA |
Change impact | Impact | Impact | Impact | NA |
Change type | Request Type | ChangeClass | Class | NA |
Scheduled start date | Schedule_start_date | StartDate | Requested Start Date (If status is completed,gets mapped to actual start date.) | NA |
Scheduled end date | Schedule_end_date | EndDate | Requested End Date (If status is completed, gets mapped to actual end date.) | NA |
Blade user | User name | CustomerLoginID | Customer Login ID | NA |
Job status - (Completed/Cancelled) | Status | Status | Depending on the interface value, value is populated automatically. If job status is completed, task is marked as closed either with success or failure. The change is marked as complete. | if job status is completed, task is marked as closed-success/failed |
Reason/description about the status of the job (Success/Failure) | StatusReason | StatusReason | NA | Status Reason |
ID of the RFC (When the RFC is being updated.) | ChangeId | InfrastructureChangeID | Change ID | Root Request ID |
ID of the task created for job (When the RFC is being updated.) | TaskID | TaskID | NA | Task ID |