What is a Universe Overload and Connection Overload ?

building semantic layer
1

Hi All,

I have searched in the forum but could not understand.

I have come across an issue, This is the first time I am coming across these terms in XI R2 migration. Can anyone help me understand ‘Universe Overload’ means?

Please give an example if you can, because I am using Import Wizard to convert reports from old environment to new XI environment.

Thanks for the help in advance.

Ahmed

ahm100 (BOB member since 2005-05-25)

2

Overloads are group / user specific changes that are applied above and beyond the SQL generated by the universe itself. Examples would be row restrictions (if I am part of group US, always add Country = ‘US’ to my SQL, table mapping (If I am part of group US, always substitute TableB instead of TableA), and connections (if I am part of group US, connect to database B instead of database A.

Prior to XI, these types of overloads were set up using the Supervisor tool. Beginning with XI the Designer tool is used to set up the overloads, but they are not part of the universe itself. By definition, the SQL changes are “overloaded” at query runtime.

Dwayne Hoffpauir :us: (BOB member since 2002-09-19)

3

Hmmm…

Dwayne, So it means only one universe is exported to the repository, and conditions like ‘US’ is added in Supervisor Tool for a single user or a group. Is that correct ?

Moreover, depending on these conditions, the universe will generate the SQL query for the user or the group of users they belong to… right on which the conditions have been added?

Thanks for your help.

ahm100 (BOB member since 2005-05-25)

4

Yep

Yep

BR
Sebastien

5

As the security model is different from classic BO (5.1.6) to XI R2, how these universe/connection overload can be handled in R2 without migrating the security from classic. Please provide some pointers.

Our plan is to build the security in R2 from scratch, without importing the user/groups from classic BO.

Thanks,
Chandru

Chandru 901 :india: (BOB member since 2007-07-20)

6

All universe or connection overloads are now managed with the combination of Central Management Console (CMC) and Universe Designer. You set up users and groups in CMC, and then you apply the overloads within Designer. The Designer screens are very similar to those found in Supervisor in 6.x and earlier.

Dave Rathbun :us: (BOB member since 2002-06-06)

7

Right the only thing is that now overloads are oect centric. I mean you first need to create the overload and then give rights on them to groups/users.

While migrating you must recreate them!

Regards
Sebastien

8

Do you mean by this that overloads cannot be moved with the migration wizard? :? Because there is an option during the wizard steps specifically for the migration of overloads…

Dave Rathbun :us: (BOB member since 2002-06-06)

9

I’ve recently migrated all my BO 5.1.9 repository to XI version.

When you’re using Import Wizard, there is an option to migrate the “overload”.

Please see the attached screen.
universe_overload.JPG

powerpuff :brazil: (BOB member since 2007-07-24)

10

Thats true there is a option, but that is only valid if we are importing the users/groups, securtiy from the source.

If the whole security system needs to be recreated in BOEXI, then this option is of no use!

Chandru 901 :india: (BOB member since 2007-07-20)

11

Hi Dwayne,

how can we achieve this?

tik :india: (BOB member since 2004-09-01)

12

Hi like in the previous release by overloading the connection. Designer / Manage restrictions. You overload the connecton and then give right to this restriction to a group.

BR
Sebastien

13

UL means using same universe but connect to different DB /table/row based on restriction aplied to group or single user.

BOBurao (BOB member since 2005-09-20)

14

Hi All,

I too have same issue regarding restriction.
Scenario I: Restriction for Regional Heads- NEWS
Solution: Created 4 groups in CMC, and provided restriction from Universe.
Scenario II: Restriction by store level (250 stores)
Solution : Created DB table with BOUSER,Store name/No.

Scenario III: Now we have to create more reports from the same universe without any restriction for other users. For that the DB table should have 250 rows for every BOUSER.

The DB table is included in the context created for Scenario I/II. Is it possible to use another context for other report (Fact and Dimension same) excluding the DB table used for restriction.

Is there any better solution for the same?
PLease help
Thanks in Advance
Regards,
Sandeep

smandal :india: (BOB member since 2010-03-24)