Business objects VIEWS XI RELEASE 2 User Manual

BusinessObjects Voyager
Administrator’s Guide

BusinessObjects Voyager XI

Patents

Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.

Trademarks

Copyright

Third-party
contributors

Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.

Copyright © 2006 Business Objects. All rights reserved.

Business Objects products in this release may contain redistributions of software licensed
from third-party contributors. Some of these individual components may also be available
under alternative licenses. A partial listing of third-party contributors that have requested or
permitted acknowledgments, as well as required notices, can be found at:

http://www.businessobjects.com/thirdparty

Contents

Chapter 1 Introduction to Voyager 7

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2 About BusinessObjects Voyager 9

Voyager components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Data sources and user access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Voyager web-based analysis client . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Voyager Multi-Dimensional Analysis Services server . . . . . . . . . . . . . 11

Voyager and BusinessObjects Enterprise architecture . . . . . . . . . . . . 11

Installing Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installation to a system using SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing Voyager alongside OLAP Intelligence . . . . . . . . . . . . . . . . . 12

Post-installation configuration of fonts . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing sample data cubes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3 Administering the Multi-Dimensional Analysis Services Server 15

Configuring the MDAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Server administration tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Microsoft Management Console (MMC) . . . . . . . . . . . . . . . . . . . . 16

Central Management Console (CMC) . . . . . . . . . . . . . . . . . . . . . . 17

Central Configuration Manager (CCM) . . . . . . . . . . . . . . . . . . . . . 17

Solaris command prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Administration tools and functionality . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Starting and stopping the MDAS server . . . . . . . . . . . . . . . . . . . . . . . . 18

Starting and stopping the MDAS server from the Microsoft

Management Console (MMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

BusinessObjects Voyager Administrator’s Guide 3

Contents

Starting and stopping the MDAS server from the Central Management

Console (CMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Starting and stopping the MDAS server from Central Configuration

Manager (CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Starting and stopping the MDAS server from Solaris . . . . . . . . . . . 19

Restarting the MDAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Restarting the MDAS server from the Microsoft Management Console

(MMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Restarting the MDAS server from the Central Management Console

(CMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Restarting the MDAS server from Central Configuration Manager

(CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Restarting the MDAS server from Solaris . . . . . . . . . . . . . . . . . . .20

Changing the MDAS server startup type . . . . . . . . . . . . . . . . . . . . . . . .20

Changing the MDAS server startup type from the Microsoft

Management Console (MMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Changing the MDAS server startup type from the Central

Configuration Manager (CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Changing the Logon As account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Changing the Logon As account from the Microsoft Management

Console (MMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Changing the Logon As account from the Central Configuration

Manager (CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Enabling and disabling an MDAS server . . . . . . . . . . . . . . . . . . . . . . . .22

Enabling and disabling the MDAS server from the Central

Management Console (CMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Enabling and disabling the MDAS server from Central Configuration

Manager (CCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Enabling and disabling the MDAS server from Solaris . . . . . . . . . .23

Adding and removing MDAS instances . . . . . . . . . . . . . . . . . . . . . . . . .24

Adding an MDAS instance from the Central Management Console

(CMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Deleting an MDAS instance from the Central Management Console

(CMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

4 BusinessObjects Voyager Administrator’s Guide

Contents

Standard options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Setting user access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Configuring the MDAS for Secure Sockets Layer (SSL) . . . . . . . . . . . 27

The Java service wrapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Single or multiple MDASServer.conf files . . . . . . . . . . . . . . . . . . . 29

Command line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using the CMC to manage MDAS server properties and metrics . . . . 31

Set properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

View metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Manage rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Clustering MDAS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Starting and stopping Tomcat in Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configuration files for the MDAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Wrapper service configuration file—MDASServer.conf . . . . . . . . . . . . 34

MDASServer.conf sample file listing . . . . . . . . . . . . . . . . . . . . . . . 34

MDAS server configuration file—mdas.properties . . . . . . . . . . . . . . . . 39

mdas.properties file listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Enable MDAS logging—mdas.log4j.properties . . . . . . . . . . . . . . . . . . 41

mdas.log4j.properties file listing . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Understanding Voyager and Microsoft Analysis Services Security 43

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

SQL Server Analysis Services Security Architecture . . . . . . . . . . . . . . . . . 44

Configuring Security in a Multi-tiered Application Environment . . . . . . . . . 44

Configuring how authentication information is passed to SSAS . . . . . . . . 46

Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Single sign-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Specified User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 5 Administering BusinessObjects Voyager Connections 49

Creating OLAP data source connections on Windows . . . . . . . . . . . . . . . 50

Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

BusinessObjects Voyager Administrator’s Guide 5

Contents

Creating a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Editing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Deleting a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Data source connection settings on Windows . . . . . . . . . . . . . . . . . . . . . . .54

Connection settings for Microsoft OLAP data sources . . . . . . . . . . . . .55

Connection settings for Essbase/DB2 OLAP data sources . . . . . . . . .55

Changing Voyager workspace properties on Windows . . . . . . . . . . . . . . . .56

Chapter 6 Managing Voyager Workspaces in the CMC 57

Managing Voyager workspaces in the Central Management Console . . . .58

Editing the name, description, and keywords of a Voyager workspace . . . 58

Changing access to Voyager workspaces . . . . . . . . . . . . . . . . . . . . . . . . .59

Seeing a list of connections linked to the workspace . . . . . . . . . . . . . . . . . 59

Appendix A Business Objects Information Resources 61

Documentation and information services . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

What’s in the documentation set? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Where is the documentation? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Documentation from the products . . . . . . . . . . . . . . . . . . . . . . . . .62

Documentation on the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Documentation on the product CD . . . . . . . . . . . . . . . . . . . . . . . . . 62

Send us your feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Customer support, consulting and training . . . . . . . . . . . . . . . . . . . . . . . . .63

How can we support you? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Online Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Looking for the best deployment solution for your company? . . . . . . . .64

Looking for training options? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5

Index 67

6 BusinessObjects Voyager Administrator’s Guide

Introduction to Vo yager

chapter

Introduction to Voyager

1

About this guide

About this guide

This guide shows you how to administer a Voyager installation.
For a description of the BusinessObjects Enterprise components and

installation instructions, see the BusinessObjects Enterprise Installation
Guide.

For installation instructions for Voyager, see the BusinessObjects
Enterprise™ XI Release 2 Installation Guide.

Who should read this guide

This guide is intended for system administrators. You need administrator
rights to administer BusinessObjects Voyager and BusinessObjects
Enterprise.

Disclaimer

Some third-party products discussed in this guide were not fully tested in
conjunction with BusinessObjects Enterprise prior to its release. Officially
supported BusinessObjects Enterprise platforms are listed in the text file

Platforms.txt. This file is found in the root folder of the BusinessObjects

Enterprise product distribution as well as in the Knowledge Base article
c2009003, which is more current (search for this article number at http://

support.businessobjects.com/search).

The third-party information included in this guide is provided as a courtesy to
assist customers with the configuration of the Business Objects product in
conjunction with these third-party platforms. The third-party information was
current at the time this documentation was written, but Business Objects does
not guarantee its accuracy. Contact the third-p arty vendor if you have specific
questions about their technology.

In the event that issues arise with an unsupported configuration, there is no
escalation support; however, the issues will be considered during the
development of the next generation of the product.

Business Objects information resources

For more information and assistance, see Appendix A: Business Objects

Information Resources. This appendix describes the Business Objects

documentation, customer support, training, and consulting services, with links
to online resources.

8 BusinessObjects Voyager Administrator’s Guide

About BusinessObjects Voyager

chapter

About BusinessObjects Voyager

2

Voyager components

Voyager components

Voyager is a query and analysis tool for working with multi-dimensional data.
Users access Voyager from within the BusinessObjects Enterprise InfoView
portal. Users can create new analysis workspaces, and view and edit
workspaces that have been saved to the BusinessObjects Enterprise
repository.

Voyager comprises these components:

• Voyager web-based analysis client.

• Voyager Multi-Dimensional Analysis Services server.

Data sources and user access

In order for the Voyager system to work there must also be a connection to a
data source, such as the Microsoft Analysis Services (MSAS), IBM DB2
OLAP, SAP BW, or Hyperion Essbase. Without a data source connection,
Voyager is not visible to users in InfoView. For this reason, you must create a
connection to data.

Sample data is provided so that you can create connections to data
immediately. Users can become acquainted with Voyager more quickly (and
without live data).

Note: Be sure to grant appropriate access rights to any data sources that you

want available to users in Voyager. If a user has no right s to any V oyager dat a
connection, then Voyager is not available in InfoView.

For more information about creating a connection to the sample data cubes,
see “Installing sample data cubes” on page 13.

For more information about how to use the Central Management Console to
set access levels for various components of the product suite, including
Voyager elements such as workspaces and connections, see the chapter
“Rights in the CMC” in the BusinessObjects Enterprise Administration Guide.

Voyager web-based analysis client

Voyager let s data analysts in your organization create V oyager workspaces to
analyze your organization’s multidimensional data. Analysts can save and
share their workspaces in the BusinessObjects Enterprise repository, so that
other analysts or business users can work with those analyses over any web
connection.

10 BusinessObjects Voyager Administrator’s Guide

About BusinessObjects Voyager

Voyager components

Users need only an internet connection, web browser software, and sufficient
rights, to access the BusinessObjects Enterprise system and create or view
Voyager workspaces.

Voyager Multi-Dimensional Analysis Services server

Voyager includes a Java BusinessObjects Enterprise server called the Multi­Dimensional Analysis Services server (MDAS). The MDAS server has
connections to the underlying data layer:

2

Voyager and BusinessObjects Enterprise architecture

Voyager fits into the broader BusinessObjects Enterprise architecture as a
client-server setup with connections at the server and database level to other
BusinessObjects Enterprise servers.

BusinessObjects Voyager Administrator’s Guide 11

About BusinessObjects Voyager

2

Installing Voyager

Installing Voyager

Voyager is installed as part of the larger BusinessObjects Enterprise suite of
products. For more information about installing products in that suite,
including Voyager, see the BusinessObjects Enterprise™ XI Release 2
Installation Guide.

Note: After installing V oyager, you may have to configure the

to have properly-rendered charts and PDF exports. For details on how to do
this, see “Post-installation configuration of fonts” on page 12.

Installation to a system using SAP

You must provide a key code for the SAP Integration Kit to enable SAP
connectivity in the Voyager application. If you want to run the MDA services
on a machine where the SAP Integration Kit is not installed, add the SAP
Integration Kit key code to that machine by running the License Manager tool.

Installing Voyager alongside OLAP Intelligence

If your organization is already using the existing Business Objects OLAP tool,
OLAP Intelligence, you can install Voyager alongside OLAP Intelligence
without problem. The two products can be used simultaneously.

fonts.xml file

Post-installation configuration of fonts

If you need to use a Unicode font such as Japanese, or if you are running
Solaris, you must make a manual change to view charts and PDF exports
correctly . The font being used can be changed by editing
located on Windows in this folder:

\Program Files\Business Objects\BusinessObjects Enterprise

11.5\win32_x86\com\businessobjects\multidimensional\serv
ices

<?xml version="1.0" encoding="UTF-8"?>
<!-- MDAS Font Configuration Replace paths to font with the

correct path for the installed system -->
<fon:Fonts

universalFontName="MS Mincho"
xmlns:fon="http://www.businessobjects.com/xml/schema
/analysis/ multidimensional/services/fonts">

<fon:Font

name="Arial"

12 BusinessObjects Voyager Administrator’s Guide

fonts.xml which is

caption="Arial"
resourceUrl="file://C:/WINDOWS/Fonts/ARIAL.TTF"
type="TrueType"
locale="en" />

<fon:Font

name="MS Mincho"
caption="MS Mincho"
resourceUrl="file://C:/WINDOWS/Fonts/MSMINCHO.TTC"
type="TrueTypeCollection"
locale="ja" />

<fon:Font

name="MingLiU"
caption="MingLiU"
resourceUrl="file://C:/WINDOWS/Fonts/mingliu.ttc"
type="TrueTypeCollection"
locale="chs" />

</fon:Fonts>

Add the new font definition to fonts.xml and then set the

universalFontName attribute in fonts.xml to the name of the new font.

Installing sample data cubes

BusinessObjects Voyager is supplied with four sample data cubes which can
be optionally installed to help users learn how to use the product without the
need to have an installed OLAP server. Installation is a manual process. The
sample cubes are generically referred to as “local cube” files, or
and were created by Microsoft Analysis Services 2000. To access these
cubes you must first install the Microsoft Pivot Table Services.

About BusinessObjects Voyager

Installing Voyager

.cub files,

2

To install sample dat a cubes

!

1. Download the Microsoft Pivot Table Services:

http://download.microsoft.com/download/4/4/D/44DBDE61-B385-4FC2­A67D-48053B8F9FAD/ptslite.exe

-or­Search the Microsoft web site http://www.microsoft.com for “Microsoft

SQL Server 2000 PivotTable Services” and select the Pivot Table
Services for download.

Note: If you have a distributed setup running more than one MDAS

server, you must inst all the Pivot Table Services on each MDAS server in
your Voyager system.

2. In the BusinessObjects Enterprise™ XI Release 2 installation files, open

the samples folder and then open the appropriate locale folder to find the
four sample

.cub files.

BusinessObjects Voyager Administrator’s Guide 13

About BusinessObjects Voyager

2

Installing Voyager

3. Logon to the BusinessObjects Central Management Console as an

4. Click Voyager Connections and then New.

5. Enter a name for the connection and an optional description.

6. For the provider choose “Microsoft OLE DB Provider for OLAP Services

7. Enter the full path name to the appropriate

8. Click Save to store the connection.

9. Repeat steps 4 through 8 for each of the other three sample cubes.

Copy these four .cub files to a network shared folder that can be
accessed by all users.

administrator.

8.0” and "Cube File" as the server type.

.cub file and then click

Connect to test the connection.

14 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

chapter

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

Configuring the MDAS server

The Multi-Dimensional Analysis Services server is a new server that is fully
integrated with BusinessObjects Enterprise XI Release 2. Like the other
BusinessObjects Enterprise servers, it registers itself with the Central
Management Server (CMS). Once registered, its services are available for
consumption by other servers or client applications that communicate via the
BusinessObjects Enterprise framework.

The Multi-Dimensional Analysis Services server provides BusinessObjects
Enterprise client applications such as BusinessObjects Voyager with an
extensible and efficient framework for accessing multi-dimensional (OLAP)
data. It not only provides access to multi-dimensional data but also converts
the raw data into various XML packages, which the requesting client
application then renders into a specific presentation format: Excel
spreadsheet, PDF, or Voyager crosstabs and charts.

Server administration tools

There are three tools you can (and in some cases must) use to administer the
MDAS and other servers. Some functionality is common between all tools.
For example, you can start and stop MDAS servers from any of the three
administration tools. You cannot perform all functions from all tools, though,
and so you must sometimes use a specific tool for a specific purpose.

Microsoft Management Console (MMC)

The Microsoft Management Console (MMC) is a host application that
contains a set of administrative tools you can use to administer services and
other system components. You can use the MMC to perform several
operations on the MDAS server:

• “Starting and stopping the MDAS server from the Microsoft Management

Console (MMC)” on page 18.

• “Restarting the MDAS server from the Microsoft Management Console

(MMC)” on page 19.

• “Changing the MDAS server startup type from the Microsoft Management

Console (MMC)” on page 21.

• “Changing the Logon As account from the Microsoft Management

Console (MMC)” on page 22.

16 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Central Management Console (CMC)

The Central Management Console (CMC) is a web-based administration tool
for managing Voyager connections and workspaces, user accounts,
published Crystal reports and OLAP reports, OLAP connections, folders,
server settings, and license keys. You have to be a BusinessObjects
Enterprise administrator to run the CMC. You can use the CMC to perform
some operations on the MDAS server:

• “Starting and stopping the MDAS server from the Central Management

Console (CMC)” on page 18.

• “Restarting the MDAS server from the Central Management Console

(CMC)” on page 20.

• “Enabling and disabling the MDAS server from the Central Management

Console (CMC)” on page 23.

Central Configuration Manager (CCM)

The Central Configuration Manager (CCM) is a server-management tool that
allows you to configure servers for your BusinessObjects products on
Windows. You can use the CCM to perform all operations on the MDAS
server:

• “Starting and stopping the MDAS server from Central Configuration

Manager (CCM)” on page 19.

• “Restarting the MDAS server from Central Configuration Manager

(CCM)” on page 20.

• “Changing the MDAS server startup type from the Central Configuration

Manager (CCM)” on page 21.

• “Changing the Logon As account from the Central Configuration Manager

(CCM)” on page 22.

• “Enabling and disabling the MDAS server from the Central Management

Console (CMC)” on page 23.

Configuring the MDAS server

3

Solaris command prompt

You can also perform some server management using command-line
commands from Solaris:

• “Starting and stopping the MDAS server from Solaris” on page 19.

• “Restarting the MDAS server from Solaris” on page 20.

• “Enabling and disabling the MDAS server from Solaris” on page 23.

BusinessObjects Voyager Administrator’s Guide 17

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

Administration tools and functionality

This table represents a grid of administration tools and the MDAS server
administration functionality each provides:

Function MMC CMC CCM Solaris

Start and Stop X X X X
Restart X X X X
Change startup type X X
Change Logon As account X X
Enable and Disable X X X

Starting and stopping the MDAS server

The MDAS server is a Java application. It uses a wrapper technology that
makes it possible to install a Java application as a Windows NT service.
When the MDAS server is installed on Windows, it can therefore be started
and stopped like any other Windows service.

Starting and stopping the MDAS server from the Microsoft Management Console (MMC)

!

To start or stop the MDAS Server from the MMC

1. On the Start menu, click Administrative Tools > Services to open the

Microsoft Management Console (MMC).

2. Click the MDAS service you want to start or stop.

3. Click the Start or Stop button, depending on which action you want to

perform.

Note: If the Start button is disabled and the MDAS server is not already

started, you must enable it first.

Starting and stopping the MDAS server from the Central Management Console (CMC)

!

To start or stop the MDAS Server from the CMC

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

18 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

4. Click Servers to view a list of servers you can administer.

5. Locate the MDAS server that you want to start or stop, and select its

check box.

6. Click the Start or Stop button, depending on which action you want to

perform.

Starting and stopping the MDAS server from Central Configurat ion Manager (CCM)

!

To start or stop the MDAS Server from the CCM

1. On the Start menu, click BusinessObjects Enterprise > Central

Configuration Manager.

2. Within the CCM (Central Configuration Manager), click MDAS Server

and then click the Start button.

3. Click the Refresh button until the Status column indicates Running.

Starting and stopping the MDAS server from Solaris

!

To start or stop the MDAS Server in Solaris

1. From Solaris, change to the /bobje directory.

2. To start the MDAS server, enter the command:

./ccm.sh -start mdas -cms <server name>:<cms port>

3. To stop the MDAS server, enter the command:

./ccm.sh -stop mdas -cms <server name>:<cms port>

Note: If only one CMS is running on the server, the -cms <server

name>:<cms port> parameter can be omitted.

3

Restarting the MDAS server

There may be occasions when you need to restart the MDAS (Multi
Dimensional Analysis Services) server. Restarting a server means stopping it
temporarily, then starting it again. This is necessary in some cases where the
server configuration files have changed and need to be reloaded during
server startup.

Restarting the MDAS server from the Microsof t Managemen t Console (MMC)

!

To restart the MDAS Server from the MMC

1. On the Start menu, click Administrative Tools > Services to open the

Microsoft Management Console (MMC).

BusinessObjects Voyager Administrator’s Guide 19

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

2. Click the MDAS service you want to restart.

3. Click the Restart button.

Restarting the MDAS server from the Central Management Console (CMC)

!

To restart the MDAS Server from the CMC

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

4. Click Servers to view a list of servers you can administer.

5. Locate the MDAS server that you want to start or stop, and select its

check box.

6. Click the Restart button.

Restarting the MDAS server from Central Configuration Manager (CCM)

!

To restart the MDAS Server in from the CCM

1. On the Start menu, click BusinessObjects Enterprise > Central

Configuration Manager.

2. Within the CCM (Central Configuration Manager), click MDAS Server

and then click the Restart button.

3. Click the Refresh button until the Status column indicates Running.

Restarting the MDAS server from Solaris

!

To restart the MDAS Server in Solaris

1. From Solaris, change to the /bobje directory.

2. To restart the MDAS server, enter the command:

./ccm.sh -restart mdas -cms <server name>:<cms port>

Note: If only one CMS is running on the server, the -cms <server

name>:<cms port>

parameter can be omitted.

Changing the MDAS server startup type

You can control how the MDAS server starts on your system. In terms of
scalability, this is useful if you have more than one MDAS server and want to
control which servers start, depending on what resources are needed to
serve changing client needs.

20 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

Changing the MDAS server startup type from the Microsoft Management Console (MMC)

!

To change the MDAS server startup type from the MMC

1. On the Start menu, click Administrative Tools > Services to open the

Microsoft Management Console (MMC).

2. Click the MDAS service you want to administer.

3. Click the Properties button to open the Properties dialog box.

4. Click the General tab.

5. In the Startup Type drop down, indicate the startup type you want:

• Automatic: The service starts when the Windows system starts.

• Manual: The service starts when a user or other service indicates.

• Disabled: The service cannot start.

6. Click Apply or OK.

Changing the MDAS server startup type from the Central Configuration Manager (CCM)

!

To change the MDAS server startup type from the CCM

1. On the Start menu, click BusinessObjects Enterprise > Central

Configuration Manager.

2. From the CCM (Central Configuration Manager), click MDAS Server and

then click the Properties button.

3. In the dialog box that opens, click the Properties tab.

4. In the Startup Type field, indicate the type of startup you want the MDAS

server to follow (Automatic, Disabled, Manual).

5. Click Apply or OK.

3

Changing the Logon As account

By default, logon attempts to the MDAS server are made as the user currently
logged onto the Windows machine that hosts the server. This the standard
logon protocol for most servers.

Y ou can, however, change the user name and password that is used to log on
to the MDAS server by changing the Logon As account.

BusinessObjects Voyager Administrator’s Guide 21

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

Changing the Logon As account from the Microsoft Management Console (MMC)

!

T o change the Logon As account from the MMC

1. On the Start menu, click Administrative Tools > Services to open the

Microsoft Management Console (MMC).

2. Click the MDAS service you want to administer.

3. Click the Properties button to open the Properties dialog box.

4. Click the Log on tab.

5. For the Log on as: type, select one of the two options:

• Local System account: Log on to the server as the user currently

logged onto the Windows machine hosting the server.

• This account: Log on to the server using a different user name and

password. If you select this option, you must also provide the user
name and password to use to log on to the server with.

Changing the Logon As account from the Central Configuration Manager (CCM)

!

T o change the Logon As account from the CCM

1. On the Start menu, click BusinessObjects Enterprise > Central

Configuration Manager.

2. From the CCM (Central Configuration Manager), click MDAS Server and

then click the Properties button.

3. From the dialog box that opens, click the Properties tab.

4. In the Log On As area, check the System Account check box if you want

to log on to the server as the account that is logged into the system at the
time the server logon occurs.

If you uncheck this box, you must supply a user name and password to
use as the logon to the server.

Enabling and disabling an MDAS server

When you disable a BusinessObjects Enterprise server, you prevent it from
receiving and responding to new requests, but you do not actually stop the
server process. This is especially useful when you want to allow a server to
finish processing all of its current requests before you stop it completely.

When you disable an MDAS instance, the service still continues running as a
service, but will not accept any new requests from the Voyager application or
Central Management Console (CMC).

22 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

When you enable a running instance of an MDAS server, the MDAS instance
accepts new requests from the Voyager application or CMC; for example,
creating a connection.

Enabling and disabling the MDAS server from the Central Management Console (CMC)

!

To enable and disable the MDAS Server from the CMC

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

4. Click Servers to view a list of servers you can administer.

5. Locate the MDAS server that you want to start or stop, and select its

check box.

6. Click the Enable or Disable button.

Enabling and disabling the MDAS server from Central Configuration Manager (CCM)

!

To enable and disable the MDAS Server from the CCM

1. On the Start menu, click BusinessObjects Enterprise > Central

Configuration Manager.

2. Within the CCM (Central Configuration Manager), click MDAS Server

and then click the Enable or Disable button.

3

Enabling and disabling the MDAS server from Solaris

!

To enable or disable the MDAS Server in Solaris

1. From Solaris, change to the /bobje directory.

2. To enable the MDAS server, enter the command:

./ccm.sh -enable mdas -cms <server name>:<cms port>

3. To disable the MDAS server, enter the command:

./ccm.sh -disable mdas -cms <server name>:<cms port>

Note: If only one CMS is running on the server, the -cms <server

name>:<cms port>

parameter can be omitted.

BusinessObjects Voyager Administrator’s Guide 23

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

Adding and removing MDAS instances

Y ou can create more than one running instance of an MDAS server. Once you
have added a new instance of the MDAS server, you must start and enable it.
For more information on starting the MDAS server, see “S t arting and stopping

the MDAS server” on page 18. For more information on enabling the MDAS

server, see “Enabling and disabling an MDAS server” on page22.

Adding an MDAS instance from the Central Management Console (CMC)

!

To add an instance of an MDAS server from the C MC

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

4. Click Servers to view a list of servers.

5. Click the Add Server button to start the Business Objects Server

wizard.

6. Click Next to begin.

7. From the Server Type and Display Name Configuration screen select

the following information:

• Server Type: The type of server you want to add to the list of servers

in the Central Management Console.

• Display Name: The “friendly” name that appears in the Central

Management Console used to represent this server.

• Server Name: The underlying system name of the server. In most

cases, this name should not be changed unless there is a specific
system need.

8. Click Next.

9. From the Set Configuration screen, if the CMS name is not already

entered in the CMS Name field, enter it now.
If the name is already entered, do not change it.

10. Click Next to view the Summary screen.

If all displayed information is correct, click Finish to close the wizard and
return to the main Central Management Console screen.

24 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

Deleting an MDAS instance from the Central Management Console (CMC)

!

To delete an instance of an MDAS server from the CMC

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

4. Click Servers to view a list of servers you can administer.

5. Locate the MDAS server that you want to delete, and select its check

box.

6. Click the Delete button.

Note: You can only delete instances of Business Objects servers.

Command line options

When you start or configure a server through the CMC or the CCM, the server
is started or restarted with a default command line that includes a typical set
of options and values. You can modify these command line values by
stopping the service in the CCM and modifying the value in the Command
field.

Note: The syntax for using these options is significantly different with

Voyager’s MDAS server, because the MDAS server operates inside the
Tanuki service wrapper. For more information, see “The Java service

wrapper” on page 28.

3

Standard options

The following table contains the server command line options:

BusinessObjects Voyager Administrator’s Guide 25

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

Option Valid

Arguments

-fg Unix only. Run the daemon in the

-name string Specify the friendly name of the server.

-ns cmsname[:port] Specify the CMS that the server should

-ntservicename The Windows NT service name, or the

-port [interface] Binds servers to the specified network

-requestPort port Specify the port that the server listens

-requestTimeout seconds CORBA request timeout in seconds.

Behavior

foreground. When passing the server's
command line to the

crystalrestart.sh script, you must

use this option (see
you run the server's command line
directly , do not use this option, because
the foreground process blocks the shell
until the server exits.

The server registers this name with the
CMS, and the name is displayed in the
CMC. The default friendly name is

hostname.servertype.

register with. Add port if the CMS is not
listening on the default port (6400).
This option does not apply to the CMS
itself.

UNIX command line used to start the
MDAS Server.

interface. Useful on multi-homed
machines or in certain NAT firewall
environments.

on. The server registers this port with
the CMS. If unspecified, the server
chooses any free port > 1024.

Note: This port is used for different

purposes by different servers.

ccm.config). If

26 BusinessObjects Voyager Administrator’s Guide

Setting user access levels

Users need certain access levels to perform their tasks in Voyager. For
example, if a user must load and edit a workspace, then sufficient workspace
rights must be granted to that user . If a user must save worksp aces to cert ain
folders locally or across a network, then that user must be granted sufficient
(write) permissions to the folder the workspace is to be saved to.

Also, if a user does not have sufficient rights to at least one connection to a
Voyager data source, Voyager is not visible from InfoView.

You can use the Central Management Console (CMC) to add groups and set
access levels for various components of the product suite, including Voyager
elements such as workspaces and folders.

To set access levels for a Voyager component

!

1. On the Start menu, click BusinessObjects Enterprise >

BusinessObjects Enterprise Java Administration Launchpad.

2. Click the Central Management Console link.

3. If you are prompted, enter your user name and password.

4. Click the type of object you want to set access levels for (for example,

Folders or Servers).

5. From the list of objects that appears, click the single object you want to

set access levels for.

6. Click the Rights tab.

7. If you want to add a user to the list of users who have rights to the object,

click the Add/Remove button.

8. If you want to change the access levels of a user that is already shown in

the list of users, click the drop-down list to the right of the user name and
select the access level for that user.

9. If you want to set advanced (detailed) access rights for a user, click the

Advanced link.

Note: For more information about how to use the Central Management

Console to set access levels for various components of the product suite,
including Voyager elements, see the chapter “Rights in the CMC” in the
BusinessObjects Enterprise Administration Guide.

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

3

Configuring the MDAS for Secure Sockets Layer (SSL)

To set up SSL for all server communication you need to perform the following
steps:

BusinessObjects Voyager Administrator’s Guide 27

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

• Deploy BusinessObjects Enterprise with SSL enabled.

• Create key and certificate files for each machine in your deployment.

• Configure the location of these files in the CCM and your web ap plication

server.

T o configure the SSL protocol in the CCM

!

1. In the CCM, right-click a server and choose Properties.

2. In the Properties dialog box, click the Protocol tab.

3. Provide the file path for the directory where you stored the key and

certificate files.

Note: Ensure you provide the directory for the machine that the server is

running on.

4. Repeat steps 1 to 3 for all servers.

!

T o configure the SSL protocol for the web application server

• If you have a J2EE web application server, run the Java SDK with the

following system properties set:
For example:

-Dbusinessobjects.orb.oci.protocol=ssl

-DcertDir=d:\ssl

-DtrustedCert=cacert.der

-DsslCert=clientcert.der

-DsslKey=client.key

-Dpassphrase=passphrase.txt

The Java service wrapper

The MDAS server relies on third-party wrapper software from Tanuki Software
(http://wrapper.tanukisoftware.org), which manages the process of starting
and stopping the server. In Windows, the wrapper start s and stops the MDAS
server as a Windows service. The service can be manipulated like any other
Windows service. In Solaris/Unix, the wrapper starts and stops the MDAS
server as a daemon. The daemon has a process ID (pid), and therefore can
be queried and manipulated like any other Unix process.

The configuration file
tweaked to alter performance and server behavior. For more information
about this file and its settings, consult the online documentation (http://

wrapper.tanukisoftware.org/doc/english/introduction.html).

In addition, for information on MDAS server performance settings that are
better suited to your organization’s unique requirements, consult Business
Objects Technical Support.

28 BusinessObjects Voyager Administrator’s Guide

MDASServer.conf contains many settings that can be

Administering the Multi-Dimensional Analysis Services Server

Note: Changing settings in the MDASServer.conf file can have negative

effects on the performance and operation of the entire Voyager application.
Proceed with caution.

Single or multiple MDASServer.conf files

The simplest server wrapper setup is a single MDAS server with a single

MDASServer.conf file; however, you can also have multiple, clustered

MDAS servers controlled by a single
have multiple MDAS servers, each controlled by its own
file.

If you use a single
servers, then you must pass parameters using the command line for each
server to indicate information such as server name, sessions, timeout, etc.
See “Generic configuration file” below.

If you want to use a separate
servers, then you can put the information for each server into its respective

MDASServer.conf file. See “Modified configuration file” below.

For more information about clustering MDAS servers, see “Clustering MDAS

servers” on page 32.

MDASServer.conf file to control a cluster of MDAS

MDASServer.conf file for each of the MDAS

Configuring the MDAS server

MDASServer.conf file. Also, you can

MDASServer.conf

3

Command line options

Command line options are passed through the service wrapper to the
application. This is performed by wrapping the command line options using:

wrapper.app.parameter.n

Where n is the next incremental application parameter number. You must use
this wrapper, regardless of whether you decid e to use a generic configuration
file for all applications, or modify your configuration file for each application.

Generic configuration file

If you are using a single generic MDASServer.conf configuration file, you
must use this method at the command line to pass all command line options
to the application.

For example, consider the following command line command and options that
you would normally expect to use with a regular BusinessObjects Enterprise
server:

"C:\Program Files\Business Objects\BusinessObjects
Enterprise 11.5\win32_x86\wrapper.exe" -t "C:\Program
Files\Business Objects\BusinessObjects Enterprise

11.5\win32_x86\MDSServer.conf" -name

IUSERBOX.product.businessobjects.com.MDASServer(2) -ns
IUSERBOX –ntservicename BOBJMDASServer(2)

BusinessObjects Voyager Administrator’s Guide 29

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

The command line options would not be passed to the application. Instead,
you must rewrite them as the following:

"C:\Program Files\Business Objects\BusinessObjects
Enterprise 11.5\win32_x86\wrapper.exe" -t "C:\Program
Files\Business Objects\BusinessObjects Enterprise

11.5\win32_x86\MDSServer.conf"
wrapper.app.parameter.2="-name"
wrapper.app.parameter.3="IUSERBOX.product.businessobjects.co
m.MDASServer(2)" wrapper.app.parameter.4="-ns"
wrapper.app.parameter.5="IUSERBOX"
wrapper.app.parameter.6="-ntservicename"
wrapper.app.parameter.7="BOBJMDASServer(2)"

Note how each option is indicated using wrapper.app.parameter.n.
Because the syntax of command line arguments differs depending on the

operating system, command line arguments such as
handled as two separate command line
statements:

wrapper.exe -t MDSServer.conf
wrapper.app.parameter.2="-name"
wrapper.app.parameter.3="IUSERBOX.product.businessobjects.co
m.MDASServer(2)"

Use this syntax for all command line arguments for the MDAS Server.

–name {name} is

wrapper.app.parameter

Modified configuration file

If you decide to modify the MDASServer.conf file, the

wrapper.app.parameter.n arguments can be added as part of the file. For

example, the command line options in the previous example are added to the
configuration file:

# Application parameters. Add parameters as needed starting
from 1

wrapper.app.parameter.1=com.businessobjects.multidimensional
.services.server.MdsServerBootstrap

wrapper.app.parameter.2=-name
wrapper.app.parameter.3=MDASServer2
wrapper.app.parameter.4=-ns
wrapper.app.parameter.5=IUSERBOX
wrapper.app.parameter.6=-maxSessions
wrapper.app.parameter.7=100
# MDS logging configuration
wrapper.java.additional.1=-Dlog4j.configuration=mds.log4j.pr

operties

30 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuring the MDAS server

Using the CMC to manage MDAS server properties and metrics

When you click a server instance listed on the Servers page of the CMC, you
are redirected to a set of pages that display read-only information about the
selected server and allow you to specify new configuration parameters. For
more information, see the following topics:

• “Set properties” on page 31.

• “View metrics” on page31.

• “Manage rights” on page 32.

Set properties

The Properties tab contains some settings you can use to adjust client and
server connections to better suit your organization’s needs:

• Client-Server timeout: This setting indicates the number of milliseconds

of inactivity between the Voyager client and MDAS server to wait before
timing out, and forcing the user to log in again. If no command line value
is set, the default is 1200000. If this value is set to 0, the connection stays
open indefinitely.

• Maximum number of sessions: This setting indicates the total number

of sessions that can be concurrently opened on the MDAS server.
Increasing this number may result in performance issues for both the
MDAS server and the database server.

3

View metrics

This tab displays information about the server in three separate sections.
The general information displayed for each server includes information about

the machine that the server is running on: its name, operating system, total
hard disk space, free hard disk space, total RAM, number of CPUs, and local
time. The general information also includes the time the server started and
the version number of the server.

The current settings section displays the values currently set for all the
configurable properties listed on the previous properties tab.

The metrics section displays server-specific information about its current load.

• Number of active sessions: This setting indicates the current number of

connections from the Voyager client(s) to the MDAS server . Note that if a
client has several workspaces open, each workspace represents a
connection that has not timed out.

BusinessObjects Voyager Administrator’s Guide 31

Administering the Multi-Dimensional Analysis Services Server

3

Configuring the MDAS server

• Number of active cubes: This setting indicates the number of data

sources that are being used to supply data to the connections (as
indicated above by the Number of active sessions) that have not timed
out.

• Number of active queries: The number of data requests that are open

between the Voyager client and the database server(s). Note that an
active query may be between any of the active sessions and any of the
active data sources.

• Supported databases: This is a list of all databases detected on the

system that can be used with Voyager.

Manage rights

This tab contains the standard Windows rights management controls. For
more information about setting up and administering rights, consult your
Microsoft Windows Server documentation.

Clustering MDAS servers

The MDAS Server is inherently memory bound. As the number of users
increases, so does the number of queries that must be handled, and therefore
so does the MDAS Server memory requirements.

For this reason, you may want to cluster multiple MDAS Servers together.
Voyager automatically identifies and makes use of clustered MDAS Servers
without further configuration.

To cluster the MDAS Server (Windows)

!

1. In the CCM (Central Configuration Manager), click the Add Server button

to start the Add Business Objects Server wizard. Click Next.

2. For Server Type, choose MDAS Server.

You can optionally change the Display Name.

3. Enter the Server Name of the server where the MDAS is located, and

then click Next.

4. Enter the name of the CMS.

All clustered MDAS Servers should point to the same CMS.

5. Click Next and then Finish.

6. In the CCM, click the new MDAS Server, and then click the Start button.

7. Finally, enable the server on the CMS:

32 BusinessObjects Voyager Administrator’s Guide

• Enable the server via the CMC (Central Management Console).

• Click the new MDAS Server in the CCM, and then click the Enable/

8. Log on to the CMS, click the checkbox beside the new MDAS server and

click OK.

Load balancing

Like other BusinessObjects Enterprise servers, you can install multiple
instances of the MDAS server . Once you have installed the MDAS server on a
single machine, you can create multiple instances of the MDAS server on that
machine using the Central Configuration Manager (CCM). For more
information, see “Clustering MDAS servers” on page 32.

You can also choose to install the MDAS server on different machines to
distribute the load.

Load balancing is achieved by random selection of an MDAS Server. If this
server can successfully return an MDAS session, then that server is used to
serve the client’s request.

Note: The architecture of the MDAS server and its services is such that when

a client requests an MDAS session, that session is maintained throughout the
lifetime of the client application instance. The session cannot be transferred
to another server within the MDAS cluster. Because of the architecture of the
MDAS server, there is no true fail-over for a client that has already
established a session. If the server that is hosting the session fails, the client's
application will also fail, closing all OLAP connections and queries.

Administering the Multi-Dimensional Analysis Services Server

or

Disable Servers button.

Starting and stopping Tomcat in Solaris

3

Starting and stopping Tomcat in Solaris

You can start and stop the Tomcat web application server from the Solaris
command prompt.

To start or stop Tomcat from Solaris

!

1. From Solaris, change to the /bobje/tomcat directory.

2. To start the MDAS server, enter the command:

./tomcatstartup.sh

3. To stop the MDAS server, enter the command:

./tomcatshutdown.sh

BusinessObjects Voyager Administrator’s Guide 33

Administering the Multi-Dimensional Analysis Services Server

3

Configuration files for the MDAS server

Configuration files for the MDAS server

You can edit these MDAS server configuration files to customize your
Voyager deployment:

• Wrapper service configuration file—MDASServer.conf.

• MDAS server configuration file—mdas.properties.

• Enable MDAS logging—mdas.log4j.properties.

Wrapper service configuration file—MDASServer.conf

The MDASServer.conf file contains parameters used by the wrapper
service. It references the JVM executable used for launching the MDAS
server. JVM settings include minimum/maximum memory heap size, MDAS
server application classpaths, wrapper log file location, and various static
Windows service properties. The configuration file contains comments which
explain the purpose of each parameter in detail.

Any changes made to this configuration file do not take effect until the next
restart of the MDAS server.

Note: The configuration file contains parameters that might overlap with

properties that can be set for the service in the CCM or Microsoft
Management Console. The values set in the CCM or Microsoft Management
Console will override the parameter values specified in the configuration file.

MDASServer.conf sample file listing

********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener
interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=Z:/MDA_Services/src/MDA_Services/lib/wrapper.jar

# Business Objects MDS Classpath values
# SOFA Java

34 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuration files for the MDAS server

wrapper.java.classpath.2=Z:/MDA_Services/win32_x86/release/bin/MDA_Data/
java/data.jar
wrapper.java.classpath.3=Z:/MDA_Services/win32_x86/release/bin/MDA_Data/
java/data-native.jar

# MDS XML Bean Binding OMS
wrapper.java.classpath.4=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/crosstab-xml-binding.jar
wrapper.java.classpath.5=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/xtab-xml-binding.jar
wrapper.java.classpath.6=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/metadata-xml-binding.jar
wrapper.java.classpath.7=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/visualization-xml-binding.jar
wrapper.java.classpath.8=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/axes-xml-binding.jar
wrapper.java.classpath.9=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/catalog-xml-binding.jar
wrapper.java.classpath.10=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/provider-xml-binding.jar
wrapper.java.classpath.11=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/cubeparameters-xml-binding.jar
wrapper.java.classpath.12=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/time-series-functions-xml-binding.jar
wrapper.java.classpath.13=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/datarowset-xml-binding.jar
wrapper.java.classpath.14=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/fonts-xml-binding.jar
wrapper.java.classpath.15=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar//server-fonts-xml-binding.jar
wrapper.java.classpath.16=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/export-metadata-xml-binding.jar

3

# MDS Third Party
wrapper.java.classpath.17=Z:/MDA_Services/win32_x86/release/bin/External/
java/jsr173_1.0_api.jar
wrapper.java.classpath.18=Z:/MDA_Services/win32_x86/release/bin/External/
java/log4j.jar
wrapper.java.classpath.19=Z:/MDA_Services/win32_x86/release/bin/External/
java/resolver.jar
wrapper.java.classpath.20=Z:/MDA_Services/win32_x86/release/bin/External/
java/xbean.jar
wrapper.java.classpath.21=Z:/MDA_Services/win32_x86/release/bin/External/
java/xml-apis.jar
wrapper.java.classpath.22=Z:/MDA_Services/win32_x86/release/bin/External/
java/xercesImpl.jar
wrapper.java.classpath.23=Z:/MDA_Services/win32_x86/release/bin/External/
java/poi-2.5.1-final-20040804.jar
wrapper.java.classpath.24=Z:/MDA_Services/win32_x86/release/bin/External/
java/xpp3.jar

BusinessObjects Voyager Administrator’s Guide 35

Administering the Multi-Dimensional Analysis Services Server

3

Configuration files for the MDAS server

wrapper.java.classpath.25=Z:/MDA_Services/win32_x86/release/bin/External/
java/itext-1.3.0.jar
wrapper.java.classpath.26=Z:/MDA_Services/win32_x86/release/bin/External/
java/commons-cli-1.0.jar

# MDS Implementation
wrapper.java.classpath.27=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-corba-transport.jar
wrapper.java.classpath.28=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-client.jar
wrapper.java.classpath.29=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-server.jar
wrapper.java.classpath.30=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-transport.jar

# Business Objects Enterprise
wrapper.java.classpath.31=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/cecore.jar
wrapper.java.classpath.32=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/cesession.jar
wrapper.java.classpath.33=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/celib.jar
wrapper.java.classpath.34=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/corbaidl.jar
wrapper.java.classpath.35=Z:/MDA_Services/win32_x86/release/bin/External/
java/ebus405.jar
wrapper.java.classpath.36=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/cosnaming.jar
wrapper.java.classpath.37=Z:/MDA_Services/win32_x86/release/bin/
Framework/java/ceplugins.jar

# MDS Configuration Path
wrapper.java.classpath.38=Z:\MDA_Services\src\MDA_Services\conf

# MDS Resource Bundlers
wrapper.java.classpath.39=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-server-languagepack.jar
wrapper.java.classpath.40=Z:/MDA_Services/win32_x86/release/bin/
MDA_Services/java/jar/mds-transport-languagepack.jar

# CVOM Visualization
wrapper.java.classpath.41=Z:/MDA_Services/win32_x86/release/bin/
Visualization/java/businessgraphics.jar
wrapper.java.classpath.42=Z:/MDA_Services/win32_x86/release/bin/
Visualization/java/cvom.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:/dev/MDA
wrapper.java.library.path.2=Z:/MDA_Services/src/MDA_Services/lib

36 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuration files for the MDAS server

# Environment PATH variable points to sofa library path
set.PATH=%PATH%%WRAPPER_PATH_SEPARATOR%%COMMON_BIN_DIR%
set.LD_LIBRARY_PATH=%LD_LIBRARY_PATH%%WRAPPER_PATH_SEPARATOR%%COMMON_BIN_
DIR%

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=128

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=256

# Application parameters. Add parameters as needed starting from 1
wrapper.app.parameter.1=com.businessobjects.multidimensional.services.ser
ver.MdsServerBootstrap

wrapper.app.parameter.2=name
wrapper.app.parameter.3=MDASServer2

wrapper.app.parameter.4=ns
wrapper.app.parameter.5=IUSERBOX

wrapper.app.parameter.6=maxSessions
wrapper.app.parameter.7=100

# MDS logging configuration
wrapper.java.additional.1=-Dlog4j.configuration=mds.log4j.properties

3

# Change the default java thread stack size to 1MB. This size
# prescribed by SOFA to handle large queries for certain providers.
wrapper.java.additional.2=-Xss1m

# AWT headless mode to support charting fonts.
# Should be set to 'false' for win32_x86 builds, 'true' for all other unix
builds
wrapper.java.additional.3=-Djava.awt.headless=%JAVA_AWT_HEADLESS_VALUE%

wrapper.java.additional.4=-Xdebug
wrapper.java.additional.5=-Xrunjdwp:transport=dt_socket,server=y,suspend=
y,address=8000

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM

# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO

# Log file to use for wrapper output logging.

BusinessObjects Voyager Administrator’s Guide 37

Administering the Multi-Dimensional Analysis Services Server

3

Configuration files for the MDAS server

wrapper.logfile=%ENTERPRISE_LOGGING_DIR%/mds_server.log
# Format of output for the log file. (See docs for formats)

wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)

wrapper.logfile.loglevel=INFO
# Maximum size that the log file will be allowed to grow to before

# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE

# Shutdown timeout. The time the wrapper waits fot the JVM to successfully
shutdown.
wrapper.shutdown.timeout=150

#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=MDA Server Console

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.

# Name of the service
wrapper.ntservice.name=BOBJMDASServer

# Display name of the service
wrapper.ntservice.displayname=MDAS Server

# Description of the service
wrapper.ntservice.description=Business Objects Multi Dimensional Analysis
Server

38 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuration files for the MDAS server

# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

MDAS server configuration file—mdas.properties

You can configure the behavior of an individual MDAS server instance by
modifying parameters in its associated MDAS.properties file. Parameters
include the CMS hostname and port number used for registering with the
CMS, MDAS session timeout, MDAS request/response timeout, as well as
various parameters used for development and testing purposes that should
not be changed or referenced in a production environment. Some of the
parameters provided by the configuration file overlap with the standard
command line options that you can specify in the CCM or the Properties tab
of the CMC. You should use the CCM or Properties tab of the CMC to
configure the behavior of the MDAS server instead of modifying the
configuration file.

Any changes made to this configuration file will not take effect until the next
restart of the MDAS server.

3

mdas.properties file listing

# The name of the remote machine that is running the MDAS server.
# Always specify fully qualified machine name. Do not use 'localhost'.
multidimensional.services.server.host=BUSINESS-JGAN03

# The name of the machine that the CMS is running upon.
# Always specify fully qualified machine name. Do not use 'localhost'.
multidimensional.services.server.enterprise.cms.name=BUSINESS-JGAN03

# The port of the machine that CMS communicates on.
multidimensional.services.server.enterprise.cms.port=6400

# The number of milliseconds that the server has to return a response
# for a request. If the server does not respond in this time period
# the client reports a TimeoutException. Also:
# The number of milliseconds that a client has to accept a response.
# If the client does not respond in this time period the response
# times out.
multidimensional.services.transport.connection.timeout=1200000

# The number of milliseconds before idle transport connections are
# closed. If a server object is not used (no client requests coming in)
# within this period, the server object is removed.

BusinessObjects Voyager Administrator’s Guide 39

Administering the Multi-Dimensional Analysis Services Server

3

Configuration files for the MDAS server

# A subsequent attempt to use this server object will cause an exception
to be thrown.
multidimensional.services.transport.idle.timeout=1200000

#

-------------------------------------------------------------------------

-------------------­# The following parameters are for DEVELOPMENT use only. They should not
be
# changed or referenced within a production environment.
#

-------------------------------------------------------------------------

-------------------­# The port on the remote machine which MDAS Server is listening for

client requests. (for standalone mode)
# In a production environment, this parameter is not configurable.
# The next available port on the remote machine is automatically selected.
# For development use only.
multidimensional.services.server.port=10550

# The name of the remote machine that is running the Naming server (for
standalone mode). For development use only.
multidimensional.services.server.naming.host=localhost

# The port of the remote machine that Naming Server communicates on (for
standalone mode). For development use only.
multidimensional.services.server.naming.host.naming.port=10555

# Flag indicating whether or not the server should run standalone
# or integrated with the BOE framework. In a production environment,
# the value should always be 'false'. For development use only.
multidimensional.services.server.standalone=false

# Set to 'false' in production environments to ensure the
# server is not using xml validation. This value should be 'true' in
# development environments. For development use only.
multidimensional.services.server.xml.use_validation=false

# Set this value to use a local file as the source of persistent
# connections. For development use only.
multidimensional.services.connection.repository.filename=connections.xml

# Defines the output level for diagnostic messages printed by
# Orbacus that are related to connection establishment and
# closure. Can be 'none', 'info', or 'verbose'. For development use only.
multidimensional.services.transport.trace.level=none

# Leave an empty line at the end of the file for unix.

40 BusinessObjects Voyager Administrator’s Guide

Administering the Multi-Dimensional Analysis Services Server

Configuration files for the MDAS server

Enable MDAS logging—mdas.log4j.properties

The MDAS server uses industry-standard log4j logging provided by Apache
Software Foundation (http://logging.apache.org/log4j).The

mdas.log4j.properties file contains standard logging parameters such as

logging threshold level, name and location of log file, size of rolling log files,
and logging format patterns.

Five log threshold levels are provided by log4j, in decreasing level of severity:
FATAL, ERROR, W ARN, INFO, and DEBUG. In a production environment, we
recommend setting the log level to ERROR so that only ERROR and FATAL
messages are generated and non-essential messages are suppressed. In a
development environment, set the log level to DEBUG so that all messages
are generated for quick error diagnosis.

mdas.log4j.properties file listing

# This configuration file that outputs to a log file under user's home
directory.
# The output information consists of relative time, log level, thread
# name, logger name, nested diagnostic context and the message in that
# order.

# For the general syntax of property based configuration files see the
# documenation of org.apache.log4j.PropertyConfigurator.
log4j.logger.com.businessobjects.multidimensional=ERROR, file

3

# Console appender.
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%d [%t] %-5p %c - %m%n

# File appender.
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.File= mdas.log
log4j.appender.file.layout=org.apache.log4j.PatternLayout
log4j.appender.file.layout.ConversionPattern=%d [%t] %-5p %c - %m%n
See Box 3 for an example mdas.log4j.properties.

BusinessObjects Voyager Administrator’s Guide 41

Administering the Multi-Dimensional Analysis Services Server

3

Configuration files for the MDAS server

42 BusinessObjects Voyager Administrator’s Guide

Understanding Voyager and Microsoft Analysis Services Security

chapter

Understanding Voyager and Microsoft Analysis Services Security

4

Overview

Overview

This section discusses Voyager security configuration and the steps required
to set up security for the various components in the Voyager and server
architecture.

SQL Server Analysis Services Security Architecture

SQL Server Analysis Services (2000 and 2005) security architecture is built
on Microsoft Windows authentication. To access data in SQL Server Analysis
Services, a user must first be authenticated by the Microsoft Windows
network (domain controller). After the user has been authenticated by
Microsoft Windows, SQL Server Analysis Services determines the user's
permissions to access data and perform tasks within a particular database by
looking up the security roles that he belongs to.

Although SQL Server Analysis Services 2000 and 2005 both support the
concept of security roles, there are some minor differences between the two
products. SSAS 2000 has database and cube roles, while SSAS 2005 has
server and database roles. Fundamentally, role security works the same way
in both versions. The database administrator creates a role and assigns it
rights to perform specific actions such as view dimensions and cell data in a
cube, write back to a cube, process a cube or dimension, etc. Next, the
administrator specifies membership in the role by assigning it Microsoft
Windows user and/or group accounts. The rights that a user has to a SSAS
database is therefore determined by his membership in these security roles.

Voyager is an OLAP client application that provides read-only access to data
and objects in SSAS databases. It does not provide functionality that allows a
user to perform any actions that process or write to objects on the SSAS
server.

Configuring Security in a Multi-tiered Application Environment

The following network diagram depicts a typical deployment of Voyager in a
multi-tiered environment. The diagram has been simplified to exclude more
complex network factors such as routers, bridges and firewalls, in order to
illustrate how MSAS security works in a multi-tiered environment:

44 BusinessObjects Voyager Administrator’s Guide

Understanding Voyager and Microsoft Analysis Services Security

Configuring Security in a Multi-tiered Application Environment

4

The end user's Windows credentials are passed to the Multi-dimensional
Analysis service, which runs on a separate physical machine. The MDAS
must somehow use the end user's Windows credentials to establish a
connection to the backend SSAS database server. The MDAS it self runs as a
Windows service in the context of a machine account like LocalSystem or a
domain account that has been granted special rights to run Windows
services. To support the security roles defined in SSAS, the MDAS service
account has to impersonate the Windows end user when it connects to the
backend SSAS server. The MDAS service running on one server
impersonates a Windows domain user to access resources that are located
on a remote server (SSAS); this process is known as delegation.

An application for delegation must satisfy several conditions:

• A Service Principal Name (SPN) must be added for each of the target

SSAS servers and/or instances.
This is done using the Microsoft utility

setspn.exe.

• The end user Windows accounts that will be impersonated by the

application process are not marked as “Account Is Sensitive and Cannot
Be Delegated” in Active Directory Users and Computers.

• The MDAS service account is configured to be trusted for delegation on

Windows Active Directory Users and Computers.

BusinessObjects Voyager Administrator’s Guide 45

Understanding Voyager and Microsoft Analysis Services Security

4

Configuring how authentication information is passed to SSAS

• If the MDAS is running under LocalSystem, this option is set on the

machine account.
If the MDAS is running a domain user account, this option is set on the

user account.

Note: To enable this option on a domain user account, you must first add

a SPN for the account with the

setspn.exe utility.

• The MDAS service must use the Kerberos security service provider

interface to authenticate users when it impersonates them.

• No additional configuration is required as the MDAS server by default

attempts to connect first with Kerberos, and only falls back to NTLM if
Kerberos authentication fails.

• All user and machine accounts must belong to the same Active Directory

domain (or to trusted domains in the same forest).

• The MDAS service must connect to the SSAS server using a fully

qualified DNS or Netbios name.
It cannot connect by directly referencing the SSAS server's IP address.

Configuring how authentication information
is passed to SSAS

The information that Voyager uses to create a connection to a cube on a
database server is stored as a connection object in the BOE Central
Management System (CMS) repository. The information required for a
connection varies depending on the server type (SAP BW, SSAS, Essbase,
etc.). The administrator can also specify how end users should be
authenticated to the backend server when they choose to create a new
Voyager workspace using the connection.

An authentication type must be specified for the connection. The following
three options are available:

• Prompt

• Single sign-on

• Specified user

All authentication types depend on the MDAS server to perform Active
Directory delegation, so all conditions must be true. The single sign-on
authentication type requires additional configuration.

46 BusinessObjects Voyager Administrator’s Guide

Prompt

When this type is selected for the connection, the end user will be prompted
with a dialog box to enter his username and password when the Voyager
application initiates the connection.

Note: The username and password are not encrypted by the Voyager

application. To protect usernames and passwords, you must enable SSL on
your web application server.

Single sign-on

With the single sign-on option selected, the user signs on once to the
InfoView application with his Active Directory credentials and then is able to
connect to the backend SSAS servers in Voyager without having to enter his
username and password again. The Voyager application (through the MDAS
server) automatically retrieves the Active Directory credentials from the
current InfoView session and passes them to the SSAS server.

Single sign-on to the database only works if the following conditions are true:

1. BusinessObjects Enterprise is configured correctly for Active Directory

2. All CMS and MDAS servers must be started with the identical domain

3. The user signs on to InfoView using the Active Directory authentication

Understanding Voyager and Microsoft Analysis Services Security

Configuring how authentication information is passed to SSAS

authentication in a Java environment. See the BusinessObjects
Enterprise XI Release 2 Administrator's Guide and the technical brief
Configuring Active Directory Authentication using Java Application
Servers for more information.

account. This service account must be trusted for delegation in Active
Directory.

plug-in.

4

Specified User

With this option selected, the administrator enters a specific username and
password which will be stored as part of the connection object. The stored
username and password will always be used to authenticate to the backend
SSAS server when this connection object is accessed from a Voyager
application. Like single sign-on, this authentication type does not require the
end user to enter a username and password in the Voyager application.
However, because the same Active Directory credentials are used for every
user who accesses the cube through this connection, this option is not
suitable if a granular security model has been applied on the backend SSAS
server.

BusinessObjects Voyager Administrator’s Guide 47

Understanding Voyager and Microsoft Analysis Services Security

4

Configuring how authentication information is passed to SSAS

48 BusinessObjects Voyager Administrator’s Guide

Administering BusinessObjects Voyager Connections

chapter

Administering BusinessObjects Voyager Connections

5

Creating OLAP data source connections on Windows

Creating OLAP data source connections on
Windows

Before users can begin working with business data in Voyager, you must
create connections to OLAP data sources for them to add to their Voyager
workspaces.

A connection is a BusinessObjects Enterprise repository object that contains
all the information that is required for Voyager to connect to an OLAP cube.
This connection object is then linked to a Voyager worksp ace. Benefits of this
connection scheme include the following:

• Reduced complexity

In typical organizations, most users outside of the IT department are not
familiar with the names, IP addresses, and other details of the back-end
database servers. When users need these details, they usually contact
IT.

With Voyager, connections are defined once by an administrator and
then saved to the BusinessObjects Enterprise repository. Users who
need to create Voyager workspaces can then choose from the list of
saved connections instead of having to remember and provide any
specific server details themselves.

• Improved security

Only administrators and users who have privileges to add objects to the
BusinessObjects Enterprise repository need to know server details. Also,
connection details such as servername, database, username, and
password are stored in the repository, not in workspace files.

• Improved manageability

Storing connection information in a shared connection object that is
referenced in workspace files allows organizations to easily move
workspaces between development and production environments. Instead
of changing all the workspaces, you modify only the shared connection
object to reference the production server instead of the development
server. The updated connection information is automatically propagated
to the workspaces that reference the shared connection object.

You create new Voyager connection objects and manage existing connection
objects in the Central Management Console (CMC).

Once you have created OLAP cube connections, these connections appear in
the list of connections in the Add Connection dialog box in BusinessObjects
Voyager, and are available for your users to add to their Voyager workspaces.

50 BusinessObjects Voyager Administrator’s Guide

Related topics:

• “Authentication” on page 51

• “Creating a connection” on page 52

• “Editing a connection” on page 53

• “Deleting a connection” on page54

• “Changing Voyager workspace properties on Windows” on page 56

Authentication

You can set the type of authentication to use when users create new
workspaces or log on to existing workspaces.

You can choose from the following authentication types when you create a
Voyager connection in the CMC:

Prompt

Always prompt users for logon credentials.

User Specified

With this option selected, the administrator enters a specific username and
password which will be stored as part of the connection object. The stored
username and password will always be used to authenticate to the backend
server when this connection object is accessed from a Voyager application.
Like single sign-on, this authentication type does not require the end user to
enter a username and password in the Voyager application. However,
because the same Active Directory credentials are used for every user who
accesses the cube through this connection, this option is not always suitable.

Administering BusinessObjects Voyager Connections

Creating OLAP data source connections on Windows

5

SSO (single sign-on)

With the single sign-on option selected, the user signs on once to the
InfoView application with his Active Directory credentials and then is able to
connect to the backend servers in Voyager without having to enter the
username and password again. The Voyager application (through the MDAS
server) automatically retrieves the Active Directory credentials from the
current InfoView session and passes them to the server.

Single sign-on to the database only works if the following conditions are true:

1. BusinessObjects Enterprise is configured correctly for Active Directory

authentication in a Java environment. See the BusinessObjects
Enterprise XI Release 2 Administrator's Guide and the technical brief
Configuring Active Directory Authentication using Java Application
Servers for more information.

BusinessObjects Voyager Administrator’s Guide 51

Administering BusinessObjects Voyager Connections

5

Creating OLAP data source connections on Windows

2. All CMS and MDAS servers must be started with the identical domain

account. This service account must be trusted for delegation in Active
Directory.

The user signs on to Business Objects InfoView using the Active Directory
authentication plug-in.

These OLAP providers support single sign-on:

Provider Authentication

Microsoft Analysis Services
2000 and 2005

SAP BW SAP authentication including Secure

Creating a connection

If you have sufficient rights in the BusinessObjects Enterprise system, you
can create a new cube connection.

Note: For detailed explanations of the parameters required to set up

connections to all supported OLAP providers, see “Data source connection

settings on Windows” on page 54.

Windows Active Directory

Network Communication (available only if
the BusinessObjects Integration Kit for
SAP has been installed)

To create a new connection object in the CMC

!

1. From the Start menu, click Programs > BusinessObjects XI Release 2

> BusinessObjects Enterprise > BusinessObjects Enterprise Java
Administration Launchpad and log on to the Central Management

Console (CMC).

2. In the Organize area in the CMC, select Voyager Connections.

3. Click New.

4. Type a Name and optionally type a Description for your connection.

5. Select an OLAP provider from the list:

• Hyperion Essbase (7.0/7.1) / IBM DB2 OLAP (8.2) Enhanced

• Microsoft OLE DB Provider for Analysis Services 9.0

• Microsoft OLE DB Provider for OLAP Services 8.0

• SAP Business Information Warehouse (available only if the

BusinessObjects Integration Kit for SAP has been installed)

6. Enter the provider-specific connection properties, such as the server

name, and click Connect.

52 BusinessObjects Voyager Administrator’s Guide

For details on provider-specific connection properties, see “Data source

connection settings on Windows” on page 54.

7. Enter your credentials and click OK.

8. In the Cube Browser, locate the cube you want to use for this connection,

and then click Select.

9. Choose an authentication type for this connection.

For information on the different authentication types, see “Authentication”

on page 51.

10. Click Save to create the connection.

The connection is now available for users to add to a Voyager
workspace.

Editing a connection

If you have an existing connection to an OLAP cube, but the connection
details have changed, you can change the connection settings. Note that you
need to have sufficient folder rights to edit a connection.

To change connection settings

!

1. From the Start menu, click Programs > BusinessObjects XI Release 2

> BusinessObjects Enterprise > BusinessObjects Enterprise Java
Administration Launchpad and log on to the Central Management

Console (CMC).

2. In the Organize area in the CMC, select Voyager Connections.

A list of existing connections is displayed.

Note: If no connections are listed, you need to create a new OLAP cube

connection to allow your data analysts to begin working with Voyager
workspaces. For more information, see “Creating a connection” on

page 52.

3. Select the check box beside the connection that you want to edit, and

click Edit.

Note: If you do not have "Add objects to the folder" permission in the

BusinessObjects Enterprise system, you cannot edit a connection, and
the Edit button is unavailable.

You can now change the contents of any of the fields to reconfigure your
OLAP cube connection.

For details on provider-specific logon information, see “Data source

connection settings on Windows” on page 54.

Administering BusinessObjects Voyager Connections

Creating OLAP data source connections on Windows

5

BusinessObjects Voyager Administrator’s Guide 53

Administering BusinessObjects Voyager Connections

5

Data source connection settings on Windows

4. Click OK to save the new connection settings.

Deleting a connection

!

T o delete a connection

1. From the Start menu, click Programs > BusinessObjects XI Release 2

> BusinessObjects Enterprise > BusinessObjects Enterprise Java
Administration Launchpad and log on to the Central Management

Console (CMC).

2. In the Organize area in the CMC, select Voyager Connections.

A list of existing connections is displayed.

3. Select the check box beside the connection that you want to delete.

4. Click Delete.

Data source connection settings on Windows

This section describes the connection settings for all supported OLAP data
sources:

• Connection settings for Microsoft OLAP data sources.

• Connection settings for Essbase/DB2 OLAP data sources.

For details on SAP BW data sources, see the documentation for the
BusinessObjects Integration Kit for SAP.

T o create connections to Microsoft Analysis Services, Hyperion Essbase, IBM
DB2 OLAP Server, or SAP BW data sources, you must install client
components for those OLAP providers on each machine where an MDAS
(Multi Dimensional Analysis Services) server is installed.

• Hyperion Essbase: requires the Hyperion Essbase runtime module.

• IBM DB2 OLAP Server: requires the IBM DB2 OLAP Server runtime

module.

• Microsoft Analysis Services 2005: requires Microsoft SQL Server 2005

Analysis Services 9.0 OLE DB Provider.

• Microsoft Analysis Services 2000: requires Microsoft SQL Server 2000

PivotTable Services 8.0.

• SAP BW: requires the BusinessObjects Integration Kit for SAP.

For more information, refer to the documentation for those products.

54 BusinessObjects Voyager Administrator’s Guide

Administering BusinessObjects Voyager Connections

Data source connection settings on Windows

Connection settings for Microsoft OLAP data sources

These connection settings are configurable with Microsoft OLAP data sources
such as Microsoft SQL Server Analysis Services 2005:

Setting Description

OLAP server This option allow you to connect to a cube on an Analysis

Services server through TCP/IP.

Local cube file
(.CUB)

HTTP cube This option allows you to connect to a cube on a Analysis

Authentication
type

The cube is standalone and does not require an OLAP
server. It is stored as a .CUB file on a local or networked
computer. Enter the full path name of the .CUB file.

Services server through HTTP. You must enter the URL to
the virtual directory that contains the "HTTP pump". Consult
Microsoft documentation for more information about
configuring HTTP connectivity for Microsoft Analysis
Services.

Set the type of authentication to use when users create new
workspaces or log on to existing workspaces. These options
are available:

• use saved credentials

Always use the username and password that was
specified when the connection was created by the
Administrator.

• use Enterprise session credentials (SSO)

Uses the credentials that you entered when you logged
on to your BusinessObjects Enterprise InfoView
session.

• prompt for credentials

Always prompt users for logon credentials.

5

For more information, see Microsoft’s documentation for Analysis Services,
which is available either as part of your Microsoft SQL Server Analysis
Services installation, or on the MSDN Website at http://msdn.microsoft.com/

library/.

Connection settings for Essbase/DB2 OLAP data sources

The following connection settings are configurable with Hyperion Essbase or
IBM DB2 OLAP data sources.

BusinessObjects Voyager Administrator’s Guide 55

Administering BusinessObjects Voyager Connections

5

Changing Voyager workspace properties on Windows

Note: You must have a Hyperion Essbase client installed in order to connect

to an Essbase or DB2 OLAP server. Either the Runtime Client or the Excel
Client is required.

Setting Description

Authentication
type

Set the type of authentication to use when users create new
workspaces or log on to existing workspaces. These options
are available:

• use saved credentials

Always use the username and password that was
specified when the connection was created by the
Administrator.

• prompt for credentials

Always prompt users for logon credentials.

Changing Voyager workspace properties on
Windows

You can also modify the properties of connections and saved Voyager
workspaces in the CMC.

T o change the properties of existing connection objects and

!

workspaces

1. From the Start menu, click Programs > BusinessObjects XI Release 2

> BusinessObjects Enterprise > BusinessObjects Enterprise Java
Administration Launchpad and log on to the Central Management

Console (CMC).

2. In the Organize area in the CMC, select Folders to search for your

workspace by folder location, or select Objects to locate your workspace
by alphabetical listing.

3. Click the workspace name to change the workspace properties, or select

the check box beside the workspace name and click Object Settings to
modify advanced settings for the workspace.

For more information on properties and object settings, see the
BusinessObjects Enterprise XI Release 2 InfoView User’s Guide.

56 BusinessObjects Voyager Administrator’s Guide

Managing Voyager Workspaces in the CMC

chapter

Managing Voyager Workspaces in the CMC

6

Managing Voyager workspaces in the Central Management Console

Managing Voyager workspaces in the
Central Management Console

The Central Management Console (CMC) is a Web-based administration tool
for managing user accounts, published Crystal reports and Voyager
workspaces, Voyager connections, folders, server settings, and license keys.
You must be a BusinessObjects Enterprise administrator to log on to the
CMC.

Please see the BusinessObjects Enterprise Administrator’s Guide for
information about logging on to the CMC.

From the CMC, you can change the properties of a saved Voyager
workspace. This section describes the following activities:

• Editing the name, description, and keywords of a Voyager workspace.

• Changing access to Voyager workspaces.

• Seeing a list of connections linked to the workspace.

Editing the name, description, and keywords of a Voyager workspace

You can use the CMC to edit the name, description, and keywords of a
Voyager workspace that has been published to BusinessObjects Enterprise.

T o edit the nam e, description, and keywords of a Voyager workspace in

!

the Central Management Console

1. In the Organize area in the CMC, select Objects.

2. Click the name of the workspace.

3. Click the Properties tab.

4. Make the desired changes and then click Update.

!

To edit the title, description, and keywords of a workspace in InfoView

1. In the Navigation Panel in InfoView, select the folder that contains the

workspace that you want to change.

2. Under the name of the workspace, click Properties.

3. Make the desired changes to the Title, Description, and Keywords, and

then click OK.

58 BusinessObjects Voyager Administrator’s Guide

Managing Voyager Workspaces in the CMC

Changing access to Voyager workspaces

Changing access to Voyager workspaces

After publishing a workspace, you can use the CMC to change its access
permissions.

To change access to workspaces

!

1. In the Organize area in the CMC, select Objects.

2. Click the name of the workspace.

3. Click the Rights tab.

4. Change the Access Level, and then click Update.

Seeing a list of connections linked to the workspace

A Voyager workspace can be linked to several connection objects.

To see a list of connection objects linked to the workspace

!

1. In the Organize area in the CMC, select Objects.

2. Click the name of the workspace.

3. Click the Connections tab.

All connection objects that are linked to the workspace are listed.

6

BusinessObjects Voyager Administrator’s Guide 59

Managing Voyager Workspaces in the CMC

6

Seeing a list of connections linked to the workspace

60 BusinessObjects Voyager Administrator’s Guide

Business Objects Information Resources

appendix

Business Objects Information Resources

A

Documentation and information services

Documentation and information services

Business Objects offers a full documentation set covering its products and
their deployment. Additional support and services are also available to help
maximize the return on your business intelligence investment. The following
sections detail where to get Business Objects document ation and how to use
the resources at Business Objects to meet your needs for technical support,
education, and consulting.

Documentation

You can find answers to your questions on how to install, configure, deploy,
and use Business Objects products from the documentation.

What’s in the documentation set?

View or download the Business Objects Documentation Roadmap, available
with the product documentation at http://www.businessobjects.com/support/.

The Documentation Roadmap references all Business Objects guides and
lets you see at a glance what information is available, from where, and in
what format.

Where is the documentation?

You can access electronic documentation at any time from the product
interface, the web, or from your product CD.

Documentation from the products

Online help and guides in Adobe PDF format are available from the product
Help menus. Where only online help is provided, the online help file contains
the entire contents of the PDF version of the guide.

Documentation on the web

The full electronic documentation set is available to customers on the web
from support web site at: http://www.businessobjects.com/support/.

Documentation on the product CD

Look in the docs directory of your product CD for versions of guides in Adobe
PDF format.

62 BusinessObjects Informati on Analyzer Administrator’s Guide

Business Objects Information Resources

Customer support, consulting and training

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is
there something you particularly like or have found useful? Drop us a line,
and we will do our best to ensure that your suggestion is included in the next
release of our documentation: [e-mail].

Note: If your issue concerns a Business Objects product and not the

documentation, please contact our Customer Support experts. For
information about Customer Support visit: http://www.businessobjects.com/

support/.

Customer support, consulting and training

A global network of Business Objects technology experts provides customer
support, education, and consulting to ensure maximum business intelligence
benefit to your business.

How can we support you?

Business Objects offers customer support plans to best suit the size and
requirements of your deployment. We operate customer support centers in
the following countries:

• USA

• Australia

• Canada

• United Kingdom

• Japan

A

Online Customer Support

The Business Objects Customer Support web site contains information about
Customer Support programs and services. It also has links to a wide range of
technical information including knowledgebase articles, downloads, and
support forums.

http://www.businessobjects.com/support/

BusinessObjects Information Analyzer Administrator’s Guide 63

Business Objects Information Resources

A

Customer support, consulting and training

Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis
stage to the delivery of your deployment project. Expertise is available in
relational and multidimensional databases, in connectivities, database design
tools, customized embedding technology, and more.

For more information, contact your local sales office, or contact us at:

http://www.businessobjects.com/services/consulting/

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can
offer a training package to suit your learning needs and preferred learning
style. Find more information on the Business Objects Education web site:

http://www.businessobjects.com/services/training

64 BusinessObjects Informati on Analyzer Administrator’s Guide

Useful addresses at a glance

Address Content

Business Objects product
information

http://www.businessobjects.com

Product documentation

http://www.businessobjects.com/
support

Business Objects Documentation
mailbox

[e-mail]

Online Customer Support

http://www.businessobjects.com/
support/

Business Objects Consulting
Services

http://www.businessobjects.com/
services/consulting/

Business Objects Education
Services

http://www.businessobjects.com/
services/training

Business Objects Information Resources

Useful addresses at a glance

Information about the full range of
Business Objects products.

Business Objects product
documentation, including the
Business Objects Documentation
Roadmap.

Send us feedback or questions
about documentation.

Information on Customer Support
programs, as well as links to
technical articles, downloads, and
online forums.

Information on how Business
Objects can help maximize your
business intelligence investment.

Information on Business Objects
training options and modules.

A

BusinessObjects Information Analyzer Administrator’s Guide 65

Business Objects Information Resources

A

Useful addresses at a glance

66 BusinessObjects Informati on Analyzer Administrator’s Guide

Index

A

access levels 27
Active Directory 46
administration tools

overview 18
architecture 10, 11
authentication 44, 46, 51

B

Business Objects

consulting services 64, 65

support services 63

training services 64, 65, 65

C

CCM 17
Central Configuration Manager 17
Central Management Console 17
Central Management System 46
changing

cube 59
Changing the Logon As account 21
Changing the MDAS server startup type 20
Client-Server timeout 31
Clustering MDAS servers 32
CMC 17
CMC (Central Management Console) 58
Command line options

syntax 29
components 10
configuration file

generic 29

modified 30
configuration files 34
connection object 46
connection settings

Essbase or DB2 OLAP data sources 55

Microsoft OLAP data sources 55
connection settings, Windows 54
connections 50

defining 13
consultants, Business Objects 64
creating an OLAP cube connection 52
credentials

authentication 51

prompt 51

user-specified 51
crystalrestart.sh 25
cube

changing 59
customer support 63

D

daemon 28

running in foreground 25
data source

connecting 50
debugging 41
default port 25
deleting an OLAP cube connection 54
documentation

feedback on 63

on product CD 62

on the web 62

roadmap 62
domain account 44

E

editing an OLAP cube connection 53
education. See training
errors 41

F

feedback, on documentation 63

BusinessObjects Voyager Administrator’s Guide 67

Index

firewall 25
fonts

configuration 12

friendly name 25

G

granting rights 27

I

information resources 62
installation 12

J

Java service wrapper 28

L

licenses

SAP 12
Load balancing 33
LocalSystem 44
logging 41
Logon As account 21

M

Manage rights 32
Maximum number of sessions 31
MDAS server

administering 16

clustering 32

configuration files 34

configuring 16

configuring Secure Sockets Layer 27

default port 25

friendly name 25

load balancing 33

Logon As 21

multiple instances 33

properties and metrics 31

restarting 19

rights 31

service wrapper 28

starting and stopping 18

startup type 20

mdas.log4j.properties 41
mdas.properties 39
MDASServer.conf 29, 34
memory 32
memory usage 19
metrics

viewing 31
Microsoft Management Console 16
MMC 16
multiple instances of the MDAS server 33
multi-tiered environment

security 44

O

OLAP connections overview 50
OLAP cube

creating a connection 52

deleting a connection 54

editing a connection 53
OLAP Intelligence designer 10
Online Customer Support 63
options

command line 25
overview 10
overview of security 44

P

performance 28, 31, 32
permissions 27
Pivot Table Service 13
port

default 25
process ID 28
Prompt 46
properties

setting 31

R

resources 62
Restarting the MDAS server 19
rights 27

68 BusinessObjects Voyager Administrator’s Guide

Index

S

sample data 13
SAP

installation issues 12

key code 12
scalability 20
Secure Sockets Layer 27
security

multi-tiered environment 44

overview 44

SQL Server 44
Service Principal Name 45
sessions 31
Single Sign On 51
Single sign-on 46
Solaris 17
Specified user 46
SPN 45
SQL Server Analysis Services 44
SQL Server security 44
SSAS 44
SSL 27
SSO 51
Starting and stopping the MDAS server 18
Starting and stopping Tomcat 33
startup types 20
support

customer 63

locations 63

technical 63

web site 63

user name and password 21
user-specified credentials 51

V

View metrics 31

W

web

customer support 63
getting documentation via 62
useful addresses 65

web application server

Secure Socket Layer 28

web sites

support 63

training 64
Windows NT service name 25
workspaces

changing the cube 59
wrapper 28

T

Tanukisoft 28
technical support 63
timeout 25, 31
Tomcat

starting and stopping 33
training, on Business Objects products 64
troubleshooting 41

U

unstable system 19
user access 27

BusinessObjects Voyager Administrator’s Guide 69

Index

70 BusinessObjects Voyager Administrator’s Guide