Adding a SOAP API definition

If you have an existing SOAP service that you want to expose more widely, you can add a SOAP API to API Connect. You can use the Developer Portal to publicize the SOAP service to the developers. If a developer wants to use the SOAP API, you can use API Connect to manage their sign-up and access to the service, and track the usage of that API.

About this task

You can add a SOAP API to expose an existing SOAP service by supplying the WSDL file that defines that existing service in one of the following ways:
  • You can provide the WSDL as a file or URL.
  • You can provide one or more WSDL files in a single .zip file that contains the WSDL files and any necessary schemas.
  • Icon indicating that this applies only to the API Manager UIIf the service owner registered that service in a supported service registry, you can search for the SOAP service in a service registry. For more information, see Adding a SOAP API definition by discovering a service from a registry.

The service must support Web Services Basic Profile Version 1.1 - Second Edition.

Important: If you are using API Connect in the cloud, then the services that you expose must be visible on the Internet, they must not be accessible only from within your corporate intranet. However, you can use TLS profiles configured in API Manager to protect the communication channel between the API Gateway in API Connect and the services that you expose on the Internet through your DMZ. You can also use the IBM Cloud Secure Gateway service to provide secure access to your on-premises services from IBM API Connect for IBM Cloud; for more information, see About Secure Gateway.
Use the following tasks to add and configure a SOAP API.
Note: These tasks can be completed only by users who have the ability to edit draft APIs. Users with the ability to view draft APIs cannot create, edit or delete APIs.