Digital Transformation . API . Integration . IAM

This blog is about the most recent release of WSO2 API Manager i.e. APIM v4.6 that brings a major leap forward in AI-driven API management, federated gateway support, and advanced analytics. This version introduces the AI Gateway with multi-model support and MCP tool integration, a universal API management interface for federated gateways, and enhanced analytics and monetization through Moesif. New Features MCP Gateway & MCP Hub – Manage and orchestrate MCP tools seamlessly. Multi-Model AI Service Provider Support – Integrate multiple AI models effortlessly. AI Guardrails & Semantic Caching – Ensure safe, efficient AI-driven API interactions. API Discovery for Federated Gateways – Simplify API visibility across gateways. API Analytics with Moesif – Gain product-level insights and monetization visibility. Application Update Workflow – Streamline application management. Application-Level Scopes – Enhance API security and access control. Improvements Expanded list of onboarded AI ...

If you are using WSO2 API Manager for managing the API's lifecycle, it's important to understand the flow when API Manager gets shutdown. So, whether you're running WSO2 API Manager in production or a test environment, it's critical to understand how it shuts down. A graceful shutdown ensures that no in-flight API requests are abruptly cut off, database connections are properly closed, and services stop cleanly. In this post, we’ll break down the sequence of events that occur when you shut down WSO2 API Manager, and why it matters. So, what Triggers the Shutdown? Shutdown can be initiated in several ways: Pressing Ctrl + C on the terminal 1. Running the shutdown script: ./wso2server.sh stop Or  ./api-manager.sh stop 2. Sending a termination signal: kill -15 <PID> Any of these methods initiate a graceful shutdown via a JVM shutdown hook, which delegates the shutdown process to the Carbon runtime environment WSO2 is built upon. Why Graceful Shutdown ?   A clean shut...

  This article is about sharing an important achievement with my readers. I’m thrilled to share an exciting milestone in my journey with WSO2 – I’ve been officially recognized as a WSO2 Ambassador for the year 2025!  Being named a WSO2 Ambassador is not just a title – it's a reflection of my commitment to empowering the community through knowledge-sharing, mentorship, and real-world implementation of WSO2 technologies. Over the years, I’ve had the privilege to work extensively with the WSO2 ecosystem, from API Manager and Micro Integrator to Identity Server, across various digital transformation projects. Official Announcement:  https://wso2.com/library/blogs/introducing-the-wso2-ambassador-program/ What This Means to Me This recognition reinforces my passion for open-source middleware and motivates me to contribute even more actively to the community. As a WSO2 ambassador, I'll get direct support from WSO2 team to amplify my impact...