Skip to content

create-instance-task-agent-tool.adoc

Latest commit

 

History

History
80 lines (62 loc) · 3.27 KB

create-instance-task-agent-tool.adoc

File metadata and controls

80 lines (62 loc) · 3.27 KB

Adding an Omni Gateway Agent or Tool Instance

This diagram shows the upstream and downstream configurations of the instance. In this configuration, the downstream service is the service making requests that are completed by the upstream service. These terms represent the direction of dependency, not the direction of information.

The instance is deployed on a gateway between the upstream and downstream configuration

Add a New Agent or Tool Instance

To add and manage server instances for Omni Gateway, use the Agent and Tool Instances section in API Manager. These server instances can represent Agents, MCP servers, or LLM servers that extend Omni Gateway functionality.

  1. Navigate to Anypoint Platform > API Manager.

  2. Click Agent and Tool Instances.

  3. Click Add and select the protocol: Agent, MCP Server, or LLM.

  4. Select an Omni Gateway to deploy the server instance to from Select a gateway.

    Note

    If you don’t see an Omni Gateway listed, or you see an Omni Gateway but its status is Not Running, See Install Omni Gateway and Register and Run in Connected Mode for more information.

  5. Click Next.

  6. Select an instance:

    • Select asset from Exchange: To manage an agent or tool asset shared through Exchange.

      • Select the asset from Select asset. You can also search for an asset.

    • Create a new asset: To create a new asset.

      • In Asset name, enter a name for the new asset.

        Note
        		 Your asset is published to Exchange after it’s protected.

  7. Click Next.

  8. Configure the downstream configuration settings:

    Managed Omni Gateway
    Self-Managed Omni Gateway (Connected Mode)

  9. Click Next.

  10. Configure one of the server upstream configurations:

  11. Click Next.

Edit Agent Network Project Instances

Some instances in Agent and Tool Instances can be created by supplying a YAML file in an agent network project. For instances created with the YAML file, the YAML file is treated as the source of truth. If you edit the instance in API Manager (for example, to add policies), the changes are reverted to the YAML file when the instance is redeployed from the agent network project.

To ensure changes to instances created from a YAML source are present after redeployment, edit the YAML source.

For more information, see anypoint-code-builder::af-define-your-agent-network-specification.adoc.

See Also

  • latest-overview-concept.adoc

  • anypoint-code-builder::af-define-your-agent-network-specification.adoc

  • gateway::flex-install.adoc

  • gateway::flex-conn-reg-run.adoc
⚡