BusinessObjects Enterprise XI 3.

0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0

Copyright

© 2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and the Business Objects logo, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight, the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. Business Objects is an SAP company. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners. 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-06-02

Third-party Contributors

Contents
Chapter 1 Getting Started 7 About this guide...........................................................................................8 What's new .................................................................................................8 Overview of BusinessObjects Enterprise XI 3.0........................................10 Deploying for the first time.........................................................................11 Changing your deployment's architecture.................................................12 BusinessObjects Enterprise guides...........................................................13 Chapter 2 BusinessObjects Enterprise XI 3.0 Architecture 15

Architectural overview................................................................................16 Architecture basics...............................................................................16 Client tier components...............................................................................18 Browser-based web applications ........................................................19 Installed desktop client applications ....................................................23 Application tier components.......................................................................29 Web application servers.......................................................................30 Java software development kit (SDK) support.....................................30 .NET software development kit (SDK) support....................................33 BusinessObjects Web Services...........................................................34 Query as a Web Service......................................................................35 Packaged applications.........................................................................36 Intelligence tier...........................................................................................38 Server classifications............................................................................38 Central Management Server (CMS).....................................................42 Event Server.........................................................................................44 File Repository Servers........................................................................44

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

3

Contents

Cache servers......................................................................................45 Processing tier...........................................................................................45 Job servers...........................................................................................46 Report and Processing servers ...........................................................48 Crystal Reports page server ................................................................50 Multi-Dimensional Analysis Server (MDAS) ........................................51 Dashboard and Analytics servers .......................................................51 Data tier ....................................................................................................53 Semantic layers ...................................................................................53 Connection Server ...............................................................................54 Security management................................................................................54 Central Management Server (CMS) security.......................................55 Security plug-ins...................................................................................55 Information flow ........................................................................................56 What happens when you schedule an object?.....................................56 What happens when you view a report?..............................................57 Chapter 3 Planning Your Deployment 63

Planning your BusinessObjects Enterprise deployment............................64 Assessing your organization's environment..............................................64 Operating systems...............................................................................65 Databases in BusinessObjects Enterprise...........................................67 Web application servers.......................................................................70 Web servers.........................................................................................72 Failover and load balancing.................................................................73 Multi-homed environment.....................................................................73 Security................................................................................................74 Performance and scalability.................................................................78 Designing for high availability...............................................................79 Deployment scenarios...............................................................................81 Desktop client to server overview.........................................................82

4

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Contents

N-tier scenario overview.......................................................................83 Complex deployment overview............................................................84 Chapter 4 Deployment Checklists 87

Deployment Checklist................................................................................88 Installation order........................................................................................89 Chapter 5 Glossary 93

Appendix A

Get More Help

105

Index

109

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

5

Contents

6

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Getting Started

1

1

Getting Started About this guide

About this guide
This guide will help you plan a successful deployment of BusinessObjects Enterprise XI 3.0. Whether you are a new or experienced user, this guide provides all the information you need to: • • • • Understand BusinessObjects Enterprise architecture. Choose an appropriate configuration. Plan a secure and fail-safe environment. Learn the new features available for BusinessObjects Enterprise.

For information about installation types and post installation considerations; including how to use wdeploy to deploy Business Objects WAR files, see the BusinessObjects Enterprise Installation and Configuration Guide. For server configuration and user management tasks, see the BusinessObjects Enterprise Administrator's Guide. For specific information related to wdeploy, see the Deploying BusinessObjects Enterprise Web Applications Using wdeploy Guide. All product documentation (including error message explanations) is available in all supported languages in an HTML-based documentation library. This system enables full-text search and other customizable features to make it easy to find the information you need. You can also access or download the PDF guides from the same website. The website is refreshed with up-to-date content as it becomes available between releases. Go to http://support.busi nessobjects.com/documentation/

What's new
BusinessObjects XI 3.0 is the first release where: • New languages can be added to your installation using the stand-alone language pack installer. For more information and to get started, see Language Packs on Windows in the BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide. • InfoView can be deployed with fail-over support for web application clusters.

8

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Getting Started What's new

1

New stand-alone client tools installer for Microsoft Windows. You can now specify which client tools and components to install using a dedicated installation program. For more information and to get started, see Stand-Alone Client Tools Installation in the BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide.

Web applications can now be deployed to supported web application servers using the BusinessObjects Enterprise installer. Previous releases deployed only to Tomcat. For more information and to get started, see Web Applications Installation in the BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide.

BusinessObjects Enterprise can now be installed on systems running either BusinessObjects Enterprise XI Release 1 or BusinessObjects Enterprise XI Release 2 using a side-by-side installation scenario. For more information and to get started, see Preparing to Install BusinessObjects Enterprise in the BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide.

Scripted installations are supported. You can now log all your installation settings in a file used to run silent or scripted installations. This feature is useful for automating custom installations. For more information and to get started, see Silent Installation of BusinessObjects Enterprise in the BusinessObjects Enterprise XI 3.0 Installation and Configuration Guide.

All product documentation (including error message explanations) is available in all supported languages in an HTML-based documentation library. This system enables full-text search and other customizable features to make it easy to find the information you need. You can also access or download the PDF guides from the same website. The website is refreshed with up-to-date content as it becomes available between releases. Go to http://support.businessobjects.com/documentation/

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

9

1

Getting Started Overview of BusinessObjects Enterprise XI 3.0

Overview of BusinessObjects Enterprise XI 3.0
BusinessObjects Enterprise XI 3.0 is the business intelligence platform that supports a range of performance management (Dashboard and Analytics), reporting, querying, and analysis applications. It also provides an industry-standard, proven architecture and platform-support for semantic layers, data integration, and security. BusinessObjects Enterprise provides for web-based administration and configuration of the entire system. BusinessObjects Enterprise features: • Extend the robust information infrastructure provided by earlier releases and integrate seamlessly with existing product lines. • Support all deployment models and let you fine-tune administration and configuration of the entire system. • Bring together features from across the Business Objects product line to meet your evolving reporting needs, from using Web Intelligence anywhere to improving Crystal Reports interactivity and personalization. • Facilitate upgrading from older products to BusinessObjects Enterprise XI 3.0. • Support side-by-side deployments, enabling existing customers to leverage their investments in Business Objects and Crystal technologies. • Deliver innovation to drive user productivity and self-service reporting. • Deliver more reporting with fewer reports. • Include a variety of major enhancements spread across data access methods, administration capabilities, and report design options. • Simplify business monitoring with dashboard functionality and improved user experience. • Deliver the strongest self-service query and analysis solution for SAP customers.
About this guide

This guide provides you with information for planning your BusinessObjects Enterprise deployment. It explains the key concepts and choices you need to make before you begin your deployment. You should read this to gain an understanding of how you can install BusinessObjects Enterprise to suit your organization.

10

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Getting Started Deploying for the first time

1

For information about installing BusinessObjects Enterprise, see the BusinessObjects Enterprise Installation and Configuration Guide. For initial server configuration and user management tasks, see the BusinessObjects Enterprise Administrator's Guide. For specific information related to wdeploy, see the Deploying BusinessObjects Enterprise Web Applications Using wdeploy Guide.
Who should use this guide?

It is recommend to consult this guide if you are: • New to BusinessObjects Enterprise XI 3.0. • Planning your first deployment. • Making significant changes to the architecture of an existing deployment. This guide is intended as pre-reading material for administrators 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 guide provides sufficient background and conceptual information to clarify administrative tasks and features.

Deploying for the first time
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: • Familiarize yourself with the BusinessObjects Enterprise system architecture by reading Architecture basics on page 16. • Assess your needs and design a deployment architecture that works best for you with Assessing your organization's environment on page 64. • To learn specific requirements and caveats related to the architecture type you have selected for your deployment, review sections of the BusinessObjects Enterprise Administrator's Guide and the BusinessObjects Enterprise Installation and Configuration Guide prior to installation. These topics include: • Deployment configuration: providing detailed configuration settings for each of the supported web application servers with simple,

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

11

1

Getting Started Changing your deployment's architecture

distributed (clustered), and complex deployment scenarios. See the BusinessObjects Enterprise Installation and Configuration Guide for more details. • Authentication and security: enabling Single Sign On (SSO), security plug-ins, active trust relationships, session tracking, environment protection, auditing, trusted authentication, third-party authentication (Active Directory or SiteMinder, using NTLM, Kerberos, or LDAP), and working with firewalls. See the BusinessObjects Enterprise Administrator's Guide for more details. Improving performance: assessing your needs and evaluating system performance, as well as how to scale or plan for scaling your system. See theBusinessObjects Enterprise Administrator's Guide for more details.

Once you have formulated your deployment plan, proceed with your installation using the BusinessObjects Enterprise Installation and Configuration Guide. After you install, read the Managing and configuring servers chapter of the BusinessObjects Enterprise Administrator's Guide for information about configuring your BusinessObjects Enterprise server processes from within the Central Management Console (CMC). The guide also includes advanced topics such as configuring clustered environments, multi-homed machines, and secure socket layer (SSL) configuration.

Changing your deployment's architecture
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 documentation: • In the BusinessObjects Enterprise Administrator's Guide, read the Improving Performance chapter for information about assessing and improving the performance of an existing deployment. • After determining which areas need improvement, read Assessing your organization's environment on page 64 to see other if a different deployment configuration would improve performance in your area of interest.

12

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Getting Started BusinessObjects Enterprise guides

1

If you need to configure server components, see the Managing and configuring servers chapter of the BusinessObjects Enterprise Administrator's Guide. For information about installing server components or deploying to a new web application server platform, see the Manually deploying the web tier section of the BusinessObjects Enterprise Installation and Configuration Guide.

BusinessObjects Enterprise guides
The following table provides a list of BusinessObjects Enterprise guides and their contents. Guide BusinessObjects Enterprise Deployment Planning Guide Description 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.

BusinessObjects Enterprise In- Leads you through the steps required to stallation and Configuration run the setup program and complete your Guide installation of BusinessObjects Enterprise. There are UNIX and Windows versions of this guide available.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

13

1

Getting Started BusinessObjects Enterprise guides

Guide BusinessObjects Enterprise Administrator's Guide

Description 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.

BusinessObjects Enterprise Publisher's Guide

BusinessObjects Enterprise Mi- Details content migration from legacy gration Guide Business Objects software, such as Classic or Enterprise 5 or 6, to BusinessObjects Enterprise XI 3.0. BusinessObjects Enterprise Upgrade Guide Information for upgrades from BusinessObjects Enterprise XI to BusinessObjects Enterprise XI 3.0.

BusinessObjects Enterprise In- Provides an overview of InfoView and foView User's Guide working with Crystal Reports, Web Intelligence, objects, discussions, encyclopedia, and Voyager workspaces.

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

14

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture

2

2

BusinessObjects Enterprise XI 3.0 Architecture Architectural overview

Architectural overview
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. • Intelligence: system server processes. • Processing: data analysis and report generation. • Data: source repositories.

16

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Architectural overview

2

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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

17

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

• •

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).

Client tier components
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.

18

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

2

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.
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
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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

19

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

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

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.

20

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

2

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. 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

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).

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

21

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

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.

22

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

2

For more information on the specific functionality or platform support provided by each report viewer, see the BusinessObjects Enterprise InfoView User's Guide or the Crystal Reports Developer's Guide, available at the customer support portal: http://support.businessobjects.com/documentation/prod uct_guides/default.asp.

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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

23

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

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

24

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

2

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. 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.
Live Office

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

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

25

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

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.

26

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

2

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.
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: • Fully Converted. • Partly Converted. • Not Converted. 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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

27

2

BusinessObjects Enterprise XI 3.0 Architecture Client tier components

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

28

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

2

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.
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 following third-party J2EE web application servers can be used with BusinessObjects Enterprise. • WebSphere 6.1. • WebSphere Community Edition 2.0. • WebLogic 10. • WebLogic 9.2. • Tomcat 5.5 (bundled with BusinessObjects Enterprise). • SAP Application Server 7.0. • Oracle 10G R3. • JBoss 4.04.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

29

2

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

Note: For specific version compatibility, refer to the BusinessObjects

Enterprise supported platform document guide online on our support web site: http://support.businessobjects.com/documentation/supported_platforms. 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). • SAP Application Server 7.0. • Oracle 10G R3. • JBoss 4.04.
Note: For specific version compatibility, refer to the BusinessObjects

Enterprise supported platform document guide online on our support web site: http://support.businessobjects.com/documentation/supported_platforms.

Java software development kit (SDK) support
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.

30

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

2

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.
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. 2. Working with repository objects. 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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

31

2

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

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: 1. DHTML report page viewer. 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 34.

32

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

2

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. 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.

.NET software development kit (SDK) support
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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

33

2

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

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.

BusinessObjects Web Services
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

34

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

2

Exposes advanced platform features such as scheduling, search, user and group administration, server administration, platform events, and calendars. • 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 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 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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

35

2

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

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. • Microsoft Office, Excel, and InfoPath. • SAP Application Server. • OpenOffice. • 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

36

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Application tier components

2

• • •

Set Analysis Predictive Analysis Process Analysis

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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

37

2

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

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 Installation guide.

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. This tier contains the following components: • Central Management Server (CMS). • Event Server. • File Repository Servers (FRS). • Cache Server instances.

Server classifications
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 and Configuring 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.

38

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

2

Server kind Description

Server instance(s) managed by CMC

Central Man- Primary server process that provides ser- CentralManage agement vices for all other servers in the Business mentServer Server Intelligence (BI) platform, including management of: • • • • security objects servers auditing
EventServer

Event Server Responsible for monitoring file based events, and notifying the CMS of these events.

File Reposito- Responsible for the creation of file system InputFileReposi ry Servers objects, such as exported reports, and im- tory, OutputFil ported files in non-native formats. eRepository Adaptive Processing Servers Generic server that hosts multiple services AdaptiveProcess responsible for processing requests from ingServer various sources. It can host services like the Publishing Service and the Client Auditing Proxy Service.

Processing servers

Processing servers are the back-end components that handle requests from Web Intelligence, Desktop Intelligence, Crystal Reports, and Voyager.
Server kind Description Server instance(s) managed by CMC

Connection Serv- Responsible for handling ConnectionServer er connection and interaction with the various datasources and providing a common feature set to its clients, by emulating the missing features if necessary.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

39

2

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

Server kind Crystal Reports Cache Server

Description Caches recently executed Crystal reports to reduce database requests.

Server instance(s) managed by CMC
CrystalReportsCacheServ er CrystalReportsProcess ingServer

Crystal Reports Runs Crystal report queries Processing Serv- and returns data to Crystal er Reports Cache Server. Desktop Intelligence Cache Server Desktop Intelligence Processing Server Job Servers

Caches recently executed DesktopIntelligence Desktop Intelligence reports CacheServer to reduce database requests. Runs Crystal report queries and returns data to Crystal Reports Cache Server. 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: • • • • Process report and document objects Process program objects Process publication objects Send objects or instances to specified destinations.
DesktopIntelligencePro cessingServer AdaptiveJobServer, Crys talReportsJobServer, DesktopIntelligenceJob Server, DestinationJob Server, ListOfValuesJob Server, ProgramJobServer, PublicationJobServer

Report Application Server

Responsible for responding ReportApplicationServer to page requests by processing reports and generating Encapsulated Page Format (EPF) pages.
WebIntelligenceProcess ingServer

Web Intelligence Runs Web Intelligence Processing Serv- queries and returns data to er the user.

40

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

2

Server kind

Description

Server instance(s) managed by CMC
MultiDimensionalAnaly sisServicesServer

Multi Dimension- OLAP framework server. al Analysis Services (MDAS) Server

Performance Management servers

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.
Server kind Description Server instance(s) managed by CMC
PMMetricsServ er

PM Metrics Server

Creates and populates metrics for the Metric Engine.

PM Repository Manages repository-specific performance PMRepository Server information. Server PM Rules Server Sets Profile Server Sets Query Server Creates and monitors Performance Management rules and alerts.
PMRulesServer

Manages Performance Management profile SetsPro information. cessServer Runs Performance Management set queries.
SetsQueryServ er

Predictive KXEN data mining engine and forecaster. PredictiveAnal Analysis ServysisServer er Process Analy- Automate tracking of of variables through ProcessAnaly sis Server BusinessObjects Enterprise. sisServer Dashboard Server Used by the Dashboard Builder to create and manipute dashboards.
DashboardServ er

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

41

2

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

Server kind

Description

Server instance(s) managed by CMC
DashboardAna lyticsServer

Dashboard An- Used by the Dashboard Builder to create alytics Server 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. 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

42

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

2

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.
Caution: 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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

43

2

BusinessObjects Enterprise XI 3.0 Architecture Intelligence tier

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.
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).
Note: 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

44

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

2

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. Two different types of cache servers are: • 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 46 Report and Processing servers on page 48 Crystal Reports page server on page 50

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

45

2

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

• •

Multi-Dimensional Analysis Server (MDAS) on page 51 Dashboard and Analytics servers on page 51

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: • Crystal Reports job server. • Program job server. • Web Intelligence job server. • Desktop Intelligence job server. • Destination job server. • List of Values job server. • Adaptive job server.
Crystal Reports job server

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.

46

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

2

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.
Desktop Intelligence job server

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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

47

2

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

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. 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 Views Administrator’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: • Web Intelligence Report Server. • Desktop Intelligence Report Server. • Report Application Server (RAS). • Crystal Reports Processing Server. • Web Intelligence Processing Server. • Desktop Intelligence Processing Server. • Adaptive Processing Server. • Dashboard Server. • Dashboard Analytics Server. • Predictive Analysis Server. • Process Analysis Server.
Web Intelligence Report Server

The Web Intelligence Report Server is used to create, edit, view, and analyze Web Intelligence documents. It also processes scheduled Web Intelligence

48

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

2

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.
Crystal Reports Processing Server

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

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

49

2

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

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. 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

50

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

2

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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

51

2

BusinessObjects Enterprise XI 3.0 Architecture Processing tier

PM Metrics Server

Dashboard and Analytics server to populate metrics created using the Metric Engine.
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.
Dashboard Analytics Server

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.

52

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Data tier

2

Data tier
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: http://support.businessobjects.com/documentation/supported_platforms.

Semantic layers
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.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

53

2

BusinessObjects Enterprise XI 3.0 Architecture Security management

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. 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: • •
54

CMS security. Third-party security plug-ins.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Security management

2

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
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

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

55

2

BusinessObjects Enterprise XI 3.0 Architecture Information flow

Enterprise. When you make subsequent changes to the third-party group membership, the list is automatically refreshed. 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 57 What happens when you schedule an object? on page 56

What happens when you schedule an object?
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).

56

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Information flow

2

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.
Note:

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 BusinessObjects Enterprise Deployment Planning Guide. 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,

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

57

2

BusinessObjects Enterprise XI 3.0 Architecture Information flow

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. 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 implemented through viewrpt.aspx. 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 58 • Viewing Web Intelligence documents on page 60

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.

58

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Information flow

2

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

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

59

2

BusinessObjects Enterprise XI 3.0 Architecture Information flow

(.epf files) through the web server to the report viewer software in the user's web browser.

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. 6. If the user has the right to view the document, the Web Intelligence Report Server checks whether it has up-to-date cached content for the document. 7. If cached content is available, the Web Intelligence Report Server sends the cached document information to the SDK. If cached content is not available, the following happens: a. The Web Intelligence Report Server obtains the document information from the CMS and checks what rights the user has on the document. b. The Web Intelligence Report Server obtains the Web Intelligence document from either the Input or Output File Repository Server and loads the document file.
Note: Which FRS is used depends on whether the request was for a

Web Intelligence document that was saved to BusinessObjects Enterprise or for an instance of the document. Documents are stored on the Input FRS. Instances are generated when an object is run according to a schedule, and they are stored on the Output FRS. c. If the document is set to “refresh on open” and the user has the View on Demand Rights, the Web Intelligence Report Server refreshes the data in the document with data from the dattabase.
Note: If the document is set to “refresh on open” but the user does

not have View On Demand rights, an error message is displayed.

60

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

BusinessObjects Enterprise XI 3.0 Architecture Information flow

2

d. The Web Intelligence Report Server stores the document file and the new document information in cache. e. The Web Intelligence Report Server sends the document information to the SDK. 8. The viewer script calls the SDK to get the requested page of the document. The request is passed to the Web Intelligence Report Server. 9. If the Web Intelligence Report Server has cached content for the page, it returns the cached XML to the SDK. If the Web Intelligence Report Server does not have the cached content for the page, it renders the page to XML using the current data for the document. It then returns the XML to the SDK. 10. The SDK applies an XSLT style sheet to the XML to transform it to HTML. 11. The viewer script returns the HTML to the browser.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

61

2

BusinessObjects Enterprise XI 3.0 Architecture Information flow

62

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment

3

3

Planning Your Deployment Planning your BusinessObjects Enterprise deployment

Planning your BusinessObjects Enterprise deployment
This section provides guidelines for assessing your organization's needs, and suggestions for deployment scenarios. By evaluating your needs before you deploy your BusinessObjects Enterprise system, you can keep troubleshooting to a minimum. The section includes examples and suggestions for deployment, but it is important to note that each deployment is unique. The flexibility of the BusinessObjects Enterprise service-based architecture allows you to tailor the deployment to serve your organization's requirements as precisely as possible. Planning your deployment involves the following steps: 1. Refer to the BusinessObjects Enterprise supported platform document at: http://support.businessobjects.com/documentation/supported_plat forms. 2. Review the key concepts you need to consider for your deployment, including operating system, database, and application server considerations, in addition to security, performance and scalability, and high availability. See Assessing your organization's environment on page 64. 3. Choose an initial deployment architecture. Which deployment architecture will serve your needs within the limits of your resources? For suggestions and common configurations, see Deployment scenarios on page 81.

Assessing your organization's environment
The resources and conventions used in your existing network environment affect how you deploy BusinessObjects Enterprise. This section serves as a checklist of criteria to help you plan your deployment, with resources provided for areas that you may need to investigate further. Different deployment options are available depending on which operating systems, web application servers, database servers and authentication method you plan to use. Other conventions used in your current environment

64

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

may also affect how you deploy BusinessObjects Enterprise, such as security, performance monitoring, and design for high availability. This section provides a high-level overview for assessing your environment prior to deployment.

Operating systems
BusinessObjects Enterprise runs on Microsoft Windows and Unix (including Linux) operating systems. There is one version of the BusinessObjects Enterprise installation guide for Windows, and one version for UNIX. An Administrator account must be used to install BusinessObjects Enterprise on Windows operating systems. However, installing BusinessObjects Enterprise on UNIX operating systems does not require root access. For a complete list of system privileges required, refer to User permissions for installing BusinessObjects Enterprise in the Windows version of BusinessObjects Enterprise Installation Guide, or UNIX permissions in the UNIX version of BusinessObjects Enterprise Installation Guide.
Note: Review the online BusinessObjects Enterprise supported platforms

document for information related to supported operating system release versions, patch levels, or caveats: http://support.businessobjects.com/docu mentation/supported_platforms.

Deployment on Windows

Ensure your hosts do not use any of the following characters in their name: an underscore, a period, or a slash. You must have Administrator rights to install BusinessObjects Enterprise on a Windows platform. BusinessObjects Enterprise supports both 32- and 64-bit Windows operating systems. To open ports and run daemon processes or services, BusinessObjects Enterprise must have the appropriate operating system account privileges.
Deployment on UNIX

Ensure your hosts use none of the following characters in their name: an underscore, a period, or a slash. You do not require root privileges in order

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

65

3

Planning Your Deployment Assessing your organization's environment

to install BusinessObjects Enterprise, although you may require root access to work with your chosen database, web, or web application systems. To run the setup program correctly, the following commands and utilities must be installed on your UNIX system and available on the PATH for the account being used to install BusinessObjects Enterprise:
/bin/sh uname awk tar stty pwd expr chown id ulimit read hostname grep dirname which touch sed tail gzip

These commands and utilities should be available on all UNIX distributions. However, if one of them is not available on your system, download and install a version appropriate to your UNIX system. It is recommended that you obtain any required files from your UNIX vendor when possible.
Note: In Solaris, AIX, and HP-UX, ensure that the PATH environment variable

of the account being used to install or run BusinessObjects Enterprise does not include GNU or third-party replacements for core system command-line tools (e.g. the GNU coreutils package, or an individually downloaded and compiled version of a tool). While the GNU versions of these tools offer enhanced functionality, their output can differ significantly from the native UNIX tools, and can cause problems with the BusinessObjects Enterprise installation or server scripts. Your operating system locale must be set to a UTF-8 encoding variant, such as en_US.UTF-8 (for other languages, use the appropriate localized UTF-8 encoding, such as de_DE.UTF-8 for German UTF-8). See the online BusinessObjects Enterprise supported platforms document for more information about locales: http://support.businessobjects.com/documenta tion/supported_platforms. BusinessObjects Enterprise supports both 32- and 64-bit UNIX operating systems.

66

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

Deployment in a virtualized environment

BusinessObjects Enterprise can also be installed in the following supported virtualized environments: • VMware. • AIX LPAR. • Solaris 10 Containers.

Databases in BusinessObjects Enterprise
In BusinessObjects Enterprise, a database can be defined as a data repository that organizes a collection of information into structures called tables for rapid search and information retrieval. Databases allow tables to be grouped together into collections of logically related tables called tablespaces. Tables are grouped into tablespaces within a database system in the same way that files are grouped into a directory within a file system.
Note: BusinessObjects Enterprise documentation uses the terms tablespace

and database interchangeably. The following database systems, among others, are supported for the Central Mangement System (CMS) database: • IBM DB/2. • Oracle Database. • MySQL. • Microsoft SQL Server. • Sybase Adaptive Server Enterprise (ASE). For a full list of database systems supported for each component of BusinessObjects Enterprise, see the platform availability report (PAR): http://support.businessobjects.com/documentation/supported_platforms. You are free to use any supported database system with BusinessObjects Enterprise. If you do not have a database system ready, the BusinessObjects Enterprise installer can create and configure a MySQL database system as part of the installation process.
Note:

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

67

3

Planning Your Deployment Assessing your organization's environment

If you use your own database system, first it must be configured and confirmed as operational, as the BusinessObjects Enterprise installer will attempt to verify the database connection. Ensure that any third-party database servers and clients are set up to use Unicode character encoding (UTF-8). Consult your database documentation to determine how to enable Unicode support.

BusinessObjects Enterprise connects directly to the database that you specify as a data source. For example, you could create reports directly from your organization's existing sales, manufacturing, or scientific database. In addition to your data source, BusinessObjects Enterprise uses several other databases to store internal system information. They can be configured as several tablespaces within a single database system, or as tablespaces distributed across several database systems. The following table details the different database or tablespace repositories used by BusinessObjects Enterprise.
Repository Description Required during installation? No

Reporting

Your organization's data repository containing the data to be analyzed with BusinessObjects Enterprise.

CMS

Main repository that stores Busines- Yes sObjects Enterprise user, group, security, content, and service information. If you do not have a CMS database from a previous installation, objects in this database will be initalized by the BusinessObjects Enterprise installer. Activity tracking repository that allows No administrators to view system usage information, such as the number of report generation or login events. Auditing can be enabled and configured during the installation process.

Auditing

68

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

Repository

Description

Required during installation?

Performance Manager (repository for Dashboard and Analytics)

Dashboard and Analytics tracks sys- No tem performance and matches it to set goals defined by an administrator. Dashboard and Analytics is only enabled when purchased as part of your license agreement. A Dashboard and Analytics repository is not set up by the installer, but can be configured after the initial installation is complete.

BusinessObjects Enterprise scripts require database user privileges that permit the creation and deletion of database objects, including tables, indexes, and temporary data. Rather than assign administrative privileges to the account used by BusinessObjects Enterprise, this table summarizes the privileges required for each supported database system.
Database IBM DB/2 Oracle Database Account or role privileges required User with Connect to database , Create tables , and Create schemas implicitly enabled.

User with the following privileges enabled: • create session • create table • create procedure Alternatively, a user with the CONNECT and RESOURCE roles enabled, and the Admin Option setting disabled for both roles.

MySQL Microsoft SQL Server Sybase ASE

Default database owner (DBO) account permissions. Default database owner (DBO) account permissions. Default database owner (DBO) account permissions.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

69

3

Planning Your Deployment Assessing your organization's environment

Databases may require specific configuration to function best with BusinessObjects Enterprise. The following table provides a list of additional configuration settings.
Database IBM DB/2 Additional settings required
DB2CODEPAGE=1208

Oracle

NLS_LANG must be set to a valid UTF-8 setting, such as AMERICAN_AMERI CA.WE8MSWIN1252 or AMERICAN_AMERI CA.AL32UTF8. The FORCE setting must be enabled.
LC_ALL must be set to a valid locale, as found in the configuration file SYBASE_HOME /locales/locales.dat.

Sybase

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 application server during the BusinessObjects Enterprise installation, or use a supported third-party web application server and Java Development Kit (JDK). Review the online BusinessObjects Enterprise supported platforms document for information related to supported web application server and JDK release versions, patch levels, or caveats: http://support.businessobjects.com/docu mentation/supported_platforms. If you use a third-party server, it must be installed and configured before you install BusinessObjects Enterprise, as the installer will attempt to verify the location of your web application server, and can deploy your web applications directly. The following table shows some of main differences between supported web application servers.

70

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

Web Application Server BEA WebLogic

Considerations Minimum 1.5 gigabytes of free space on install partition used to hold /tmp or the user-defined temporary directory, with a minimum of one gigabyte of free disk space on the install partition (WebLogic 9) or two gigabytes for WebLogic 10. Also recommended to have one gigabyte of RAM (minimum: 512 MB).

IBM WebSphere It is recommended that you have at least 1.2 gigabytes of free space on the partition used to hold /tmp or the user-defined temporary directory specified by your TMPDIR environment variable. Also recommended to have one gigabyte of RAM (minimum: 512 MB). Note: The BusinessObjects Enterprise installer will not deploy web

applications for the following web application servers. • JBoss. • SAP Application Server. • IBM WebSphere Community Edition.
Note: wdeploy tool will not deploy web applications for the following web

application server. • IBM WebSphere Community Edition. These web application servers must have web applications deployed manually, and in the case of JBOSS or the SAP Application Server, you can also use the supplied wdeploy tool. The wdeploy tool can be used to deploy web applications on third-party web application servers, as well as split tier web and web application servers, where a dedicated web server serves static content, and the web application server servers dynamic content. This is achieved by wdeploy separating the static and dynamic content, so the static content can be copied to the web server, and the dynamic content deployed to the web application server. The wdeploy tool enables you to deploy WAR files to a web application server in two distinct ways. 1. Standalone mode.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

71

3

Planning Your Deployment Assessing your organization's environment

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. Supported distributed combinations for BusinessObjects Enterprise XI 3.0: • Apache HTTP Server 2.2 and Tomcat 5.5. • Apache HTTP Server 2.2 and WebLogic 9.2 MP2 or 10. • IBM HTTP Server 6.1 and WebSphere 6.1.07. For more information on wdeploy, see the BusinessObjects Enterprisewde ploy user's guide or the Post Installation Web Application Deployment chapter of the BusinessObjects Enterprise Installation guide.

Web servers
Although web application servers come with built-in web server functionality, BusinessObjects Enterprise also supports the separation of web and web application servers into a de-paired configuration. In a de-paired configuration, the web server will serve static and cached content to offset a portion of the requests sent to the web application server. A web server may also support a reverse proxy configuration to improve site security. For more information on reverse proxy configuration, please see Reverse proxy on page 76. The BusinessObjects Enterprise installer will not automatically deploy the InfoView or Central Management Console (CMC) web applications to a de-paired environment. Web application tools must be configured manually using the bundled wdeploy utility to split the static and dynamic content so that each can be separately deployed to the web and web application servers. For more information on wdeploy, see the BusinessObjects Enterprisewde ploy user's guide or the Post Installation Web Application Deployment chapter of the BusinessObjects Enterprise Installation guide
Note: For more information about configuring split web and web application

servers, please see the BusinessObjects Enterprise Installation Guide.

72

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

Failover and load balancing
BusinessObjects Enterprise supports the clustering of your web application and back-end servers. Hardware or software load balancers can be used as the entry-point for the web application servers to ensure that the processing is evenly distributed among your servers. The following hardware load balancers are currently supported: • • • Cisco Content Services Switches (CSS). Cisco Content Switching Modules (CSM). The F5 BIG-IP family of load balancers.

The following persistence types are currently supported: • Source IP address persistence. • Cookie persistence Insert mode (ArrowPoint Cookie).
Note: Web services applications are currently not supported with cookie

persistence.

Multi-homed environment
BusinessObjects Enterprise supports multi-homed environments, in which a server has two or more network addresses. This allows servers to be configured to receive requests from one network and transmit requests to another. For example, an environment may have web application servers and database servers on separate subnets. The server tier can be configured to accept requests from the web application servers on one subnet (e.g. 192.168.0.0), and transmit database requests to database servers on another (e.g. 10.50.0.0). Multihomed environments use multiple physical or logical network cards.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

73

3

Planning Your Deployment Assessing your organization's environment

Security
Your organization's security policies affect how you deploy BusinessObjects Enterprise on your network. Do you plan to use the system's built-in authentication, or do you need it to work with existing LDAP or Windows Active Directory (AD) authentication? You also need to decide how your firewalls are configured, and if you plan to use a reverse proxy. To protect against unauthorized access, the BusinessObjects Enterprise architecture supports features such as: SSL encryption, reverse proxies, single sign-on, resource access security, object rights, and LDAP or Windows AD authentication.

Authentication
Authentication verifies the identity of a user who attempts to access the system. Assess how authentication is handled by your existing environment before deciding how to manage security within BusinessObjects Enterprise. The current release supports these methods of authentication: • BusinessObjects Enterprise authentication • LDAP authentication • Windows AD authentication • Trusted Authentication To use any of the third-party methods of authentication or Trusted Authentication, you will need to configure them before you use them with BusinessObjects Enterprise. For detailed instructions, see the Configuring third-party authentication section of the BusinessObjects Enterprise Administrator's Guide. For information about how to configure primary authentication or single sign-on, see the Security concepts section of the BusinessObjects Enterprise Administrator's Guide.

74

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

Firewalls
The Central Management Server (CMS) uses two ports: the request port and the name server port. The request port is selected dynamically by default. The name server port is 6400 by default. BusinessObjects Enterprise servers initially contact the CMS on its name server port. The CMS responds by returning the value of its request port.
Internal network communication

Almost all internal communication between networked BusinessObjects Enterprise servers is conducted through dynamically chosen port numbers. There are a few exceptions to this rule, as the standard port numbers are used if your deployment features any SMTP, FTP, rexec, rsh, and NetBIOS, or Microsoft Directory services. Standard ports for database and web application servers are also used, unless you specify otherwise during the BusinessObjects Enterprise installation process. If your BusinessObjects Enterprise system is distributed across more than one network (such as multiple CMS servers running in different geographic locations, or individual servers running on different subnets), you can configure the system to use static port numbers. This may simplify integration with any network security systems through which your BusinessObjects Enterprise system components must communicate. If all of your BusinessObjects Enterprise system components are contained locally within the same network, with unrestricted communication between each of the server machines, no configuration is required to facilitate internal communication.
External network communication

For both distributed and locally contained networked deployments, a firewall or other security system may separate the internal BusinessObjects Enterprise system components from any external web browser or feature-rich Java clients. Unless you change the default port numbers for your CMS and InfoView web applications, you must allow incoming traffic through your firewall on port 6400 TCP to allow clients to contact the CMS, and incoming traffic on port 1566 TCP to allow clients to contact InfoView. Your firewall

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

75

3

Planning Your Deployment Assessing your organization's environment

must also allow outbound connections on any port to allow the CMS and InfoView to reply to external clients on a dynamically chosen port.
Network Address Translation (NAT)

Firewalls often provide Network Address Translation (NAT) between systems on either side of the firewall. The CMS server configuration page allows you to enter the firewall's IP address or hostname in place of the corresponding system on the other side of the firewall. Outbound network traffic is then sent to the firewall, which is configured to forward it to the appropriate machine on the other side. For example, a CMS server is configured to send database requests to a firewall that resides between two different subnets. Effectively, the CMS considers the firewall to be a database server. The firewall accepts traffic from the CMS and passes it through to a database server running on a different subnet. Effectively, the database server sees the firewall as a CMS server. Neither the CMS nor the database server is aware of the firewall's existence, as the firewall provides the network translation between each of the two subnets.
Note: Static port numbers must be unique when using NATas firewalls

forward traffic based upon the port number used. If two different servers on one side of a firewall attempt to use the same port number, the traffic will merge and go to only one receiving server on the other side of the firewall.

Packet filtering

Your firewall may also provide packet filtering. This service allows or blocks traffic across a firewall based upon the original or destination network address. If your firewall uses packet filtering you must configure it so that traffic from your BusinessObjects Enterprise system components is allowed to pass through the firewall. For detailed information on any of these topics, see the Working with firewalls section of the BusinessObjects Enterprise Administrator's Guide.

Reverse proxy
Reverse proxies hide internal web application servers from clients on an external network. They receive and forward resource requests from external

76

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

client to servers on an internal network. They then return any responses from the internal network back to the originating clients, modifying the HTTP headers so the clients cannot detect that their request was not processed by the reverse proxy.
Restriction: A reverse proxy used with BusinessObjects Enterprise must

have the ability to modify the value of the path attribute in Set-Cookie headers. As a result, Apache 2.0 and Microsoft ISA 2006 are currently unsupported and cannot be used with BusinessObjects Enterprise XI 3.0. If you have a de-paired web and web application server, you can configure them to operate in a reverse proxy arrangement. The configuration of a reverse proxy server is a post-installation task that involves configuring a web server to forward client requests to the BusinessObjects Enterprise web application server.
Note: When using Apache as your reverse proxy server, pay attention to

the ProxyPass paths mapped in the Apache httpd.conf configuration file. Paths with similar beginnings must be mapped with the longest path first. For example, map InfoViewAppActions/ before InfoViewApp/.
ProxyPass /bobj/InfoViewAppActions http://192.168.57.169:8080/InfoViewAppActions ProxyPassReverseCookiePath /InfoViewAppActions /bobj/InfoViewAp pActions ProxyPass /bobj/InfoViewApp http://192.168.57.169:8080/In foViewApp ProxyPassReverseCookiePath /InfoViewApp /bobj/InfoViewApp

For more information about reverse proxies and BusinessObjects Enterprise, including detailed steps for individual web application servers, see the Modifying Default Security Behavior section of the BusinessObjects Enterprise Administrator's Guide.

HTTPS support
You can secure the HTTP communication between your BusinessObjects Enterprise web application server and the web browser clients it serves by using secure socket layer (SSL) encryption for HTTP. This arrangement is commonly referred to as HTTPS. As HTTPS communication is handled by the web application server and the client web browser, it is transparent to BusinessObjects Enterprise system

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

77

3

Planning Your Deployment Assessing your organization's environment

components and must therefore be configured post-install on your chosen web application server platform. To generate the encryption keys and enable HTTPS encryption, please consult the documentation supplied by your web application server vendor.

CORBA SSL support
Non-HTTP network communication between your BusinessObjects Enterprise system components uses the Common Object Request Broker Architecture (CORBA) communication standard. As CORBA supports SSL encrpytion, non-HTTP network traffic in your deployment can be secured: • Between rich clients and back-end servers. • Between your web application and back-end servers. • Between back-end servers.
Note: To learn more about how to secure HTTP traffic between your web

application server and web clients, read HTTPS support on page 77. You can enable CORBA SSL encryption by configuring each component of your BusinessObjects Enterprise deployment in turn, post-installation. See the Managing and configuring servers section of the BusinessObjects Enterprise Administrator's Guide.

Performance and scalability
Before deciding how to deploy your system, consider whether the demand on the system may change after it has been installed. This could be an increase in the number of concurrent users, the volume of business data, report complexity, or any other factor that could cause your BusinessObjects Enterprise system requirements to change. Anticipate these changes before you deploy to save you time and money by making architectural choices that will support a scalable solution. For example, if you are expecting an increase in the number of concurrent users accessing your system, you may consider deploying a small three-node cluster that can be expanded to five-nodes when demand increases.

78

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Assessing your organization's environment

3

By monitoring and regularly re-evaluating your system's performance, schedule tuning or configuration changes before potential issues become performance problems. For general information about assessing BusinessObjects Enterprise performance, see the Improving performance section of the BusinessObjects Enterprise Administrator's guide.

Split web and web application servers
You may choose to split your web and web application server into two servers, separated by a reverse proxy and firewall. This arrangement improves the performance of your web applications by off-loading static content from the web application server onto the web server, as well as shielding your web application servers behind several network layers for improved security.

Designing for high availability
High availability refers to a system that is almost always operational. When designing a system for high availability, consider how much down-time is acceptable for the system. To minimize time down, consider a combination of failover processing, server or server process redundancy, and frequent back-ups: • Failover processing If a BusinessObjects Enterprise service fails, a fault-tolerant system allows for continuous processing of system requests with no loss of service. To achieve this level of availability, you should provision duplicate BusinessObjects Enterprise services. For example, if a Web Intelligence Job Server process fails, the duplicate Web Intelligence Job Server process immediately takes its place. • Server redundancy A disaster recovery plan can minimize the effects of a disaster on an organization so you can maintain or quickly resume important system functions. It is good practice to keep the backup system at a different geographic location. The BusinessObjects Enterprise disaster recovery plan involves implementing redundant servers that mirror the primary system. If the

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

79

3

Planning Your Deployment Assessing your organization's environment

primary system goes down, a backup system is still available and becomes the production system. • Frequent data backups Regular and frequent backups provide an easy, cost-effective, and reliable method of protecting your valuable data. During a catastrophic system failure, the entire system can be quickly restored to the last backup point without the need to recreate a lot of data.
Note: When you back up your primary system, you need to back up: the

Central Management Server system database; the content of the Input and Output File Repository Servers; the user ID and password for the Administrator account; the application code from the Web Application Server; and the registry settings (if manual changes were made). You may not have the resources to implement a high degree of availability, but you can use best practices to provide the best possible availability for your system. These include vertical scaling (adding redundant server processes to a system in case the primary server process fails) and maintaining a regular back-up schedule.

Designing a multiple-server system for high availability
In a multiple-server environment, duplicate server processes can be installed onto additional machines. This is referred to as horizontal scaling because the duplicate server processes are spread across several machines, as opposed to the vertical scaling with duplicate server processes installed on just one machine. You can also cluster servers together so that transactions are processed more quickly, and, in the event of a failure, an unaffected machine can continue to process requests with minimal impact on the system's overall ability to process requests. Two common examples of fault tolerance in a multiple-server environment are: • CMS clustering With CMS clustering, a set of two or more server machines function as a single Central Management Server. In the event of a network, power,

80

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Deployment scenarios

3

hardware, or software failure on one server, the workload of the failed CMS is picked up by another within the same cluster. For more information about CMS clustering, see Managing and configuring servers in the BusinessObjects Enterprise Server Administrator's Guide. • Active and passive File Repository Servers (FRS) Your deployment can have multiple Input and Output FRSes. The first File Repository Server pair to register with the CMS cluster becomes the active FRS pair and the other FRS services are considered passive. Although all File Repository Server services run simultaneously, only the active FRS pair handles requests. If an active FRS fails, a passive FRS that is registered with the CMS cluster is changed to active status. When the previously active FRS becomes operational again, it is registered as a passive FRS with the CMS.

Deployment scenarios
After you determine the needs of your users and the resources required for the deployment, you can develop an initial deployment plan for BusinessObjects Enterprise. This section describes sample scenarios for administrators planning an installation of BusinessObjects Enterprise. To see detailed information for any of these scenarios, review the Deployment Scenarios chapter of the BusinessObjects Enterprise Installation and Configuration Guide. The optimal configuration for your deployment will depend on many factors: hardware configuration, database software, reporting requirements, operating system, clock speed, hyperthreading, disk speed, application server configuration, load frequency, and many more. Every deployment is unique, and these examples are provided only as guidelines. For information about assessing your system's unique needs and fine-tuning performance, see the Improving Performance section of the BusinessObjects Enterprise Administrator's guide. It is also recommended that you contact your Business Objects sales representative and request information about the BusinessObjects Enterprise Sizing Guide. A Business Objects Services consultant can assess your

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

81

3

Planning Your Deployment Deployment scenarios

reporting environment and assist in determining the configuration to best integrate with your current environment. As a baseline, this section assumes that you have not yet distributed the BusinessObjects Enterprise server processes across multiple machines; however, this section does assume familiarity with the BusinessObjects Enterprise architecture, installation, and server configuration. For preliminary installation information, see the BusinessObjects Enterprise Installation Guide.
Tip: If you are deploying multi-processor machines, you may also want to

run one or more BusinessObjects Enterprise server processes in multiple instances on that machine. For details, see Managing and deleting servers in the BusinessObjects Enterprise Administrator's Guide.

Desktop client to server overview
This scenario illustrates a simple client to server scenario which involves a desktop client application - Desktop Intelligence - connecting to the BusinessObjects Enterprise back-end server behind a firewall.
System layers

• • •

Data Tier: one machine with existing database server Server Tier: one machine for hosting the framework servers and another for all other BusinessObjects servers Client Tier: one machine for installing and running Desktop Intelligence

Configuration details

• • •

A firewall exists between client and server tiers Only the ports required for the communication between the desktop client and the server tier are open on the firewall BusinessObjects servers are distributed over two machines.
Windows Server 2003 SP2 Enterprise Edition Microsoft SQL Server 2005 Not relevant

Installation platform for BusinessObjects Enterprise Database for Central Management Server (CMS) Web application server

82

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Deployment scenarios

3

Firewall

Linux iptables

Desktop client to server diagram

The following diagram illustrates the system overview for the scenario once it is implemented.

N-tier scenario overview
This section describes how to setup a scenario in which a web browser accesses BusinessObjects Enterprise system through web applications.
System layers

• • • •

Data Tier: One machine used to host the database server. Server Tier: Three machines hosting the framework, processing and performance management (PMC) servers. Web Tier: One machine in hosting the web application server. Client Tier: One machine running the Live Office application.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

83

3

Planning Your Deployment Deployment scenarios

Configuration details Installation platform for BusinessObjects Enterprise Database for Central Management Server (CMS) Web application server Firewall Windows Server 2003 SP2 Enterprise Edition Oracle 10g R2 Oracle 10g R3 Linux iptables

Basic n-tier diagram

The following diagram illustrates the system overview for the scenario once it is implemented.

Complex deployment overview
The following scenario illustrates an end to end scenario which combines split web and server tiers. The web tier contains a load balancer and clustered web applications clustered on two separate machines. The server tier comprises clustered Central Management (CMS) and File Repository servers,

84

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Planning Your Deployment Deployment scenarios

3

and multiple instances of the remaining servers clustered on two separate machines..
System layers

• • • •

Data Tier: contains databases used by the CMS and File Repository servers. Server Tier: all BusinessObjects Enterprise servers installed on two machine running as a cluster. Web Tier: two web application servers installed on separate machines running as a cluster with fail- over support through load balancer. Client Tier: a browser used to log into Central Management Console (CMC).

Configuration details Installation platform for BusinessObjects Enterprise Database for Central Management Server (CMS) Web application server Load balancer Firewall Windows Server 2003 SP2 Enterprise Edition Microsoft SQL Server 2005 WebLogic 10 Cisco CSS 11500 series load balancer Linux iptables running on Red Hat Linux with two network interface cards (NIC)

Complex deployment diagram

The following diagram illustrates the system overview for the scenario once it is implemented.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

85

3

Planning Your Deployment Deployment scenarios

86

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Deployment Checklists

4

4

Deployment Checklists Deployment Checklist

Deployment Checklist
This section provides a checklist for the steps you need to perform when planning a deployment of BusinessObjects Enterprise. This section provides a checklist of the major tasks to be completed for the planning phase of your BusinessObjects Enterprise deployment.
Checklist item Reference Complete? (Y/N)

Understand the tiers that make up the Busi- Assessing your orga- Y__/N__ nessObjects Enterprise architecture. nization's environment on page 64 Understand the components and how they communicate with each other. Understand the workflows (how information travels through the architecture). Architectural overview on page 16 Y__/N__

Information flow on Y__/N__ page 56 Y__/N__ Y__/N__

Identify the operating system you will be de- Operating systems ploying the system on. on page 65 Choose the database servers will you be ac- Databases in Busicessing. nessObjects Enterprise on page 67 Choose a web application server.

Y__/N__ Web application servers on page 70

If you are using third-party authentication, Security on page 74 Y__/N__ secure sockets layer, firewalls, and/or reverse proxy, read the pertinent sections of the BusinessObjects Enterprise Administrator's Guide. Identify potential performance problems. Performance and scalability on page 78 Designing for high availability on page 79 Y__/N__

Choose whether or not to design for high availability and failover support.

Y__/N__

88

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Deployment Checklists Installation order

4

Checklist item

Reference

Complete? (Y/N)

Choose an architecture that meets all of these Deployment scenar- Y__/N__ needs. ios on page 81 Review the installation order for BusinessOb- Installation order on Y__/N__ jects Enterprise. page 89

Installation order
The following table lists the recommended order that BusinessObjects Enterprise system components should be installed. The actual order will vary depending on whether your system included pre-existing systems that are to be incorporated into the new BusinessObjects Enterprise deployment.
Order 1. Component Database server Description To use your own database server to store BusinessObjects Enterprise data, rather than the version of MySQL installed by the installer, at least one database server must be available for the CMS to use. A second database will be required to enable auditing. In addition, BusinessObjects Enterprise requires a connection to your organization's own database, to act as source material against which to run reports. To protect your database behind a firewall, install the firewall after the databases are configured and verified to be working. Ensure that access through the firewall is working in both directions.

2.

Database firewall

3. (a)

BusinessObjects En- Install the appropriate database drivers on terprise database your BusinessObjects Enterprise server sysdrivers tems and ensure that the database servers can be accessed through the firewall.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

89

4

Deployment Checklists Installation order

Order 3. (b)

Component

Description

BusinessObjects En- Install your BusinessObjects Enterprise terprise server or server or cluster using the BusinessObjects cluster Enterprise installer. You will need to enter connection information for all databases during the install. Server firewall To protect your BusinessObjects Enterprise server or cluster behind a firewall, install the firewall after the servers are configured and verified to be working. Ensure that access through the firewall is working in both directions. To use your own web application server instead of the version of Tomcat installed by the installer, install the web application server or cluster and verify network connectivity between it and the BusinessObjects Enterprise server. When your web application server is verified to be working, deploy the BusinessObjects Enterprise WAR files. To protect your web application server or cluster behind a firewall, install the firewall after the servers are configured and verified to be working. Ensure that access through the firewall is working in both directions. To use split web and web application servers so that server static content can be off-loaded from the web application servers, configure your web server or cluster and ensure connectivity to the web application server. When using a load balancer, configure the load balancer after the web servers or cluster are verified to be working. To protect your web server behind a firewall, install the firewall after the servers are configured and verified to be working. Ensure that access through the firewall is working in both directions.

4.

5. (a)

Web application server or cluster

5. (b)

WAR files

6.

Web application server firewall

7.

Web server or cluster

8.

Web server firewall

90

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Deployment Checklists Installation order

4

Order 9.

Component Reverse proxy

Description When using a reverse proxy server, configure the reverse proxy to once access through the web or web application server firewall has been verified. To protect your entire deployment behind a firewall, install the firewall after the entire system is configured and verified to be working. Ensure that access through the firewall is working in both directions.

10.

External firewall

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

91

4

Deployment Checklists Installation order

92

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

5

Glossary

access levels A predefined group of rights which allow you to set common security levels quickly. Using the predefined access levels whenever possible can greatly reduce the complexity of your object security model.
Note: In developer documentation, access levels are referred to as

"roles". advanced right A tool which allows administrators more granular control when setting rights in the CMC. alias A placeholder that allows administrators to link a user's multiple BusinessObjects Enterprise accounts. This is useful when a user has a third-party account that is mapped to Enterprise and an Enterprise account. By assigning an alias to the user, the user can log on using either a third-party user name and password or an Enterprise user name and password. Thus, an alias enables a user to log on via more than one authentication type. Application foundation See Dashboard and Analytics. Auditing A BusinessObjects Enterprise component that enables administrators to monitor, analyze, and optimize their BI system. A set of pre-defined reports are available. In addition, a BusinessObjects Universe is provided for administrators to create their own custom reports and analysis. authentication The process of verifying the identity of a user who attempts to access the system. Authentication types include Enterprise, Windows AD, Windows NT and LDAP authentication. Note that third-party user accounts and groups must be mapped to BusinessObjects Enterprise before you can use the latter three types of authentication. authorization The process of verifying that the user has been granted sufficient rights to perform the requested action upon the specified object. Automated Process Scheduler See Central Management Console

94

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

available right BusinessObjects Enterprise administrators setting rights in the CMC will be presented with rights options depending on the object they are setting rights on. For example, you can grant users the right to schedule a report, but you cannot grant users the right to schedule another user (because users cannot be scheduled). base right A right that applies to all objects in the system. For example, the "View objects" right is a base right: it applies equally well to folders, to reports, and to other BusinessObjects Enterprise objects. BusinessObjects See Desktop Intelligence. BusinessObjects Enterprise A business intelligence (BI) platform that powers the management and secure deployment of specialized end-user tools for reporting, query and analysis, and performance management (Dashboard and Analytics) on a scalable, and open services-oriented architecture. Cache server A server responsible for handling all report viewing requests. The Cache Server checks whether or not it can fulfill the request with a cached report page. If the Cache Server finds a cached page that displays exactly the required data, with data that has been refreshed from the database within the interval that you have specified as the default, the Cache Server returns that cached report page. calendar A customized list of run dates for scheduled jobs. When users schedule objects, they can use a calendar to run the job on a predefined set of dates. Calendars are particularly useful when users want to run a recurring job on an irregular schedule, or if administrators want to provide users with sets of regular scheduling dates to choose from. category An alternative to folders as a way of organizing objects. There are two types of categories: corporate and personal. Corporate categories are created and administrated by administrators with the appropriate rights, and are visible only to groups and users who have the rights to view them; personal categories are created by individual users, and are only visible to the users who created them.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

95

5

Glossary

Central Configuration Manager (CCM) A server administration tool provided in two forms. In a 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 a command line.For more information on the CCM, see the BusinessObjects Enterprise Deployment and Configuration Guide. Central Management Console (CMC) A web-based administrative tool for managing a BusinessObjects Enterprise system. It provides a single interface for user, content, and server management. Central Management Server (CMS) A server responsible for maintaining a database of information about your BusinessObjects Enterprise system which other components of the system can access as required. The data stored by the CMS includes information about users and groups, security levels, BusinessObjects Enterprise content, and servers. The CMS maintains security and manages objects and servers. connection See universe connection. Content Search An optimized search tool that enables users to search within the content of objects managed by BusinessObjects Enterprise. It also 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. With this enhanced search capability, users can also search within Discussions Notes and Encyclopedia information. Crystal Management Server See Central Management Server. Crystal Reports Explorer An application which allows users to create and modify reports, design layouts, and perform data analysis using a zero client interface. This functionality reduces IT reporting backlog by enabling users to create, save, and redistribute personalized report views in BusinessObjects Enterprise. Dashboard and Analytics

96

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

A suite of products which help 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 • • • Set Analysis Predictive Analysis Process Analysis

Designer A tool used to build universes. Desktop Intelligence A web-enabled integrated query, reporting, and analysis solution that allows users to access data in their corporate databases directly from their desktops. Desktop Intelligence makes it easy to access this data, because users work with it in the business terms that are familiar to them; they don't require knowledge of technical database terms like those used in SQL.This product was previously known as BusinessObjects in release 5.x/ 6.x. destination A place where scheduled objects are sent. Destinations include user inboxes, email, and FTP. Destination Job Server A server which can send objects and instances to destinations inside the BusinessObjects Enterprise system (i.e. to a user's inbox) or outside the system (i.e. to an email address). The Destination Job Server does not run the actual report or program objects. It handles only objects and instances that already exist in the Input or Output File Repository Servers. discussions A feature which enables users to create notes for reports, hyperlinks, programs, and other objects in InfoView. BusinessObjects Enterprise users who have the appropriate rights can view the notes or add their own comments to a discussion thread, which is a series of related notes in a hierarchical format. Users can create a discussion

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

97

5

Glossary

thread or add notes to a discussion thread for any object to which they have access. effective rights A calculation performed by the CMS that takes into account the effect of the rights set on an object. The result is displayed on the Rights page in the CMC. Encyclopedia A user panel inside BusinessObjects Enterprise for creating business intelligence (BI) reference guides. Accessible from your BI portal, Encyclopedia helps users locate and interpret your corporate information for more confident and accurate decision making. event A preset trigger for scheduling and processing objects. Event-based scheduling provides you with additional control over scheduling objects: you can set up events so that reports are proccessed only after a specified event occurs. Working with events consists of two steps: creating an event and scheduling an object with events. That is, once you create an event, you can select it as a dependency when you schedule an object . The scheduled job is then processed only when the event occurs. You can schedule an object with a file event, a custom event, and/or a schedule event. Event Server A server which 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 then starts any jobs that are dependent upon your file-based event. Everyone A group created by default in BusinessObjects Enterprise. All users are members of the Everyone group. File Repository Server (FRS) BusinessObjects Enterprise implementations typically include one Input and one Output File Repository Server. (In larger deployments, there may be multiple Input and Output File Repository Servers, for redundancy.) The Input File Repository Server manages all of the report objects that have been published to the system by

98

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

administrators or end users (using the Publishing Wizard, the CMC, the Import Wizard, or a component such as Crystal Reports). The Output File Repository Server manages all of the report instances generated by the LDAP authentication(s). The File Repository Servers 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. group A collection of users who share the same account privileges. Groups enable you to make changes to user rights in one place (the group) instead of modifying each user account individually. Groups are created by default (as in the case of the Administrators and Everyone groups), and custom-created by administrators according to organizational needs. inbox A destination for a scheduled report. When scheduling a report, you can specify that you want the system to store the report instances in the inbox of one or more users. You can also send existing report objects or instances to a user's inbox by using the "Send to" feature. Information Analyzer See Voyager. InfoView A web-based interface that end users access to view, schedule, and keep track of published reports. InfoView consolidates the presentation of a company's BI information and allows it to be accessed in a way that is secure, focused, and personalized to users inside and outside an organization. inheritance The method by which rights set on groups or folders are passed to subgroups, subfolders, individual users, and files in BusinessObjects Enterprise. instance A copy or "version" of an object that contains data that has been retrieved from one or more databases. Each instance contains data that is current at the time the report, query, or program is processed. In BusinessObjects Enterprise, you publish objects to the system, and then schedule those objects to generate instances on a recurring basis.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

99

5

Glossary

Java viewer A client-side viewer which is downloaded and installed in the user's browser. Job Server Any server which processes scheduled actions on objects at the request of the CMS. Job servers can be configured to process either report objects or program objects when you add the servers to BusinessObjects Enterprise. List of Values Job Server A server which processes scheduled list-of-value objects. List of Values object An object that contains the values of specific fields in a Business View. Lists of values are used to implement dynamic prompts and cascading lists of values within Crystal Reports. List-of-value objects do not appear in CMC or InfoView. For more information, see the Business Views Administrator's Guide. object A generic term for items represented in the Repository. BusinessObjects Enterprise supports many types of objects including reports, Web Intelligence documents, programs, Microsoft Excel files, Microsoft Word files, Microsoft PowerPoint files, Adobe Acrobat PDFs, rich text format files, text files, hyperlinks, and object packages. object package A type of object which functions as a folder for other objects, and allows you to schedule the contents simultaneously. Object packages can be composed of any combination of report and program objects that are published to the BusinessObjects Enterprise system. (Third-party objects, such as Excel, Word, Acrobat, Text, Rich Text, PowerPoint, and Hyperlink objects, cannot be added to object packages.) OLAP Intelligence A tool for creating reports based on multidimensional data. For more information, see the OLAP Intelligence User's Guide. Also see Voyager. Page Server

100

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

A server which responds to on-demand page requests from the Cache Server to generate Encapsulated Page Format (EPF) pages. The Page Server then returns the EPF pages to the Cache Server. The EPF pages contain formatting information that defines the layout of the report. The data for the report is saved with the report or retrieved on demand from the database. Performance management See Dashboard and Analytics. profile A tool for personalizing the content that users see when Desktop Intelligence documents are published. With profiles, users can schedule a publication (based on a Desktop Intelligence document) once, and deliver many different personalized versions of the document to your users (known as single-pass report bursting in earlier versions of BusinessObjects). Program Job Server A server which 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, and then runs the program. By definition, program objects are custom applications. Therefore the outcome of running a program depends on the particular program object run. program object An executable, script, or Java program that users can schedule to run regularly or based on an event. Program object features allow administrators to automate a wide range of administrative tasks, making BusinessObjects Enterprise a self-managing environment. Additionally, administrators can use program objects to trigger external processes, thus integrating BusinessObjects Enterprise into a broader workflow. Publishing A feature that allows users to schedule and distribute Desktop Intelligence documents, or specific sections of documents, through InfoView. Documents are then distributed to users either via the web or email. Publishing includes the ability for users or administrators to subscribe to and receive publications on a pre-defined timetable. publishing

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

101

5

Glossary

The process of adding objects to BusinessObjects Enterprise and making them available to authorized users. Publishing Wizard An application which allows you to publish objects to BusinessObjects Enterprise quickly. It also allows you to specify a number of options on each object that you publish. Although this application runs only on Windows, you can use it to publish reports to BusinessObjects Enterprise servers that are running on Windows or on UNIX. Report Application Server (RAS) A server which provides users with report design capability over the Web. It process reports that BusinessObjects Enterprise users view with the Advanced DHTML viewer, and it provides ad hoc reporting capabilities that allow users to create and modify reports over the Web. Report Job Server A server which processes scheduled reports, as requested by the CMS, and generates report instances. To generate a report instance, the Report Job Server obtains the report object from the Input 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. right The base unit for controlling user access to files, users, applications, servers, and other features in BusinessObjects Enterprise. When granted, each right provides a user or group with permission to perform a particular action. role See access level. scheduling The process through which a user determines when an object will run on the system. universe An abstraction of a data source that presents data to users in non-technical terms. Web Intelligence, Desktop Intelligence, and Crystal Reports users can connect to a universe and run queries against a database. They can perform data analysis and create reports using the objects in a universe, without seeing, or having to know anything about, the underlying data structures in the database.

102

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Glossary

5

Universes are created using the Designer. For complete information, see the Designer's Guide. universe connection A named set of parameters that defines how a BusinessObjects application accesses data in a database. A connection links Web Intelligence to your middleware. You must have a connection to access data. You must select or create a connection when you create a universe. For complete information, see the Designer's Guide. Voyager A web-based OLAP analysis tool that users access through InfoView. Voyager workspaces display OLAP data in crosstabs and charts. A user creates a workspace, populates it with crosstab and chart objects, connects those objects to OLAP data sources, and then defines queries to explore the data. For more information see the Business Objects Voyager User's Guide. Web Component Adapter (WCA) A server which communicates directly with the application server that hosts the BusinessObjects Enterprise SDK. The Web Component Adapter (WCA) runs within the application server and provides all services that are not directly supported by the BusinessObjects Enterprise SDK. The web server passes requests to the application server, which then forwards the requests to the WCA. Web Intelligence A web-based query and analysis tool that enables users to track, understand, and manage corporate data using a simple browser as their interface, while maintaining tight security over data access. Web Intelligence provides business users an easy-to-use interface for building and analyzing reports on corporate data over secured intranets and extranets. For more information, see the Web Intelligence User's Guide. Web Intelligence Job Server A server which processes scheduling requests it receives from the 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. Web Intelligence Report Server

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

103

5

Glossary

A server used to create, edit, view, and analyze Web Intelligence documents. It 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 cache the new information.

104

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Get More Help

A

A

Get More Help

Online documentation library

Business Objects offers a full documentation set covering all products and their deployment. The online documentation library has the most up-to-date version of the Business Objects product documentation. You can browse the library contents, do full-text searches, read guides on line, and download PDF versions. The library is updated regularly with new content as it becomes available. http://support.businessobjects.com/documentation/product_guides/
Additional developer resources

http://devlibrary.businessobjects.com
Online customer support

The Business Objects Customer Support web site contains information about Customer Support programs and services. It also has links to a wide range of technical information including knowledgebase articles, downloads, and support forums. http://www.businessobjects.com/support/
Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in relational and multidimensional databases, in connectivities, database design tools, customized embedding technology, and more. For more information, contact your local sales office, or contact us at: http://www.businessobjects.com/services/consulting/
Looking for training options?

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

106

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Get More Help

A

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line, and we will do our best to ensure that your suggestion is included in the next release of our documentation: mailto:documentation@businessobjects.com
Note: If your issue concerns a Business Objects product and not the

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

Business Objects product information

For information about the full range of Business Objects products, visit: http://www.businessobjects.com.

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

107

A

Get More Help

108

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Index
A
Adaptive job server 46 Adaptive processing server 48 authentication 74 BusinessObjects Enterprise servers Event Server 44 File Repository Servers 44 BusinessObjects Enterprise Web Services 34 BusinessObjects Mobile 19

B
basic web tier scenario configuration details 83 diagram 83 overview 83 system layers 83 Business view 53 Business Views Manager 23 BusinessObjects Enterprise .NET SDK 33 authentication 55 browser clients 19 Central Management Server (CMS) 55 Crystal Reports page server 50 desktop clients 23 documentation 13 Java SDK 30 job servers 46 packaged applications 36 Performance Management 51 report and processing servers 48 security 54 security plug-ins 55 semantic layers 53 web application servers 30 workflows 56 BusinessObjects Enterprise Java SDK 30

C
Central Configuration Manager (CCM) 23 Central Management Console (CMC) 19 Central Management Server (CMS) 42 security 55 clustering 80 Connection server 54 CORBA SSL encryption 78 Crystal Reports .NET SDK 33 Crystal Reports Cache Server 45 Crystal Reports Designer 23 Crystal Reports Explorer 36 Crystal Reports job server 46 Crystal Reports page server 50 Crystal Reports processing server 48 Crystal Reports Viewer 23

D
Dashboard Analytics server 48 Dashboard and Analytics 19, 36 Dashboard server 48 Data Source Migration Tool 23 deployment architecture 16 checklist 88 clustering 80 database 67

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

109

Index

deployment (continued) documentation 13 encryption 77, 78 firewalls 75 high availability 79 inital 11 installation order 89 load balancers 73 multi-homed 73 overview 10 planning 64 reverse proxy 76 scalability 78 security 74 split tier 79 updating 12 web application servers 70 web servers 72 what's new 8 deployment scenario complex 84 diagram 84 deployment scenarios desktop client to server 82 Desktop Intelligence 23 Desktop Intelligence report server 48 Desktop Intellignce job server 46 Destination job server 46 disaster recovery 79

H
high availability 79 HTTPS encryption 77

I
Import Wizard 23 InfoView 19, 23 Input File Repository Server 44

J
Java SDK 30 JavaServer Faces Components SDK 30

L
List of Values job server 46 Live Office 23

M
Multi-Dimensional Analysis Server (MDAS) 51

O
OLAP 51 Output File Repository Server 44

E
Event Server 44

P
Performance Management 51 Predictive Analytics server 48 Process Analysis server 48 Program job server 46 Publishing Wizard 23

F
fault tolerance 79 File Repository Servers 44 firewalls 75

110

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Index

Q
Query as a Web Service 23, 35, 36

U
Universe 53 Universe Builder 23 UNIX deployment 65

R
Report Application Server .NET SDK 33 Report Application Server (RAS) 48 Report Application Server (RAS) Java SDK 30 Report Conversion Tool 23 Report Engine Java SDK 30 Report Viewers 19 Repository Diagnostic Tool 23 reverse proxy 76

V
Viewers Java SDK 30 voyager 36 Voyager 19

W
wdeploy 36 web application servers 30 Web Intelligence 19 Web Intelligence job server 46 Web Intelligence processing server 48 Web Intelligence report server 48 Web Intelligence rich client 23 web services 34, 36 Query as a Web Service 35 web services Java SDK 30 Windows deployment operating systems 65 workflows report viewing 57 report viewing with cache and Crystal Reports servers 58 scheduling an object 56 viewing web intelligence documents 60

S
scenarios 81 SDK .NET 33 Java 30 web services 34 Server Intelligence 19 Software Inventory Tool 23 split tiers 79

T
tiers application 29 client 18 data 53 intelligence 38 processing 45 Translation Manager 23

X
Xcelcius 19

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

111

Index

112

BusinessObjects Enterprise XI 3.0 Deployment Planning Guide

Sign up to vote on this title
UsefulNot useful