Interwrite workspace system requirements

#Interwrite workspace system requirements driver
#Interwrite workspace system requirements windows

If the client virtual driver has data to send to the server, the data is also sent immediately.Virtual Channel SDK routes the data to the appropriate callback of the registered object for that Virtual channel. When the client receives the data, Citrix Workspace app for Chrome de-multiplexes the virtual channel data from the ICA stream and passes to the third-party Chrome app implementing the virtual channel. If the server application has data to send to the client, the data is sent to the client immediately.Both the client-side virtual driver and server-side application can send data initiatively:.The server-side application starts, obtains a handle to the virtual channel, and optionally queries for additional information about the channel.

The client passes information about the virtual channels that it supports to the server.

The client connects to the server running XenApp or XenDesktop.

The following is an overview of the client-server data exchange using a virtual channel: Citrix Workspace app for Chrome does not know any data package detail for each virtual channel and it only transfers all available data between the server and the client virtual driver. It is also responsible for sending the data using the appropriate object to the server in coordination with the Citrix Workspace app for Chrome. This figure illustrates the virtual channel client-server connection:Д¬itrix Workspace app for Chrome Virtual Channel SDK is responsible for de-multiplexing the virtual channel data from the ICA data stream and routing it to the correct callback of the registered virtual channel. Each virtual channel should register separately in your Chrome packaged app and Workspace app for Chrome should be configured accordingly. You can either have different Chrome packaged app for each virtual channel or one Chrome packaged app with all the virtual channel implementation. The Chrome packaged app must be installed and the virtual channel must be registered before launching a Citrix Workspace app for Chrome session. When you configure Citrix Workspace app for Chrome using the Chrome packaged app id and the virtual channel name, Citrix Workspace app for Chrome communicates with the Chrome packaged app by sending messages with the help of SDK and calls the appropriate callbacks provided at the time of registering the virtual channel. You must implement the virtual driver by including virtual channel SDK JavaScript file in the Chrome packaged app.

The client side custom virtual driver executes in the context of the client.

#Interwrite workspace system requirements windows

It can be an application or a Windows NT service. The virtual channel on the server side is a normal Win32 process. Each implementation of an ICA virtual channel consists of two components: Server-side portion on the computer running XenApp or XenDesktop В¶

New devices, such as scanners, card readers, and joysticksДЄn ICA virtual channel is a bidirectional, error-free connection for the exchange of generalized packet data between a client and a server running XenApp or XenDesktop.

You can use virtual channels to add functionality to clients. Client requirement В¶Д¬itrix Workspace app for Chrome 2.5 and later Architecture В¶ДЄ Citrix Independent Computing Architecture (ICA) virtual channel is a bidirectional, error-free connection for the exchange of generalized packet data between a server running Citrix XenApp or XenDesktop, and a client device. The Workspace app for Chrome Virtual Channel SDK is supported on Citrix XenApp 6.5 (and later) and Citrix XenDesktop 7.6 (and later). Execution Environment Requirements В¶ Server requirement В¶

Otherwise, the custom virtual channel is not initialized with the launched session. Third-party Chrome app must register the custom virtual channel using the Virtual Channel SDK before launching a HDX app/desktop sessions. However, Citrix recommends you to use Google Admin Console. You can use any supported configuration methods. IDs of all the third-party Chrome apps and the virtual channel stream name must be set in the Workspace app for Chrome configuration before launch of a session. Up to three client side virtual channels are supported where the virtual channel implementation of each virtual channel might be part of the same third-party Chrome app or different app. If virtual channel SDK is added as a part of non-background window, then virtual channel connection is established only when that window is active. Adding the Virtual Channel SDK in the background page ensures that the Virtual Channel is added to the session regardless of the third-party Chrome app running or not. Virtual Channel SDK is a JavaScript file that should be included in the third-party Chrome app preferably in the background page. Third-party Chrome app must be implemented to add a new virtual channel.