Important Notice Copyright 2001 2009 Jetro Platforms, Ltd. All rights reserved. This document is furnished by Jetro Platforms for information purposes only to licensed users of the Jetro COCKPIT product. It is furnished on as as is basis without any warranties whatsoever, express or implied. Information in this document is subject to change without notice and does not represent any commitment on the part of Jetro Platforms. The software described in this document is furnished under a license agreement. It is against the law to copy or use the software except as specifically allowed in the license. No part of this document may be reproduced or transmitted in any form or by any means, whether electronically or mechanically, including, but not limited to, photocopying, recording, or information recording and retrieval systems, without the express written permission of Jetro Platforms. COCKPIT is a registered trademark of Jetro Platforms Ltd. Microsoft Windows, Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Server 2008 (X86 and X64), Windows Vista, Windows 7 and other Microsoft products and logos are registered trademarks of the Microsoft Corporation. Adobe Acrobat is a registered trademark of Adobe Systems Incorporated. Other company and brand products and service names are trademarks or registered trademarks of their respective holders. Publication date: June 2009 Part No. Jet 05 09 B 2 Important Notice
About This Guide This guide is intended for system administrators who will perform the installation and quick setup of a COCKPIT4 Application Delivery environment. It starts from the prerequisites and describes the installation and configuration process. This guide describes enough of the options to get Application Delivery up and running quickly and to enable you to test that at least one Application Delivery client user can access at least one application through the COCKPIT4 client. We highly recommend that you closely follow the instructions provided in this guide. The guide is organized so that you can read it from cover to cover in order to set up your first Application Delivery experience. After reading this guide, you may refer to the Jetro COCKPIT4 User Guide for a full description of all the options in the Application Delivery configuration process. NOTE: For a description of Application Delivery options, you may refer to the Jetro COCKPIT4 for Application Delivery Administrator Guide. This guide contains the following chapters: Chapter 1, Introduction, page 7, introduces the COCKPIT4 Application Delivery platform and presents the workflow for installing and configuring the Application Delivery servers and clients. Chapter 2, Installing Application Delivery Servers, page 19, describes how to install the servers that enable Application Delivery. Chapter 3, Configuring Application Delivery Servers, page 55, describes how to configure Application Delivery servers. Chapter 4, Setting Up Application Delivery Clients, page 89, describes how to install and use the Jetro Application Delivery Client on a user s computer. Index, page 101 About This Guide 3
Table of Contents Support and Contacting Information... 6 Conventions Used in this Guide... 6 CHAPTER 1, INTRODUCTION...7 What is Jetro COCKPIT4?... 8 Benefits... 8 Features and Capabilities... 9 Experiencing Application Delivery... 10 Setting Up Application Delivery... 10 Enjoying Application Delivery... 10 Application Delivery Architecture... 12 COCKPIT4 Clients... 12 COCKPIT4 Controller... 13 Terminal Servers... 15 COCKPIT4 Administration Console... 15 Other COCKPIT4 Options... 16 Installation and Configuration Workflow... 18 CHAPTER 2, INSTALLING APPLICATION DELIVERY SERVERS...19 System Requirements... 20 Installing the COCKPIT4 Primary Controller Server... 20 Installing DataStore... 21 Installing the COCKPIT4 Server... 28 Installing the COCKPIT4 for Application Delivery License Server... 34 Installing the COCKPIT4 for Application Delivery Administrator Console.. 42 Installing the COCKPIT4 Terminal Server Service... 49 CHAPTER 3, CONFIGURING APPLICATION DELIVERY SERVERS...55 Configuring the License Server... 56 Configuring Domains... 58 Configuring the Connection to the Hosts... 62 Adding a Host COCKPIT4 Secondary Controller Server... 63 Adding a Host COCKPIT4 Terminal Server... 68 Configuring Application Delivery Users... 71 Configuring Application Delivery... 73 4 Table of Contents
Configuring Applications...74 General Tab Applications... 76 Security Tab Applications... 79 Host Groups Applications... 83 Configuring Application Groups...84 Adding Application Groups... 85 CHAPTER 4, SETTING UP APPLICATION DELIVERY CLIENTS... 89 Application Delivery Client Prerequisites...90 Installing the Application Delivery Client...90 Logging into the COCKPIT4 Client...97 Exiting the COCKPIT4 Client...99 Uninstalling the Application Delivery Client...99 INDEX... 101 Table of Contents 5
Support and Contacting Information For information about Jetro Platforms and our products, visit our website at http://www.jetroplatforms.com/ Or contact us by e-mail or phone at: E-mail: support@jetroplatforms.com or info@jp-inc.com Phone: 1-800-639-5516 For help using Jetro COCKPIT, you can visit our online support section at: http://www.jetroplatforms.com/support Conventions Used in this Guide NOTE: This is a note 6 Support and Contacting Information
3CHAPTER 1 INTRODUCTION This chapter introduces the COCKPIT4 Application Delivery platform and presents the workflow for installing and configuring the Application Delivery servers and clients. This chapter contains the following sections: What is Jetro COCKPIT4?, page 8 Experiencing Application Delivery, page 10 Application Delivery Architecture, page 12 Installation and Configuration Workflow, page 18 INTRODUCTION 7
What is Jetro COCKPIT4? Benefits Jetro COCKPIT4 is a comprehensive Server Based Computing (SBC) solution for centralizing application deployment and management using Windows Terminal Services. Software applications are installed and managed centrally rather than on each individual desktop. The COCKPIT4 platform enables administrators to define which user groups (users) can access which applications and when. It is easy to install and administer and runs transparently to end users as a client on their desktop. COCKPIT4 is a remotely operated and controlled virtual desktop that enables IT personnel to standardize software usage in corporate environment. It can be customized by an administrator for each user and accessed from any computer. It is a valuable management tool that enables administrators to deploy applications quickly and easily, while enabling users to work productively in a seamless environment. The COCKPIT4 functionality is enabled by its server site that provides an application distribution client server environment. Enhances Performance: With Jetro COCKPIT4 more users can be connected to each terminal server, thereby reducing the load on the Terminal Servers hardware resources. Improves Effectiveness: COCKPIT4 delivers the most effective load balancing solution in Server-Based Computing (SBC) today. With hundreds of performance counters and numerous unique features, COCKPIT4 enables administrators to match the ultimate load balancing policy for addressing the organization s specific needs. Highly Reliable: COCKPIT4 features built in clustering and failover with its core components. Easy to Implement: The simplicity of the COCKPIT4 architecture results in quicker implementation and easier maintenance. Simple to Manage: Advanced administrator console. Competitively Priced: Jetro COCKPIT4 is an affordable solution. COCKPIT On Key: COCKPIT On Key provides access to COCKPIT applications from a disk-on-key, as well as from other portable storage devices according to pre-defined parameter settings. 8 INTRODUCTION
Jetro COCKPIT2i: Jetro s secure browser guarantees 100% safe web access. Secure Browsing streams web pages as video bitmaps so that the content that end-users view does not contain any HTML, JavaScript, JPEG, Flash or any other kind of internet content. In this way, Secure Browsing-enabled web browsing is resilient against both known and unknown security threats. Complete Integrated Printing Solution: COCKPIT4 provides a seamless user printing solution that supports both Native and Universal printing to save and significantly lower TCO. This as an optional add-on feature. Features and Capabilities The following is a partial list of COCKPIT4 features and capabilities: Delivers seamless Remote Display Protocol (RDP) sessions Publishes applications throughout the enterprise Runs applications on any thin client Provides secure access to remote applications Improves system security using encryption, Smart Card support and more Monitors server activity in real time Load Balances server sites that have Microsoft Terminal Servers Maximizes and monitors the use of existing software licenses Creates application groups, schedules and security policies Generates usage reports Provides server-to-client content redirection for voice mail, video and more Provides client to server content redirection for voice mail, video and more Improves system performance Provides PDF/PostScript and EMF printing solutions for applications that enable remote applications to print on any locally available printer. This is an optional add-on feature. INTRODUCTION 9
Experiencing Application Delivery Setting Up Application Delivery Corporate system administrators are responsible for defining (publishing) the applications to be delivered by COCKPIT. Administrators use the administrator console to define which of the applications installed on corporate Terminal Servers are available to corporate COCKPIT4 users. In COCKPIT, software applications are installed and managed centrally rather than on each individual user s desktop. The COCKPIT4 platform enables administrators to define which users and user groups can access which applications, when they can access them and how they will experience their usage. The COCKPIT4 system then automatically handles application delivery to COCKPIT4 clients according to these defined polices. Enjoying Application Delivery End users experience a COCKPIT4 client as a desktop that displays the application links and application groups that have been assigned to them by the enterprise administrator. Applications delivered by COCKPIT4 run seamlessly on each user s desktop and behave in the same way as any other window on their desktop, as follows: Window: Applications run seamlessly in their own window and are integrated into the user s local windows in the same way that they would be if they were running locally. This is a significant advantage over standard Server Based Computing (SBC) solutions that only function by providing an entire desktop. Copy/Paste: Content can be copied and pasted between local and remote applications Desktop and Start Menu Access: In addition to access from COCKPIT4 s application panel, COCKPIT4 applications can be accessed from desktop icons and the Start menu as defined by the administrator. 10 INTRODUCTION
Taskbar: The taskbar shows COCKPIT4 applications and enables access to them in the same way that is shows locally run applications. Alt Tab: The Alt Tab keys can be used to switch between regular applications and those delivered by COCKPIT. Resizing, Stack, Move, Minimize and Maximize Windows: COCKPIT4 application windows behave in the same way as regular applications. This feature is also called Seamless Windows. Children Windows: Child windows that are opened from COCKPIT4 application windows behave in the same way as regular windows. Terminal Server and Local Applications: COCKPIT4 delivers applications either from the enterprise s Terminal Servers or locally, from the user s own machine. Users are still enabled access to their own local applications. IMPORTANT NOTE: For users of previous COCKPIT versions Previous versions of COCKPIT delivered the application panel from the Terminal Server. This version of COCKPIT4 delivers the application panel that appears on the user s desktop from the COCKPIT4 Controller. This enables users to immediately see the icons of the applications to which they are allowed access even before they connect to a Terminal Server. This also ensures that Terminal Server CALs (Client Access Licenses) are not wasted, because they are not used until the end user actually launches an application through COCKPIT4 from a Terminal Server. INTRODUCTION 11
Application Delivery Architecture The following shows a typical Application Delivery implementation and the components that enable the secure flow of data: Application Delivery Architecture: Basic System COCKPIT4 Clients The COCKPIT4 client can be installed on any standard user s workstation to enable the seamless operation, integration and delivery of applications from the enterprise s Terminal Servers. The COCKPIT4 client displays application links and application groups, a shown below: 12 INTRODUCTION
The example above shows two application groups and three local applications. Users can click on an application or open a group and then click on an application to run it. The application then runs seamlessly on the end user s desktop from a Terminal Server according to the definitions of the COCKPIT4 Controller. Administrators can define and control COCKPIT4 client user activities, such as host resolution (NAT enabled or disabled), local printing and disk drive mapping. COCKPIT4 Controller What is a COCKPIT4 Controller? The COCKPIT4 Controller manages and monitors application delivery on the COCKPIT4 site, as well as the relationships between all the elements in the COCKPIT4 site server-based computing network. When a COCKPIT4 client connects to the COCKPIT4 Controller, the Controller sends the client information about the applications that can be accessed by this user. The COCKPIT4 client then displays these applications in its application panel, as described on the previous page. This means that COCKPIT4 users can see the applications to which administrators have given them access as soon as the client connects to the COCKPIT4 Controller. When a COCKPIT4 Controller receives a request from a COCKPIT4 client to launch an application, it instructs the COCKPIT4 client which Terminal Server to use according to the applications that run on the Terminal Servers, corporate policies and load balancing policies. The COCKPIT4 Controller handles the provisioning of sessions between Terminal Servers, as described in the Terminal Servers section below. INTRODUCTION 13
Two types of COCKPIT4 administration data are shared by the Controllers: Static data, which represents the descriptions made in the COCKPIT4 Administration Console by the administrator, as described in this guide. You can use the Backup and Restore option in the Administration branch of the COCKPIT4 Administration Console to backup and later restore this data. Dynamic data, which represents the ongoing usage and performance status of various entities in the system, such as: Which user is logged onto which Terminal Servers Which applications each user is running The files and settings stored on the Terminal Servers To which printers each user has access Multiple Controllers Each COCKPIT4 site has a single primary Controller, which stores and manages the primary copy of the current COCKPIT4 administration data, whereas, other Controllers in the COCKPIT4 site only hold copies of this data for backup purposes. When data is changed in any of the Controllers, the same information is updated and synchronized on all of the other Controllers in the site. Load Balancing is performed automatically between these Controllers. Controller Resilience Multiple Controllers are also used for redundancy, meaning that if the Primary Controller fails, another Controller assumes primary control. Sites that have more than two Controllers provide additional backup according to corporate requirements. If there is a failure in the system and the Controllers cannot synchronize between them, both Controllers can continue to operate independently and will automatically resynchronize their data when their connection is restored. If during the synchronization process after a failure, the Controllers have conflicting information, then the system status of the primary Controller will prevail. The description of the primary Controller is dynamic, meaning that in case of a failure of the primary Controller, it is possible to delegate the role of primary Controller to another Controller. 14 INTRODUCTION
Terminal Servers Multiple Terminal Servers run applications on a COCKPIT4 site. COCKPIT4 clients send application requests to the COCKPIT4 Controller, which instructs the COCKPIT4 client which Terminal Server to use. The COCKPIT4 environment provides an important resource and license saving feature called Session Sharing. COCKPIT4 only opens a session between a client and a Terminal Server when the client actually launches an application and not before. While this session is open, all other applications that run from this same COCKPIT4 client and that run on this same Terminal Server use this same session. COCKPIT4 Administration Console The COCKPIT4 Administration Console provides the site administration functionality and user interface described throughout this guide. The COCKPIT4 Administration Console is typically run on the Primary Controller, but can also easily be installed on the system administrator s machine. The administrator console communicates with all the other COCKPIT4 site components, such as the Terminal Server COCKPIT4 Agents. Using the COCKPIT4 Administration Console, an administrator can define which users can access which applications, when they can access them and the way that the application will function. The main window of the COCKPIT4 Administration Console is shown below: INTRODUCTION 15
Other COCKPIT4 Options The following describes other COCKPIT4 options. These options are not detailed in this guide. You may refer to the Jetro COCKPIT4 User Guide for more information. COCKPIT4 Secure Connector The COCKPIT4 Secure Connector enables remote users connecting from an unsecured network environment to establish a secure communication channel between the COCKPIT4 client and the internal restricted COCKPIT4 site. This option is especially suitable for enterprise employees who work at home from time to time. It provides a secure connection that enables access to all required applications, but does not add that workstation to the corporate network, nor does it share other information residing on that workstation. Depending on the type of request, the Secure Connector transfers the request to the Terminal Server or the COCKPIT4 Controller. Traffic is encrypted and decrypted using RSA encryption. COCKPIT4 Universal Connector The COCKPIT4 Universal Connector is intended for any non-windows based workstations and RDP enabled devices running legacy thin clients. It provides that workstation with full access to COCKPIT4 functionality inside an RDP session. The COCKPIT4 Universal Connector manages the authentication and session state and enables reconnection to disconnected session from various clients. Platforms include: Win32, WinCE, Win FLP, XP Embedded Linux, Apple, Solaris and Microsoft Mobile with a suitable RDP client. 16 INTRODUCTION
COCKPIT4 on Key COCKPIT4 On Key provides access to COCKPIT applications from a disk-on-key, as well as from other portable storage devices. The Jetro COCKPIT4 Portable Client Packager utility enables administrators to create a COCKPIT4 On Key client executable that uses pre-configured connection parameters. The Packager packages the COCKPIT4 On Key client into a single executable file and creates an autorun.inf file that can be placed on a USB disk-on-key. Inserting the USB key into a desktop computer automatically launches and runs the COCKPIT4 On Key client according to the pre-configured parameters (unless the autorun function is disabled). Removing the USB key from the computer closes the client leaving no trace on the host computer. INTRODUCTION 17
Installation and Configuration Workflow The following presents the workflow for installing and configuring the various components of a Jetro COCKPIT4 Application Delivery system. This procedure can be performed quite quickly and may vary between organizations. We highly recommend that you closely follow the instructions provided in this guide. This guide is organized so that you can read it from cover to cover in order to set up your first Application Delivery experience. Step 1 Installing Application Delivery Servers Page 19 Configuring Application Delivery Servers Page 55 Setting Up Application Delivery Clients Page 89 Testing Application Usage Step 1, Installing Application Delivery Servers, page 19, describes how to install the servers that enable Application Delivery. Application Delivery is enabled by installing a primary Controller (and optionally a secondary Controller) and Terminal Servers that serve the applications. Step 2, Configuring Application Delivery Servers, page 55, describes how to configure Application Delivery servers. Step 3, Setting Up Application Delivery Clients, page 89, describes how to install the Jetro Application Delivery Client on a user s computer. Step 4, Testing Application Usage, simply launch all the applications in order to verify that they application delivery is operating properly. 18 INTRODUCTION
4CHAPTER 2 INSTALLING APPLICATION DELIVERY SERVERS This chapter describes how to install the servers that enable Application Delivery. This chapter contains the following sections: System Requirements, page 20 Installing the COCKPIT4 Primary Controller Server, page 20 Installing the COCKPIT4 Terminal Server Service, page 49 INSTALLING APPLICATION DELIVERY SERVERS 19
System Requirements This following describes the prerequisites that must be installed before installing the COCKPIT4 for Application Delivery components. The system requires one Primary Controller and optionally may have additional Controllers. The system requires one or more Microsoft Terminal Servers. Each Terminal Server must be a member server in one of the corporate Active Directory domains. The COCKPIT4 system can be installed on any machine that is suitable for Microsoft Window Server 2003 SP2 or Window Server 2008 (X86 and X64) architecture. Installing the COCKPIT4 Primary Controller Server This section describes how to install the COCKPIT4 Primary Controller Server. The installation package for this server includes the following installation components: JSB-DataStoreSetup, page 21, installs a Data Storage server. This setup may also install MS.net2.x, SQL Server Express 2005 and MSXML 4.x, depending on what is already installed on the machine. JSB-ServerSetup, page 28, installs a basic server. This setup is run on all Jetro Application Delivery servers, regardless of their type. JSB-LicenseServerSetup, page 34, installs the License Server. JSB-AdminConsoleSetup, page 42, installs the administrator console which can be used to configure the system and to verify that the system is running properly. 20 INSTALLING APPLICATION DELIVERY SERVERS
Installing DataStore Installing DataStore installs the database for the Jetro COCKPIT4 Application Delivery system. Optionally, this process automatically detects and installs two components if they do not already exist on the computer: Microsoft SQL Express 2.005 and MS XML 6. To install DataStore for COCKPIT4 for Application Delivery: 1 Copy the COCKPIT4 for Application Delivery Setup programs to a local directory of the Windows Server 2003/2008 where COCKPIT4 for Application Delivery Controller is to be installed. 2 Double-click the DataStore setup file named JSB-DataStoreSetup.exe. The InstallShield Wizard displays a list of required Microsoft SQL applications that must be installed prior to installing DataStore, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 21
3 Click Install to install the required programs. The Wizard displays the progress of the installation of the required applications. 22 INSTALLING APPLICATION DELIVERY SERVERS
4 When the Next button becomes active, meaning after the installation of the MS SQL applications is complete, click Next. The JSB-Data Store Install Wizard Welcome window is then displayed, as shown below: 5 To continue, click Next. The License Agreement window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 23
6 Accept the terms of the License Agreement. The Next button becomes active. 7 Click Next. The Customer Information window is then displayed, as shown below: 8 Enter your customer information in the fields provided and then click Next. The Destination Folder window is then displayed, as shown below: 24 INSTALLING APPLICATION DELIVERY SERVERS
9 Click Next to install to the default folder. Alternatively, click the Change button to install to a different folder. The Change Current Destination Folder is then displayed, as shown below: 10 As required, use the browse mechanism to select an alternative destination folder. Otherwise, use the default destination that appears in the Look In field. When you are ready to continue with the installation procedure, click OK. The Setup Type window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 25
11 Choose the Complete setup type and then click Next. The Ready to Install the Program window is then displayed, as shown below: 12 Click Install to begin the installation. The Installing JSB-Data Store progress window is then displayed, as shown below, which shows the progress of the installation. 26 INSTALLING APPLICATION DELIVERY SERVERS
13 When the installation is complete, click Next. The InstallShield Wizard Completed window is then displayed, as shown below: 14 Click Finish. INSTALLING APPLICATION DELIVERY SERVERS 27
Installing the COCKPIT4 Server Ensure that you have first installed DataStore, as described in the previous section, before proceeding with this section. To install the COCKPIT4 for Application Delivery Server: 1 Open the COCKPIT4 for Application Delivery local Server directory. This is the directory into which you copied the setup files. 2 Double-click the Server Setup program, JSB-ServerSetup.exe. The Preparing to Install... progress window is then displayed, as shown below: 28 INSTALLING APPLICATION DELIVERY SERVERS
The Setup Wizard for JSB-Server window is then displayed, as shown below: 3 Click Next. The License Agreement window is then displayed, as shown below: 4 Accept the terms of the License Agreement. The Next button becomes active. INSTALLING APPLICATION DELIVERY SERVERS 29
5 Click Next. The Destination Folder selection window is then displayed, as shown below: 6 Click Next to install to the default folder. Alternatively, click the Change button to install to a different folder. The Change Current Destination Folder is then displayed, as shown below: 30 INSTALLING APPLICATION DELIVERY SERVERS
7 As required, use the browse mechanism to select an alternative destination folder. Otherwise, use the default destination that appears in the Look In field. When you are ready to continue with the installation procedure, click OK. The Ready to Install the Program window is then displayed, as shown below: 8 Click Install to begin the installation. The Installing JSB-Server progress window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 31
9 After the installation is complete, click Next. The JSB-Server Configuration window is then displayed, as shown below: 10 Select the Primary Controller option to assign this JSB-Server instance as the Primary Controller. IMPORTANT NOTE: There can be and must be only one Primary Controller in any given installation or environment. NOTE: In practice, there is nothing that stops the installer from designating a second Primary Controller from this window. However, this is not recommended because it may produce an unpredictable result! 32 INSTALLING APPLICATION DELIVERY SERVERS
11 Click OK. The following window is displayed for the primary Controller. Click No. The InstallShield Wizard Completed window is then displayed, as shown below: 12 Click Finish. The installation procedure has successfully installed the JSB-Server to your selected destination. INSTALLING APPLICATION DELIVERY SERVERS 33
Installing the COCKPIT4 for Application Delivery License Server The same license server can serve both a COCKPIT4 Controller and a Secure Browsing Controller, even if they are installed on different computers. Installation Considerations The COCKPIT4 for Application Delivery License Server is subject to the following considerations: The COCKPIT4 for Application Delivery system will not run without a properly installed License Server. A Primary Controller must be installed, as described in the previous section. The out-of-the-box License Server provides the system with up to 1,000 concurrent users for 30 days. After 30 days, the system requires a valid activation file. This can be purchased from Jetro directly or from an authorized reseller. An activation file can apply to COCKPIT4 only, to Application Delivery only or to both. It is recommended to install the License Server on the Primary Controller machine. 34 INSTALLING APPLICATION DELIVERY SERVERS
Installation Procedure To install the COCKPIT4 License Server: 1 Open the COCKPIT4 for Application Delivery local Server directory. This is the directory into which you copied the setup files. 2 Double-click the Server Setup program, JSB-LicenseServerSetup.exe. The Preparing to Install... progress window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 35
After preparation, the Setup Wizard for JSB-Server is then displayed, as shown below: 3 Click Next. The License Agreement window is then displayed, as shown below: 4 Accept the terms of the License Agreement. The Next button becomes active. 36 INSTALLING APPLICATION DELIVERY SERVERS
5 Click Next. The Customer Information window is then displayed, as shown below: 6 Enter the User Name and Organization in the provided fields and select a user security option. 7 Click Next. The Destination Folder selection window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 37
8 Click Next to install in the default folder. Alternatively, click the Change button to specify to install to a different folder. The Change Current Destination Folder is then displayed, as shown below: 9 As required, use the browse mechanism to select an alternative destination folder. Otherwise, use the default destination that appears in the Look In field. When you are ready to continue with the installation procedure, click OK. The Setup Type window is then displayed, as shown below: 38 INSTALLING APPLICATION DELIVERY SERVERS
10 Click Next. The Ready to Install the Program window is then displayed, as shown below: 11 Click Install to begin the installation. The Installing Jetro License Server progress window is displayed showing the progress of the installation, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 39
After a while the following window is displayed. 12 Click the Generate ID button to automatically generate a unique identifier for this COCKPIT4 farm, as shown below: 40 INSTALLING APPLICATION DELIVERY SERVERS
13 In the Farm name field, enter a name for the farm and click OK. 14 After the installation is complete, click Next. The InstallShield Wizard Completed window is then displayed, as shown below: 15 Click Finish to exit the Wizard. The installation procedure has successfully installed the JSB-License Server. INSTALLING APPLICATION DELIVERY SERVERS 41
Installing the COCKPIT4 for Application Delivery Administrator Console Installation Considerations The COCKPIT4 for Application Delivery Administrator Console is subject to the following considerations: It is a best practice to install an Administrator Console on the Primary Controller. This allows the administrator to configure the system and to verify that the system is functioning properly. For day-to-day operations, System Administrators will find it convenient to install the Administrator Console on their personal workstations, as shown in the system architecture diagram on page 17. Installation Procedure To install the COCKPIT4 for Application Delivery Administrator Console: 1 Open the COCKPIT4 for Application Delivery local Server directory. This is the location into which you copied the setup files at the beginning of the installation procedure. 42 INSTALLING APPLICATION DELIVERY SERVERS
2 Double-click the Server Setup program, JSB- AdminConsoleSetup.exe. The InstallShield Wizard prepares to install the Admin Console. 3 Click Next. The Administrator Console License Agreement window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 43
4 Accept the terms of the License Agreement. The Next button becomes active. 5 To continue, click Next. The Destination Folder window is then displayed, as shown below: 6 Click Next to install to the default folder. Alternatively, click the Change button to install to a different folder. The Change Current Destination Folder is then displayed, as shown below: 44 INSTALLING APPLICATION DELIVERY SERVERS
7 As required, use the browse mechanism to select an alternative destination folder. Otherwise, use the default destination that appears in the Look In field and then click OK. The Wizard is then ready to begin installation. 8 Click Install to begin the installation. The Installing JSB-Admin Console progress window is displayed showing the progress of the installation. INSTALLING APPLICATION DELIVERY SERVERS 45
9 After the installation is complete, click Next. The InstallShield Wizard Completed window is then displayed, as shown below: 10 Check the Launch JSB-Admin Console checkbox to launch the JSB-Admin Console immediately and click Finish. Alternatively, if you do not check this option, you can launch the JSB-Admin Console later by clicking Finish and then starting the Admin Console application using the icon that the installation procedure creates on the workstation desktop. 46 INSTALLING APPLICATION DELIVERY SERVERS
11 The first time the JSB-Admin Console runs, you will be prompted to enter the Controller Server Settings. As you can see, the window above shows the words Not Connected on its bottom left. In the Controller Server field, specify the server name or IP address of the Controller server. In the Controller Server Communication Port field, leave the default port value of 13000 to specify the port though which the Controller server communicates. NOTE: The Login as option cannot be selected at this point, because the Domain has not yet been defined. In the Login as field, enter your own user name and password and the domain of the controller. INSTALLING APPLICATION DELIVERY SERVERS 47
12 Click OK to display the main Administrator Console window. Upon success, the Primary Controller is shown on the bottom left of the window. 13 Select the Network All Hosts branch to display a list of all the defined Application Delivery hosts in this site, as shown below: 14 Verify that this window shows that the primary Controller is installed and that the columns shown above have green checkmarks. 48 INSTALLING APPLICATION DELIVERY SERVERS
Installing the COCKPIT4 Terminal Server Service This section describes how to install the COCKPIT4 Terminal Server service inside the LAN. The installation package for this server only requires the installation of JSB-ServerSetup, as described below, which installs a basic server. This setup is run on all Jetro Application Delivery servers, regardless of their type. Verify that the Terminal Services are installed and operating properly. To install the COCKPIT4 Terminal Server service: 1 Copy the COCKPIT4 for Application Delivery Setup program to a local directory of the Windows Terminal Server 2003/2008 where COCKPIT4 for Application Delivery Controller is to be installed. INSTALLING APPLICATION DELIVERY SERVERS 49
2 Double-click the Server Setup program, JSB-ServerSetup.exe. The Preparing to Install... progress window is then displayed, as shown below: The Setup Wizard for JSB-Server is then displayed, as shown below: 50 INSTALLING APPLICATION DELIVERY SERVERS
3 Click Next. The License Agreement window is then displayed, as shown below: 4 Accept the terms of the License Agreement. The Next button becomes active. 5 Click Next. The Destination Folder selection window is then displayed, as shown below: INSTALLING APPLICATION DELIVERY SERVERS 51
6 Click Next to install to the default folder; alternatively, click the Change button to install to a different folder. The Change Current Destination Folder is then displayed, as shown below: 7 As required, use the browse mechanism to select an alternative destination folder. Otherwise, use the default destination that appears in the Look In field. When you are ready to continue with the installation procedure, click OK. The Ready to Install the Program window is then displayed, as shown below: 52 INSTALLING APPLICATION DELIVERY SERVERS
8 Click Install to begin the installation. The Installing JSB-Server progress window is displayed and shows you the progress of the installation. 9 When the installation is complete, click Next. 10 The Installation Wizard automatically detects the Terminal Server services that are installed on this computer and displays the JSB-Server Configuration window, as shown below: Check the Terminal Server checkbox and click OK. INSTALLING APPLICATION DELIVERY SERVERS 53
11 Click OK. The InstallShield Wizard Completed window is then displayed, as shown below: 12 Click Finish. The installation procedure has successfully installed the JSB-Server to your selected destination. You have now completed the installation of all the servers. You must now configure these servers, as described in Chapter 3, Configuring Application Delivery Servers on page 55. 54 INSTALLING APPLICATION DELIVERY SERVERS
5CHAPTER 3 CONFIGURING APPLICATION DELIVERY SERVERS This chapter describes how to configure Application Delivery servers. This chapter contains the following sections: Configuring the License Server, page 56 Configuring Domains, page 58 Configuring the Connection to the Hosts, page 62 Configuring Application Delivery Users, page 71 Configuring Application Delivery, page 73 Configuring Applications, page 74 Configuring Application Groups, page 84 CONFIGURING APPLICATION DELIVERY SERVERS 55
Configuring the License Server This section describes how to configure the Application Delivery License Server that you installed, as described in the previous chapter. To configure the License Server: 1 Under the General branch, select the License Server branch. 2 Right-click the Registration of License Server button to display the Registration on License Server window, as shown below: 3 Enter or change the connection information to the License Server, as follows: License Server Address: Specify the name of the server (in most cases it is the Primary Controller, on which you installed the License Server. It is displayed on the bottom of this window, as shown above. Do not enter the Localhost here. License Server Port: Specify the port of the Primary Controller on which you installed the License Server. 56 CONFIGURING APPLICATION DELIVERY SERVERS
4 Click the Test Connection button to test whether the Controller can actually communicate with this License Server using the specified port. A success message should be displayed at the bottom of the window, as shown below: 5 Click Register to specify that the Application Delivery or COCKPIT4 site works with this License Server. Wait a few moments until a message window is displayed that reads Operation successfully completed. 6 Click OK. CONFIGURING APPLICATION DELIVERY SERVERS 57
Configuring Domains Both COCKPIT4 Application Delivery and Secure Browsing use Active Directory objects to manage users and user groups. In a COCKPIT4 Application Delivery environment, there is typically only one Active Directory. However, a very large organization may have more than one Active Directory domain. The following shows how to configure a single Domain. You can use this same procedure to add additional Domains. NOTE: If both COCKPIT4 and Secure Browsing are installed in the same environment, then the Active Directory domain used by COCKPIT4 Application Delivery will serve as the internal Active Directory domain for Secure Browsing and you must also register the external Active Directory domain for Secure Browsing. NOTE: In COCKPIT, in order for a user to log on, that user must have an account in the Active Directory. That user can then log on from any computer. In Secure Browsing, in order to log on, the computer must be a member in the Active Directory and the user must also have an Active Directory account. The following describes how to register an Active Directory domain. To add an internal domain for determining user access: 1 Select the Network Domains branch, as shown below: 58 CONFIGURING APPLICATION DELIVERY SERVERS
2 Right-click in the center of the page and select New or click the New tool. The first page of the Domain Addition Wizard is displayed, as shown below: 3 Click Next to continue. A list of the defined hosts is displayed in the Host Choice window, as shown below: CONFIGURING APPLICATION DELIVERY SERVERS 59
4 Select the Primary Controller host and click Next to display a list of all the domains that this Controller can see, as shown below: 5 Select the domain to which the Controller is registered. NOTE: In this procedure you select a Domain in the Active Directory, which is simply a list of users and the groups to which users are assigned. Only the users who are members of one of these selected Domains can launch Applications in the COCKPIT4 client. All security settings and application permissions specify a security object, which represents a client s membership in a Domain in the Active Directory. 60 CONFIGURING APPLICATION DELIVERY SERVERS
6 Click Finish. The Domain Registration window displays a message indicating that the selected domain was successfully registered. The same message specifies the name of the Active Directory Explorer of the domain. 7 Click Close. The System Administrator Console is displayed showing the newly registered domain. The following changes to the Console can be noted: The name of the registered domain appears in the list to the left of the display area. The name of the registered domain appears in the DNS Name field. The NetBIOS Name for the domain appears as well. CONFIGURING APPLICATION DELIVERY SERVERS 61
Configuring the Connection to the Hosts The All Hosts branch displays a list of all the hosts defined in the Application Delivery site and specifies their role, meaning whether the host is a Controller, Primary Controller, Terminal Server or Active Directory server. A green checkmark appears in the relevant column to indicate each host s role, as shown below: As shown above, this window displays one row that describes the COCKPIT4 Controller. Each host row provides the following columns: DNS Name: The host's DNS name. Host Roles: A green checkmark indicates the host's role: Primary Controller, Controller or Terminal Server: The Controller appears with two checkmarks to indicate that it is the Primary Controller. AD Explorer: This host serves as an Active Directory services connector, which is also known as an Active Directory Communicator. This server communicates with the enterprise s Active Directory and sends/receives Controller user and group queries. Zone: The network is divided into segments (both remote and local) by nature. A Zone defines the segment in which each component resides. A server resides in a specific Zone. Enabled/Disabled: Specifies whether a server is active or not. A disabled server is defined as part of the Application Delivery site, but is not currently being used. The administrator defines whether a server is enabled or disabled. 62 CONFIGURING APPLICATION DELIVERY SERVERS
This section contains two subsections describing how to add the following hosts: Adding a Host COCKPIT4 Secondary Controller Server, below Adding a Host COCKPIT4 Terminal Server, page 68 Adding a Host COCKPIT4 Secondary Controller Server This section describes how to add a COCKPIT4 Secondary (backup) Controller Server host to the Application Delivery site. The Application Delivery service must first be installed and running before adding a host in the administrator console, as described below. To add a host: 1 Select the Network All Hosts branch to display a list of all the hosts defined in the COCKPIT4 site, as shown below: CONFIGURING APPLICATION DELIVERY SERVERS 63
2 Right-click in the center of the page and select New or click the New tool. The first page of the Host Addition Wizard is displayed, as shown below: 3 Click Next to display the Zone Choice window, as shown below: This window enables you to define within which Zone the new host resides. A network is divided into segments by nature. A Zone can be either a remote or local network segment. In COCKPIT, a Zone defines the network segment in which each Application Delivery component resides. 64 CONFIGURING APPLICATION DELIVERY SERVERS
4 Select the Zone option and the Default zone, as shown below: 5 Click Next to display the Connect to Host window, as shown below: In this window you define the connection between this host and the secondary Controller, as follows: In the Host Address field, specify the host's name or IP address. In the Host Port field, it is recommended to leave the existing default communications port. CONFIGURING APPLICATION DELIVERY SERVERS 65
6 Click the Test Connection button to confirm that the secondary Controller can communicate with this host through this port. A success message should be displayed at the bottom of the window, as shown below: 7 Click Finish to close the Host Connection Wizard. The following success window is then displayed: 66 CONFIGURING APPLICATION DELIVERY SERVERS
The administrator console now shows a new row representing the COCKPIT4 Secondary (backup) Controller Server that was added. As shown above, the Loading column shows the word Offline. 8 Press the Refresh button. After a few seconds, communication should be established. The Loading column will then show the word Low, as shown below: If the word Low does not appear after 30 seconds, then check the connection. CONFIGURING APPLICATION DELIVERY SERVERS 67
Adding a Host COCKPIT4 Terminal Server This section describes how to add one COCKPIT4 Terminal Server host to the Application Delivery site. After you have completed all the processes in this guide and have tested that Application Delivery is functioning properly, you can then add as many Terminal Servers as required. The Application Delivery service must first be installed and running before adding a Terminal Server in the administrator console, as described below. To add a Terminal Server: 1 Select the Network All Hosts branch to display a list of all the hosts defined in the COCKPIT4 site, as shown below: 2 Right-click in the center of the page and select New or click the New tool. The first page of the Host Addition Wizard is displayed, as shown below: 68 CONFIGURING APPLICATION DELIVERY SERVERS
3 Click Next to display the Zone Choice window. This window enables you to define within which Zone the new host resides. A network is divided into segments by nature. A Zone can be either a remote or local network segment. In COCKPIT, a Zone defines the network segment in which each Application Delivery component resides. 4 Select the Zone option and the Default zone, as shown below: 5 Click Next to display the Connect to Host window, as shown below: In this window you define the connection between this host and the Terminal Server, as follows: In the Host Address field, specify the host's name or IP address. In the Host Port field, it is recommended to leave the existing default communications port. CONFIGURING APPLICATION DELIVERY SERVERS 69
6 Click the Test Connection button to confirm that the Terminal Server can communicate with this host through this port. A success message should be displayed at the bottom of the window, as shown below: 7 Click Finish to close the Host Connection Wizard. The following success window is then displayed: 70 CONFIGURING APPLICATION DELIVERY SERVERS
This window also now shows a new row representing the COCKPIT4 Terminal Server that was added. The window below shows two Controllers (primary and secondary) and two Terminal Servers. Configuring Application Delivery Users This section describes how to define which users can connect COCKPIT4 clients to the COCKPIT4 Controller. Please note, that defining a user in the Application Delivery branch, as described below, does not award that user access to any applications. It only enables the user access to the Controller. To assign applications to a user, the administrator must use the Applications branch, as described in the Configuring Applications section on page 74. To configure Application Delivery users: 1 Select the Application Delivery Users branch, as shown below: CONFIGURING APPLICATION DELIVERY SERVERS 71
2 Right-click in the center of the page and select New or click the New tool. The following window is displayed: 3 Select the relevant user groups or users and click OK. The selected users are then displayed, as follows: Add only one user for testing or add as many user groups and/or users, as required. 72 CONFIGURING APPLICATION DELIVERY SERVERS
Configuring Application Delivery This section describes how to define which users are able to connect to the Controller using COCKPIT4 client. To configure an application delivery user: 1 Select the Application Delivery Users branch, as shown below: 2 Right-click in the center of the page and select New or click the New tool. The following window is displayed: CONFIGURING APPLICATION DELIVERY SERVERS 73
3 Select the relevant user groups or users and click OK. The selected users are then displayed as follows: Add only one user for testing or add as many user groups and/or users, as required. Configuring Applications The Application branch enables you to define the applications that can be accessed by COCKPIT4 client users. To define an application: 1 Select the Application Delivery Application branch, as shown below: 74 CONFIGURING APPLICATION DELIVERY SERVERS
2 Right-click in the center of the page and select New Application or click the New Application tool to display the following window: The following describes how to define the applications that can be accessed by COCKPIT4 client users: General Tab Applications, page 76 Security Tab Applications, page 79 Host Groups Applications, page 83 CONFIGURING APPLICATION DELIVERY SERVERS 75
General Tab Applications This tab provides general definitions of an application. 1 The General tab is shown above. In the General tab, fill in the required information: Application Name: Specifies the name of this application as it appears in the administrator interface and in the COCKPIT4 application panel. Description: Describes the application. Disabled: Uncheck this option. Executable Path: The path to the application installed on the Terminal Server. Use the Browse button to locate the file or type the path and name in the text box. A list of the Terminal Servers defined in the COCKPIT4 site is displayed on the left, as shown below: 76 CONFIGURING APPLICATION DELIVERY SERVERS
Each time you select a Terminal Server on the left, the applications installed on that Terminal Server are displayed on the right, as shown below: It is recommended to work in a COCKPIT4 environment in which all Terminal Servers have the same applications installed on them (this is called a homogenous environment). In this case, you can select any of the Terminal Servers on the left, because they all contain the required application. However, if you are working in a non-homogenous environment in which the Terminal Servers do not all have the same applications installed on them, then you have two options for handling this case, as follows: If the required application is in the same path on each Terminal Server on which it is located, then you must select the Terminal Server on the left that has the required application installed on it in order to display it on the right and then select it. NOTE: By default, COCKPIT4 looks for the application in the same path on all Terminal Servers. If this file is not located in the same path on all servers, then you must create a Delivery Configuration profile. A full description of this feature is provided in the Jetro COCKPIT4 User Guide. CONFIGURING APPLICATION DELIVERY SERVERS 77
Working Directory (Optional): Specifies the path to the working directory used by this application, if required. Use the Browse button to locate the file or type the path and name in the text box. Documents/Parameters (Optional): Add the relevant parameters to the application or the path of a file that opens automatically whenever the application is activated, if required. For example, Microsoft Access database files, Word documents and so on. The file must be published on an identical location on all of the Terminal Servers or on a UNC path routing to a single permanent location. For example, \\Server\Share\Document. This field can specify environment variables. For example, %username% and so on. All standard parameters are supported and should follow standard rules of application parameters. For example, a command that contains spaces must be enclosed by brackets. Please note that in certain applications this string of parameters may be quite long. Icon: Use the Browse button to select or extract an icon that enables the user to activate this application. Icons can be extracted from.exe or.dll files. If the application does not show an icon next to this field, then you can use this option to browse for the icon. NOTE: Every time an application s executable path is added or changed, the icon associated with that path becomes the default icon. If you want to use a different icon, you must update the icon after you change the executable image path. 2 Click Save. 78 CONFIGURING APPLICATION DELIVERY SERVERS
Security Tab Applications This tab enables you to define Security Objects. Each Security Object specifies the users and user groups that are allowed or that are denied access to this application. You can add additional security objects as part of the Security Policy for the application defined in the General tab. Security Policies only define who has access, not how an application appears or functions. 1 Click the Security tab to display the following window: 2 To define a new Security Object, click the New tool to display the following window: The Security Object specifies the users who are able to access the application using the COCKPIT4 client. CONFIGURING APPLICATION DELIVERY SERVERS 79
3 Click the Object Types button to display the following window in which you can specify whether you want to search through Users and/or Groups of users in Active Directory. Click OK. Your selection is then displayed next to the Select this Object Type field. 4 Click the Domains button to display the following window in which you can specify in which registered Domain to search for users. Select a Domain and click OK. Your selection is then displayed next to the Select Domain field. 5 Click the Locations button to display the following window in which you can specify the starting location (directory) in Active Directory for the search. Click OK. Your selection is then displayed next to the From this location field. 80 CONFIGURING APPLICATION DELIVERY SERVERS
6 Click the Check Names button to display the results of the search criteria that you specified in this window. If only one matched object was found, the matching object is shown in the Selected Objects field. If more than one matched object was found, the Multiple Names Found window is displayed, as shown below: Select one or more names in this list or click Cancel to redefine the search. CONFIGURING APPLICATION DELIVERY SERVERS 81
After you click OK, your selection is displayed in the Select Object Types field, as shown below: NOTE: The search is dependent on the selections made in the fields previously described in this window. 7 Click OK. The newly defined Security Object is saved and added as a row to the Security Object area of the Security tab, as shown below: Security Policies only define who has access, not how an application in the group appears or functions. 8 Click OK to set access to this Security Object access and return to the Security tab. 82 CONFIGURING APPLICATION DELIVERY SERVERS
9 Click Save. NOTE: If you want to close this window without saving your changes since the last save, click. When is used, the system does not display any warnings or confirmation windows. You can also use to exit without saving. Host Groups Applications Another way to define which Terminal Servers publish an application is to add Host Groups. To add a Host Group: 1 Click Add/Delete Host Group button, the Select Host Groups window is displayed, as shown below: 2 The left side of this window lists all the Host Groups defined in the COCKPIT4 site. Select the Host Groups to serve this application by moving the relevant Host Groups into the Selected area. CONFIGURING APPLICATION DELIVERY SERVERS 83
Configuring Application Groups Application Groups enable you to organize the applications that appear in users application panels into groups, as shown below: The window above shows one application group called MS Office and four applications. Application Groups provide an easy way of grouping similar typed applications into a single group. For example: all office applications or all accounting applications can be grouped into one group. An application can exist in one or more groups, or it may not exist in any group. When an application is assigned to an Application Group, it may disappear from users application panels and only be displayed to users who have permission to access both the Application Group and the application. Users can be given access to an Application Group even though they have access to only some of the applications in that group. In this case, the Application Group appears on the user s virtual desktop, but it only shows the applications the user is allowed to access when it is opened. If an application is removed from all Application Groups, it is again displayed on the application panel of all users who are allowed to access this application. 84 CONFIGURING APPLICATION DELIVERY SERVERS
Adding Application Groups To add an Application Group: 1 Under the Application Delivery branch, select the Application Groups branch to display a list of all the Application Groups defined in the COCKPIT4 site, as shown below: 2 Right-click the Application Groups branch and select the New Application Group option from the menu. The New Application Group window is displayed, as shown below. NOTE: Alternatively, you can click the New Application Group tool or right click in the center of the page and select New Application Group. CONFIGURING APPLICATION DELIVERY SERVERS 85
Three tabs of information are provided for defining an Application Group, as follows: General Tab Applications Group, below Applications Tab Applications Group, page 87 Security Tab Applications Group, page 88 General Tab Applications Group This tab provides general definitions of an Application Group. 1 The General tab is shown above. In the General tab, fill in the required information: Application Group Name: Specifies the name of this Application Group as it appears in the administrator interface and on the COCKPIT4 application panel. Description: Describes this Application Group. Disabled: Enables you to disable this Application Group so that in no longer appears on users COCKPIT4 application panels. Scheduled Policy: Leave this field as is. 2 Click Save. 86 CONFIGURING APPLICATION DELIVERY SERVERS
Applications Tab Applications Group This tab enables you to define which applications belong to this Application Group. 1 Click the Applications tab to display the following window: 2 The left side of this window lists the applications that have been added to COCKPIT, as described in the Configuring Applications section on page 74. From the Available list on the left, select the applications to be included in this Application Group and then click the button. This moves the select application to the right side of the window into the Selected area. If needed, you can use the Application Group from the Selected list. button to remove an Tip: The Search field can help you find applications in these lists. Enter all or part of the name of an application and click to filter the list to show only those applications that contain this string. Click to clear the filter in the window and show all available applications. 3 Click Save. CONFIGURING APPLICATION DELIVERY SERVERS 87
Security Tab Applications Group This tab enables you to create Security Objects that define the users on whose COCKPIT4 application panels this Application Group (folder of applications) appears. This window helps you search, filter and select users and groups of users from an Active Directory window. The options in this tab are similar to the Security tab provided for defining applications. You may refer to the Security Tab Applications section on page 79 for a description. 88 CONFIGURING APPLICATION DELIVERY SERVERS
6CHAPTER 4 SETTING UP APPLICATION DELIVERY CLIENTS This chapter describes how to install t describes how to install and use the Jetro Application Delivery Client on a user s computer. This chapter contains the following sections: Application Delivery Client Prerequisites, page 90 Installing the Application Delivery Client, page 90 Logging into the COCKPIT4 Client, page 97 Uninstalling the Application Delivery Client, page 99 SETTING UP APPLICATION DELIVERY CLIENTS 89
Application Delivery Client Prerequisites This section describes the prerequisites for installing an Application Delivery client. A COCKPIT4 client can be installed on all standard Windows-based computers running Windows 98 and above. Installing the Application Delivery Client The Application Delivery Client can be installed using a simple wizard, as described below: To install the Application Delivery client using the wizard: 1 Double-click the Client Setup program called JDs-CockpitClient.msi. The InstallShield Wizard starts preparing to install the client, as shown below: 90 SETTING UP APPLICATION DELIVERY CLIENTS
2 Click Next to display the following window: SETTING UP APPLICATION DELIVERY CLIENTS 91
3 Accept the terms of the license agreement and click Next to display the following window: 4 Click Next to display the following window: 92 SETTING UP APPLICATION DELIVERY CLIENTS
5 Click OK to display the following window: 6 Click Install to begin the installation. SETTING UP APPLICATION DELIVERY CLIENTS 93
7 After the InstallShield Wizard Completed window is displayed, click Finish. After the installation procedure has successfully installed the JSB client to your computer, the following desktop icon is displayed: 94 SETTING UP APPLICATION DELIVERY CLIENTS
8 Double-click the COCKPIT4 desktop icon. The following window is displayed enabling you to connect to the COCKPIT4 Controller: 9 Enter the name of the Primary Controller in the Host field. Use the actual name of the Primary Controller machine. In the Host field, specify the name of the Controller. An example is shown below. This is the name that was defined in the All Hosts List. For example, as shown below: 10 In the Port field, specify the port of the Controller. Do not select the Secure Connector checkbox option. SETTING UP APPLICATION DELIVERY CLIENTS 95
11 Click OK. 12 Wait a few moments while the COCKPIT4 client searches for the Controller. The Login window is then displayed, as shown below: 13 Enter the User name and Password that was assigned by the COCKPIT4 system administrator in the Application Delivery Users branch. 96 SETTING UP APPLICATION DELIVERY CLIENTS
Logging into the COCKPIT4 Client By default, the Login window is only displayed the first time that a COCKPIT4 client connects to a Controller. However, the administrator can define that this login window is displayed every time the COCKPIT4 client is launched. The password is save/encrypted with the user s local profile. To login to the COCKPIT4 Client: 1 Double-click the COCKPIT4 desktop icon. The Login window is then displayed, as shown below: 2 Enter the User name and Password that was assigned by the COCKPIT4 system administrator in the Application Delivery Users branch. The application panel is then displayed, as shown below: SETTING UP APPLICATION DELIVERY CLIENTS 97
The pane on the left displays a tree whose root is the COCKPIT4 farms. The branches under it are the Terminal Servers of each farm and the branches under that are the applications running on each Terminal Server. 3 You can double-click an application icon to launch that application. You can also double-click a group to see the applications that it contains and then double-click an application icon to launch that application. The first time you launch an application from this client on each Terminal Server, a progress bar is displayed on the bottom of this window requesting that you wait few moments while a session is opened between this client and the Terminal Server. The next time you run another application from this client on the same Terminal Server, this message is not displayed because the same session will be used. When you exit an application, the session between this client and this Terminal Server remains open. However, if no application is open for a certain amount of time (the default is 1 minute) with this Terminal Server, then a timeout occurs and the Terminal Server session is closed. The branch of the Terminal Server is then removed from the tree. When an application is closed, it is removed immediately from the tree on the left. 98 SETTING UP APPLICATION DELIVERY CLIENTS
Exiting the COCKPIT4 Client Before exiting the COCKPIT4 client, you should save all documents and close all applications. To exit the COCKPIT4 client: Click the tool in the application panel or right-click on the icon in the tray and select the Exit option. The following message is then displayed: You can click the icon in the application panel to minimize it. You can then redisplay the application panel by right-clicking on the tray and selecting the Restore option. icon in the Uninstalling the Application Delivery Client To uninstall the Application Delivery client, use the Add/Remove Programs utility in the Windows Control Panel. SETTING UP APPLICATION DELIVERY CLIENTS 99