Example: Set up integration between PPM 9.2x and ALM 11.52 from scratch

This section provides information for setting up a full integration between PPM version 9.2x and ALM version 11.52 from scratch.

Prerequisites

Make sure the following prerequisites are met:

  • PPM version 9.2x is installed, with ALM content bundle deployed.
  • The Oracle database is already there
  • ALM version 11.52 is installed

Back to top

Tasks

  1. Log on to PPM as administrator.

  2. From the menu bar, select Open > Administration > Open Workbench.

    The PPM Workbench opens.

  3. From the shortcut bar, select Configuration > Workflows.

    The Workflow Workbench opens to the Query tab.

  4. Click List and then, on the Results tab, double-click ALM - Request For Change.

    The Workflow windows opens to the Layout tab.

  5. Go to step 23. Non Release Sub WF, right click and select Edit Source from the context menu.

    The Workflow: Non Release Sub WF window opens to the Layout tab.

  6. Right click step 4. Quality Process Mode, and select Edit from the context menu.

    The Workflow Step window opens to the Properties tab.

  7. Update the value for Request Status to Approved.
  8. Click OK.
  9. Click Save and exit the workflow completely.

  1. Log on to Site Administration of ALM.

  2. On the Site Projects tab, navigate to the desired location, and provide a path for your project in the Physical Directory field, and click Create Project.

  3. In the Create Project dialog, select Create an empty project, and then click Next.

  4. Enter a project name in the Project Name field, select a domain for the project from the In Domain drop-down list, and then click Next.

  5. Select Oracle as Database Type, and then provide credentials for the DB Server in the Server Name, DB Admin User, and DB Admin Password fields, and then click Next.

  6. Specify tablespaces, and then click Next.

  7. Select project administrators, and then click Next.

  8. Select extensions to activate for the project, and then click Next.

  9. Review summary of project information, select Activate project , and then click Create.

  10. Click OK when the confirmation message box pops up.

  11. Run the following SQL script to enable hidden fields in the ALM project for the requirement module for the integration:

    update  <db_name>.SYSTEM_FIELD set sf_is_active = 'Y', SF_IS_VISIBLE_IN_NEW_BUG='111111', sf_is_system = 'N', sf_udf_version=1,  sf_can_change_permissions='Y', sf_is_transition_logic='Y', sf_grant_modify='111001' where sf_table_name = 'REQ' and SF_COLUMN_NAME like 'RQ_REQUEST%';
    commit;

    Note: This script applies to ALM with Oracle as database.

    For instructions on how to enable hidden fields in the ALM project for the defect module for the integration, go to KM1352699.

    Note: The configuration information provided here is based on the out-of-the-box ALM - Request For Change workflow. If your organization has customized any out-of-the-box workflow, make sure you adjust the SQL script accordingly.

  12. In Site Administration, deactivate the project, repair the project, and then activate the project.

  13. Check in ALM groups and permissions if the fields are active.

  14. Go to Project Lists > Requirement Status to check if any status is missing.

  15. Add request statuses that PPM workflow (ALM - Request For Change) contains but ALM requirement does not.

    1. Log on to the integrated ALM project.
    2. From the menu bar, click Tools > Customize > Project Lists > Requirement Status > New Item.

    3. Set Item Name as the following PPM request status name, and add them one by one:

      • Build

      • Pending Approval

      • Approved

      • Test

      • Resource Assessment

      • Pending Rework

      • Run Impact Analysis

      • Impact Assessment

      • Ready for Review

      • 6-Running Sanity Tests in Quality Center

      • Backout

      • Pending Requestor Sign-off

      • Review Results Post Deployment

      • Closed - Successful

      • Closed – Failed

  16. Return to the ALM project schema database. Update the TRAN_RULES table by running the following script.

    update <database schema name of your QC/ALM project>.tran_rules
    set tr_rules='New,1-Requirements Setup Completed' || chr(10) || '1-Requirements Setup Completed,2-Test Plan Setup Completed' || chr(10) || '2-Test Plan Setup Completed,3-Test Lab Setup Completed' || chr(10) || '4-Running Tests in Quality Center,5-Test Execution Completed' || chr(10) || '3-Test Lab Setup Completed,Build' || chr(10) || 'Build,Pending Approval' || chr(10) || 'Pending Approval,Approved' || chr(10) || 'Approved,4-Running Tests in Quality Center' || chr(10) || 'Approved,Test' || chr(10) || '4-Running Tests in Quality Center,Pending Rework' || chr(10) || 'Test,Pending Rework' || chr(10) || '4-Running Tests in Quality Center,Resource Assessment' || chr(10) || 'Test,Resource Assessment' || chr(10) || 'Resource Assessment,Run Impact Analysis' || chr(10) || 'Run Impact Analysis,Impact Assessment' || chr(10) || 'Impact Assessment,Ready for Review' || chr(10) || 'Ready for Review,Run Impact Analysis' || chr(10) || 'Ready for Review,Pending Approval' || chr(10) || 'Approved,6-Running Sanity Tests in Quality Center' || chr(10) || 'Pending Rework,Closed - Failed' || chr(10) || 'Pending Rework,Build' || chr(10) || '6-Running Sanity Tests in Quality Center,Closed - Failed' || chr(10) || 'Pending Rework,Test' || chr(10) || '6-Running Sanity Tests in Quality Center,Test' || chr(10) || 'Test,Pending Requestor Sign-off' || chr(10) || 'Test,Backout' || chr(10) || 'Backout,Pending Requestor Sign-off' || chr(10) || 'Build,Pending Requestor Sign-off' || chr(10) || 'Pending Requestor Sign-off,Review Results Post Deployment' || chr(10) || 'Review Results Post Deployment,Closed - Successful' || chr(10) || 'Review Results Post Deployment,Closed - Failed'
    WHERE tr_field_name = 'RQ_REQUEST_STATUS';
    commit;

    Note: The configuration information provided here is based on the out-of-the-box ALM - Request For Change workflow. If your organization has customized any out-of-the-box workflow, make sure you adjust the SQL script accordingly.

  17. In Site Administration, deactivate the project, repair the project, and then activate the project.

  18. Check again for TRAN_RULES in the permissions of the PPM Request Status.

Note: The configuration information provided here is based on the out-of-the-box ALM - Request For Change workflow. If your organization has customized any out-of-the-box workflow, make sure you adjust the scripts accordingly.

  1. Add scripts to perform the operation on ALM server side.

    1. Log on to ALM as administrator.

    2. From the menu bar, click Tools > Customize > Workflow > Script Edit.

      The Script Editor opens.

    3. From the navigation pane, select Requirement module script, then go to the last script of this category, copy and append the content of add requirement script.txt to the end of the script in the editing pane.

      Note: To obtain the add requirement script.txt, go to KM00630244 and click workflow scripts to download the zip package.

    4. Click Save.

      The new script is added to the Requirement module script.

    5. From the navigation pane, select Defect module script, then go to the last script of this category, copy and append the content of add defect script.txt to the end of the scrip in the editing pane.

      Note: To obtain the add defect script.txt, go to KM00630244 and click workflow scripts to download the zip package.

    6. Click Save.

      The new script is added to the Defect module script.

    7. Exit and log off.

  2. Manually run the SQL scripts provided by support.

    For instructions on how to activate workflow script in ALM project, go to https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result/-/facetsearch/document/KM1352700

  1. Log on to PPM.

  2. From the menu bar, click Open > Administration > Integrations.

    The Integration landing page opens to the Manage Application Change tab.

  3. In the Server Configuration Details section, select ALM – Request for Change (RFC) from the drop-down list and click Add Integration Configuration.

    Note: The Default QC/ALM Folder Name is the folder that will store the requirements created with this integration.

  4. Click Next.

  5. Provide values for the fields as desired or leave as is until the wizard has finished.

  1. Create a request in PPM.

    Note: The QC/ALM Instance and QC/ALM Domain fields are prepopulated. This also applies to the QC/ALM Project field if there IS only one project. If you have associated your Request Type with several projects, this field is not populated. Use a rule or populate the field manually.

  2. Follow the workflow until the request is pushed to ALM.

  3. Follow the request to closure.