Different datasource for Query Studio

[BristolSmithy]

We've got a requirement to use different log-ons for Query Studio and Report Studio users.  Was wondering if anyone knew of a way of setting up data sources in Framework Manager dynamically so that Query Studio and Report Studio use different ones?

e.g. Report Studio would use datasource: DB_RS
Query Studio would use: DB_QS

The reason for this is so that we can force the DB2 workload manager to keep Query Studio queries in a seperate resource pool so that that they don't slow down pur report studio reports.

[Lynn]

I have used parameter maps to dynamically select a schema, but not sure that suits your need. Assuming you could use a macro to select the datasource, I don't know that you could tell which tool a person is using. Maybe there is a way to know what a request is coming from but I'm not familiar with it.

If there is no overlap of the capabilities (e.g., the QS users don't use RS and vice versa) and you can identify them by some group set up in your authentication source, then you could try a parameter map approach.

Attached is a document explaining what I do to dynamically select a schema name ('cuz mine differ between DEV and PROD). Similar concepts would be involved in your case, although as I said I've never tried a macro for the data source property itself...

[PRIT AMRIT]

Report Studio would use datasource: DB_RS
Query Studio would use: DB_QS

Never implemented though, instead of FM can we create say 2 different groups RS group & QS group. In cognos connection-Data Source Connections

We can associate these data sources to the respective groups?

[MFGF]

We've got a requirement to use different log-ons for Query Studio and Report Studio users.  Was wondering if anyone knew of a way of setting up data sources in Framework Manager dynamically so that Query Studio and Report Studio use different ones?

e.g. Report Studio would use datasource: DB_RS
Query Studio would use: DB_QS

The reason for this is so that we can force the DB2 workload manager to keep Query Studio queries in a seperate resource pool so that that they don't slow down pur report studio reports.

As Prit suggests, the easiest way is to define two new Groups in the Cogos namespace - one for RS users, and one for QS users.  Add the Report Studio users from your authentication source into the RS group, and the Query Studio users into the QS group.

Then go to the data source and define two connections within the one data source name.  In the properties of each connection, define security so that the QS group has access to one, and the RS group has access to the other.

Regards,

MF.