We’ve recently encountered the following issues using GMU:
We’ve imported a web api with the same URL of an existing service by mistake, and as a result the Gateway never received that service API call from clients from then on because of this inconsistent state (no messages detected in ssg logs).
The following information is required ..
Release : 9.4
Component : API GATEWAY
A solution for the usecase can be derived with the manageMappings command, and the associated settings:
I referred the below documentation.
Below are the sequence of commands I used, and this set of commands doesn't allow a duplicate resolution path while migration.
GatewayMigrationUtility.bat migrateOut --all --plaintextPassword 7layer -z SOURCE.properties -d SourceServices.xml
GatewayMigrationUtility.bat manageMappings -b SourceServices.xml -t service --targetRoutingUri --outputFile SourceServicesOverride.xml --action NewOrExisting
GatewayMigrationUtility.bat migrateIn --plaintextPassword 7layer -z DEST.properties -b SourceServices.xml -map SourceServicesOverride.xml -r MigrateInResults.xml
Furthermore, --deactivate switch is intended to retain the active version of the policy, and doesn't apply to the policy itself.
for example, if source contains 4 versions of a policy - A,B,C,D, and B being the active version, and
target contains 5 versions - A,B,C,D,E and A being the active version, using --deactivate switch will not disturb the active version.