News Article

Version 6 Client Options

PROIV Client Overview

The PROIV Client is a 32 bit Windows program that handles the power user interface. It provides a Multiple Document Interface (MDI - for more information see the PROIV Client Session Manager Briefing Paper) and communicates with the PROIV Virtual Machine via a PROIV protocol running over TCP/IP.

ActiveX controls

PROIV applications can make use of client side third-party ActiveX components to extend the functionality of the PROIV Client.

Graphics

The graphics used by a PROIV application can be held locally on each client PC, or in a central location and downloaded via http. If they are held centrally the administrator specifies whether graphics are to be downloaded on every occasion, only if a newer version exists, or only if the graphic doesn't exist.

PROIV Client deployment

The deployment of the PROIV Client can be an undesirable overhead for PROIV application users. The need to manually install the PROIV Client can lead to logistical problems, particularly in organisations with large numbers of users distributed across multiple installations. To overcome these issues PROIV has developed easy to manage, centrally-controlled deployment options. PROIV Version 6 provides several methods to deploy the PROIV Client.

Manual Installation

The original method for installing the PROIV Client was via a manual 'setup.exe' InstallShield. This method installs all the necessary PROIV Client components in folders and in the client computers Windows registry.

The disadvantage of this method is that the install must be run on each client PC that will be running PROIV. It is also not appropriate for sites which have 'locked down' PCs, where software can only be installed from a central server (see below).

PROIV Client Administration deployment

The PROIV Client Administration component allows for the centralised management of cabinet (.cab) files. Cabinet files are compressed files similar to .zip files and are an efficient way to package and deliver applications over the web.

The cabinet file containing the PROIV Client is held centrally and will be deployed and installed automatically when a user selects the appropriate URL from their browser. The PROIV Client will then run as a standalone application.

When a new version of the PROIV Client needs to be distributed ,this can be uploaded via the Client Administration module. Each application user will then receive the latest version of the software the next time they access the system. All the settings normally associated with the PROIV Client are set via a service definition in the PROIV Client Administration. These settings are maintained once for all application users of that service.

The graphics required by the application are downloaded by each client from a central location. The administrator specifies whether graphics are to be downloaded on every occasion, only if a newer version exists, or only if the graphic doesn't exist.

Customers who wish to deploy additional client side objects with the PROIV Client (e.g. ActiveX controls used by their application) may do so by re-packaging the .cab file.

Microsoft Active Directory deployment

What is Microsoft Active Directory?

Microsoft Active Directory is a distributed directory service , which is included with Windows 2003 Server.

With Active Directory, a system administrator can add a user to Active Directory and through that entry enable access to many applications and services using a single Windows sign-on. Using Active Directory, installation packages for the software required on client PCs are held and controlled on the Network Domain server. These applications can include both Microsoft and third party applications.

Using Active Directory with PROIV will work at sites where client browsers are restricted from downloading and running ActiveX controls, as these sites are unable to use the standard PROIV Client Administration option.

How does Active Directory Work?

On the network domain controller server, a Group Policy Object Editor allows the addition of software packages which the administrator wishes to make available to network users. These packages are Microsoft Installer files (.msi files).

Client computers on the network will then automatically display these packages as available for install in the Add/Remove Programs option.

Combined PROIV Client Admin / Active Directory deployment

The PROIV Client Administration can be used in conjunction with Active Directory. In an Active Directory environment the PROIV Client Administration will recognise that the .msi is to be downloaded to allow client software deployment but it will continue to manage session settings and images as described earlier.

Customers who wish to deploy additional client side objects with the PROIV Client (e.g. ActiveX controls used by their application) may do so by re-packaging the .msi file, using third party tools such as InstallShield.

Which deployment method is right for me?

* To automatically install client side objects you must re-package the msi or cab file using a third party editor.