Questions From The Field…Answered
How does the virtual user handle disconnected sessions?
Find out in our new Vlog series: “Questions From The Field…Answered”!
The other day I had the benefit of working with one of our customers in the healthcare practice. They use Login PI to make sure their EHR medical application services are always available throughout their 30 clinics and hospitals, 24 x 7 x 365, and have nearly 30,000 employees. This customer also uses IGEL, which is a supported platform to run the Login PI launchers.
If you aren’t familiar with Login PI, the virtual appliance is set up to ask the launcher to establish a session to a hosted workspace or application, so that the virtual user can log in, start multiple applications in a particular workflow, interact with those applications and logoff. This can be a continuous process or can happen many times per hour and day if you’d like.
Recommended For You:
Given the number of different networks at the clinics and hospitals this customer manages, it makes sense that he would be very interested in what happens if a session suddenly becomes disconnected, or if enabled, automatically reconnects. Networks should be reliable, but sometimes they can be a little flakey, and when it comes to EHR, he wants to make sure everything is quickly accessible and available…ALWAYS.
So, in this edition of Questions From The Field…Answered, I’m providing a quick video demonstration of how we handle reconnects…it works like this…if a session where we have our Login PI engine running gets disconnected we will detect this and log the virtual user off immediately. This ensures that next time we start a session, the environment is prepped to run the virtual user engine again.
If the Login PI Environment Login Time is set to a value less than the total time it takes to run the full workload (e.g., 1 minute), then Login PI will immediately log back in after a session gets disconnected. After getting logged back in again, we’ll start the application workflow over to make sure we didn’t miss any important data.
Here’s what happens in the video:
- Have Login PI start a session to a healthcare workspace that runs a radiology application, an EMR application, and MS Excel
- We disconnect the session before we have a chance to run through the complete application workflow. We get through the 3D Radiology app, but never get to the EHR application or Excel
- We see the session abruptly ended on the disconnect, but seconds later the Login PI Launcher connects back to the workspace with the given user and starts the workflow over…