GMU migrateOut Fails with GlmMetricsGlobalConfig Internal Server Error
search cancel

GMU migrateOut Fails with GlmMetricsGlobalConfig Internal Server Error

book

Article ID: 438746

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

When performing a full migration using the Layer7 Gateway Migration Utility (GMU) against an API Gateway (specifically version 11.2.1), the process fails with an Internal Server Error.

Error Message: Execution failed. Reason: Internal Server Error. Detail: Can not find generic entity manager for class: com.l7tech.external.assertions.latencymetrics.config.GlmMetricsGlobalConfig 

Environment

Product: Layer7 API Gateway

Gateway Version: 11.2.1

Utility: Gateway Migration Utility (GMU)

Cause

This issue typically occurs due to a version mismatch between the Gateway Migration Utility and the API Gateway version. Specifically, older versions of the GMU (e.g., using ca-gateway-rest-management-api-1.9.00.jar) may not recognize classes or generic entities introduced or modified in Gateway 11.2.1, such as the GlmMetricsGlobalConfig class associated with Latency Metrics.

Resolution

To resolve this issue, you must update the Gateway Migration Utility to the version specifically bundled with the Gateway 11.2.1 update.

Step 1: Verify the Current GMU Jar Version

Check the lib or jar directory of your GMU installation for the REST management API jar file.

  • Path: gmu/lib/ca-gateway-rest-management-api-*.jar
  • If the version is 1.9.00 or older, it is incompatible with Gateway 11.2.1 features.

Step 2: Download the Compatible GMU Version

The compatible version of GMU for Gateway 11.2.1 is 1.11.0-2233. This is included in the Gateway 11.2.1 update package.

  1. Obtain the Layer7_API_Gateway_v11.2.1.zip package from the Broadcom Support portal.
  2. Locate the file GatewayMigrationUtility-1.11.0-2233.zip within the package. 
  3. Extract the contents of GatewayMigrationUtility-1.11.0-2233.zip to your GMU installation directory.
  4. Verify that ca-gateway-rest-management-api-1.11.0-2233.jar is now present in the jar/lib folder. 

Step 4: Execute migrateOut

Re-run your migrateOut command. The utility should now correctly handle the generic entities and complete successfully.