How to connect multiple SAM together?

Solace Agent Mesh
1

Hi Guys,

I deployed 2 x SAM (self managed) with same LLM and I would like to make them communicate each other.

is this possible?

Regards,

Alex Kwan

2

Hi Alex,

SAM agents communicate through the Solace event broker using A2A topics - not directly. So to make two SAM deployments talk:

Point both at the same broker with the same NAMESPACE. Discovery happens automatically over {namespace}/a2a/v1/discovery/agentcards, and agents on either side become visible to each other (subject to allow_list/deny_list).

If they must use separate brokers, link those brokers via DMR (event mesh) and keep the namespace identical — the topics propagate across.

The shared LLM doesn’t matter here; this is purely a broker + namespace wiring question. Does that help?

3

hi giri,

I am experiencing same issues. I try to point both SAM into sam broker with same namespace.

But it fail to create queue on ‘default_namespace/q/gdk/gateway/a2a_webui_app’ with error ‘Max clients exceeded for queue’. I try to disable turn on WebUI gui when init on the 2nd SAM, but it doesn’t help.

4

Hi @chung.w - curious to know what your setup for the two SAM instances is. From the error you got it seems like you are trying to run multiple instance of the same web ui gateway which is causing the error. What is your end goal? Are you trying to run multiple agents or gateways in different sam instances?

Agent Mesh is your runtime environment for the components you’re running for your agentic solution, so more on details on your setup would be helpful to debug. (and @alexkkk if you can shine some light on your use-case it would be great!)

For example, if you have the following agent mesh instances:

  1. The first sam instance is hosting the webUI gateway and the orchestrator. This instance is self managed locally with your own LLM model
  2. The second instance is hosting all your agent in a k8s pod in EKS in AWS.
  3. The third sam instance is hosting some specialized agents and gateways in GCP.

If all these instances are configured with the same solace broker connection, then you would easily have a holistic view of all your components (agents + gateways) communicating with each other and discoverable through the webUI gateway. Let me know if you have any follow up questions.

Hope this helps!