|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/ibm-api-connect-developer-guide-basics/
课程评论：没有评论
**IBM API Connect 开发者指南 - 基础课程总结** 本课程深入探讨了 IBM API Connect 的完整 API 生命周期管理，涵盖从 API 的创建到最终的退役。课程将 API 生命周期划分为以下关键阶段： * **API/产品创建 (Create an API/Product)** * **部署 (Deployment)** * **运行 (Running)** * **API 安全 (API security)** * **API 管理 (API Management)**，包括监控 (Monitoring)、弃用 (Deprecate) 和退役 (Retire) 等。 课程详细讲解了每个生命周期阶段的实现与配置，并配以实际操作演示，旨在帮助学员理解 API 生命周期概念，并通过具体的策略操作构建集成流程。 **核心内容要点：** * **API Manager (提供商组织的一部分):** 提供用户界面，用于创建、管理、保护、版本控制和退役 API。API 可在 API Manager 中通过策略设计，或直接导入。 * **API 发布与开发者门户:** API 发布后，可在开发者门户中供外部消费者使用。消费者通过创建应用程序在开发者门户中注册。 * **API 治理与策略:** API Manager 通过创建代理端点和应用各种策略来治理 API。可根据业务需求配置如速率限制、客户端 ID 强制执行等策略。 * **集成流程构建:** 支持使用如 switch、log、XSLT、invoke、map 等多种策略操作来创建集成流程。 * **分析功能:** 提供分析功能，以便了解交易情况和系统负载。 * **安全机制:** 课程详细讲解并实践了以下安全机制： * 基本认证 (Basic Authentication) * API 密钥验证 (API key validation) * OAuth v2.0 本课程强调通过实际操作和具体示例，帮助学员掌握 API Connect 的核心功能，从而有效地管理和保护 API。
This course is designed to understand the complete API Lifecycle Management from the creation of the API to the Retirement of the API. The below listed are the life cycle stages in IBM API connect. Create an API/ProductDeployment/RunningAPI securityAPI Management(Monitoring/Deprecate/Retire etc)The implementation/configuration stage for each lifecycle is explained with the practicals. The focus of the course is to make understand the API Lifecycle concepts with proper examples and to build the integration flows using the policy actions. The API Manager which is part of the Provider organization provides the UI to create, manage, secure, versioning, and retire the APIs. The APIs can be designed using the policies in the API manager or the APIs can be imported. When the APIs are published, it is available in the Developer portal. The consumers of this API, register with the Developer portal by creating the application. The developer portal is part of the consumer organization. API manager governs the API by creating the proxy endpoint and applying the different kinds of policies. Based on the business requirements, the required policies like rate limiting, Client ID enforcement, etc. can be configured. It has the option to create integration flows using different policy actions like a switch, log, XSLT, Invoke, map, etc. It provides the Analytics feature to understand the transactions and the load on the system. The following security mechanisms are explained and implemented.Basic AuthenticationAPI key validationOAuth v2.0
