API Gateway GMU - issue detecting services with same URL

book

Article ID: 192868

calendar_today

Updated On:

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction

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 ..

1. After migrating services to the target Gateway, GMU doesn't prompt you for any conflicts if the any services containing Multiple resolution paths with same name.
2. Use migrateIn with the --deactivate argument doesn't seem to work with true or false
3. Is there a way to disable all the services within the folder using --deactivate switch.

Environment

Release : 9.4

Component : API GATEWAY

Resolution

A solution for the usecase can be derived with the manageMappings command, and the associated settings:

I referred the below documentation.
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-gateway/9-4/gateway-migration/gmu-command-help/managemappings-command.html

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.