Introduction to the Integration

Integrating OpenText PPM requests with QC/ALM defects or requirements enables you to create requirements and defects in QC/ALM while using OpenText PPM. This allows users of both applications to participate in the processing of defects, change requests, and release requests.

In OpenText PPM, a request type is a template, and when you create a request, you must select a request type. With the OpenText PPM–QC/ALM integration, creating the request in OpenText PPM automatically creates a defect or requirement in the integrated QC/ALM project. For example, depending on the integration configuration, creating a OpenText PPM request of the type PPM_Defect could create a defect in QC/ALM project A or project B, and creating a OpenText PPM request of the type PPM_Requirement could create a requirement in QC/ALM project A or project B.

In addition, for integration with ALM, when an ALM defect is created, an associated OpenText PPM request can be created automatically.

PPM supports integrating with QC 10.00 and OpenText Application Quality Management, however, the integrations have the following differences.

Difference	Details
Mapping relationship	Using QC 10.00, multiple OpenText PPM request types can be integrated with the same QC entity (either a defect or a requirement) in a project. Using OpenText Application Quality Management version 11.x or 12.x, each integration must include a one-to-one, unique mapping between a OpenText PPM request type and an OpenText Application Quality Management entity (defect or requirement). In any case, different OpenText PPM request types can be integrated with different entities of the same project or different projects in QC/OpenText Application Quality Management. If the request types are integrated with entities of different projects, the projects can be on the same or different QC/OpenText Application Quality Management servers, and each QC/OpenText Application Quality Management server can be at version 10.00, 11.x, or 12.x.
Integration deployment	For integration with QC 10.00, PPM provides the PPM-QC Integration Tool, which you can install on any computer. You use a software wizard to help create the required mapping files, which you then deploy to OpenText PPM and to QC. For integration with OpenText Application Quality Management, you use a menu option in PPM to create the mapping files in a central PPM location. Note: Do not attempt to use the PPM-QC Integration Tool to configure integration with OpenText Application Quality Management.

Difference

Details

Mapping relationship

Using QC 10.00, multiple OpenText PPM request types can be integrated with the same QC entity (either a defect or a requirement) in a project.
Using OpenText Application Quality Management version 11.x or 12.x, each integration must include a one-to-one, unique mapping between a OpenText PPM request type and an OpenText Application Quality Management entity (defect or requirement).

In any case, different OpenText PPM request types can be integrated with different entities of the same project or different projects in QC/OpenText Application Quality Management. If the request types are integrated with entities of different projects, the projects can be on the same or different QC/OpenText Application Quality Management servers, and each QC/OpenText Application Quality Management server can be at version 10.00, 11.x, or 12.x.

Integration deployment

For integration with QC 10.00, PPM provides the PPM-QC Integration Tool, which you can install on any computer. You use a software wizard to help create the required mapping files, which you then deploy to OpenText PPM and to QC.
For integration with OpenText Application Quality Management, you use a menu option in PPM to create the mapping files in a central PPM location.

Note: Do not attempt to use the PPM-QC Integration Tool to configure integration with OpenText Application Quality Management.