The SAP BusinessObjects BI 2025 release arrives this spring with a message of “New Hopes, New Beginnings.” This update ushers in a new era of data analytics, empowering businesses with even more powerful tools to make informed decisions and drive innovation. With enhanced performance, improved integration capabilities, and a user-centric design, the 2025 release is tailored to meet the evolving needs of modern enterprises. As spring symbolizes growth and renewal, SAP BusinessObjects BI 2025 provides organizations with the fresh capabilities they need to thrive in a data-driven world, bringing a renewed sense of optimism and endless possibilities for the future. Before proceeding further read the welcome blog by Gregory Botticchio: Welcome to SAP BusinessObjects BI 2025.
so, What’s New in BI 2025…
Enhanced Usability
The driving force behind the enhancements in BI Launchpad is a deep empathy for the end-user experience, focusing on boosting productivity and simplifying workflow execution.
There were many enhancements got delivered in the BI Launchpad in support of this thought process… be it “Column Customizations”, “Displaying count on Tiles”, “Right click menu option for duplicating content”, “New Horizon Themes” and many more…. want to know more, read the blog by Hari Chennamadhavuni: Enhancing User Experience with SAP BI Launchpad.
Pin Your KPIs to the Homepage for Easy Monitoring
This new feature allows end users to pin their key performance indicators (KPIs) directly to the homepage or landing page of BI Launchpad as KPI Tiles, providing quick and easy access for ongoing monitoring. By having KPIs readily available, users can track critical metrics at a glance, improving efficiency and decision-making. This feature streamlines workflow and ensures that important data is always within reach, enhancing the overall user experience.
For more details on KPI Tiles.. read the blog by Hari Chennamadhavuni: Enhancing Decision-Making with BI Launchpad KPIs.
Client Credentials grant for OAuth authorizations
As you know we have introduced OAuth authorization support as a new kind of SSO in BI Platform with SAP BusinessObjects BI 4.3 SP02 release. That time it was introduced with only “Authorization Code” grant, which requires end user authorization to access the resource, now with this release we are introducing “Client Credentials” grant flow along with the “Authorization Code” grant type, so that now you can configure your services accounts for the resource access and avoid the end user authorizations.
To avail this new grant type for OAuth Authorizations we have introduced a new field name “Grant Type” for the Authorization Server configuration in CMC application, now you can choose between “Authorization Code” grant or “Client Credentials” grant to configure your Authorization server based on your need.
The default value for this new property “Grant Type” is “Authorization Code”. This also ensures the backward compatibility, for any existing Authorization server configurations in your system.
Test Connection for Authorization Configuration
When the “Authorization Server Configuration” application is introduced in BI 4.3 SP02 release, there is no provision to test the connection in the CMC application page while creating or editing the authorization server configurations…. until this release you need to test the configuration by navigating to “Authorization Tokens” section of User Settings in BI Launchpad. Now with this release we have introduced the “Test Connection” button in “Authorization Server Configuration” page in CMC application.
“Last Login Time” and “Last Login Application”
Now your end users can have track of their sessions… to enhance security and respect the right to know information standard, we are now displaying the “Last Login Time” and “Last Login Application” in the CMC home page. Same way in BI Launchpad as well… this information will be displayed in the “User information” page in User settings section of BI Launchpad.
Trusted Authentication Enhancement
Administrators can now securely configure Trusted Authentication with the newly introduced “Authorized URL Configuration” application under the Applications section in CMC. This enhanced method allows administrators to define trusted URLs for Enterprise Authentication, eliminating the need for manual generation and handling of Shared Secrets. By enabling Trusted Authentication through this streamlined process, administrators can ensure a more secure and efficient setup, enhancing both system integrity and ease of management.
Navigate to Central Management Console (CMC) -> Applications -> Authorized URL ConfigurationEnter a system for each URL that the BI Platform is accessible on (Ensure these URLs are resolvable from the CMS machines)
For each System, select ‘Enable’, give a unique name, and enter in the URL, in the format below:
https://<HOST>:<PORT>/BOE/CMC/TrustedAuthSetTokenServlet
The hostname and port above must be the direct Tomcat (or other supported WAS) URL, accessible via HTTPS from the operating system of any system hosting a CMSIt is only required to have one URL for each Web Application Server in a cluster (/BOE/CMC/TrustedAuthSetTokenServlet will work for all web applications, eg BILP)The HTTPS certificate must be valid for this hostname (via Common Name / CN or Subject Alternative Name / SAN)Hit Save and closeRepeat step 2 for each system (direct web application server URL)
On Update to BI 2025 or BI 4.3 SP04 patch 1000+, Trusted Authentication will continue to work using the global shared secret (no impact to existing workflows). Once the steps below are performed, the previous method of Trusted Authentication will be disabled permanently, and it will only be possible to configure the new method.
Note: It is not recommended to perform these steps until it is confirmed that the new method is working properly.
Log in to Central Management Console (CMC)Navigate to Authentication -> EnterpriseDisable Trusted AuthenticationSaveRestart one Central Management Server
At this point the old Trusted authentication is disabled permanentlyAfter the restart, navigate to CMC -> Authentication -> EnterpriseEnable Trusted Authentication again
This ensures the new method of Trusted authentication is kept enabled
On Fresh installation of BI 2025 or BI 4.3 SP04 patch 1000+, Trusted Authentication can only be configured using the new method.
In the new method of Trusted Authentication, the shared secret file (TrustedPrincipal.conf) is no longer relevant / used in the configuration.
Prerequisites for configuration
HTTPS must be configured on the direct web application server (eg Tomcat) that BI is accessible with, for configuration steps, see your Web Application Server documentation. SSL offloading via Load Balancers is not recommended. It is recommended, but not essential, that CORBA SSL is configured, see:
3026364 – How to configure Corba SSL using a CA-signed certificate for SAP BI 4.2 SP05+
2634052 – How to configure Corba SSL using self-signed certificate for SAP BI 4.2 SP05+
The CMS (Central Management Server) now generates a secure passphrase for each web application server (WAS) and sends the passphrase to the WAS over HTTPS. To allow this to happen, specific steps are needed to configure the URLs that the BI Platform is accessible on.
Known Issues with the new method of Trusted Authentication
It is no longer possible to use Trusted Authentication for the Administrator userWorkflow Assistant will not be functional with the new method of Trusted AuthenticationBW Event Scheduling using biprws Trusted Authentication will not workAny biprws trusted authentication workflows will not workNew Trusted authentication incorrectly requires Enterprise Aliases, raised as a bug:
3578093 – Trusted Authentication not working for non-enterprise users
Note: These issues will occur after a fresh installation + configuration of BI 2025 or BI 4.3 SP04 Patch 1000+, or after disabling the old method of Trusted Authentication. If the old method of Trusted Authentication is still enabled (For example an update scenario where trusted auth was previously configured / working), these issues won’t occur.
For more details:
Please refer the following SAP Knowledge Base Article 3559381 – Configuring Trusted Authentication.
Automated Merge Tool
SAP BusinessObjects BI 2025 installation package contains a very useful tool named “AutomatedMergeTool” inside Tools subfolder of the Collaterals folder. You can use this tool to conveniently take the backup of the BOE web applications configurations before running the Update Installer and after the successful update installation, run this tool again to merge the configuration of the BOE Web applications, like *.properties files, configuration files related to SAML and others. For more details refer the blog by Hari Chennamadhavuni: “Streamlining SAP BusinessObjects Updates with the Automated Merge Tool“.
Upgrade Paths
Now let us see how to come to BI 2025, if you plan to update your existing BI landscape and if you are on BI 4.2.x / BI 4.3.x and the Operating System where the existing landscape is running on is still supported with BI 2025 version, then you can perform the in-place update. Or else you need to build a fresh landscape with BI 2025 by performing the fresh installation and migrate your content from the previous version using any of the Promotion Management Tools of the BI 2025 version.
Platform Support & Removals
BI 2025 is only supported on Windows and Linux operating systems and the Solaris and AIX support is removed.With the GA release, BI 2025 is only supported on Tomcat Application Server, more importantly SAP NetWeaver application server support is removed. And other application servers certification is planned for future.Another important point “Web Application Server Container(WACS)” is no more packaged in BI 2025, this component is removed, if your web applications are deployed on WACS recommendation is to use the default bundled Tomcat server or other supported application servers in future based on your choice. As whatever the functionality is possible to achieve with WACS should be possible also with default bundled Tomcat.And many other components and features are also got removed from the BI 2025 suite of packages…..
For more details: Refer the following SAP Knowledge Base Article 3560025 – Which products and features are removed in SAP BusinessObjects BI platform 2025?. and Product Availability Matrix.
The SAP BusinessObjects BI 2025 release arrives this spring with a message of “New Hopes, New Beginnings.” This update ushers in a new era of data analytics, empowering businesses with even more powerful tools to make informed decisions and drive innovation. With enhanced performance, improved integration capabilities, and a user-centric design, the 2025 release is tailored to meet the evolving needs of modern enterprises. As spring symbolizes growth and renewal, SAP BusinessObjects BI 2025 provides organizations with the fresh capabilities they need to thrive in a data-driven world, bringing a renewed sense of optimism and endless possibilities for the future. Before proceeding further read the welcome blog by Gregory Botticchio: Welcome to SAP BusinessObjects BI 2025.so, What’s New in BI 2025… Enhanced UsabilityThe driving force behind the enhancements in BI Launchpad is a deep empathy for the end-user experience, focusing on boosting productivity and simplifying workflow execution.There were many enhancements got delivered in the BI Launchpad in support of this thought process… be it “Column Customizations”, “Displaying count on Tiles”, “Right click menu option for duplicating content”, “New Horizon Themes” and many more…. want to know more, read the blog by Hari Chennamadhavuni: Enhancing User Experience with SAP BI Launchpad. Pin Your KPIs to the Homepage for Easy MonitoringThis new feature allows end users to pin their key performance indicators (KPIs) directly to the homepage or landing page of BI Launchpad as KPI Tiles, providing quick and easy access for ongoing monitoring. By having KPIs readily available, users can track critical metrics at a glance, improving efficiency and decision-making. This feature streamlines workflow and ensures that important data is always within reach, enhancing the overall user experience.For more details on KPI Tiles.. read the blog by Hari Chennamadhavuni: Enhancing Decision-Making with BI Launchpad KPIs. Client Credentials grant for OAuth authorizationsAs you know we have introduced OAuth authorization support as a new kind of SSO in BI Platform with SAP BusinessObjects BI 4.3 SP02 release. That time it was introduced with only “Authorization Code” grant, which requires end user authorization to access the resource, now with this release we are introducing “Client Credentials” grant flow along with the “Authorization Code” grant type, so that now you can configure your services accounts for the resource access and avoid the end user authorizations. To avail this new grant type for OAuth Authorizations we have introduced a new field name “Grant Type” for the Authorization Server configuration in CMC application, now you can choose between “Authorization Code” grant or “Client Credentials” grant to configure your Authorization server based on your need.The default value for this new property “Grant Type” is “Authorization Code”. This also ensures the backward compatibility, for any existing Authorization server configurations in your system. Test Connection for Authorization ConfigurationWhen the “Authorization Server Configuration” application is introduced in BI 4.3 SP02 release, there is no provision to test the connection in the CMC application page while creating or editing the authorization server configurations…. until this release you need to test the configuration by navigating to “Authorization Tokens” section of User Settings in BI Launchpad. Now with this release we have introduced the “Test Connection” button in “Authorization Server Configuration” page in CMC application. “Last Login Time” and “Last Login Application”Now your end users can have track of their sessions… to enhance security and respect the right to know information standard, we are now displaying the “Last Login Time” and “Last Login Application” in the CMC home page. Same way in BI Launchpad as well… this information will be displayed in the “User information” page in User settings section of BI Launchpad. Trusted Authentication EnhancementAdministrators can now securely configure Trusted Authentication with the newly introduced “Authorized URL Configuration” application under the Applications section in CMC. This enhanced method allows administrators to define trusted URLs for Enterprise Authentication, eliminating the need for manual generation and handling of Shared Secrets. By enabling Trusted Authentication through this streamlined process, administrators can ensure a more secure and efficient setup, enhancing both system integrity and ease of management.Navigate to Central Management Console (CMC) -> Applications -> Authorized URL ConfigurationEnter a system for each URL that the BI Platform is accessible on (Ensure these URLs are resolvable from the CMS machines)For each System, select ‘Enable’, give a unique name, and enter in the URL, in the format below:https://<HOST>:<PORT>/BOE/CMC/TrustedAuthSetTokenServletThe hostname and port above must be the direct Tomcat (or other supported WAS) URL, accessible via HTTPS from the operating system of any system hosting a CMSIt is only required to have one URL for each Web Application Server in a cluster (/BOE/CMC/TrustedAuthSetTokenServlet will work for all web applications, eg BILP)The HTTPS certificate must be valid for this hostname (via Common Name / CN or Subject Alternative Name / SAN)Hit Save and closeRepeat step 2 for each system (direct web application server URL)On Update to BI 2025 or BI 4.3 SP04 patch 1000+, Trusted Authentication will continue to work using the global shared secret (no impact to existing workflows). Once the steps below are performed, the previous method of Trusted Authentication will be disabled permanently, and it will only be possible to configure the new method.Note: It is not recommended to perform these steps until it is confirmed that the new method is working properly.Log in to Central Management Console (CMC)Navigate to Authentication -> EnterpriseDisable Trusted AuthenticationSaveRestart one Central Management ServerAt this point the old Trusted authentication is disabled permanentlyAfter the restart, navigate to CMC -> Authentication -> EnterpriseEnable Trusted Authentication againThis ensures the new method of Trusted authentication is kept enabledOn Fresh installation of BI 2025 or BI 4.3 SP04 patch 1000+, Trusted Authentication can only be configured using the new method.In the new method of Trusted Authentication, the shared secret file (TrustedPrincipal.conf) is no longer relevant / used in the configuration. Prerequisites for configurationHTTPS must be configured on the direct web application server (eg Tomcat) that BI is accessible with, for configuration steps, see your Web Application Server documentation. SSL offloading via Load Balancers is not recommended. It is recommended, but not essential, that CORBA SSL is configured, see:3026364 – How to configure Corba SSL using a CA-signed certificate for SAP BI 4.2 SP05+2634052 – How to configure Corba SSL using self-signed certificate for SAP BI 4.2 SP05+The CMS (Central Management Server) now generates a secure passphrase for each web application server (WAS) and sends the passphrase to the WAS over HTTPS. To allow this to happen, specific steps are needed to configure the URLs that the BI Platform is accessible on.Known Issues with the new method of Trusted AuthenticationIt is no longer possible to use Trusted Authentication for the Administrator userWorkflow Assistant will not be functional with the new method of Trusted AuthenticationBW Event Scheduling using biprws Trusted Authentication will not workAny biprws trusted authentication workflows will not workNew Trusted authentication incorrectly requires Enterprise Aliases, raised as a bug:3578093 – Trusted Authentication not working for non-enterprise users Note: These issues will occur after a fresh installation + configuration of BI 2025 or BI 4.3 SP04 Patch 1000+, or after disabling the old method of Trusted Authentication. If the old method of Trusted Authentication is still enabled (For example an update scenario where trusted auth was previously configured / working), these issues won’t occur.For more details: Please refer the following SAP Knowledge Base Article 3559381 – Configuring Trusted Authentication. Automated Merge ToolSAP BusinessObjects BI 2025 installation package contains a very useful tool named “AutomatedMergeTool” inside Tools subfolder of the Collaterals folder. You can use this tool to conveniently take the backup of the BOE web applications configurations before running the Update Installer and after the successful update installation, run this tool again to merge the configuration of the BOE Web applications, like *.properties files, configuration files related to SAML and others. For more details refer the blog by Hari Chennamadhavuni: “Streamlining SAP BusinessObjects Updates with the Automated Merge Tool”. Upgrade PathsNow let us see how to come to BI 2025, if you plan to update your existing BI landscape and if you are on BI 4.2.x / BI 4.3.x and the Operating System where the existing landscape is running on is still supported with BI 2025 version, then you can perform the in-place update. Or else you need to build a fresh landscape with BI 2025 by performing the fresh installation and migrate your content from the previous version using any of the Promotion Management Tools of the BI 2025 version. Platform Support & RemovalsBI 2025 is only supported on Windows and Linux operating systems and the Solaris and AIX support is removed.With the GA release, BI 2025 is only supported on Tomcat Application Server, more importantly SAP NetWeaver application server support is removed. And other application servers certification is planned for future.Another important point “Web Application Server Container(WACS)” is no more packaged in BI 2025, this component is removed, if your web applications are deployed on WACS recommendation is to use the default bundled Tomcat server or other supported application servers in future based on your choice. As whatever the functionality is possible to achieve with WACS should be possible also with default bundled Tomcat.And many other components and features are also got removed from the BI 2025 suite of packages….. For more details: Refer the following SAP Knowledge Base Article 3560025 – Which products and features are removed in SAP BusinessObjects BI platform 2025?. and Product Availability Matrix. Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
