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
2008-12-04
Contents
Getting Started23Chapter 1
About this help...........................................................................................24
What's new in BusinessObjects Enterprise XI 3.0?...................................25
Where should I start?.................................................................................28
This help provides you with information and procedures for deploying and
configuring your BusinessObjects Enterprise system. Procedures are provided
for common tasks. Conceptual information and technical details are provided
for all advanced topics.
For daily maintenance tasks and procedures for working with the CMC, see
the BusinessObjects Enterprise Administrator's Guide.
For information about installing BusinessObjects Enterprise, see the
BusinessObjects Enterprise Installation Guide.
Who should use this help?
This help covers deployment and configuration tasks. We recommend
consulting this guide if you are:
•planning your first deployment
•configuring your first deployment
•making significant changes to the architecture of an existing deployment
•improving your system's performance.
This help is intended for system administrators who are responsible for
configuring, managing, and maintaining a BusinessObjects Enterprise
installation. Familiarity with your operating system and your network
environment is beneficial, as is a general understanding of web application
server management and scripting technologies. However, to assist all levels
of administrative experience, this help aims to provide sufficient background
and conceptual information to clarify all administrative tasks and features.
About BusinessObjects Enterprise
BusinessObjects Enterprise is a flexible, scalable, and reliable solution for
delivering powerful, interactive reports to end users via any web
application—intranet, extranet, Internet or corporate portal. Whether it is
used for distributing weekly sales reports, providing customers with
personalized service offerings, or integrating critical information into corporate
portals, BusinessObjects Enterprise delivers tangible benefits that extend
across and beyond the organization. As an integrated suite for reporting,
analysis, and information delivery, BusinessObjects Enterprise provides a
solution for increasing end-user productivity and reducing administrative
efforts.
What's new in BusinessObjects Enterprise
XI 3.0?
This version of BusinessObjects Enterprise introduces many new features
and enhancements. The following table briefly describes these features and
where to find more information about them.
Documentation resourcesWhat's New
1
Server Intelligence: Server management is now
handled through the CMC. This enhancement
simplifies many common server management
procedures, and introduces new features that
make it easier to add and configure servers,
monitor server status, and automate server
processes.
Cloning servers: Instead of manually configuring
a new server, you can create a new "cloned"
server based on the configuration settings of
an existing server.
•
About Server Intelligence on page 208
•
Server management:
what's new in this version of BusinessObjects
Enterprise on page 209
Federation: This new feature is an important
cross-site replication tool. Federation allows
you to manage content from a BusinessObjects
Enterprise deployment (Origin site) and replicate
it to other BusinessObjects Enterprise deployments (Destination sites). Both one-way and
two-way replication is possible, as well as setting replication on a recurring schedule. With
Federation, you can manage your content from
one site, streamline global processes and reduce network traffic.
Access levels: This release of BusinessObjects
Enterprise lets you create and maintain access
levels that are customized for your deployment
and security needs. Access levels are groups
of rights that users frequently need. They allow
administrators to set common security levels
quickly and uniformly.
Documentation resourcesWhat's New
•For more information
about Federation, see
the BusinessObjects
Enterprise Administrator's Guide. The latest
version of the PDF is
available on the Business Objects technical
support site.
•
How rights work in BusinessObjects Enterprise
on page 586
•
Working with access
levels on page 605
Publishing: This version features many enhancements to the Publishing feature, including support for Crystal reports and Web Intelligence
documents, new processing capabilities, and
the ability to publish to multiple formats and
destinations and enhanced PDF, as well as
support for customized publication extensions,
dynamic recipients, and delivery rules.
sion of the PDF is available on the Business
Objects technical support site.
What's new in BusinessObjects Enterprise XI 3.0?
Instance Manager: This version features a new
area of the CMC called the Instance Manager,
which allows you to manage all of the instances
on BusinessObjects Enterprise from one location. You can multi-select instances to perform
batch operations on them, such as pause, resume, run now, or delete. You can also use the
Instance Manager to request detailed information for a single instance, which is useful when
you need to diagnose and resolve system
problems that cause instances to fail.
Auditing: The range of auditable actions and
details on those actions has been increased.
Administrators can now audit client applications
(including Desktop and Web Intelligence), and
Desktop Intelligence server actions. The auditing Universe has been extended, and a greater
amount of detail will be captured by the auditing
events, including template and instance IDs, as
well as IP addresses and machine names for
client applications.
Getting Started
Documentation resourcesWhat's New
•
Instance Manager on
page 756
•
Managing instances on
page 753
•
Managing Auditing on
page 443
1
Content Search: Content Search is an optimized
search tool that enables InfoView users to
search within the content of objects managed
by BusinessObjects Enterprise. Content Search
can recognise stem and stop words, search
techniques used similar to those used in other
search engines, and enables users to search
in multiple languages. Content Search refines
the search results by grouping them into categories of similar object types, and ranking them
in order of their relevance to the search term.
It can recognise search terms in data structure
and suggest new Web Intelligence queries that
may contain the data users are searching for.
Searches in InfoView.
For information on conducting Content Searches, see the BusinessOb-
jects Enterprise InfoView
User’s Guide.
Getting Started
1
Where should I start?
Online documentation library
A completely new interface to the full documentation set now has guides for
all Business Objects products. The new online documentation library has
the most up-to-date version of the Business Objects product documentation,
posted upon publication and updated regularly. You can browse the library
contents, run full-text searches, read guides on line, and download PDFs.
Depending on your situation, you may want to focus on specific sections of
this help, and there may be other resources available for you. For each of
the following situations, there is a list of suggested tasks and reading topics.
•
Planning or performing your first deployment on page 28
•
Configuring your deployment on page 29
•
Changing your deployment's architecture on page 29
•
Improving your system's performance on page 30
•
Working with objects in the CMC on page 30
Planning or performing your first deployment
If you are planning or performing your first deployment of BusinessObjects
Enterprise, it is recommended that you perform the following tasks and read
the corresponding sections:
•
To get familiar with the components, read Architectural overview on
page 36.
•To assess your needs and design a deployment architecture that works
best for you, read the BusinessObjects Enterprise Deployment PlanningGuide.
•
Understanding communication between BusinessObjects Enterprise
components on page 358
•
Security overview on page 84
•
If you plan to use third-party authentication, read Configuring Third-Party
•For advice about assessing your anticipated performance needs, see
Improving performance on page 400.
•For more information about installing BusinessObjects Enterprise, see
the BusinessObjects Enterprise Installation Guide.
•
After you install, read Server management overview on page 202.
Configuring your deployment
If you have just completed your installation of BusinessObjects Enterprise
and need to perform initial configuration tasks, such as firewall configuration
and user management, it is recommended that you read the following
sections:
•
Server management overview on page 202
•
Understanding communication between BusinessObjects Enterprise
components on page 358
•
Security overview on page 84
Getting Started
Where should I start?
1
•
If you plan to use third-party authentication, read Configuring Third-Party
Authentication on page 105
•For advice about assessing and improving your system's performance,
see Improving performance on page 400.
•
If you want to monitor your existing system, read Managing Auditing on
page 443 and Auditing Reports on page 479.
Changing your deployment's architecture
Are you expecting a significant increase in server traffic? Do you need to
accommodate a sudden influx of users? Do you need to incorporate new
kinds of content from new sources? Or do you need to update a deployment
that didn't adequately anticipate the volume of objects being processed on
a daily basis?
If you need to revise your deployment to account for significant changes in
how you use the system, it is recommended that you read the following
sections:
•For advice about assessing and improving your system's performance,
see Improving performance on page 400.
•
If you are installing new server components, see Server management
overview on page 202.
•
If you are importing or configuring new users, see Account management
overview on page 624.
•For information about installing new components, you can find more
information in the BusinessObjects Enterprise Installation Guide.
Improving your system's performance
If you want to assess your deployment's efficiency and fine-tune it in order
to maximize resources, it is recommended that you read the following
sections:
•For advice about assessing and improving your system's performance,
see Improving performance on page 400.
•
If you want to monitor your existing system, read Managing Auditing on
page 443 and Auditing Reports on page 479.
•For daily maintenance tasks and procedures for working with servers in
the CMC, see Server management overview on page 202.
Working with objects in the CMC
If you are working with objects in the CMC, read the following sections:
•
To get started with the CMC, see Using the CMC on page 578.
•For information about setting up users and groups in the CMC, see
Account management overview on page 624.
•
To publish objects to BusinessObjects Enterprise, see About Publishing
on page 810
•
To set security on objects, see How rights work in BusinessObjects
BusinessObjects Enterprise Installation and Configuration
Guide
BusinessObjects Enterprise
Administrator's Guide
This guide covers the key concepts you
should consider before you begin deploying BusinessObjects Enterprise. This
guide includes an overview of the architecture, tips for assessing your existing environment, determining your organization's
needs, and preparing for the installation.
Leads you through the steps required to
run the setup program and complete your
installation of BusinessObjects Enterprise.
There are UNIX and Windows versions of
this guide available.
Provides content for server administration
and content administration. The server
administration topics includes server configuration, managing authentication, configuring firewalls, and measuring system
performance. The content administration
topics include working with the CMC,
configuring rights and access levels,
managing users, and working with Business Objects applications and objects.
Provides an overview of the publishing
process, working with publications, publishing Crystal reports, publishing web intelligence documents, publishing desktop
intelligence documents, and publishing
security.
Getting Started
BusinessObjects Enterprise guides
DescriptionGuide
1
BusinessObjects Enterprise Migration Guide
BusinessObjects Enterprise
Upgrade Guide
BusinessObjects Enterprise InfoView User's Guide
For a complete list of all of our product documentation please visit our support
site: http://support.businessobjects.com/documentation/product_guides/de
fault.asp
Details content migration from legacy
Business Objects software, such as Classic or Enterprise 5 or 6, to BusinessObjects Enterprise XI 3.0.
Information for upgrades from BusinessObjects Enterprise XI to BusinessObjects
Enterprise XI 3.0.
Provides an overview of InfoView and
working with Crystal Reports, Web Intelligence, objects, discussions, encyclopedia,
and Voyager workspaces.
This section outlines the overall platform architecture, system tiers, and
individual services and components that make up the business intelligence
(BI) platform. This information will help administrators understand the
essentials of BusinessObjects Enterprise and how to plan the deployment,
management, and maintenance of the system.
BusinessObjects Enterprise includes specialized services including Web
Intelligence, Desktop Intelligence, and Crystal Reports components, and a
set of Dashboard and Analytics services for metrics management, predictive
analysis, and process analysis. These services are available to software
created by your own organization through several application programming
interfaces (APIs).
BusinessObjects Enterprise is designed for high performance across a broad
spectrum of user and deployment scenarios. For example, specialized
platform services are included that handle either on-demand data access
and report generation or time- or event-based report scheduling. You can
offload processor intensive scheduling and processing to dedicated servers
to improve performance. The architecture is designed to meet the needs of
virtually any BI deployment, and is flexible enough to grow from several users
with a single tool, to tens of thousands of users with multiple tools and
interfaces.
Architecture basics
The BusinessObjects Enterprise technical architecture is composed of a set
of tiers optimized for specific tasks and operations. The five tiers are:
•Client: web browser and rich clients.
•Application: Java web application servers and tools.
Developers can access the platform using a set of web services and Java
APIs to integrate BusinessObjects Enterprise into other enterprise systems,
and to share dynamically updated documents with users on separate
networks.
End users can access, create, edit, and interact with reports using specialized
tools and applications that include:
•Crystal Reports.
•Web Intelligence.
•Desktop Intelligence.
•Voyager.
•Dashboard and Analytics.
•Dashboard Builder.
IT departments can use data and system management tools that include:
•Central Management Console.
•Central Configuration Manager.
•Import Wizard.
•Publishing Wizard.
•Universe Designer.
•Repository Diagnostic Tool.
To provide flexibility, reliability, and scalability, the components that make
up BusinessObjects Enterprise can be installed on one or many machines.
You can even install two BusinessObjects Enterprise deployments
simultaneously on the same hardware, although this configuration is
recommended only for upgrade or testing purposes.
Server processes can be "vertically scaled" (where one computer runs
several, or all, server-side processes) to reduce cost, or "horizontally scaled"
(where server processes are distributed between two or more networked
machines) to improve performance. It is also possible to run duplicate
instances of a server process on the same machine, or across several
networked machines.
Note:
Server processes run as "services" on Windows machines, and as "daemons"
on UNIX machines. While it is possible to deploy a mixture of Windows and
UNIX platforms at the tier level (such as a UNIX web application server with
a Windows CMS), it is recommended that you do not mix operating systems
for server processes (such as a cluster of two CMS systems where one runs
Windows and the other runs UNIX).
Two application categories are available in the client tier: operating system
independent web applications that run in web browsers, like Internet Explorer,
Firefox, or Safari; and rich desktop applications installed on a Microsoft
Windows operating system.
Browser-based web applications
The first category is made up of light-weight, web browser-based client
front-ends that run on all supported operating system platforms. A web
application server receives client requests and interfaces with the
BusinessObjects Enterprise intelligence and processing tiers to return data
to the users' web browsers. This approach allows you to provide business
intelligence (BI) access to large groups of users through your intranet or the
web, without the challenges of deploying desktop software products.
Communication is conducted over HTTP and can be secured with SSL by
enabling HTTPS encryption on the web application server. Examples of this
type of application include the InfoView, Web Intelligence, Central
Management Console (CMC), and report viewers.
Architecture
Client tier components
2
Desktop applications
The second category is made up of locally installed, rich-client applications
installed on a supported Microsoft Windows operating system. This approach
allows you to offload BI processing from BusinessObjects Enterprise onto
individual client computers. Most desktop applications directly access your
organization's data through middleware drivers installed on the desktop, and
communicate with your BusinessObjects Enterprise deployment through
CORBA or encrypted CORBA SSL. Examples of this type of application
include Crystal Reports, Desktop Intelligence, and Live Office clients.
Note:
Although Live Office is a desktop application, it communicates with
BusinessObjects Enterprise web services over HTTP. You can configure
BusinessObjects Enterprise so that Microsoft Office documents containing
Live Office components dynamically update, even when sent to recipients
outside your organization's secured network.
Browser-based web applications use web technologies such as, Active X,
Flash, Ajax framework, J2EE, and .NET web components (framework and
reporting services) to integrate with BusinessObjects Enterprise.
These web applications also act as an effective demonstration of how
BusinessObjects Enterprise software development kits (SDKs) can be used
to create custom web applications for end users or administrators.
InfoView
InfoView can access, interact with, and export, any type of business
intelligence including reports, analytics, dashboards, scorecards, and strategy
maps.
InfoView allows users to manage:
•BI catalog browsing and searching.
•BI content access (creating, editing, and viewing).
•BI content scheduling and publishing.
Central Management Console (CMC)
The Central Management Console (CMC) is a web-based tool to perform
day-to-day administrative tasks, including user management, content
management, and server management. It also allows you to publish, organize,
and set security levels for all of your BusinessObjects Enterprise content.
Because the CMC is a web-based application, you can perform all of these
administrative tasks remotely.
All users can log on to the CMC to change their user preference settings.
Only members of the Administrators group can change management settings,
unless explicitly granted the rights to do so.
The CMC also demonstrates how you can use the administrative objects
and libraries in the BusinessObjects Enterprise software development kit
(SDK) to create custom web applications for administering BusinessObjects
Enterprise.
Server Intelligence is a component of the Central Management Console
(CMC) that simplifies administrative procedures previously carried out by
the Central Configuration Manager (CCM), such as the management of CMC
server processes. This includes the addition and removal of server processes,
server process configuration, and the automatic restart or shutdown of servers
that encounter unexpected conditions.
Server Intelligence also archives server process information in the CMS
database so you can easily restore default server settings, or create
redundant instances of server processes with the same settings.
Note:
The CCM is a tool that allows you to configure and manage the Server
Intelligence Agent. The Server Intelligence Agent is the component that
allows you to manage all servers through the CMC.You can also use the
CCM to create and manage nodes in your deployment.
Dashboard and Analytics
Dashboard and Analytics integrates all performance data and processes,
enabling CFOs, finance departments, and business managers to track and
analyze key business metrics and goals via management dashboards,
scorecards, and alerting.
2
Business Objects dashboard and scorecard products consist of an integrated
dashboard, scorecard, and dashboard builder, as well as a catalog of analytic
templates and five integrated analytic engines. The five analytic engines
(metrics, rules, sets, predictive, and process analysis) provide the processing
power to monitor performance, alert to exceptions, track customer segments,
forecast, and analyze business processes.
Web Intelligence
Web Intelligence is a scalable online query and analysis tool for knowledge
workers to build queries and analyze business information through a user
friendly drag-and-drop interface. The patented Business Objects semantic
layer hides the complexity of underlying data sources. Reports can be
published to the BusinessObjects Enterprise web portal, or to Microsoft Office
applications using BusinessObjects Live Office.
Voyager is an AJAX-based online analytical processing (OLAP) web client
designed for business and financial analysts. It not only provides access to
a wide range of OLAP databases, but also allows users to combine
information from different systems within a single workspace. Voyager offers
a comprehensive range of business and time calculations, and includes
features such as time sliders to make the analysis of OLAP data as simple
as possible.
The Voyager OLAP feature set complements both Crystal Reports (for direct
data access to OLAP cubes for production reporting) and Web Intelligence
(for ad hoc analytic reporting with universes built on OLAP data sources).
Xcelsius
Xcelsius is a data visualization tool that transforms BI data into engaging
presentations and dashboards. It enables the integration of dynamically
updated data into Microsoft Office, PDF, and web documents with Business
Objects queries and reports. Xcelsius is comprised of designer and viewing
extensions leveraging Business Objects web services.
BusinessObjects Mobile
BusinessObjects Mobile allows your organization access to information from
any wireless device. Management and information workers can stay
up-to-date and make decisions with access to the latest information. Sales
and field service staff can provide the right customer, product, and work order
information, where and when it's needed, helping to shorten sales cycles,
and increasing customer satisfaction.
Report viewers
BusinessObjects Enterprise includes report viewers that support different
platforms and different browsers in the client tier, and which have different
report viewing functionality.
Report viewers fall into two categories:
•Client-side viewers (Active X viewer, Java viewer)
Client-side viewers are downloaded and installed in the user's browser.
When a user requests a report, the application server processes the
request, and retrieves the report pages from the BusinessObjects
Enterprise framework. The application server then passes the report
pages to the client-side viewer, which processes the report pages and
displays them directly in the browser.
•Zero-client viewers (DHTML viewer)
Zero-client viewers reside on the application server. When a user requests
a report, the application server processes the request, and then retrieves
the report pages from the BusinessObjects Enterprise framework. The
application server processes the report and creates DHTML pages that
the viewer displays in the user's web browser.
All report viewers help process requests for reports, and present report pages
that appear in the user's browser.
For more information on the specific functionality or platform support provided
by each report viewer, see the BusinessObjects Enterprise InfoView User'sGuide or the Crystal Reports Developer's Guide, available at the customer
support portal: http://support.businessobjects.com/documentation/prod
uct_guides/default.asp.
2
Installed desktop client applications
The installed desktop client applications interact with the BusinessObjects
Enterprise intelligence or processing servers. They do not communicate with
the Java web application server. Communication between the clients and
the servers can be secured with SSL encryption (CORBA SSL).
Desktop products are installed client applications that run on Microsoft
Windows operating systems. They can store resources locally and access
your organization's data through locally installed database driver middleware
or the Central Management Console (CMC).
Business Views Manager
Business Views is a multi-tier system that enables companies to build
comprehensive and specific Business Views objects that help report designers
and end users access the information they require.
Administrators use the Business View Manager—a thick-client designer,
which runs as a Microsoft Windows application. This designer provides a
wide range of capabilities for creating Data Connections, Dynamic Data
Connections, Data Foundations, Business Elements, and Business Views.
The Business View Manager allows you to design relational views of
information. This designer also allows you to set detailed column and
row-level security for various objects in a report.
Crystal Reports Designer
Crystal Reports Designer allows database experts or application developers
to create and integrate detailed reports that can be easily shared with others
using Crystal Reports Viewer or a web browser.
Crystal Reports Viewer
The Crystal Reports Viewer is available as a free download from
http://www.businessobjects.com/product/catalog/crystalreports, and allows
users to open reports created in read-only mode. Reports cannot be
refreshed, as the data used is saved within the report itself.
Central Configuration Manager (CCM)
The CCM is a server troubleshooting and node configuration tool provided
in two forms. In a Microsoft Windows environment, the CCM allows you to
manage local and remote servers through its graphical user interface (GUI)
or from a command line. In a UNIX environment, the CCM shell script
(ccm.sh) allows you to manage servers from the command-line.
The CCM allows you to view and to modify server settings only while Business
Objects server processes are offline. The Central Management Console
(CMC) is used to stop server processes, then the CCM is used to modify
performance settings or change server port numbers.
Note:
Most server management tasks are now handled through the CMC, not in
the CCM. The CCM was the primary tool for server management in previous
versions, but the CCM is now used only for troubleshooting and node
configuration.
Desktop Intelligence
Desktop Intelligence is an integrated query, reporting and analysis tool that
allows you to access data using familiar business terms, rather than using
technical database query methods, like SQL. The complexity of the underlying
data storage is abstracted in the semantic data layer known as the Business
Objects Universe.
Data Source Migration Wizard
The Data Source Migration Wizard allows you to migrate reports that are
based on Crystal Reports queries, dictionaries, or InfoViews, to a
BusinessObjects Enterprise deployment.
You can migrate two types of objects: reports and data sources. The wizard
converts the data source of each report into an object that is usable in
BusinessObjects Enterprise, and then resets the data source location of the
report to point to the new object. The result is that you can use the new
features of BusinessObjects Enterprise while keeping the functionality of the
reports and data sources from your previous installation.
Repository Diagnostic Tool
The Repository Diagnostic Tool (RDT) is new for BusinessObjects Enterprise
XI 3.0. This tool can scan, diagnose, and repair inconsistencies that may
occur between the Central Management Server (CMS) system database
and the File Repository Servers (FRS) filestore.
2
RDT scans the CMS system database and identifies inconsistencies. It can
also repair the logged inconsistencies, and report the repair status and
completed actions. To determine synchronization between the file system
and database, RDT should be used after the user first completes a hot
back-up. Or the customer can use the RDT after a restoration and prior to
starting their BusinessObjects Enterprise services. The user can set a limit
for the number of errors the RDT will find and repair before stopping.
Import Wizard
The Import Wizard guides administrators through the process of importing
universes, reports, users, groups, and folders, from a previously released
version of BusinessObjects Enterprise to the latest version. It also allows
administrators to export to BIAR (Business Intelligence Archive Resource)
files.
The Import Wizard runs on Microsoft Windows platform, but can be used to
import information into BusinessObjects Enterprise systems running any
supported Windows or UNIX operating system.
BusinessObjects Live Office integrates with the Microsoft Office environment,
allowing for dynamically updated data to be embedded within Microsoft
PowerPoint, Excel, and Word documents. Plus, you can share your
documents with others over the web for collaborative decision-making. From
within Microsoft Office, you can use intuitive wizards and toolbars to easily
connect to a Crystal report, Web Intelligence document, or use ad hoc data
selections. Then format your data using familiar Microsoft Office tools.
Using Live Office, you can publish "live" documents to BusinessObjects
Enterprise for sharing with your coworkers through a business intelligence
portal. Or, take it outside the firewall and email it to an off-site partner or
coworker.
Note:
Web services applications are currently only supported with the following
load balancer configurations:
1. Source IP address persistence.
2. Source IP and destination port persistence (available only on a Cisco
Content Services Switch).
3. SSL persistence.
Note:
SSL persistence may cause security and reliability issues on some web
browsers. Check with your network administrator to determine if SSL
persistence is appropriate for your organization.
For information on configuring web services to work with Live Office, see the
BusinessObjects Enterprise Web Services Administrator Guide.
Publishing Wizard
The Publishing Wizard enables both administrators and end users to create
and publish reports to BusinessObjects Enterprise. By assigning object rights
to individual folders on a given server, you control who can publish reports
and where they are published.
Use the Publishing Wizard if you have access to the application and you
want to add multiple objects or an entire directory of objects to
BusinessObjects Enterprise. Once an object is added, it appears in the folder
that you specified in InfoView (or your customized web desktop) and in the
Folders management area of the CMC.
For more information, see the Adding Objects to the Repository chapter of
BusinessObjects Enterprise Administrator's guide.
Query as a Web Service
Query as a Web Service provides new and easy ways to analyze information
through user-driven client solutions for businesses. Business Intelligence
(BI) content is usually bound to a specific user interface of BI tools. Query
as a Web Service changes this by allowing BI content to be delivered to any
user interface that can process web services.
Using Query as a Web Service, business users define their own query from
a universe, and then easily and securely publish that query as a standalone
web service.
Query as a Web Service provides new client solutions for businesses. For
example, it enables Crystal Xcelsius to aggregate multiple disparate data
sources into a trusted BI view.
Query as a Web Service also enables a range of client-side solutions in tools
such as:
•Microsoft Office, Excel, and InfoPath.
•SAP Application Server.
•OpenOffice.
•Business rules and process management applications.
•Enterprise Services.
2
Report Conversion Tool
The Report Conversion Tool converts Desktop Intelligence reports to the
Web Intelligence format and publishes the converted reports to the CMS.
It retrieves reports from the CMS, in the Public, Favorites, or Inbox folders.
Once converted, you can publish to the same folder as the original Desktop
Intelligence report or to a different folder. The tool does not convert all
Desktop Intelligence features and reports. The level of conversion depends
on the features in the original report. Some features prevent the report from
being converted. Other features are modified, reimplemented, or removed
by the tool during conversion.
The tool assigns one of three statuses to each report:
The Report Conversion Tool also lets you audit your converted reports. This
helps identify reports that cannot be fully converted by the Report Conversion
Tool and explains why.
Translation Manager
BusinessObjects Enterprise provides support for multilingual documents and
universes. A multilingual document contains localized versions of universe
metadata and document prompts. A user can create reports, for example,
from the same universe in their chosen languages.
The Translation Manager is the tool that defines the multilingual universes
and manages translation of universes and their Web Intelligence documents
and prompts.
Translation Manager:
•Translates universe or a Web Intelligence documents for a multilingual
audience.
•Defines the metadata language parts of the document and the appropriate
translation. It generates external XLIFF format and imports XLIFF files to
get translated information.
•Lists the universe or Web Intelligence document structure to be translated.
•Lets you translate the metadata through the interface.
•Lets you translate the metadata using external translation tools by
exporting and importing XLIFF files.
•Creates a multilingual document where several languages can be saved.
Universe Builder
A universe is a semantic layer of abstraction that exists between
BusinessObjects Enterprise and the data in your organization's database.
Universe Builder allows you to create universes from XML metadata and
Oracle Analytic Services.
Universe data sources can be multi-dimensional objects (dimensions,
measures, details), enabling the end user to analyze the data without needing
to know the details of the underlying database structure.
Once you start Universe Builder, you connect to a metadata source, then
using a universe creation wizard, map metadata structures to equivalent
classes, objects, dimensions, and details, used in a standard BusinessObjects
universe.
You can create universes from metadata sources with both Universe Builder
and Designer. Universe Builder is a stand-alone product that provides an
independent user interface for universe creation from metadata sources.
Designer is used for the universe generation at the end of the creation
process.
Universe Designer
Universe Designer provides a connection wizard that allows you to connect
to your database middleware. You can create multiple connections with
Designer, but only one connection can be defined for each universe. This
database connection is saved with the universe.
Designer provides a graphical interface to select and view tables in a
database. The database tables are represented as table symbols in a schema
diagram. You can use this interface to manipulate tables, create joins between
tables, create alias tables, create contexts, and solve loops in your schema.
Web Intelligence users do not see this schema.
2
Web Intelligence rich client
Web Intelligence can be used offline as a Web Intelligence rich client, as a
standalone Microsoft Windows application equivalent to the Java Report
Panel. Web Intelligence rich client allows you to continue to work with Web
Intelligence documents (WID) when you are unable to connect to a CMS,
when you want to perform calculations locally rather than on the server, and
when you want to work with Web Intelligence documents without installing
a CMS or application server.
Web Intelligence rich client can also be used when connected to a CMS.
Application tier components
The application tier acts as the translation layer between the end user and
the processing tier. A third-party web application server hosts Java SDK
modules to process requests from the user tier, then communicates those
requests to the appropriate service in BusinessObjects Enterprise.
The web and application services tier communicate with the following
BusinessObjects Enterprise :
•The BusinessObjects Enterprise SDK.
•BusinessObjects Enterprise web services.
Web application servers
BusinessObjects Enterprise requires a Java web application server to process
the server-side scripts that make up web applications. You can install the
Tomcat web application server during the BusinessObjects Enterprise
installation, or use a supported third-party web application server and Java
Development Kit (JDK).
The following web application servers are supported in BusinessObjects
Enterprise.
•WebSphere 6.1.
•WebSphere Community Edition 2.0.
•WebLogic 10.
•WebLogic 9.2.
•Tomcat 5.5 (bundled with BusinessObjects Enterprise).
The BusinessObjects Enterprise Java 2 Enterprise Edition (J2EE) software
development kit (SDK) allows you to create Java web applications that run
on the web application server in your BusinessObjects Enterprise deployment.
SDKs give you the ability to create web applications that integrate powerful
reporting features, such as those offered by Web Intelligence or InfoView.
The following Java SDKs are included with BusinessObjects Enterprise.
•BusinessObjects Enterprise Java SDK.
•Report Engine Java SDK.
•Report Application Server (RAS) Java SDK.
•Viewers Java SDK.
•Web services Java SDK.
•JavaServer Faces Components (JSF) for BusinessObjects Enterprise
SDK.
Architecture
2
BusinessObjects Enterprise Java SDK
The BusinessObjects Enterprise SDK allows you to incorporate
BusinessObjects Enterprise functionality into your own web applications.
1. Authentication and session management.
Users can be authenticated by using the BusinessObjects Enterprise
authentication protocol or some other protocol, such as LDAP or Kerberos.
Once the user is authenticated, a user session is created. The user
session maintains state information as the user performs actions and
navigates to different pages within the BusinessObjects Enterprise web
application.
The information entity in BusinessObjects Enterprise is the InfoObject.
All operations involve the retrieval and manipulation of InfoObjects from
the Central Management Server (CMS).
3. Report operations.
The BusinessObjects Enterprise SDK supports many types of report
documents: Crystal reports, Web Intelligence and Desktop Intelligence
documents, as well as Microsoft Excel, and Adobe's Portable Document
Format (PDF), among others.
4. Administering BusinessObjects Enterprise.
Many aspects of a BusinessObjects Enterprise deployment can be
administered programmatically, such as managing server process and
server process groups, and server auditing.
Report Engine SDK
The Report Engine SDK includes libraries that you can use to build a web
report design tool. Applications built with this SDK can view, create, or modify,
a variety of different Web Intelligence and Desktop Intelligence documents.
Users can modify documents by adding, removing, and modifying objects
such as tables, charts, conditions, and filters.
Report Application Server (RAS) Java SDK
The Report Application Server (RAS) Java SDK is an API for developing
Java web applications with advanced report creation and modification
functionality. With the RAS Java SDK, you can create Java client applications
that interact with the RAS server from a web application server.
Web application users can create or modify Crystal reports by adding,
removing, or modifying tables, charts, parameters, and fields.
Viewers Java SDK
The Viewers SDK is an API that lets you incorporate reports in a range of
different formats within your web application.
Viewers are a 'thin-client' technology - users of your web application don't
need to install any additional software in order to view the reports. Two Java
viewers are available:
This viewer provides basic thin-client report viewing capabilities to present
data and allow drill-down, page navigation, zooming, prompting, text
searching, highlighting, exporting, and printing.
2. Report parts viewer.
This viewer provides the ability to view individual report parts including
charts, text, and fields.
Web services Java SDK
See BusinessObjects Web Services on page 55.
JavaServer Faces (JSF) SDK
The JavaServer Faces (JSF) SDK consists of JavaServer Faces components
and managed Java beans built on top of the BusinessObjects EnterpriseJava
SDK. The components encapsulate common BusinessObjects Enterprise
functionality, such as logging on to the system, navigating through folders
and categories, listing managed content, and viewing Crystal reports.
JSF component functionality can be divided into several main areas of
BusinessObjects Enterprise application development.
1. Identifying end users in a BusinessObjects Enterprise system.
2
Individual users can be associated with their actions, such as logging on
or off, and changing a password.
2. Listing and navigating managed content.
Users can navigate repetitive information using nested lists rendered from
a data source.
3. Scheduling of managed content.
Your application's users can schedule reports to run at custom intervals
if you create pages that enable a user to set scheduling options.
4. Viewing managed content.
The ReportPageViewer component lets you quickly add the ability to
view reports on a page.
The following .NET SDKs are included with BusinessObjects Enterprise.
•Report Application Server (RAS) .NET SDK.
•Crystal Reports .NET SDK.
•Web services .NET SDK.
Report Application Server (RAS) .NET SDK
The Report Application Server (RAS) SDK is a API for developing .NET web
applications with advanced report creation and modification functionality.
With the RAS .NET SDK, you can create .NET client applications that interact
with the RAS server from a web application server.
Web application users can create or modify Crystal reports by adding,
removing, or modifying tables, charts, parameters, and fields.
Crystal Reports .NET SDK
The Crystal Reports .NET SDK allows you to incorporate BusinessObjects
Enterprise functionality into your own web applications, including:
1. Core functions.
Embed Crystal Reports Designer in your applications for report creation.
2. Database connections.
Log on to a database server and access data.
3. Report data manipulation.
Filter, group, sort, and total report data.
4. Report appearance and report objects.
Format, work with field and text objects, and enhance report presentation.
5. Printing and Exporting.
Export reports to other formats, and print reports.
Business Objects Web Services provide a Java and .NET API accessed by
rich clients in the user interaction tier, such as Live Office and Crystal Reports.
Web Services consists of software components that can be called remotely
using the Simple Object Access Protocol (SOAP). SOAP is a protocol for
exchanging information that is not dependent on a specific platform, object
model, or programming language.
BusinessObjects Enterprise Web Services includes functionality in the
following areas:
•Session
Authentication and user privilege management.
•BI platform
Exposes advanced platform features such as scheduling, search, user
and group administration, server administration, platform events, and
calendars.
Architecture
Application tier components
2
•Report Engine
Displays Web Intelligence and Crystal Reports in HTML, PDF, Excel, and
XML format.
•Query
Builds ad-hoc queries based on the Business Objects universe semantic
layer.
Business Objects web services uses standards such as XML, SOAP, AXIS
2.0 and WSDL. The platform follows WS-Interoperability Basic Profile
1.0 web services specification.
Note:
Web Services applications are currently only supported with the following
load balancer configurations:
1. Source IP address persistence.
2. Source IP and destination port persistence (available only on a Cisco
SSL persistence may cause security and reliability issues on some web
browsers. Check with your network administrator to determine if SSL
persistence is appropriate for your organization.
For information on installing and configuring Web Services, see the
BusinessObjects Enterprise Web Services Administrator Guide.
Query as a Web Service
Business Objects Query as a Web Service is a wizard-based application that
allows queries to be made into a web service and integrated with web-ready
applications. Queries can be saved to create a catalog of standard queries
that application builders can select as required.
Business Intelligence (BI) content is usually bound to a specific user interface
of BI tools. Query as a Web Service changes this by allowing BI content to
be delivered to any user interface that can process web services.
Query as a Web Service is designed to work on top of any Microsoft Windows
application the same way as other web services. Query as a Web Service
is based on the W3C web service specifications SOAP, WSDL, and XML. It
has two main components:
1. Server component
The server component (included in BusinessObjects Enterprise) stores
the Query as a Web Service catalog and hosts the published web services.
2. Client tool
This is how business users create and publish their queries as a web
service on the server. You can install the client tool on several machines
that can access and share the same Query as a Web Service catalog
stored on the server. The client tool communicates with the server
components via web services.
Query as a Web Service allows web queries to be used as part of a range
of client-side solutions.
•Business rules and process management applications.
•Enterprise Service Bus platforms.
Packaged applications
This section describes the tools that are installed with BusinessObjects
Enterprise.
Dashboard and Analytics
Dashboard and Analytics is a suite of products that helps users track and
analyze key business metrics via management dashboards, scorecards, and
alerting. These products allow goals to be set around metrics and assigned
to owners; they also support group decision-making and analysis via
integrated collaboration and workflow capabilities. Dashboard and Analytics
includes the following products:
•Dashboard Builder
•Performance Manager
•Set Analysis
•Predictive Analysis
•Process Analysis
Architecture
Application tier components
2
The Dashboard and Analytics repository stores the metrics, goals, sets and
calendar definitions, used by Dashboard and Analytics users to create
dashboards and analytics. Each time users refresh a metric, the values for
the metric refresh are written to the Dashboard and Analytics repository.
Note:
To use Dashboard and Analytics features, you must purchase a
BusinessObjects Enterprise license that includes Dashboard and Analytics
as part of the software license agreement.
Voyager
Voyager is an online analytical processing (OLAP) 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 is accessed from BusinessObjects InfoView in a web browser, which
can be distributed to a large number of users, including those outside of your
secure network, on the internet.
Voyager requires a connection to a supported OLAP data source, such as
Microsoft Analysis Services, SAP BW, or Oracle Hyperion Essbase.
Therefore, you must create a connection to data before analysts can begin
using Voyager to analyze data.
Note:
The Voyager web application is available only as a Java web application.
There is no corresponding Voyager application for .NET.
Deploying web applications with wdeploy
BusinessObjects Enterprise ships with a tool to ease the deployment of web
applications on supported web application servers. Based on the Apache
Ant scripting tool, wdeploy allows you to deploy WAR files to a web
application server in two ways:
1. Standalone mode.
All web application resources are deployed together on a web application
server that serves both dynamic and static content.
2. Distributed mode.
The application's dynamic and static resources are separated: static
content is deployed to a web server; dynamic content is deployed to a
web application server.
For more information about wdeploy, see the Post Installation Web
Application Deployment chapter of the BusinessObjects Enterprise Installationguide.
Intelligence tier
The Intelligence tier manages the BusinessObjects Enterprise system. It
maintains all of the security information, sends requests to the appropriate
servers, manages audit information, and stores report instances.
The Central Management Console (CMC) web application provides the ability
to add, remove, enable, or disable, BusinessObjects Enterprise servers.
These processes are grouped into three categories: Framework servers,
Processing servers, and Performance Management servers. For more
information about server management , see Chapter 6: Managing andConfiguring Servers in the BusinessObjects Enterprise Adminstrator's Guide
.
Framework servers
Framework servers provide back-end core system services that form the
foundation of the BusinessObjects Enterprise Business Intelligence platform.
Primary server process that provides services for all other servers in the Business
Intelligence (BI) platform, including management of:
•security
•objects
•servers
•auditing
events, and notifying the CMS of these
events.
Responsible for the creation of file system
objects, such as exported reports, and imported files in non-native formats.
Generic server that hosts multiple services
responsible for processing requests from
various sources. It can host services like
the Publishing Service and the Client Auditing Proxy Service.
Server instance(s)
managed by CMC
CentralManage
mentServer
EventServerResponsible for monitoring file based
InputFileReposi
tory, OutputFil
eRepository
AdaptiveProcess
ingServer
Processing servers
Processing servers are the back-end components that handle requests from
Web Intelligence, Desktop Intelligence, Crystal Reports, and Voyager.
connection and interaction
with the various datasources
and providing a common feature set to its clients, by emulating the missing features if
necessary.
Caches recently executed
Crystal reports to reduce
database requests.
Runs Crystal report queries
and returns data to Crystal
Reports Cache Server.
Caches recently executed
Desktop Intelligence reports
to reduce database requests.
Runs Crystal report queries
and returns data to Crystal
Reports Cache Server.
Server instance(s) managed
by CMC
ConnectionServerResponsible for handling
CrystalReportsCacheServ
er
CrystalReportsProcess
ingServer
DesktopIntelligence
CacheServer
DesktopIntelligencePro
cessingServer
Job Servers
Processes scheduled actions
on objects at the request of
the CMS. When you add a
Job server to the BusinessObjects Enterprise system, you
can configure the Job server
to:
to page requests by processing reports and generating
Encapsulated Page Format
(EPF) pages.
Runs Web Intelligence
queries and returns data to
the user.
OLAP framework server.Multi Dimension-
Server instance(s) managed
by CMC
ReportApplicationServerResponsible for responding
WebIntelligenceProcess
ingServer
MultiDimensionalAnaly
sisServicesServer
Performance Management servers are the back-end servers for the
Performance Management product suite. Performance Management is only
enabled if you purchase the appropriate BusinessObjects Enterprise software
license.
PMRulesServerCreates and monitors Performance Man-
SetsPro
cessServer
SetsQueryServ
er
Architecture
Intelligence tier
2
DescriptionServer kind
KXEN data mining engine and forecaster.Predictive
Analysis Server
Process Analysis Server
Dashboard
Server
Dashboard Analytics Server
Automate tracking of of variables through
BusinessObjects Enterprise.
Used by the Dashboard Builder to create
and manipute dashboards.
Used by the Dashboard Builder to create
and manipute analytic content.
Central Management Server (CMS)
The Central Management Server (CMS) maintains a database of information
about your BusinessObjects Enterprise system. This is known as the CMS
database. All the platform services are managed and controlled by the CMS.
The CMS also manages access to the system file store where the physical
documents are managed. The system repository database is maintained
using the provided MySQL database, or by using the supported database
of your choice.
Server instance(s) managed by CMC
PredictiveAnal
ysisServer
ProcessAnaly
sisServer
DashboardServ
er
DashboardAna
lyticsServer
CMS data includes information about users and groups, security levels,
content, and services. The CMS can also maintain an optional auditing
database of information about user actions, and files with the File Repository
Servers. This data allows the CMS to perform four main tasks:
•Maintaining security
The CMS enforces the application of rights at both the folder and object
level, and supports inheritance at the user and group level. It also supports
aggregation through a flexible, group-user membership model.
An integrated security system is available for customers who do not
currently use an entitlement database, although BusinessObjects
Enterprise is designed for integration with multiple concurrent third-party
security systems, such as LDAP, Siteminder, or Microsoft Active Directory.
When a change is made to a user in the entitlement database, the change
is then propogated to BusinessObjects Enterprise.
•Managing objects
The CMS keeps track of the object location and maintains the folder
hierarchy. "InfoObjects" are system metadata objects that contain contain
index information, and the actual documents or objects are stored in a
file store. The separation of the object definition (metadata) from the
document allows for fast object processing as only the required information
is retrieved from the system’s repository. The CMS also runs scheduled
report jobs.
•Managing servers
Server process are monitored by the CMS and allocates work to less
busy processes. It will also add or remove service instances as work
loads change or services become unavailable.
The CMS handles load balancing and automated clustering to avoid
bottlenecks and maximize hardware efficiency. In some multi-server
environments, BusinessObjects Enterprise may not require a separate
third-party load balancing system.
•Managing auditing
User actions can be monitored and written to a central audit database.
This information allows system administrators to better track and manage
their BusinessObjects Enterprise deployment.
The auditing functionality allows administrators to better understand which
users accessed the enterprise system, which documents they interacted
with, and the overall system metrics for system optimization. Usage data
is collected from the system interactions recorded in the auditing database.
A sample universe and sample auditing reports are also available to
provide fast access to information such as the most accessed reports,
peak system use times, and average user session times.
Note:
It is strongly recommended that you back up and audit the CMS system
database frequently.
The CMS database should not be accessed directly. System information
should only be retrieved using the calls that are provided in the
BusinessObjects Enterprise software development kit (SDK).
Restriction:
You may access the optional audit database in read-only mode to create
custom audit reports.
On Windows, the Setup program can install and configure its own MySQL
database if you do not already have a database server allocated for the
deployment. You can switch to a different database later if your deployment
needs change.
Event Server
The Event Server manages file-based events. When you set up a file-based
event within BusinessObjects Enterprise, the Event Server monitors the
directory that you specified. When the appropriate file appears in the
monitored directory, the Event Server triggers your file-based event: that is,
the Event Server notifies the CMS that the file-based event has occurred.
The CMS can then start any jobs that are dependent upon the file-based
event.
Architecture
Intelligence tier
2
Note:
Schedule-based and custom events are managed through the CMS.
File Repository Servers
Input and Output File Repository Server (FRS) processes run on each
BusinessObjects Enterprise server machine.
The Input FRS manages report and program objects that have been published
to the system by administrators or end users (using the Publishing Wizard,
the CMC, the Import Wizard, or a Business Objects designer component
such as Crystal Reports, or Web Intelligence report panels).
Objects with associated files, such as text files, Microsoft Word files, or PDFs,
are stored on the Input File Repository Server.
The Output FRS manages all of the report instances generated by the Report
Job Server or the Web Intelligence Processing Server, and the program
instances generated by the Program Job Server.
Tip:
If you use the BusinessObjects Enterprise SDK, you can also publish reports
from within your own code.
The FRSes are responsible for listing files on the server, querying for the
size of a file, querying for the size of the entire file repository, adding files to
the repository, and removing files from the repository.
Caution:
To avoid conflicts between input and output objects, the Input and Output
FRSes cannot share the same file system directory. In larger deployments,
there may be multiple Input and Output FRSes. However, only one set is
active at any given time. In this case, all Input File Repository Servers share
the same directory. Likewise, all Output File Repository Servers share the
same directory.
Cache servers
Cache servers handle report view requests. A cache server intercepts report
requests and checks if it can fulfill the request with a cached report page
before requesting new data from the database. This avoids accessing the
database each time a report is requested, which accelerates viewing
performance and reduces network traffic.
A cache server intercepts report requests sent from clients to the page server.
If the cache server cannot fulfill the request with a cached report page, it
passes the request on to the page server, which runs the report and returns
the results. The cache server then caches the report page for future use,
and sends the report to the viewer.
BusinessObjects Enterprise also performs active data sharing to reduce
database access request. Reports that are different, but which use the same
data, can be rendered from the same cache.
•Crystal Reports cache server, which handles requests for Crystal Reports.
•Desktop Intelligence cache server, which handles requests for Desktop
Intelligence reports.
Processing tier
The BusinessObjects Enterprise processing tier accesses the data tier and
generates reports for clients. It is the only tier that directly interacts with the
reporting database.
The processing tier includes the following server types.
Related Topics
•Job servers on page 67
•Report and Processing servers on page 69
•Crystal Reports page server on page 72
•Multi-Dimensional Analysis Server (MDAS) on page 72
•Dashboard and Analytics servers on page 73
Architecture
Processing tier
2
Job servers
A job server processes scheduled actions on objects at the request of the
Central Management Server (CMS). When you add a job server to the
BusinessObjects Enterprise system, you can configure the job server to:
•Process reporting or document objects.
•Process publication objects.
•Process program objects.
•Send objects or instances to specified destinations.
If you configure a job server to process Crystal Reports objects, it becomes
a Crystal Reports job server. If you configure a job server to process program
objects, it becomes a program job server, and so on. The Processing tier
includes:
The Crystal Reports job server processes scheduled reports, as requested
by the Central Management System (CMS), and generates report instances
(instances are versions of a report object that contain saved data). To
generate a report instance, the Crystal Reports job server obtains the report
object from the Input File Repository Server (FRS) and communicates with
the database to retrieve the current data. Once it has generated the report
instance, it stores the instance on the Output FRS.
Program job server
Program objects allow you to write, publish, and schedule custom
applications, including scripts, and Java programs that run against, and
perform maintenance on, BusinessObjects Enterprise.
The Program job server processes scheduled program objects, as requested
by the CMS. To run a program, the Program job server first retrieves the files
from storage on the Input File Repository Server (FRS), and then runs the
program. By definition, program objects are custom applications. Therefore,
the outcome of running a program is dependent on the program object that
is run.
Unlike report instances, which can be viewed in their completed format,
program instances exist as records in the object history. BusinessObjects
Enterprise stores the program’s standard out and standard error in a text
output file. This file appears when you click a program instance in the object
History.
Web Intelligence job server
The Web Intelligence job server processes scheduling requests it receives
from the Central Management System (CMS) for Web Intelligence documents.
It forwards these requests to the Web Intelligence Report Server, which will
generate the instance of the Web Intelligence document. The Web Intelligence
job server does not actually generate object instances.
The Desktop Intelligence job server processes scheduling requests it receives
from the CMS for Desktop Intelligence documents and generates the instance
of the Desktop Intelligence document.
Destination job server
If you configure a job server to send objects or instances, it becomes a
Destination job server. A Destination job server processes requests that it
receives from the CMS and sends the requested objects or instances to the
specified destination:
•If the request is for an object, it retrieves the object from the Input File
Repository Server.
•If the request is for a report or program instance, it retrieves the instance
from the Output File Repository Server.
The Destination job server can send objects and instances to destinations
inside the BusinessObjects Enterprise system, for example, a user’s inbox,
or outside the system. For example, by sending a file to an e-mail address.
2
The Destination job server does not run the actual report or program objects.
It only handles objects and instances that already exist in the Input or Output
File Repository Servers.
List of Values job server
The List of Values job server processes scheduled list-of-value objects.
These objects contain the values of specific fields in a Business View. Lists
of values implement dynamic prompts and cascading lists of values within
Crystal Reports. List-of-value objects do not appear in Central Management
Console (CMC) or InfoView. For more information, see the Business ViewsAdministrator’s Guide.
Adaptive job server
A generic server that hosts BusinessObjects Enterprise job services.
Report and Processing servers
The processing tier includes the following servers:
The Web Intelligence Report Server is used to create, edit, view, and analyze
Web Intelligence documents. It also processes scheduled Web Intelligence
documents and generates new instances of the document, which it stores
on the Output File Repository Server (FRS). Depending on the user’s access
rights and the refresh options of the document, the Web Intelligence Report
Server will use cached information, or it will refresh the data in the document
and then caches the new information.
Desktop Intelligence Report Server
The Desktop Intelligence Report service is the core engine that handles the
collection of data, formatting, and layout of a Desktop Intelligence document.
The server communicates with the Central Management Server (CMS) when
a document is requested, manages the connection to the Universe, and
retrieves the data.
Report Application Server (RAS)
The Report Application Server (RAS) provides ad-hoc reporting capabilities
that allow users to create and modify Crystal reports via the RAS Software
Development Kit (SDK). This SDK supports the Java viewer SDKs and does
not require a specific license; it is included with your BOE package.
Note:
The RAS is also used to resolve Dynamic Recipient Lists at runtime or during
the design phase when working with publications.
The Crystal Reports Processing Server retrieves data for the report from an
instance or directly from the database (depending on the user's request and
the rights he or she has to the report object). When retrieving data from the
database, the Crystal Reports Processing Server automatically disconnects
from the database after it fulfills its initial request and reconnects if necessary
to retrieve additional data. (This behavior conserves database licenses.)
The Crystal Reports Processing Server responds to page requests made by
the Cache Server. Requests always pass through the Cache Server and go
directly to the Processing Server.) The Processing Server and Cache Server
also interact to ensure cached EPF pages are reused as frequently as
possible, and new pages are generated when required.
Web Intelligence Processing Server
The Web Intelligence Processing Server is used to create, edit, view, and
analyze Web Intelligence documents. It interacts with the Enterprise
framework services like the CMS to list documents and universes, and
communicates with the Input File Repository Server (FRS) to open or save
Web Intelligence documents. It also processes scheduled Web Intelligence
documents for the Web Intelligence Job Server and generates new instances
of documents on the Output FRS. Depending on the user's access rights
and the refresh options of the document, the Web Intelligence Processing
Server will use cached information, or it will refresh the data in the document,
and then cache the new information.
2
The Crystal Report Designer also communicates with the Web Intelligence
Processing Server to create Crystal reports based on universes.
Desktop Intelligence Processing Server
The Desktop Intelligence Processing Server runs queries and generates
reports on behalf of the Desktop Intelligence client.
Adaptive Processing Server
An Adaptive Processing server is a generic server process that hosts
BusinessObjects Enterprise services. It provides a hosting environment,
enables the services to run and manages the life-cycle of the services
including starting and stopping. Furthermore, it can host services such as
the Publishing Service, and the Client Auditing Proxy Service; for a complete
set of available services, please see the Central Management Console
(CMC).
Crystal Reports page server
The Crystal Reports page server is responsible for responding to page
requests by processing reports and generating encapsulated page format
(EPF) pages. The key benefit of EPF is that it supports page-on-demand
access so only the requested page is returned, instead of the entire report.
This enhances performance and reduces unnecessary network traffic for
large reports.
The EPF pages contain formatting information that defines report layout.
The page server retrieves data for the report from an instance or directly
from the database (depending on the user request and the rights he or she
has to the report object). When retrieving data from the database, the page
server automatically disconnects from the database after it fulfills its initial
request and if necessary, reconnects to retrieve additional data. This helps
conserve database traffic and limit the unnecessary use of database licenses.
The Cache Server and Page Server work closely together. Specifically, the
Page Server responds to page requests made by the Cache Server. The
Page Server and Cache Server also interact to ensure cached EPF pages
are reused as frequently as possible, and new pages are generated as
required. BusinessObjects Enterprise takes advantage of this behavior by
ensuring that the majority of report-viewing requests are made to the Cache
Server and Page Server. However, if a user’s default viewer is the DHTML
viewer, the report is processed by the Report Application Server.
Multi-Dimensional Analysis Server (MDAS)
The Multi-Dimensional Analysis Server (MDAS) registers itself with the Central
Management Server (CMS), and its services are available for consumption
by other servers or client applications that communicate via the
BusinessObjects Enterprise framework.
The MDAS provides BusinessObjects Enterprise client applications with an
extensible and efficient framework for accessing multi-dimensional (OLAP)
data. It provides access to multi-dimensional data and also converts the raw
data into XML packages, which the requesting client application renders into
a specific presentation format: Excel spreadsheet, PDF, or Voyager crosstabs
and charts.
Note:
OLAP single sign-on (SSO) is only supported for Microsoft Analysis Services
and SAP BW.
Dashboard and Analytics servers
BusinessObjects Enterprise integrates specialized analytic engine services
to support dashboard, scorecard and analytic products. Each of these
services can be configured separately, depending on the license options you
purchase, and your specific implementation requirements. For more
information, consult the Dashboard and Analytics Setup and Administration
Guide.
PM Metrics Server
Dashboard and Analytics server to populate metrics created using the Metric
Engine.
Architecture
Processing tier
2
PM Repository Server
Dashboard and Analytics server to read and store performance information
from the Dashboard and Analytics repository.
PM Rules Server
Dashboard and Analytics server to create rules and alerts. Rules and alerts
automate the process of detecting and interpreting change, and delivering
relevant analysis. Rules enable you to proactively monitor your business and
take appropriate and timely action in response to specific events.
Dashboard Server
Server process used by the Dashboard Builder component to create and
manipute corporate and personal dashboards. Dashboard Builder offers
metric, alert, and dashboard management capabilities to help organizations
monitor and understand their business activities.
Server process used by the Dashboard Builder component to create and
manipute corporate and personal dashboard analytic content.
Predictive Analysis Server
Server process used for Predictive Analysis (Data Mining) using KXEN
engine, which quickly uncovers key business drivers from your data and
forecasts future business conditions. It helps users make proactive decisions
more easily by providing insight in familiar terms through dashboards across
the organization.
Process Analysis Server
The process analysis server monitors server activity. This helps your
organization to automate the tracking of quality variables by using alarm
rules and control chart types defined by your quality improvement initiatives.
The Data tier is made up of the data sources that contain the information
used in the reports and documents managed by your BusinessObjects
Enterprise XI system, which supports a wide range of corporate databases.
Please review the online BusinessObjects Enterprise supported platforms
document for information related to supported database release versions,
patch levels, or caveats at the Business Objects customer support site:
The Business Objects semantic layer is a platform-unspecific layer of
abstraction that lies between BusinessObjects Enterprise and the raw source
data contained with a reporting database.
Universes
The Universe abstracts the data complexity by using business language
rather than data language to access, manipulate, and organize data. This
business language is stored as objects in a universe file. Web Intelligence
and Crystal Reports use universes to simplify the user creation process
required for simple to complex end-user query and analysis.
Universes are a core component of BusinessObjects Enterprise. All universe
objects and connections are stored and secured in the central repository by
the Connection Server. Universe designers need to login to BusinessObjects
Enterprise to access the system and create universes. Universe access and
row-level security can also be managed at the group or individual user level
from within the design environment.
The semantic layer allows Web Intelligence to deliver documents, by utilizing
multiple synchronized data providers, including online analytical processing
(OLAP) and common warehousing metamodel (CWM) data sources.
Business Views
Business Views simplify report creation and interaction by abstracting the
complexity of data for report developers. Business Views help separate the
data connections, data access, business elements, and access control.
Business Views can only be used by Crystal Reports and are designed to
simplify the data access and view-time security required for Crystal report
creation. Business Views support the combination of multiple data sources
in a single view. Business Views are fully supported in BusinessObjects
Enterprise.
2
BusinessObjects Enterprise includes a series of dedicated, pre-configured
platform management services for tasks such as password management,
server metrics, and user access control for decentralized management
functions.
Connection Server
The Connection Server provides database access to the raw source data.
It supports relational databases (Oracle, MySQL, Microsoft SQL Server,
DB2, Sybase) as well as OLAP (SAP BW, Microsoft Analysis Services,
Hyperion Essbase). The Connection Server is responsible for handling
connection and interaction with the various datasources and providing a
common feature set to its clients, by emulating the missing features if
necessary.
The Connection Server can be accessed through a Dynamic Link Library
(inproc), a CORBA server (called through CORBA or HTTP), or by using the
Java API.
Security management
System security is managed by the Central Management Server (CMS),
security plug-ins, and third-party authentication tools, such as SiteMinder or
Kerberos. These components authenticate users and authorize user access
for BusinessObjects Enterprise, its folders, and other objects.
This section discusses key components of system security, including:
•CMS security.
•Third-party security plug-ins.
Note:
Because these components are responsible for additional tasks, several are
described in more detail in other sections.
Central Management Server (CMS) security
The Central Management Server (CMS) manages security information, such
as user accounts, group memberships, and object rights that define user
and group privileges.
When you set up your system, the CMS allows you to create user accounts
and groups within BusinessObjects Enterprise, or reuse existing user
accounts and groups that are stored in a third-party system, such as LDAP
or Windows Active Directory (AD). The CMS supports third-party
authentication, so users can log on to BusinessObjects Enterprise with their
current LDAP, or Windows AD credentials.
When users log on, the CMS coordinates the authentication process with
security plug-ins; the CMS then grants the user a logon token and an active
session on the system. The CMS also responds to authorization requests
made by the rest of the system. When a user requests a list of reports in a
particular folder, the CMS authorizes the request only after it verifies the
user's account or group membership has sufficient privileges.
Security plug-ins expand and customize how users are authenticated.
BusinessObjects Enterprise ships with the BusinessObjects Enterprise
security plug-in as a default, and with LDAP and Windows Active Directory
(AD) security plug-ins. Each security plug-in offers several key benefits.
Security plug-ins automate account creation and management by allowing
you to map user accounts and groups from third-party systems into
BusinessObjects Enterprise. You can map third-party user accounts or groups
to existing BusinessObjects Enterprise user accounts or groups, or you can
create new Enterprise user accounts or groups that corresponds to each
mapped entry in the external system.
The security plug-ins dynamically maintain third-party user and group listings.
This means once you map an LDAP or Windows AD group into
BusinessObjects Enterprise, all users in group can log on to BusinessObjects
Enterprise. When you make subsequent changes to the third-party group
membership, the list is automatically refreshed.
Architecture
Information flow
2
BusinessObjects Enterprise supports the following security plug-ins:
•BusinessObjects Enterprise security plug-in.
•LDAP security plug-in.
•Windows AD security plug-in.
Information flow
The following workflow information describes what happens at the Enterprise
Framework or Architecture level when an Enterprise process is invoked.
These workflows provide a high-level view of the architecture and how
report-processing is performed. This section covers two different scenarios:
Related Topics
•What happens when you view a report? on page 79
•What happens when you schedule an object? on page 78
When you schedule an object, you instruct BusinessObjects Enterprise to
process an object at a particular point in time, or on a recurring schedule.
For example, if you have a report that is based on your web server logs, you
can schedule the report to run every night on a recurring basis.
When a user schedules an object using InfoView, the following happens:
1. InfoView sends the request to the web server.
2. The web server passes the web request directly to the application server,
where it is evaluated by the BusinessObjects Enterprise SDK.
3. The SDK passes the request to the CMS.
4. The CMS checks to see if the user has sufficient rights to schedule the
object.
5. If the user has sufficient rights, the CMS schedules the object to be run
at the specified time(s).
6. When the time occurs, the CMS passes the job to the appropriate job
server. Depending on the type of object, the CMS will send the job to one
of the following job servers:
•If the object is Web Intelligence document, it sends the job to the Web
Intelligence Job Server, which sends the request to the Web
Intelligence Processing Server.
•If the object is a Crystal report, it sends the job to the Report Job
Server.
•If the object is program, it sends the job to the Program Job Server.
7. The job server retrieves the object from the Input File Repository Server
and runs the object against the database, thereby creating an instance
of the object.
8. The job server then saves the instance to the Output File Repository
Server, and tells the CMS that it has completed the job successfully.
If the job was for a Web Intelligence document, the Web Intelligence
Processing Server notifies the Web Intelligence Job Server. The Web
Intelligence Job Server then notifies the CMS that the job was completed
successfully.
•The Cache Server and the Page Server do not participate in scheduling
reports or in creating instances of scheduled reports. This can be an
important consideration when deciding how to configure BusinessObjects
Enterprise, especially in large installations. For more information, see the
•When you schedule program objects or object packages, the interaction
between servers follows the same pattern as it does for reports.
What happens when you view a report?
This section describes the viewing mechanisms that are implemented in
InfoView. It contains information on:
•Report viewing with the Crystal Reports Cache Server and Page Server.
•Viewing Web Intelligence documents.
When you view a report through BusinessObjects Enterprise, the processing
flow varies depending upon your default report viewer, the type of report,
and the rights you have to the report. In addition, the processing flow for
custom applications may differ. In all cases, however, the request that begins
at the web server must be forwarded to the application server.
Architecture
Information flow
2
The actual request is constructed as a URL that includes the report's unique
ID. This ID is passed as a parameter to a server-side script that, when
evaluated by the application server, verifies the user's session and retrieves
the logon token from the browser. The script then checks the user's InfoView
preferences and redirects the request to the viewing mechanism that
corresponds to the user's default viewer.
Different report viewers require different viewing mechanisms:
•The zero-client DHTML viewer is implemented through CAF and OpenDoc.
When evaluated by the application server, this script communicates with
the framework in order to create a viewer object and retrieve a report
source from the Cache Server and Page Server.
•The client-side report viewers (the ActiveX and Java viewers) are
The Crystal Web Request is executed internally through viewer code on
the application server. The viewer code communicates with the framework
in order to retrieve a report page (in .epf format) from the Cache Server
and Page Server.
If they haven't already done so, users are prompted to download and
install the appropriate viewer software.
Related Topics
•Report viewing with the Crystal Reports Cache Server and Page Server
on page 80
•Viewing Web Intelligence documents on page 81
Report viewing with the Crystal Reports Cache Server and Page
Server
This section describes the process for viewing a Crystal report when using
the zero-client DHTML, ActiveX, or Java viewer. This process uses the Crystal
Reports Cache Server and the Crystal Reports Page Server.
1. Upon receiving a report-viewing request, the Cache Server checks to see
if it has the requested pages cached. Cached pages are stored as
Encapsulated Page Format (.epf) files.
2. If a cached page for the report (.epf file) is available:
a. The Cache Server checks with the CMS to see if the user has rights
to view the cached page.
b. If the user is granted the right to view the report, the Crystal Reports
Cache Server sends the cached page (.epf file) to the application
server.
3. If a cached page for the report (.epf file) is unavailable:
a. The Cache Server requests new cached pages (.epf files) from the
Crystal Reports Page Server.
b. The Crystal Reports Page Server checks with the CMS to see if the
user has rights to view the report.
c. If the user is granted the right to view the report, the Crystal Reports
Page Server retrieves the report from the Input File Repository Server.
d. If the report is an instance, and the user only has View rights, the
Crystal Reports Page Server will generate pages of the report instance
using the data stored in the report instance. That is, the Crystal Reports
Page Server will not retrieve the latest data from the database.
If the report is an object, the user must have View On Demand rights
to view the report successfully (because the Crystal Reports Page
Server needs to retrieve data from the database).
e. If the user has sufficient rights, the Crystal Reports Page Server
generates the cached page (.epf files) and forwards them to the Crystal
Reports Cache Server.
f. The Crystal Reports Cache Server then caches the pages (.epf files).
g. The Crystal Reports Cache Server sends the pages (.epf files) to the
application server.
4. The application server sends the report to the user's Web browser in one
of two ways, depending on how the initial request was made:
•If the initial request was made through a DHTML viewer, the CAF, via
OpenDoc, generates HTML that represents both the DHTML viewer
and the report itself. The HTML pages are then returned through the
web server to the user's web browser.
•If the initial request was made through an Active X or Java viewer
(viewrpt.aspx), the application server forwards the cached pages
(.epf files) through the web server to the report viewer software in the
user's web browser.
2
Viewing Web Intelligence documents
This section describes the process for viewing a Web Intelligence document.
1. InfoView sends the request to the web application server.
2. The web application server sends the request to the application server,
which creates a new session with the Web Intelligence Report Server.
3. The Web Intelligence Report Server checks if the user has rights to use
the Web Intelligence application.
4. The web application server then sends the request to the Web Intelligence
Report Server.
5. The Web Intelligence Report Server contacts the CMS to check whether
the user has the right to view the document, and to check when the
document was last updated.
This section details the ways in which BusinessObjects Enterprise addresses
enterprise security concerns, thereby providing administrators and system
architects with answers to typical questions regarding security.
Click the appropriate link to jump to that section:
•
Security overview on page 84
•
Authentication and authorization on page 85
•
Security plug-ins on page 92
•
Active trust relationship on page 95
•
Sessions and session tracking on page 97
•
Environment protection on page 99
•
Auditing web activity on page 100
Security overview
The BusinessObjects Enterprise architecture addresses the many security
concerns that affect today's businesses and organizations. The current
release supports features such as distributed security, single sign-on,
resource access security, granular object rights, and third-party Windows
NT, LDAP, and Windows AD authentication in order to protect against
unauthorized access.
Because BusinessObjects Enterprise provides the framework for an
increasing number of components from the Enterprise family of Business
Objects products, this section details the security features and related
functionality to show how the framework itself enforces and maintains security.
As such, this section does not provide explicit procedural details; instead, it
focuses on conceptual information and provides links to key procedures.
Click the appropriate link to jump to that section:
•For key procedures that show how to modify the default accounts,
passwords, and other security settings, see BusinessObjects EnterpriseAdministrator's Guide.
•For procedures that show how to set up authentication for Enterprise
users, see BusinessObjects Enterprise Administrator's Guide. For the
basic information on how to set up third-party authentication to work with
BusinessObjects Enterprise, see the following sections:
•
Using NT Authentication on page 106
•
Using LDAP authentication on page 113
•
Using AD with NTLM on page 135
•For more in depth information on how to use Kerberos with AD
authentication, see Using AD and Kerberos with Java application servers
on page 141.
Authentication and authorization
Security Concepts
3
Authentication is the process of verifying the identity of a user who attempts
to access the system, and authorization is the process of verifying that the
user has been granted sufficient rights to perform the requested action upon
the specified object.
This section describes the authentication and authorization processes in
order to provide a general idea of how system security works within
BusinessObjects Enterprise. Each of the components and key terms is
discussed in greater detail later in this section. The detailed information on
how to implement these different methods of authentication is discussed in
the following section:
The current release supports these methods of authentication:
If you want to use any of the third-party methods of authentication or Trusted
Authentication, you will need to configure them before you use them. See
the following sections, for procedural details on how to implement these
authentication methods:
•
•
•
•
Because BusinessObjects Enterprise is fully customizable, the authentication
and authorization processes may vary from system to system. This section
uses InfoView as a model and describes its default behavior. If you are
developing your own BusinessObjects Enterprise end-user or administrative
applications using the BusinessObjects Enterprise Software Development
Kit (SDK), you can customize the system's behavior to meet your needs. For
complete details, see the developer documentation available on your product
CD.
Note:
Although a user can configure Windows NT authentication for BOE and
custom applications through the CMC, the CMC and InfoView themselves
do not support Windows NT authentication. The CMC and InfoView do not
support Windows AD authentication with NTLM.
Using NT Authentication on page 106
Using LDAP authentication on page 113
Using AD with NTLM on page 135
Using AD and Kerberos with Java application servers on page 141
The only methods of authentication that the CMC and InfoView support are
Windows AD with Kerberos, LDAP, Enterprise, and Trusted Authentication.
Primary authentication
Primary authentication occurs when a user first attempts to access the
system. One of two things can happen during primary authentication:
•If single sign-on is not configured, the user provides their credentials,
such as their user name, password and authentication type.
These details are entered by the users on the logon screen.
•If a method of single sign-on is configured, the credentials for the users
These details are extracted using other methods such as Kerberos,
SiteMinder.
•The authentication type may be Enterprise, Windows NT, LDAP, or
Windows AD authentication, depending upon which type(s) you have
enabled and set up in the Authentication management area of the Central
Management Console (CMC). The user's web browser sends the
information by HTTP to your web server, which routes the information to
the CMS or the appropriate BusinessObjects Enterprise server.
Note:
Although Windows NT and AD with NTLM authentication is supported for
BusinessObjects Enterprise applications, they are not supported for the
InfoView or CMC themselves.
The web application server passes the user's information a server-side script.
Internally, this script communicates with the SDK and, ultimately, the
appropriate security plug-in to authenticate the user against the user
database.
For instance, if the user is logging on to the InfoView and specifies Enterprise
Authentication, the SDK ensures that the BusinessObjects Enterprise security
plug-in performs the authentication. The Central Management Server (CMS)
uses the BusinessObjects Enterprise security plug-in to verify the user name
and password against the system database. Alternatively, if the user specifies
LDAP or Windows AD authentication, the SDK uses the corresponding
security plug-in to authenticate the user.
3
If the security plug-in reports a successful match of credentials, the CMS
grants the user an active identity on the system and the system performs
several actions:
•The CMS creates an enterprise session for the user. While the session
is active, this session consumes one user license on the system.
•The CMS generates and encodes a logon token and sends it to the web
application server.
•The web application server stores the user's information in memory in a
session variable. While active, this session stores information that allows
BusinessObjects Enterprise to respond to the user's requests.
Note:
The session variable does not contain the user's password.
•The web application server persists the logon token in a cookie on the
Each of these steps contributes to the distributed security of BusinessObjects
Enterprise, because each step consists of storing information that is used
for secondary identification and authorization purposes. This is the model
used in InfoView. However, if you are developing your own client application
and you prefer not to store session state on the web application server you
can design your application such that it avoids using session variables.
Note:
The third-party Windows NT, LDAP, and Windows AD security plug-ins work
only once you have mapped groups from the external user database to
BusinessObjects Enterprise. For procedural details, see the following
sections:
client's browser. This cookie is only used for failover purposes, such as
when you have a clustered CMS or when InfoView is clustered for session
affinity, not as a part of the normal operation of the system.
Note:
Although it is not the default behavior, it is possible to disable the logon
token, However, if you disable the logon token, you will disable failover.
•
Using AD with NTLM on page 135
•
Using LDAP authentication on page 113
•
Using NT Authentication on page 106
Note:
In a single sign-on situation, BusinessObjects Enterprise retrieves users'
credentials and group information directly from Windows AD or SiteMinder.
Hence, users are not prompted for their credentials.
Single sign-on support
The term single sign-on is used to describe different scenarios. At its most
basic level, it refers to a situation where a user can access two or more
applications or systems while providing their log-on credentials only once,
thus making it easier for users to interact with the system.
Single sign-on to the InfoView and the CMC can be provided by
BusinessObjects Enterprise, or by different authentication tools depending
on your application server type and operating system.
These methods of single sign-on are available if you are using a Java
application server on Windows:
•Windows AD with SiteMinder.
•Windows AD with Kerberos
These method of single sign-on support is available on Windows or Unix,
with either any supported web application server for the platform.
•LDAP with SiteMinder.
•Trusted Authentication.
•Windows AD with Kerberos
Note:
Windows AD with Kerberos is supported if the Java application is on UNIX.
However, the BusinessObjects Enterprise services need to run on a Windows
server.
The following table describes the methods of single sign-on support for the
InfoView and CMC that are available.
Single sign-on using Windows NT authentication is not supported for the
InfoView or the CMC.
Server
Windows
only
Any supported
platform
Any supported
platform
Windows AD with
Kerberos only.
Supported LDAP directory servers, with
SiteMinder only.
Trusted Authentication
NotesOptionsCMS
Windows AD authentication to the
InfoView and CMC is available
out of the box.
LDAP authentication to the InfoView and CMC is available out
of the box. SSO to the InfoView
and CMC requires SiteMinder.
Enterprise authentication to the
InfoView and CMC is available
out of the box. SSO with enterprise authentication to the InfoView and CMC requires Trusted
Authentication.
Within the context of BusinessObjects Enterprise, we distinguish the following
levels of single sign-on:
•
Single sign-on to BusinessObjects Enterprise on page 90
•
Single sign-on to database on page 91
•
End-to-end single sign-on on page 92
Single sign-on to BusinessObjects Enterprise
Single sign-on to BusinessObjects Enterprise means that once users have
logged on to the operating system (for Windows) or SiteMinder protected
resources (for LDAP), they can access BusinessObjects Enterprise
applications that support SSO without having to provide their credentials
again. When a user logs on, a security context for that user is created. This
context can be propagated to BOE in order to perform SSO - resulting in the
user being logged on as a BOE user that corresponds to the user.
The term “anonymous single sign-on” also refers to single sign-on to
BusinessObjects Enterprise, but it specifically refers to the single sign-on
functionality for the Guest user account. When the Guest user account is
enabled, which it is by default, anyone can log on to BusinessObjects
Enterprise as Guest and will have access to BusinessObjects Enterprise.
For more information, see the Managing Accounts and Groups chapter of
the BusinessObjects Enterprise Administrator's Guide.
For information on configuring single sign-on to BusinessObjects Enterprise
with LDAP authentication, see Configuring LDAP authentication on page 118
.
Single sign-on to database
Once users are logged on to BusinessObjects Enterprise, single sign-on to
the database enables them to perform actions that require database access,
in particular, viewing and refreshing reports, without having to provide their
logon credentials again. Single sign-on to the database can be combined
with single sign-on to BusinessObjects Enterprise, to provide users with even
easier access to the resources they need. See End-to-end single sign-on on
page 92.
Security Concepts
Authentication and authorization
3
In BusinessObjects Enterprise XI 3.0, single sign-on to the database is
supported through Windows AD using Kerberos. You may want to use single
sign-on to the database rather than end-to-end single sign-on, if you don't
want the account for IIS to be trusted for delegation.
Note:
This only relates to custom-built web applications. Single sign-on to the
InfoView and CMC are not supported with IIS. End-to-End single sign-on to
the InfoView and CMC is available for Java application servers.
See these sections for information on configuring single sign-on to the
database with BusinessObjects Enterprise:
•
Using AD and Kerberos with Java application servers on page 141
•
Configuring Kerberos and single sign-on to the database for Java
application servers on page 162
Configuring Kerberos and single sign-on for Java InfoView on page 163.
End-to-end single sign-on
End-to-end single sign-on refers to a configuration where users have both
single sign-on access to BusinessObjects Enterprise at the front-end, and
single sign-on access to the databases at the back-end. Thus, users need
to provide their logon credentials only once, when they log on to the operating
system, to have access to BusinessObjects Enterprise and to be able to
perform actions that require database access, such as viewing reports.
In BusinessObjects Enterprise XI end-to-end single sign-on is supported
through Windows AD and Kerberos. For more information, see Configuring
Kerberos for Java application servers on page 142.
Security plug-ins
Security plug-ins expand and customize the ways in which BusinessObjects
Enterprise authenticates users. BusinessObjects Enterprise currently ships
with the system default BusinessObjects Enterprise security plug-in and with
the Windows NT, LDAP, and Windows AD security plug-ins. Each security
plug-in offers several key benefits.
Security plug-ins facilitate account creation and management by allowing
you to map user accounts and groups from third-party systems into
BusinessObjects Enterprise. You can map third-party user accounts or groups
to existing BusinessObjects Enterprise user accounts or groups, or you can
create new Enterprise user accounts or groups that corresponds to each
mapped entry in the external system.
The security plug-ins dynamically maintain third-party user and group listings.
So, once you map a Windows NT, LDAP, or Windows AD group into
BusinessObjects Enterprise, all users who belong to that group can log on
to BusinessObjects Enterprise. When you make subsequent changes to the
third-party group membership, you need not update or refresh the listing in
BusinessObjects Enterprise. For instance, if you map a Windows NT group
to BusinessObjects Enterprise, and then you add a new NT user to the NT
group, the security plug-in dynamically creates an alias for that new user
when he or she first logs on to BusinessObjects Enterprise with valid NT
credentials.
Moreover, security plug-ins enable you to assign rights to users and groups
in a consistent manner, because the mapped users and groups are treated
as if they were Enterprise accounts. For example, you might map some user
accounts or groups from Windows NT, and some from an LDAP directory
server. Then, when you need to assign rights or create new, custom groups
within BusinessObjects Enterprise, you make all of your settings in the CMC.
Each security plug-in acts as an authentication provider that verifies user
credentials against the appropriate user database. When users log on to
BusinessObjects Enterprise, they choose from the available authentication
types that you have enabled and set up in the Authorization management
area of the CMC: Enterprise (the system default), Windows NT, LDAP, or
Windows AD.
Note:
The Windows NT and Windows AD security plug-ins cannot authenticate
users if the BusinessObjects Enterprise server components are running on
UNIX.
BusinessObjects Enterprise supports the following security plug-ins:
•
BusinessObjects Enterprise security plug-in on page 93
3
•
LDAP security plug-in on page 114
•
Windows AD security plug-in on page 136
BusinessObjects Enterprise security plug-in
The BusinessObjects Enterprise security plug-in (secEnterprise.dll) is
installed and enabled by default when you install BusinessObjects Enterprise.
This plug-in allows you to create and maintain user accounts and groups
within BusinessObjects Enterprise; it also enables the system to verify all
logon requests that specify Enterprise Authentication. In this case, user
names and passwords are authenticated against the BusinessObjects
Enterprise user list, and users are allowed or disallowed access to the system
based solely on that information. For details on setting up Enterprise users
and groups, see the BusinessObjects Enterprise Administrator's Guide.
When you first install BusinessObjects Enterprise, this plug-in sets up two
default Enterprise accounts: Administrator and Guest. Neither account has
a default password.
Single sign-on
The BusinessObjects Enterprise authentication provider supports anonymous
single sign-on for the Guest account. Thus, when users connect to
BusinessObjects Enterprise without specifying a user name and password,
the system logs them on automatically under the Guest account. If you assign
a secure password to the Guest account, or if you disable the Guest account
entirely, you disable this default behavior. For details, see the
BusinessObjects Enterprise Administrator's Guide.
Processing extensions
BusinessObjects Enterprise offers you the ability to further secure your
reporting environment through the use of customized processing extensions.
A processing extension is a dynamically loaded library of code that applies
business logic to particular BusinessObjects Enterprise view or schedule
requests before they are processed by the system.
Note:
On Windows systems, dynamically loaded libraries are referred to as
dynamic-link libraries (.dll file extension). On UNIX systems, dynamically
loaded libraries are often referred to as shared libraries (.so file extension).
You must include the file extension when you name your processing
extensions.
Through its support for processing extensions, the BusinessObjects
Enterprise administration SDK essentially exposes a "handle" that allows
developers to intercept the request. Developers can then append selection
formulas to the request before the report is processed.
A typical example is a report-processing extension that enforces row-level
security. This type of security restricts data access by row within one or more
database tables. The developer writes a dynamically loaded library that
intercepts view or schedule requests for a report (before the requests are
processed by a Job Server, Processing Server, or Report Application Server).
The developer's code first determines the user who owns the processing
job; then it looks up the user's data-access privileges in a third-party system.
The code then generates and appends a record selection formula to the
report in order to limit the data returned from the database. In this case, the
processing extension serves as a way to incorporate customized row-level
security into the BusinessObjects Enterprise environment.
Tip:
In BusinessObjects Enterprise XI, you can also set and enforce row-level
security through the use of Business Views. For more information, see the
Business Views Administrator's Guide.
The CMC provides methods for registering your processing extensions with
BusinessObjects Enterprise and for applying processing extensions to
particular object. For details, see the BusinessObjects EnterpriseAdministrators' Guide.
By enabling processing extensions, you configure the appropriate
BusinessObjects Enterprise server components to dynamically load your
processing extensions at runtime. Included in the SDK is a fully documented
API that developers can use to write processing extensions. For more
information, see the developer documentation available on your product CD.
3
Note:
In the current release, processing extensions can be applied only to Crystal
report (.rpt) objects.
Active trust relationship
In a networked environment, a trust relationship between two domains is
generally a connection that allows one domain accurately to recognize users
who have been authenticated by the other domain. While maintaining security,
the trust relationship allows users to access resources in multiple domains
without repeatedly having to provide their credentials.
Within the BusinessObjects Enterprise environment, the active trust
relationship works similarly to provide each user with seamless access to
resources across the system. Once the user has been authenticated and
granted an active session, all other BusinessObjects Enterprise components
can process the user's requests and actions without prompting for credentials.
As such, the active trust relationship provides the basis for BusinessObjects
Enterprise's distributed security.
A logon token is an encoded string that defines its own usage attributes and
contains a user's session information. The logon token's usage attributes
are specified when the logon token is generated. These attributes allow
restrictions to be placed upon the logon token to reduce the chance of the
logon token being used by malicious users. The current logon token usage
attributes are:
•Number of minutes
This attribute restricts the lifetime of the logon token.
•Number of logons
This attribute restricts the number of times that the logon token can be
used to log on to BusinessObjects Enterprise.
Both attributes hinder malicious users from gaining unauthorized access to
BusinessObjects Enterprise with logon tokens retrieved from legitimate users.
Note:
Storing a logon token in a cookie is a potential security risk if the network
between the browser and application or web server is insecure – for example
if the connection is made over a public network and is not using SSL or
Trusted Authentication. It is good practice to use Secure Sockets Layer (SSL)
to reduce security risk between the browser and application or web server.
When the logon cookie has been disabled, and the web server or web
browser times out, the user is presented with the logon screen. When the
cookie is enabled, and the server or browser times out, the user is seamlessly
logged back onto the system. However, because state information is tied to
the web session, the user's state is lost. For example, if the user had a
navigation tree expanded and a particular item selected, the tree is reset.
For BusinessObjects Enterprise, the default is to have logon tokens enabled
in the web client, however, you can disable logon tokens for InfoView. When
you disable the logon tokens in the client, the user session will be limited by
the web server or web browser timeout. When that session expires, the user
will be required to log in again to BusinessObjects Enterprise.
Enterprise systems dedicated to serving a large number of users typically
require some form of distributed security. An enterprise system may require
distributed security to support features such the transfer of trust (the ability
to allow another component to act on behalf of the user)
BusinessObjects Enterprise addresses distributed security by implementing
a ticket mechanism (one that is similar to the Kerberos ticket mechanism).
The CMS grants tickets that authorize components to perform actions on
behalf of a particular user. In BusinessObjects Enterprise, the ticket is referred
to as the logon token.
This logon token is most commonly used over the Web. When a user is first
authenticated by BusinessObjects Enterprise, he or she receives a logon
token from the CMS. The user's web browser caches this logon token. When
the user makes a new request, other BusinessObjects Enterprise components
can read the logon token from the user's web browser.
Security Concepts
3
Sessions and session tracking
In general, a session is a client-server connection that enables the exchange
of information between the two computers. A session's state is a set of data
that describes the session's attributes, its configuration, or its content. When
you establish a client-server connection over the Web, the nature of HTTP
limits the duration of each session to a single page of information; thus, your
web browser retains the state of each session in memory only for as long
as any single Web page is displayed. As soon as you move from one web
page to another, the state of the first session is discarded and replaced with
the state of the next session. Consequently, Web sites and Web applications
must somehow store the state of one session if they need to reuse its
information in another.
BusinessObjects Enterprise uses two common methods to store session
state:
•Cookies—A cookie is a small text file that stores session state on the
client side: the user's web browser caches the cookie for later use. The
BusinessObjects Enterprise logon token is an example of this method.
•Session variables—A session variable is a portion of memory that stores
Note:
Ideally, the system should preserve the session variable while the user is
active on the system. And, to ensure security and to minimize resource
usage, the system should destroy the session variable as soon as the user
has finished working on the system. However, because the interaction
between a web browser and a web server can be stateless, it can be difficult
to know when users leave the system, if they do not log off explicitly. To
address this issue, BusinessObjects Enterprise implements session tracking.
Click the appropriate link to jump to that section:
•
session state on the server side. When BusinessObjects Enterprise grants
a user an active identity on the system, information such as the user's
authentication type is stored in a session variable. So long as the session
is maintained, the system neither has to prompt the user for the information
a second time nor has to repeat any task that is necessary for the
completion of the next request.
For Java deployments, the session is used to handle .jsp requests; for
.NET deployments, the session is used to handle .aspx requests.
Session tracking on page 98
•
CMS session tracking on page 98
Session tracking
The web application server's idle connection timeout is set to a default of 20
minutes but can changed via the CMC in the properties for all processing
servers. For more information about changing idle connection timeout
settings, see Configuring the processing tier for enhanced performance on
page 422.
CMS session tracking
The CMS implements a simple tracking algorithm. When a user logs on, he
or she is granted a CMS session, which the CMS preserves until the user
logs off, or until the web application server session variable is released.
The web application server session is designed to notify the CMS on a
recurring basis that it is still active, so the CMS session is retained so long
as the web application server session exists. If the web application server
session fails to communicate with the CMS for a ten-minute time period, the
CMS destroys the CMS session. This handles scenarios where client-side
components shut down irregularly.
Environment protection
Environment protection refers to the security of the overall environment in
which client and server components communicate. Although the Internet and
web-based systems are increasingly popular due to their flexibility and range
of functionality, they operate in an environment that can be difficult to secure.
When you deploy BusinessObjects Enterprise, environment protection is
divided into two areas of communication:
•
Web browser to web server on page 99
•
Web server to BusinessObjects Enterprise on page 100
Security Concepts
Environment protection
3
Web browser to web server
When data is transmitted between the web browser and the web server,
some degree of security is usually required. Relevant security measures
usually involve two general tasks:
•Ensuring that the communication of data is secure.
•Ensuring that only valid users retrieve information from the web server.
Note:
These tasks are typically handled by web servers through various security
mechanisms, including the Secure Sockets Layer (SSL) protocol, Windows
NT Challenge/Response authentication, and other such mechanisms. It is
good practice to use Secure Sockets Layer (SSL) to reduce security risk
between the browser and application or web server. For procedural
information, see Configuring servers for SSL on page 271.
You must secure communication between the web browser and the web
server independently of BusinessObjects Enterprise. For details on securing
client connections, refer to your web server documentation.
Firewalls are commonly used to secure the area of communication between
the web server and the rest of the corporate intranet (including
BusinessObjects Enterprise). BusinessObjects Enterprise supports firewalls
that use IP filtering or static network address translation (NAT). Supported
environments can involve multiple firewalls, web servers, or application
servers.
For complete details on BusinessObjects Enterprise and firewall interaction,
see Understanding communication between BusinessObjects Enterprise
components on page 358.
Auditing web activity
BusinessObjects Enterprise provides insight into your system by recording
web activity and allowing you to inspect and to monitor the details. The web
application server allows you to select the web attributes—such as time,
date, IP address, port number, and so on—that you want to record. The
auditing data is logged to disk and stored in comma-delimited text files, so
you can easily report off the data or import it into other applications.
Protection against malicious logon attempts
No matter how secure a system is, there is often at least one location that
is vulnerable to attack: the location where users connect to the system. It is
nearly impossible to protect this location completely, because the process
of simply guessing a valid user name and password remains a viable way
to attempt to "crack" the system.
BusinessObjects Enterprise implements several techniques to reduce the
probability of a malicious user achieving access to the system. The various
restrictions listed below apply only to Enterprise accounts—that is, the
restrictions do not apply to accounts that you have mapped to an external
user database (Windows NT, LDAP, or Windows AD). Generally, however,
your external system will enable you to place similar restrictions on the
external accounts.