Skip to content

Fix: Add PizzaShack backend note for distributed setup #9872 [4.6.0] #10514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Walapalam wants to merge 1 commit into
base: 4.6.0
Choose a base branch
from
Open

Fix: Add PizzaShack backend note for distributed setup #9872 [4.6.0] #10514

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions ...tup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<table>
<tr>
<th>
Expand Down