Exposing a SOAP API to Applications
The API Provider can restrict the exposure of specific operations of a SOAP API to other applications.
Consider you have a native SOAP API created in API Gateway with operations - Operation A, Operation B, and Operation C. You might want to expose the Operation A and Operation C, and restrict the visibility of Operation B to other applications. You can use the Expose to consumers button to switch on the visibility of Operation A and Operation C and switch off the visibility of Operation B as required.
If an application attempts to invoke the Operation C in the above SOAP API, API Gateway returns a HTTP response code 404.
By default, the Expose to consumers button is switched on for all operations of the SOAP API. Once the API is activated, all of its operations are exposed to registered applications. If you do not want a particular set of operations to be hidden for registered applications, switch off the Expose to consumers button in the SOAP API definition.
Note:
Be aware that API Gateway will not allow you to activate a SOAP API if none of the operations in the API are selected for exposing to other applications. You must select at least one operation of the SOAP API to enforce runtime invocations.
To expose a set of operations of the SOAP API
1. Click APIs in the title navigation bar.
This displays a list of APIs available in API Gateway.
2. Click the name of the required API.
This opens the API details page.
3. Click Edit.
If the API is active, API Gateway displays a warning message to let you know that the API is active.
4. Click Operations.
This displays a list of operations available in the API.
a. To select an operation, switch on the Expose to consumers button next to the operation URI.
You can select one or more operations to expose to other applications.
5. Click Save to save the updated API.
Activate the API, if it is not active, to put it into effect.