We are pleased to announce the latest release of IBM WebSphere Automation 1.10.0 on September 26, 2025.

At IBM, we believe that the best innovations begin with listening. Our customers’ insights are the cornerstone of how we shape and refine our products. In response to your feedback, we have introduced a few powerful upgrades that matter most to your business: performance, stability, and security.

Let us walk through what is new and more importantly how these enhancements deliver tangible business value in real-world scenarios.

Support for Modernized Runtime Extension for Java (MoRE)

Traditional WebSphere Servers v9.0.5.23 onwards have a new IBM Modernized Runtime Extension for Java (MoRE v1.0.0) that can be installed. WebSphere Automation showed an incorrect Java SDK version on its user interface. This would have prevented users from leveraging the product to view JDK Common Vulnerabilities and Exposure (CVEs), leaving the systems open to vulnerabilities. This has been corrected in the new version and now provides:

·      Improved Compatibility Assurance

Ensuring the correct SDK version is visible helps teams validate compatibility and avoid runtime errors, especially in production environments.

·      Faster Troubleshooting and Support

Support teams can now immediately verify the correct Java version, speeding up root cause analysis and resolution times.

·      Improved Operational Accuracy

Reduces misconfiguration risks and ensures that developers and admins are working with accurate environment metadata, which is critical for debugging, compliance, and performance tuning.

Filtering & Grouping

Customers with huge WebSphere estate having thousands of WebSphere servers would find it cumbersome to check vulnerabilities for individual server and apply the fixes. We have come up with a new feature of tags that are custom values that can be created and assigned to registered servers for custom grouping. Customers can now tag the servers and filter them to apply fixes based on priority. This helps in:

·      Enhanced Visibility and Organization

Tags allow teams to slice and dice server inventories in ways that align with business priorities. Instead of rigid, predefined groupings, you get custom views tailored to your operational needs.

·      Streamlined Operations

Need to apply a patch to all servers tagged “Finance”? Or monitor only those tagged “High Availability”? Tags make it easy to automate tasks, filter dashboards, and target actions with precision—saving time and reducing errors.

·      Better Reporting and Decision-Making

Tags enable more meaningful analytics. You can generate reports based on business-relevant groupings, helping stakeholders understand performance, cost, and risk across different segments.

·      Improved Governance and Compliance

By tagging servers with compliance levels or data sensitivity, organizations can enforce policies more effectively and ensure that critical assets are managed according to regulatory standards.

·      Agility for Growth and Change

As your infrastructure evolves, tags provide a scalable way to adapt. Whether you're onboarding new teams, migrating workloads, or reorganizing business units, tags help maintain clarity and control.

Here is a video on the tagging feature demo: WSA Tagging feature

Several bug fixes added

Clarifying Ownership and Permissions in Ansible process

More details are provided in WebSphere documents on ownership and permissions of Ansible process like BackUp, DownloadFix and InstallFix as WebSphere Automation uses multiple IDs for various Ansible tasks. This would help in improved security posture, reduced downtime, increased operational accountability and better compliance.

Install Directory Ownership change for WebSphere server install directories after installation

For Traditional WebSphere Application Server, when the IM owner of WebSphere Server is root and the IM Install Directory owner is non-root user, there is a Privilege Mismatch. So, if the installation is done by root, the install directory ownership changes to root. This causes server restart failure. We have added a task to change that Install Directory ownership back to non-root user so that server restarts successfully.

Multiple installations are triggered by the same user with shared directory

For Traditional WebSphere Application Server servers, multiple installations are triggered by the same user with shared directory. When the same user tries two installations in different servers with shared directories, we added a resolution to create a unique directory every time it tries to create a directory and do a smooth clean up of those directories without affecting each other’s installations.

Multiple security vulnerabilities have been resolved.

These updates are more than just enhancement, they are a reflection of our continued commitment to delivering a secure, stable, and high-performing experience for every user.

 Curious about what's new or how these improvements can elevate your team's productivity? Lets take a closer look.