Benefit from significantly shorter job runtimes and faster connection setup thanks to targeted optimizations. New ad-hoc features like SAP user management and instance-level control provide even more flexibility in daily operations. In addition, job chaining enables a substantial reduction in downtime during patch processes.
In this article, we take a closer look at the performance improvements and new ad-hoc features in the EPOS Admin Engine. Updates to the BlueCopy system copy app and EPOS Automation Apps are covered in separate posts.
EPOS Framework
- New ad-hoc tasks such as SAP User Management in the Admin Engine
- Enhanced performance
- Downtime minimized during patching (first step) – job chains
EPOS Automation
- New apps: HANA Parameter, SAP Transports, MaxDB Update
- Enhancements in Profile Parameters, Compliance, HANA Update
BlueCopy (Our EPOS app for fully automated SAP system copies)
- Schedule system copies periodically via the internal scheduler
- Extended email functionality – notifications
- Additional SAP tasks added to standard
- Simplified UserExits with plugins
EPOS Reporting
- With even more information available now
Internal processes have been restructured in version 25.4, resulting in significantly improved performance. The most noticeable impact is during connection initialization.
„Job runtimes look much better now! An all-in-one collector with 34 systems now runs in just under 9 minutes, down from almost 40"
Two new capabilities have been added to the Admin Engine with this release:
- SAP user management
- Starting and stopping not only entire systems but also individual instances
Need to quickly lock or unlock a user in an SAP system? Use the new Admin Engine function for fast access.
Right-click on the system and select the desired action.
EPOS will automatically connect to the selected client using your stored SAP credentials and execute the action immediately.
Need to shut down an application server or add one during high-load periods?
Simply select the desired system in the Admin Engine and execute. As shown in this example, you can now also start, stop, or restart individual SAP instances.
You can now combine multiple actions into a single, streamlined workflow by defining a follow-up job directly.
The advantage: less waiting between steps — and significantly reduced downtime during patch processes.
In this example, a HANA update job was scheduled to run directly after a kernel update:
Reach out to our team anytime - we’re happy to assist!
Stay up to date with the latest news
With SAP announcing the end of the SAP Business Suite in 2027 – including SAP ERP ECC – SAP Landscape Management (SAP LaMa) is also being retired. …
Read more
Empirius feature in the E3 magazine. 'Choosing the right path for SAP Basis automation: Best-of-breed tools or an integrated suite?'
Read more
With the EPOS 25.4 update, we’re taking automation of SAP system copies to the next level: a new periodic scheduler, flexible email notifications, …
Read more