Adding or Modifying an Integration Configuration
Adding an Integration Configuration
Add an integration configuration to integrate a PPM request type with an ALM entity type:
- Log on to PPM.
From the menu bar, select Open > Administration > Integration. The Manage Application Change page opens.
- In the Server Configuration Details section, select a request type from the drop-down list of available request types and click Add Integration Configuration.
Field Name (*Required)
(Read only) Status of the integration of this request type.
After you finish configuring the integration, you enable or disable the integration by clicking the Status icon in the Integration Configurations list.
Select an ALM version from the drop-down list.
Valid values include:
ALM 11.20(The complete version number is ALM 11.00 SP2)
ALM 12.00(applicable for all versions above 12.00)
Caution: There is a known issue in the ALM 12.00 side: PPM related fields are not returned in the REST response when querying for the requirement entities. This issue blocks the requirement synchronization. Make sure your ALM version includes the fix of this issue before you use ALM 12.00 or later.
*QC/ALM Server URL
URL of the ALM server, in either of the following format:
Username used to access ALM.
If ALM runs in SSO mode, provide the API key instead of username.
Password for the QC/ALM Username.
If ALM runs in SSO mode, provide the API key secret instead of secret.
*QC/ALM Server Time Zone
Time zone of the ALM server. Required to ensure that the integration correctly manages updates between fields mapped as bidirectional between PPM requests and associated ALM defects or requirements. Default is the time zone of the PPM Server.
Note: For some of the GMT time zones, only the "Daylight Savings Time Not Used" option is available, time zones names that include city names are not available due to the changes with a third-party product.
For example, you may see the "GMT +9:00 Daylight Savings Time Not Used" option only, the "GMT +9:00 (Asia/Yakutsk) Yakutsk Time" option is not available.
Domain on the ALM server to use for the integration. To retrieve the set of domains, click Get Domains.
ALM project to use for the integration. (List is populated when QC/ALM Domain is selected.)
ALM entity type to be used for integration—Defect or Requirement. Available option(s) depend on whether the QC/ALM Defect Information field group (for defects) or the QC/ALM Info field group (for requirements) or both field groups are configured in the request header type for the request type. If only one of the field groups is configured in the request header type, this field is read only.
Options that change based on whether the request type is integrated with a defect or a requirement. See Configuring Integration Options.
Click next to go to Step 2: Map PPM-QC/ALM Fields.
The Field Mapping section provides default mappings for you. For details, see Default Field Mappings for PPM and ALM.
If you want to modify it, For details, see Configuring Field Mappings.
- Click Next to go to Step 3: Complete Configuration.
Options for email notification when integration errors occur, and when integration creates or updates entities.
You can optionally send emails to addresses you specify when integration errors occur, either as they occur or as a daily consolidation.
Separately, you can optionally send emails to addresses you specify when the integration creates or updates entities, either as these changes occur or as a daily consolidation.
Event logs provide the same information as email notifications. See Viewing Event Logs.
Click Save to save the configuration.
Clicking Save & Enable saves the configuration and enables the integration for the request type.
Modifying an Existing Integration Configuration
Log on to PPM.
From the menu bar, select Open > Administration > Integration.
The status for each request type on the Integration Configurations screen is one of the following:
Enabled . The integration of the request type and ALM entity (defect or requirement) is enabled and operable.
Disabled . The integration of the request type and ALM entity is disabled and not operable.
Tip: You can easily toggle the status of an integration by clicking the status icon. That is, clicking disables the integration, and clicking enables the integration.
Read-Only . The integration of the request type and QC entity is operable but not configurable. You can upgrade the integration configuration to ALM version 11.00 or later. For more information, see Upgrading from Integration with QC 10.00 to Integration with ALM.
The QC/ALM data displayed for each request type also includes the URL of the QC/ALM server and the QC/ALM version, domain, project, and entity type (defect or requirement).
- Click the request type for which you want to modify the integration configuration.
- Modify the information in Step 1: Configure Server Details. See step 4 for details.
Modify the information in Step 2: Map PPM-QC/ALM Fields.
QC/ALM Synchronization Control Field
Specifying a value in this field allows the QC/ALM end users to control whether they want to create a defect in PPM Center as a result of creating a defect in ALM.
The values in the drop-down list are fields (with
Y/Nvalues) retrieved from the Defect entity type of the ALM project specified in the Project field.
The field is read-only if you selected the Creating a PPM Center request automatically creates an associated QC/ALM entity integration option on the Step 1: Configure Server Details tab page.
Limitation: If the field you specified in this option is set as a required field in ALM, errors appear no matter whether or not you build field mapping for the field. Therefore, do not set the field you selected in this option as required in ALM.
Separate lists of unmapped QC/ALM Entity Fields and PPM Request Fields, followed by a table of the pre-configured Current Field Mappings. See Configuring Field Mappings.
- Modify the information in Step 3: Complete Configuration. See step 7 for details.
Click Save to save your changes.
Clicking Save & Disable saves the configuration and disable the configuration for the request type..