In version 1.1 of the Citrix Linux VDA, the Broker Agent service (ctxvda) adds a new feature that system power state firmly and network changes. This feature provides the Delivery Controller (Broker) with details on the state of the Linux VDA and in particular the ability of these compounds to accept negotiated VDA.
What does this mean? If the Broker Agent service in either power state change recognizes (suspend / hibernate or wake / Resume) or IP address change on a network interface, the service will notify the Delivery Controller that a change has occurred. When the engine is stopped or the Broker Agent Service be hibernated disconnect active sessions and log out of the Delivery Controller. When the machine is awakened from a sleep, take a rest or the IP address changes to one of the network interfaces, the broker agent will re-register with the Delivery Controller.
The table below summarizes the action by the Service Broker agents taken if a system performance or network state change occurs.
System status change | Broker Agent Action |
| Networking - New IP | with Delivery controller [1945003Re-registrieren] |
| Networking - delete IP | Re-register with Delivery controller |
| power - Sleep / Hibernate | Disconnect all sessions and log out with Delivery controller |
| power - Wake / Resume | with Delivery controller Register |
and how this is achieved? as you may know, the Linux VDA Broker Agent is a Java component, and use not only managed code to power and network events subscribe. To overcome this limitation, we use a Java Native Interface (JNI) to access native system events and these notifications up into the Java part of the service.
For network status changes, the post of Broker Agent service JNI component waits for changes to the network interface and if an IP address is added or deleted, the Broker Agent service triggers a re-registration with the Delivery controller. The registration renewed notifies the Delivery Controller of the new IP address for the connection of calls to this Linux VDA to use.
changes for power state, the Broker Agent service depends on the Power Management Utilities (pm-utils) framework in RedHat 6.x and SuSE 11.x or suspend systemd and Service files in RedHat 7.x and SUSE 12.x. resume when a power state event occurs, pm-utils or systemd solve our own hooks, which in turn notifies the Broker Agent service JNI component of the power state event. a separation of all sessions and logging off from the Delivery Controller
If the Linux VDA goes to sleep solves the Broker Agent service or hibernation. And if the Linux VDA is woken from sleep or hibernate again by one of Broker Agent service triggers a registration with the Delivery Controller.
more of the Linux Virtual reading Desktop Team
, please click on out all our our team posts here .
0 Komentar