A Personal connection is created by one user and cannot be used by other users. The connection details are stored in PDAC.LSI file.

A shared connection can be used by other users through a shared server. The connection details are stored in SDAC.LSI file in the Business Objects installation folder. However, one cannot set rights and securities on objects in a shared connection. Neither can a Universe to exported to repository using a shared connection.

A secured connection overcomes these limitations. Through it rights can be set on objects and documents. Universes can be exported to the central repository only through a secured connection. The connection parameters in this case are saved in the CMS.

BI Launchpad is a Java or HTML based interface of Business Objects tool to perform analytical reporting and data analysis. You can set the preference for your BI Launchpad which determines which tool interface is launched via Launchpad.

Using Web or Internet Application to access WebI interface via BI Launchpad, you can perform the below tasks −

Create, edit and refresh all the reports in Web Intelligence.

Create and edit all the queries in no data source (Universes) but not BEx queries in Web application.

You can create Webi documents based on BEx (business Exchange Queries) created by BEx Query Designer which is based on Info Cube in SAP BW system. You can connect to a BEx query in WebI with use of BICS BI consumer service connection. You need not to create Universe for BEx queries and all attributes, hierarchies, dimensions and measures are automatically mapped in WebI document.

Query filters are used to limit the rows returned in a WebI document. Query filters allow you to hide the data that you don’t want to show to specific people and also limit the size of. wid document. When you run a query, it only returns the rows that meet the query filter definition.

Below are the key features used in Query filter −

You can retrieve data as per specific business requirement.

You can hide the data that you don’t want specific users to see in a WebI document.

Limit the size of WebI document of network and hence provides performance optimization.

Context defines a particular join path between tables or a specific group of joins for a particular query. Any objects created on a table column which belong to specific contexts is naturally compatible with all other objects from same contexts.

Contexts may be created using detect contexts feature or manually. They are generally created based on logical calculation and business requirements, hence the detect context method is not very effective. To manually create a context, Go to Insert Context, give the context name and select the joins that should be present in the context. For a universe context should be created in a way that all joins (except shortcut joins) fall in at least one context.

Aggregate awareness function is used in scenarios where we have same fact tables in different grains. Using this function, we can define only one object for the measures in the fact tables.

aggregate_aware(highest_level,lower level)

We also need to define dimensions for associated granularities and define their incompatibilities with the corresponding facts through the aggregate navigation. This is accesses through Tools → Aggregate Navigation.

Use

They are used to enhance the performance reports by utilizing arrogate tables available at database and are applied at Universe level as function.

Subqueries provides you a more flexible option to filter the data as compared to an ordinary query filter. Using Subqueries, you can limit the values returned with a WHERE clause. You can also compare the values of objects in a subquery with the other objects.

Using Subqueries, you can implement complex logic to limit the size of data which are not possible to apply with simple query filters.

A dimension displays values that report users want to see in their documents. You can use a dimension for a scope of analysis. You can merge a dimension with a dimension from another data source to synchronize two different data sources.

A detail provides additional, complementary information to the information contained in a dimension and must be associated with a dimension. A detail cannot serve in a scope of analysis or merge with an object from another data source to synchronize two different data sources.

Query stripping feature optimizes the query to fetch only DATA which will be directly or indirectly rendered or displayed to the User, thus decreasing the response time and faster display of the report for the user. This feature is only available for OLAP universes, and it will be greyed out when using any RDBMS universe. It is used in Query panel.

Conditional Formatting is used to highlight some specific values in the report. If you want you can show specific low or high values with some specific colors. Conditional formatting can be applied to below elements −