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

[Walapalam]

Purpose

Resolves #9872. PizzaShack sample fails in distributed setup because backend isn't included.

Goals

Instruct users to host the 'pizzashack.war' separately for distributed deployments.

Approach

Added an '!!! Note' block in 'deploying-wso2-api-m-in-a-distributed-setup.md'.

User stories

As a DevOps engineer, I want to know why PizzaShack isn't working in my distributed cluster.

Release note

Fixed documentation issue regarding Resolves #9872. PizzaShack sample fails in distributed setup because backend isn't included..

Documentation

Updates 'deploying-wso2-api-m-in-a-distributed-setup.md'.

Training

N/A

Certification

N/A

Marketing

N/A

Automation tests

• Unit tests

  N/A (Documentation change only)

• Integration tests

  N/A (Documentation change only)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? yes
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

Parallel PR targeting '4.6.0' branch.

Migrations (if applicable)

N/A

Test environment

Local MkDocs build.

Learning

Reviewed existing documentation and verified links/commands.

[coderabbitai]

Warning

Rate limit exceeded

@Walapalam has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 28 minutes and 21 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 89d01a9 and 92bbcac.

📒 Files selected for processing (1)

• en/docs/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

All committers have signed the CLA.

[Copilot]

Pull request overview

This PR adds documentation to address issue #9872, where users experience failures when trying to use the PizzaShack sample API in distributed API-M deployments. The documentation clarifies that the PizzaShack backend needs to be hosted separately in distributed setups.

Key Changes:

• Added a note block explaining that the PizzaShack backend (pizzashack.war) must be hosted on a separate application server or container in distributed deployments
• Clarified that the backend is not included by default in distributed API-M components
• Provided guidance that the backend URL must be accessible to the Gateway

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.