Disclaimer: Please be aware that the SAP BusinessObjects BI add-on for SAP Lumira is currently in Ramp-Up and is not generally available (yet). For more information you can follow any updates from Product Manager adrian.westmoreland to get the latest news!
On the 19th of June sharon posted this blog SAP Lumira Server 1.17 and Lumira add-on to BI 4.1 platform pre-requisites where she announced the availability of the SAP BusinessObjects BI add-on for SAP Lumira Ramp-Up program.
This add-on brings your SAP Lumira content into your BI platform deployment so you can enjoy the security, scalability, and ease of use it provides. The SAP Lumira viewer is integrated into the BI platform as a web application, enabling users to have the same experience viewing and exploring stories in BI launchpad as they do in SAP Lumira. The BI platform enforces security on stories and datasets, and allows access, categorization, and sharing in the same manner as other BI platform content, allowing you to seamlessly adopt SAP Lumira within your organization. Datasets that are based on universes can be refreshed, ensuring your stories contain the most up-to-date data. The SAP HANA database stores the data and creates the visualizations which it passes to the BI platform, creating only a minimal load on the BI platform servers.
In part 1 of this blog I'm going to show you how to integrate the Lumira add-on into your BI platform deployment, install the Lumira add-on to your BI platform deployment and configure SAP HANA to allow communication with the BI platform. Part 2 of this blog How to install SAP BusinessObjects BI add-on for SAP Lumira (Part 2) - Ramp-Up! continues with setting up a user in SAP HANA, configure the Lumira add-on services, and finally publish datasets and stories to the BI platform.
More information can be found in the SAP BusinessObjects BI add-on for SAP Lumira Guide were all scenario´s are described.
This picture below from the Guide shows the different components that work together and enable you to integrate SAP Lumira with BI 4:
First stap is to install the Lumira add-on to our BI platform machine which is running on Linux. As we have a simple BI platform deployment (where all components exist on the same machine) all Lumira add-on components will be installed onto that machine. For an overview of the Lumira add-on components please check chapter 2.1 of the SAP BusinessObjects BI add-on for SAP Lumira Guide.
Make sure you that you have the correct versions of the products installed as listed below:
- BI platform 4.1 Support Package 3 or higher
- SAP HANA Support Package 08 Revision 74 or higher
- SAP Lumira Server version 1.17
- SAP HANA user is created with the correct roles: The Lumira add-on service communicates with the SAP HANA database in the context of a technical user.
The technical user must be assigned to the following roles:
- SAP Lumira version 1.17
The software can be found on the following location on SMP:
If no data is displayed please contact your account manager as SAP to ensure you have the correct licenses.
After you unzipped the installation package run setup.sh
On the 'Select Installer Language' screen, select the language that you want to run the installation program in
On the Configure Destination Folder screen, enter the directory where Lumira add-on will be installed.
This product must be installed to the BI platform installation directory (the directory containing modifyOrRemovePrograms.sh ). In this example it's /usr/sap.
On the Check Prerequisites screen, review the results press 'Enter' to continue.
On the Welcome screen, press 'Enter'.
On the License Agreement screen, review the agreement, select I accept the License Agreement, and select Enter.
On the Select Language Packages screen, select any additional languages that you want to install.
On the Existing CMS Deployment Information screen, enter the name, port number, and logon credentials for the existing BI platform CMS.
You can use the Central Management Console (CMC) or the Central Configuration Manager (CCM) to find out the CMS name.
On the Start Installation screen, press 'Enter' to start the installation.
The installation may take some time to complete.
On the confirmation screen, press 'Enter' to complete the installation.
If you logon to the CMC you can see that a new entry has been created under 'Organize' to manage 'Lumira Datasets'.
If you click on 'Servers' you can see that under 'Service Categories' a new server category called 'Lumira Services' is created.
The next step in the installation procedure is the configuration of the SAP Lumira add-on. To configure the Lumira add-on to work with SAP HANA involves the following steps:
Assertion tickets are used by the RESTful web services to communicate securely with SAP HANA. First we need to download the CommonCryptoLib librarylibsapcrypto.so and the SAP Cryptographic tool sapgenpse to generate the assertion tickets.
In the Software Download Center http://service.sap.com/swdc, expand Support Packages and Patches and select Browse our Download Catalog. Choose SAP Cryptographic Software. Expand SAPCRYPTOLIB and choose SAPCRYPTOLIB 5.5.5 (or the latest version). Download the package that matches your SAP HANA machine; for example, Linux on x86_64 64bit. Unpack the .sar. file you downloaded to get the files libsapcrypto.so and sapgenpse.
Perform the following steps to generate the assertion ticket:
1. Log into the SAP HANA machine as root user.
2. Copy the files sapgenpse and libsapcrypto.so to this directory: /usr/sap/<SID>/SYS/global/security/lib/
3. Set execute permissions on these files, for example: chmod 755 sapgenpse chmod 755 libsapcrypto.so
4. Set an environment variable for the /lib/ path, for example: export LD_LIBRARY_PATH=/usr/sap/<SID>/SYS/global/security/lib
5. Switch to your HANA SID user name for the remaining steps in this procedure, for example: su <SID>adm
6. Create the sec directory under /usr/sap/<SID>/HDB<InstanceNum>/<servername> if it does not exist: mkdir /usr/sap/<SID>/HDB00/<servername>/sec
7. Go to the directory that contains the crypto files: cd /usr/sap/<SID>/SYS/global/security/lib/
8. Create the trust stores and signing request using the following certificate specifications:
./sapgenpse gen_pse –p /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/sapsrv.pse –x "" "CN=<servername>,C=CA,S=BC,O=SAP-
AG,OU=HR"
./sapgenpse gen_pse –p /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/sapcli.pse –x "" "CN=<servername>,C=CA,S=BC,O=SAP-
AG,OU=HR"
./sapgenpse gen_pse –a DSA –p /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/saplogonSign.pse –x ""
"CN=<servername>,C=CA,S=BC,O=SAP-AG,OU=HR"
The following files will be created in /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec:
Next step is to configure the SAP HANA services to use the assertion ticket. Please open the SAP HANA studio and select the system.
Launch the 'Administration designer'.
Select the 'Configuration' tab.
Expand 'indexserver.ini' and then expand 'authentication'.
Right-click on 'saplogontickettruststore' and select 'Change'.
Enter the path to saplogonSign.pse: /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/saplogonSign.pse
Expand 'xsengine.ini' and then expand 'authentication'.
If the 'authentication' and 'saplogontickettruststore' sections do not exist right-click on xsengine.ini and select 'Add Section'.
Enter 'authentication' as section name then click 'Next'
Click 'Next' to assign values to the system level.
Enter saplogontickettruststore as the Key and the file location for saplogonSign.pse as the value. Example: /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/saplogonSign.pse7.
Click 'Finish'.
Please stop and start the HANA server.
In part 2 of this blog How to install SAP BusinessObjects BI add-on for SAP Lumira (Part 2) - Ramp-Up! I will continue with setting up a user in SAP HANA, configure the Lumira add-on services, and finally publish datasets and stories to the BI platform.
Thanks for reading my blog so far and please contact me if you have any questions!
With kind regards,
Martijn van Foeken
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
14 | |
10 | |
9 | |
7 | |
5 | |
4 | |
4 | |
4 | |
4 |