User Context

8
User Context It is a user specific roll area which is used to keep user authorizations, parameters, screens and earlier accessed content. Process Flow (LOGON) 1. User requests 2. Dispatcher handles the request 3. Keeps in queue and assign WP based on FIFO 4. The work process gets the username, password, client, logon language and the task handler interprets and hand over the task to the database process. 5. The DB process checks the credentials of the user and provides the ne cessary authorizations to the process. 6. The entire i nformation is copied into the user context which is referred as ROLL OUT. (The information is copied into Roll Area which is subsequently available for all the requests made by the user) The user context remains until the user is logged out. The user context is displayed in the transaction SU56. This complete journey should be completed within 600 Milli seconds on an average or goes up to 600 Seconds Max. 1. Front End Time/ GUI Time : Time taken by the user to reach the dispatcher is called as Front end time. The GUI time should not exceed more than 200 M.Sec. If it exceeds this consider the following. 1. User desktop is slow 2. If this is same with all the users, network might be congested. 3. The user request is expensive (FI and basis will logon to the central instance. Rest of all the users are allowed to login to Dialogue instance) Note: GUI response time is not considered as a part of the Dialogue response time because the request is not received by the dispatcher. 2. Wait Time: The amount of time the user request sits in the queue. Generally it should not be more than 50 M.Sec or 10% of the response time. If the time e xceeds, consider the following. 1. The work process are not sufficient to handle the user requests. (1:5) 2. There are sufficient processes but the existing process are held with expensive request. Login/disable_multi_gui_login. 3. Roll in Time: The work process copies the Roll in User context into WP task handler. The time taken by the work process to copy the context (Roll In) is referred as Roll in time. Generally it should not be more than 50 M. Sec. If it is more than this consider the following. 1. The user context is heavy to Roll in (User might having more authorizations, parameters)

Transcript of User Context

Page 1: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 1/8

Page 2: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 2/8

Page 3: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 3/8

Page 4: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 4/8

Page 5: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 5/8

Page 6: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 6/8

Page 7: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 7/8

Page 8: User Context

7/31/2019 User Context

http://slidepdf.com/reader/full/user-context 8/8