Integration with ALM

• ALM supports multiple instances of the Content Pack.

• DCS Integration: An extractor using the Data Collection Service mechanism that extracts entities from the source and generates corresponding flat files. For details, see Data Collection Service (DCS) .

• All fields are case-sensitive.

• Port 8080 / 8443 must be available.

• To control the data extraction page size from the Data Warehouse server side, set the alm.page.size parameter to 1000 in $HPBA_HOME/ContentPacks/ALM/EXTRACTOR/extractor-alm/setting.properties.
• The ALM Adapter transfers the relevant information from the ALM data source. In the ALM Site Administration, select the Site Configuration tab and make sure that the REST_API_MAX_PAGE_SIZE configuration is at least 2000 pages. In the ALM activation page in ALM, the alm.page.size setting should be equal to or less than the REST_API_MAX_PAGE_SIZE setting.

1. Prerequisites:

   • Port 8080 / 8443 must be available.

2. Select ADMIN > Data Management > Install Content Pack then click the install button relevant for the data source.

3. Select ADMIN > Data Management > Connect Data Source then click Add data source.

4. The Add Data Source page opens. Select the ALM data source type.

5. Select or enter the configuration parameters.

6. Click Next to proceed to the validation page.

1. Export the ALM SSL certificate to a file. For details, see the ALM Hardening Guide.

2. After the installation procedure is finished, reveal the ALM certificate to Data Warehouse, you import the SSL certificate trusted by the ALM server into the JDK key store using the keytool.exe tool provided by the JDK by running the command :

   On the server side (glassfish): Run the $HPBA_Home/jdk/jre/bin/keytool" -importcert - alias <alias> -file <path_to_certificate>" –keystore"<JRE>/lib/security/cacerts" - trustcacerts -storepass changeit command.

3. Select the Is secured toggle-button in the activation parameters screen.

4. Change the port to a secured port (default is 8443).

ALM Demand Management provides system parameter fields. You can change name and data length of these parameter fields in ALM Demand Management, depending on your purpose and requirements.

To support all customers’ KPIs, all ALM customized fields of Demand Management are populated to the Data Warehouse and added as place holders in the universe. You can use these fields in BA KPI formulas.

Related Dimension Tables and Views

Related Dimension Tables

• REQUIREMENT_PLHD_DIM
• PROJECT_PLHD_DIM
• DEFECT_PLHD_DIM
• TEST_PLHD_DIM
• TESTINSTANCE_PLHD_DIM
• TESTRUN_PLHD_DIM
• TESTSET_PLHD_DIM

Related Views

• REQUIREMENT_PLHD_DIM_V
• PROJECT_PLHD_DIM_V
• DEFECT_PLHD_DIM_V
• TEST_PLHD_DIM_V
• TESTINSTANCE_PLHD_DIM_V
• TESTRUN_PLHD_DIM_V
• TESTSET_PLHD_DIM_V

If you are integrating ALM and PPM data sources, the consolidation process between ALM and PPM identifies ALM releases as child- projects of PPM projects.You can map which release of the ALM domain is connected to the specific PPM project. The manual mapping must be performed before running ETL.

To configure ALM and PPM consolidation:

1. Navigate to $HPBA_HOME/ContentPacks/ALM/EXTERNAL/.

2. Open the ALM_RELEASE_MAPPING.csv file.

   

3. Note Do not remove the header row. In addition, if the spreadsheet has a dummy row under the header row, do not edit or delete the dummy record. This record tells the ETL process what data type to use when processing the column.

4. Save your additions and changes.

You can configure a defect's reopen event by mapping which defect status changes can trigger a reopen event. When you configure the file, all of these status changes are marked as reopen events. This allows for a dynamic configuration of reopen events mapping.

To configure reopen event mapping:

1. Navigate to $HPBA_HOME/ContentPacks/ALM/EXTERNAL.

2. Open the ALM_DEFECT_REOPEN_MAPPING.csv file.

3. Enter the required defect status, for example, old_value = Fixed, new_value= Open. All records that match this pattern will be marked as reopen event.

4. Save your additions and changes.

The data warehouse is connected to ALM through high-level integration processes. A set of database views enables the extraction of the main ALM objects.

Mandatory fields are marked with a red asterisk.

User interface elements are described below:

For a list of the ALM-related KPIs and Metrics, see KPIs and Metrics.

The place holder entities: DEFECT_PLHD, REQUIREMENT_PLHD, PROJECT_PLHD columns are listed below with their corresponding context columns: