So far, we have learned how to use SAP BUSINESSOBJECTS ANALYSIS, EDITION FOR OLAP, but we have not looked at the configuration part of the necessary components. In this field, we will learn more about some of the important deployment topics.
SAP BusinessObjects Analysis, edition for OLAP allows you to export the information to Microsoft Excel, CSV, and PDF, but this can be a very memory consuming activity and therefore you can setup a limit for this feature.
You can configure the property multidimensional.services.export.cells.limit as part of the mdas.properties file.
You can find the mdas.properties file
You can configure the property multidimensional.services.export.cells.limit and simply set the cell limit for the export, for example multidimensional.services.export.cells.limit=50000.
When you are using SAP BusinessObjects Analysis, edition for OLAP in combination with SAP NETWEAVER BW, you can limit the number of entries for the list of values for the BEx Variables, and you can limit the overall data volume retrieved by your workspace. These configurations are done as part of the configuration for the Multi Dimensional Analysis Service (MDAS), which is part of your SAP BusinessObjects BI server environment.
1.Logon to the Central Management Console (CMC) via the menu Start > All Programs > SAP BusinessObjects BI Platform 4 > SAP BusinessObjects BI Platform > SAP BusinessObjects Bi Platform Central Management Console.
2.Select the area Servers (see Figure 6.1).
Figure 6.1 Server – Central Management Console
3. Select the entry Analysis Services.
4. Select the entry for the Adaptive Processing Service which is configured with the Multi Dimensional Analysis Service.
5. Use a right-click and open the Properties.
6. Scroll down to the configuration options for the Multi Dimensional Analysis Service (see Figure 6.2).
Figure 6.2 Multi Dimensional Analysis Service
Here you can configure the limit for the number of cells returned by a BEX QUERY and you can limit the number of entries for the member selector that is used for BEx variables and when creating a filter. After you configured these entries, you will have to restart the service.
Remember that these settings are configured on the server component level, so you will have to repeat these steps when you use more than one Multi Dimensional Analysis Service as part of your overall SAP BusinessObjects BI landscape.
When it comes to setting up your SAP BusinessObjects BI4 system – including SAP BusinessObjects Analysis, edition for OLAP – you will have to start with a sizing exercise for your system to plan for the best possible performance and scalability.
It helps you to ensure the best possible performance and scalability for your BI landscape.
If you would like to enable statistics for SAP BusinessObjects Analysis, edition for OLAP on your SAP NetWeaver BW system, you need to configure the mdas.properties file. In addition to configuring the mdas.properties file, you also need to active the SAP BW statistics for those InfoProviders that you would like to monitor.
To make the necessary changes to the mdas.properties file:
1.Navigate to the following location on your SAP BusinessObjects BI server:
As you learned in the previous chapters and sections, you can configure an OLAP Connection within your SAP BusinessObjects BI4 environment to point to a SAP NetWeaver BW system, to a SAP NetWeaver BW InfoProvider, or to a single BEx query.
Independent on how you configure the OLAP connection, the user will always have the option to see the list of queries in SAP BusinessObjects Analysis, edition for OLAP.
If your OLAP connection points to the SAP NetWeaver BW system, then the user will see the InfoAreas, and InfoProviders and can select a BEx queries from all InfoProviders that the user is allowed to see.
If your OLAP connection points to a SAP NetWeaver BW InfoProvider, then the user will see all BEx queries for the configured InfoProvider.
If your OLAP connection points to a single BEx query, then the user will only see this single BEx query.
To avoid too many OLAP connections in your SAP BusinessObjects BI4 system, here some simple recommendations:
In case you are using naming conventions for the technical names of InfoProviders and BEx queries, you could (perhaps it is already configured) use Authorization object limiting the access to InfoProviders and BEx queries based on the naming conventions. In such a scenario, a single OLAP connection pointing to the SAP NetWeaver BW system and configured with Single Sign On could be all that you need, as each user will only see the InfoProvider and BEx queries based on the technical naming conventions.
In case you do not have such naming conventions in place in SAP NetWeaver BW, you most likely will have to create multiple OLAP connections in your SAP BusinessObjects BI server and assign the necessary rights to your users and user groups.
I am Ruchitha, working as a content writer for MindMajix technologies. My writings focus on the latest technical software, tutorials, and innovations. I am also into research about AI and Neuromarketing. I am a media post-graduate from BCU – Birmingham, UK. Before, my writings focused on business articles on digital marketing and social media. You can connect with me on LinkedIn.