IBM Support

LI81742: MIGRATION: CATALOG TITLE FOR CATALOG PROPERTIES NEEDS TO BE SLUGIFIED ON PORT-TO-APIGW

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In API Connect version 5, APIs can use Catalog Titles for
    Catalog Properties, however, API Gateway expects Catalog Names
    for Catalog Properties in APIs. The APMU command 'apicm
    archive:port-to-apigw' is not sluggifying them resulting in
    error afterward in the DataPower API Gateway
    - Reproduction steps
    1-In API Connect version 5, create an API that with some
    properties for your specific catalogs (that contain a space in
    their name such as 'ext prod' or 'int prod')
    For example:
    ext prod:
      properties:
      backend-api-key: <key>
      product-endpoint-url: <http://<backend-endpoint-ext>/v3
    int prod:
      properties:
      backend-api-key: <key>
      product-endpoint-url: <http://<backend-endpoint-int>/v3
    2- Migrate your API to APIGW using the AMU tool ( 'apicm
    archive:port-to-apigw' command)
    3- When APIs are published to the catalogs you get messages
    such as:
    ---
    200921T091044.861Z [0x81000228][cli][error] : tid(75791)
    gtid(5407bcec37b24bc5b3a365556c19318d): *** Wrong number of
    arguments 4, expected between 1 and 3.
    20200921T091044.861Z [][cli][error] : tid(75791)
    gtid(5407bcec37b24bc5b3a365556c19318d):
    (20.test_int-prod_collection.cfg:394211): property
    backend-api-key ext prod <value>
    ---
    

Local fix

Problem summary

  • In v5, catalog properties were defined as the Catalog Title,
    which can contain spaces. In v2018/v10 APIGW, catalog properties
    are defined as Catalog Name, which cannot contain spaces or
    capital letters. As a result, users would experience error on
    migration that an API with the Catalog Title couldn't publish.
    AMU fix goes in and replaces Catalog Title with associated
    Catalog Name or sluggifies the Title if needed.
    

Problem conclusion

  • Fix delivered to v10.0.1.1 and v2018.4.1.15
    
    Customer workaround: Go into APIs affected and replace Catalog
    Title with Catalog Name
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI81742

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-25

  • Closed date

    2020-12-10

  • Last modified date

    2020-12-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]

Document Information

Modified date:
11 December 2020