EPOS 25.6 at a Glance: All subreleases and what’s new

With Release 25.6, we introduce a set of targeted enhancements and new features for EPOS and BlueCopy. The focus is on further improving the robustness of database update processes, enhancing usability, and increasing flexibility in the day-to-day work of SAP Basis teams.

Below you will find an overview of the most important improvements delivered with subreleases 25.6.5, 25.6.4, 25.6.3, 25.6.2, and 25.6.1.

This minor release, EPOS 25.6.5, not only addresses minor imperfections but also introduces several useful features. This means you don't have to wait for the next major release to benefit from these advancements.

Previously, defining Start/Stop dependencies in EPOS was possible, but traceability and visualization were challenging. With this new release, you can now see dependencies graphically displayed and intuitively operable. This significantly simplifies the management and understanding of complex dependency structures.

The Db2 update process has been further optimized: License file integration is now fully automated as part of the process. This eliminates manual steps and ensures a smoother update. Additionally, the database and instance configuration is now backed up and compared not only before but also after the update. This provides a transparent overview of all changes at a glance.

In Oracle patching, the 'Golden Image' method is now supported. This offers you additional flexibility and efficiency when updating your Oracle databases.

Patching Diagnostic Agents on individual SAP systems is significantly simplified. Instead of having to define them individually, you can now use the new command-line parameter 'daadestination' to control whether the agent alone or both (SAP system and DAA) should be patched.

For example, to update only the DAA, simply enter the SAP system on which the DAA is installed and set the parameter daadestination=only.

This allows for more precise and flexible control over your kernel updates.

In addition to several minor improvements, this release also includes a new feature.

A status email always contains a direct link to the corresponding job. By default, the hostname of the EPOS server is used. If access to such links is not permitted in your organization and you need to use the FQDN instead, Release 25.6.4 provides the following options.

If you need to use not only the hostname but the fully qualified domain name (FQDN), you can simply adjust this in the mail template.

File:

templates\MailAlert.mailtmp

The following line exists there by default:

Open job in WebUi: <a href="{PROTOCOL}://{EPOSFQDN}:{PORT}/job/{JOBID}">{JOBID}</a>

Change it by specifying the full name (example: epossrv.emp.de):

Open job in WebUi: <a href="{PROTOCOL}://epossrv.emp.de:{PORT}/job/{JOBID}">{JOBID}</a>

Alternatively, after setting the global parameter PUBLIC_BASE_URL (available as of 25.4.6):

Open job in WebUi: <a href="{PROTOCOL}://{PUBLIC_BASE_URL}:{PORT}/job/{JOBID}">{JOBID}</a>

Release 25.6.3 delivers several focused improvements to the database update apps, along with a new option for handling LDAP configurations in EPOS. All changes are designed to provide greater control, transparency, and flexibility during update processes.

A new automatic check verifies available disk space in the DB2DIR directory. By default, the system checks for at least 3 GB of free space. This threshold can be adjusted via an app parameter.

The db2prereqcheck script can now optionally be executed already during the check phase. In this case, the software is also copied during the check run. This behavior is controlled via a new parameter in the app settings.

A new check validates available database disk space before starting a reconfiguration.

A new parameter allows granular permissions for database patches to be temporarily disabled when needed—useful for special cases or specific maintenance scenarios.

For environments using LDAP integration, a new configuration parameter has been introduced in EPOS. This is particularly helpful in scenarios where the browser does not retain the selected connection—for example, in restricted network environments.

With Release 25.6.3, database processes become even more robust and adaptable—further improving stability and convenience for SAP Basis teams.

Release 25.6.2 primarily includes smaller optimizations and refinements. One new feature, however, significantly improves clarity and usability when working with job folders in EPOS and BlueCopy.

A search bar has been added to the folder view within relevant job types. This allows users to locate subfolders much faster—especially beneficial in complex directory structures.

Breadcrumb navigation has been added to the folder overview. This provides instant visibility into the current location within the folder hierarchy, including all parent directories—making navigation more intuitive and efficient.

Release 25.6.1 introduces several practical enhancements designed to further streamline daily work with EPOS and BlueCopy.

The RFC TableSet has been extended to include the table RFCDES_OAUTH. As a result, OAuth-related RFC destinations are now automatically considered during system copies.

A new parameter, DB_BACKUP_CHECK, can now be set in the app settings (JSON file). This allows full control over whether the presence of a database backup is verified before an update is executed.

The Custom App has been enhanced to support faster script execution across multiple systems. SAP and DB checks can now be selectively disabled when required. In addition, the user interface has been visually refreshed and improved.

Security notes identified by the SecNotes QuickCheck are now clearly displayed in the reporting view. This makes it easy to see at a glance which security notes are relevant for each system.

Editing Filter Sets has been simplified. With the new option to display a Filter Set as plain JSON text, content such as lists of SAP notes can easily be added or modified using copy & paste.

Release 25.6.1 delivers many small but impactful improvements that make everyday work easier for SAP Basis teams—practical, efficient, and immediately usable, as you would expect from Empirius.