exp31sp1_inst-depl-adm_en

SAP BusinessObjects Explorer Installation, Deploymentand Administration Guide■ SAP BusinessObjects Enterprise XI 3.1

2009-06-06

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects andits logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid Mart™,

Copyright

SAP BusinessObjects Data Insight™, SAP BusinessObjects Desktop Intelligence™,SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist Security™,SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks orregistered trademarks of Business Objects, an SAP company and/or affiliatedcompanies in the United States and/or other countries. SAP® is a registeredtrademark of SAP AG in Germany and/or other countries. All other namesmentioned herein may be trademarks of their respective owners.

2009-06-06

Contents

About this guide...................................................................................7Chapter 1

Overview...............................................................................................9Chapter 2

SAP BusinessObjects Explorer fundamentals for administrators................9Supported data providers..........................................................................10How SAP BusinessObjects Explorer works with SAP BusinessObjectsEnterprise..................................................................................................11The backend servers.................................................................................11The SAP BusinessObjects Explorer user population................................12

Deployment Architecture..................................................................15Chapter 3

Supported platforms..................................................................................15SAP BusinessObjects Explorer deployment scenarios.............................15Deploying SAP BusinessObjects Explorer for improved Information Spaceexploration.................................................................................................17Deploying SAP BusinessObjects Explorer for improved indexing.............18Deploying SAP BusinessObjects Explorer, accelerated version for SAPNetWeaver BW..........................................................................................19Implementing a complex distributed deployment scenario........................20

Installation..........................................................................................23Chapter 4

Installation pre-requisites...........................................................................23Installation package contents....................................................................25Installation procedures...............................................................................26Installing SAP BusinessObjects Explorer on Microsoft Windows..............26

3

Installing SAP BusinessObjects Explorer on IBM AIX...............................30Installing SAP BusinessObjects Explorer on Linux SUSE.........................31Deploying the WAR files manually.............................................................33Post installation configuration ...................................................................36Configuring SAP BusinessObjects Explorer to work with SAP NetWeaverBW Accelerator..........................................................................................37Standardizing font usage across your deployment....................................40WebSphere policy configuration with Java 2 security...............................44Verifying your installation...........................................................................44Logging on.................................................................................................45Logging on with SAP authentication..........................................................46Uninstalling SAP BusinessObjects Explorer on Microsoft Windows.........47Uninstalling SAP BusinessObjects Explorer on UNIX...............................48

Security...............................................................................................51Chapter 5

Reverse proxies.........................................................................................51Firewall port usage for SAP BusinessObjects Explorer.............................51Configuring firewall ports...........................................................................52Authentication methods.............................................................................53Configuring SAP BusinessObjects Explorer for SAP authentication.........54Single Sign On...........................................................................................56Activating Single Sign On..........................................................................56SSO for WinAD authentication using Vintela.............................................59SSO for WinAD using Kerberos.................................................................60SSO for LDAP authentication using SiteMinder........................................61Enabling Trusted Authentication................................................................63Allocating rights to users and groups........................................................66Explorer user rights per user profile..........................................................68

Administration....................................................................................73Chapter 6

Starting and stopping the backend servers...............................................73Customizing the web application server settings.......................................73Explorer Web Application settings.............................................................73Configuring the server settings..................................................................76

4

Contents

Configuring the path for Information Space indexes.................................77Configuring the session timeout period.....................................................79Configuring the request timeout limit.........................................................80Increasing virtual memory on the Explorer servers...................................80Configuring the number of Corba threads.................................................83Configuring the bookmark validity period..................................................85Configuring the workload update setting for load balancing......................86Logging methods.......................................................................................87Configuring the Explorer server log files....................................................88Web application logging.............................................................................90Indexing best practices..............................................................................90

More Information................................................................................93Appendix A

Index 97

5

Contents

6

Contents

About this guide

This guide is for administrators of who wish to deploy SAP BusinessObjectsExplorer and perform administration tasks specific to the application.

End-user information on how to use SAP BusinessObjects Explorer to analyzecorporate business intelligence data is provided in the Help.

Information:For an overview of the information resources dedicated to deployments ofSAP BusinessObjects Explorer with SAP NetWeaver BW Accelerator, referto the Master Guide for SAP BusinessObjects Explorer, accelerated versionfor SAP NetWeaver Business Warehouse at: http://help.sap.com.

7

About this guide

http://help.sap.com

8

About this guide

Overview

SAP BusinessObjects Explorerfundamentals for administrators

SAP BusinessObjects Explorer is an innovative search and explore tool thatallows business users to find and analyze corporate data on the fly, withoutneeding to build reports or format charts. In order to understand how SAPBusinessObjects Explorer consumes your corporate data and systemresources you will need to familiarize yourself with some key terms.

Information Spaces

An Information Space is a collection of objects mapped to data for a specificbusiness operation or activity. SAP BusinessObjects Explorer users type inkey words related to the business question they wish to analyze, in order toretrieve the Information Space(s) that contain the relevant data. Power users,with the Space Creator user profile, create the Information Spaces on top ofcorporate data providers.

Indexing

In order to prepare Information Spaces for consumption by the Explorersearch and charting engines, Information Spaces need to be indexed whenthey are created. Information Space indexes can be run manually orscheduled to run at a time of your choice to manage the load on your systemwith maximum efficiency. When the Indexing process is run, SAPBusinessObjects Explorer generates an index associated to the objectscontained in the Information Space.

Note:Indexing consumes relatively large resources. If your deployment requiresindexes to be run frequently, SAP recommends you deploy multiple Explorerindexing servers on your SAP BusinessObjects Explorer cluster.

9

Overview

Facets

Facets organize the information available within an Information Space. Afacet contains the list of values available for each of the objects included inthe Information Space. For example, a facet called "Vehicle" could includevalues such as "Car", "Bicycle", "Motorbike", "Truck", and so on.

Related Topics• Supported data providers on page 10• Explorer user rights per user profile on page 68• Deploying SAP BusinessObjects Explorer for improved indexing on

page 18

Supported data providersInformation Spaces can leverage data via the following corporate dataproviders:• BusinessObjects universes

Information:Refer to the SAP BusinessObjects Designer's Guide and the Using SAPBW in Universe Designer guide on the SAP BusinessObjects tab at:http://help.sap.com

• NetWeaver Business Warehouse Accelerator indexes enabled for SAPBusinessObjects Explorer

Information:Refer to the SAP NetWeaver Library at: "http://help.sap.com/nw70/".

These data providers can leverage data from operational applications, datawarehouses, Relational DataBase Management Systems (RDBMS) andOnLine Analytical Processing (OLAP) sources.

10

Overview

http://help.sap.com

http://help.sap.com

HowSAPBusinessObjects Explorerworkswith SAP BusinessObjects Enterprise

SAP BusinessObjects Explorer is an add-on to SAP BusinessObjectsEnterprise XI. The servers, Information Spaces and users are managed bythe BusinessObjects Enterprise Central Management Server (CMS) andCentral Management Console (CMC).

Note:You cannot audit the SAP BusinessObjects Explorer servers.

The backend serversWhen you install SAP BusinessObjects Explorer, the following servers areadded to the BusinessObjects Enterprise Central Configuration Manager(CCM) and Central Management Console (CMC):• Explorer Master Server

11

Overview

Manages all of the Explorer servers (that is, the Explorer Indexing Server,Explorer Search Server and Explorer Exploration Server).

• Explorer Indexing Server

Provides and manages the indexing of Information Space data andmetadata.

• Explorer Search Server

Processes search queries and returns search results.

• Explorer Exploration Server

Provides and manages the Information Space exploration and analysiscapabilities including search on data, filtering and aggregation.

Each Explorer server manages its own index.

Related Topics• SAP BusinessObjects Explorer deployment scenarios on page 15

The SAP BusinessObjects Explorer userpopulation

The SAP BusinessObjects Explorer user population includes the followingprofiles:

Space Explorers

Space Explorers make up the majority of the SAP BusinessObjects Exploreruser population. Their interactions with the application consist of searchingfor Information Spaces, navigating and analyzing the data within thoseInformation Spaces and saving Information Spaces to other file formats.These users sometimes export Information Spaces to other applications toanalyze the data further.

Space Creators

Space Creators make up a small percentage of the total SAP BusinessObjectsExplorer user population. They understand the underlying data structures inthe data providers consumed by the application and understand the business

12

Overview

concerns of their Space Explorer collaborators. With this knowledge, SpaceCreators can build Information Spaces that contain contextually related setsof data, and so provide Space Explorers with a complete picture for a givenbusiness query.

Your system requirements and sizing parameters will depend on thepercentage of Space Explorers and Space Creators across your SAPBusinessObjects Explorer deployment.

Administrators

Administrators are responsible for scheduling Information Space indexing,so that the load on the system can be kept to a minimum during peak usagetimes. In addition, administrators can manage SAP BusinessObjects Exploreruser rights and change the server settings.

More Information:For information on sizing your system according to the usage patterns of theusers across your deployment, refer to the SAP BusinessObjects ExplorerXI 3.1 Service Pack 1 Sizing guide available at: http://service.sap.com/bosap-support.

Related Topics• Explorer user rights per user profile on page 68

13

Overview

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


14

Overview

Deployment Architecture

Supported platformsFor detailed information on supported operating systems and web applicationservers, refer to the SAP BusinessObjects Explorer XI 3.1 Service Pack 1Supported Platforms document in the "Articles" section at: SAP CommunityNetwork.

SAPBusinessObjectsExplorer deploymentscenarios

The deployment architecture you choose for SAP BusinessObjects Explorerwill depend on the size of your deployment, the types of actions your usersmost frequently perform when they use the software and the performanceand reliability requirements of your business intelligence infrastructure. TheExplorer servers can be installed on one or several machines with one orseveral instances of a server installed on each machine, to share the workloadof your deployment.

Increasing Performance

You can opt to install SAP BusinessObjects Explorer on the same server asSAP BusinessObjects Enterprise XI or on dedicated machines. InstallingSAP BusinessObjects Explorer on dedicated machines results in betterperformance.

You need to install a Server Intelligence Agent (SIA) on each Explorer servermachine that does not include an SAP BusinessObjects Enterprise XIinstallation. The SIA component is available from the BusinessObjectsEnterprise installer when you deploy the BusinessObjects Enterprise ServerComponents module.

When you deploy a Explorer server on a machine that does not have an SAPBusinessObjects Enterprise XI installation, Explorer connects to another

15


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


BusinessObjects Central Manager Server (CMS) on a separate machine onyour network. You can modify this via the CMC at any time.

Failover

If failover is a key requirement, you can deploy more than one ExplorerMaster Server to manage the other Explorer servers. The Master Serverswork together to maintain the consistency of critical data.

Load balancing

SAP BusinessObjects Explorer supports the clustering of your web applicationserver. Hardware or software load balancers can be used as the entry-pointfor the web application servers to ensure that the processing is evenlydistributed among servers.

Information:For information about load balancing for SAP BusinessObjects Enterprise,refer to the BusinessObjects Enterprise Administrator's Guide XI 3.1 availableon the "SAP BusinessObjects" tab at: http://help.sap.com. For informationabout which hardware load balancers SAP supports for BusinessObjectsEnterprise, refer to the BusinessObjects Explorer XI 3.1 Service Pack 1Supported Platforms document in the "Articles" section at: SAP CommunityNetwork.

Related Topics• Implementing a complex distributed deployment scenario on page 20• Deploying SAP BusinessObjects Explorer for improved indexing on

page 18• Deploying SAP BusinessObjects Explorer for improved Information Spaceexploration on page 17

• Configuring the workload update setting for load balancing on page 86

16


http://help.sap.com



Deploying SAP BusinessObjects Explorerfor improved Information Spaceexploration

If the main activity of your user population is exploration, then it isrecommended you deploy SAP BusinessObjects Explorer in a cluster withadditional Explorer servers to ensure maximum performance when yourusers navigate Information Spaces.

Deploying a high-end machine to the cluster improves the performance andlowers any server restraints.

Related Topics• The SAP BusinessObjects Explorer user population on page 12

17


Deploying SAP BusinessObjects Explorerfor improved indexing

The indexing of Information Spaces is dependent upon:• the number of Explorer servers deployed and how they are deployed• the hardware (CPU, memory, hard disk) used for Explorer servers• the Java Virtual Machine heap

If you wish to improve the performance of indexing, then ensure the following:• Install the primary Explorer Master Server, Explorer Indexing Server,

Explorer Search Server, and Explorer Exploration Server on the machinewhere SAP BusinessObjects Enterprise is installed.

• Install additional Explorer Indexing Servers on separate machines ensuringthat they are directed to the SAP BusinessObjects Enterprise installation.

The indexing load is shared across the indexing servers.

The number of servers required is dependent on the number of usersexpected to use SAP BusinessObjects Explorer. For example, if youexpect a high number of users indexing the large Information Spaces at

18


the same time (an extreme scenario), then an additional server is required.Indexing many Information Spaces has an impact on explorers while theyare exploring. It is recommended you schedule Information Spaces forindexing when there is less activity, such as over night.

Note:It is good practice to install a Explorer Search Server and a ExplorerExploration Server on the additional machines. This allows those machinesto share the load of searching and exploration when there is no indexingin progress.

Related Topics• Indexing best practices on page 90

Deploying SAPBusinessObjects Explorer,acceleratedversion for SAPNetWeaverBW

SAP BusinessObjects Explorer, accelerated version for SAP NetWeaver BWallows you to deploy SAP BusinessObjects Explorer with SAP NetWeaverBusiness Warehouse Accelerator (BW Accelerator) and SAP NetWeaverBW. In this deployment scenario, end users can create and exploreInformation Spaces based on BW Accelerator indexes, which leverage thedata in InfoCubes.

The following diagrams present possible deployment scenarios for SAPBusinessObjects Explorer, accelerated version for SAP NetWeaver BW:

Note:For more information about SAP NetWeaver BW Accelerator, see theTechnical Operations Manual for BI Accelerator available on the SAPCommunity Network (SDN) at: http://sdn.sap.com/bia.

19


http://sdn.sap.com/bia

Implementing a complex distributeddeployment scenario

20


You can deploy SAP BusinessObjects Explorer in a distributed scenario overmultiple nodes, using firewalls and reverse proxies for your security to setup a complex environment that ensures security and failover.

21


22


Installation

Installation pre-requisitesFor a detailed list of supported environments and hardware requirements,consult the SAP BusinessObjects Explorer XI 3.1 Supported Platformsdocument available on the SAP Community at: http://sdn.sap.com in the"Articles" section. This document includes specific version and patch-levelrequirements for web application servers, web browsers, and operatingsystems.

Pre-requisites for all installations of SAP BusinessObjects Explorer

SAP BusinessObjects Enterprise XI 3.1 must be installed and configuredcorrectly before you install SAP BusinessObjects Explorer XI 3.1.

Information:See the BusinessObjects Enterprise XI 3.1 Installation and ConfigurationGuide at: http://service.sap.com/instguides.

Note:If you have an existing installation of SAP BusinessObjects Polestar XI 3.1,you need to uninstall this version before you install SAP BusinessObjectsExplorer XI 3.1. Some files need to be removed manually before you installthe new version. For details on which files you need to remove, see theUninstalling SAP BusinessObjects Explorer sections for Windows or UNIX,listed in Related Topics, below. It is highly recommended you back up theSAP BusinessObjects Explorer WAR files, before you start the uninstallationprocedure.

The following BusinessObjects servers are required for the application torun correctly:• Central Management Server (CMS)• Web Intelligence Processing Server• Output File Repository Server

23

Installation

http://sdn.sap.com

http://service.sap.com/instguides

• Input File Repository ServerA web application server is also required.

Before you begin to deploy SAP BusinessObjects Explorer, ensure thefollowing:• You have administrative access to the designated machine for installation.• The machine that SAP BusinessObjects Enterprise XI 3.1 is installed on

is operating and is accessible on the network.• A BusinessObjects Enterprise SIA is installed on any machine that hosts

Explorer servers.• You have the CMS details of the SAP BusinessObjects Enterprise XI 3.1

installation. For example, the CMS name, port, and user credentials.

Additional pre-requisites for SAP BusinessObjects Explorer, acceleratedversion for SAP NetWeaver BW

If your deployment includes SAP NetWeaver BW Accelerator and you wantto use SAP BusinessObjects Explorer, accelerated version for SAPNetWeaver BW to analyze data from InfoCubes, you need to install the SAPNetWeaver BW Accelerator driver for SAP BusinessObjects Explorer. Thedriver is included in the installation package.

Before you install the driver, the following applications need to be deployedand accessible on your network:• SAP NetWeaver EhP1 SP2

Needs to include SAP Netweaver BW 7.0.1 SP2.

Information:See the Installation Guide SAP Enhancement Package Installation

• SAP NetWeaver BW Accelerator 7.0

Information:See the Update Guide SAP NetWeaver BW Accelerator 7.0

• SAP BusinessObjects Integration, version for SAP solutions

Information:See the BusinessObjects XI Integration for SAP Solutions Installationand Administration Guide available on the "SAP BusinessObjects" tabat. http://service.sap.com.

24

Installation

http://service.sap.com

Related Topics• Uninstalling SAP BusinessObjects Explorer on Microsoft Windows on

page 47• Uninstalling SAP BusinessObjects Explorer on UNIX on page 48

Installation package contentsThe SAP BusinessObjects Explorer setup includes the following packages:

Explorer servers

This feature includes:• The backend servers:

• Master• Indexing• Search• Exploration

• Third-party components• The BusinessObjects Java SDK

Note:You can install the servers on different host machines. For example, youcan have dedicated machines for indexing, exploration, and search.

Web Application Server Component

This feature includes the necessary web portal deployment components.

Note:If you do not have the default BusinessObjects Enterprise web applicationserver installed, the required WAR (Web Application Archive) files have tobe deployed separately. You can deploy the WAR files manually using thewdeploy application.

CMS Add-on

The CMS Add-on needs to be installed on the BusinessObjects EnterpriseCMS. This add-on enables the CMS to recognize SAP BusinessObjectsExplorer.

25

Installation

Related Topics• Installation procedures on page 26

Installation proceduresThe installation procedure you follow depends on the Operating System(O/S) of your Explorer server host machines.

Related Topics• Installing SAP BusinessObjects Explorer on Microsoft Windows on

page 26• Installing SAP BusinessObjects Explorer on IBM AIX on page 30• Installing SAP BusinessObjects Explorer on Linux SUSE on page 31

Installing SAP BusinessObjects Explorer onMicrosoft Windows

Note:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name could appear in some of theinterface messages you will see during the installation procedure.

1. Double-click setup.exe.2. In the "BusinessObjects Polestar Setup" dialog, click Next >.3. Read and accept the License Agreement, then click Next > to start your

installation.The detected directory is based upon your BusinessObjects EnterpriseXI 3.1 installation.

4. Confirm your installation options:

26

Installation

DescriptionOption

• Select the Explorer serversyou want to install at thespecified location.

• Select CMS Add-On.• Select Web Application

Server component.

You want to install all of theExplorer servers and the Ex-plorerWebApplication Serveron theBusinessObjects Enter-prise server.


• Select CMS Add-On.

You want to install all of theExplorer servers on the Busi-nessObjects Enterprise serv-er.

• Type the file path to the hostmachine where you want toinstall the server(s).

• Enter the CMS Name andport number of the BusinessObjects installation to whichyou want to connect.


You want to install one orseveral Explorer servers on amachine that does not includethe BusinessObjects Enter-prise server.

Note:You need to install the Explor-er CMSadd-onon theBusines-sObjects Enterprise serverand install an SIA on the ma-chine where you want to in-stall the Explorer server(s)before you install the Explorerserver(s).

• Type the file path to yourWeb Application Server hostmachine.

• Select Web ApplicationServer component.

You want to install the Explor-er Web Application compo-nent on your BusinessObjectsEnterprise Web ApplicationServer.

If the details are accepted, you are prompted to install SAPBusinessObjects Explorer.

27

Installation

5. Click Next >.6. Enter your CMS logon credentials:

• CMS Name• Port number• User Name• Password• Authentication

7. Click Next >.If you chose to install the Web Application Server component, you areprompted to automatically deploy the Explorer Web Application Servercomponents (WAR files).

8. How and where you deploy the Explorer Web Application Servercomponents depends on which Web Application Server you want to usefor SAP BusinessObjects Explorer:

28

Installation

DescriptionOption

• To deploy the WAR files auto-matically, selectAutomatical-ly

• To deploy the WAR filesmanually, using wdeploy, se-lect Manually

Note:If you choose either automaticor manual deployment, the nec-essary files are copied locally to:C:\Program Files\Business Ob-

jects\BusinessObjects Enter-

prise 12.0\java\applications\

Youwant to deploy the Explor-er Web Application Servercomponents to the ApacheTomcat used by BusinessOb-jects Enterprise.

You need to deploy the ExplorerWeb Application Archive (WAR)files separately. You can deploythe WAR files manually usingthe wdeploy application.

Youwant to deploy the Explor-er Web Application Servercomponents to another WebApplication Server.

9. Optional: If you chose to deploy automatically, you are prompted toconfigure the default web application server:Type the Server Instance and Service Name. Ensure the ApplicationServer Installation Directory is correct. Click Next > to continue.

10. Click Next > to launch the installation.When the installation is complete, a message is displayed indicatingwhether installation was successful or not.

After installation ensure that the Explorer servers are enabled and startedwithin the BusinessObjects Enterprise CCM or CMC. Within the CCM, youcan enable and start servers via the Server Intelligence Agent (SIA).

Related Topics• Deploying the WAR files manually on page 33

29

Installation

InstallingSAPBusinessObjectsExplorer on IBMAIX


1. Type the path to the directory where you want to install launch the Explorerserver(s), type: ./install.sh <install_dir>For example: ./install.sh /usr/unix/Explorer/

2. On the "BusinessObjects Polestar Setup" dialog, select the currentlanguage for the installation.

3. Press Enter.The "BUSINESS OBJECTS LICENSE AGREEMENT "screen appears.

4. To accept the license agreement, press y.5. Select the language packs you want to install.6. Select the features you want to install on the directory you specified:

• Explorer Servers (Master, Indexing, Search, and Exploration)• Web Application Server Component (this includes the web portal

deployment components)• CMS Add-On (This feature is disabled when the CMS is not detected.)

7. Press Enter.8. In the "Enter Information for existing CMS" screen, type the following

information:• CMS Name• Port number• User Name• Password

9. Press Enter.The "Redeploy web applications?" screen appears.

10. You have two options:

30

Installation

• If the machine you selected for installation includes Apache Tomcatand you want to deploy the Explorer Web Application Servercomponents on that machine, select Yes.

• If you don't want to deploy the Explorer Web Application Servercomponents on the selected machine, select No.

11. Press Enter.12. Optional: If the Enter Web Application Server configuration "Tomcat 5.5

"screen appears, type the Instance to install, ensure the Application ServerInstallation Directory is correct, and then press Enter.

13. In the "Confirm Install" screen, verify the installation directory is correct,then press Enter to start the installation.

The "Running Post Install Actions" screen displays.

Depending on the fonts installed on your AIX server and the languageversions across your deployment, you may need to install specific fonts onthe server and/or the client machines.

Related Topics• Standardizing font usage across your deployment on page 40

Installing SAP BusinessObjects Explorer onLinux SUSE


1. Type the path to the directory where you want to install launch the Explorerserver(s), type: ./install.sh <install_dir>

For example: ./install.sh /usr/linux/Explorer/

2. On the "BusinessObjects Polestar Setup" dialog, select the currentlanguage for the installation.

3. Press Enter.The "BUSINESS OBJECTS LICENSE AGREEMENT "screen appears.

4. To accept the license agreement, press y.

31

Installation

5. Select the language packs you want to install.6. Select the features you want to install on the directory you specified:

• Explorer Servers (Master, Indexing, Search, and Exploration)• Web Application Server Component (this includes the web portal

deployment components)• CMS Add-On (This feature is disabled when the CMS is not detected.)

7. Press Enter.8. In the "Enter Information for existing CMS" screen, type the following

information:• CMS Name• Port number• User Name• Password

9. Press Enter.The "Redeploy web applications?" screen appears.

10. You have two options:• If the machine you selected for installation includes Apache Tomcat

and you want to deploy the Explorer Web Application Servercomponents on that machine, select Yes.

• If you don't want to deploy the Explorer Web Application Servercomponents on the selected machine, select No.

11. Press Enter.12. Optional: If the Enter Web Application Server configuration "Tomcat 5.5"

screen appears, type the Instance to install, ensure the Application ServerInstallation Directory is correct, and then press Enter.

13. In the "Confirm Install" screen, verify the installation directory is correct,then press Enter to start the installation.

The "Running Post Install Actions" screen displays.

Depending on the fonts installed on your Linux server and the languageversions across your deployment, you may need to install specific fonts onthe server and/or the client machines.

Related Topics• Standardizing font usage across your deployment on page 40

32

Installation

Deploying the WAR files manuallyNote:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name could appear in some of theinterface messages you will see during the installation procedure.

If you did not auto-deploy the Explorer WAR files during installation, youneed to deploy the files manually using the wdeploy application providedwith your BusinessObjects Enterprise XI installation.

Related information:Deployment is dependent on your web application server and operatingserver, refer to the web application server documentation for detailedinformation on WAR file deployment. For further detailed information on webapplication deployment, refer to: BusinessObjects Enterprise XI 3.1 WebApplication Deployment Guide for Windows at http//:help.sap.com.

The WAR files are located at:

C:\Program Files\Business Objects\BusinessObjects Enterprise12.0\java\applications\

To deploy the Explorer WAR files on your Explorer Web Application Serverusing wdeploy:

1. Open the corresponding configuration file for edit:C:\Program Files\Business Objects\deployment\

For example, if you are deploying WAR files to a Tomcat web applicationserver, edit the config.tomcat55 file.

By default, configuration files contain parameters that are related to thepreviously used web application server.

2. Replace all parameters so that they are specific to the web applicationserver you wish to deploy to.

3. Open a cmd console and navigate to the location of wdeploy.C:\Program Files\Business Objects\deployment\

4. Run the wdeploy command to deploy the Explorer WAR files on to yourweb application server.

33

Installation

http://help.sap.com

Launch the command for each WAR. Reference the properties files locatedat C:\Program Files\Business Objects\deployment\apps\:

Related WAR FileFile

Polestar WARpolestar.properties

PolestarAppActions WARPolestarAppActions.proper

ties

Online Helppolestar_help.properties

Video Tutorialpolestar_tutorial.properties

For example, to deploy the PolestarAppActions WAR file on Tomcat,reference the name of the properties file:

wdeploy tomcat55 -DAPP=PolestarAppActions deploy

Note:For further information on wdeploy commands, refer to the wdeployREADME located at: C:\Program Files\BusinessObjects\deployment\

5. Various BusinessObjects Enterprise WAR files need to be redeployed.Launch the wdeploy command for each WAR, the properties files are:

Related WAR FileFile

CMC application WARCmcApp.properties

CmcAppActions WARCmcAppActions.properties

InfoView application WARInfoViewApp.properties

InfoViewAppActions WARInfoViewAppActions.proper

ties

PlatformServices WARPlatformServices.properties

For example, to deploy the CmcApp WAR file on Tomcat, reference thename of the properties file:

34

Installation

wdeploy tomcat55 -DAPP=CmcApp deploy

The WAR files are deployed to your web application server.

Example:

1. Stop Tomcat.2. Open for edit the following file: C:\Program Files\Business

Objects\deployment\config.tomcat55.3. Ensure that the file content resembles your Tomcat installation, for

example:

#### Business Objects Configuration Utility##

# as_dir: the installation directory of the applicationserveras_dir=C:\Program Files\Business Objects\Tomcat55

# as_instance: the application server instance to deployto (represents the name of a folder in the conf/Catalinadirectory)as_instance=localhost

# as_service_name: on windows, the name of the tomcat service when tomcat is installed as a service#as_service_name=%AS_SERVICE_NAME%

# as_service_key: on windows, when tomcat is installed asa service, the name of the key where the java startup parameters are stored# (there is generally no need to touch this)as_service_key=HKLM\SOFTWARE\Apache Software Foundation\Procrun 2.0\${as_service_name}\Parameters\Java

# as_service_key_value: name of the String value where thejava startup parameters are stored, in the key pointed toby as_service_key# (there is generally no need to touch this)as_service_key_value=Options

4. Open a cmd console and navigate to the wdeploy utility location:C:\Program Files\Business Objects\deployment\

5. Launch the following commands to deploy all of the WAR files:

35

Installation

Command

wdeploy tomcat55 -DAPP=polestar deploy

wdeploy tomcat55 -DAPP=PolestarAppActions deploy

wdeploy tomcat55 -DAPP=polestar_help deploy

wdeploy tomcat55 -DAPP=polestar_tutorial deploy

wdeploy tomcat55 -DAPP=CmcApp deploy

wdeploy tomcat55 -DAPP=CmcAppActions deploy

wdeploy tomcat55 -DAPP=InfoViewApp deploy

wdeploy tomcat55 -DAPP=InfoViewAppActions deploy

wdeploy tomcat55 -DAPP=PlatformServices deploy

6. If necessary, restart Tomcat.

Post installation configurationOnce your SAP BusinessObjects Explorer installation is complete, you needto configure the following:• the index directory where indexes will be stored• the session timeout• the Java Virtual Machine (JVM) heap size for each Explorer server• the OpenDocument URL so that the end-user option to export Explorer

Information Spaces to SAP BusinessObjects Web Intelligence will workcorrectly

Related Topics• Configuring the path for Information Space indexes on page 77• Configuring the session timeout period on page 79• Increasing virtual memory on the Explorer servers on page 80• Explorer Web Application settings on page 73

36

Installation

Configuring SAP BusinessObjects Explorer towork with SAP NetWeaver BW Accelerator

• The following should not be necessary with the GA build: Enable theTREX cache and configure the TREX index server for SAPBusinessObjects Explorer.

Information:For step-by-step information on how to enable the TREX cache andconfigure the TREX index server, refer to the Master Guide for SAPBusinessObjects Explorer, accelerated version for SAP NetWeaverBusiness Warehouse at http://help.sap.com.

• Connect to a specific SAP NetWeaver BW Accelerator

To ensure failover, you can define one or more SAP NetWeaver BWAccelerator blades as backup blades for your BW Accelerator landscape.The BW Accelerator backup blade(s) take the load of your productionBW Accelerator blade in the event of failure.

• Configure SAP BusinessObjects Explorer for SAP authentication• Make SAP NetWeaver BW Accelerator indexes and user authorizations

available to SAP BusinessObjects Explorer.

Information:For information on how to do this, refer to the Master Guide for SAPBusinessObjects Explorer, accelerated version for SAP NetWeaverBusiness Warehouse at http://help.sap.com.

• Import SAP NetWeaver BW user profiles to the BusinessObjectsEnterprise CMS or create new users with the same user profile as inNetWeaver BW.

Information:For information on creating new users on the BusinessObjects EnterpriseCMS refer to the SAP BusinessObjects Enterprise Administrator's GuideXI 3.1. For information on importing users into the BusinessObjectsEnterprise CMS, refer to the SAP BusinessObjects XI Integration for SAPSolutions Installation and Administration Guide. Both guides are availableat: http://help.sap.com.

37

Installation

http://help.sap.com

http://help.sap.com

http://help.sap.com

Related Topics• Connecting to an SAP NetWeaver BW Accelerator on page 39• Configuring SAP BusinessObjects Explorer for SAP authentication on

page 54

Configuring SAP BusinessObjects Explorer for SAPauthentication

In order for SAP NetWeaver BW users to log into SAP BusinessObjectsInfoView using their NetWeaver BW user login, you need to import yourNetWeaver BW users into the BusinessObjects Enterprise CMS at the CMClevel. To do this, SAP authentication is required.

Note:SAP highly recommends you use the SAP BusinessObjects Integration Kitfor SAP. For more information, see the SAP BusinessObjects XI Integrationfor SAP Solutions Installation and Administration Guide available on the SAPBusinessObjects tab at. http://service.sap.com.

Before setting up SAP authentication for SAP BusinessObjects Explorer,you need to:• ensure that SAP authentication and security is configured within the

BusinessObjects Enterprise CMC

Note:The SAP option becomes available in the BusinessObjects EnterpriseCMC once you have added your SAP NetWeaver BW system within theSAPGUI. The SAPGUI is installed when you install the BusinessObjectsIntegration Kit for SAP. For full information, see the BusinessObjects XIIntegration for SAP Solutions Installation and Administration Guideavailable on the "SAP BusinessObjects" tab at. http://service.sap.com.

• verify that you can log on to the BusinessObjects Enterprise CMC viaSAP authentication

• configure the Explorer Web Application Server properties file for SAPauthentication

Related Topics• Configuring SAP BusinessObjects Explorer for SAP authentication on

page 54

38

Installation



Connecting to an SAP NetWeaver BW Accelerator

Note:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name could appear in some of theinterface messages you see in SAP BusinessObjects Explorer and the SAPBusinessObjects Enterprise CMC.

Before performing this task, verify that SAP BusinessObjects Enterprise,SAP BusinessObjects Explorer, the SAP NetWeaver BW Accelerator driverfor SAP BusinessObjects Explorer, and SAP NetWeaver BW Acceleratorare deployed and are accessible on the network.

The SAP BusinessObjects Enterprise system requires an SAP user accountthat is authorized to access SAP role membership lists, authenticate SAPusers, and so on. You will need this user name and its password when youconnect SAP BusinessObjects Enterprise to your SAP NetWeaver BWsystem.

To connect SAP BusinessObjects Explorer with a designated SAP NetWeaverBW Accelerator via the CMC administration page:

1. Stop the Explorer servers.2. Logon to the BusinessObjects Enterprise CMC.3. Navigate to Manage > Applications.4. Right-click Polestar and click Properties.5. 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 at least to a blade with a master name server).

39

Installation

6. Optional: if you have one or more backup blades in place for your BWAccelerator landscape, you can also configure additional connections tothose 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

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

When you are logged into SAP BusinessObjects Explorer, NetWeaver BWAccelerator indexes appear listed in theManage Spaces tab, within the SAPNetWeaver BW Accelerator folder.

Related Topics• Deploying SAP BusinessObjects Explorer, accelerated version for SAPNetWeaver BW on page 19

Standardizing font usage across yourdeployment

Note:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The directories on the Explorer servers use theprevious name: polestar.

The fonts used to display character strings in Information Spaces are providedby the font libraries on the clients and servers across your SAPBusinessObjects Explorer deployment:• the Exploration servers supply the fonts used to display the character

strings on charts

40

Installation

• the client machines logged into SAP BusinessObjects Explorer supplythe fonts used to display the character strings in the rest of the applicationGUI

If the fonts installed on the Exploration server(s) do not match the fonts onthe client(s), the character strings in the charts and the rest of the applicationGUI display with different fonts.

Deploying the Arial unicode J font

A licensed version of the Arial Unicode J font, which includes the glyphs forall supported languages, is installed by default when you install the SAPBusinessObjects Explorer server components. The Arial Unicode J font ismatched by the Arial Unicode MS font on most Microsoft Windows clientmachines, which provides a standard display for character strings throughoutthe application GUI. In the case of your client machines not having acompatible font, you can opt to install a copy of the Arial Unicode J font onyour client machines.

The font is available on the following directory of each SAP BusinessObjectsExplorer server once you have installed the application: <BusinessObjects_Polestar_InstallDir>/Polestar12.0/jre/lib/fonts.

Note:If you implement a distributed deployment architecture, then you need toverify that this font is installed on each Exploration server.

Installing custom fonts

On some language versions fonts may appear too large, resulting in chartareas being hidden by axis labels or facet values being truncated, and somelanguage-specific special characters may be missing. These types of fontinconsistencies are more common on UNIX platforms than Windows. Tosolve these issues, administrators can install fonts of their choice on theservers and/or clients. Once the font(s) are installed, you need to modify twofiles so that these fonts are used in both the charts and the rest of theapplication GUI.

To deploy a font of your choice:• Stop the Exploration server(s).• Install and distribute the font of your choice to the Exploration server(s)

and/or clients.

41

Installation

The location on the server is: <BusinessObjects_Polestar_InstallDir>/Polestar12.0/jre/lib/fonts.

• To include the font of your choice in charts:1. Open the <BusinessObjects_Polestar_In

stallDir>/polestar12.0/chart-template.sample file for edit.2. Search for the following string:

[Arial Unicode J, Arial Unicode MS, Arial]

3. Replace the three font names with the names of your installed fonts,as follows:

[FontFaceName 1;FontFaceName 2;Font FaceName 3]

Information:The fonts are specified in order of preference. If the first font in the listis not available, the second font is used; if the second font is notavailable, the third font is used, and so on.

4. Optional: to specify the font size, search for the following string:

[10.0];

5. Replace the "10.0" font size with the size of your choice, for exampleyou would specify a choice of two size 14 Japanese fonts as follows:

<GlobalValue><DefaultValues>

<DefaultValue type="4" value="[jiskan24.pcf.z;k14.pcf.Z];[14.0];[0];[0;0;0;0];[]" />

</DefaultValues></GlobalValue>

Note:If a different font size is specified for a particular chart zone, such asthe legend, then the global font size is overridden in that particularchart zone.

6. Rename the file chart-template.xml and save it to <BusinessObjects_Polestar_InstallDir>/Polestar12.0/.

• For the rest of the application interface, you can define a font or font sizeglobally for all languages and, if necessary, define a specific font or fontsize for a specific language(s) that will override the global setting for that

42

Installation

language. To include the font of your choice in the application GUI otherthan the chart area:1. Open the <install_dir>\webapps\polestar\schema\chi

nese.css.example\ file for edit.2. Replace the default font name and size with the font and size of your

choice:

global {font-family: Arial Unicode J, Arial Unicode MS, Arial,Sans-serif;font-size: 13pt;}

Information:The fonts are specified in order of preference. If the first font in the listis not available, the second font is used; if the second font is notavailable, the third font is used, and so on.

Note:If a different font size is specified for a particular interface label, suchas ToolTips, then the global font size is overridden in that particulartype of label.

3. Where you save the file depends on whether you want to apply thesesettings globally, to all languages, or just to a specific language:• to apply the settings to all languages, rename the file as glob

al.css and save it to: <install_dir>\webapps\polestar\schema\global\global.css\

• to apply the settings to a specific language, rename the file as<language>.css and save it to a sub-folder named with thelanguage code for that language as follows: <install_dir>\webapps\polestar\schema\global\<language_code>\<language>.css\

For example, for Chinese, you would save the file as follows: <install_dir>\webapps\polestar\schema\global\zh_CH\chinese.css\

4. Restart the Exploration servers.

Note:Because the css. file(s) control all of the display properties, it isrecommended you only modify the values for these specified parameters.

43

Installation

WebSphere policy configuration with Java 2security

When Java 2 security is activated on WebSphere, it is necessary to modifythe server policy permissions so that SAP BusinessObjects Explorer functionscorrectly. You need to modify the permissions in the following file:/usr/WebSphere6.1/AppServer/profiles/visual01/properties/server.policy

• java.lang.RuntimePermission modifyThreadGroup• permission java.util.PropertyPermission "*", "read, write";• permission java.io.FilePermission "<<ALL FILES>>", "read, write";

To do this:1. Launch policytool.2. Open the server.policy file.3. Add the appropriate permission, and then save your changes.4. Use policytool in /usr/WebSphere6.1/AppServer/java/bin.5. Re-start WebSphere.

Verifying your installationTo verify your installation:• Start the Explorer servers• Log onto SAP BusinessObjects Explorer via the URL• Create a new Information Space and index it• Navigate to the new Information Space and explore the displayed values

Related Topics• Starting and stopping the backend servers on page 73

44

Installation

Logging on

Verify that the end users in your deployment have their web browser set toaccept session cookies. If session cookies are not accepted, users cannotlog into SAP BusinessObjects Explorer.

To access SAP BusinessObjects Explorer:

1. Launch your web browser and go to the to following URL:http://<webserver_name>:<port_number>/polestar

Replace webserver and port with the name and port of the web serverthat is setup for Business Objects Enterprise. If you are unsure what theweb server name is or what the exact URL is, check with youradministrator.

The "Log On" page appears.

2. Type in the name of your system within the System field.3. Type your username and password within the Username and Password

fields.4. Click the Authentication list to select Enterprise, LDAP, or Windows AD

authentication.Enterprise authentication requires a username and password that SAPBusiness Objects Enterprise recognizes.

LDAP authentication requires a username and password that an LDAPdirectory server recognizes.

Windows AD authentication requires a username and password thatWindows AD recognizes.

Note:Enterprise authentication is the default method. LDAP, and ADauthentication requires specific set up. If necessary, contact your systemadministrator for further help.

5. Click the Log On button.If your logon credentials are accepted the welcome page with the Hometab appears.

45

Installation

Note:If you have the correct rights, the Manage Spaces tab is also available.To open the tab, click Manage Spaces on the title bar (located on thetop-right corner).

To log off Business Objects Explorer, click Logoff on the title bar (locatedon the top-right corner). The Log On page reappears.

Logging on with SAP authentication

Before you can log on through SAP authentication, the BusinessObjectsEnterprise platform has to be configured with SAP security.

To log on through SAP authentication:

1. Type in the URL (the address of the Polestar product) in your web browser.2. Go to the to following URL:

http://<webserver_name>:<port_number>/polestar

Replace webserver and port with the name of the web server and portthat is setup for Business Objects Enterprise. If you are unsure what theweb server name is or what the exact URL is, check with youradministrator.

The Log On page appears.

3. Click the Authentication list to select SAP authentication.The SAP specific fields are displayed.

4. Type in the value of the system ID within the SAP System ID: field.5. Type in the value of the client ID within the SAP Client ID: field.6. Type in the name of your system within the System: field.7. Type your SAP username and password into the Username and

Password fields.8. Click the Log On button.

If your SAP logon credentials are accepted the welcome page with the"Home" tab appears.

46

Installation

Note:If you have the correct rights, the "Manage Spaces" tab is also available.To create or edit Information Spaces, click Manage Spaces on the titlebar (located on the top-right corner).

To log off, click Logoff on the title bar (located on the top-right corner).

Uninstalling SAP BusinessObjectsExplorer on Microsoft Windows


It is highly recommended you back up the SAP BusinessObjects ExplorerWAR files, before you start the uninstallation procedure.

To uninstall SAP BusinessObjects Explorer:

1. Navigate to the Control Panel of your Windows installation on the servermachine.

2. Open Add or Remove Programs.3. Locate SAP BusinessObjects Explorer.4. Click Remove.

A confirmation dialog appears.

5. Click Yes to uninstall SAP BusinessObjects Polestar.6. Remove the following files manually:

• The polestar directory:

<BusinessObjectsEnterprise install_dir> /Polestar12.0/

• Polestar Web Application Server files in:

<Polestar_web_app_install_dir>\<web_app_server>\webapps\

47

Installation

Uninstalling SAP BusinessObjectsExplorer on UNIX


It is highly recommended you back up the SAP BusinessObjects ExplorerWAR files, before you start the uninstallation procedure.

This procedure describes how to uninstall SAP BusinessObjects Explorerfrom an IBM AIX or Linux SUSE platform.

1. To undeploy the Web Application Server(s), run the wdeploy.sh scriptto remove your installation from the following locations:

./wdeploy.sh tomcat55 - DAPP=polestar undeploy

./wdeploy.sh tomcat55 -DAPP=polestar_help undeploy

./wdeploy.sh tomcat55 -DAPP=polestar_tutorial undeploy

./wdeploy.sh tomcat55 -DAPP=PolestarAppActions undeploy

Note:This example shows the command for Apache Tomcat.

2. To uninstall the servers, run the AddOrRemoveProducts.sh script.3. Remove each language pack.4. Remove BusinessObjects Explorer XI 3.1.5. In the "Enter Information for existing CMS" screen, confirm you want to

remove BusinessObjects Explorer XI 3.1.6. Confirm your choice.

The uninstallation is processed.

7. Verify that the following folder contains no files including the namePolestar:• /mira/bobje/tomcat/webapps

Note:It is especially important to remove any files containing "Polestar" if youwish to install another version of SAP BusinessObjects Explorer.

48

Installation

SAP BusinessObjects Explorer is removed from your system.

49

Installation

50

Installation

Security

Reverse proxiesSAP BusinessObjects Explorer supports the same reverse proxy configurationas SAP BusinessObjects Enterprise. No specific reverse proxy configurationfor SAP BusinessObjects Explorer is required.

Information:For information about reverse proxy configuration for SAP BusinessObjectsEnterprise, refer to the BusinessObjects Enterprise Administrator's Guide XI3.1 available on the "SAP BusinessObjects" tab at: http://help.sap.com.

Firewall port usage for SAPBusinessObjects Explorer

When you deploy SAP BusinessObjects Explorer, you can protect yournetwork with a firewall, however the firewall can block network communicationbetween your deployment nodes. For example, if you have deployed theExplorer Web Application on one node, deployed the Explorer servers onanother node and various BusinessObjects Enterprise servers are alreadydeployed on a third node, you may have to open ports to allow the nodes tocommunicate.

Each server can be configured so that they use a specific port. The firewallcan then be configured so that the specific ports are open.

It is necessary to choose a set of port numbers which do not interfere withother network services and it is necessary to ensure that the correct serversare configured. For example, the following servers are required to have theirports configured on a simple Explorer deployment:• Central Management Server• Explorer Master Server• Explorer Indexing Server

51

Security

http://help.sap.com

• Explorer Search Server• Explorer Exploration Server• Web Intelligence Processing Server

Note:If you allow access to the CMS, other services can connect and exchangeinformation.

Example: Port configuration

This example demonstrates how you could configure servers on a simpledeployment:

PortServer

64002Central Management Server

64023Explorer Master Server

64022Explorer Indexing Server

64024Explorer Search Server

64021Explorer Exploration Server

64032Web Intelligence Processing Server

Related Topics• Configuring firewall ports on page 52

Configuring firewall ports

Before beginning, it is necessary to have administrative access to all nodes.

To open a port for a server within your SAP BusinessObjects Explorerdeployment:

1. Login to the BusinessObjects Enterprise CMC and click Servers.2. Navigate to your chosen server.

For example: Service Categories > Polestar

52

Security

3. Right-click the server and click Properties.4. Under Common Settings, unselect Auto assign.5. Within Request Port: type a port number.

Note:Ensure that the chosen port is not being used and that there are noconflicts.

6. Click Save & Close.7. Configure your firewall (or firewalls) so that the port is open for all

necessary nodes in your deployment.

Your chosen server is able to communicate with other nodes within yourdeployment environment.

Authentication methodsSAP BusinessObjects Explorer supports the authentication methodssupported by SAP BusinessObjects Enterprise:• Enterprise• Windows AD• LDAP• SAP R/3

To enable SAP R/3 authentication on your SAP BusinessObjects Explorerdeployment, you need to perform some manual configuration procedures onthe Explorer server.


page 38• Configuring SAP BusinessObjects Explorer for SAP authentication on

page 38

53

Security

Configuring SAP BusinessObjects Explorer forSAP authentication

This table provides the settings you need to configure in order to make SAPauthentication available to SAP BusinessObjects Explorer users.

Note:Before configuring SAP BusinessObjects Explorer for SAP authentication,verify that SAP authentication is already configured for the BusinessObjectsEnterprise CMS. For information on how to do this, refer to theBusinessObjects XI Integration for SAP Solutions Installation andAdministration Guide available on the "SAP BusinessObjects" tab at.http://service.sap.com.

The SAP authentication settings are stored within the Explorer settingsproperties file (default.settings.properties).

Table 5-1: SAP authentication web application settings

Example Configu-ration (for SAPAuthentication)

Example Configu-ration (withoutSAP Authentica-tion)

DescriptionSetting

SAP_IDThe name of theSAP system.

default.sapsys

tem.name

truefalseDetermines if theSAP system nameis shown within theLog On page.

show.sapsystem.name

falsetrueDisables the SAPsystem name textbox within the LogOn page. You can-not change thetextbox value.

disable.sapsys

tem.name

54

Security


Example Configu-ration (for SAPAuthentication)

Example Configu-ration (withoutSAP Authentica-tion)

DescriptionSetting

100The SAP client ID.default.sap

client.name

truefalseDetermines if theSAP client name isshown within theLog On page.

show.sapclient.name

falsetrueDisables the SAPclient name textboxwithin the Log Onpage. You cannotchange the textboxvalue.

disable.sap

client.name

secSAPR3secEnterpriseThe default log onauthentication touse. The value isselected in the Au-thentication list ofthe Log On page.

default.authentica

tion.method

secEnterprise

secWinAD, se

cLDAP,secSAPR3

secEnter

prise,secWinAD,se

cLDAP

The values thatpopulate the Au-thentication list.

authentications

Example: Properties file configured for SAP authentication

default.sapsystem.name=SAP_IDshow.sapsystem.name=truedisable.sapsystem.name=falsedefault.sapclient.name=100show.sapclient.name=truedisable.sapclient.name=false

55

Security

default.authentication.method=secSAPR3authentications=secEnterprise,secWinAD,secLDAP,secSAPR3

Single Sign OnNote:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The directories on the Explorer servers use theprevious name: polestar.

You can configure SAP BusinessObjects Explorer for Single Sign On (SSO)for the following authentication methods:• Enterprise• Windows AD• LDAP

The following files are used to configure SSO:• $<PolestarWebappRoot>/WEB-INF/classes/sso.properties contains

all of the SSO options• $<PolestarWebappRoot>/WEB-INF/web.xml contains a servlet filter that

needs to be activated for Vintela authentication (for Windows AD)• $<PolestarWebappRoot>/WEB-INF/default.settings.properties

contains Explorer startup options that can be overridden by the SSO inthe sso.properties file

Related Topics• Activating Single Sign On on page 56• SSO for WinAD authentication using Vintela on page 59• SSO for LDAP authentication using SiteMinder on page 61• Enabling Trusted Authentication on page 63

Activating Single Sign On

SSO must already be configured on BusinessObjects Enterprise before youconfigure SSO on SAP BusinessObjects Explorer.

56

Security

Information:See the SAP BusinessObjects Enterprise Administrator's Guide for XI 3.1at: http://help.sap.com.

To activate SSO:

1. Stop the Explorer Web Application Server.2. Open the following file for edit:

$<PolestarWebappRoot>/WEB-INF/classes/sso.properties

3. Set the following parameters to the values specified:

ValuesSetting

truesso.global.enabled

<provider_name>sso.global.providers

Note:By default, the sso.properties file contains a set of ready-to-use valuesfor the sso.global.providers file. The property must only be set oncein the entire file. However, you can specify multiple providers using acomma-separated list of providers.

4. Optional: three additional parameters can be set:

57

Security

http://help.sap.com

ValuesDescriptionSetting

trueControls the CMS used duringthe authentication. If no valueis specified, the de

fault.cms.name value set inthe default.settings.prop

erties is used.

sso.glob-al.cms

Possible values are:• secEnterprise

• secLDAP

• secWinAD

Controls the authenticationmethod used.

sso.glob-al.au-thentica-tion

Two possible values:• false - the logon workflow

continues normally as itwould if SSO was not en-abled

• true - the logon dialog isnot displayed

Controls how the SSO systembehaves if no credential hasbeen found.

sso.glob-al.erro-rOnFail-ure

Example:

sso.global.enabled=truesso.global.authentication=sso.global.cms=hostname:portsso.global.providers=sso.vintela

58

Security

SSO for WinAD authentication using Vintela

The Vintela Authentication Services provider uses the credentialsautomatically passed from the browser to the web server to authenticate theuser against an Active Directory server.

Note:the authentication cannot be overriden and is implicitely set to secWinAD.

It works as follows:• Retrieves the Windows credential from the current execution context

using Vintela• Logs on to the server with authentication using these credentials

To enable Vintela Authentication Services for SSO on WinAD, you need tomake two additional modifications to $<PolestarWebappRoot>/WEB-INF/web.xml.• uncomment the definition of the authFilter• uncomment the mapping of the authFilter

You also need to set the following parameters:

59

Security

ValuesDescriptionSetting

com.businessob-jects.datadiscov-ery.sso.vintela.VintelaS-SOProvider

class-Name

<cms_name>controls the CMS used for authentica-tion. It can be used to override the de-fault CMS.

cms

Example:

## Vintela parameters (sso.vintela provider)#sso.vintela.className=com.businessobjects.datadiscovery.sso.vintela.VintelaSSOProvidersso.vintela.cms=

SSO for WinAD using Kerberos

SAP BusinessObjects Explorer supports WinAD using Kerberos. You needto set up WinAD authentication with Kerberos on your BusinessObjectstEnterprise system. No configuration is necessary on the Explorer servers.


60

Security

http://help.sap.com

SSO for LDAP authentication using SiteMinder

The SiteMinder provider uses a cookie SMSESSION containing a uniquesession ID to be used as a user name to perform an authentication usingsecLDAP or secWinAD.

Note:this provider is based on a generic provider with predefined values, asspecified below.

It works as follows:• Retrieves the SiteMinder session cookie from the current execution context• Logs on to the server with authentication using this cookie value

You need to set the following parameters:

61

Security

ValuesDescriptionSet-ting

com.businessobjects.datadiscov-ery.sso.generic.GenericSSO-Provider

class-Name

<cms_name>controls the CMS used for au-thentication. It can be used tooverride the default CMS

cms

By default, this is set to: se-cLDAP. It can be changed tosecWinAD

authen-tication

The value is set to COOKIE bydefault.

Note:The default value should not bechanged.

the method to be used to retrievethe user name

user.re-trieval

The value is set to SMSESSIONby default.

Note:The default value should not bechanged.

specifies the parameter used bythe user.retrieval method to re-trieve the user name

us-er.param

Example:

## SiteMinder parameters (sso.siteminder)#sso.siteminder.className=com.businessobjects.datadiscov

62

Security

ery.sso.generic.GenericSSOProvidersso.siteminder.cms=sso.siteminder.authentication=secLDAPsso.siteminder.user.retrieval=COOKIEsso.siteminder.user.param=SMSESSION

Enabling Trusted Authentication

You need to configure the Business Objects Enterprise CMC for trustedauthentication before you can enable trusted authentication on SAPBusinessObjects Explorer.


To enable trusted authentication on SAP BusinessObjects Explorer:

1. Stop the Explorer Web Application Server.2. Open the following file for edit:

$<PolestarWebappRoot>/WEB-INF/classes/sso.properties

3. Set the following parameters:

ValuesSetting

Enter the CMS name and port number as follows:<servername.portnumber >

cms.default

truesso.enabled

falsesiteminder.en-abled

4. Find the following string:trusted.auth.user.retrieval

63

Security

http://help.sap.com

5. Enter the parameter value that corresponds to the user retrieval methodyou want to implement:

64

Security

ValueUser Retrieval Method

RE-MOTE_US-ER

Retrieve the user name from a call to getRemoteUser () on the HttpServletRequest object for the current requestin a servlet or JSP.

Note:For .NET the following properties need to be set on yourInfoViewApp directory, using IIS Manager:• disable Anonymous access checkbox• enable the Windows Integrated Authentication

checkbox

HTTP_HEAD-ER

Retrieve the user name from the contents of a specifiedparameter in the request URL.

Note:You define the query string parameter in the trust-ed.auth.user.param parameter in the web.xml file for SAPBusinessObjects InfoView.

COOKIERetrieve the user name from the contents of a specifiedcookie.

Note:You define the cookie in the trusted.auth.user.paramparameter in the web.xml file for SAP BusinessObjectsInfoView.

WEB_SES-SION

Retrieve the user name from the contents of a specifiedsession variable.

Note:You define the web session variable in the trusted.auth.us-er.param parameter in the web.xml file for SAP Busines-sObjects InfoView.

65

Security

ValueUser Retrieval Method

Retrieve the user name from a call to getUserPrincipal () .getName ( ) on the HttpServletRequest object for thecurrent request in a servlet or JSP.

USER_PRIN-CIPAL

For more information about the possible parameter values, see the SAPBusinessObjects Enterprise Administrator's Guide for XI 3.1 at:http://help.sap.com.

6. Verify you have specified how to retrieve the shared secret forBusinessObjects Enterprise.To retrieve the shared secret from a session variable, you need toconfigure the $<PolestarWebappRoot>/WEB-INF/classes/sso.properties file on SAP BusinessObjects Explorer.

7. Set the following parameter value in the $<PolestarWebappRoot>/WEB-INF/classes/sso.properties file:

ValueParameter

Enter the session variable name from which to retrievethe shared secret.

trust-ed.auth.shared.se-cret

8. Save and close the file.

Re-start the Explorer Web Application Server.

Allocating rights to users and groupsNote:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name appears in the SAPBusinessObjects Enterprise CMC.

66

Security

http://help.sap.com

http://help.sap.com

You configure SAP BusinessObjects Explorer user profiles within theBusinessObjects Enterprise CMC. You need to specify the following typesof user authorization in the CMC:• Define which Explorer features your users have access to, by granting

or denying rights to the appropriate objects• Grant users application rights for the other SAP BusinessObjects

applications leveraged by SAP BusinessObjects Explorer• Allocate the appropriate Access Level to users so they can perform

Explorer scheduling and export tasks as appropriate• Verify users with a Space Creator or Administrator profile have the

appropriate access rights to any BusinessObjects universes on whichthey need to build Information Spaces

Note:If users require the ability to build Information Spaces on SAP NetWeaverBW Accelerator indexes, you need to set up the correct user authorizationat the SAP NetWeaver BW InfoCube level and on each SAP NetWeaverBW Accelerator index before you configure those users' rights on SAPBusinessObjects Enterprise.

• Verify users have the necessary rights to folders where Information Spacesare stored on the BusinessObjects Enterprise CMS

Note:If objects have object-level security applied to them (for example universeobjects within SAP BusinessObjects Designer), SAP BusinessObjectsExplorer supports this security.

Information:For detailed information on user rights and setting those rights, refer to theSAP BusinessObjects Enterprise Administrator's Guide for XI 3.1 availableat: http://help.sap.com.


67

Security

http://help.sap.com

Explorer user rights per user profile

Note:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name appears in the SAPBusinessObjects Enterprise CMC.

Depending on the profiles you wish to allocate to your Explorer users, youneed to grant specific permissions.

Table 5-2: Feature usage permissions for Explorer users

PermissionsUser Profile

Explore Information Spaces

SpaceExplor-er

Explore Information Spaces: Export to Book-mark/Email

Explore Information Spaces: Export to CSV

Explore Information Spaces: Export to Image

Explore Information Spaces: Export to Web Intelli-gence

Log onto Polestar and view this object in the CMC

68

Security



Space Cre-ator





Manage Information Spaces

Manage Information Spaces: Create a new Space

Manage Information Spaces: Launch indexing

Manage Information Spaces: Modify a space

Manage Information Spaces: Schedule indexing

Delete objects

Edit this object


69

Security



Administrator





Manage Information Spaces

Manage Information Spaces: Create a new Space

Manage Information Spaces: Launch indexing

Manage Information Spaces: Modify a space

Manage Information Spaces: Schedule indexing

Delete objects

Edit this object


Modify the rights users have to this object

Securely modify rights users have to objects

Because SAP BusinessObjects Explorer is an add-on to SAPBusinessObjects Enterprise and leverages the SAP BusinessObjects WebIntelligence and SAP BusinessObjects InfoView applications, some additionalApplication Rights are also required for each Explorer user profile

70

Security

Table 5-3: Application Rights for Explorer users

BusinessObjects Enterprise Application RightsUser Profile

Application Right - InfoView: Log on to InfoView andview this object in the CMC

Space Ex-plorer


SpaceCreator Application Right - CMC: Log on to the CMC and view

this object in the CMC

Application Right - Web Intelligence: Create document


Administrator Application Right - CMC: Log on to the CMC and view

this object in the CMC

Application Right - Web Intelligence: Create document

SAP BusinessObjects Enterprise comes with predefined Access Levels. Youneed to allocate the appropriate Access Levels to your Explorer users sothey can perform the scheduling and export tasks that match the needs oftheir user profile.

Table 5-4: Access Levels for Explorer users

BusinessObjectsEnter-prise Access Level(s)

User Pro-file

The user can explore InformationSpaces and can export to WebIntelligence, CSV, or to an image.

View On DemandSpaceExplorer

71

Security

BusinessObjectsEnter-prise Access Level(s)

User Pro-file

The user can manage InformationSpaces and schedule.Schedule

SpaceCreator The user can explore Information

Spaces and can export to WebIntelligence, CSV, or to an image.

View On Demand

The user has full access andcontrol to SAP BusinessObjectsExplorer.

Full ControlAdministrator

Note:When configuring authorizations for Space Creators and Administrators,ensure that they have the correct access levels to Universes and UniverseConnections. The access levels state the rights they have for Universes andUniverse Connections. Having the right of Data Access for a UniverseConnection allows the user to access the Universe for Information Spacecreation.

For full information on the user rights and security levels available at the SAPBusinessObjects Enterprise level, refer to the SAP BusinessObjectsEnterprise Administrator's Guide for XI 3.1 available at: http://help.sap.com.


72

Security

http://help.sap.com

Administration

Starting and stopping the backend serversThe Explorer servers (Explorer Master server, Explorer Exploration server,Explorer Indexing server, and Explorer Search server) can be started,stopped, or restarted within the BusinessObjects Enterprise CMC.

Information:Refer to theBusinessObjects Enterprise Administrator's GuideXI 3.1 availableat: http://help.sap.com.

Customizing the web application serversettings

Explorer Web Application settings

Note:In previous releases, SAP BusinessObjects Explorer was called SAPBusinessObjects Polestar. The previous name, polestar, is used in the WebApplication settings properties file.

You can modify application settings via a single properties file:

default.settings.properties

The file is stored under the web application server directory, for example:

• C:\Program Files\BusinessObjects\Tomcat55\webapps\polestar\WEB-INF\classes\

73

Administration

http://help.sap.com

Table 6-1: Explorer Web Application settings

Default ValuesExampleDescriptionSetting

For internal use only.product.name

enThe default locale touse. For example, En-glish.

default.locale

myserver:6400The name and portnumber of your CMS.default.cms.name

true

false

Determines if the valuestored in de

fault.cms.name is dis-played in the CMSName field of the LogOn page.

show.cms.name

true

false

Disables the CMSname textbox within theLog On page. You can-not change the textboxvalue.

disable.cms.name

secEnterprise

The default log on au-thentication to use. Thevalue is displayed in theAuthentication list ofthe Log On page.

default.authentica

tion.method

sec Enter

prise, secWin

dowsNT, se

cLDAP

The values that popu-late theAuthenticationlist.authentications

74

Administration


true

false

Determines if the Au-thentication list is dis-played in the Log Onpage.

hide.authentica

tion.method

true

false

Disables the Authenti-cation list within theLog On page. You can-not change the value.

disable.authentica

tion.method

true

false

Determines if graphicaleffects are to be used.For example, afterclicking Log On the LogOn box has a graphicaleffect applied to it.

use.effects

30

100

The period of time inseconds before Explor-er times out after anoperation, such as log-ging into the system.

request.timeout

/polestar_help_The root location for theExplorer documenta-tion.

help.url

/polestar_tu

torial

The root location for theExplorer tutorial.tutorial.url

true

false

Determines if passwordencryption is to beused.

disable.password.en

cryption

75

Administration


http://serv

er:port/Open

Document/open

doc/openDocu

ment.jsp

The OpenDocumentURL of your Busines-sObjects Enterprise de-ployment. It is usedwhen a user exports In-formation Space datato a Web Intelligencequery. Setting the valueopens the query viaOpenDocument. If youdo not set the value,the query is notlaunched.

opendoc.url

Note:There are also several settings used for SAP authentication.


page 54

Configuring the server settingsYou can configure the following settings:• The number of Corba threads to improve server communication.

• The unit to use for validating bookmarks, possible values include: DAYS,MINUTES, HOURS, or WEEKS.

• The period of time (based on the unit) that a bookmark is stored. Forexample 365.

• The period of time (in milliseconds) before a session object (handled byan underlying watchdog) is deleted.

76

Administration

• The delay (in milliseconds) between each update of when slave serversinform the master server about their workload in order that the load isbalanced.

You can also configure the indexing path (in order of priority) via:• a properties file (for all servers on a single node)• the BusinessObjects Enterprise CMC server properties (for a single

indexing server on a single node)

Modifications you make to settings are implemented in the following orderof priority:• configurations made via the command line for each server within the CMC

(for a single server on a single node)• configurations made directly in a properties file (for all servers on a single

node)• configurations made via the CMC application properties (for all nodes

within your deployment cluster)

For example, if you configure the settings via a properties file on a node, theCCM settings are ignored for that node.

Configuring the path for Information Spaceindexes

You can specify where you want the indexes to be stored. You can eitherset the indexing path via the BusinessObjects Enterprise CMC or create aproperties file and specify the index path there.

Related Topics• Configuring the index path via the server properties within the CMC on

page 78• Configuring the index path via a properties file on page 78

77

Administration

Configuring the index path via the server propertieswithin the CMC

To change the indexing path for a single indexing server, edit the serverproperties within the CMC. The indexing path is dependent on your installationpath and is defaulted to:• %DefaultDataDir%/Polestar/index

1. Logon to the CMC.2. Navigate to the Explorer Indexing server you want to configure via

Servers.3. Right-click the server and click Properties.4. Within Index Files Directory:, enter your preferred path.5. Click Save.

Note:If you copy existing indexes to the new location, the Explorer IndexingServer has to be stopped.

6. Restart the server.

Configuring the index path via a properties file

You can change the indexing path for all servers on a single node, by creatingor editing a properties file.1. Create or edit a properties file named polestar.service.properties

located under:• C:\Program Files\Business Objects\Polestar12.0\

Add this entry:• index.path=C:/Index

2. Amend the value accordingly and save the file.3. Restart the servers.

Note:If you copy existing indexes, the Explorer Indexing Server has to bestopped.

78

Administration

Configuring the session timeout period

The Explorer Master Server ensures that useless resources are releasedefficiently. The session object is deleted when the associated peer stopsoperating or when the underlying network is lost. A watchdog serviceobserves all network activity.

The watchdog.timeout parameter specifies the duration of time (inmilliseconds) a live session is considered active even if the watchdog detectedno activity.

Note:It is necessary for the watchdog.timeout parameter value to be superior tothe timeout value set for the http session. If this is not the case, the Explorersession can expire even though the http session is still valid.

To change the session timeout period, an administrator can either:• Change a setting for a single node. Create or edit a properties file named

polestar.service.properties located under:• C:\Program Files\Business Objects\Polestar12.0\

Add this entry: watchdog.timeout=30, amend the value accordingly andrestart the servers.

• Add the following to the command line to configure a single server:

-watchdog.timeout 30

For example:

-loggingPath "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/" -serverkind polestarMaster-trace true -watchdog.timeout 30

Note:The default value of watchdog.timeout is 300 000 milliseconds (5 minutes).Altering the setting (especially if the specified value is too low) can have animpact on stability and even delete a valid session. This value must be smallerthan the value of workload.update.delay.

79

Administration

Configuring the request timeout limit

Timeouts may occur while using large datasets.

Workaround:It is necessary to change the default request.timeout setting (in seconds)located within:

C:\Program Files\Business Objects\Tomcat55\webapps\polestar\WEB-INF\classes\default.settings.properties

To do this:1. Open for edit the default.setting.properties file.2. Locate the request.timeout setting.3. Change the setting accordingly.

Caution:Defining a large value affects the waiting time for users.

DescriptionOption

Deactivate timeout limit-1

Maximum value for timeout.360

4. Save the file.5. Restart the Explorer servers.

The timeout is changed according to the new value.

Increasing virtual memory on the Explorerservers

The amount of virtual memory required by the Explorer servers depends onthe size of the Information Spaces being explored and indexed across yourdeployment. You can increase the amount of virtual memory available oneach server by changing the JVM heap size value as necessary:

80

Administration

• If a large number of end users need to explore large Information Spaces,it is recommended you increase the JVM heap size value on yourExploration Server(s).

• If you have a lot of users indexing, it is also recommended you increasethe JVM heap size value on your Explorer Indexing Servers.

By default, the JVM heap size value is 1 GB. In most cases, this is sufficientfor the Master server(s) and Search Server(s).

The JVM heap size has an influence on the following:• Memory garbage collection

For example, having a large heap size for the Indexing Server(s) reducesthe rate of garbage collection of memory during indexing, thus improvingperformance. If the heap size is small, scheduling spends more time tofree (and retrieve) memory than executing the required task. A heap sizeof 1.6 GB decreases the rate of garbage collecting in most cases.

• Swapping memory to hard disk

The JVM heap size value you define should always be lower than theamount of physical memory available on the server. Having a low amountof physical memory and configuring large values for the heap size of eachserver results in the swapping of memory to the hard disk. For example,if there is 2 GB of RAM, it is not efficient to provide a heap size of 1024MB for each Explorer server. SAP BusinessObjects Explorer functionscorrectly but memory swapping occurs, therefore having an impact onperformance.

On 32 bit machines, JVMs cannot address more than 2GB, globally. Becausethere are multiple memory pools with different sizes, the practical limit forthe heap size is approximately 1.5GB.

Note:The memory is configured via an INI configuration file. Do not use the servercommand line to configure the memory.

Configuring the JVM heap size value

Verify the memory limit you can configure for a server and the JVM. Theheap size is dependent on the hardware and software used. For example,

81

Administration

a Windows 32-Bit or a Windows 64-Bit operating system, the version of theJVM and the amount of physical memory installed.

Note:Do not use the server command line to configure the memory. Only use theINI configuration file.

To modify the JVM heap size value:1. Stop the Explorer server on which you want to modify the JVM heap size

value.2. Navigate to:

C:/Program Files/Business Objects/Polestar12.0/

3. Edit the INI configuration file corresponding to the server you want toconfigure.For example, if you want to increase the memory for the ExplorerExploration Server, edit the poleExpl.ini file.

4. Find the Xmx entry, type your desired memory size:-Xmx1gThe value of the heap size can be changed according to yourrequirements. For example, change the value from 1GB to 1600MB.

5. Save the file.6. Re-start the server.

The server you have configured uses a maximum JVM memory heap sizeaccording to the value within the command line.

Example:

You want to change the Explorer Master Server heap size to 1628MB:

1. Navigate to: C:/Program Files/Business Objects/Polestar12.0/.2. Edit the poleMast.ini configuration file.3. Find the Xmx entry and edit the entry as follows:

-Xmx1628m

4. Save the file.

82

Administration

Configuring the number of Corba threads

This parameter defines the maximum number of requests that can be handledsimultaneously by a given server. Most web application servers have similarsettings where you can configure the number of corba threads you want tomake available. For example:• on Apache Tomcat you specify a value for the maxThreads parameter• on IBM WebSphere you specifiy a value for the thread-maximum-size

setting in the server.xml file.

By default, the number of Corba threads is set to 100 on each of the Explorerservers (Master Server, Navigation Server, Indexing Server, Search Server).This is suitable for a simple deployment scenario, where Apache Tomcat isyour Web Application Server and you only have one Master Server, oneNavigation Server, one Indexing Server and one Search Server deployed atthe backend. Setting 1000 threads for the Explorer backend servers whenApache Tomcat only has 100 is of no use and could even be harmful becauseit would cause many context switches and thus impact performance.

In the case of a complex deployment scenario, however, it may be necessaryto either increase this value or add more backend nodes. For example, ifyour deployment includes multiple WebSphere instances behind a loadbalancer, with the thread-maximum-size parameter set to its maximum valueof 1000, it would not make sense to keep the default 100 thread pool sizefor the Explorer servers, because this would merely push the bottleneck tothe backend.

The absolute value depends on the expected number of concurrent sessions.It is necessary to adjust the concurrency level consistently throughout theentire stack in order to maximize throughput on all nodes.

Configuring the number of Corba threads via theserver command line within the CMC

To change the number of Corba threads for a single server, edit the serverproperties within the BusinessObjects Enterprise CMC.1. Logon to the CMC.2. Navigate to the Polestar server you want to configure via Servers.

83

Administration

3. Right-click the server and click Properties.4. Within Command Line Parameters, add the following:

-nb_threads 150

For example:

-loggingPath "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/" -serverkind polestarIndexing-trace true -nb_threads 150

5. Click Save.

Configuring the number of Corba threads via aproperties file

You can change the number of Corba servers for all servers on a singlenode, by creating or editing a properties files.1. Create or edit a properties file named polestar.service.properties


2. Add this entry: nb_threads=150.3. Amend the value accordingly and save the file.4. Restart the servers.

Configuring the number of Corba threads via the CMC

To change the number of Corba threads via the CMC, amend the value withinthe CMC administration page. In this case, the value is taken into accountby all slave nodes.

1. Logon to the CMC.2. Navigate to Manage > Applications.3. Right-click Polestar and click Properties.4. Change the Number of threads: value and click Save.

84

Administration

Configuring the bookmark validity period

Configuring the bookmark validity period via the servercommand line within the CMC

To change the Explorer validity period for a single server, edit the serverproperties within the BusinessObjects Enterprise CMC.

1. Logon to the BusinessObjects Enterprise CMC.2. Navigate to the Explorer server you want to configure via Servers.3. Right-click the server and click Properties.4. Within Command Line Parameters, add the following:

-bookmark.validity.time 365 -bookmark.validity.unit DAYS

For example:

-loggingPath "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/" -serverkind polestarIndexing-trace true -bookmark.validity.time 365 -bookmark.validity.unit DAYS

5. Click Save.

Configuring the bookmark validity period via aproperties file

You can change the Explorer bookmark validity for all servers on a singlenode, by creating or editing a properties files.1. Create or edit a properties file named polestar.service.properties


2. Add the following entries.

bookmark.validity.time=365

bookmark.validity.unit=DAYS

85

Administration

3. Amend the value accordingly and save the file.4. Restart the servers.

Configuring the bookmark validity period via the CMC

To change the bookmark validation period via the BusinessObjects EnterpriseCMC, amend the value within the CMC administration page. In this case,the value is taken into account by all slave nodes.1. Logon to the BusinessObjects Enterprise CMC.2. Navigate to Manage > Applications.3. Right-click Polestar and click Properties.4. Change the Bookmark validity: values and click Save.

Configuring the workload update setting forload balancing

The workload is balanced by ensuring that servers with the least load havea higher job priority. Slave servers (within a cluster) ensure that the ExplorerMaster Server is periodically updated with their workload costs.

The workload.update.delay parameter specifies the duration of time (inmilliseconds) between updates to the Explorer Master Server.

To change the workload update delay period, an administrator can either:• Change a setting for a single node. Create or edit a properties file named

polestar.service.properties located under:• C:\Program Files\Business Objects\Polestar12.0\

Add this entry: workload.update.delay=30, amend the value accordingly,and restart the servers.

• Add the following to the command line to configure a single server:

-workload.update.delay 30

For example:

86

Administration

-loggingPath "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/" -serverkind polestarMaster-trace true -workload.update.delay 30

Note:The default value of workload.update.delay is 15 000 milliseconds. Alteringthe setting (especially if the specified value is too low) can have an impacton network traffic and performance. The value must be significantly smallerthan the value of watchdog.timeout.

Logging methodsThere are two SAP BusinessObjects Explorer logging methods, each trackingdifferent operations:1. Server logging.

You can trace the activity of the backend servers. Logging is appendedto a file where its name is automatically generated at creation time. Forexample:

• C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\Logging\PolestarServer_XXXXX.polestarSearch=PolestarSearch_XXXXXXXX_XXXXXX.log

This file logs the server operations by using log4j. By default, ERROR tracingis activated.

2. Web application logging.

By using your web application server (such as Apache Tomcat) loggingservices, you can log the application operations. For example, via theTomcat configuration, you can also change the logging level and changethe logging path. By default, log files are stored in the Tomcat logsdirectory:

C:\Program Files\Business Objects\Tomcat55\logs\

You can also view logs by running Tomcat via a command line such asCommand Prompt.

For detailed information on Tomcat logging, see:

87

Administration

http://tomcat.apache.org/tomcat-6.0-doc/logging.html

For information on other web application server logging facilities, refer tothe web application server documentation.

Related Topics• Configuring the Explorer server log files on page 88• Web application logging on page 90

Configuring the Explorer server log files

By default, server logging within SAP BusinessObjects Explorer is activated.It is configured to only log errors. To activate other trace levels for serverlogging:

1. Open the BusinessObjects Enterprise CMC, navigate to the "Servers List"and locate the server you want to apply logging to.Ensure that the server has been stopped.

2. Right-click the server and click Properties.The Properties dialog appears.

3. Locate the Command Line Parameters: textbox.4. Type the following if it does not already exist:

• -loggingPath "C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/Logging/" -trace true

Note:The loggingPath value is the location to place the output log file and thetrace value activates logging. By default, if the trace value is false,only errors are logged.

5. Click Save to save your changes.6. Start the server.

Logs and traces are applied to a log file in the following directory:

• C:\Program Files\Business Objects\BusinessObjects Enterprise12.0\Logging\

The name of the file is generated on creation and is based on the name ofthe server and when the server was started. For example:

88

Administration

Server_XXXXXXXX_XXXXXX.log

Overriding Polestar server logging methods

To override the existing logging method:

1. Create a file called polestar.log4j.properties and store it under thefollowing directory:C:\Program Files\Business Objects\Polestar12.0\

2. Enter your desired Log4j logging content to the file. For example:

log4j.debug=truelog4j.rootLogger=WARN, A1

log4j.appender.A1=org.apache.log4j.ConsoleAppenderlog4j.appender.A1.layout=org.apache.log4j.PatternLayoutlog4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p%c %x - %m%n

log4j.appender.A2=org.apache.log4j.net.SocketAppenderlog4j.appender.A2.remoteHost=localhostlog4j.appender.A2.port=4567log4j.appender.A2.locationInfo=falselog4j.appender.A2.reconnectionDelay=10000

To filter, enter the following line, and edit it appropriately:

log4j.logger.package/class=level

You can log packages and classes using the following levels: INFO,WARN, ERROR, FATAL

For further information on Log4j logging, refer to: http://logging.apache.org/log4j/.

3. Restart the servers.

Customized logging for the servers is applied.

89

Administration

Web application logging

Note:This example is for Apache Tomcat under Windows. For specific logginginformation for other web application servers, refer to the web applicationserver documentation.

To activate and amend the log4j logging:

1. Open the log4j.properties file, located at:C:\Program Files\BusinessObjects\Tomcat55\webapps\polestar\WEB-INF\classes\

2. Edit the logging levels you want use (such as ERROR) for SAPBusinessObjects Explorer within the file by following the guidelines locatedat:http://logging.apache.org/log4j/

3. Save your changes and close the file.

Logs and traces are applied to the following log file:

C:\Program Files\Business Objects\Tomcat55\logs\stdout.log

Indexing best practicesPerformance during indexing is dependent upon the hardware (hard drive,memory and JVM heap size) number of concurrent users, number ofInformation Spaces being indexed concurrently, and the size of thoseInformation Spaces.

If users only access SAP BusinessObjects Explorer during working hours,schedule the indexing over night, users are not impacted by indexing. If youhave medium sized Information Spaces and concurrent user access is notexpected, then a single high-end machine is considered to be efficient.

However if you have many users indexing and exploring large InformationSpaces constantly, ensure the following:• SAP BusinessObjects Explorer is deployed in a cluster with additional

machines each having extra servers

90

Administration

The number of machines deployed is dependent on the number ofexpected concurrent users and the size of the Information Spaces.

• fast hard disk drives are installed on each machine• there is a large amount of memory on each machine (especially on the

host machine with the Master Server)• the JVM heap size for each server on each machine is configured correctly

according to available memory

Scheduling Information Spaces for indexing does not impact performance ifyou have deployed, installed, and configured everything correctly.

91

Administration

92

Administration

More Information

LocationInformation Resource

http://www.sap.comSAP BusinessObjectsproduct information

Select http://help.sap.com > SAP BusinessObjects.

You can access the most up-to-date documentation cov-ering all SAP BusinessObjects products and their deploy-ment at the SAP Help Portal. You can download PDFversions or installable HTML libraries.

Certain guides are stored on the SAP Service Marketplaceand are not available from the SAP Help Portal. Theseguides are listed on the Help Portal accompanied by alink to the SAP Service Marketplace. Customers with amaintenance agreement have an authorized user ID toaccess this site. To obtain an ID, contact your customersupport representative.

SAP Help Portal

93

More Information

http://www.sap.com

http://help.sap.com/


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

• Installation guides: https://service.sap.com/bosap-instguides

• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installationguides, upgrade and migration guides, deployment guides,release notes and Supported Platforms documents. Cus-tomers with a maintenance agreement have an authorizeduser ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to theSAP Service Marketplace from the SAP Help Portal, usethe menu in the navigation pane on the left to locate thecategory containing the documentation you want to ac-cess.

SAP Service Marketplace

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

SAP BusinessObjects ar-ticles on the SAP Commu-nity Network

https://service.sap.com/notes

These notes were formerly known as Knowledge Basearticles.

Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAPCommunity Network

94

More Information


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

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

http://service.sap.com/releasenotes

http://service.sap.com/releasenotes

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums


http://www.sap.com/services/education

From traditional classroom learning to targeted e-learningseminars, we can offer a training package to suit yourlearning needs and preferred learning style.

Training


The SAP Support Portal contains information about Cus-tomer Support programs and services. It also has links toa wide range of technical information and downloads.Customers with a maintenance agreement have an autho-rized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support

http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertiseis available in topics such as relational and multidimensional databases, connectivity, database design tools, andcustomized embedding technology.

Consulting

95

More Information

http://www.sap.com/services/education




96

More Information

IndexAAIX

installation 30AIX uninstall 48application servers 15architecture

deployment 19auditing 11authentication

trusted 63

Bbackup blades 37blades

back up BW Accelerator 37BusinessObjects Enterprise 11BW Accelerator 10

CCCM

servers 73CMC 11

BWA connection 39configuring number of Corba threads 84configuring users 66, 68profile permissions 68server properties

bookmark validation period configuration85, 86

configuring number of Corba threads 83index path configuration 78

CMS 11configuration

bookmark validation 76bookmark validation period 86BWA connection 39indexing path 76, 78SAP authentication 38, 54server communication 76, 83, 84, 85

configuration (continued)server memory 80, 81session timeout period

watchdog.timeout 79watchdog timeout

peer session 76web application settings 54, 73workload 86workload update delay

load balancing 76cookies 45Corba

configuring number of threads 83, 84corba threads

configuring 83custom fonts 40

Ddefault.settings.properties 54, 73deployment

complex environment 20for improved exploration 17for improved indexing

scheduling 90deployment scenarios 19

EExplorer

installationmanual 33wdeploy 33

overview 9

Ffonts 40

97

HHome tab

welcome page 45, 46

IInfoCube 10Information Space data 10installation

AIX 30Linux SUSE 31MS Windows 26

installation package 25installation prerequisites 23

JJava 2 security

WebSphere 44JVM heap size 80

KKerberos 60

LLDAP 61LDAP SSO

SiteMinder 61Linux SUSE

installation 31Linux uninstall 48load balancing 86logging off 45, 46logging on

authenticationEnterprise 45LDAP 45Windows AD 45Windows NT 45

log on credentials 45, 46Log On page 45, 46SAP authentication 46server URL 45, 46

logslog4j 88, 89, 90server logging 87servers

overriding default 89web application 90web application logging 87

MMS Windows

installation 26

Ooperating systems 15

Ppolestar.service.properties file

bookmark validation period configuration85

configuring number of Corba threads 84index path configuration 78

prerequisitesinstallation 23

Rrequest timeout 80restarting servers 73

SSAP

authentication 46SAP authentication 38session cookies 45SIA 20SiteMinder 61SSO 56

activating 56LDAP 61WinAD 59, 60

starting serversExploration Server 73

98

Index

starting servers (continued)Indexing Server 73Master Server 73Search Server 73

stopping serversExploration Server 73Indexing Server 73Master Server 73Search Server 73

supported platforms 15SUSE uninstall 48

Ttimeout

configure for large data sets 80trusted authentication 63

Uuninstall

IBM AIX 48

uninstall (continued)Linux SUSE 48MS Windows 47

universes 10user profiles

Administrator 68Space creator 68Space explorer 68user rights 68

VVintela 59

WWebSphere

Java 2 security 44WinAD 59, 60WinAd SSO

Kerberos 60Vintela 59

99

Index

100

Index

Documents

exp31sp1_inst-depl-adm_en