API Connect

API Connect

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#API Connect
#Applicationintegration
#APIConnect
 View Only

  • 1.  inline schema issue after migration in APIConnect v10

    Posted 02/14/22 03:08 PM
    Edited by santhoshkumar surisetty 02/15/22 10:57 AM
    Hi,

    apiconnect v5  artifacts are migrated by using apic-migrate-utility_v10.0.3.0-R3  . we are getting errors on api level as field may have  two types in the response  , string or null. the same working in v5 but giving validation errors in v10.could you please help on it. it seems to be null type is not supported by v10



    ------------------------------
    santhoshkumar surisetty
    ------------------------------


  • 2.  RE: inline schema issue after migration in APIConnect v10

    Posted 02/15/22 12:03 PM
    Santhoshkumar,

    I really would suggest you create the API from zero (you can create just the part that are giving you errors) and compare
    This utility is not mature to make those migrations with no errors, we had a lot of problems with it here.

    Thanks!

    ------------------------------
    Leandro Takeda
    ------------------------------



  • 3.  RE: inline schema issue after migration in APIConnect v10

    Posted 02/15/22 12:43 PM
    Thank you Leandro , Point noted.

    ------------------------------
    santhoshkumar surisetty
    ------------------------------

    Original Message


  • 4.  RE: inline schema issue after migration in APIConnect v10

    Posted 02/16/22 08:46 AM

    Hi Santhoshkumar,

    This is not an AMU issue.  The AMU is moving the definition from the v5 API to the v10 API without change.  What is different here is that the validation being done by the v10 management server is much more stringent than v5 and is producing these validation errors.  Definitions in v5 were primarily used by the map and validate policies.  I'm almost positive that the map policy would only use the first array element to determine the type but I'm not sure about the validate policy.  I'd open a PMR for this to have this validation issue investigated.  I'd provide the v5 and the migrated v10 API yaml files with the issue.

    Regards,



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM
    ------------------------------



  • 5.  RE: inline schema issue after migration in APIConnect v10

    Posted 02/17/22 02:06 AM
    Hi Steve,

    We successfully migrate the API Connect from V5 to V10, but when we tried to publish API's into existing product from API designer it show-
    "Error
    Something went wrong...."

    We face same error for all the migrated API's and products.
    Could you please help on it.



    ------------------------------
    Suraj Sakpal
    ------------------------------

    Original Message


  • 6.  RE: inline schema issue after migration in APIConnect v10

    Posted 02/17/22 04:11 PM

    Hi Suraj,

    I'd suggest you open a PMR and provide your AMU logs and the specific detail of what you're seeing in the API designer with any API designer logs as well.  That would be the best way to triage what you're running into.  The "Something went wrong ..." is obviously lacking the detail needed.  As noted in my previous post the publish validations on the API Designer are more stringent in v10 that v5.  We've seen some issues where the AMU has added support to attempt to "fix" some of these types of issues during the migration process.  If indeed your issue is only due to the array of types in your definition which the publish validation doesn't like, that will need to be investigated to determine if there is a product issue that needs to be resolved.  As for your definition issue noted in your initial post, providing your v5 and API Gateway yaml files would be a good starting point as well to recreate the issue and see exactly how you are using this in your definitions (ie, validation policy, map policy, or perhaps used to generate sample requests in the portal?).

    Regards,



    ------------------------------
    Steve Linn
    Senior Consulting I/T Specialist
    IBM
    ------------------------------

    Original Message


Related Content