Designer XI

Designer XI
It is a meta data modeling tool which is used to create
universes.

Universe:
A universe acts as an interface between end
user and underlying database. It hides the complexities
of the database from the end user. It is one of the
metadata layers in BO XI.

Contd..
The universe is used for reporting.
A universe contains meaningful mapping of the
underlying data base. It contains classes and objects.
class:
A class is a collection of related objects.
Object:
An object maps to a database column. The end
user uses the objects to define the query while
generating the report.


Contd..
Universe (Semantic Layer)

Sales
Finance
Stock
Corporate
Database /
DW
Designer User
User
Universe Design process..

Corporate
Database /
DW
3. Design
2. User Requirements
1. Data Analysis
4. Implementation
5. Maintenance
Contd..

Connection:

A connection defines communication path to
the source of data. It contains information such as data
base name, data base user name, and password.
Types of connections..
Personal connection:
The connection information is
stored in a local desktop machine by the name pdac.lsi
There is no security as any user who is using the local
system can use the connection.
Shared connection:
The connection information is
stored in a shared network folder in a file called as
sdac.lsi
Any user can access the connection in the network. This
is not secured connection.
Personal access is stored in local system, where sdac
i.e. shared access is in network.


Contd..
Secured connection:
The connection information is
stored in the security domain of the repository. There is
security.

Note: only administrator can create a secured
connection

Schema: A schema is graphical representation of the
underlying database. It contains tables, columns, and
joins. In the universe pane we create classes and
objects.

Creating a connection..
Creating a universe..
Steps to be followed.
Understand the user requirements
Create a connection
Create a schema (import tables and define joins)
Create classes and objects
Check the integrity (nothing but passing)
Distribute the universe (sending into repository)
Contd..
Summary tab: It displays number of classes, objects,
tables, joins etc.. Used in the universe. Revision number
displays the number of times the universe has been
exported to the repository.
Strategies: Here define the join strategy
J oin strategy: It is an (built-in) script which business
objects uses to define the relationship among data.
Data base key matching: this checks two columns have
primary key and foreign key relationship
smart matching column name: it detects the joins if two
columns have the same name.
emp.loc dept.loc
Contd..
Controls tab:
This is used to control the size of the result set and
execution time for a query.

Sql tab :
This is used to define the type of query to be generated
i.e. unions, intersect, minus, and sub queries.

Links tab:
This is used to dynamically link two universes
Inserting tables..
Contd..
Extract joins with tables: If this option is selected then
joins are defined. While importing the tables, based on
join strategy.

Detect cardinalities in joins: If this is selected
cardinalities are defined for joins.

Create default classes and objects from tables: If this
is selected then business object creates one class. For
every table being imported with columns of tables as
objects and classes.
Derived tables..
Derived tables:
We can use the result column of sql
query as a table in business objects. This table is called
as derived table.
Advantages:
The sql query for the derived table is
executed by database server, by using derived table we
can improve performance of the query because joins or
aggregates are performed at the database level.
select emp.deptno,sum(emp.sal) as sumsal from emp group by
emp.deptno
Inserting derived tables..
Creating a class..
Creating a sub class..
Types of objects.
Measure/Fact:
Object for which operation takes place is called as
measure object.
It is the object which is being analyzed e.g. salary,
sales..
Dimensions:
It is the object with respect to which we perform
analysis. E.g.. employee, region, department, time etc..
Details:
They provide extra information about a dimension

Contd..
Hierarchies:
Hierarchies define the hierarchical relationship among
data.
e.g. year-quarter-month-week, country-state-city.

When we create objects in business objects we classify
them as either measure, dimension, or detail. This
information is used by business objects while creating a
cube.

A cube stores data in multi dimensional analyzed format.
Creating a dimension object..
Contd..

Key tab: Here define index awareness for the object.


Index awareness: Index awareness is the ability of the
business object to use indexes created at database level
by using this information business object generate
efficient sql. This is new in XI.

List of values used in defining filters.
How to improve performance of query?

It can be done using,

Derived tables

Index awareness
Creating a measure object..
Creating a detail object..
Types of joins..
A join defines the relationship between the data, defining
the joins is compulsory, if we dont define a join then in
the reports we get cross product.
Equi-join
Non-Equi join or theta join
Outer joins
Defining joins..

Detecting joins automatically (based on join strategy)


Manually creating joins
Cardinalities..

A cardinality defines the relative occurrence of a
relationship.


A cardinality can be one to one, many to one, one to
many, many to many.
Defining cardinalities..
Conditions..



A condition is a reusable filter definition
Hierarchies..
Hierarchies enables us to drill-up, drill-down, drill across
in a report. There are two types of hierarchies.

Custom hierarchy: This is user defined hierarchy. We
can have multiple hierarchies.

Default hierarchy: For every class which contains one
dimension object, a default hierarchy is created with the
order of objects in a class becomes the order of levels in
a hierarchy.
Creating a custom hierarchy..
Contd..
Difference between filter and prompt?

In filter the values cannot be changed at runtime. Where
as in prompt it can be done.
@functions..
@ functions: These are business objects specific
functions.
@ select: It is used to reuse an existing select clause of
an object. Its syntax is S must be capital letter.
syntax: @select (class name/object name) it is defined
in a select clause of an object.
@where: It is used to reuse an existing where clause
syntax: @where (class name/object name)
Prompt: It causes a prompt to be appear at the report
time asking the user to input a value.
Contd..
syntax: @prompt (message, type, lov, mono/multi,
free/constrained)
message: It is the text which appears in the prompt.
type: The type of the prompt, it can be
N-numeric
A-alpha numeric
D-date
list of values: The lov is a hard coded or it can be full
list of values.{10,20,30}
It cant provide whole table, it only provides one column.
Contd..
Mono: The end user can input the single value
Multi: The end user can input multiple values
Free: The user can input any value freely constrained,
can select only from the available list of values, prompts
defined in the where clause of an object.
Constrained: Select from the given list of values.

@variable: It is used to restrict the data using business
objects system variables like bo user and bo password.
Syntax: @variable (system variable)
Creating a prompt..
Checking integrity of the universe..
Loops..
Loops:
A loop forms whenever the joins in the business objects
forms the circular paths. Loops degrade the performance
and gives us wrong results.
Hence before using a universe the loops must be
resolved.
First method: check for integrity
Second method: detect loops
Loops can be resolved by using alias
Alias..
An alias is a duplicate of an original table. It contains the
same structure and same data as the original table.

An alias can be used to resolve the loops.

Alias can be created which contain less records,
because if we select with more records performance
degrades.
Creating an alias..
Automatically
Manually
Distributing universes..
Export:
The process of sending the universe from local desktop
machine to the repository is called as export.
When we export universe to repository the other user
can use it to generate the reports. The universe is saved
with an extension .unv till 6.5. In XI R2 it is also saved
with .unw. This is as internal format used by web
intelligence.
Procedure.
Contd..
Import:
The process of getting the universe from the repository is
called as import.

procedure.
Linking universes..
we can link universes dynamically, if
Both are made with the same data source

Both are exported to the same domain in the repository

The universe which is being reused is called as
master/kernel universe.

The other universe is called as derived/active universe.
In informatica it is called as mapplets