Layer7 API Management

Hi Team,

Recently we have updated our Active Directory configurations in development environment. 

Using GMU, we tried to migrate development environment service into UAT and service has authentication against updated Active Directory. Then facing migration issue ""(name)" must be unique exception.

Do let me know how to overcome this issue to migrate service.

Below are the migrateOut ,manageMappings and template commands in development.

#
echo "Exporting Service Policy $SHORTN to $TARGET_FILE.xml"
/opt/SecureSpan/gmu/GatewayMigrationUtility.sh migrateOut --argFile /opt/SecureSpan/gmu/commonargs.props --serviceName "/$INTEXT/$SHORTN" --dest $TARGET_FILE.xml --defa
ultAction NewOrUpdate
#
echo "Managing Mappings for Service Policy $TARGET_FILE.xml"
/opt/SecureSpan/gmu/GatewayMigrationUtility.sh manageMappings --argFile /opt/SecureSpan/gmu/commonargs.props --bundle $TARGET_FILE.xml --type ID_PROVIDER_CONFIG -N --t
ype service --action NewOrUpdate
#
echo "Templating Service Policy $TARGET_FILE.xml to $TARGET_FILE.properties"
/opt/SecureSpan/gmu/GatewayMigrationUtility.sh template --argFile /opt/SecureSpan/gmu/commonargs.props --bundle $TARGET_FILE.xml --template $TARGET_FILE.properties
#

Below is the migrateIn command in UAT environment.

echo "Importing Service Policy from $TARGET_FILE Writing output to results.xml"
/opt/SecureSpan/gmu/GatewayMigrationUtility.sh migrateIn --argFile /opt/SecureSpan/gmu/commonargs.props --bundle $TARGET_FILE.xml --template $TARGET_FILE.properties --r
esults results.xml --destFolder /$INTEXT $2 $3

Regards,

Radha

Dear saisuneel ,

Can you show the gmu.log under GMU install folder?

Just want to double confirm what entity caused the name duplication problem.

Regards,

Mark

Just double check exported xml bundle. The GMU sometimes exports some objects twice (it is not so funny, but ...). Just try to find duplicity in the bundle and delete one occurrence. 

Michal

Radha,

The error that you are seeing """(name)" must be unique exception." occurs when an entity is created manually in the destination environment with the same name so the underlying GOID does not match. As it already exists you will need to map it so the source ID and the destination ID are linked.

Sincerely,

Stephen Hughes

Broadcom Support