GMU Migration Failed - Resource validation failed due to INVALID VALUES property publicIdentifier
Article ID: 112234
Updated On:
Products
CA API Gateway
Issue/Introduction
A GMU Migration (migrateIn) failed with the following error:
Execution failed. Reason: Test migrate in failed: Bad Request Resource validation failed due to 'INVALID_VALUES' property 'publicIdentifier', must be a valid public identifier.
Execution failed. Reason: Test migrate in failed: Bad Request Resource validation failed due to 'INVALID_VALUES' property 'publicIdentifier', must be a valid public identifier.
Environment
Gateway 10.x and Gateway 11
Resolution
The failure is a result of the presence of DTD's in the bundle (from the source Gateway), that don't have a public Identifier.
You can identify the offending DTD's by doing the following:
1. Login to Policy Manager as an administrator
2. Navigate to Tasks > Global Settings > Manage Global Resources
3. Sort by "Type" and look for any resources of type "DTD" that have a blank value under the "Details" column. These are the offending DTD's.
The current solutions are:
1. Add a public Identifier to the offending DTD's in the source Gateway via Policy Manager, then re-run a migrateOut
2. Remove the DTD's in the source Gateway via Policy Manager, then re-run a migrateOut.
You can identify the offending DTD's by doing the following:
1. Login to Policy Manager as an administrator
2. Navigate to Tasks > Global Settings > Manage Global Resources
3. Sort by "Type" and look for any resources of type "DTD" that have a blank value under the "Details" column. These are the offending DTD's.
The current solutions are:
1. Add a public Identifier to the offending DTD's in the source Gateway via Policy Manager, then re-run a migrateOut
2. Remove the DTD's in the source Gateway via Policy Manager, then re-run a migrateOut.
Feedback
Yes
No
Powered by
