![]() ![]() An exception is made for the system administrator, who can log in to disconnect current users by means of the User Connection Monitor or increase this governing setting. When the maximum number of user sessions for a project is reached, users cannot log in to the system. You can limit the number of sessions that are allowed for each project. If you sort the list of connections by the Project column, you can see the total number of user sessions for each project. In the User Connection Monitor, the connections made to the project display the project name in the Project column. When a user accesses a project, a connection (called a user session) is established for the project and Intelligence Server. To specify this setting, in the Intelligence Server Configuration Editor, select the Governing Rules: Default: General category and type the number in the Maximum number of user sessions field. When the maximum number of user sessions on Intelligence Server is reached, users cannot log in, except for the administrator, who can disconnect current users by means of the User Connection Monitor or increase this governing setting. Project sessions are governed separately with a project level setting, User sessions per project, which is discussed below. In the User Connection Monitor, the connections made to Intelligence Server display as in the Project column. Each session connects once to Intelligence Server and once to each project that the user accesses. A single user account can establish multiple sessions on an Intelligence Server. This includes connections made from MicroStrategy Web products, Developer, Distribution Services, Scheduler, or other applications that you may have created with the SDK. ![]() This setting limits the number of user sessions that can be connected to an Intelligence Server. Limit the Number of User Sessions on Intelligence Server These user session limits are discussed below as they relate to software features and products. If the user then closes thier browser or logs out without canceling the job, the user session remains open until the open job "Waiting for Autoprompt" times out. For example, if a MicroStrategy Web user runs a report with an autoprompt and, instead of answering the prompt, clicks the browser's Back button, an open job is created. This includes reports that are waiting for autoprompt answers. ![]() Intelligence Server does not end a user session until all the jobs submitted by that user have completed or timed out. In this case, if you set the inactive time limit to 15 minutes, the person who left for lunch has their session ended by Intelligence Server. You can set a time limit for the total duration of a user session, and you can limit how long a session remains open if it is inactive or not being used. If Intelligence Server is serving the maximum number of user sessions and another user attempts to log in to the system, that user is not allowed to log in. Also, both Developer and MicroStrategy Web have session timeouts so that when users forget to log out, the system logs them out and their sessions do not unnecessarily use up Intelligence Server resources.įor example, a user logs in, runs a report, then leaves for lunch without logging out of the system. To help control the load that user sessions can put on the system, you can limit the number of concurrent user sessions allowed for each project and for Intelligence Server. The more user sessions that are allowed on Intelligence Server, the more load those users can put on the system because each session can run multiple jobs. Users that are logged in but are not doing anything still consume some resources on Intelligence Server. This user session remains open until the user logs out of the system or the system logs the user out. When a user logs in to a MicroStrategy system, a user session is established. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |