From dc46545b0d9dac07a9338d87854d2410a33c1701 Mon Sep 17 00:00:00 2001 From: walapalam Date: Mon, 5 Jan 2026 23:33:32 +0530 Subject: [PATCH] Add instruction for hosting PizzaShack sample backend in distributed setup #9872 --- .../deploying-wso2-api-m-in-a-distributed-setup.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md b/en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md index 3cff0ea94c..aedb2c162b 100644 --- a/en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md +++ b/en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md @@ -7,6 +7,9 @@ Given below are the API-M nodes you can have in a distributed deployment by defa !!! Tip To enable high availability, you need a minimum of two nodes running each component distribution. +!!! Note + To use the PizzaShack sample API in a distributed deployment, you need to host the sample PizzaShack backend (`pizzashack.war`) on a separate application server or container, as the backend is not included in the API-M component distributions by default. Ensure the backend URL is accessible to the Gateway. +