Downloads

Important considerations when upgrading

1. Before executing the Pulse installer, it is recommended to stop the Pulse services manually.

2. If your Pulse server is v6.6.0 on Windows (Pulse Monitor should be v2.2.0), then you don't need to upgrade the Pulse Monitor. It is recommended to upgrade to the latest Pulse Monitor (now at v2.2.1) for Linux. Significant optimizations have been added to the Pulse Monitor in v6.6.0. If your Pulse version is lower than v6.6.0 then after upgrading the Pulse Application Server, you should upgrade the Pulse Monitor on each TM1 server (Customers on IBM Cloud are not impacted).

3. It is recommended to Back-up Pulse.

4. The conf\server.xml file is overwritten by the Pulse installer by default:

   1. The first time you upgrade to a v8.x version, you have to tick this option. Pulse needs to create a new server.xml file as Tomcat was upgraded.

   2. Once this new file is created, you will be able to find your changes in the conf\server.xml.backup file. Once v8.x installed, you need to copy your changes manually from the backup file to the new server.xml file. Starting with v8.x, the server.xml is slightly different so you can’t use your backup file as is.

5. After upgrading Pulse to v7.0.0 from v6.4.0 or earlier version, a restart of Pulse will be required to include the new dashboards and features of Opensearch. After installing Pulse and Pulse is running, you will need to restart Pulse again to allow Pulse Opensearch to be fully operational.

6. Keep Pulse versions aligned. To avoid compatibility issues with migration packages, when doing a migration between two Pulse Application server, both Pulse servers must run the same version. When upgrading Pulse, you should find a window when no migrations are scheduled.

Summary

Version 8.0.0 is a major release for Pulse, headlined by the new Public Pulse SDK and built-in AI capabilities. Administrators can now manage Pulse programmatically (environments, instances, users, groups, migrations and alerts) using per-user API keys, and interact with Pulse and TM1 through AI assistants via the new, secured Pulse MCP tools and Claude integration. Alongside this, the release delivers 15 further enhancements and 11 fixes spanning security hardening, platform upgrades, migration and the overview and alerting experience.

New Features

Public Pulse SDK

Pulse now offers a public SDK so administrators can manage Pulse programmatically, covering environments, instance settings, users and groups, migrations and alerts. This makes it possible to automate tasks that previously required the UI, such as listing, downloading and executing migration packages across instances.

Access is controlled with API keys that can now be generated per individual user rather than only at the server level, giving finer-grained control over who can call the API.

Pulse Python SDK API

AI in Pulse: MCP tools and Claude integration

Pulse now exposes a secured Model Context Protocol (MCP) endpoint, letting you interact with Pulse through AI assistants. You can ask questions in natural language, such as how your TM1 instances performed over the weekend, or create alerts conversationally. Access is protected by an API-key bearer token configured in Pulse.

Pulse MCP Tools

Improvements to existing features (15)

• Pulse – Overview: Save dashboard and overview state per environment, including search text, page size and page position

• Pulse – Users: Searchable and filterable user and group lists

• Pulse – Alerts: Save As option to duplicate an existing alert

• Pulse – Alerts: No 0 GB disk space alert raised by default

• Pulse – Source Code: Sort by file size and name in Change Tracking

• Pulse – Migration: Optimized creation and deployment of large offline migration packages

• Pulse – Security: Fixed the Log4j Rfc5424Layout log injection vulnerability (CVE-2026-34478) in the application server and OpenSearch

• Pulse – Platform: Upgraded to Tomcat 11

• Pulse – Platform: Upgraded the bundled Java runtime

• Pulse – Platform: Migrated the embedded H2 database to 2.1+

• Pulse – Build: Configured a cloud-based code-signing certificate for signed releases

• Pulse – V12: Removed the deprecated Performance Monitor flag for V12 (PAaaS) instances

• Pulse – Authentication: Updated support for the latest IBM PAW authentication flow

• Pulse – Documentation: Included Bedrock control objects in the technical documentation

• Pulse – Documentation: Updated documentation links

Bug fixes (11)

• Pulse – Overview: Fixed an inconsistent cube view count

• Pulse – Security: Fixed some Pulse URLs being accessible to users not in any security group

• Pulse – Packages: Create and Execute Package wizard now lists only environments with instances the user can access

• Pulse – Model Spotlight: Fixed incomplete information shown for remote TM1 servers

• Pulse – Configuration: Fixed the SMTP configuration test failing

• Pulse – Alert Templates: Server link now updates the service list in Generate Alert Templates

• Pulse – User Reports: Non-admin users with access to limited TM1 instances can now view User Reports

• Pulse – Maintenance: Session rows with a null LogOutTime are now purged

• Pulse – User Analytics: Fixed the User Session Summary tab failing to render

• Pulse – Overview: The "Select All" checkbox state is now retained when navigating away and back

• Pulse – Alerts: Fixed the inconsistency between Alert Type and Template Alert Type