A Universe about Universes: ManagerO

 < Day Day Up > 



Prior to printed reports, one could get universe documentation only through another universe: managerO. With printed reports directly from Designer, Business Objects had intended to eliminate managerO. ManagerO is structured strictly for Oracle-based repositories, but you can modify it to work with other databases. While Oracle may be the predominant database in BusinessObjects deployments, the vendor would clearly have to update managerO for other databases if it were a more predominant offering. You’ll notice that managerO is never discussed in any documentation. However, the vendor is kind enough to still supply it via the Freeware directory on the BusinessObjects installation CD. Despite greatly improved printed reports, I still find managerO a really useful tool. It contains information not available in the printed reports. Additionally, if you wish to print information about individual objects or classes, ad hoc reporting with this universe gives you more control over the output than do the standard Designer reports.

To install managerO, copy it from the Freeware directory to your Universe folder. Launch Designer and select File | Open | managerO. Select File | Parameters to modify the default connection to point to your particular Universe Domain.

ManagerO organizes information about the universe into the following classes:

  • Universe Parameters

  • Class Details

  • Object Details

  • Condition Details

  • Universe Tables

  • Joins

  • Contexts

  • Hierarchies

If your repository is not stored in an Oracle database, you will need to modify any objects that make use of nonstandard SQL functions. For example, Object Security Access Level uses DECODE to translate the numeric settings in the repository to match the meaningful descriptions you see in Designer. To identify these objects, print the Full Description for Objects and look for SQL your database does not support.

click to expand

In Chapter 8 (Table 8-2), I warned that you must take care in renaming objects to ensure the OBJECT_ID is preserved. This is a great example of information that is accessible through managerO and not the standard Designer reports. Following are some additional objects that provide information not otherwise available through the printed reports:

  • Number of Universes

  • Number of Linked Universes

  • Universe ID

  • Version shows the revision number listed under File | Parameters | Summary

  • Linked Universe ID

  • Incompatible Tables, set through Tools | Aggregate Navigation (where there are incompatible objects)

  • Object Table Name, set through Object Properties, Tables button. While the printed reports will show the table used in the SQL SELECT or WHERE statement, it will not show tables selected that may be used to force a join (see Chapter 7).



 < Day Day Up > 



Business Objects(c) The Complete Reference
Cisco Field Manual: Catalyst Switch Configuration
ISBN: 72262656
EAN: 2147483647
Year: 2005
Pages: 206

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net