Creating an API by Importing an API from a URL
Before you begin
You must have the webMethods API Gateway's manage APIs or activate/deactivate APIs functional privilege assigned to perform this task.
About this task
To create an API by importing an API from a URL
Procedure
What to do next
Note:
- Importing an API fails for an invalid WSDL file.
- Creating an API by importing swagger files from an HTTPS URL that is using self-signed certificates might fail. To workaround this, you can set the system environment variable as: export TRUST_ALL=true, so that the invalid certificates are ignored. Be aware that setting this variable makes the swagger-parser ignore all invalid certificates too. So this workaround has to be used with caution.
- To avoid encountering errors while parsing large
responses from the native API, you have to change the enablesoapValidation property by commenting
out the
<parameter name="enableSoapValidation">true</parameter>
in SAG_Install_Directory\IntegrationServer\instances\default\config\wss\axis2.xml and restart the server for the change to take effect. - Since the GraphQL API schema does not contain a native endpoint, you must manually update the Native endpoint URL in the API details section and the Endpoint URI in the routing policy after you create a GraphQL API.