P. 1
Business Objects Best Practices and Lessons Learnt

Business Objects Best Practices and Lessons Learnt

|Views: 43|Likes:
Published by sanj80

More info:

Published by: sanj80 on Aug 27, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less

09/06/2014

pdf

text

original

Business Objects Best Practices and Lessons Learnt

V1.0

Business Objects Universe Design Best practices

DOCUMENT REVISION LIST

Client: Project: Document Name: Business Objects Universe Design Best practices Release Notice Reference (for release): Rev . No. Revision Date Revision Description Page No. Prev Page No. Action Taken Addend a/New Page Release Notice Reference

Page 2 of 30

Business Objects Universe Design Best practices

Table of Contents
1 1.1 1.2 1.3 1.4 1.5 Universe Design Best Practices ........................................................................................................... 5 Introduction ...................................................................................................................................... 5 Universe Design and Development ................................................................................................. 5 Universe Design ............................................................................................................................... 5 General Universe Development Best Practices ............................................................................... 6 Some Real time Best Practices Solutions........................................................................................ 8 1.5.1 1.5.2 Define default value „ALL‟ for prompts ............................................................. 8 Universe Documentation ........................................................................... 11

References .................................................................................................................................................. 12 2 2.1 2.2 2.3 2.4 Business Objects Report Development Best Practices ..................................................................... 13 Introduction .................................................................................................................................... 13 Desktop Intelligence Documents ................................................................................................... 13 WebIntelligence Documents .......................................................................................................... 14 Some real time Best Practices Solutions ....................................................................................... 14 2.4.1 2.4.2 3 3.1 3.2 Methods to getting Desktop Intelligence data in Excel sheet ................................. 14 Incorporating an Image as a report object ....................................................... 15

Business Objects Design and Development Lessons Learnt ............................................................ 16 Introduction .................................................................................................................................... 16 Lessons Learnt in Reporting .......................................................................................................... 17 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 Chart ................................................................................................... 17 Drill ..................................................................................................... 17 Data source........................................................................................... 17 Report ................................................................................................. 17 Formatting ............................................................................................ 17 Functions ............................................................................................. 17 Report layout and print ............................................................................. 18 Templates............................................................................................. 18 Scheduling ............................................................................................ 18 Report view ........................................................................................... 18 Universe Changes ................................................................................... 18 Images ................................................................................................ 18 Hyperlinks............................................................................................. 18 Dynamic Prompts .................................................................................... 19 Restoration of a Universe Deleted From CMS .................................................. 19 Ensuring that client-server communication in BO is secured ................................. 19

3.3

Lessons Learnt in Universe Design ............................................................................................... 19 3.3.1 3.3.2

3.4

Lessons Learnt with Security Implementation ............................................................................... 19 3.4.1

4 4.1 4.2

Business Objects Installation, Configuration and Deployment Best Practices .................................. 20 Introduction .................................................................................................................................... 20 Back Up and Recovery Best Practices .......................................................................................... 20 Page 3 of 30

..........................................................2..............6 5......... 20 Enterprise Content Back up compared to Server Back up ........................................Business Objects Universe Design Best practices Back Up and Recovery Process Concept ..................................................................................2... 23 4..................................................... 21 Business Objects Content to Back up .....................................8 References ......... 25 Optimizing Document Design ...........................................................2..2.............2....6 4........... 24 5 5.. 25 Introduction ...................................................... 28 General Server Tuning ...............................4 5..............................1 4.........................................2.............................. 26 Improving Overall Document Computation Time ..................3 5............................ 27 Network and System Configuration ...............................2....1 5............ 29 Web Servers ............................................ 20 Incremental Back up compared to Full Back up ...................................... 29 Configuring the Cluster Modules .......................4 4......................................................................................................................................................................... 30 References ................................. 30 Page 4 of 30 ..5 5...................................2 5.......7 4...................1 5.............................................. 20 The Importance of a Proper Back up Sequence ....2 4............2 Business Objects Performance Optimization Best Practices .......................................................................................... 25 5..2.......................... 25 WebIntelligence Documents ...................................................................................................................................................................................................................7 Desktop Intelligence Documents ............... 21 High-Level Sequence of Back up Events ............ 23 High-Level Sequence of Recovery Events ..................2.....3 4.................................................................... 21 Cold Back up compared to Warm Back up .....5 4..................2......................................................................................................

This feedback loop is critical and will result in a more effective universe that will ultimately facilitate ad-hoc queries. During the Build phase. provide feedback. A universe is a businessoriented mapping of the data structure found in databases: tables.    Page 5 of 30 .Business Objects Universe Design Best practices 1 Universe Design Best Practices 1. Insert universe tables one at a time. understanding how each table relates to rest of the universe. joins. etc.2 Universe Design and Development The following is a general workflow for universe design:         Identify reporting requirements. Identify the primary and foreign keys of that schema. which uses a group of pilot users to test the universes. use the iterative process known as Rapid Application Development (RAD). or group of users. universes enable end users to build queries from which they can generate reports and perform analysis. Specify cardinalities manually as opposed to using the Detect Cardinalities feature in Designer. provide feedback. columns. Ensure that the data and structure of that schema is stable and not likely to change dramatically during development without warning. not in bulk. A few real time best practices solutions are also incorporated. system. Keep the universe business-focused. BusinessObjects development is centered on the development of universes. Knowledge of primary and foreign keys will assist in cardinality decision. Test the universe by building queries in Desktop Intelligence Add any other elements to universe such as predefined conditions. etc. Insert joins based on primary and foreign keys. Build universes by referring to existing company documents. Build relevant objects. because this feature relies on the structure and content of the database. In the BusinessObjects end user modules (this includes WebIntelligence). Decide on cardinalities of joins. especially in naming objects (this ensures the terminology is correct). Identify the database schema relevant to the universe you are creating. 1. hierarchies    1. Ensure there is representative data in that schema.3 Universe Design Follow the general workflow and the following tips to design an effective universe that meets end users‟ needs:  Involve users at every step of the universe design and production process.1 Introduction This document serves to illustrate the best practices that could be kept in mind while creating new or modifying existing BusinessObjects universes. for example when naming objects and classes. It can represent any specific application. Build universes by starting with user requirements. test modifications.

4 General Universe Development Best Practices Take user requirements at face value. Use this latter description to represent a business description of the universe's purpose. set the following parameters:                Page 6 of 30 . review of object definitions for syntactic accuracy. For example. divide it into multiple universes. ranks and alerters quicker. Fewer rows will be returned from the database thus making reports smaller and the calculation of their variables. In Designer. coordinate their efforts to avoid development on a universe that is out of date. Use the Tools > Detect Contexts feature of Designer to manage your contexts. This feature will not prevent someone from importing the universe and making changes. Always arrange tables logically in the structure window.39 MB. remaining in business terms.e. remember that the Lock universes on import feature will only prevent people from exporting over the universe in the repository. Basic rules of thumb:  Do not normalize. After the Build Phase. such as on dates and measure objects. i. When several developers are working on one universe. ensure an adequate Quality Control phase to verify the universes for technical accuracy (adherence to standards. Use the comments text box (File > Parameters > Summary > Comments) to record the status and changes of a universe for other developers. if the universe is 1. Do all aggregations on the server side instead of in the document (this can result in huge saving of time). Database designers apply a series of rules to eliminate redundancy of information in a database. If the universe is bigger than 1MB. Define aggregate SQL functions on universe measures. When you select File > Open. although they will not be able to export those changes back to the repository until the lock has been removed. then it uses 1. Base lists of values on lookup tables. which speeds up query time by using special tables containing precalculated data. to avoid cardinality warning messages. Remove unnecessary lists of values. under File > Parameters > SQL. having the same piece of data stored in more than one place. If you change a universe name.5MB RAM. even for self joins. whereas the description text (shown on the Definition tab) is visible to end users when they select an available universe. you load the universe into RAM.Business Objects Universe Design Best practices          Specify standards for: Universe names: always carefully choose the universe name. Always check integrity. Therefore if several developers have the ability to import and export the same universe. Always detect loops and contexts. Use Multi-Dimensional Modeling instead. you will have to re-point all documents created in that universe to the new name. This text is only visible in DESIGNER. Lay out your structure window with cardinalities facing the same direction. as renaming a production universe is not recommended. This helps you identify and visualize the contexts. Use aggregate awareness. validation of joins). Always define cardinality. This could have had an impact on the RAM available to your system. Object definition guidelines Simple object names Complex object names Aggregate object names Class names Alias names Help text 1.

Universes should not allow Cartesian Products since they are a symptom of incomplete joins and will affect performance and accuracy of query results. Page 7 of 30 .Business Objects Universe Design Best practices   Set Cartesian products to Prevent. although you may choose to enable this option during development since it may solve some fan trap situations. Select the multiple path options as shown below. Multiple SQL statements for each measure can negatively impact performance.

sometimes they need to view the result for ALL country. Since BO definitely needs any text as input for prompt.5 Some Real time Best Practices Solutions 1. For ex: In Prompt for selecting particular country. will generate the report without any restriction by the prompt value. Just by selecting the string (ALL) as a default value for the prompt. Step 1: Create one object as below: Object name. so that it will result (ALL) for UNION in LOV object) See the below Screenshots for reference Page 8 of 30 . one of the most expecting requirements from the users is the ability to select a default value for Prompts. such that final LOV for error code will have the (ALL) text also.Business Objects Universe Design Best practices 1.LOV with ALL option Select clause.<ALL> Associate any table  Click the icon “Tables” to associate any table to this object  It is better to define the object on any reference table to obtain good performance. so we need to substitute any default text like ALL Solution We have to edit the LOV object and make one UNION with the new default ALL object and also define prompt accordingly. Implementing method: Below are the steps to include (ALL) in the list of values for an object “Error code”. which will bring all the records without restriction of the prompt value.5. (Make sure that the reference table should have at least one record at any point of time.1 Define default value ‘ALL’ for prompts Problem: For every BO report with Prompts and LOV.

Business Objects Universe Design Best practices Sample tables Page 9 of 30 .

g.ERROR_CD FROM ref_customer_score_errors UNION SELECT DISTINCT '(ALL)' FROM ref_customer_score_error_log This SQL will give us the LOV with ALL.Business Objects Universe Design Best practices Step 2: Select the object (for e. the SQL will be as below SELECT DISTINCT ref_customer_score_errors.: Error code) we need to provide as LOV Go to object properties-EDIT Now if you see the Error code object in the SQL window.ERROR_CD FROM ref_customer_score_errors Step3: Click the UNION icon (Combine Queries) in SQL window and choose the new object „LOV with ALL option ' in second part of UNION Now your SQL will be as shown below: SELECT DISTINCT ref_customer_score_errors. Page 10 of 30 . while clicking the values button during refreshing the report having prompts.

2 Universe Documentation Problem: Documenting the Universe details in text format. Now this report can be used to extract them directly from the repository. (ALL) will be listed first in order. The reason behind the usage of „(„ as suffix and prefix for ALL is .ERROR_CD = @ Prompt („Enter the Error code [or (ALL) for default]‟.0\Universe ( or your default universe location) Open it in the Designer and change the Owner name of all the tables to you repository name Create the report in BO with required information and refresh it. MONO.‟A‟. which can be used to simplify your task for creating the 'Universe/report handover document'. You can generate different reports as per your need from this universe. This is an ad hoc universe. This universe has every detail you would need from your universe for documentation. This will simplify loads of your documentation work. ALL.‟A‟. You are done.e. FREE) Advantages 1) We can achieve the result for all relevant inputs 2) In order to change anything in the LOV or removing the database prefix we can do it in a single object 3) Easy to maintain the LOV for larger numbers of objects. from Universe to excel sheet Solution Here comes a report. Note: The default value can be any text i. SQL. Conditions etc. Assign the particular available Universe name in repository as filter. Since we used to manually copy and paste each object's Description.MONO.‟error code‟. „Error code‟. such that it‟s easy to choose 1. So it‟s very difficult to document universe in object by object level.FREE) OR „(ALL)‟ = @ Prompt („Enter the Error code [or (ALL) for default]‟. Page 11 of 30 .Business Objects Universe Design Best practices Step4: Create one condition object having prompt for Error code as: ref_customer_score_errors. while listing in LOV. Detach the following universe to c:\Program Files\BO51\BusinessObjects 5.. In Earlier version of Business objects saving the Universe in text format is not possible directly. A report with all the required information like object definitions and conditions will be generated. Joins. (ALL) etc such that the prompt should also changed accordingly.5.

Business Objects Universe Design Best practices References  Universe Design Guidelines Document Page 12 of 30 .

The more data providers need be synchronized. Since Desktop Intelligence retrieves data for each data provider.         Page 13 of 30 . Calculations (variables and formulas) created at the document level are performed upon the opening of the report by the BusinessObjects process (busobj on Windows and bolightsvr on UNIX). create a “base” data provider that contains the data used by all the reports. and revenue by country. Instead of creating a data provider for each report you create a data provider containing the Revenue.Business Objects Universe Design Best practices 2 Business Practices 2. Example: Create reports showing revenue by country and resort.2 Desktop Intelligence Documents The following tips are specific to Desktop Intelligence documents:  When creating full-client Desktop Intelligence documents.1 Introduction Objects Report Development Best This document serves to illustrate the best practices that could be kept in mind while creating reports in either Desktop Intelligence or Web Intelligence reports. Instead. it is more efficient to retrieve data once and distribute it to several reports than to retrieve the same data several times. Create Summary / Detail documents in Desktop Intelligence using View > Outline. This method works well with universes built on transaction databases where performance is an issue. This allows you to fold and unfold the sections and/or data that correspond to a break in the current block. Less data is therefore transferred to the client browser. Each data provider requires a separate connection to the database. It‟s better to create a single document with multiple report tabs rather than separate queries for separate documents. the more machine resources are required by the busobj /bolightsvr to accomplish this task. You can create different Desktop Intelligence reports by adding more tabs that represent the data in numerous ways or use filters to display different values for a dimension for each report tab. In this example the Revenue and Country objects are common to both reports. You can use the Query Panel to modify a data provider by selecting: Data > Edit Data Provider. so that the PDF/HTML is only generated for the tabs that the user requests. 2. and the greater the impact on performance when the report is opened or refreshed. The more variables and formulas created at the document level. A few real time best practices solutions are also incorporated. do not create a separate data provider for each report. the heavier the load on system resources. as this will result in more efficient processing for an On-Line Transaction Processing (OLTP) system. If you have multiple reports on separate report tabs and these reports draw their data from the same source. reduce the number of calculations in a document to the required minimum (including the count calculation). This opens up very quickly even if the tabs have to be generated. Limit data providers in the creation of a Desktop Intelligence documents. have the first tab be cover sheet containing information about the document. A busobj /bolightsvr process synchronizes all the data from each provider. With Desktop Intelligence documents. Break up large Desktop Intelligence documents into separate report tabs. Country. and Resort objects and use these objects in both reports.

Page 14 of 30 .txt file. This may help some performance issues. When creating Web Intelligence documents. no export of graphs 2. In Excel: Open created HTML file. Consider the number of users that request this particular document. and not a concrete limit. 2. Large Web Intelligence documents have an especially negative impact in extranet and WAN deployments. filters. In Desktop Intelligence: Edit-> Copy All: in Excel: Paste Special -> text Advantage: Retains sections. filters.txt. So even though they can able to view or refresh the data using BusinessObjects. In Excel: Open created . groupings) and formula/variable results. as users will be able to see the first page of the document before the server can download the other pages. Solution: Replicating the same formatting of BO to Excel is difficult in earlier version like 5. Avoid designing 600-page long Web Intelligence documents! This is a guideline.also there are different methods to do the same. In Desktop Intelligence: Save As . the fewer clients response time is affected by the network.1. formula/variable results Disadvantage: Colours are lost.1 Methods to getting Desktop Intelligence data in Excel sheet Problem: Before implementing BusinessObjects. Beyond the document processing stage.    2. Disadvantage: Loses colours and graphs. This allows you to cut your document page by page. use the Row Count per Page option in the Web Panel.3 WebIntelligence Documents The following tips are specific to thin-client (Web Intelligence) documents:  Avoid calculating sums and percentages in Web Intelligence documents encompassing several thousand rows. Methods of getting BusinessObjects data into Excel with pros and cons 1.Business Objects Universe Design Best practices  Choose the presentation format for Desktop Intelligence documents according to their intended distribution media. The smaller the web pages transferred to the client. most of the users are familiar with Microsoft Excel. consider the load on your network as the client requests such a document. Use drill functionality or the Web Intelligence hyperlink index for section navigating. groupings. two-step procedure. they like to have the same data in Excel for their familiar data manipulation. In Desktop Intelligence Data -> View Data -> Results tab: Export -> File Format: MS Excel Advantage: Directly creates an excel file. but now in the latest version there is an option to save directly as Excel . In Desktop Intelligence: Save as HTML.4. which are network-bound. exports whole data cube Disadvantage: Loses all formatting and calculations 3. but considers the impact on the server of processing such a document.4 Some real time Best Practices Solutions 2. need to re-do for each report in the Desktop Intelligence document 4. Advantage: Retains formatting (sections. The count calculation has a negative impact on performance on very long documents. All of these performance factors contribute to the response time of large and complex documents.

4. after exporting to repository and then while viewed by various users. In Desktop Intelligence: Click exactly on border of a table -> Copy. There is another best way to do this Solution: Normal procedure to include a picture was Insert->Picture then drag the pointer in report followed by selecting the required picture available in a particular location/path.for Advanced Users 8. creates the HTML files in a sub-folder structure 5.Business Objects Universe Design Best practices Advantage: Only method that retains all formatting and calculations incl. Use the 'Copy to DDE' option (Data-> View Data -> results Tab -> Export. Disadvantage: Two-step procedure. 2. ( Disadvantage: not very reliable). 6. so that anybody who is having access to server can able to view the corporate logo in business objects report. graphs. 7. The most effective way to include corporate logo is  Open the Corporate logo in MS-Paint  Select All by pressing Ctrl + A and copy  In Desktop Intelligence report insert a free standing cell and paste the picture Advantages The Logo/Picture can be viewed anywhere by any user in remote location without having the image file in Server /local system Page 15 of 30 . In Desktop Intelligence: Use the available Desktop Intelligence _VBA methods DP. it‟s not visible to them. in Excel: Paste. in Excel: Paste Special -> Paste Link)) to dynamically update the data cube results in Excel 9.ConvertTo() or Report. Outcome: Copies the whole report as picture into Excel / PowerPoint etc. that is because the image file is missing in the local system /server.2 Incorporating an Image as a report object Problem: Corporate Logo is not appearing in Desktop Intelligence report while accessing from remote location A report will mostly have the respective corporate logo in header. so that image file also need to be exported to the server . In Excel: Paste Special ->Picture (Enhanced Metafile).ExportAs() . Embed a Desktop Intelligence report by calling it in Excel via Insert-> Object -> Create from File (Mark Option 'Link to file'). Outcome: Pastes static image file of that particular table into Excel / PowerPoint etc. saves all reports in the Desktop Intelligence document in one step. In Desktop Intelligence: Edit -> Copy All.

Some points listed here might be well known to the developers.5.Business Objects Universe Design Best practices 3 Business Objects Design and Development Lessons Learnt 3. mainly the challenges in developing a reporting solution using WebIntelligence 6.5.1 Introduction The purpose of this document is to share the experience. in its new. This document is more of a review of this product in comparison with its thick client equivalent. only when involved in a development project. is definitely more than WebI 2. enhanced version 6. But many of them. WebI. one would come to know. Page 16 of 30 .x.

then a newly added column will inherit the “auto fit” property. a report pointing to universe „X‟ cannot be pointed to universe „Y‟ as we do with full client reports. it cannot use data from personal data files. Page 17 of 30 .2. whereas it is “.  Where condition cannot use an object as the Right Hand Side operand. they disappear when the drill is removed. 3.  Post fetch drill cannot be stopped if users drill further below / above the level set in scope of analysis.2.e. and cannot be used for any business need.2.Business Objects Universe Design Best practices 3.” in Full client.2. Workaround is to create rank objects in the universe and use in reports.2 Drill  Synchronized drilling across multiple blocks in the same report r equires “Option->View->Drill Options-> Synchronize drill on report blocks” to be checked. If drill is enabled again. the parameter delimiter for built in functions is “. i.  Custom sort is not possible  If existing columns in a report have “auto fit” property.) In results mode any format change requires server-client interactions and consumes more time. synchronized drilling is possible. 3.1 Chart  3D chart option is very poor.2.3 Data source  WebI requires the data source to be a universe.2.. Unlike Full client.”.  If columns are added in drill mode.  Column headers won‟t change with the drill level. So all changes in the report blocks must be done with drill off‟.5 Formatting  Copy between two tabs is not possible  Formatting changes should be done in “structure” mode (To obtain this mode click “view structure” button in the tool bar. If the same data provider is used for multiple reports in the same tab of the document.4 Report  Macros cannot be used 3. Or we can say. Hence filtering the zero values in a chart/table is not possible unless it is done at query level. Linking feature is not available  Queries cannot be overridden. the columns won‟t reappear. if you change the universe name. the report will be irrecoverably lost as there is not a way to change the universe name in the report manually.2 Lessons Learnt in Reporting 3.6 Functions  Ranking is not possible. 3.  In WebI.  Set operations cannot be performed between two queries. 3.  Source universe cannot be changed in the same way as that of Full client.  Queries cannot be synchronized i.  Size of the chart cannot be auto fit  Filters can be applied only for dimensions and not for metrics.e. Synchronized drilling is not possible in full client.

This may also depend on hardware capacity) 3.2. Page 18 of 30 . (It would mean that for every universe. it is not possible to archive reports with their title reflecting the reporting period.2. Values alone can be passed as parameters to the target reports. Also the user has to log off from the current session and log back in to see the changes.7 Report layout and print  If the page lay out is set as landscape/portrait. Workaround is to create a report with common standards and styles from the universe. the “Read content as” checkbox under Rep ort properties->cell properties->Display needs to be checked.2. 3. But in WebI. For WebI to read the cell content as HTML. Users have to sort it by date to pick up archived reports of a specific period. we must place the image files in WebI server or any other server that can talk to WebI server to show them on reports (This might be required for displaying logo) 3.11 Universe Changes  Every time when a universe is changed. and be saved or sent to inbox. 3. as they do not have document ids. This can be used only for reports developed using the same universe. which can be used as a base for creating reports further. it alters only the page view.12 Images  Images can be a part of the report in Full client.2.13 Hyperlinks  Hyperlinks are used to connect source (parent) reports to target (child) reports. Reports can be scheduled with “non overwrite” mod e. which can be modified for actual development) 3.9 Scheduling  As Macros cannot be used. create one standard dummy report. The parent report cannot call the documents stored in personal docs. it may take a while to see the changes across multiple servers (propagation delay). 3. it requires us to manually set it in the printer properties to be landscape/portrait again.2.2.8 Templates  Report Templates cannot be used to develop reports.Business Objects Universe Design Best practices 3.2. our experience is that cannot handle more than 100 pages. When it goes to print.10 Report view  Draft mode to see the report without page breaks cannot handle very large reports running for several pages (though data decides the page limit.

 Never delete a universe directly from CMC.1 Dynamic Prompts Dynamic Prompts are developed such that key word in prompt is „MaxDate‟ and the maximum value will be taken from LOV. This security certificate can be generated or imported from a trusted certification authority.unv file. To generate the certificate. the physical path of the universe on the BO server was found. in the list of universes. Because of this action the universe couldn‟t be opened and all reports made using this universe couldn‟t be run.unv file while over writing it. 3. Following this path on server the existing . all communications can be through “https” instead of “http”. environment is secured i.  Create a BIAR file of the universes & reports daily as a back up. every time Default value is „MaxDate‟ but the value differs based on the refreshed LOV.1 Ensuring that client-server communication in BO is secured Whenever a request from a client browser hits the BO server.4 Lessons Learnt with Security Implementation 3.e. Page 19 of 30 . This process creates a .3.e.xml file). a security certificate needs to be embedded in the Web service so that it will be invoked every time a request hits the web server. This helps to get the refreshed report avoiding the user to refresh again hence reduces the number of hits to the database and thus performance increases. by editing the server. 3.3. Then from CMC.3 Lessons Learnt in Universe Design 3. So the same was later deleted from the CMS through the CMC. Next.4.Business Objects Universe Design Best practices 3. So to counter this problem an empty universe was created with exactly the same name as that of the universe which was previously deleted and the same was exported.  So the lessons learnt from this were:  Always lock a universe while importing.unv file was replaced with the latest version of . we used the “keytool” utility provided with Java. the Web application server decodes the request and forwards it to appropriate BO service. Hence while scheduling the report. we provided the path to this file in the Tomcat configuration properties (i.  Always maintain a back up of . This means in order to have secure communication. Once this is done & Tomcat restarts successfully.2 Restoration of a Universe Deleted From CMS A newer version of a universe was accidentally overwritten by an older version in the CMS.keystore file (contains a certificate-key pair) which will be used for authentication.

The plan aims to minimize the effects of the disaster on the daily operations so that the organization is able to maintain or quickly resume mission-critical functions. but these can be resolved by performing a re-installation of operating systems or Enterprise.3 Enterprise Content Back up compared to Server Back up Enterprise content back up focuses on the essential components of Enterprise only. Enterprise content back up does not insure the operating system or any applications. to involve an implementation of redundant servers in a back up system. Enterprise content back ups are relatively fast and inexpensive to capture. and minimize the delay before resumption of normal business operations.2 The Importance of a Proper Back up Sequence Without backing up the Enterprise system databases and the file repository. With an Enterprise content back up.1 Back Up and Recovery Process Concept A back up and recovery plan consists of precautions to be taken in the event of a full system failure due to a natural disaster or a catastrophic event. This document mostly focuses on a Enterprise content back up strategy. In the event that the primary system goes down. It is recommended. including the Enterprise executables and DLLs.2. 4.2 Back Up and Recovery Best Practices 4. and that is the most important thing. optimize data recovery. which mirrors the primary system. no restoration of the environment is possible. Content back up also will not insure one against corrupted or deleted Enterprise application DLLs/EXEs or other operating system problems.Business Objects Universe Design Best practices 4 Business Objects Installation. Good back up integrity requires shutting down certain BusinessObjects services prior to capturing the back up. It is a best practice to back up BusinessObjects servers on a daily basis.1 Introduction The purpose of this document is to outline recommended best practices during the installation. These procedures are used to reduce data loss. the back up system is still available and becomes the operational system. Configuration and Deployment Best Practices 4. configuration and deployment of Business Objects XI Release 2 server and/or desktop products. Methods to back up and recover data for key BusinessObjects XI Release 2 system components are extensively illustrated. as part of a BusinessObjects Enterprise disaster recovery plan. Under certain conditions. Page 20 of 30 . failure to follow a proper service shut down sequence before backing up could result in one or both of the following consequences: • False sense of security in the quality/integrity of the back up • Inability to fully recover BusinessObjects if the back up is of poor integrity 4.2. however. 4. one can recover a BusinessObjects environment from scratch on a different hardware environment if necessary. it does insure all of the intellectual content that is created and customized by users of the Enterprise system.2.

The frequency of back ups may be revised based on an acceptable amount of time for recovery to satisfy your company‟s requirement. this is a full back up that captures every byte on every local hard disk in a server. It is recommended to back up the CMS system database and PM repository once daily with incremental back ups and a full back up only once per week. Typically. The UNIX distribution of Enterprise includes the ccm. 4. 4. but can also be slow and expensive to capture and later restore.2. A warm back up usually allows applications and users to continue to maintain connections to the database and Enterprise XI while the back up occurs. furthermore.sh script to assist in the start.6. but they are also the slowest and most expensive to capture and maintain. Because of this. upon each subsequent back up. Incremental back ups are faster and less expensive to capture. A server back up should incorporate the same data as an Enterprise content back up. Routinely backing up all of the following content elements will enable you to recover from virtually any type of disaster (virus. only the files changed since the last back up are captured. stop and restart process. and so on). This type of back up insures the server‟s operating system as well as any applications and data stored on the server‟s local drives. Where resources allow. Full back ups are the safest and least complex type of back up to restore. 4. it is recommended that two scripts be used. a factor which must be taken into consideration when scheduling cold back ups. The Central Management Server (CMS) service must be stopped before a true cold back up of the CMS system database and File Repository Server (FRS) can occur. CMS and PM tables could be captured in an out-of-sync state.6 Business Objects Content to Back up There are several content-oriented elements that must be backed up daily in order to recover from a disaster. the FRS.2. Because of this. Thereafter. it is Page 21 of 30 . hardware failure. Stopping the CMS will prevent users from accessing the Enterprise system. but they are less robust than full back ups. natural disaster. as well as the data connection information. one to stop the relevant services and the other to restart them. 4. Because the CMS database is the heart of the environment.1 Database Back up Central Management Server System Tables This database contains all the user rights and metadata information about reports and universes. It is a valuable type of back up. These scripts can be executed before and after the database back up process begins. a situation which compromises the integrity and usefulness of the back up.Business Objects Universe Design Best practices A server back up is the deepest type of back up. Business Objects advises capturing full back ups once per week. To aid in stopping and restarting Enterprise XI services before and after a cold back up occurs.5 Cold Back up compared to Warm Back up Cold back ups are a best practice and by far the preferred type of back up to capture on a daily basis.4 Incremental Back up compared to Full Back up A full back up captures every targeted byte. incremental back ups are usually acceptable for daily back ups. a warm back up exposes the possibility that the CMS and Performance Management (PM) tables and FRS will be captured in a state of change.2.2. An incremental back up begins as a full back up.

when the CMS and FRS services are stopped. At a minimum. Auditing Tables This database contains usage statistics and auditing information for the environment. The file repository typically ranges in size from 1 GB to 100 GB depending on the size and complexity of the deployment. a back up and recovery plan should cover connectivity parameters for all known data sources. these items should be backed up daily.2 Custom Java applications/code Any programmatic customizations to InfoView or other custom user interfaces should be backed up as frequently as they change. Orphaned report pointers are those records in the CMS system database that do not point to a valid input or output file in the Enterprise Input or Output FRS. File Repository This is a standard OS file share that contains all the report templates and instances for the environment. Key Performance Indexes (KPI). the environment cannot be restored. each BusinessObjects server writes audit records to a log file local to the server. the CMS communicates with the audited servers to request copies of records from the local log files.Business Objects Universe Design Best practices absolutely critical to frequently back up this database. During active development periods. or as often as the code is modified. Since the file repository is designed to exist in synchronicity with the CMS tables. could result in poor back up integrity. Currently. Thereafter.2. Failure to capture the file repository and CMS system tables simultaneously.2. it should be backed up at exactly the same time as the CMS system tables. It should be backed up daily. making it easy to capture during a routine back up of the CMS tables. If a user were to select a report object or report instance that was orphaned. these tables will be stored in the same physical database as the CMS system tables. Without this database. In many Enterprise environments. Local audit log files When auditing servers is enabled. Only the Input and Output subfolders need to be backed up (the Temp folder can be ignored). A back up of this database is not needed to recover from a disaster because the information this database contains is the least important of all BusinessObjects components. This database should be captured at the same frequency as the CMS system database.6.3 Database Connections (ODBC DSNs) Special database connections (such as ODBC DSNs) can not be easily captured and restored via normal back up processes. Orphaned input or output files in the file repository are a benign problem compared to orphaned pointers in the CMS tables. At regular intervals. and key relationships that drive dashboards and scorecards. Because of this limitation.6. The back up and recovery process should be revised once more projects are integrated into it. it would cover: • The name of the ODBC DSN • The name of the target database Page 22 of 30 . ideally on a daily basis. an error message would occur and they would not be able to access that object or instance. metadata. they can be backed up weekly or monthly. 4. 4. This is because of the increased risk for orphaned report objects or report pointers in the CMS system database if a database restore becomes necessary. Performance Management System Tables This database stores metrics. These log files need to be backed up daily. Business Objects Integrated System consists only of Port Director Dashboards and does not contain any custom code.

Business Objects Universe Design Best practices • The type of target database in Oracle • The user ID and password used to connect to the database • A listing of the reports that rely on the data source • Any other pertinent information that an administrator can use to recreate the data source manually if necessary 4. Prevents users from accessing Enterprise. 4.7 High-Level Sequence of Back up Events 1.2. Releases the CMS‟ connection to the system database. Individual files from a specific date can be restored from the file system back up tapes. This action: i. 2. Page 23 of 30 .8. install the OS on the same disk as before.4 Query Data Source – Data Warehouse Although technically not Enterprise components. If recovering only Enterprise content. conduct the installations as above and use the Business Objects Import Wizard to import the required information from one Enterprise system to another.2 Web and BusinessObjects XI Release 2 Data Files 1. v. and so on until the file system is fully restored. Prevent report jobs/analytics from executing (and terminates any report jobs/analytics already in execution). iv. Assures the continued integrity of the Enterprise File Store. Restore the back up of the PM repository. Restore the Input and Output File Repositories. The Central Management Server (CMS) and all job-processing and Performance Management servers should be stopped by an automated script. After the back up is complete. the IT Administrator restarts the Enterprise services. the IT Administrator should capture the back up of the components mentioned in the Business Objects Content to Back up section. Releases Performance Management‟s connection to its tables in the CMS system database. iii. ensuring that the number and size of disk volumes are the same or larger than the previous system. If it is necessary to restore entire file systems. make sure to install Enterprise on the same drive as on the original system. 4. Install/configure the data source client software to point to the restored database and report source.1 Web and BusinessObjects XI Release 2 System Files If necessary.2. 2.2. After the Enterprise services have stopped.2.8. 4. ii. 4. all reporting databases and cubes should be backed up on a daily basis or at least as frequently as the data changes. If you must rebuild a system by starting with an empty hard drive. then recreate the partitions and volumes as they were on the damaged system.8 High-Level Sequence of Recovery Events 4.2. 3. the most recent full system back up tape should be restored first. This can be done by an automated script.6. then the second incremental back up. followed by the first incremental back up. Restore the back up of the CMS system database. 3. rebuild and restore the system. For replicating on a second server.

Business Objects Universe Design Best practices References Business Objects Document: Backup and Recovery Best Practices. Page 24 of 30 .

date/time. chart. As with universe development. 5.   5. but performance depends on your specific deployment. It is therefore important to strategically design documents with your system. Calculations (variables and formulas) created at the document level are performed upon the opening of the report by the Desktop Intelligence Page 25 of 30 . table. Restrict the amount of data returned to the client by placing conditions on query objects. and data provider names. and at every stage. block. In general. For example all inventory documents run from IN1000 to IN9999. Remove redundant or unused variables. etc.Business Objects Universe Design Best practices 5 Business Objects Performance Optimization Best Practices 5. network and system configuration and general server tuning. as often as possible. Give each data provider a meaningful. removes any confusion when relating to technical support. Define standards for document variable. Documents that take a long time to run and refresh may not be designed in an optimal manner. Whenever possible. logo. Use user prompts in standard documents to restrict data and display relevant data to individual users under a common format. network specifics. network. These variables can be drastically different between deployments. document computation time. the better. and user population specifics in mind. The following general tips are designed to guide you in creating a document design strategy appropriate to your deployment:         Documents over 200 MB will significantly impact performance. use breaks to have better control over white spaces. This makes maintenance easier. tab. Save this as the default template. A101 etc. limit document size to approximately 5 MB.2 Optimizing Document Design Dissatisfaction with the performance of a product is sometimes due to the user‟s tendency to use the product in a way for which it was not designed. The smaller. user-friendly name. available resources. column. Reports that are excessively long or complex may therefore lead to display issues such as long response time. involve end users as soon as possible. This can reduce the number of documents being developed for multiple users.1 Introduction This document serves to illustrate a few best practices that can be followed to enhance and optimize the performance of a Business Objects deployment in the aspect of document design. font and calculation formats. and as a result.2. there are no fast rules on designing documents. Give each document a unique identifier. This makes identifying the document easier for retrieval. all customer-related documents run from CU1000 to CU9999 etc. Use sections for better navigability. make its title a combination of letters and/or numbers: A100. title. Keep documents in 'sets' and reflect this in the numbering. and it avoids the possible wide-scale distribution of documents containing large and potentially irrelevant amounts of data. This will enable you to design the type of document that best needs your end users‟ information needs. Create document prototypes to demonstrate both for feedback and "educational" purposes.1 Desktop Intelligence Documents  The following tips are specific to full-client (Desktop Intelligence) documents: When creating full-client (Desktop Intelligence) documents. Produce a standard corporate document template. reduce the number of calculations in a document to the required minimum (including the count calculation). which may incorporate header/footer. For example. Keep and monitor your document size to well below this limit. This is especially valid over slower networks.

Instead. You can create different Desktop Intelligence reports by adding more tabs that represent the data in numerous ways or use filters to display different values for a dimension for each report tab. A BusObj/bolightsvr process synchronizes all the data from each provider. the more machine resources are required by the BusObj/bolightsvr to accomplish this task. Choose the presentation format for Desktop Intelligence documents according to their intended distribution media. Limit data providers in the creation of a Desktop Intelligence documents. create a “base” data provider that contains the data used by all the reports. If you have multiple reports on separate report tabs and these reports draw their data from the same source. Avoid designing 600-page long Web Intelligence documents! This is a guideline.Business Objects Universe Design Best practices             process (BusObj on Windows and bolightsvr on UNIX). Use drill functionality or the Web Intelligence hyperlink index for section navigating. the heavier the load on system resources. do not create a separate data provider f or each report. Country. have the first tab be a cover sheet containing information about the document. consider the load on your network as the client requests such a document. Large Web Intelligence documents have an especially negative impact in extranet and WAN deployments. You can use the Query Panel to modify a data provider by selecting: Data > Edit Data Provider Create Summary / Detail documents in Desktop Intelligence using View >Outline. Beyond the document processing stage. and revenue by country In this example the Revenue and Country objects are common to both reports. This allows you to fold and unfold the sections and/or data that correspond to a break in the current block. Instead of creating a data provider for each report you create a data provider containing the Revenue. Each data provider requires a separate connection to the database.  Page 26 of 30 . The more variables and formulas created at the document level. Example: Create reports showing revenue by country and resort. This method works well with universes built on transaction databases where performance is an issue. so that the PDF/HTML is only generated for the tabs that the user requests. but consider the impact on the server of processing such a document. and not a concrete limit. 5. the fewer clients response time is affected by the network. Consider the number of users that request this particular document. This opens up very quickly even if the tabs have to be generated.2 WebIntelligence Documents The following tips are specific to thin-client (Web Intelligence) documents:   Avoid calculating sums and percentages in Web Intelligence documents encompassing several thousand rows. The smaller the web pages transferred to the client. With Desktop Intelligence documents. Break up large Desktop Intelligence documents into separate report tabs. which are network-bound. it is more efficient to retrieve data once and distribute it to several reports than to retrieve the same data several times. The more data providers need be synchronized.2. It‟s better to create a single document with multiple report tabs rather than separate queries for separate documents. All of these performance factors contribute to the response time of large and complex documents. and the greater the impact on performance when the report is opened or refreshed. as this will result in more efficient processing for an On-Line Transaction Processing (OLTP) system. Less data is therefore transferred to the client browser. The count calculation has a negative impact on performance on very long documents. Since Desktop Intelligence retrieves data for each data provider. and Resort objects and use these objects in both reports.

make sure the data is purged from the cube: View > Data Manager > Results tab. In Desktop Intelligence. Page 27 of 30 . especially if the document will be refreshed on being opened in InfoView (File > Publish to Corporate Documents.Business Objects Universe Design Best practices 5. import and refresh of the document are considerably quicker. Do not store data within a full-client document. We suggest that you: Create a document per section and/or per report tab. as is the opening of the document in InfoView. This can optimize querying when Oracle is running in rule-based mode. the export. right-click on a table and use the Number of rows in table option. You can reduce the time it takes to open the Desktop Intelligence document and generate the HTML by breaking down the document into smaller documents and/or by breaking the report into separate report tabs. HTML Options button: Deselect the Store generated HTML in document option).3      Improving Overall Document Computation Time Keep the number of variables to a minimum. Avoid having a single query with multiple select statements being "joined" or "synchronized" by Desktop Intelligence. Purge As a document without data takes up less space in the repository.     Do not store HTML within a document. Purge button. especially if the document will be refreshed on open in InfoView. when you export a document to the repository. Avoid linking multiple queries into a single document. Reduce the number and/or the complexity of the formulas in your documents whenever possible. For Oracle connectivity.

Keep all system components in the same subnet and going into a dedicated switch. so applications are forced to swap to disk. Bottlenecks are caused when part of the system is not running fast enough to keep up with the demands placed on it. Under Windows 2000. preferably the same switched hub. Use optic fibre when possible. Put Web Intelligence. Any extranet server should have as few devices as possible between it and the WAN connection. This hub should be running at least 100 mbps full duplex. the repository and the corporate database on a switched hub. Use the fastest network cards and hardware possible. the repository and the corporate databases.4              Network and System Configuration Closely monitor your system for bottlenecks. Remove all unrequired protocols.Business Objects Universe Design Best practices Uncheck this 5. which can slow response The system is out of processor power The network interface is overloaded Remove as many network components in the system as possible between the Web Intelligence server. especially when performance is less than satisfactory. The most common bottlenecks occur for the following reasons: Slow disks or disk arrays aren't able to handle I/O requests quickly enough The system is starved for memory. Keep all the system components physically close to each other. select Background services in the Application response box (My Computer > Properties > Advanced > Performance Options): Page 28 of 30 . It is especially important to keep the database and the Web Intelligence server close to each other.

CPU will often be the first resource that Web Intelligence uses up. put frequently accessed files on RAID 0 or 0+1. specifically the Deployment Guide and the UNIX Performance. Use RAID disks for Storage.    Purchase machines that will allow more CPUs to be added later. Each configuration and type and conditions of usage is different. Never bind web servers to virtual IP addresses. with the operating system on its own disk (RAID 0 or 1.   5. Remember. When estimating the number of servers you need for your user population.” from Sun Performance and Tuning. Choose SCSI disks for the best I/0 performances and. but understand that these are just general guidelines. such as by binding them on different ports rather than addresses. Page 29 of 30 . that memory is not the only possible bottleneck in a deployment. you can put your web server on a Windows or a UNIX node.Business Objects Universe Design Best practices 5. You can never have too much memory on a server. Optimization and Sizing Guide in particular if you have a UNIX server. but UNIX is recommended because it has the best throughput.6 Web Servers Web servers are an element of your deployment that can be tuned relatively easily to improve performance. “The most serious bottleneck is an overloaded or slow disk (I/O). If you are deploying a cluster. Adrian Cockcroft & Richard Pettit. and the Application and Web Intelligence servers on RAID 5).5 General Server Tuning The server should be dedicated to Web Intelligence system usage. use the formulas contained in the Business Objects documentation. benchmarking and more benchmarking. you will only be able to pinpoint what your optimal configuration is by benchmarking. if using RAID arrays. You can bind web servers on the same network interface in other ways. though.

To minimize dead user sessions due to users closing the browser rather than logging out. If possible. In larger deployments. CORBA/ORB. minimize network traffic. using a Cisco Local Director or equivalent) may be the best strategy if you are concerned about system uptime. as the throughput on this server is one of the critical aspects for performance.7 Configuring the Cluster Modules General Advice        Disable logging whenever and wherever it is not absolutely necessary. failover is excellent! Multiple session managers can speed up login. Put the heavier processing load on cluster nodes. an all cluster manager deployment (therefore multiple clusters. as well as logging on the web server. This includes Web Intelligence internal and user activity traces. Note that user logging must be enabled if AUDITOR is being used. Note that this multiple cluster manager configuration is not supported for use with a single instance of AUDITOR. Use the fastest disk possible on the server running the WIStorageManager and WISessionManager. Use the WIGenerator parameter Node Load Factor to take full advantage of the capacity of each cluster machine.Business Objects Universe Design Best practices For example: webserver1 = http://ipaddress:8080 webserver2 = http://ipaddress:9090 5. References Business objects Document: BO Best Practices for Performance Tuning ========= End of Document ========= Page 30 of 30 . process thin-client documents on certain machines. You can set session timeout to 60 minutes. If every machine is a cluster manager. leaving the cluster manager freer to perform its control and management functions. and full-client documents on others. depending on the workflow. and can. and middleware. drop WIGenerator and other module timeouts to 20-30 minutes.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->