1. Test the upgrade in a staging environment
2. Use latest iFixes for your source and target versions
3. Review product-specific critical notes below
4. Document baseline timings and system state

Why Testing is Critical:

• Detects data issues before production impact
• Provides accurate upgrade timing estimates
• Validates compatibility with your environment

Testing Environment Requirements:

• Hardware comparable to production (CPU, RAM, disk I/O)
• Copy of production data (ideal) or comparable dataset
• Network configuration similar to production

What to Document:

• Pre-upgrade task duration: _ hours.
• Upgrade execution time: _ hours.
• Post-upgrade task duration: _ hours.
• Any errors or warnings encountered.

Reference: Setting up a test staging environment with production data

IBM recommends upgrading using the latest iFixes for both source and target releases.

If using older iFixes: Review the known issues list to identify potential upgrade impacts.

iFix Documentation:

• Interim fixes for ELM 7.1
• Interim fixes for ELM 7.2

The lists show known issues organized by Product and Component/area.

Review the critical notes for products in your environment before proceeding.

Key Issues and Considerations:

Review the comprehensive guide before upgrading: Key considerations and known issues when upgrading to ELM 7.2.0 (LQE relational store)

Starting with ELM 7.2.0, LQE Jena-based storage is no longer supported. This release supports only the LQE relational store (LQE rs). If you are using LQE Jena in earlier versions, you must migrate your reports and usage to LQE rs before upgrading to ELM 7.2.0.

Important: Before upgrading to ELM 7.2.0, you must first upgrade to ELM 7.1.0 SR1 (or any later 7.1.0 iFix) to complete the migration and validation of your reports.

This document covers:

• Known limitations.
• Performance considerations.
• Migration constraints identified.

Why iFix008 is Important:

Contains critical TRS performance fixes that improve:

• TRS Feed Validation speed
• LQE indexing performance
• LDX indexing efficiency

Reference: Interim Fix 8 details for ELM 7.1

Problem Description

OSLC Migration Task shows poor performance, running for extended periods (days) with no indication of completion.

Background: What is OSLC Migration?

OSLC migration is a background process that runs after an upgraded ETM server starts:

Key Characteristics:

• Manages OSLC Migrators for specific artifact types
• Publishes delete and create events in TRS2 feed
• Runs asynchronously (does not block server operations)
• Users can continue normal activities during migration

Typical Duration: Varies based on data volume and system resources

Impact on Your System

Example Impact:

ETM 7.0.3/7.1 introduced an advanced property to include archived approval groups in REST/OSLC APIs, PDF, and JRS Reports:

Figure 1: ETM Advanced Property (Administration > Advanced Property)

Reference: ETM 7.0.3 New & Noteworthy

Post-upgrade, an OSLC Migrator updates archived approval details in the artifact schema. If the property is enabled before migration completes, archived approvals appear only for migrated artifacts.

Summary: Existing reports work as before upgrade while migration is in progress.

Monitoring Migration Progress

Status Page Location: https://elm.host.name/<qm-context>/oslcMigrationStatus

Figure 2: OSLC Migration Status Page showing progress

What to Monitor:

• Overall completion percentage
• Individual migrator status
• Estimated time remaining
• Any error messages

Resolution Steps

Please provide feedback to help us improve this documentation:

• Contact the authors with suggestions
• Report issues or corrections
• Share your upgrade experiences