Using a different connection based on certain criteria

Question

For particular administrative needs, we managed data by projects on separate database.
Those projects data are on a particular database based on the company division and/or the country of the project.
A user may have access to two projects that are on different database.
We have 30 SqlServer 'Project' databases with the same schema, and a corporate database that contains security tables (with a Project-Database relation table).
We are presently using Webi on BO 2.0.
In order to access the right database via the Universe and Reports, we defined 30 generic users (ex: uDB1,
uDB2, uDB3, ...) and add 30 access restrictions in the Universe based on the generic user.
With a custom application and thru the API, we execute a Webi report with the generic user based on the
database name in which the real user is logged in.
That way, with the help of the access restriction in the BO universe, the data comes from the right database.
We don't let users create their own report.
Instead, we have created a template with a few fields from the universe.
Users, thru the generic user account, can execute the template, add or remove a few fields, and save as
another report name.
But with that strategy, any users that have access to the same database could modify the reports of each
other, because they all log thru the same generic account.
So we set the security in order to not let a user modify his own report.
But this is resulting in having a few iteration of the same report (Ex: Report_A_v1, Report_A_v2,
Report_A_v3,...) each time a real user wants to modify his own report.
We are in the process of moving to BO 3.1 in a few weeks.
We were told that we may be able to resolve our problem with Stored Procedure.
Instead of having generic accounts, we should be able to have real users accounts and, with security table where we store on which database is store a project, we should be able to create stored procedure dynamically to access the right database.
Has anyone faced a similar problem and found a solution ?

Answer 1

For an SQL query on a database use a View Object. First, you will need to create a new Entity object to represent each table in the database you need to use in the queries. Once you have created your view objects with their correct SQL queries, you need to specify how they are related. Example:
RootView is all elements with ParentId of null.
OtherView is all elements with ParentId not null.
RootToOtherLink is a view link which links RootView.Id to OtherView.ParentId. You can specify this in the dialog. You will want to select all accessors available to make your life easier later, but make sure to name them something you will recognize, like "RootToOtherDestination".
You will also need OtherToOther Link which links OtherView.Id to OtherView.ParentId. This starts the recursive nature of the hierarchical relationship.
Once you have this set up, you will need to create an Application Module so that you have a data control you can bind your tree to. Set up the data model in a hierarchical fashion using your link.
This will create a data control on the Data Controls pane you can drag onto your .jspx page. A menu will show up from which you can select tree component. This will take you to the tree binding dialog. Here is where all your work so far will pay off. You want to click the green plus button to add your RootView. Then, with the RootView selected you will want to hit the green plus again to select your destination accessor, such as "RootToOtherDestination" as mentioned earlier. This will show the OtherView as a child of the RootView. Finally, with OtherView selected you will want to hit the green plus again and select your other destination accessor, such as "OtherToOtherDestination". Select the attributes you want to have available to your tree at the bottom of the dialog and click ok.
Your tree will show up. If you want to customize the way it looks or especially the attributes it displays in a node, those can be edited in the <af:tree> tag on your .jspx page.