Step 2
Set Up Omni Gateway
Overview
All five modules in this workshop run on an Omni Gateway — MuleSoft’s next-generation API gateway. Before starting any module, provision your own gateway instance. You will reference the gateway’s public endpoint throughout the day.
Step 1 — Navigate to MuleSoft Platform
- Log in at anypoint.mulesoft.com using the credentials provided by your workshop instructor
- Make sure you are using the legacy UI (not the enhanced experience)
- In the top-right corner, confirm you are in the business group assigned to you
Step 2 — Navigate to Omni Gateways
- From the top navigation, go to Runtime → Runtime Manager
- In the left sidebar, click Omni Gateways
Step 3 — Add a Managed Omni Gateway
- Click Add Managed Omni Gateway
-
Fill in the form:
Field Value Gateway name attendee-gatewayDeployment target CloudHub-US-East-2→ Shared SpaceRelease channel Long Term SupportGateway size Small - Click Save & Deploy
The gateway will begin provisioning. This typically takes 2–3 minutes.
Step 4 — Verify the gateway is connected
- Wait for the gateway status to change to Connected (also shown as Running)
- If the status remains Disconnected or Pending after 5 minutes, refresh the page
Step 5 — Note your Public Endpoint
Once the gateway shows Connected, click on attendee-gateway to open its detail page. Find and copy the Public Endpoint URL — it will look like:
https://attendee-gateway-<unique-id>.cloudhub.io
Keep this URL handy. You will use it as the base URL when configuring MCP Servers, LLM Proxies, and API instances in every module throughout the workshop.
Verify your setup
- Gateway status shows Connected
- Public Endpoint URL copied and saved
Ready? Start with Module 1 — Scanners →