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.

 View Only
  • 1.  Exposure of the 3 API Connect catalogs on different FQDNs

    Posted Wed July 03, 2024 01:56 PM


    Good morning

    We currently have an API Connect v5c 10.0.5.1 setup,
    on production which hosts three catalogues:

    "- fatturazione"
    "- integrazioni"
    "- interventi"

    These APIs and related products that are hosted on these catalogs are all reachable from the same FQDN https://apic.digibyte.it. 
    This is limiting our flexibility,
    when assigning certain restrictions/policies at the catalog level, 
    so we wanted to see what options we have.

    What we want to achieve is to have three distinct FQDNs:

    https://fatturazioneapic.digibyte.it
    https://integrazioniapic.digibyte.it
    https://interventiapic.digibyte.it

    so that traffic on these endpoints is delivered to the correct catalog.

    While researching online, we discovered that the concept of Vanity Endpoints exists: https://medium.com/@nisha.narayanan/vanity-endpoints-legacy-behavior-e6f69e09a97f. 
    Is it something that can help us achieve what we want? 

    And if so, are there other configurations to do to fully achieve what we want? 

    I took a look at the configurations in our catalog and the Vanity Endpoints are all configured on https://apic.digibyte.it.

    We would appreciate any advice on this.

    Thanks in advance
    Emil C.



    ------------------------------
    Emiliano Canova
    ------------------------------


  • 2.  RE: Exposure of the 3 API Connect catalogs on different FQDNs

    Posted Thu July 04, 2024 03:16 AM

    Hi Emil.

    vanity endpoint represents the endpoint by which an API is known externally, that is the endpoint published to the Developer Portal and is used by an application developer to invoke the API.  But APIs are running on the gateway host ( https://apic.digibyte.it), So we have to configure DNS Mapping in network level to route the calls to the gateway host where the API is running. (Eg: https://fatturazioneapic.digibyte.ithttps://apic.digibyte.it ).



    ------------------------------
    Nirmalan
    ------------------------------



  • 3.  RE: Exposure of the 3 API Connect catalogs on different FQDNs

    Posted Thu July 04, 2024 04:39 AM

    See this Blog post: https://community.ibm.com/community/user/integration/blogs/nisha-narayanan/2021/10/13/vanity-endpoints-in-api-connect



    ------------------------------
    Nick Cawood
    API Connect Consultant
    IBM Expert Labs
    IBM UK Ltd

    https://www.linkedin.com/in/nickcawood/
    ------------------------------