Minimum Hardware requirements:
P3 700 MHz
1 GB RAM (2 GB is preferred)
6 GB of minimum Hard disk space
Saturday, February 28, 2009
XI R2 Installation
Business Objects Enterprise XI R2 Installation procedure
Pre-requisites:
Copy the content of BOXI R2 CDs to the server. Unpack all the files and keep in one folder.
Make sure that your Windows 2003 server has IIS 6.0 installed and enabled on the server if the goal is to put all the BO XI R2 components on the same server.
Pre-requisites:
Copy the content of BOXI R2 CDs to the server. Unpack all the files and keep in one folder.
Make sure that your Windows 2003 server has IIS 6.0 installed and enabled on the server if the goal is to put all the BO XI R2 components on the same server.
Make sure the Application server for ASP .NET is installed and enabled. If not, open your windows components in the “Add or Remove programs” section and double click on the application server and enable the ASP.NET.
Work with DBA to create two empty databases with the names BOE115 and BOE115_AUDIT. BOE115 is going to be CMS repository and BOE115_AUDIT is going to be the audit database. DBA should give read, write and update rights to these databases for the SQL ID “BOBJ” which the installer will be using during the installation.
Create ODBC DSNs on the BO application server with the same names as database names to connect to the respective DB.
Make sure that CMS database connection information is readily available while running the installation software.
Install all database client software required to connect to the reporting data sources. As our primary data source is EDW, we do not need any DB client software to be installed on the server.
Have both the permanent Business Object Enterprise Key code and Performance Manager key code (if applicable) ready before the start of the install.
Steps:
1. Run setup.exe from the BOE XI R2 software directory. Select “English” and click OK.
Note: Close all the programs before starting the installation.
Note: Close all the programs before starting the installation.
2. Click Next.
3. Accept the license agreement and click Next.
4. Select the “Perform Server Installation” option to install both the server and client components on the server. Click Next.
5. Enter the Key codes for Business Objects Enterprise and Performance Management and Click Next.
6. Specify the destination directory. By default the destination folder is displayed as “C:\Program Files\Business Objects”. If this needs to be changed to another folder or another drive, it can be changed here. Even though it is possible to change the folder locations or names, it is suggested to keep the same names as default. But drives (from C to E) can be changed and there is not going to be any impact on the installation. Click Next.
7. Select the install type as “Custom” as we need to select the components which we want to install. Use “Expand” option if you want to install any additional components on the servers for scalability or load balancing. Click Next.
8. When selecting the components, make sure to deselect the default “MySQL Server” under servers\Central Management Server as we want our repository to be SQL Server. Also deselect the “Java Web Component Adapters” as Wheels installation is a .NET installation. Click Next.
9. Select the checkbox and click Next.
10. Select “Yes” for new installation. If you want to install BO XI R2 components on additional server and to cluster with the existing CMS, choose the NO option and enter the existing CMS name. Click Next.
11. Select ODBC DSN for both the CMS database and for Auditing database using the browse button which displays all the system DSN entries. Select BOE115 for CMS and BOE115_AUDIT for audit database. Click Next.
12. Select only IIS ASP.NET checkbox as Wheels installation is a .NET installation. Click Next.
13. Click Next.
14. Installation begins.
15. At the end of the installation, hit “Register Later” button and click Next.
16. Click Finish to end the installation. By default all the Business Objects Services will be started and enabled after the install.
17. Make sure to reboot the server after the installation.
Note: Please find post-install configuration requirements on “Configuration of Business Objects Enterprise XI R2” document.
Note: Please find post-install configuration requirements on “Configuration of Business Objects Enterprise XI R2” document.
Thursday, February 26, 2009
DESKI vs WEBI
DESKI
VB Macro
Slice and Dice functionality
Database Ranking is not there
Column can be conditionally hidden
Free-hand sql, SP can be used as data providers
No time out error.
Needs to be installed on all the desktop machines
WEBI
Macro is not there
Slice and Dice functionality is not there
Database Ranking is there
Column cannot be conditionally hidden
Only universe is used as a data provider.
Time out error can appear.
Web based
VB Macro
Slice and Dice functionality
Database Ranking is not there
Column can be conditionally hidden
Free-hand sql, SP can be used as data providers
No time out error.
Needs to be installed on all the desktop machines
WEBI
Macro is not there
Slice and Dice functionality is not there
Database Ranking is there
Column cannot be conditionally hidden
Only universe is used as a data provider.
Time out error can appear.
Web based
Migration
The Import Wizard:
The Import Wizard acts as a bridge between the source repository and the target CMS repository (InfoStore).
Imports content from the source repository
Updates content (for example, universe IDs), and converts document format where necessary (for example, version Web Intelligence 2.x .wqy documents to version XI R2 Web Intelligence .wid files, as well as version 6.x BusinessObjects .rep files into version XI R2 .rep files)
Exports content into the target repository and physical storage area. At the end of the import, the Import Wizard creates a log file you can check for information about successful operations and issues.
Report conversion tool, is also available to convert Business Objects documents in version 6.x to Web Intelligence documents after you import them to the destination environment. As version XI R2 supports these documents, however, this type of conversion is a deployment choice, and not an integral part of the migration process.
The Import Wizard acts as a bridge between the source repository and the target CMS repository (InfoStore).
Imports content from the source repository
Updates content (for example, universe IDs), and converts document format where necessary (for example, version Web Intelligence 2.x .wqy documents to version XI R2 Web Intelligence .wid files, as well as version 6.x BusinessObjects .rep files into version XI R2 .rep files)
Exports content into the target repository and physical storage area. At the end of the import, the Import Wizard creates a log file you can check for information about successful operations and issues.
Report conversion tool, is also available to convert Business Objects documents in version 6.x to Web Intelligence documents after you import them to the destination environment. As version XI R2 supports these documents, however, this type of conversion is a deployment choice, and not an integral part of the migration process.
Wednesday, February 25, 2009
B O XI R3.0
Business Objects XI R3.0
Better security (Custom Access Levels, "Trumping" of rights, etc.)
Being able to prevent access rights from propagating to sub-objects (thereby avoiding the need to break inheritance)
New GUI for the CMC
Repository Federation (=replication of the repository to other BOE cluster)
Repository Diagnostic Tool (to remedy inconsistencies between CMS database entries and files in the FRS)
SIAs (new grouping/managing of servers, see also "bootstrap" files)
Cloning Server Services
Building Server Services templates (for cloning)
The CMC is now the leading system, not the CCM ( Central Configuration Manager)
Enhanced failover capabilities (session failover, etc.)
Improved Import Wizard (better understandable options)
Rich Client version of WebIntelligence (offline Webi), called WRC
Tracking feature in WebIntelligence
New Publishing features (close to BCAP of version 6.x)
Multi-language support for universes
Designer: Smart measures (or so called database delegated measures in the universe)
Designer: Focing predefined conditions on the whole universe or on a universe class
Optional prompts
Database delegated search for LOVs (data type CHARACTER)
Enhanced OLAP universes (see also SAP BW, etc.)
Better performance against SAP BW OLAP based universes
Being able to do an update to the structure of OLAP based universes with conflict resolution
Being able to build universes using stored procedures
Better security (Custom Access Levels, "Trumping" of rights, etc.)
Being able to prevent access rights from propagating to sub-objects (thereby avoiding the need to break inheritance)
New GUI for the CMC
Repository Federation (=replication of the repository to other BOE cluster)
Repository Diagnostic Tool (to remedy inconsistencies between CMS database entries and files in the FRS)
SIAs (new grouping/managing of servers, see also "bootstrap" files)
Cloning Server Services
Building Server Services templates (for cloning)
The CMC is now the leading system, not the CCM ( Central Configuration Manager)
Enhanced failover capabilities (session failover, etc.)
Improved Import Wizard (better understandable options)
Rich Client version of WebIntelligence (offline Webi), called WRC
Tracking feature in WebIntelligence
New Publishing features (close to BCAP of version 6.x)
Multi-language support for universes
Designer: Smart measures (or so called database delegated measures in the universe)
Designer: Focing predefined conditions on the whole universe or on a universe class
Optional prompts
Database delegated search for LOVs (data type CHARACTER)
Enhanced OLAP universes (see also SAP BW, etc.)
Better performance against SAP BW OLAP based universes
Being able to do an update to the structure of OLAP based universes with conflict resolution
Being able to build universes using stored procedures
Designer
In Designer, objects are qualified as one of three types: dimension, detail, or measure.
Dimension Parameters for analysis. Dimensions typically relate to a hierarchy such as geography, product, or time. For example Last Name and City_Id
Detail Provide a description of a dimension, but are not the focus for analysis. For example Phone Number
Measure Convey numeric information which is used to quantify a dimension object. For example Sales Revenue
The universe design methodology described in this manual consists of one planning stage, and three implementation phases:
• Analysis of business problem and planning the universe solution
• Designing a schema
• Building the universe
• Distributing the universe to users
Each implementation phase is based on an assumption that you have completed an initial planning phase. The planning phase can be done without using Designer, and is the decisive phase for the success or failure of your universe. A poorly planned universe that is not based on a study of user reporting needs will be difficult to design, implement, maintain, and will not be useful to your target users.
Dimension Parameters for analysis. Dimensions typically relate to a hierarchy such as geography, product, or time. For example Last Name and City_Id
Detail Provide a description of a dimension, but are not the focus for analysis. For example Phone Number
Measure Convey numeric information which is used to quantify a dimension object. For example Sales Revenue
The universe design methodology described in this manual consists of one planning stage, and three implementation phases:
• Analysis of business problem and planning the universe solution
• Designing a schema
• Building the universe
• Distributing the universe to users
Each implementation phase is based on an assumption that you have completed an initial planning phase. The planning phase can be done without using Designer, and is the decisive phase for the success or failure of your universe. A poorly planned universe that is not based on a study of user reporting needs will be difficult to design, implement, maintain, and will not be useful to your target users.
Query as a Web Service
Query as a Web Service is a Business Objects application that allows business users to quickly create queries and publish them as web services.A query as a web service is a SQL statement that has been built on a BusinessObjects universe and published as a web service to a host server housing web services.
The query as a web service is available to any application that uses web services, and allows users to access data returned by the query from within the application. It allows Business Intelligence (BI) information to be securely delivered to any application that can consume web services.
Query as a Web Service has a client component that you use to create queries from universes, and a server-side web service that allows developers to create web services from specific Business Objects queries.
The query as a web service is available to any application that uses web services, and allows users to access data returned by the query from within the application. It allows Business Intelligence (BI) information to be securely delivered to any application that can consume web services.
Query as a Web Service has a client component that you use to create queries from universes, and a server-side web service that allows developers to create web services from specific Business Objects queries.
Xcelsius
Xcelsius complements all types of Portal initiatives, Business Intelligence programs, Executive Dashboards, Balanced Scorecard projects, Marketing Reports, and day-to-day reporting and presentation requirements. Xcelsius does this by letting users participate in the report creation process and analysis.
Crystal Xcelsius Designer 4.5 enables to create interactive presentations from Managed Enterprise Data. Using the new Live Office Connector in Crystal Xcelsius Designer and the new Live Office Web Services in BO Enterprise XI R2, can create and refresh Xcelsius Visualizations against managed Enterprise data.
Crystal Xcelsius Designer 4.5 enables to create interactive presentations from Managed Enterprise Data. Using the new Live Office Connector in Crystal Xcelsius Designer and the new Live Office Web Services in BO Enterprise XI R2, can create and refresh Xcelsius Visualizations against managed Enterprise data.
Saturday, February 21, 2009
Performance Tuning
Why Report takes a long time to execute?
Did you look at the execution time of the data provider?
You will have to separate this time from the computation time, this is the time that it takes Business Objects to actually render the data on your screen after the data has been retrieved from the database. The computation time includes calculating of all variables, formulas, filters, alerters, applying formatting, etc.
Suddenly Report performance decreased?
Ask your DBA to check on the database server.
Did any DBMS parameters change?
Did the load on the database server increase?
Data base partition might have dropped.
System resources might not be available.
Did the data volume increase by a magnitude?
Have database indexes been dropped? How about statistics, etc.
How to improve the performance of the report?
Do not use constant values in the report.
Organize your query well .
Know the db structure to best design the query.
Do not refresh every report on open or so, do it as per requirement.
Try to make sure you where clauses constrain on integers in the where clause, if possible, you can use Index Awareness in Designer for this.
Try and produce your reports with as few data providers as possible. Remove unused formule, they should, ideally all be variables.
Universe side
Minimize the unnecessary joins.
Use derived tables which reduce data returned to a document for analysis, Use short cut joins, Aggregate awareness, Index awareness.
Make sure all the measure objects have aggregate functions.
Increase the array fetch size from the file
-> Universe parameters -> Definition-> Edit -> Advanced.
Increasing the Array fetch size may get the results to appear faster on the users PC.
Try to limit the size of the long objects
Try to use faster cardinality detection
If the data base is cost bases then we must make sure the statistics are upto date.
If the data base is rule based optimization, the order of the tables in the “From” clause are important.
Altering these manually by assigning the row counts in the designer.
Right click on the table -> Number of rows in the table -> Check “modify manually tables row count” to the size depending on the order of the tables in the “From” clause of the Join.
(make sure that the tables contains smaller number of rows should be in the first next to the “From” clause)
Data base side
Try and resolve complex calculations using your ETL, rather than calculate at run time, using Business Objects.
Try to use properly indexed tables or material views rather than derived table or standard views.You should analyse the query using a SQL editor, e.g. Explain Plan for Oracle. You should then provide indexing on the database and hints in Designer as required.
Installation steps of BO 5.1 and 6.5
-Creating Repository.-Server Configuration i.e creating clusters, ORB config etc. -Creating groups/users in Supervisor, assigning rights based on each module i.e. Supervisor, Designer, BusinessObjects reporter, WebI.-Designing universes/reports. -Testing, UAT (User Acceptance Testing), rollout & signoff.\
SQL Query tuning
1. Index plays a big part in performance. Indexing a column. Whichever columns we are using most of the times for searching we can make that column as index.
Scenario: select * from empinfo where name='smith'
What is a Index: Index points to a table or view
There are implicit and explicit index. Single column index (Index for one column) and Composite Index (Indexing multiple columns)
System itself create index whenever there is a primary key in a column and is called Implicit Index.
select index_name from dba_indexes where owner='scottsql' by logging in as system user
When creating index on a table what happens is it creates one more table and all the names will come together.
Using Alias name when calling the table instead of calling the table name improves the performance
WHEN USING FROM , SMALLEST TABLE SHOULD BE FIRST AND THEN THE LARGEST TABLE - PERFORMANCE INCREASES (FROM READS FROM THE LEFT HANDSIDE)
WHERE LAST_NAME='SMITH'----- RETURNS 2000 ROWS
WHERE CITY = 'DALLAS' ----- RETURNS 30,000 ROWS
WHENEVER WE ARE USING WHERE CLAUSE FIRST WE SHOULD BE KEEP THE WHERE CITY='DALLAS' AND LAST_NAME='SMITH' AND THIS IS BETTER THAN WHERE LAST_NAME='SMITH' AND CITY=DALLAS. --- IMPROVES THE PERFORMANCE AND. WHERE CLAUSE READS FROM THE RIGHT HAND SIDE)
VIEW PLAYS AN IMPORTANT ROLE ON SECURITY
vIEW PLAYS AN IMPORTANT ROLE IN PERFORMANCE TUNING
VIEW IS AN VIRTUAL TABLE
VIEW IS STORED IN MEMORY ONLY SO IT WON'T OCCUPY ANY SPACE
COMBINE MULTIPLE TABLES AND USE JOIN AND CREATE THE VIEW FOR OUR OWN NEEDS - VERY IMPORTANT
NESTED VIEW ALSO POSSIBLE
VIEW CAN't BE OVERWRITTEN AND IT CAN BE DROPPED AND RECREATED AGAIN
A VIEW CAN BE CREATED FROM A VIEW
If there is a primary key in the original table inserting and deleting from the view will not affect the original table. If inserting we must insert all the fields
If there is no primary key then inserting or updating the view will update the original table
Synonym (another name for table or view)
using this increases the performance
surrogate key in a database is a unique identifier for either an entity in the modeled world or an object in the database. The surrogate key is not derived from application data.
Did you look at the execution time of the data provider?
You will have to separate this time from the computation time, this is the time that it takes Business Objects to actually render the data on your screen after the data has been retrieved from the database. The computation time includes calculating of all variables, formulas, filters, alerters, applying formatting, etc.
Suddenly Report performance decreased?
Ask your DBA to check on the database server.
Did any DBMS parameters change?
Did the load on the database server increase?
Data base partition might have dropped.
System resources might not be available.
Did the data volume increase by a magnitude?
Have database indexes been dropped? How about statistics, etc.
How to improve the performance of the report?
Do not use constant values in the report.
Organize your query well .
Know the db structure to best design the query.
Do not refresh every report on open or so, do it as per requirement.
Try to make sure you where clauses constrain on integers in the where clause, if possible, you can use Index Awareness in Designer for this.
Try and produce your reports with as few data providers as possible. Remove unused formule, they should, ideally all be variables.
Universe side
Minimize the unnecessary joins.
Use derived tables which reduce data returned to a document for analysis, Use short cut joins, Aggregate awareness, Index awareness.
Make sure all the measure objects have aggregate functions.
Increase the array fetch size from the file
-> Universe parameters -> Definition-> Edit -> Advanced.
Increasing the Array fetch size may get the results to appear faster on the users PC.
Try to limit the size of the long objects
Try to use faster cardinality detection
If the data base is cost bases then we must make sure the statistics are upto date.
If the data base is rule based optimization, the order of the tables in the “From” clause are important.
Altering these manually by assigning the row counts in the designer.
Right click on the table -> Number of rows in the table -> Check “modify manually tables row count” to the size depending on the order of the tables in the “From” clause of the Join.
(make sure that the tables contains smaller number of rows should be in the first next to the “From” clause)
Data base side
Try and resolve complex calculations using your ETL, rather than calculate at run time, using Business Objects.
Try to use properly indexed tables or material views rather than derived table or standard views.You should analyse the query using a SQL editor, e.g. Explain Plan for Oracle. You should then provide indexing on the database and hints in Designer as required.
Installation steps of BO 5.1 and 6.5
-Creating Repository.-Server Configuration i.e creating clusters, ORB config etc. -Creating groups/users in Supervisor, assigning rights based on each module i.e. Supervisor, Designer, BusinessObjects reporter, WebI.-Designing universes/reports. -Testing, UAT (User Acceptance Testing), rollout & signoff.\
SQL Query tuning
1. Index plays a big part in performance. Indexing a column. Whichever columns we are using most of the times for searching we can make that column as index.
Scenario: select * from empinfo where name='smith'
What is a Index: Index points to a table or view
There are implicit and explicit index. Single column index (Index for one column) and Composite Index (Indexing multiple columns)
System itself create index whenever there is a primary key in a column and is called Implicit Index.
select index_name from dba_indexes where owner='scottsql' by logging in as system user
When creating index on a table what happens is it creates one more table and all the names will come together.
Using Alias name when calling the table instead of calling the table name improves the performance
WHEN USING FROM , SMALLEST TABLE SHOULD BE FIRST AND THEN THE LARGEST TABLE - PERFORMANCE INCREASES (FROM READS FROM THE LEFT HANDSIDE)
WHERE LAST_NAME='SMITH'----- RETURNS 2000 ROWS
WHERE CITY = 'DALLAS' ----- RETURNS 30,000 ROWS
WHENEVER WE ARE USING WHERE CLAUSE FIRST WE SHOULD BE KEEP THE WHERE CITY='DALLAS' AND LAST_NAME='SMITH' AND THIS IS BETTER THAN WHERE LAST_NAME='SMITH' AND CITY=DALLAS. --- IMPROVES THE PERFORMANCE AND. WHERE CLAUSE READS FROM THE RIGHT HAND SIDE)
VIEW PLAYS AN IMPORTANT ROLE ON SECURITY
vIEW PLAYS AN IMPORTANT ROLE IN PERFORMANCE TUNING
VIEW IS AN VIRTUAL TABLE
VIEW IS STORED IN MEMORY ONLY SO IT WON'T OCCUPY ANY SPACE
COMBINE MULTIPLE TABLES AND USE JOIN AND CREATE THE VIEW FOR OUR OWN NEEDS - VERY IMPORTANT
NESTED VIEW ALSO POSSIBLE
VIEW CAN't BE OVERWRITTEN AND IT CAN BE DROPPED AND RECREATED AGAIN
A VIEW CAN BE CREATED FROM A VIEW
If there is a primary key in the original table inserting and deleting from the view will not affect the original table. If inserting we must insert all the fields
If there is no primary key then inserting or updating the view will update the original table
Synonym (another name for table or view)
using this increases the performance
surrogate key in a database is a unique identifier for either an entity in the modeled world or an object in the database. The surrogate key is not derived from application data.
B-O-E Professional
BusinessObjects Enterprise Professional
BOE Professional is the core BI Platform license that organizations license to deliver BI capabilities to end users and administrators. It includes a centralized and customizable BI platform for IT to manage and administer. Through a secure, personal BI portal (InfoView), end users have the right to work with one BI content type – Crystal Reports or Web Intelligence/Desktop Intelligence/Voyager.
Product Capabilities
Key end user BOE Professional capabilities include:
BI Portal
The InfoView BI portal allows users to view and work with one of the following two content types:
Crystal Reports content (BusinessObjects Enterprise Professional for Enterprise Reporting) – From BOE, users can view, refresh, and schedule Crystal Reports. Interaction, such as prompts and guided navigation, are permitted when the capability has been pre-engineered into the reports by the report author. Report authoring requires Crystal Reports.
-OR-
Web Intelligence/Desktop Intelligence/Voyager content (BusinessObjects Enterprise Professional for Query, Reporting, and Analysis) – From BOE, users can view, refresh, and schedule Web Intelligence and Voyager content. Interactive viewing is available with a Web Intelligence Interactive Viewing license. Interactive viewing and full self-service query and analysis capabilities require a full Web Intelligence license.
The BI Portal also supports the management of third party documents such as Adobe PDF, Microsoft Word, Excel, or PowerPoint.
Discussions
Threaded discussions provide collaboration to users from within the BI portal and within performance management dashboards and scorecards. Discussions are available for all BI content types.
Scheduling
Time-based scheduling of reports including support for business calendars
Sending reports to email, file server, or to other users within the system
Offline/batch processing of documents
BI Content Search
Securely find existing BI content from within the InfoView BI portal.
Key word search allows users to quickly find the right Crystal reports, Web Intelligence and Desktop Intelligence documents, and Dashboard Manager metrics.
New navigation capabilities categorize results, which helps users further refine their search and find the right information.
Auto report generation from search requires a Web Intelligence license.
Delivered with the BusinessObjects XI Release 2 Productivity Suite.
Auditing
Allow administrators to monitor, analyze, and optimize their BI system. BOE stores audit data in a relational database.
Configure and setup auditing database.
Track success and failure of system and user actions.
Leverage sample templates or create custom auditing reports.
Ad hoc analysis of your BI systems.
Identify and track trends.
Customers that are currently license for Auditor can receive Auditing provided they are current on maintenance.
Publishing
Ability to send information from a single report with information specific to each recipient.
Refresh selected documents once for each user based on their individual security profile.
Included in BOE Professional for Query, Reporting, and Analysis only.
Key administrative BOE Professional capabilities:
Web-based management console
License key management.
Security access control and configuration.
User & group creation/management.
Server/service setup and configuration.
Semantic layer creation• Universe and Business Views creation
Development and SDKs
Web services, Java, and .NET SDKs for application and portal integration.
Portal Integration Kits (PIKs) integrate BI content into popular enterprise portals.
SDK documentation.
•Management samples.
BOE Professional is the core BI Platform license that organizations license to deliver BI capabilities to end users and administrators. It includes a centralized and customizable BI platform for IT to manage and administer. Through a secure, personal BI portal (InfoView), end users have the right to work with one BI content type – Crystal Reports or Web Intelligence/Desktop Intelligence/Voyager.
Product Capabilities
Key end user BOE Professional capabilities include:
BI Portal
The InfoView BI portal allows users to view and work with one of the following two content types:
Crystal Reports content (BusinessObjects Enterprise Professional for Enterprise Reporting) – From BOE, users can view, refresh, and schedule Crystal Reports. Interaction, such as prompts and guided navigation, are permitted when the capability has been pre-engineered into the reports by the report author. Report authoring requires Crystal Reports.
-OR-
Web Intelligence/Desktop Intelligence/Voyager content (BusinessObjects Enterprise Professional for Query, Reporting, and Analysis) – From BOE, users can view, refresh, and schedule Web Intelligence and Voyager content. Interactive viewing is available with a Web Intelligence Interactive Viewing license. Interactive viewing and full self-service query and analysis capabilities require a full Web Intelligence license.
The BI Portal also supports the management of third party documents such as Adobe PDF, Microsoft Word, Excel, or PowerPoint.
Discussions
Threaded discussions provide collaboration to users from within the BI portal and within performance management dashboards and scorecards. Discussions are available for all BI content types.
Scheduling
Time-based scheduling of reports including support for business calendars
Sending reports to email, file server, or to other users within the system
Offline/batch processing of documents
BI Content Search
Securely find existing BI content from within the InfoView BI portal.
Key word search allows users to quickly find the right Crystal reports, Web Intelligence and Desktop Intelligence documents, and Dashboard Manager metrics.
New navigation capabilities categorize results, which helps users further refine their search and find the right information.
Auto report generation from search requires a Web Intelligence license.
Delivered with the BusinessObjects XI Release 2 Productivity Suite.
Auditing
Allow administrators to monitor, analyze, and optimize their BI system. BOE stores audit data in a relational database.
Configure and setup auditing database.
Track success and failure of system and user actions.
Leverage sample templates or create custom auditing reports.
Ad hoc analysis of your BI systems.
Identify and track trends.
Customers that are currently license for Auditor can receive Auditing provided they are current on maintenance.
Publishing
Ability to send information from a single report with information specific to each recipient.
Refresh selected documents once for each user based on their individual security profile.
Included in BOE Professional for Query, Reporting, and Analysis only.
Key administrative BOE Professional capabilities:
Web-based management console
License key management.
Security access control and configuration.
User & group creation/management.
Server/service setup and configuration.
Semantic layer creation• Universe and Business Views creation
Development and SDKs
Web services, Java, and .NET SDKs for application and portal integration.
Portal Integration Kits (PIKs) integrate BI content into popular enterprise portals.
SDK documentation.
•Management samples.
BO 6 Installation
BO 6 Installation
Install Apache web server & Install Tomcat application server
Configure Apache & Tomcat server
Try the connection between the Apache & Tomcat using mod_jk.dll connector
Install the BO server products
Configure the BO server products
Configure the ORB (For cluster settings)
Set the service parameters (Allow to define the Business Objects server to run automatically and run as a windows service)
Creating the application instance (Deploying Infoview on apache and tomcat)
Start Cluster, Start Apache, Start Tomcat and then Business Objects Server
Install Apache web server & Install Tomcat application server
Configure Apache & Tomcat server
Try the connection between the Apache & Tomcat using mod_jk.dll connector
Install the BO server products
Configure the BO server products
Configure the ORB (For cluster settings)
Set the service parameters (Allow to define the Business Objects server to run automatically and run as a windows service)
Creating the application instance (Deploying Infoview on apache and tomcat)
Start Cluster, Start Apache, Start Tomcat and then Business Objects Server
Fan Trap
Fan Trap
A Fan Trap is a one - many relationship.
This would happen if you are using a Summary and a Detail table in one query. Fan Traps can cause numbers to multiply.
Fact table that contains aggregated facts are called summary table
Scenario of Fan Trap
when you select dimensions from D1 and measures from F1 and F2. Then you may have fan trap that needs to be resolved.
The universe has the below situation,
Table A - Dimensions table ( contains few measure values)
Table B - Fact (No reporting objects - contains only key fields - measure less fact)
Table C - Fact (detailed fact - Transaction amounts)
A -> B -> C all are one to many joins between the tables.
Scenario 1: Dimensions, Measures from A and measures from C report returns correct results and BO generates sql for each measure.
Scenario 2: Dimensions/Measures from A and measures/dimensions from C. Then the measures from 'A' aggregating wrongly (doubled / tripled) , where as measures from 'C' is fine. I beleive this is due to the reason that Table 'C' is more detail data.
Is this a Fan Trap situation? If YES how to resrtict? Tried the regular scenario of aliasing the table 'A' and creating context but no success.
http://www.forumtopics.com/busobj/viewtopic.php?t=93351
Business Objects resolves this transparently by using 2 queries.
It is resolved automatically as long as the measure objects have aggregrate functions that means, (query will split in 2).
Also, you just need to make sure the Multiple SQL Statements for Each Measure box is checked in Designer. File -> Parameters->SQL-> Check “Multiple SQL Statements for each measure”
Another way to solve this problem is,
1. Create an alias for the table (Original table) that is producing multiplied aggregation
2. Create a one to one join between the alias table and the original table
3. Build the object that is causing the aggregation on the alias tables
4. Define a context for a original table and a context for the alias table
5. File -> Parameters->SQL-> Check “Multiple SQL Statements for each measure”
6. Modify the select statement for the columns that are summed so that the columns in the alias table are summed and not the columns in the original table
A Fan Trap is a one - many relationship.
This would happen if you are using a Summary and a Detail table in one query. Fan Traps can cause numbers to multiply.
Fact table that contains aggregated facts are called summary table
Scenario of Fan Trap
when you select dimensions from D1 and measures from F1 and F2. Then you may have fan trap that needs to be resolved.
The universe has the below situation,
Table A - Dimensions table ( contains few measure values)
Table B - Fact (No reporting objects - contains only key fields - measure less fact)
Table C - Fact (detailed fact - Transaction amounts)
A -> B -> C all are one to many joins between the tables.
Scenario 1: Dimensions, Measures from A and measures from C report returns correct results and BO generates sql for each measure.
Scenario 2: Dimensions/Measures from A and measures/dimensions from C. Then the measures from 'A' aggregating wrongly (doubled / tripled) , where as measures from 'C' is fine. I beleive this is due to the reason that Table 'C' is more detail data.
Is this a Fan Trap situation? If YES how to resrtict? Tried the regular scenario of aliasing the table 'A' and creating context but no success.
http://www.forumtopics.com/busobj/viewtopic.php?t=93351
Business Objects resolves this transparently by using 2 queries.
It is resolved automatically as long as the measure objects have aggregrate functions that means, (query will split in 2).
Also, you just need to make sure the Multiple SQL Statements for Each Measure box is checked in Designer. File -> Parameters->SQL-> Check “Multiple SQL Statements for each measure”
Another way to solve this problem is,
1. Create an alias for the table (Original table) that is producing multiplied aggregation
2. Create a one to one join between the alias table and the original table
3. Build the object that is causing the aggregation on the alias tables
4. Define a context for a original table and a context for the alias table
5. File -> Parameters->SQL-> Check “Multiple SQL Statements for each measure”
6. Modify the select statement for the columns that are summed so that the columns in the alias table are summed and not the columns in the original table
Chasm Trap
Chasm Trap
A chasm Trap is a many - one relationship.
This would happen when two "many to one" joins converge on a single table. You will get incorrect results when the following circumstances exist:
A "many to one to many relationship" exists among three tables in the universe structure. The query includes objects based on two tables both at the "many" end of their respective joins. There are multiple rows returned for a single dimension.
One way to resolve a Chasm Trap use Designer to define a context for each table at the "many" end of the joins. This creates two SQL statements and two separate tables in Business Objects.
Another way to resolve a Chasm Trap is in Designer select the option Multiple SQL Statements for Each Measure from the Universe Parameters dialog box. (This is a default setting). Only applies to measures. You force the SQL generation engine in Reporter to generate SQL queries for each measure that appears in the Query panel. You cannot use this solution to generate multiple SQL statements for dimensions.
A chasm Trap is a many - one relationship.
This would happen when two "many to one" joins converge on a single table. You will get incorrect results when the following circumstances exist:
A "many to one to many relationship" exists among three tables in the universe structure. The query includes objects based on two tables both at the "many" end of their respective joins. There are multiple rows returned for a single dimension.
One way to resolve a Chasm Trap use Designer to define a context for each table at the "many" end of the joins. This creates two SQL statements and two separate tables in Business Objects.
Another way to resolve a Chasm Trap is in Designer select the option Multiple SQL Statements for Each Measure from the Universe Parameters dialog box. (This is a default setting). Only applies to measures. You force the SQL generation engine in Reporter to generate SQL queries for each measure that appears in the Query panel. You cannot use this solution to generate multiple SQL statements for dimensions.
Alias
Alias
When designer see 2 join statements between same 2 tables then loop forms and in this case we can’t get the expected output (few rows will be returned).
Alias represents the table in a different context.
When designer see 2 join statements between same 2 tables then loop forms and in this case we can’t get the expected output (few rows will be returned).
Alias represents the table in a different context.
Context
Context
When more than one join path is possible, context resolves which join path to take Context groups a set of tables in to one star schema.
Basically context will resolve a issue of having 2 universes
When there are multiple fact tables in a star schema surrounded by dimensional tables with one to many relational ship between the dimensional table and the fact table then loop is formed, then context can be used to fix this loop issue
Set the cardinalities first
Detect context -> Add the context -> Rename the context if needed
When more than one join path is possible, context resolves which join path to take Context groups a set of tables in to one star schema.
Basically context will resolve a issue of having 2 universes
When there are multiple fact tables in a star schema surrounded by dimensional tables with one to many relational ship between the dimensional table and the fact table then loop is formed, then context can be used to fix this loop issue
Set the cardinalities first
Detect context -> Add the context -> Rename the context if needed
Loop:
Loop:
A loop is said to exist when there is more than one “path” of joins between two tables.
If a loop exists between two tables, BusinessObjects will not be able to generate the SQL for a query against the tables; it does not know which “path” to choose
A common type of join path that returns too few rows is called loop (Joins form multiple paths between lookup tables)
Tables depending upon many tables
Dimensional table that depends upon a lookup table forms a loop and in this case we can’t get the expected output (few rows will be returned). Intersection.
Loops problem can be resolved using Aliases, contexts and detecting cardinalities
alias represents the table in a different context.
Loop problem can be resolved by removing a Join
Loop is a Multiple paths between the tables selected in queries. Or you can say loop is a closed path structure.
Loops can be resolved by…
ALIASES Alias - Same as the namesake in SQL.Exact duplicate of the original table.A different name “tricks” the SQL query to accept that you are using 2 different tables.
CONTEXTS• Rule which helps BO decide which of the 2 paths to choose in a loop.
BO prompts the user to indicate the correct perspective (relevant path) for the query.
When to AliasA loop with a single lookup table should be resolved by an aliasA lookup table can be identified by its cardinality A lookup table only has the ‘one’ end of joins attached to it
A loop is said to exist when there is more than one “path” of joins between two tables.
If a loop exists between two tables, BusinessObjects will not be able to generate the SQL for a query against the tables; it does not know which “path” to choose
A common type of join path that returns too few rows is called loop (Joins form multiple paths between lookup tables)
Tables depending upon many tables
Dimensional table that depends upon a lookup table forms a loop and in this case we can’t get the expected output (few rows will be returned). Intersection.
Loops problem can be resolved using Aliases, contexts and detecting cardinalities
alias represents the table in a different context.
Loop problem can be resolved by removing a Join
Loop is a Multiple paths between the tables selected in queries. Or you can say loop is a closed path structure.
Loops can be resolved by…
ALIASES Alias - Same as the namesake in SQL.Exact duplicate of the original table.A different name “tricks” the SQL query to accept that you are using 2 different tables.
CONTEXTS• Rule which helps BO decide which of the 2 paths to choose in a loop.
BO prompts the user to indicate the correct perspective (relevant path) for the query.
When to AliasA loop with a single lookup table should be resolved by an aliasA lookup table can be identified by its cardinality A lookup table only has the ‘one’ end of joins attached to it
Linked Universe
Linked Universe
The Data provided is from two different data providers then we link those two universe , such type of universe is called Linked Universe
Disadvantages:
- more complex deployment (promoting) from DEV --> TEST --> PROD
- Depending on your BusinessObjects version, you might loose LOVs & universe contexts in your derived universe and will have to re-create them
- Higher risk of corrupted universes (so makes sure you keep valid backups!)
Advantages:
- Use linked universes/kernel universe as building blocks for a Universe based Enterprise Bus structure (similar to conformed dimensions in a data warehouse).
BO Hintz Old
Class Group of individual Objects
Object refer to column of data
Universe Designer table maps to form fields to object in the universe
Joins more than one table in a report
Context resolves which join path
Aliases resolve the loops
Measure aggregate form
Dimension textual information
LOV associated with an object in the universe
Advanced objects SQL editor
Prompt interactive objects
Cascading Prompts means one prompt depends on another prompt..
Alters type of formatting
Break Table into multiple pieces
Row level security - table mappings to provide another way to implement
Object level security -
Private controlled Restricted Public Confidential
Type of provides –
Free Hand SQL Personal Data files Stored procedures VB Macros OLAP
Date Formula- = Format Date ((ToDate,"YYYY-MM-DD"),"DD-MM-YYYY")
Users-
General Supervisor Supervisor Designer Supervisor Designer User Versatile user
BCA Scheduling the reports - Hourly /Daily / Weekly / Monthly
General Actions Categories Scheduling Distribution
Send to BCA –
Which Server / Action / Locate Destination /Task scheduling /Distribution
Eport as-
HTML File / Report(BO) / Via BO / PDF / Excel
Repository
Universe Design Quick Design Wizard Universe Name must be 8 characters
Definition /Summary /Strategies/Control/SQL/Links / Parameter
Definition DSN, Personal / Shared / Secured
Summary Table / Join / Aliases / Conditions (Predefined)
Strategies Objects/Joins/Tables (select from drop down list)
Control Limit-Size/Execution/Text Object Size
SQL Query/Cartesian/Multiple points
Link Universe
Parameter Database SQL Parameters Parameters and property
Universe Customization
Universe Pane Edit Properties (Definition Properties Advanced)
Definition
-> Name - Type Description Select Where sum
Properties
-> Qualification-Associate a List of Values (Dimension Measure Detail)
Edit Select statement of Objects…
Tables & Columns Class & Objects Operators Function
Report Creation: Report Wizard –
Data Access Specification - Universe or Others
Others
– Free Hand SQL Personal Data files Stored procedures VB Macros OLAP
Query Panel –
Right Side Class & Objects Left Side Result Objects & Conditions Run Query
Slice & Dice
- Analyzing Data / Sort information / Filtering, grouping, calculation of groups
Filter Ranking Alters SQL View Sorter Sum
Object refer to column of data
Universe Designer table maps to form fields to object in the universe
Joins more than one table in a report
Context resolves which join path
Aliases resolve the loops
Measure aggregate form
Dimension textual information
LOV associated with an object in the universe
Advanced objects SQL editor
Prompt interactive objects
Cascading Prompts means one prompt depends on another prompt..
Alters type of formatting
Break Table into multiple pieces
Row level security - table mappings to provide another way to implement
Object level security -
Private controlled Restricted Public Confidential
Type of provides –
Free Hand SQL Personal Data files Stored procedures VB Macros OLAP
Date Formula- = Format Date ((ToDate
Users-
General Supervisor Supervisor Designer Supervisor Designer User Versatile user
BCA Scheduling the reports - Hourly /Daily / Weekly / Monthly
General Actions Categories Scheduling Distribution
Send to BCA –
Which Server / Action / Locate Destination /Task scheduling /Distribution
Eport as-
HTML File / Report(BO) / Via BO / PDF / Excel
Repository
Universe Design Quick Design Wizard Universe Name must be 8 characters
Definition /Summary /Strategies/Control/SQL/Links / Parameter
Definition DSN, Personal / Shared / Secured
Summary Table / Join / Aliases / Conditions (Predefined)
Strategies Objects/Joins/Tables (select from drop down list)
Control Limit-Size/Execution/Text Object Size
SQL Query/Cartesian/Multiple points
Link Universe
Parameter Database SQL Parameters Parameters and property
Universe Customization
Universe Pane Edit Properties (Definition Properties Advanced)
Definition
-> Name - Type Description Select Where sum
Properties
-> Qualification-Associate a List of Values (Dimension Measure Detail)
Edit Select statement of Objects…
Tables & Columns Class & Objects Operators Function
Report Creation: Report Wizard –
Data Access Specification - Universe or Others
Others
– Free Hand SQL Personal Data files Stored procedures VB Macros OLAP
Query Panel –
Right Side Class & Objects Left Side Result Objects & Conditions Run Query
Slice & Dice
- Analyzing Data / Sort information / Filtering, grouping, calculation of groups
Filter Ranking Alters SQL View Sorter Sum
Subscribe to:
Posts (Atom)
