What is best ways to have better framework for Catalog of services with eaze to accessed by any developer in portal
One of the way is to port the WADL into portal hence it automatically creates the documentation with required authentication information and methods.
Onboard the subscriber hence, on-boarded application can invoke the required SOAP/REST based on the group/organization
Do we need to any customization in Portal or WADL (generated from SOAP UI) to make the catalog framework for (for Portal) eaze to subscriber ? Please advice any recemendations
The approach you mentioned should work well to give developers the required information about your APIs. As long as you upload the WADL via the Portal for each of your APIs, developers will be able to see details about the API in API Explorer. The Catalog will serve as a means of showing to developers all the APIs that are available for them to use. No customization should be required.
Product Owner, CA Technologies