Back to all use cases

Architecture AdvisoryCross-Industry

No single agent and no single person between a recipe and Production

Integration Team

A typical Workato consulting engagement for a team whose on-prem connections run through one agent and whose Production deploys depend on one person: an agent group design, a network path check and a documented Development to Production routine.

Workato consulting

Overview

This is a typical engagement for an integration team whose recipes reach an on-prem database and file shares through one Workato on-prem agent, and whose deployments to Production are done by one collaborator from memory. AceMQ engineers, with a partner subject-matter expert where needed, review the agent path and the deployment routine and write the design.

Challenge

Workato recommends several agents per on-prem group for availability, fault tolerance and load balancing. The agent makes outbound connections to Workato over TCP 443 and needs no inbound ports, but a TLS inspection proxy can break its mutual TLS trust chain, and the group IP allow-list controls where agents connect from, not where they connect to. With Environments enabled, projects deploy from Development to Test or Production, and the collaborator needs the deployment privilege in both environments.

Environment

One on-prem agent on a single Windows server, recipes using on-prem connections, Environments enabled with Development, Test and Production, and a deployment checklist kept by one engineer.

Approach

AceMQ engineers review the agent host, its group, the outbound path including proxies and any TLS inspection, and the connections that depend on it. They design a group of two or more agents on separate hosts, an upgrade procedure, and a deployment routine with roles in both environments, a test step and a rollback.

Solution

  1. Agent inventory, host placement and group layout with at least two agents on separate hosts
  2. Outbound TCP 443 path, gateway allow-lists, proxy and TLS inspection findings
  3. Agent upgrade and restart procedure that keeps one agent serving
  4. Environment layout and which collaborators hold the deployment privilege in each
  5. A written Development to Test to Production routine with a rollback
  6. Alerting for agent status through a Handle errors block on the on-prem steps

Outcome

The engagement delivers a written design with the agent group layout, the network findings, the upgrade procedure, the deployment routine and a rehearsal plan in Test. The customer's team implements it, or AceMQ can implement it alongside them.

Technologies

WorkatoOn-prem agent

Have a Workato Challenge Like This?

AceMQ's senior Workato engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.