Tricise Automic V26 Enablement Series: SAP Agent Multiple System Support

Automic V26 SAP Agent Multiple System Support – Feature Lookup Overview

Automic V26 introduces one of the most impactful architectural enhancements for SAP integrations with SAP Agent Multiple System Support. With this article, we officially start the Feature Lookup within our Tricise Automic V26 Enablement Series, where we analyze and explain the most important innovations of Broadcom‘s latest Automic release.

Over the coming weeks, we will publish deep dives into several new features of the V26 release, helping customers understand technical changes, operational impact, and strategic advantages. This first Feature Lookup focuses specifically on SAP Agent Multiple System Support and what it means for SAP-centric automation landscapes.

What Changes with SAP Agent Multiple System Support in Automic V26?

In previous versions, SAP connection details were tightly bound to the agent configuration. A fixed connection object — typically maintained in Client 0 — was required before execution. This created administrative overhead and reduced flexibility, especially in dynamic or multi-client environments.

With the new version, connection details no longer need to be statically defined on the agent. Instead, SAP connection parameters can now be passed directly within the executing SAP object.

• No mandatory fixed connection object in Client 0
• No pre-assignment required before agent startup
• Connection objects can be created in the execution client
• More flexible handling of multi-system SAP environments

Why This Enhancement Matters for SAP Landscapes

For enterprises running complex SAP landscapes — including clustered systems, multiple SIDs, or hybrid environments — this enhancement introduces significantly improved scalability and architectural flexibility.

By moving connection handling into the job context, configuration becomes more transparent and easier to maintain. Security improves because connection definitions are scoped to execution contexts rather than centralized static objects.

This reduces administrative effort, simplifies onboarding of new SAP systems, and lowers operational risk in highly dynamic environments.

Operational Benefits in the V26 Release

• Reduced configuration effort
• Higher flexibility for SAP integrations
• Improved governance and separation of concerns
• Cleaner architecture for multi-client setups
• Enhanced security posture

For customers planning upgrades to Automic V26, this feature alone can justify a detailed review of their SAP agent architecture. If you are preparing your upgrade strategy, our Automic Environment Update Services can support you in evaluating and implementing these changes efficiently.

Part of the Tricise Automic V26 Enablement Series

This article is part of our ongoing series, where we continuously analyze the most relevant improvements of the new release. In the coming weeks, we will cover additional innovations from both administrator and end-user perspectives.

If you want structured, in-depth training on Automic V26, our upcoming Tricise University update courses will include detailed explanations, real-world examples, and migration guidance.

For hands-on experience, we are also preparing V26 demo environments and labs to allow customers to explore new capabilities in a safe and controlled setup. More detailed feature deep dives will follow soon.