Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Dear customer, can you please confirm whether you have see the setting of "Endpoint behavior" = "v5 legacy behavior", which allows you to configure a separate vanity endpoint per gateway as described at the following links:
https://medium.com/@nisha.narayanan/vanity-endpoints-legacy-behavior-e6f69e09a97f
https://www.ibm.com/docs/en/api-connect/10.0.1.x?topic=wc-retaining-version-5-vanity-endpoint-behavior-in-catalog
Please let us know if you have looked at that, and whether it meets your requirement.
What we want, is that it is up to the API provider to decide, whether he wants to use a vanity end point or not. All APIs that do not have a vanity endpoint configured in their OpenAPI spec should use the default URL.
With the settings
Endpoint behavior: Default
Endpoint URLs: Display vanity URLs
Preference: API priority (use vanity endpoint(s) defined in the OpenAPI definitions)
it is possible to define one default endpoint only. But as we use 2 gateway services per catalog, we need to define the default endpoint per gateway service
This requirement is already supported by the legacy endpoint option available today - you can map gateway URLs to vanity URLs and that would help map multiple gateway URLs too different vanity URLs. For more details: https://medium.com/@nisha.narayanan/vanity-endpoints-legacy-behavior-e6f69e09a97f