We are currently facing a challenge in exposing a SOAP service through IBM API Connect. The WSDL and its associated XSDs have been successfully deployed to the API Manager. However, when attempting to access the service via the browser using the ?wsdl query parameter, the returned WSDL reference points to a generic endpoint without a unique identifier URI.

🔍 Observed Behavior:

• Accessing the WSDL via the browser (e.g., https://apic-1-gw-gateway-cp4i-dev.apps.cloudpak-ocp-nonprod.XXXXX.com/XXX-dev/$catalog_name/?wsdl) returns a fixed reference to one specific WSDL.

• The returned WSDL contains a generic service endpoint without a unique path or identifier, making it difficult to distinguish between services.

• Attempts to manually update the service tag in the WSDL with a specific path were unsuccessful-the reference still resolves to the generic endpoint.

• Suspected caching issue: republishing the APIs under different products did not resolve the behavior.

• This issue affects approximately 40 SOAP APIs.

❓ Request for Guidance:

• Is there a recommended approach to ensure each SOAP service exposes a unique URI in the WSDL reference?

• Can this issue be tested and resolved by updating one or two APIs first, or is it necessary to update all 40 APIs to observe the effect?

• Are there any known caching mechanisms or configuration steps in API Connect that could be influencing this behavior?

📌 Additional Notes:

We are looking for a scalable and maintainable solution that allows proper exposure of each SOAP service with a distinct endpoint. Any best practices or configuration tips would be greatly appreciated.