Login Restrictions For users

[teccum]

I have a requirement where the business wants to allow
only certain users to login during peak hours (between
8.00 a.m to 11.00 a.m)everyday. So I have to restrict
the login of certain users into MicroStrategy.

Do anyone have an idea of how to restrict the user
login for certain duration of the day and for all days.
How to accomplish this. Have anyone implemented this in
your organisation.

Well, I would also like to know how you handle
the MicroStrategy queries during the data loading
process. Do u bring the down I-Server while the data
is loaded into the data warehouse during the nightly
batch process.
(My idea is to try to create a script through command
manager and run it as a batch process everynight so
that it stops and restarts the server automatically.
Is this doable and if anyone have done it can you share
the script.)

kindly share your experience and ideas. Appreciate
your response.

Thanks
teccum.

 

[FLB]

I personally prefer not to stop I-Server if this is not necessary. Instead I:
- set the project in execution idle (i.e. users can do whatever they want, but the request wait in queue and do not hit the DB)
- set DB thread / priority differently early in the morning in case the ETL process is running late but we _have_ to run some report for the executive.

If you want certain groups of users to not be able to login at all, then look into creating an ESM (External Security Module). This is a piece you add to MicroStrategy Web that handles authorization (and authentication).

2 cents,
FLB

 

[teccum]

FLB,

I too do not prefer stoping the I - Server and hence, I
am currently handling the user logins restriction by
idling and loading of the project automatically through
the schedule manager (time) feature, which I think
is the same as what you have mentioned.

I will look into ESM module as you have mentioned for
the web users. But, any idea on how to do it for the
few desktops users.

Thanks
teccum

 

[FLB]

execution idling the project will prevent _all_ users from generating queries that will hit the data warehouse while keeping it up and running (i.e. users can see objects, open history list messages,....). [please not that idle mode is different from unloading a project]

Another idea: Another similar way of achieving similar functionality but _just_ for a set of users is to play with user groups and priority maps. If you were to make the undesirable users part of the "low priority" user group, then in the morning, you could change your priority map to make sure the "low priority" user group can only run at the "Low priority" level _and_ set the number of low priority DB thread to 0.... That will make their query wait until the nb of db thread is raised.

2 cents,
FLB.

 

[teccum]

FLB,

I also had this option open but my I.T head wants
to restrict the access to those set of user completely
for a particular duration of time. I am thinking of
handling it through command manager. I need to try that.

Thanks for your ideas.

teccum.

 

[FLB]

Another way would also to disable those users (using Command Manager) at specific times. Not sure how that would translate into the user experience. I would still go the ESM route!