Using API Mediation Layer

There are numerous ways you can use the API Mediation Layer. Review this topic and its child pages to learn more about the various ways to use the API Mediation Layer.
For information about the API versioning, see API Catalog and Versioning.

Tip: For testing purposes, it is not necessary to set up certificates when configuring the API Mediation Layer. You can configure Zowe without certificate setup and run Zowe with verify_certificates: DISABLED.

For production environments, certificates are required. Ensure that certificates for each of the following services are issued by the Certificate Authority (CA) and that all keyrings contain the public part of the certificate for the relevant CA.

• z/OSMF
• Zowe
• The service that is onboarding to Zowe

API Mediation Layer Use Cases

There are two primary use cases for using the API ML:

• To access APIs which have already been onboarded to the Mediation Layer via the API Catalog, and leverage their associated Swagger documentation and code snippets.
• To onboard a REST API service to the API ML to contribute to the Zowe community.

See the following topics for detailed information about how to use the API Mediation Layer:

• Ways to use API ML via API ML Catalog

  • View Service Information and API Documentation
  • Swagger "Try It Out" functionality
  • Swagger Code Snippets functionality
  • Static APIs refresh functionality
  • Change password via API Catalog functionality
  • Onboarding a REST API service with the YAML Wizard

• Other features when using API ML

  • Using Metrics Service (Technical Preview)
  • API Mediation Layer Routing
  • Obtaining Information about API Services
  • WebSocket support in API Gateway
  • Personal Access Tokens
  • SMF records