Master Guide

Master GuideSAP® BusinessObjects Explorer – Accelerated Version

ComponentsSAP® BusinessObjects Explorer (blade) 2.0

SAP® BusinessObjects Accelerator (blade) 1.0

SAP® NetWeaver BW Accelerator 7.20

SAP® NetWeaver 7.0 Enhancement Package 1 SPS (Support Package Stack) 5 (including SAP® NetWeaver Business Warehouse)

Target AudienceSAP CustomersSAP Hardware Partners

Document Version 1.2 – 03/31/2010

© Copyright 2010 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any formor for any purpose without the express permission of SAP AG. Theinformation contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors containproprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,System p5, System x, System z, System z10, System z9, z10, z9, iSeries,pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390,OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, PowerArchitecture, POWER6+, POWER6, POWER5+, POWER5, POWER,OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS,HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, ParallelSysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity,Tivoli and Informix are trademarks or registered trademarks of IBMCorporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and othercountries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the OpenGroup.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet,PartnerEdge, ByDesign, SAP Business ByDesign, andother SAP products and services mentioned herein as wellas their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several othercountries all over the world. All other product and servicenames mentioned are the trademarks of their respectivecompanies. Data contained in this document servesinformational purposes only. National productspecifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth inthe express warranty statements accompanying suchproducts and services, if any. Nothing herein should beconstrued as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™.Any code change in these components may causeunpredictable and severe malfunctions and is thereforeexpressively prohibited, as is any decompilation of thesecomponents.

Any Java™ Source Code delivered with this product isonly to be used by SAP’s Support Services and may notbe modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internetaddress:service.sap.com/instguidesIn order to make your document available under this alias,contact Kathrin Luecke. You can find more informationabout Master Guides using the quick link /go/TICM in theCorporate Portal.

Typographic Conventions IconsIcon Meaning

Caution

Example

Note

Recommendation

SyntaxType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

Master Guide SAP BusinessObjects Explorer, Accelerated Version

March 2010 4

History of ChangesThis Master Guide is regularly updated in SAP Service Marketplace at the following places:

- http://service.sap.com/instguides

- http://service.sap.com/bosap-explorer

Make sure you have the latest version of this Master Guide, by checking SAPService Marketplace immediately before starting the installation.

The following table provides an overview of the most important changes that were made inthe latest versions.

Master Guide Version Important Changes

1.0 (November, 17, 2010) Final version for RTC

1.1 (January, 05, 2010) Minor changes

1.2 (March, 31, 2010) Feedback docupedia (minor changes)

http://service.sap.com/instguides

http://service.sap.com/bosap-explorer


March 2010 5

ContentsHISTORY OF CHANGES .................................................................................................................... 4

1 GETTING STARTED ................................................................................................................... 6

1.1 ABOUT THIS DOCUMENT ........................................................................................................... 61.2 RELATED INFORMATION ............................................................................................................ 7

1.2.1 Information for Planning the Deployment ........................................................................... 71.2.2 Further Useful Links .......................................................................................................... 71.2.3 Documentation ................................................................................................................... 81.2.4 Software Downloads ........................................................................................................ 10

1.3 IMPORTANT SAP NOTES .......................................................................................................... 11

2. FEATURES OVERVIEW .......................................................................................................... 12

3. LANDSCAPE, COMPONENTS AND SCENARIOS ................................................................ 13

3.1 ARCHITECTURE ....................................................................................................................... 133.2 REQUIRED SOFTWARE COMPONENTS ........................................................................................ 143.3 PRE-REQUISITES ...................................................................................................................... 16

3.3.1 Platform support .............................................................................................................. 163.3.2 Sizing ............................................................................................................................... 16

3.4 DEPLOYMENT SCENARIOS ........................................................................................................ 173.4.1 Overview .......................................................................................................................... 173.4.2 Deployment Diagram with Data Flows ............................................................................. 20

4. USER SECURITY AND AUTHORIZATIONS......................................................................... 22

4.1 OVERVIEW .............................................................................................................................. 22

5. CHECKLIST FOR INSTALLATION AND INITIAL CONFIGURATION ............................ 24

6. INITIAL CONFIGURATION ................................................................................................... 34

6.1 INITIAL CONFIGURATION OF BW ACCELERATOR ...................................................................... 346.1.1. Activating TREX/BWA extensions .................................................................................... 346.1.2 Activating TREX/BWA Cache ........................................................................................... 346.1.3 Activating Automatic Merge of Delta Index ....................................................................... 36

6.2 INITIAL CONFIGURATION OF BUSINESS WAREHOUSE ................................................................. 376.2.1 Indexing BW Data for SAP BusinessObjects Explorer ....................................................... 376.2.2 Activating BW Objects for SAP BusinessObjects Explorer................................................. 40

6.3 SETTING UP INTEGRATED AUTHENTICATION .............................................................................. 466.3.1 Import roles to SAP BusinessObjects Enterprise ............................................................... 466.3.2. Verify roles and users are imported correctly................................................................... 47

7. CONNECTING EXPLORER, BWA AND BW ......................................................................... 48

7.1 CONNECTING BWA TO BW (OPTIONAL) ................................................................................... 487.2 CONNECTING EXPLORER TO BWA (MANDATORY) .................................................................... 487.3 CONNECTING BWA TO DATA SERVICES ................................................................................... 49

8. VERIFYING YOUR INSTALLATION ..................................................................................... 50


March 2010 6

1 Getting Started1.1 About This DocumentPurposeThis Master Guide is the central starting point for the technical implementation of the SAPBusinessObjects Explorer, accelerated version solution. You can find scenario-specificinformation in this guide.

SAP BusinessObjects Explorer replaces SAP BusinessObjects Polestar.Some product documentation uses the previous name.

SAP NetWeaver Business Intelligence (BI) has been renamed to SAPNetWeaver Business Warehouse (BW). In the context of SAP NetWeaver 7.0the name SAP NetWeaver Business Intelligence (BI) or SAP NetWeaverBusiness Intelligence Accelerator (BIA) means the same as SAP NetWeaverBusiness Warehouse (BW) or SAP NetWeaver Business WarehouseAccelerator (BWA).

Use the Master Guide for the following purposes:- Getting an overview of SAP BusinessObjects Explorer; accelerated version, its

architecture, its software units, and its deployment scenarios- Installing and configuring SAP BusinessObjects Explorer accelerated version,

according to the described deployment scenariosThis Master Guide refers you to the additional required documentation, mainly:

- Configuration documentation for SAP BusinessObjects Explorer accelerated version- SAP NetWeaver documentation on the SAP Help Portal and SAP Service

Marketplace- SAP BusinessObjects documentation on the SAP Help Portal and SAP Service

Marketplace- SAP Notes and SAP BusinessObjects Release Notes for SAP BusinessObjects

Explorer accelerated version

You can find the up-to-date information about the technical implementation ofSAP BusinessObjects Explorer, accelerated version and the latest installationand configuration guides on SAP Service Marketplace athttp://service.sap.com/bosap-explorer.We strongly recommend you use the documents available there. The guidesare regularly updated.



March 2010 7

1.2 Related Information1.2.1 Information for Planning the DeploymentFor additional information about planning your deployment, see the following content on SAPService Marketplace:

Content Location on SAP Service Marketplace

Latest documentation forSAP BusinessObjects Explorer, acceleratedversion


Latest documentation forSAP NetWeaver BW Accelerator

http://service.sap.com/bwa

Latest versions of installation and upgradeguides


SAP BusinessObjects installation anddeployment guides

http://service.sap.com/bosap-instguides

SAP BusinessObjects Support http://service.sap.com/bosap-support

Sizing, calculation of hardware requirements -such as CPU, disk and memory resource - withthe QuickSizer tool

http://service.sap.com/quicksizer

Note that the QuickSizer information for SAPBusinessObjects Explorer, accelerated versionis currently not available, but will be availablesoon. For details about sizing and SAPS, seeSAP Notes 1398242 and 1398303.

Released platforms and technology-relatedtopics such as maintenance strategies andlanguage support

Platform Availability Matrix (PAM)http://service.sap.com/pam

Network security http://service.sap.com/securityguide

High Availability http://service.sap.com/ha

Performance http://service.sap.com/performance

Information about Support Package Stacks,latest software versions and patch levelrequirements

http://service.sap.com/sp-stacks

1.2.2 Further Useful LinksThe following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages http://service.sap.com/messages

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (softwaredownload and ordering of software)

http://service.sap.com/swdc

SAP Online Knowledge Products (OKPs) –role-specific learning maps

http://service.sap.com/rkt







http://service.sap.com/bosap-support


http://service.sap.com/quicksizer

https://service.sap.com/sap/support/notes/1398242


http://service.sap.com/pam

http://service.sap.com/securityguide

http://service.sap.com/securityguide

http://service.sap.com/ha

http://service.sap.com/performance

http://service.sap.com/sp-stacks

http://service.sap.com/messages

http://service.sap.com/notes


http://service.sap.com/rkt


March 2010 8

1.2.3 DocumentationKnowledge CenterDocumentation forSAP BusinessObjectsExplorer, acceleratedversion on SMP and SAPHelp Portal

- Installation/SAP Service Marketplacehttp://service.sap.com/bosap-explorer

- Administration/SAP Help Portalhttp://help.sap.com/bosap-explorer

Documentation for SAPNetWeaverBW Accelerator

- Installation/SAP Service Marketplacehttp://service.sap.com/bwa

- Administration/SAP Community Network (SDN)https://www.sdn.sap.com/irj/sdn/bwa

Feedback to DocumentationAdd your comments oradditional information tothe documentation on theDocupedia wiki

- Docupediahttps://docupedia.sap.com

Documentation for Installation and DeploymentTitle Location

SAP BusinessObjects Explorer (blade) 2.0

SAP BusinessObjectsExplorer (blade) 2.0Installation Guide

https://service.sap.com/bosap-explorer

Planning, Installation, Configuration & SizingSAP BusinessObjects Explorer (blade) 2.0

Installation Guide

SAP NetWeaver Business Warehouse Accelerator

Installation GuideSAP NetWeaverBusiness WarehouseAccelerator 7.20

http://service.sap.com/bwa Installing SAP NetWeaver BW Accelerator 7.20

Note that the BW Accelerator is installed initially bythe SAP BWA hardware partners only.

Update/Upgrade GuideSAP NetWeaverBusiness WarehouseAccelerator 7.20


Update of SAP NetWeaver BW Accelerator 7.20

SAP BusinessObjects Data Services and Index Designer

SAP BusinessObjectsData Services InstallationGuide for Unix


Planning, Installation, Configuration & Sizing Installing SAP BusinessObjects Data ServicesUNIX: Installing SAP BusinessObjects Data

Services XI 3.2 SP1

SAP BusinessObjectsData Services InstallationGuide for Windows


Planning, Installation, Configuration & Sizing Installing SAP BusinessObjects Data Services


http://help.sap.com/bosap-explorer


https://www.sdn.sap.com/irj/sdn/bwa

https://docupedia.sap.com/

https://service.sap.com/

https://websmp105.sap-ag.de/~sapidb/011000358700001318872009E/exp_blade2_install_en.pdf




https://service.sap.com/~sapidb/011000358700001256772009E/BWA_720_Update_smp.pdf


https://service.sap.com/~sapidb/011000358700001240002009E/xi321_ds_install_unix_en.pdf




March 2010 9

Windows: Installing SAP BusinessObjects DataServices XI 3.2 SP1

SAP BusinessObjectsAccelerator Index DesignerGuide

https://help.sap.com/bosap-explorer

Administration SAB BusinessObjects Data ServicesSAP BusinessObjects Accelerator Index Designer

Guide

chapter “Installing the Index Designer”

Additional SAPBusinessObjects DataServices documentation

http://help.sap.com Select the SAP BusinessObjects tab Click All Products

Choose Data Services.

SAP NetWeaver Business Warehouse

Master Guide SAPNetWeaver 7.0

http://service.sap.com/instguidesnw70

Installation Planning Master Guide - SAP NetWeaver 7.0 Enterprise Data Warehousing

Installation Guide SAPEnhancement PackageInstallationUsing SAP EnhancementPackage Installer(SAPehpi)

http://service.sap.com/instguidesnw70

Installation Installation - SAP NetWeaver Systems Enhancement Package Installation Guides Enhancement Package Installation on Existing

SAP Systems Choose your operating system and database

SAP NetWeaver BusinessWarehouse User, Rolesand authorization

User and Role administration in AS ABAP

Creation of BW Analysis Authorizations

https://service.sap.com/~sapidb/011000358700001239982009E/xi321_ds_install_win_en.pdf


https://help.sap.com/

http://help.sap.com/businessobject/product_guides/boexir32SP1/en/exp_acc_index_en.pdf


http://help.sap.com/

https://service.sap.com/instguides

https://service.sap.com/instguides

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/52/671126439b11d1896f0000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/66/019441b8972e7be10000000a1550b0/frameset.htm


March 2010 10

1.2.4 Software DownloadsFor downloading the required software products and components for SAP BusinessObjectsExplorer, accelerated version go to the following navigation paths:

SAP NetWeaver BW Accelerator 7.20https://service.sap.com/swdc Download Support Packages and Patches Support Packages and Patches – Entry by Application Group SAP BusinessObjects portfolio SBOP EXPLORER ACCELERATED VERSION SAP BI ACCELERATOR SAP BW ACCELERATOR 7.2

The BW Accelerator is installed on a preconfigured blade system delivered bySAP hardware partners. Note that the BW Accelerator is installed initially by theSAP BWA hardware partners only.

SAP BusinessObjects Explorer (blade) 2.0https://service.sap.com/swdc

Download Installations and Upgrades Installations and Upgrades – Entry by Application Group SAP BusinessObjects portfolio SBOP EXPLORER ACCELERATED VERSION SBOP EXPLORER (BLADE) SBOP EXPLORER (BLADE) 2.0

SAP BusinessObjects Accelerator (blade) 1.0https://service.sap.com/swdc Download Installations and Upgrades Installations and Upgrades – Entry by Application GroupSAP BusinessObjects portfolio SBOP EXPLORER ACCELERATED VERSION SBOP ACCELERATOR (BLADE) SBOP ACCELERATOR BLADE 1.0

https://service.sap.com/swdc




March 2010 11

1.3 Important SAP NotesYou must read the following SAP Notes before you start the installation. These SAP Notescontain the latest information about the installation, as well as corrections to the installationdocumentation.Make sure that you have the most up-to-date version of each SAP Note, which you can findon SAP Service Marketplace at service.sap.com/notes.

SAP Note Component/Title

SAP BusinessObjects Explorer, accelerated version

1380736 Central Note: SAP BO Explorer, accelerated version

1384526 SAP BusinessObjects Explorer, acceler. version: New Features

1397539 SAP BusinessObjects Explorer, acceler. version: Known Issues

1398242 SIZING SAP BusinessObjects Explorer, accelerated version

1398303 Performance & Reliability SAP BO Explorer, acceler. version

SAP NetWeaver BW Accelerator 7.20

1393505 BWA 7.20: Central Note

1392570 BWA 7.20: Installation

1392526 BWA 7.20: Update

1392524 BWA 7.20: Upgrade/Migration BIA 7.0 to BWA 7.20

1448323 BWA 7.20 Layering Concept

SAP NetWeaver BW 7.0 Enhancement Package 1

1370156 Composite note for BO Explorer accelerated 7.0.1 SP06

Check the current SAP notes for the various parts of SAP Business Objects, acceleratedversion by searching for any of the following CSS/CSN components:BWA/TREX: BC-TRX-BIA, BC-TRX-EXP, BC-TRX-INS, BC-TRX

BW for BWA: BW-BEX-OT-BIA

SBOP Explorer: BOJ-ERQ-EXP-ACC, BOJ-ERQ-EXPSBOP Data Services: BOJ-EIM-DEP, BOJ-EIM-DI

CSS/CSN search also supports */asterisk search, so you can, for example, also searchfor BC-TRX*, BOJ-ERQ-EXP*, BOJ-EIM* or similar and you will get results for allsub-components.













March 2010 12

2. Features OverviewSAP BusinessObjects Explorer, accelerated version brings together intuitive informationsearch and exploration combined with high performance and scalability made possible bySAP NetWeaver Business Warehouse Accelerator.By leveraging SAP NetWeaver BW Accelerator, SAP BusinessObjects Explorer is able toconsume agnostic data sources (using SAP BusinessObjects Data Services to load the datainto BW Accelerator) and SAP NetWeaver BW InfoCubes directly. This means it is notnecessary to build BusinessObjects universes that map to the data sources.SAP BusinessObjects Data Services enables SAP BusinessObjects Explorer, acceleratedversion to load any kind of non-SAP data into the SAP NetWeaver BW Accelerator anddisplay it via the intuitive exploration capabilities of the SAP BusinessObjects Explorer. Inaddition the integration of SAP BusinessObjects Explorer with SAP NetWeaver BW has beenenhanced, so that BW multiproviders, restricted key figures, calculated measures and BWhierarchies are supported.Power users, who understand the structures of the underlying SAP NetWeaver BW datasources (BW InfoCubes), use SAP BusinessObjects Explorer to create Information Spaces,which are sets of contextually-related objects selected directly from an SAP NetWeaver BWAccelerator index enabled for Explorer. New Information Spaces need to be indexed once, inorder to generate the metadata required by the Explorer search engine. The indexingtechnology is provided by Lucene, a third-party search engine integrated into SAPBusinessObjects Explorer. Because BWA indexes are consumed directly, the values visibleto users are always the latest, up-to-date values on the underlying BW InfoCube.Information consumers and analysts search and explore Information Spaces to createpersonal exploration views of the data and share their views with coworkers via bookmarks orby exporting their view as an image or in CSV format.


March 2010 13

3. Landscape, Components andScenarios3.1 ArchitectureThe following figure shows the high-level architecture for SAP BusinessObjects Explorer,accelerated version.

BWAccelerator

BWAccelerator

Explorer, BOE,Integr. for SAP SolutionsExplorer, BOE,

Integr. for SAP Solutions

BusinessWarehouseBusiness

Warehouse

DataServices

DataServices

NW 7.01 SPS05

SAP BusinessObjectsExplorer (blade) 2.0

SAP BusinessObjectsAccelerator (blade) 1.0

IndexDesigner

IndexDesigner

The following figure shows a schematic system landscape and its data flow (for a moredetailed figure, see section “3.4.2 Deployment Diagram with Data Flows”):


March 2010 14

3.2 Required Software Components

The SAP BusinessObjects Explorer, accelerated version consists of multiplesoftware packages. Each software package consists of several softwarecomponents. The names of a software package may indicate that all of thesoftware components it includes are installed on a Linux blade (For exampleSAP BusinessObjects Explorer (blade) 2.0). However some of its componentsrequire installation on a separate Windows host (for example, SAPBusinessObjects Client Tools XI 3.1). Details of the required installationplatform for each software component are provided in this guide.

This list gives you a short overview of the software components of SAP BusinessObjectsExplorer, accelerated version:

SAP BusinessObjects Explorer (blade) 2.0SAP BusinessObjects Explorer XI 3.2 (Linux)SAP BusinessObjects Enterprise XI 3.1 SP (Service Pack) 2 (Linux)SAP BusinessObjects Client Tools XI 3.1 SP (Service Pack) 2 (Windows)SAP BusinessObjects SAP Integration XI 3.1 SP (Service Pack) 2 for SAP Solutions(Linux)

SAP BusinessObjects Accelerator (blade) 1.0SAP BusinessObjects Data Services XI 3.2 SP (Service Pack) 1 (Linux)SAP BusinessObjects Data Services Designer (Windows)SAP BusinessObjects Accelerator index designer (Windows)

SAP NetWeaver Business Warehouse Accelerator 7.20 Revision 1(Linux)

[Optional] SAP NetWeaver 7.0 Enhancement Package 1 SPS (Support PackageStack) 5 (including SAP NetWeaver Business Warehouse)

SAP BusinessObjects Explorer, accelerated version contains the following softwarecomponents (detailed overview):

SAP BusinessObjects Explorer (blade) 2.0You need to install SAP BusinessObjects Explorer blade edition 2.0, which containsthe following components:- SAP BusinessObjects Explorer XI 3.2 – the Explorer web tier and backend

server components and the SAP NetWeaver BW Accelerator driver for SAPBusinessObjects Explorer.

- SAP BusinessObjects Enterprise XI 3.1 SP (Service Pack) 2 – the SAPBusinessObjects platform including the Central Management Server (CMS) andthe Central Management Console (CMC), necessary to implement administrationtasks, plus MySQL database for the CMS repository and a Web ApplicationServer to deploy the SAP BusinessObjects Enterprise and SAP BusinessObjectsExplorer Web Applications.

- SAP BusinessObjects Client Tools XI 3.1 SP (Service Pack) 2- SAP BusinessObjects Integration, version for SAP Solutions XI 3.1 SP

(Service Pack) 2 – integration software to enable SAP authentication and importexisting SAP NetWeaver user accounts into the SAP BusinessObjects EnterpriseCMS.


March 2010 15

A software load balancer is required outside of the Explorer blade, to providesecurity. For full details, refer to section 4. User Security and Authorizationslater in this document.

- Supported operating systemFor information about supported operating systems and Web application servers, seethe SAP BusinessObjects Explorer XI 3.1 SP1 for Linux Supported Platformsdocument in the Articles section on the SAP Community Network at:http://www.sdn.sap.com/irj/boc/articles

SAP BusinessObjects Accelerator (blade) 1.0- SAP BusinessObjects Data Services XI 3.2 SP (Service Pack) 1- SAP BusinessObjects Accelerator index designer

Software version:You need to install SAP BusinessObjects Data Services XI 3.2 with the SAPBusinessObjects Accelerator index designer, which contains the followingcomponents:- SAP BusinessObjects Data Services client components (Windows) are the

following:o SAP BusinessObjects Data Services Designer is the graphical user

interface that is used to design and test all jobs and from which the IndexDesigner is launched.

o The Repository Manager is used to create and manage all types of SAPBusinessObjects Data Services repositories.

o SAP BusinessObjects Accelerator index designer is the graphical userinterface which allows you to model SAP NetWeaver BW Acceleratorindexes on top of any data source and stores the resulting target schemaas a BWA data store in the SAP BusinessObjects Data Servicesrepository.

- SAP BusinessObjects Data Services server components – includes the JobServer, Access Server, Technology Interfaces, and Metadata Integrator(Windows only) which allow you to execute batch jobs, provide real-time access,and collect metadata from the SAP BusinessObjects Enterprise system forimpact and lineage analysis.

- SAP BusinessObjects Data Services web tier components – includes theManagement Console to manage the SAP BusinessObjects Data Servicesenvironment.

- Supported operating system: For information about supported operating systems,see the Product Availability Matrix (PAM) on http://service.sap.com/pam

SAP NetWeaver Business Warehouse Accelerator 7.20- Software version:

You need to install BW Accelerator 7.2 Revision 0 or higher.- Supported operating system: SUSE Linux SLES 10, latest SP

The BW Accelerator is a new approach for boosting SAP NetWeaver BWperformance based on specially configured hardware. Customers adopting the BWAccelerator can expect improvements in query performance through sophisticated in-memory data compression and horizontal and vertical data partitioning, with nearzero administrative overhead.

SAP NetWeaver Business Warehouse- Software version:

http://www.sdn.sap.com/irj/boc/articles



March 2010 16

You need to update SAP NetWeaver BW to SAP NetWeaver 7.0 EnhancementPackage 1 SPS (Support Package Stack) 5 (including SAP NetWeaver BusinessWarehouse)

- Supported Operating System:SAP NetWeaver Business Warehouse is a pre-requisite for the SAP BusinessObjectsExplorer, accelerated version solution. Because SAP NetWeaver BW is installed on atraditional machine, it is not restricted to being on the same operating system as theSAP BusinessObjects Explorer and SAP NetWeaver BW Accelerator softwarecomponents (BWA is installed on blades). For the most up-to-date information aboutplatform and operating system availability for SAP NetWeaver software components,see the Product Availability Matrix (PAM) on SAP Service Marketplace at:http://service.sap.com/pam

3.3 Pre-Requisites3.3.1 Platform supportThe SAP BusinessObjects Explorer, accelerated version is supported for deployment on theplatforms supported for SAP NetWeaver and SAP BusinessObjects Explorer blade edition.

SAP NetWeaver Business Warehouse and BW AcceleratorFor information about platform and operating system availability for SAP NetWeaversoftware components, see the Product Availability Matrix (PAM) on SAP ServiceMarketplace at: http://service.sap.com/pamSAP BusinessObjects Explorer blade edition 2.0For information about supported operating systems, see the Product Availability Matrix(PAM) on SAP Service Marketplace at: http://service.sap.com/pamSAP BusinessObjects Data ServicesFor information about supported operating systems, see the Product Availability Matrix(PAM) on SAP Service Marketplace at: http://service.sap.com/pam

3.3.2 SizingYour SAP NetWeaver BW Accelerator landscape is usually sized for a BW scenario.Using the BW Accelerator as part of the SAP BusinessObjects Explorer, acceleratedversion solution creates additional load for the BW Accelerator and a resizing of yourlandscape is required. You need to contact your SAP hardware partner for sizing.For details about sizing and SAPS information, see athttp://service.sap.com/bosap-explorer

https://service.sap.com/pam






March 2010 17

3.4 Deployment Scenarios3.4.1 OverviewThe picture below describes a typical deployment scenario for SAP BusinessObjectsExplorer, accelerated version including SAP NetWeaver BW deployment.


March 2010 18

For security and performance reasons the deployment landscape is structured in componentsthat are installed inside of a blade landscape and components installed outside of it.

The SAP BusinessObjects Explorer, accelerated version consists of multiplesoftware packages. Each software package consists of several softwarecomponents. The names of a software package may indicate that all of thesoftware components it includes are installed on a Linux blade (For exampleSAP BusinessObjects Explorer (blade) 2.0). However some of its componentsrequire installation on a separate Windows host (for example, SAPBusinessObjects Client Tools XI 3.1). Details of the required installationplatform for each software component are provided in this guide.

The following components are installed inside of the blade landscape:- SBOP Explorer (SAP BusinessObjects Explorer XI 3.2)- SBOP Enterprise (SAP BusinessObjects Enterprise XI 3.1 SP2)- SBOP Data Services (SAP BusinessObjects Data Services XI 3.2 SP1)- SBOP Data Services Designer (installed via SBOP Data Services installation)- Index Designer (SAP BusinessObjects Accelerator index designer; installed via BO

Data Services installation)- BW Accelerator (SAP NetWeaver BW Accelerator 7.20)

The following components are installed outside of the blade landscape:- AS source Database: SAP NetWeaver BW (SAP NetWeaver 7.0 Enhancement

Package 1 SPS (Support Package Stack) 5 (including SAP NetWeaver BusinessWarehouse Warehouse)

- Web Tier (SAP BusinessObjects Web Tier)- Loadbalancer (SAP BusinessObjects Loadbalancer)- Any Source Database

All components are connected via the following network segments:- Ethernet Network segment 1 (Corporate Network)- Ethernet/Network segment 2- Ethernet/Network segment 3

Ethernet/Network segment 4

Network Segment 1 (Corporate Network)The network segment 1 represents the productive intranet local area network (LAN) of whichthe productive BW system is part and that can be connected to other servers of the customerlandscape as well. All BW users can access the BW system using the LAN.

Exclusiveness of Network Segment 3 and 4Network segment 3 and 4 must be used exclusively for the connection between the BWsystem, the BusinessObjects system and the BW Accelerator. It is mandatory to have the BWsystem, the BusinessObjects system and the BW Accelerator together in a dedicated subnet.Otherwise, full BWA performance cannot be guaranteed. There has to be a dedicated LANconnection between the BWA system and the BusinessObjects systems as a logical unit onthe one hand and the BW Accelerator and the BW system as a logical unit on the other hand.The network accessibility between each BW application server, the BusinessObjects serverand each BW Accelerator blade must be guaranteed.

Connection Between SAP BW System and BWAYou must use local SAP gateways for the connection between the BW application server andthe BW Accelerator blades. It is mandatory to use local SAP gateways for the connection:


March 2010 19

Using a central gateway is not allowed. This means, that each BW application server must beable to reach each BWA blade using the ping <hostname> command and vice versa.

Connection Between SAP BusinessObjects System and BWAThe SAP BusinessObjects system communicates with BWA via the proprietary TCP/IP-basedTREXNet protocol. On the SAP BusinessObjects system, a BWA driver must be installed toenable communication to take place.

BWA Blades

LocalGateway

LocalGateway

LocalGateway

SAP BusinessObjects System

Explorer Servers(blade edition)

SAP BW System

RFC connections

Server 1 Server 2 Server 3

BWA Driver BWA Driver

Data Services

TREXNet – TCP/IP

Connection Data Services User to SAP BusinessObjects Client ToolsThe Data Services user accesses the Data Services clients like the Data Services Designerand the Accelerator Index Designer, which are installed and running on a Windows hostinside of the blade landscape, via the Remote Desktop Protocol (RDP). The control data flowgoes through the firewall. By this it is guaranteed that the blade landscape can not beintruded by unauthorized access. Using the client tools on a Windows instance via RemoteDesktop Protocol (RDP) and Terminal Service Client is the most secured way and thereforestrongly recommended by SAP.

The firewall is a software firewall (default). If the customer has additionalsecurity requirements, then an optional hardware firewall can be provided bythe hardware partner at the customer’s choice.

Network communications- The components outside of the blade landscape are connected via a corporate

network (network segment 1) to the components inside of the blade landscape.- The blade landscape components communicate with each other via the network

segments 2 to 4 as depicted.- The BW Accelerator communicates with the BW system via a specific Ethernet

Network (segment 3) of its own. The BW system is outside of the blade landscape.- The Ethernet network segment 3 connects the BW Accelerator with the

BusinessObjects components inside of the blade landscape. The BusinessObjectscomponents in turn communicate with the components outside of the bladelandscape via Ethernet Network segment 2.

- The communication between Ethernet Network segment 1 and the corporate networkis secured by a firewall.


March 2010 20

3.4.2 Deployment Diagram with Data FlowsThe picture below describes the data flows for SAP BusinessObjects Explorer, acceleratedversion including SAP NetWeaver BW deployment.


March 2010 21

1. CONTROL – Data Flow for Controlling the DataThe Data Services user accesses the Data Services clients like the Data Services Designerand the Accelerator Index Designer, which are installed and running on a Windows hostinside of the blade landscape, via the Remote Desktop Protocol (RDP). The control data flowgoes through the firewall. By this it is guaranteed that the blade landscape can not beintruded by unauthorized access. Using the client tools on a Windows instance via RemoteDesktop Protocol (RDP) and Terminal Service Client is the most secured way and thereforestrongly recommended by SAP.

Currently only one single user is allowed to access at the same time the clienttools per Windows instance due to technical reasons. To bypass thisrestriction you can enable parallel usage of the client tools for several usersby running several virtual Windows instances on VMware. Another way couldbe to install the client tools outside of blade landscape and network, forexample, locally on a Windows machine. In that case the customer has toopen the firewall for the IP of the external client machine and has to take careof the security of this client machine.

2. LOAD – Data Flow for Loading the DataThe source data is extracted and loaded from the source data base and loaded through thefirewall via the Data Services server into the BW Accelerator for processing. BY means of theSBOP Data Services Designer and SBOP Index Designer the necessary modeling andtransformation processes are done.

3. EXPLORE – Dataflow for Exploring the DataThe processed data is then transferred back via the SBOP Explorer and SBOP Enterpriseserver through the firewall to be explored by the SBO Explorer UI. A load balancer distributesthe work load caused by multiple users to several web tier servers.


March 2010 22

4. User Security and Authorizations4.1 OverviewSAP BusinessObjects Explorer users are managed by the SAP BusinessObjects EnterpriseCMS. If users require the ability to use their SAP BW NetWeaver profiles to log into SAPBusinessObjects Explorer, it is necessary to import existing SAP NetWeaver BW user profilesinto the CMS. In addition, it is necessary to allocate the appropriate user authorization toeach BWA index enabled for consumption by SAP BusinessObjects Explorer. Explorer endusers can only to view Information Spaces built on the BWA indexes to which they haverights. You need to set up authorization for your users correctly at the following three levels:

The SAP BW InfoCubes on which you want to generate Explorer-enabled BWAccelerator indexes

The Explorer-enabled BW Accelerator indexes you generate for consumption by SAPBusinessObjects Explorer

The SAP BusinessObjects Enterprise folders in which you store the ExplorerInformation Spaces built on those BWA indexes

Knowledge of SAP NetWeaver BW authorization and SAP BusinessObjectsEnterprise security concepts is a pre-requisite to setting up authorization forSAP BusinessObjects Explorer Accelerated. For more information, see theSAP library documentation on SAP Help Portal User and Role administrationin AS ABAP, Creation of BW Analysis Authorizations and the SAPBusinessObjects Enterprise XI 3.1 Administrator’s Guide athttp://help.sap.com/bosap-explorer Administration

The following list provides an overview of the applications you need to use to provide userswith authorization at each of these levels and directs you to the relevant documentation.

Restrict/Authorize

Goals Software/Tool

SAP BWInfoCubes

Define and create user and authorization inSAP NetWeaver BW (using transactionSU01)Set authorizations at the data slice level(using the transaction RSECADMIN)For details, see 5. Checklist for Installationand Initial Configuration section d)Implement SAP NetWeaver BW Goal 3:Define user security levels for SAPNetWeaver BW.

– SAP NetWeaver BWServer User Administration(Transaction SU01)– SAP NetWeaver BWServer Data Slices AnalysisAuthorizations (TransactionRSECADMIN)

Explorer-enabled BWAcceleratorindexes

When creating the BWA indexes, assignusers the analysis authorizations that werecreated in the transaction RSECADMIN.For details, see 5. Checklist for Installationand Initial Configuration section d)Implement SAP NetWeaver BW Goal 6:Make BWA indexes and user authorizationsavailable to Explorer

BI Accelerator IndexMaintenance Wizard forBusinessObjects Explorer.(transaction RSDDV orRSDDTPS)




http://help.sap.com/bosap-explorer


March 2010 23

BusinessObjectsEnterprisefolders on theCMC

– Create specific folders to storeInformation Spaces– Grant specific user groups access rightsto these foldersFor details, see 5. Checklist for Installationand Initial Configuration section b)Implement SAP BusinessObjects Explorer(blade) 2.0 Goal 5: Enable users to viewand/or create/explore Explorer InformationSpaces.

Business ObjectsEnterprise CentralManagement Console(CMC)


March 2010 24

5. Checklist for Installation and InitialConfigurationThe following checklist describes the deployment and initial configuration tasks you need toperform so that the SAP BusinessObjects Explorer application works on top of SAPNetWeaver BW Accelerator indexes. The checklist is structured according to theimplementation sequence:

a) Implement SAP NetWeaver BW Acceleratorb) Implement SAP BusinessObjects Explorer (blade) 2.0c) Implement SAP BusinessObjects Data Servicesd) Implement SAP NetWeaver BW (optional)

a) Implement SAP NetWeaver BWA

Goal / Documentation Steps Software/Tools

1. Install or Update BWA

Documentation:For more information about theupdate process,see the BWA KnowledgeCenter on SAP ServiceMarketplacehttp://service.sap.com/bwa BWA 7.20 UpdateGuide (SAP ServiceMarketplace (SMP) userrequired)

Note that as a hardwareappliance the BWA can onlybe installed initially by yourSAP hardware partners. SAPhardware partner (IBM,Hewlett Packard, Fujitsu, orSun Microsystems) offer theBW Accelerator hardware as apackaged appliance and installand deliver a preconfiguredblade system to the customersite.Contact your SAP hardwarepartner for planning, sizing,and setting up the BWAccelerator for SAPBusinessObjects Explorer,accelerated version.

SAP NetWeaverBWA

2. Enable the TREX index serverfor Explorer and maximize theTREX query processing speedand performance.Documentation:For details, see section6.1 Initial Configuration of BWAccelerator

Activate the TREX extensionsand the TREX cache.Those settings need to beactivated, to guarantee that theBWA works as intended.

SAP NetWeaverBWA

Stand-alone TREXadmin tool(Python)

http://service.sap.com/%0Bbwa

http://service.sap.com/%0Bbwa




March 2010 25

3. Activate Dimension FunctionIndex (DFI).Documentation:For details, see SAP Note1133742 BIA 7.00:DimFunction Index (DFI)

If you use SAPBusinessObjects Explorertogether with BWA, SAPstrongly recommends the useof DFI.

SAP NetWeaverBWA

b) Implement SAP BusinessObjects Explorer blade edition


1. Install SAP BusinessObjectsExplorer (blade) 2.0.Documentation:For details, see InstallationGuide SAP BusinessObjectsExplorer (blade) 2.0

Install the following SAPBusinessObjects components:– SAP BusinessObjectsEnterprise XI 3.1 Service Pack 2– SAP BusinessObjectsIntegration, version for SAPSolutions XI 3.1 Service Pack 2– SAP BusinessObjectsExplorer XI 3.1 Service Pack 2

SAPBusinessObjectsExplorer bladeedition

2. Enable/Import BW users toBOE, using the SAPBusinessObjects Integration,SAP Solutions softwareinstalled on the Explorerblade.Documentation:1. For details on changing

the authenticationsettings on Explorer, seechapter11.3.5. Configure theExplorer web applicationfor SAP of theInstallation Guide SAPBusinessObjectsExplorer (blade) 2.0

2. For details on importingSAP users to theBusinessObjectsEnterprise CMS, see:6.3 Setting up integratedauthentication

1. Set up SAP authentication viathe Explorer server.2. Set up SAP authentication onthe BusinessObjects EnterpriseCMC.You have two configurationoptions:a) Import users dynamically withfirst logon (recommended)b) Create new users and groupsmanually using the same namingconvention as in SAPNetWeaver BW.

1. Theauthenticationsettings in thedefault.propertiesfile on theExplorerserver at:<InstallDir>\BusinessObjects\Tomcat55\webapps\polestar\WEB-INF\classes

2. SAP BusinessObjectsEnterpriseCentralManagementConsole(CMC)










March 2010 26

3. Configure the connectionbetween SAPBusinessObjects Explorerand the designated SAPNetWeaver BW Accelerator.Documentation:For details, see section7.2 Connecting Explorer toBWA

Verify that server and port for theSAP NetWeaver BW Acceleratorare entered correctly in theBusinessObjects EnterpriseCMC.

SAPBusinessObjectsEnterprise CMC

Applications Explorer Properties

4. Configure the Explorer webtier and backend servers.Documentation:1. For details on setting the

path for indexes, seechapter 7.3.2 Specifythe index directory of theInstallation Guide SAPBusinessObjectsExplorer (blade) 2.0

2. For details on settingsession timeout, seechapter 7.3.3 Setsession timeout of theInstallation Guide SAPBusinessObjectsExplorer (blade) 2.0

3. For details on tuning foroptimum performance,see the SAPBusinessObjectsExplorer PerformanceWhite Paper attached toSAP Note 1398303.

1. Set indexing path2. Define the session timeout

duration3. Optimize performance:

a. Configure CORBAthreads (number ofconcurrent sessions onweb tier)

b. Configure JVM heapsize (virtual memoryavailable on backendservers)

SAPBusinessObjectsEnterprise CMC

5. Enable users to view and/orcreate and explore SAPBusinessObjects ExplorerInformation SpacesDocumentation:For details on granting useraccess, see chapter UserManagement onhttp://help.sap.com/bosap-explorer/

AdministrationSAP Business

ObjectsExplorer(blade) 2.0Administrator's Guide

Grant users access to theBusinessObjects Enterprisefolders where the InformationSpaces to which they requireaccess are stored.

SAP BusinessObjects EnterpriseCentralManagementConsole (CMC)








http://help.sap.com/%0Bbosap-explorer/


http://help.sap.com/businessobject/product_guides/boexplXI32/en/exp_blade2_admin_en.pdf





March 2010 27

6. Validate your installation.DocumentationFor details, see section8. Verifying your installation

Create Information Spaces andverify that everything workswithin the SAP BusinessObjectsExplorer application.

SAPBusinessObjectsExplorer

c) Implement SAP BusinessObjects Data Services


1. Download the SAPBusinessObjects DataServices software as part ofthe SAP BusinessObjectsAccelerator (blade) 1.0:

SAP BusinessObjects DataServices XI 3.2 SP1 (12.2.1)(SERVER) Linux IA64 (64bit)

SAP BusinessObjects DataServices XI 3.2 SP1 (12.2.1)(CLIENT) Windows (32bit)

SAP BusinessObjectsAccelerator index designerWindows (32 bit)

Downloads are availablefrom the SAP ServiceMarketplace:http://service.sap.com/swdcFor details, see chapter1.2.4 Software Downloads

SAPBusinessObjectsData Services

2. Review the requirements andcomplete the necessarydatabase preparation for theSAP BusinessObjects DataServices repository.Documentation:See Chapter 1: Preparing toInstall” of the SAPBusinessObjects DataServices Installation Guide forUNIX

For a detailed list ofsupported environments andhardware requirements, seethe PlatformAvailability Matrix(PAM) athttp://service.sap.com/pam.










March 2010 28

3. Install the server componentsto the blade configured forSAP BusinessObjects DataServices.

When prompted during theinstallation, take the followingactions:

create the SAPBusinessObjects DataServices repository

configure the Job Server install the Tomcat

application server

Documentation:See Chapter 2: StandardInstallation” of the SAPBusinessObjects DataServices Installation Guide forUNIX

Contact your SAP hardwarepartner for planning, sizing,and setting up the SAPBusinessObjects ExplorerAccelerated solution.


4. Install the client componentsto a Windows machine.

Documentation:See Chapter 2: StandardInstallation of the SAPBusinessObjects DataServices Installation Guide forWindows

Note: Install only the clientcomponents.


5. Install the Index Designerplug-in to the Windowsmachine where the SAPBusinessObjects DataServices client is installed.

1. Start the index designerinstallation by double-clickingthe fileIndexDesigner.msi onthe Windows machine whereSAP BusinessObjects DataServices Designer isinstalled.

2. Follow the instructions onthe installation screens.

The index designer islaunched directly from theData Services Designer UI.There is not a separateprogram icon for indexdesigner.

Index Designer SAP

BusinessObjectsData Services










March 2010 29

6. If you did not create an SAPBusinessObjects DataServices repository during theinstallation process, then youmust create the repository atthis point.

See Chapter 4: AfterInstallation of the SAPBusinessObjects DataServices Installation Guide forWindows or the SAPBusinessObjects DataServices Installation Guide forUNIX.

Create a Data Servicesrepository using either theRepository Manager fromyour Windows server or therepoman executable fromyour Linux server.


7. If you did not create an SAPBusinessObjects DataServices Job Server during theinstallation process, then youmust create a Job Server atthis point.See Chapter 4: AfterInstallation of the SAPBusinessObjects DataServices Installation Guide forUNIX.

Configure a Job Server onyour Linux server.


8 Install and configureconnectivity to agnostic sourcesystems.

In order to extract data fromsource systems, install andconfigure the appropriatedatabase middleware on theSAP BusinessObjects DataServices server.

For a detailed list ofsupported environments andhardware requirements, seethe Products AvailabilityReport (PAR) available in theSAP BusinessObjectsSupport > SupportedPlatforms section of the SAPService Marketplace:http://service.sap.com/bosap-support.

This document includesspecific version and patch-level requirements fordatabases, applications, andoperating systems.

Third-party clientsoftware
















March 2010 30

9 Model any source data bymeans of the Index Designerin SAP BusinessObjects DataServices Designer.For details, seehttp://help.sap.com/bosap-explorer/

AdministrationSAP BusinessObjects

Accelerator IndexDesigner Guide

d) Implement SAP NetWeaver BW (optional)


1. Decide the SAPBusinessObjects Exploreruse cases for SAPNetWeaver BW.Explanation:Check how the data ismodeled in your BW system:In which BW InfoProviderscan the relevant data befound? Are the measures(Explorer terminology)/keyfigures (BW terminology)modeled as basic keyfigures inside of the BW orare they qualified byrestriction through a BWInfoObject?

Search for existingInfoProviders in SAP NetWeaverBW that are relevant for theBusinessObjects Explorer usecases.

If none are available, createnew BW InfoProviders wherenecessary and stage the data.

SAP NetWeaverBW







March 2010 31

2. Check SAP NetWeaver BWcurrency and unitconversionsExplanation:In general units and theirconversions are stored in theBW table T006. WithExplorer on top of BWA, onlysimple conversions arepossible, therefore you haveto check your transactiondata for convertible units.Currencies and theirconversions are stored in theBW tables TCUR*. Checkwhether the values in yourtransaction data can beconverted into the targetcurrency, which you willdefine in step 12 by the BIAIndex Maintenance Wizard.

a) Verify whether or not the usedcurrencies used have aconversion factor.b) Verify whether or not the usedunit is convertible

SAP NetWeaverBW

SAPNetWeaver BW(table TCURR andtransaction data)

SAPNetWeaver BW(table T006 andtransaction data)

3. Define user security levelsfor SAP NetWeaver BW.

Documentation:User and Roleadministration in AS ABAPCreation of BW AnalysisAuthorizations

Create users and authorization inNetWeaver BW for the SAPInfoCubes on which you want togenerate Explorer-enabled BWAccelerator indexes

SAP NetWeaverBW






March 2010 32

4. Update existing SAPNetWeaver BW to SAPNetWeaver 7.0Enhancement Package 1 SP5 incl. SAP NetWeaver BWDocumentation:Installation Guide SAPEnhancement PackageInstallationUsing SAP EnhancementPackage Installer (SAPehpi)For more information, see:http://service.sap.com/instguidesnw70

Installation Installation - SAP

NetWeaver Systems Enhancement

Package InstallationGuides Enhancement

Package Installationon Existing SAPSystems Choose your

operating system anddatabase

SAP NetWeaverBW

5. Enable SAPBusinessObjects Explorerinside SAP NetWeaver BW.Documentation:For details, see sections 6.2.1 Indexing BW Data

for SAPBusinessObjectsExplorer

6.2.2 Activating BWObjects for SAPBusinessObjectsExplorer

Execute reportRSDDTREX_ADMIN_MAINTAINand enterPOLESTAR_SYSTEM = 2.

SAP NetWeaverBW

https://service.sap.com/instguidesnw70

https://service.sap.com/instguidesnw70


March 2010 33

6. Make SAP NetWeaver BWAccelerator indexes anduser authorizations availableto SAP BusinessObjectsExplorerDocumentation:For details, see sections 6.2.1 Indexing BW Data

for SAPBusinessObjectsExplorer

6.2.2 Activating BWObjects for SAPBusinessObjectsExplorer

Create the enhanced version ofthe SAP NetWeaver BWAindexes that you require for therelevant BW InfoProvider.

BI AcceleratorIndex MaintenanceWizard forBusinessObjectsExplorer.(TransactionRSDDV orRSDDTPS)


March 2010 34

6. Initial Configuration6.1 Initial Configuration of BW AcceleratorTo setup the SAP BusinessObjects Explorer Accelerated solution, you need to verify thatspecific parameters are set on BW Accelerator so that Explorer can connect to BWA.

Structure and handling of the BWA *.ini file configuration has been improvedfrom BWA 7.0 to BWA 7.20 Revision 4. For more information, see SAP note1448323 - BWA 7.20 Layering Concept.

6.1.1. Activating TREX/BWA extensionsThe TREX index server contains an interpreter for the Python programming language. Thisfeature allows you to use Python script to enhance, the TREX index server, for example, tochange the behavior of the index server while indexing and while querying. For Explorer aPython extension is used for the queries, where guided navigation calls are triggered by thePython script activated while performing the query. The scripting allows some flexibility inconfiguring the TREX for an application such as Explorer. The extension needs to beswitched on explicitly.

1. Start the TREX admin tool (standalone) on the BWA.You can also use the TREX admin tool (transaction TREXADMIN) in an SAP system(if available).

2. Log on with the user <sapsid>adm.3. Enter the following:

cd <TREX_DIR>

./TREXAdmin.sh

Where <TREX_DIR> = /usr/sap/<SAPSID>/TRX<instance_number>4. In the TREX admin tool navigate to the screen area "Landscape: Ini":

a. Open the configuration file "TREXExtensions.ini" and navigate to the[extensionhandlers] section.

b. If you have not already done so, remove the comment sign # in front of thestring trexxpy so that the entries appears as follows:[extensionhandlers]trexxpy

By removing the comment sign # in front of trexxpy, you activate the TREXextensions.

5. Use the Save to all hosts button to publish the changed TREX configuration file to allblades in your BWA landscape.

6. Restart all TREX index servers.

6.1.2 Activating TREX/BWA CacheWhen you update the BWA or use a BWA 7.0 version before BWA 7.0 Revision 50 you haveto check that settings for TREX/BWA cache are set as follows.

For more information, see SAP note 1331582 BWA 7.00: Cache for SAPBusinessObjects Explorer





March 2010 35

For the TREX/BWA caching, whole queries are cached, and if a new query matches, thecached result is delivered instead of processing the query again. The result is cached in aformat that allows it to be sent directly as a data stream to the client without conversion. Forsome query types, the caching needs to be configured in the caching section of theTREXIndexServer.ini file.



cd <TREX_DIR>

./TREXAdmin.sh

Where <TREX_DIR> = /usr/sap/<SAPSID>/TRX<instance_number>4. In the TREX admin tool (standalone/Python) navigate to the screen area Landscape:

Ini:5. Open the configuration file "TREXIndexServer.ini"6. Check the [trexcache] section.

The section may look like as follows:[trexcache]use_cache = yes#calls_to_cache = olap fuzzy SearchTable SimilarClassesDocumentFeatures SimilarDocuments SimilarTerms ClassFeaturesDocumentLanguage TermIDs ThesaurusTerms

7. Set the parameter use_cache to yes (if not already done).8. Delete the hash sign (#) in front of "calls_to_cache", so that the settings in that

line take effect.9. Delete the entry olap in calls_to_cache.

RESULTThe [trexcache] section should now look like as follows:

[trexcache]use_cache = yescalls_to_cache = fuzzy SearchTable SimilarClassesDocumentFeatures SimilarDocuments SimilarTerms ClassFeaturesDocumentLanguage TermIDs ThesaurusTerms

By setting the parameters for use_cache and calls_to_cache you have activatedthe TREX/BWA cache.




March 2010 36

6.1.3 Activating Automatic Merge of Delta IndexBecause of the in-memory delta index you need to activate the memwatch and the mergedeltas functions in the memwatch section of the TREXIndexServer.ini file. Without thesefunctions activated the delta information would become too large and would lead to highmemory consumption and bad performance.

You only need to check these parameters for an existing installation. For anew installation these parameters are already set as described below.



cd <TREX_DIR>

./TREXAdmin.sh

Where <TREX_DIR> = /usr/sap/<SAPSID>/TRX<instance_number>4. In the TREX admin tool (standalone/Python) navigate to the screen area Landscape:

Ini:5. Open the configuration file "TREXIndexServer.ini"6. Check the [memwatch] section.

The section may look like as follows:[memwatch]use_watch = yes…merge_deltas = nomerge_mem_delta_only = no

7. Set the parameter merge_deltas to yes (if not already done).8. Set the parameter merge_mem_delta_only to yes (if not already done).

RESULTThe [memwatch] section should now look like as follows:

[memwatch]use_watch = yes…merge_deltas = yesmerge_mem_delta_only = yes




March 2010 37

6.2 Initial Configuration of Business Warehouse6.2.1 Indexing BW Data for SAP BusinessObjects ExplorerUseYou can use SAP BusinessObjects Explorer to display data from a SAP NetWeaver BWAccelerator Index (BWA index). If you want to use this to analyze data from BWInfoProviders, you first need to create a version of a BWA index supplemented with specialdata and metadata in the BW system.

Restrictions to hierarchy nodes that are defined in the BW authorizationscannot be displayed in BusinessObjects Explorer. These are thereforeignored when the filter is defined.

If a BWA index already exists for the BW InfoProvider in question, it is replaced by thesupplemented version. You cannot index the data in parallel both with and without theenhancement.The following figure provides an overview of the architecture:

BW Data Manager

TREX JAVA API (für Explorer)

BusinessObjects Explorer

BW Database (Fact Data, MasterData, Text Data)

BW Accelerator Index MaintenanceAssignment of authorizationsand conversion of units and

quantities

BW Accelerator

BW Accelerator Index (view of BWrelevant data)

Explorer Index (view of Explorerrelevant data)

Facts

ConversionIndex

AuthorizationIndex

Master Dataand Texts

External Values

BW Accelerator Engine

PrerequisitesDepending on how you configure your system, you can use either the existing BIA IndexMaintenance Wizard for BusinessObjects Polestar or the enhanced interface for activatingBW objects.To use the latter of these options, check that you have installed SAP Business WarehouseAccelerator 7.2. Then start program RSDDTREX_ADMIN_MAINTAIN In ABAP Editor(transaction SE38) with OBJECT = 'POLESTAR_SYSTEM' and VALUE = '2’.In the maintenance screen for aggregates and BIA indexes (transaction RSDDV), the systemdisplays the function key Polestar for the screen for activating BW objects.


March 2010 38

FeaturesFor the following types of BW InfoProviders, you can create a BWA index that is suitable fordisplaying in SAP BusinessObjects Explorer:

BW Accelerator Index for an InfoCubeScenario: You want to use SAP BusinessObjects Explorer to analyze data from a single BWInfoCube.The basis for these is the BWA index. You can create this on the Aggregate/BI AcceleratorIndex Maintenance: Select InfoCube screen (transaction RSDDV) for the required InfoCube.If an InfoCube is activated for SAP BusinessObjects Explorer, the system adds texts andcharacteristic values to the InfoCube’s data in its external format. If a standard BWA indexalready exists for this InfoCube, the Explorer enhancements can be activated without theBWA index being deleted and rebuilt.

BW Accelerator Index for a MultiProviderScenario: You want to use SAP BusinessObjects Explorer to analyze data for aMultiProvider that is scattered throughout multiple BW InfoProviders.You have the following options:

You can index all InfoProviders in the MultiProvider individually. You can index all MultiProvider data as a snapshot.

Creating a BWA index for a MultiProvider at the level of the InfoProviders(abbreviation: PartProviders) contained in itThis option is only available for certain MultiProviders. A check routine in the BW systemchecks whether the BWA Engine allows this option for the MultiProvider in question. Atpresent, this option can be used by all MultiProviders that only contain InfoCubes and forwhich the problem known as the CMP problem does not occur. This problem occurs when acompounded characteristic is taken account of in the MultiProvider that is not actuallysupplied with data from one of the InfoProviders contained in it.

For more information about the CMP problem see SAP Notes 1009987 and1045683.

If you select the PartProvider option, all InfoProviders are indexed as a standard BWA indexif indexes have not already been created. The system also creates a logical index (ametadata construct in the BWA) that contains the mapping information for a MultiProvider.The queries from SAP BusinessObjects Explorer are performed against this logicalMultiProvider index. For Explorer users, the logical MultiProvider index looks like anInfoCube. It does allow Explorer users to display some of the metadata though.The system only indexes the InfoCubes contained in the MultiProvider in conjunction with theMultiProvider that you want to make available (not as independent InfoProviders therefore).For Explorer users, the InfoCubes contained here are not visible. This means that theycannot create any Information Space for an InfoCube as part of a MultiProvider. If you wantto do this, you have to index and activate the InfoCube yourself.

Creating a BWA index for a snapshot of the MultiProviderThis option is available for nearly all MultiProviders.A MultiProvider snapshot provides a snapshot of the data in the MultiProviders duringindexing scheduled for background processing. If you select the Snapshot option, the systemreads all data in the InfoProviders from the database (or external source) during indexing andcollates it in accordance with how the MultiProvider has been modeled. This data is written to


March 2010 39

a fact index on the BWA server. The fact index is "flat"; meaning that it does not contain anydimensions. All characteristics appear as line items. All master data indexes are created tooand filled with data, provided that indexes do not already exist for the InfoProviders containedin the MultiProvider. The system also creates a logical index (a metadata construct in theBWA) that combines all of this data. The queries from SAP BusinessObjects Explorer areperformed against this logical MultiProvider snapshot index. For Explorer users, the logicalMultiProvider snapshot looks like an InfoCube.

If the data in the InfoProviders contained in the MultiProvider changes, note thatthe system does not update the MultiProvider snapshot index.To find out more about the functions and restrictions of this application, seeSAP Note 1332392.

BW Accelerator Index for a QueryScenario: You want to use SAP BusinessObjects Explorer to analyze InfoProvider data thatfirst needs to be subject to complex processing, meaning that the required functionality in theBWA Engine will not be available.To do this, you can index the snapshot of a query result in the BWA and make it available forSAP BusinessObjects Explorer.

An example of this type of functionality that requires a full OLAP Engine iscomplex key figure conversions, for example of bottles and cans into liters.

Restrictions: A query result cannot be indexed if the query meets one of the followingconditions:

It is an input-ready query. An aggregation level is used as the InfoProvider.(SAP BusinessObjects Explorer does not support planning.)

Input-ready variables are used in the query. (As indexing is carried out in thebackground, no entries can be made.)

The query contains a temporary hierarchy join. (The result cannot be storedin a "flat" index.)

The query contains more than one structure Calculations in the query cannot be performed before aggregation. Local aggregation is used. (The query result in the OLAP Engine is not the

same as the one that the user sees.) The technical name of the query is more than 20 letters long. An index ID is

formed from the query name. There is a technical limitation for this.

To be able to index the snapshot of a query result in the BWA, you first need toactivate the query. To do this, call ABAP Editor (transaction SE38) and runprogram RSR_QPROV_CHECK with the name of the query in question. Theprogram checks the query to see if it meets any of the conditions listed above. Ifnone of these conditions apply, the system sets the query property Activated forSAP BusinessObjects Explorer. The query is then visible in the tree of BWobjects for making indexing settings (transaction RSDDTPS). The query resultis given the read mode Query to Read All Data at Once (A), which means thatthe free characteristics are also used in GROUP BY.

During indexing, the system executes the query and stores the result in a flat table. This flattable is indexed in the BWA. The master data tables are also indexed, provided that they donot exist yet. The system creates one logical index only, in order to collate all of this


March 2010 40

information. The queries from SAP BusinessObjects Explorer are performed against thislogical query snapshot index. For Explorer users, the logical query snapshot looks like anInfoCube (or a MultiProvider snapshot index).

More InformationIntegration in Process Chain MaintenanceScenario: Metadata for BW objects that are relevant for SAP BusinessObjects Explorer havechanged. This makes it necessary to update the corresponding BWA index for SAPBusinessObjects Explorer.To update the Explorer settings in a process chain, there is a special process chain type:Other BW Processes Update Explorer Properties of BW Objects.Once you have created a process of this type, you have the following options:1. Select an InfoProvider (object name: InfoProvider name, query name). You can use Input

help for this.2. Define which properties to update:

o Conversion indexes: Updates conversion routineso Hierarchy indexes: Updates hierarchieso Authorization indexes: Updates authorizationso Restricted/calculated key figures: Updates restricted or calculated key figures

Texts are not updated automatically. To re-index texts in a process chain, you can useprogram RSDDTPS_TEXT_RELOAD with input parameter = InfoObject name in the processchains. Since time-dependent texts are only created during initial indexing, this also providesyou with the opportunity to update time-dependent texts.

6.2.2 Activating BW Objects for SAP BusinessObjectsExplorer

UseTo be able to display BW InfoProvider data with SAP BusinessObjects Explorer, you want toactivate the corresponding BW objects for indexing in SAP NetWeaver BW Accelerator.

Procedure1. Enter transaction code RSDDTPS in the input field. The Explorer Object Selection screen

appears. On the left of the screen, there is a list of all BW objects that can be activatedfor display in SAP BusinessObjects Explorer. The objects are displayed under theInfoAreas that they belong to. The ,icon in the Explorer Status column indicates thatthe corresponding object has already been activated.

If you want to activate an InfoCube, you can also select it on the Aggregate/BIAccelerator Index Maintenance: Select InfoCube screen (transaction RSDDV).Choose Polestar. The Display Object screen appears. This contains thefollowing tab pages: Authorizations, Key Figures/Conversions, Restricted/Auth.Key Figures., Hierarchies.

2. Double-click the required BW object to open the tab to define the indexing settings for therelevant InfoProvider on the right of the screen. (You can also do this by choosingChange in the context menu).


March 2010 41

The context menu also contains the following options:Object Overview: This opens a screen containing an overview of all InfoObjects(characteristics and key figures) in the InfoProvider.Object Display in Maintenance UI: This opens a screen for maintainingInfoProviders.

The screen area above the tab pages provides information about the BW InfoProvider:o Object Name: Technical name of the InfoProvidero Descriptiono Object Type: InfoCube, MultiProvider, Queryo Saving Status: saved/not saved. If the status is not saved, the object has been

edited but not saved.o Indication of whether the object is a snapshot (selected)

The context menu also contains the following options:Information (Logs/Status): The Log Selection screen appears. You can determinewhether the system should offer you the option to Save, Activate or Delete thelog from the application log.Global Settings: The Global Settings screen appears. On this screen, you can setthe date format and the language. You have to make these system settings whencalling transaction RSDDTPS for the first time.Last Changed by: The Last Changed by screen opens. The system shows whomade the most recent changes, together with the date and time of the mostrecent change.Delete Hierarchy Indexes: If no hierarchy has been selected for a BW object (seethe information below about the Hierarchy tab page), the hierarchy is notautomatically deleted, as it can still be used by another BW object. Instead, thereis a type of garbage collector for hierarchies. This can be called from the contextmenu. If you select this entry, the system lists all hierarchies that are not beingused by any users. You can then select the ones that you want to delete.

The overview below shows which tab pages the system offers for which InfoProvider.Tab Pages per BW InfoProviderTab Pages InfoCube MultiProvider

(PartProvider/Snapshot)Query (Snapshot)

Authorizations x x x

Key figures/Conversions x x

Restricted/calculated keyfigures

x x

Hierarchies x x

Exclude PartProvider x

Filter filter/data x x

3. Make the settings for indexing. The following selection provides a description of thevarious settings.Tab Pages for InfoCube and MultiProvider PartProvider Indexesa) Authorizations


March 2010 42

Users in SAP BusinessObjects Explorer have filter conditions assigned to them,which the system uses automatically when the user sends a query. This securityconcept is different to the lock concept in a BW system (Filter versus Loc, or Rowlevel versus multidimensional). Both security concepts are optimized for thecorresponding systems.In the SAP BusinessObjects Explorer authorization maintenance transaction, you canassign filter conditions to users. If the data comes from a BW system, you definethese filter conditions in the BW system using a BW analysis authorization object.You can do this either with existing authorization objects, if suitable, or by creatingnew ones to use in SAP BusinessObjects Explorer in the analysis authorizationmaintenance transaction (transaction RSECADMIN). This filter is then usedautomatically every time the data is edited or used in SAP BusinessObjects Explorer.Any number of filters can be described in a BW authorization object.You have to enter at least one user on the Authorizations tab page.Users that you enter in this step can use SAP BusinessObjects Explorer to accessthe BWA index. Users who are not entered in this step do not see any data and donot receive any error messages from the system in SAP BusinessObjects Explorer.Once you have entered a user, you can restrict their access to the data with exactlyone BW analysis authorization, which you can select. A filter is created from theselected authorization. This filter is used in each Explorer query made by this user forthe InfoProvider in question.Rows can be filled in various ways.

Enter the user name and assign the authorization object to it. If it does not have anauthorization object assignment, the user automatically has full rights.Enter the user name and choose Generate Proposal. If the user already has anauthorization object assigned to it, this is used automatically.Copy a list of users, from the notepad for example, and insert this list into the table. Bychoosing Import from File, you can also upload user/authorization pairs, from an Exceltable for example.Enter an SAP BusinessObjects Explorer user group using the pattern $$$_Group ID, forexample $$$_DE, and assign the authorization object. All users in this group automaticallyhave the selected authorization.

To create a special group like this, choose Extras Maintain AuthorizationGroup. The screen opens for editing user groups for SAP BusinessObjectsExplorer (table view maintenance transaction SM30 for tableRSDDTPS_AUTHGRP). Assign the group and user IDs to each other.Example: You create group DE and assign this to 100 user IDs that have thesame authorizations in SAP BusinessObjects Explorer. You can use this usergroup for as many BW objects as you like, as long as they have beenactivated for display in SAP BusinessObjects Explorer, and combine themwith various authorization objects, depending on the BW object in question.

To create a row to enter another user and their authorization, choose .b) Key figures/Conversions

On the Key Figures/Conversion tab page, you can select conversions for keyfigures that depend on units of measure or currencies. Since BusinessObjectsExplorer is always aggregated, but there can be different units and currencies in theBW InfoProvider, you must specify your required target unit or target currency. Youcan only specify one target unit or target currency for each key figure.

Select the target unit for key figures that depend on units. Whether or not a conversion ispossible depends on the units of the InfoProvider, since BusinessObjects Explorer onlysupports simple conversions.


March 2010 43

Possible conversions include centimeter to meter and gram to kilogram.Conversions from piece to pallet, however, are not supported. These keyfigures cannot be evaluated in SAP BusinessObjects Explorer. If you stillneed to perform these complex conversions however, you can have a querysnapshot indexed as a BW InfoProvider instead. The complex conversion isthen performed by the OLAP engine during indexing.

With key figures that depend on currencies, you have to select a currency translation type inaddition to the target currency. The conversion always uses the rate that was valid when theconversion index was created.

Key figures that the target unit or currency cannot be entered for are notconvertible. The system displays a message informing you of this. Theseinclude:Key figures with exception aggregation. These cannot be used in SAPBusinessObjects Explorer, as the dependencies there cannot be depictedfor other characteristics and settings. The system therefore only supports keyfigures with aggregation type Total, Minimum or Maximum.Non-cumulative key figures. The system ignores these in the enhancementfor SAP BusinessObjects Explorer.If conversion is not possible, you need to restrict the corresponding units andcurrencies in SAP BusinessObjects Explorer.The Display setting (for a key figure) to define scaling is ignored in SAPBusinessObjects Explorer. The system always displays the values posted.Values cannot be shifted (shifting by 1,000 for example, where 5.300 isdisplayed as 5,3.

If a key figure is not needed in SAP BusinessObjects Explorer, you have the option as a BWadministrator of defining that this key figure is not displayed in SAP BusinessObjectsExplorer. To do this, set the Hide flag. The key figure will then be indexed but will not bevisible in SAP BusinessObjects Explorer. This simplifies the Information Space Design.

c) Restricted/Calculated Key FiguresOn the Restricted/Calculated Key Figures tab page, the system displays allglobally restricted and calculated key figures that meet the conditions for this BWInfoProvider. In the Use column, select the key figures that you want to be availablein SAP BusinessObjects Explorer.

For example, you could use a key figure like “Amount in 2008 MINUS Amount in2009”.

If you select these key figures, the system does not index their values in the factindex. The BWA Engine analyzes the formula or restriction at query runtime instead.For users in SAP BusinessObjects Explorer, these key figures look like key figureswithout restrictions or formulas, although some metadata can also be displayed in theExplorer.If the definition of the key figure contains variables, the system also has to make thevariable values available at design time. You define these on the Variables forRestricted/Calculated Key Figures screen. The system opens this screenautomatically before saving. You can also call it by choosing Process Variables.Use F4 help to choose the required values.For information about other calculated key figures that cannot be used in SAPBusinessObjects Explorer, choose Display Messages.

d) HierarchiesOn the Hierarchies tab page, the system displays all hierarchies that were definedon InfoObjects belonging to this BW InfoProvider and that meet the condition of being


March 2010 44

non-time dependent. In the Selection column, select the hierarchies that you want tobe available in SAP BusinessObjects Explorer.Since the hierarchies in SAP BW Accelerator are used by various BWA indexes, theIndex Exists column indicates whether the index is already available in SAP BWAccelerator or whether it needs to be created first.

By selecting Delete Hierarchy Indexes from the context menu, you can deletehierarchies that you do not need any more (see above).

Other Functions for MultiProvider Snapshot Indexese) PartProvider

On the PartProvider tab page, the system displays all BW InfoProviders containedin a MultiProvider .In the Exclude column, select the PartProviders that you do not want to be indexed.This allows you to exclude data that you do not intend to use right from the start.

f) FilterOn the Filter tab page, you can create a filter characteristic for the data. Thisallows you to exclude data that you do not intend to use right from the start.You can also use this function to parallelize the processing jobs and thus improve theperformance: For each filter condition, a job is processed in the background. Bydefining independent filter conditions, you can parallelize and speed up data loading.Firstly, select the filter material. You can use Input help for this.Choose Create/Display Filter. The Filter Condition for MultiProvider Index screenappears.On the Select Single Values or Select Intervals screen, define the filter conditionsand choose Apply.

g) ConfiguringBy pressing the Configure, experts can call a function to exclude individualInfoObjects from indexing.

If you exclude a key figure, the system does not read it from the MultiProvider. The key figureis not contained in either the fact index or the logical index. This reduces the amount of data.If you exclude a characteristic, this corresponds to an aggregation using this characteristicwhile reading data during the upload process. The data in the MultiProvider index is then on alower granularity level than in the MultiProvider. If you exclude a characteristic, note that itsnavigation attributes are also excluded.

Configurations of this type modify the structure of the BW object, and settings madebefore can be lost. If an index has already been created, this will be deleted duringconversion.

Functions for Query Snapshot IndexesDefine the authorizations (see the section above on the Authorizations tab page).The tab pages for key figures and hierarchies cannot be used for query snapshotindexes, as the key figures are contained in the query itself, and hierarchies for querysnapshot indexes are not supported.As with the MultiProvider snapshot indexes however, you can define filters (see the Filtersection above) and can reconfigure them (see the Reconfiguring section above). Whenusing query snapshot indexes, you should pay special attention to the following features:

Filter DataOn the Filter Data tab page, you can define additional conditions for data filters.As with MultiProvider snapshot indexes, you can also use filters to divide up theindexing job and have the various parts in parallel. This allows both faster indexing


March 2010 45

and indexing of mass data in query snapshots. The query result cannot be read bypackage. Instead, the data must be read and processed all in one go by the OLAPprocessor. This means that the amount of data that can be indexed is limited inrelation to the capacity of the application server (normally 1-5 million records).. Youcan also divide the data up into blocks and define filter conditions for these blocks.Provided that these blocks do not exceed the limits of the application server, anyamount of data can be read, processed and indexed.Example: You want to index data from 10 years, amounting to over 5 million datarecords. To do this, you create ten data filters, each of which contains the data forone year. The query snapshot can now be indexed.By pressing Configure, you can define the role of the navigation attributes: Theyare either a part of the fact index (and therefore part of the Snapshot too) or areavailable with the master data index using a join (and are therefore subordinate tothe change runs in the BW system).

4. Once you have defined all settings for indexing, remember to save them. Choose .Before saving, the system checks the settings automatically. If this check finds anyerrors, you cannot save. Once the settings are saved, they are stored for indexing in adatabase table (not in the SAP BW Accelerator)

5. To activate the settings for indexing, and to transfer them to the SAP BW Accelerator,choose Activate. (Before activating, the system saves the settings again and carriesout another check before saving).A dialog opens where you can define the start dates for processing jobs in thebackground.

6. Define the start dates.At the chosen time, the settings activation job will be processed in the background(name: BW_TR_RSDDTPS_SETTINGS_ACTIVATE). This job indexes the following:o Settings for the authorizationso The logical index that contains information about restricted, calculated and other key

figures,o Hierarchies that have not been indexed yeto If a BWA index already exists, texts and characteristic values are added to it in

external format. If a BWA index does not exist yet, the system builds one.7. If you want to change settings, make the required changes on the corresponding tab

pages, and choose either Save or Activate. (If the settings were not saved before,SAP BW Accelerator and SAP BusinessObjects Explorer will not recognize them yet.)

If you want to activate changes to settings for a snapshot index that is alreadyactive, you can either delete the data from the index and rebuild it (by selectingthe With Rebuild option) or adapt the settings without rebuilding (by selecting theWithout Rebuild option).

8. If you want to delete settings, choose Delete.

Depending on the object type, you can either just delete the data from the BWAindex (by selecting the Data option) or delete the data together with the indexingsettings (by selecting the Data and Settings option). For MultiProviders with thePartProvider option, you still need to decide which PartProviders to delete. Notethat these might still be being used by other MultiProviders.

9. If metadata in the BW InfoProviders changes, and the BWA index needs to be updated,you can use a special process type to schedule these activities.


March 2010 46

6.3 Setting up integrated authenticationTo make the Explorer login process seamless for BW users, you need to import BW userroles to the SAP BusinessObjects Enterprise CMC.The import procedure consists of the following two steps:

Import a role to BusinessObjects Enterprise Verify roles and users are imported correctly:

6.3.1 Import roles to SAP BusinessObjects EnterpriseTo allow role members to log on to SAP BusinessObjects Explorer with their usual SAPcredentials, you need to import SAP roles into SAP BusinessObjects Enterprise. For eachrole that you import, BusinessObjects Enterprise generates a group. Each group is namedwith the following convention: SystemID~ClientNumber@NameOfRole. You can view thenew groups in the "Users and Groups" management area of the SAP BusinessObjectsEnterprise CMC. You can use these groups to define object security within SAPBusinessObjects Enterprise.For details, see the SAP BusinessObjects Enterprise Administrator's Guide on the SAPBusinessObjects tab at: http://help.sap.com.Consider three main categories of users when configuring SAP BusinessObjects Enterprisefor publishing,

1. Log onto the SAP BusinessObjects Enterprise Central Management Console (CMC).2. Go to the "Authentication" management area of the CMC. To access it from the home

page of the CMC, click Authentication3. Double-click the SAP link.4. On the Options tab, select or clear the Automatically import users check box,

depending on how you want BusinessObjects Enterprise to handle user accountswhen you import roles.

Select the check box to have BusinessObjects Enterprise create a useraccount and a user folder immediately for each member of the role(s) thatyou import When you later add members to a role within SAP,BusinessObjects Enterprise dynamically creates additional user accountsand user folders when new role members first log on to BusinessObjectsEnterprise with valid SAP credentials.

Clear the check box to have BusinessObjects Enterprise import roles withoutimmediately creating user accounts and user folders.SAP BusinessObjects Enterprise dynamically creates new user accounts anduser folders when role members first log on to BusinessObjects Enterprisewith valid SAP credentials. Once user accounts and user folders are created,you can subsequently view them in the "Users and Groups" and "Folders"management areas of the CMC.

5. On the Options tab, select either Concurrent users or Named users depending onyour licenses.

The option you select here does not change the number or type of user licenses thatyou have installed in SAP BusinessObjects Enterprise.You must have the appropriate licenses available on your system.

6. Click Update.7. On the Role import tab, select the appropriate entitlement system from the Logical

system name list.

http://help.sap.com/


March 2010 47

8. In the Available roles area, select the role(s) that you want to import, and then clickAdd.

9. Click Update.

6.3.2. Verify roles and users are imported correctly1. Ensure that you know the user name and password of an SAP user who belongs to

one of the roles that you just mapped to SAP BusinessObjects Enterprise.2. Launch your web browser and go to the following URL:

http://<webserver:<port_number>r>/polestar.Replace <webserver> with the name of the web server and <port_number> with theport number that is set up for SAP BusinessObjects Explorer.

3. From the Authentication Type list, select SAP.4. Type the SAP system and system client that you want to log on to.5. Type the user name and password of a mapped user.6. Click Log On.

You should be logged on to SAP BusinessObjects Explorer as the selected user.


March 2010 48

7. Connecting Explorer, BWA and BW7.1 Connecting BWA to BW (optional)The connection between BWA and the respective BW system will be established during theinitial set up that is done by the SAP hardware partners.

7.2 Connecting Explorer to BWA (mandatory)You connect SAP BusinessObjects Explorer with a designated SAP NetWeaver BWAccelerator via the SAP BusinessObjects Enterprise Central Management Console (CMC)administration page:

1. Stop the Explorer servers.2. Log on to the BusinessObjects Enterprise CMC.3. Navigate to Servers and stop the Explorer servers.4. Navigate to Manage Applications.5. Right-click Polestar and click Properties.

(SAP BusinessObjects Explorer was previously called SAP BusinessObjects Polestarand the previous name is sometimes referenced.)

6. Within Advanced Configuration type the host and port values of the designated BWA.For example:com.businessobjects.datadiscovery.dataprovider.trex.host=<mybwaserver>

com.businessobjects.datadiscovery.dataprovider.trex.port=3<TREX_instance_number>16

Note: This first entry should point to the blade with the first master name server (or atleast to a blade with a master name server).

7. Optional: if you have one or more backup blades in place for your BW Acceleratorlandscape, you can also configure additional connections to those backup blades.For example, to add two backup blades:com.businessobjects.datadiscovery.dataprovider.trex.host1=<bwa_backup_blade1>

com.businessobjects.datadiscovery.dataprovider.trex.port1=3<TREX_instance_number>16

com.businessobjects.datadiscovery.dataprovider.trex.host2=<bwa_backup_blade2>

com.businessobjects.datadiscovery.dataprovider.trex.port2=3<TREX_instance_number>16

8. Click Save and Close.9. Restart the servers.


March 2010 49

7.3 Connecting BWA to Data ServicesWhen initially starting the SAP BusinessObjects Accelerator index designer from the SAPBusinessObjects Data Services Designer, the index designer asks for specific parametersthat are needed for creating a new project, for creating BWA indexes and for connecting DataServices and BW Accelerator.The connection between the Data Services and BW Accelerator will be established during thecreation of BWA indexes by specifying the Data Store Connection URL.

ProcedureYou start the index designer in the following way:1. Start the Data Services Designer:

Choose Start Programs SAP BusinessObjects XI 3.2 SAP BusinessObjects DataServices Data Services Designer

2. From the SAP BusinessObjects Data Services Designer, launch the index designer inone of the following ways:

Creating BWA indexes- Right-click on the datastore you want to use as the source and select Create

Accelerator index.- Select columns within a datastore, then right-click your selection and select

Create Accelerator index. Only the selected columns are used as the source forthe index.

Edit and modify BWA indexes- In the workspace area of the Data Services Designer navigate to Edit Accelerator

Index. The index designer starts in a new window.From the Tools menu, click Accelerator Index Designer.

- The index designer starts empty without creating any project.

Parameters Requested for New Project Screen

Parameters Description

Source:

Datastore: Specifiy the name of the data store, that the index designeris connected to.

Target:

Project/Datastore/Job/…: Specifiy the project name

Data Store ConnectionURL:

Specifiy the URL of the BWA server the Data ServicesDesigner will be connected to.URL syntax:trex://<BWA_hostname>:3<instance>16/ds

Example: trex://ld4711.wdf.sap.corp:34716/dsYou can test the connection between the BWA and the DataServices Designer by choosing the Test button.In case the connection has been established successfully,you will get a “sucessfully connected” message.In case the connection could not be established, you will geta an error message with short description.


March 2010 50

8. Verifying your installationThis section provides the workflows necessary to verify that your SAP BusinessObjectsExplorer Accelerated solution is installed and configured correctly. The following steps arerequired:

Index and BW InfoCube and enable it for SAP BusinessObjects Explorer Start SAP BusinessObjects Explorer and log into the application via your web

browser Create an Information Space on the BW Accelerator index enabled for SAP

BusinessObjects Explorer Index the new Information Space Access the Information Space via the Home tab and explore the data it contains

Index a BW InfoCube for SAP BusinessObjects ExplorerSee 6.2.1 Indexing BW Data for SAP BusinessObjects Explorer.

Start SAP BusinessObjects Explorer and log into the application1. Start the Explorer servers

The Explorer servers (Explorer Master server, Explorer Exploration server, ExplorerIndexing server, and Explorer Search server) can be started, stopped, or restartedwithin the SAP BusinessObjects Enterprise CMC.

2. Launch your web browser, and then log into SAP BusinessObjects Explorer usingSAP authentication.The default URL to the login page is:http://<webserver_name>:<port_number>/polestar

Create an Information Space1. Click Manage Spaces to display the "Manage Spaces" tab.

The available data providers are listed here.2. Select a data provider, then click the Create New button at the top of the3. tab.

The Create Information Space dialog appears.4. Enter an appropriate name for the new Information Space.

This name will appear as the Information Space title to other users.5. Optional: type a description and key words into the appropriate fields.6. To select the folder where you want to save the new Information Space, click the

arrow on the "Folder" drop-down menu and then select the appropriate folder.

The Information Space will only be accessible to users who have access to thatfolder.

7. Optional: select a different regional setting from the default or, to allow the regionalsettings of each end user to be applied to the Information Space dynamically when itis opened, click Use End-user Settings.

8. Click the Objects tab, and then select the objects you want to include into theInformation Space.

9. To verify your data selection has no errors, click Validate.10. A message informs you whether your data selection is OK or whether there are

error(s) that need resolving.11. Click the OK button to close the "Create Information Space" dialog box.


March 2010 51

Index the new Information Space On the Manage Spaces tab, click the Index Now button to the right of the

Information Space title.The index is created.

Access the Information Space and explore the data it contains1. On the Home tab, click the title of the new Information Space.

The Information Space opens.2. To display a specific sub-set of the date, select values from the columns in the upper

pane.The results of your data selection are displayed in the chart in the lower pane.