SAP Business Objects Architecture and Universes

Business Objects has three repository connection modes: shared mode (multiple users share same connection), secured mode (each user has separate credentials), and personal mode (local development). Option A is incorrect as 'single shared' is not a standard mode name, and option C's terminology doesn't match BO conventions.

In Business Objects, thick clients are full-featured desktop applications installed locally. Desktop Intelligence (also known as DeskI) is the classic thick client for advanced report creation. Crystal Reports can be thick or thin, Web Intelligence is browser-based (thin), and 'none' is not applicable.

Thin clients in Business Objects are web-based tools that run in browsers without requiring local installation. Web Intelligence (WebI) is the primary thin client for ad-hoc reporting and analysis. Crystal Reports is typically thick client, Desktop Intelligence is thick client, and InfoView is a portal not a reporting tool itself.

Desktop Intelligence (Deski) reports use the .rep file extension to store report definitions, data providers, and formatting information. This is the standard file format for Deski reports in Business Objects Enterprise.

Crystal Reports files universally use the .rpt file extension. This extension stores the complete report definition including SQL queries, formatting formulas, and parameter settings.

Web Intelligence (Webi) reports use the .wid file extension to store report definitions, query specifications, and document structure. This format is specific to Web Intelligence in the BOE platform.

CMC stands for Central Management Console in Business Objects Enterprise. It provides the web-based administrative interface for managing users, servers, folders, and security across the entire BI platform.

BusinessObjects Enterprise XI R2 uses an n-tier architecture that separates concerns across multiple layers: client tier (applications), web tier (web servers), processing tier (report and job servers), and data tier (repository and databases). The n-tier design provides scalability and flexibility.

CCM stands for Central Configuration Manager in Business Objects Enterprise. It is a Windows-based administrative tool used to manage, start, stop, and configure all BOE servers on the system.

BusinessObjects Enterprise XI R2 includes 28 different server types in its standard deployment. These servers handle various functions like report processing, web application delivery, scheduling, caching, and data access across the platform.

In SAP Business Objects Universes for OLAP sources, direct access is supported for MultiProviders (MP) and Infocubes. These are valid SAP BW/BI data structures that can be directly accessed in universe design. ODS and Infoset are not typically direct-access OLAP sources in this context.

When creating a Business Objects universe on an SAP BW Infocube, the BI metadata features available include Hierarchies, Display Attributes, and Basic Key Figures. These are standard metadata objects exposed from Infocube structures. Variables are not part of the base Infocube metadata in this context.

To export an OLAP universe to the Business Objects repository, a Secured connection must be used. Personal connections are local to the machine, while Secured connections are stored in the repository and allow sharing. Universe exports require repository access via secured connections.

A single BO Universe connection maps to one specific data source or BEx query. It cannot simultaneously connect to multiple BEx queries. Each query requires its own connection definition in the universe parameters.

For key figures involving percentages in Business Objects universes, the 'Database Delegated' aggregation function must be used. This ensures percentage calculations are performed at the database level rather than aggregated incorrectly (summing percentages would produce wrong results).

In Business Objects Universe, optional variables defined in a query can be configured as mandatory when the universe is accessed through BO tools. This allows administrators to enforce parameter entry at the universe level rather than relying solely on report-level prompts. The variable's mandatory status overrides its optional definition in the BEX query.

The Universe Refresh Structure wizard in Business Objects performs comprehensive schema synchronization. When database structures change, the wizard can add new objects corresponding to new tables or columns, modify existing objects to reflect changed definitions, delete objects that no longer have underlying database structures, and hide deprecated objects while preserving them for backward compatibility. All four operations are standard features.

Web Intelligence report row limits can be enforced at the universe level through universe parameter configuration. Administrators can set maximum row retrieval limits to prevent resource-intensive queries from returning excessive data, which protects system performance and ensures reports remain manageable. This is a standard universe-level constraint.

Web Intelligence reports can leverage multiple universes in a single document, enabling data combination from different semantic layers. This capability allows reporting across heterogeneous data sources by creating separate queries from different universes, then merging the results at the report level. This is a standard feature for multi-source reporting.