Updating SAP BusinessObjects BI4.0 or SAP BusinessObjects BI4.1 into SAP BusinessObjects BI4.2 requires a new License Key
As of SAP BusinessObjects BI 4.2 SP2, you will need a new license key to finish up the upgrade of any earlier version of BI4.x. The new update installer will inform you with this during the initial steps of the installer as well at finalization of this installation. This document provides you the background of the new license key requirement, the process to request a new license key and the process to implement the new key.
- Updating SAP BusinessObjects BI4.0 or SAP BusinessObjects BI4.1 into SAP BusinessObjects BI4.2 requires a new License Key
IMPORTANT INFO !
We regret to inform that a minor issue has been sneaked into the BI4.2 Platform SP2 build (build 1975). If you plan to use the Web Intelligence Applet for the languages:
- fi (Finnish)
- ro (Romanian)
- sv (Swedish)
- sk (Slovak)
- zh_TW (Traditional Chinese)
please read http://service.sap.com/sap/support/notes/2294665
Why is a new License Key required?
After the release of BI4.1 we learned that support messages often have been address to the wrong versions of BI4.x, leading to additional lead time before a support message reached the correct team. As the available components for selection at the creation of a support message is depending on the recorded version in the system (by the customer/partner), we can better streamline our support teams in supporting your messages slightly faster.
The new license key requires to update the system information as recorded in SAP support system, enabling both SAP and customers to gain from a improved support model.
When is a new License Key required
As not all products from the SAP BusinessObjects portfolio are impacted with the license key change, it may be confusing when a new license key is required. The following products from the SAP BusinessObjects portfolio do need a new license key when updating into BI4.2 SP02 or higher.
- SAP BusinessObjects BI Platform 4.0
- SAP BusinessObjects BI Platform 4.1
- SAP BusinessObjects BI Platform 4.2 -> SP00 (RTM release) and SP1 (only applicable for customers that have been joining the Early Adopters Program)
- SAP BusinessObjects Information Platform Services 4.0
- SAP BusinessObjects Information Platform Services 4.1
- SAP Crystal Server 2011
- SAP Crystal Server 2013
- SAP Crystal Server 2016 -> SP00 (RTM release) and SP01 (only applicable for customers that have been joining the Early Adopters Program)
- SAP BusinessObjects BI, EDGE Edition 4.0
- SAP BusinessObjects BI, EDGE Edition 4.1
- SAP BusinessObjects BI, EDGE Edition 4.2
- SAP Data Services 4.0
- SAP Data Services 4.1
- SAP Data Services 4.2
- SAP Information Steward 4.0
- SAP Information Steward 4.1
- SAP Information Steward 4.2
- SAP BusinessObjects Live Office 4.0 (Client Install)
- SAP BusinessObjects Live Office 4.1 (Client Install)
- SAP BusinessObjects Live Office 4.2 (Client Install) -> SP00 (RTM release) and SP01 (only applicable for customers that have been joining the Early Adopters Program)
- Lumira Server for Teams 1.29 or earlier
The new license key requirement will only be needed the first time that you install any version of BI4.2 SP2 or higher against a version listed above. If you plan to update a BI4.2 SP2+ deployment with a higher Support Pack in the future, you will not need to update your license key anymore.
If you are running a greenfield installation, you will have the normal installation screen requesting a license key during the install. If you had any BI4.x version before, this also would require the request of a new license key.
Is there a new license/contract required?
NO, there is no new license or contract required to request the new BI4.2 License Key. Any customer/partner with a valid (maintenance) contract has the ability to request a new key. You can request the exact same license key as you have been using in your existing BI4.0 / BI4.1 deployment without the need to renegotiate your existing contract.
How to request a new License Key
You can request your new BI4.2 License Key via the normal process available on the SAP Support Portal. A step by step guide on how to request a new license key is documented in https://support.sap.com/content/dam/library/SAP%20Support%20Portal/keys-systems-installations/keys/new-request-license-k…
SAP strongly recommend to record all of your SAP products as deployed accordingly. If you have multiple systems like Development, Test, Quality and Prod it would be recommended to record each system. By this you would enable SAP to better support you in case of an issue.
BI4.2 SP2+ Update Install Process
The installation of the BI4.2 SP2 Update is no different from any previous patch, with the the only difference of an additional screen.
During the initial phase of the update installer you will be prompted with the following screen
You have to select the tick box before you are able to continue to the next step of the update installer.
Once the update installer is completed and showing the final screen it will provide the following post installation instruction:
Note: the post installation instruction screen is dynamic and can contain multiple instructions.
After finishing the update you need to update your license key within the Central Management Console. If you have a clustered system, you need to install the BI4.2 SP2 Update on all systems before proceeding with the next step.
Example screenshot when upgrading a BI4.1 into BI4.2 SP2 (or higher), containing multiple post installation instructions:
Entering your new BI4.2 License Key
Once all the servers in your BI Deployment have been updated to BI4.2 SP2, you have to enter the Central Management Console of your deployment.
after entering the Central Management Console of your updated BI4.2 deployment and navigate to -> Servers -> All Servers, you will notice that multiple servers are disabled and cannot be enabled. This is due to an invalid license key.
To enable your servers, you will have to enter your new 4.2 License Key. For this, navigate to the "License Key" tab of the Central Management Console.
You will be informed that the existing License Key(s) are invalid
It is important that you delete your old License Key(s) before entering your new License Key(s). If you enter your 4.2 License Key while the old keys are still in the system you will get an error while adding your license key.
In case you have multiple license keys recorded in your system, you can remove the license keys using a script. The process to remove License Keys by script can be found in http://service.sap.com/sap/support/notes/2276413
In case if you are using Web Application Container Server(WACS) as the only Web Application Server to access CMC or in case of multiple license keys need to be recorded in your system you can add your License Key(s) by script as well. The process to add License Keys by script can be found in http://service.sap.com/sap/support/notes/2281830
After you have entered you 4.2 License Key it is recommended to restart you Server Intelligent Agent (SIA) before enabling you servers. For restarting your SIA, please refer the the administrator guide available via http://help.sap.com/bobip42#section4. After the restart of you Server Intelligent Agent (SIA) you can logon to the Central Management Console (CMC) again and navigate back to "Servers -> All Servers" and enable all servers required for your deployment.
References
Where and How to request License Key
- Link to access the New License Key application : https://support.sap.com/keys-systems-installations/keys.html
- Step by step guide to New License Key application: https://support.sap.com/content/dam/library/SAP%20Support%20Portal/keys-systems-installations/keys/new-request-license-keys-bobj.pdf
Command Line License Key solutions
- Adding License Keys : http://service.sap.com/sap/support/notes/2281830
- Deleting License Keys : http://service.sap.com/sap/support/notes/2276413
What's New in BI4.2
- SAP BusinessObjects BI4.2 What's New L0
- SAP BusinessObjects BI4.2 What's New L1
- SAP BusinessObjects BI4.2 What's New L2
Features by version matrix (update to BI4.2 planned for Q2)