Layer7 API Management

Expand all | Collapse all

CA GMU

  • 1.  CA GMU

    Posted 04-17-2019 04:24 PM

    Hi,

     

    We use GMU to migrate API Gateway service from lower environment to higher. Observed that source environment cluster wide properties and secure password are migrating as is into higher environment if service already exists in target environment.

     

    We don't want to migrate properties from source environment to target environment if properties exists in target.

     

    Kindly do help on GMU export and import scripts, providing scripts are as below.

     

    Export:

     

    ####################
    TARGET_FILE=$TARGET_ENV/$INTEXT/Service/$SHORTN
    #
    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 NewOrExisting
    #
    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

     

     

    Import:

     

    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



  • 2.  Re: CA GMU

    Posted 04-19-2019 05:48 AM

    If you don’t want to migrate cluster properties, you have to mark cluster properties as “ignore” with the manage mappings command. 



  • 3.  Re: CA GMU

    Posted 04-22-2019 04:14 AM

    Hi rmkennell,

     

    We would like to migrate cluster wide properties which are not exists in higher environment and ignore those are already exists. So could you please help us how to change export command.

    Export Command,

     

    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 NewOrExisting

     

     

    Regards,

    Radha



  • 4.  Re: CA GMU

    Posted 04-23-2019 08:56 AM

    You might take a look at https://docops.ca.com/ca-api-gateway/9-4/en/gateway-migration/get-started-and-run-gmu#GetStartedandRunGMU-GMUEntityTypes

     

    This also refers to the type CLUSTER_PROPERTY to use in your ManageMapping command for the cluster wide properties. Using NewOrExisting action will only create them and not update existing properties.