The situation:
- A company has more then 10,000 users.
- Each user can only see his own data.
- All users use a set of 20 IWR reports.
- A new user may be added or the existing user may be changed at any time.
- In order to implement security on what basically is a User level, a user class was setup for each user. This was done because filters can only be applied to user classes in a catalog.
The problem:
Whenever a new user is added or the existing user is changed, that user must wait for the nightly process to update catalogs. It can not be done in real time because a new user class must be added to the catalog. This means shutting down IWR and changing and republishing .IMR files.
The question.
- How to set up security to get around this situation?
- The purpose is to avoid changing catalogs in order to add or edit user's data access privileges.
- The ultimate goal is to be able to refresh Cognos security with out impacting the user's ability to use reports.
Thanks in advance for your help.
Dima.
- A company has more then 10,000 users.
- Each user can only see his own data.
- All users use a set of 20 IWR reports.
- A new user may be added or the existing user may be changed at any time.
- In order to implement security on what basically is a User level, a user class was setup for each user. This was done because filters can only be applied to user classes in a catalog.
The problem:
Whenever a new user is added or the existing user is changed, that user must wait for the nightly process to update catalogs. It can not be done in real time because a new user class must be added to the catalog. This means shutting down IWR and changing and republishing .IMR files.
The question.
- How to set up security to get around this situation?
- The purpose is to avoid changing catalogs in order to add or edit user's data access privileges.
- The ultimate goal is to be able to refresh Cognos security with out impacting the user's ability to use reports.
Thanks in advance for your help.
Dima.