Merge pull request #631 from mulesoft/W-22323446-Flex-to-Omni-rebranding-CP

W-22323446-Flex-to-Omni-rebranding-CP

Author: Crispy-Salesforce

modules/ROOT/pages/_partials/af-shared.adoc

@@ -63,7 +63,7 @@ To complete these tasks, you also need:
 * xref:anypoint-code-builder::start-acb.adoc[Anypoint Code Builder desktop]
 +
 Allowlist Anypoint Code Builder URLs. For more information, see xref:anypoint-code-builder::urls-to-allow.adoc[Allow URLs for Anypoint Code Builder].
-* xref:gateway::flex-gateway-managed-ingress-egress.adoc[Flex Gateway Ingress and Egress gateways]
+* xref:gateway::flex-gateway-managed-ingress-egress.adoc[Omni Gateway Ingress and Egress gateways]
 
 === MuleSoft Vibes Requirements (Optional)
 
@@ -87,7 +87,7 @@ If you're using the Anypoint CLI to create agent network projects, ensure you me
 . Use Anypoint Runtime Manager to set up a private space in CloudHub 2.0 or deployment target in Runtime Fabric.
 +
 See xref:anypoint-code-builder::af-get-started.adoc#setup-space[Set Up the Private Space or Deployment Target for Your Environment].
-. Set up Ingress and egress Flex Gateways for the private space or deployment target.
+. Set up Ingress and egress Omni Gateways for the private space or deployment target.
 +
   * If using Anypoint Code Builder, see xref:anypoint-code-builder::af-get-started.adoc#setup-gateways[Set Up Agent Network Gateways for the Private Space or Deployment Target].
   * If using the Anypoint CLI, see the xref:anypoint-code-builder::af-build-agent-networks-in-a-ci-cd-environment.adoc#agent-network-setup-gateways[setup gateways command reference].

modules/ROOT/pages/af-agent-networks.adoc

@@ -44,7 +44,7 @@ Publish existing agents and tools (HRIS, Identity, ITSM, Payroll, Facilities, LM
 An agent broker decomposes the task of onboarding the new hire (create HR record, provision identity, assign hardware, grant app access, enroll in benefits and training), calling MCP and A2A agents as needed, with human‑in‑the‑loop approvals where required.
 * Govern
 +
-Flex Gateway enforces authentication, least‑privilege access, and guardrails. API Manager policies ensure consistent controls across all calls and data exchanges.
+Omni Gateway enforces authentication, least‑privilege access, and guardrails. API Manager policies ensure consistent controls across all calls and data exchanges.
 * Observe
 +
 Monitoring and traces (beta) give end‑to‑end visibility into progress, failures, and latency. Visualization shows which agents interacted and where bottlenecks occurred.
@@ -114,16 +114,16 @@ The asset might also be published to Exchange.
 [[agent-network-architecture]]
 == Agent Network Architecture
 
-This diagram shows an agent network with agents and MCP servers, traffic through Flex Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer.
+This diagram shows an agent network with agents and MCP servers, traffic through Omni Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer.
 
-image::agent-fabric-architecture.png[Agent Fabric showing agents and MCP servers defined in YAML and published to Exchange, with traffic through Flex Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer]
+image::agent-fabric-architecture.png[Agent Fabric showing agents and MCP servers defined in YAML and published to Exchange, with traffic through Omni Gateway, governed by API Manager, and observed in Anypoint Monitoring and Agent Visualizer]
 
 [calloutlist]
 . Publish the agentic assets to Anypoint Exchange for discovery and reuse after you define the agent network (brokers, agents, MCP servers) in the agent network YAML in Anypoint Code Builder.
 . Deploy the agentic assets to CloudHub 2.0 (managed in Runtime Manager).
-. Enforce policies on incoming traffic to the network with an ingress Flex Gateway, which sits in front of brokers and API endpoints.
-. Enforce policies, manage connections, and emit telemetry data with an egress Flex Gateway, which sits on outbound paths from brokers and agents to external agents and services.
-. Collect logs, metrics, and traces from Flex Gateway and runtimes in Anypoint Monitoring.
+. Enforce policies on incoming traffic to the network with an ingress Omni Gateway, which sits in front of brokers and API endpoints.
+. Enforce policies, manage connections, and emit telemetry data with an egress Omni Gateway, which sits on outbound paths from brokers and agents to external agents and services.
+. Collect logs, metrics, and traces from Omni Gateway and runtimes in Anypoint Monitoring.
 
 [[llm-support]]
 == Large Language Models

modules/ROOT/pages/af-deploy-agent-network-targets.adoc

@@ -1,9 +1,9 @@
 [[deploy-instances]]
 = Deploy Agent Network Instances
 
-Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric. When you deploy, Flex Gateway secures your agent network in the ingress gateway. Also, it secures your brokers, agents, and MCP servers in the egress gateway.
+Deploy your agent network instance to a deployment target. You can deploy to a CloudHub 2.0 private space or to a Runtime Fabric. When you deploy, Omni Gateway secures your agent network in the ingress gateway. Also, it secures your brokers, agents, and MCP servers in the egress gateway.
 
-These Flex Gateway policies are applied automatically at deployment.
+These Omni Gateway policies are applied automatically at deployment.
 
 
 [%header,cols="20,40a"]

modules/ROOT/pages/af-get-started.adoc

@@ -25,17 +25,17 @@ You must complete this step so that the private space appears as a valid deploym
 +
 Create a target space for Runtime Fabric.
 +
-For information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Flex Gateway on Runtime Fabric].
+For information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Omni Gateway on Runtime Fabric].
 
 [[setup-gateways]]
 == Set Up Agent Network Gateways for the Private Space or Deployment Target
 
 After you have a target space, use the `MuleSoft: Set Up Agent Network Gateways` command to create the ingress and egress gateways required for deployment in either CloudHub 2.0 or Runtime Fabric.
 
-For agent networks, you must have at least one small Managed Flex Gateway and one large Managed Flex Gateway in your environment.
+For agent networks, you must have at least one small Managed Omni Gateway and one large Managed Omni Gateway in your environment.
 For more information about gateways, see xref:gateway::flex-architecture-basic-deployments.adoc[].
 
-For more information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Flex Gateway on Runtime Fabric].
+For more information about Runtime Fabric deployments, see xref:gateway::flex-gateway-managed-set-up.adoc#rtf[Managed Omni Gateway on Runtime Fabric].
 
 . In Anypoint Code Builder, from the Command Palette, run the command *MuleSoft: Set Up Agent Network Gateways*.
 +

modules/ROOT/pages/af-project-files.adoc

@@ -444,7 +444,7 @@ policies:
 
 Apply policies at the broker or at the connection. Reference the policy definition and apply the configuration.
 
-For more information about applying policies via Flex Gateway in Local Mode, see:
+For more information about applying policies via Omni Gateway in Local Mode, see:
 
 * xref:gateway::flex-agent-secure.adoc[]
 * xref:gateway::flex-gateway-secure-local.adoc[]

modules/ROOT/pages/af-troubleshoot-agent-networks.adoc

@@ -28,7 +28,7 @@ Enable logging and log levels from CloudHub 2.0 or Runtime Fabric:
 
 Edit `agent-network.yaml` to set message logging for MCP servers and agents.
 
-Message logging uses the xref:gateway::policies-included-message-logging.adoc[Flex Gateway Message Logging policy]. In the `connection` section of the agent or MCP server instance you want to log, add the following logging policy inside `policies`:
+Message logging uses the xref:gateway::policies-included-message-logging.adoc[Omni Gateway Message Logging policy]. In the `connection` section of the agent or MCP server instance you want to log, add the following logging policy inside `policies`:
 
 [source,yaml]
 ----
@@ -65,7 +65,7 @@ Use the steps in this section to diagnose and fix common problems in agent netwo
 If Anypoint Monitoring isn't showing traces for agents and MCP servers, check these settings:
 
 * In API Manager, verify you've enabled the tracing policy for all brokers and agents.
-* In the managed Flex Gateways, verify that you've enabled Distributed Tracing for ingress and egress.
+* In the managed Omni Gateways, verify that you've enabled Distributed Tracing for ingress and egress.
 
 === Issue: No Agent Network Commands in Anypoint Code Builder