Before you Begin

This manual is for system administrators responsible for installing, configuring, and maintaining the Citrix ICA Client for Java (also called the Citrix ICA Java Client). This manual assumes knowledge of:

Citrix MetaFrame Application Server for Windows or Citrix WinFrame

The operating system on the client computer

Java Virtual Machines (JVMs) or Java-enabled Web browsers

Installation, operation, and maintenance of network and printing hardware


How to Use this Guide

To get the most out of the Citrix ICA Client Administrator's Guide, review the table of contents to familiarize yourself with the topics discussed.

This guide contains the following sections:

Chapter	Contents
Chapter 1, "Introduction to the Citrix ICA Java Client"	Gives a list of features and system requirements.
Chapter 2, "Installing the Citrix ICA Java Client"	Describes how to install the Citrix ICA Java Client.
Chapter 3, "Configuring the Citrix ICA Java Client"	Describes how to start and configure connections to Citrix servers.


Conventions

The following conventional terms, text formats, and symbols are used throughout the printed documentation:

Convention	Meaning
Bold	Indicates boxes and buttons, column headings, command-line commands and options, icons, dialog box titles, lists, menu names, tabs, and menu commands.
Italic	Indicates a placeholder for information or parameters that you must provide. For example, if the procedure asks you to type filename, you must type the actual name of a file. Italic also indicates new terms and the titles of other books.
ALL UPPERCASE	Represents keyboard keys (for example, CTRL, ENTER, F2).
[brackets]	Encloses optional items in syntax statements. For example, [password] indicates that you can choose to type a password with the command. Type only the information within the brackets, not the brackets themselves.
...(ellipsis)	Indicates a command element can be repeated.
Monospace	Represents examples of screen text or entries that you type at the command line or initialization files.
	Indicates a procedure with sequential steps.
•	Indicates a procedure with only one step.
	Indicates a list of related information, not procedural steps.
The Citrix ICA Clients allow users to connect to MetaFrame servers and WinFrame servers. When describing a feature or procedure common to MetaFrame and WinFrame servers, this manual uses the term Citrix server. When describing a feature unique to a MetaFrame or WinFrame server, this manual specifies either a MetaFrame or WinFrame server.


Finding More Information

This manual contains conceptual information and installation and configuration steps for the Citrix ICA Java Client. For additional information, consult the following sources:

The Citrix ICA Client Administrator's Guides for the ICA DOS, Win16, Win32, Web, Macintosh, and UNIX Clients.

For instructions on installing, configuring, and maintaining your Citrix servers, see the documentation included in your MetaFrame or WinFrame package.

This manual and other Citrix documentation is available in Adobe PDF format in the documentation directory of your MetaFrame or WinFrame CD-ROM. Using the Adobe Acrobat Reader, you can view and search the documentation electronically or print it for easy reference. To download the free Adobe Acrobat Reader, please visit Adobe's Web site at http://www.adobe.com.

Important  Consult the Readme.txt files for MetaFrame, WinFrame, and the Citrix ICA Clients for any last-minute updates, installation instructions, and corrections to the documentation.


Citrix on the World Wide Web

Citrix offers online Technical Support Services at http://www.citrix.com that include the following:

Downloadable Citrix ICA Clients, available at http://download.citrix.com

A Frequently Asked Questions page with answers to the most common technical issues

An FTP server containing the latest service packs and hotfixes for download

An Online Knowledge Base containing an extensive collection of technical articles, troubleshooting tips, and white papers

Interactive online support forums


Year 2000 Readiness

For a detailed description of the Year 2000 Readiness of Citrix products, see our Web site at http://www.citrix.com/misc/y2000.htm.


Introduction to the Citrix ICA Java Client
Chapter 1 - Introduction to the Citrix ICA Java Client

The Citrix ICA Java Client lets you access a Citrix WinFrame or MetaFrame server from a Java virtual machine (JVM). The JVM can be a PC running a JVM, a Java-based device, or a Web browser that supports Java applets.


Application and Applet Modes

The Citrix ICA Java Client can be used in one of two modes: applet mode or application mode. In applet mode, the ICA Java Client resides on a Web server. Users initiate remote control sessions on the Citrix server by using a browser that has Java support to access an HTML page that has a reference to the ICA Java Client applet tag. When run in applet mode, the ICA Java Client is also called the Java Web Client. In application mode, the ICA Java Client resides on a client system that has an installed JVM. Connections to a Citrix server are usually initiated by executing the ICA Java Client from the command line (with the exception of Macintosh client systems, which have no command line).

In general, the ICA Java Client mode used depends upon the type of access client system users need. From the client system user's point of view, application mode is the more flexible method of launching remote control sessions. Application mode sessions run in their own window on the local desktop. Users can specify command line parameters when invoking sessions to control such ICA Java Client features as event logging, client printing, hotkeys, window resolutions, initial programs, and server addresses.

In applet mode, client system users launch sessions that are embedded in an HTML page on a Web browser. All of the command line parameters available to application mode users are not available to the applet mode user; usually, only those users with write access to the Web server can edit the HTML page that contains the ICA Java Client applet tag and its parameters. For this reason, applet mode sessions offer more control to the network administrator than the client system user and may be preferable when administrators want to relieve client system users of the mechanics of launching sessions.

Although both applet and application modes use the same set of class files and support the same functionality, this manual discusses them separately when procedures are specific to the mode used.


Citrix ICA Java Client Features

This release of the ICA Java Client supports the following features:

Video resolutions up to 1280 x 1024

256 color ICA sessions only

Client printer mapping for printers attached to client COM and LPT ports

Event logging

Hotkeys

Shadowing

International keyboard support

Multiple locale support

Basic encryption

Load balancing

Application publishing


Citrix ICA Java Client Requirements

To run the ICA Java Client as an applet, the client system must have the following:

A Web browser with Java Development Kit (JDK) 1.1 or higher Java support

TCP/IP (Dial-up or LAN)

VGA or equivalent display

Mouse

Access to a Web server that will store the ICA Java Client files

To run the ICA Java Client as an application, the client system must have the following:

Java virtual machine (JVM), Version 1.1 or greater

TCP/IP (Dial-up or LAN)

VGA or equivalent display

Mouse


Java 1.1 Compliance

The Citrix ICA Java Client is fully JDK-1.1-compliant. To run the ICA Java Client you must have a JVM or Java-enabled Web browser that fully supports JDK 1.1.

To support client systems using non-1.1-compliant JVMs or browsers (such as Internet Explorer 3.x or below or Netscape Navigator 3.x or below), you must use the JDK-1.0-compliant version of the Citrix ICA Java Client. The JDK-1.0- compliant Citrix ICA Java Client is available from the Citrix Web site at http://www.citrix.com.


Browser Compatibility

The Citrix ICA Java Client has been tested with various browsers and client systems. The following list describes some browser and platform combinations that have been tested and approved for use with the ICA Java Client as an applet:

Browser	Platforms
Microsoft Internet Explorer 4.0x	Windows 95, Windows NT 4.0, Macintosh, and Solaris 2.6
Netscape Navigator 2.02 for OS/2	OS/2 Warp 4.0
Netscape Communicator 4.05 with AWT 1.1 support and Netscape Communicator 4.06+	Windows 95, Windows NT 4.0, Macintosh, and Solaris 2.6
HotJava Browser 1.1	Windows 95, Windows NT 4.0, Solaris 2.6, and JavaOS for Business
HotJava Views	Sun JavaOS


Tested JVMs

The Citrix ICA Java Client has been tested with several JDKs and client systems. The following list describes some JDK and platform combinations that have been tested and approved for use with the ICA Java Client as an application:

Solaris 2.6 - Sun JDK 1.1.5

Mac OS 8 - Apple MRJ 2.0.1

Windows 95 and Windows NT 4.0 - Sun JDK 1.1.5, 1.1.6, and 1.1.7B; Microsoft JVM 1.1

OS/2 Warp 4.0 - IBM JDK 1.1.4

JavaOS for Business 2.0, 2.1 - IBM JDK 1.1.6

Sun JavaStation Server - Sun JDK 1.1.6


Installing the Citrix ICA Java Client
Chapter 2 - Installing the Citrix ICA Java Client

This chapter explains how to install the Citrix ICA Java Client as an applet and as an application on various platforms.

This chapter also explains how to uninstall the ICA Java Client.


Tasks to Complete

In this chapter you will complete the following tasks.

Applet mode installations:

Install the ICA Java Client on your Web server—(5 minutes)

Create a Web page users can visit to launch the ICA Java Client—(10 minutes)

Application mode installations:

Install the ICA Java Client on each client machine—(5 minutes per machine)

Macintosh users must create a Macintosh launching script—(5 minutes)

JavaStation Server users must configure the JavaStation server to serve the ICA Java Client to its client systems—(20 minutes)

JavaOS for Business Server users must configure the JavaOS for Business server to serve the ICA Java Client to its client systems. See Configuring the JavaOS for Business Server 2.0 or Configuring the JavaOS for Business Server 2.1—(20 minutes)


Installation

Due to the ICA Java Client's support for multiple platforms and its ability to function in both application and applet modes, the installation procedures for the ICA Java Client must account for a wide range of operating systems, hardware, and intended usage. With the exception of a common first step, applet and application mode installations differ and are described separately in this help. The following procedure describes the first step of both applet and application installations.


Copying the Installation Files to Your Web Server

Depending on the language version of MetaFrame or WinFrame you purchased, the \Icaclnt\Icajava directory on your CD-ROM contains one of the following sets of installation files:

setup.class: This setup program is a Java application that you can run to install the ICA Java Client 4.02 on any client system or Web server that has an installed Java virtual machine (JVM).

JavaEnt.sea.hqx, JavaEnt.tar.gz, JavaEnt.zip: These files are simple archives containing the ICA Java Client 4.02 files.

In addition to these installation archives, the \Icaclnt\Icajava directory contains download.htm. This HTML document contains a hyperlink or hyperlinks to the ICA Java Client installation file(s) in the \Icaclnt\Icajava directory. If you are installing the ICA Java Client as an application, multiple client users can visit this page to download the appropriate ICA Java Client setup archive for individual application mode installations.

To copy the installation files to your Web server

•	Both applet and application mode installations require the installation files be placed in a location accessible to all client systems. Copy the contents of the \Icaclnt\Icajava directory to your Web server's Web root directory. For your convenience, you can create a separate directory in your Web server's Web root directory for the files. For example, create a directory called \JICA in the Web root directory and copy the files into \JICA. If you are installing the ICA Java Client as an application, make sure you copy both download.htm and the ICA Java Client installation archive(s) to the same directory on the Web server. If you are installing the ICA Java Client as an applet only, you will not need to copy download.htm to the Web server.

Note   The application mode installation procedure described in this chapter facilitates installing the ICA Java Client on multiple client systems. When installing the ICA Java Client on a limited number of client systems, it may be more convenient to simply copy the installation archive by some method of file transfer to your client systems and then proceed with installation. See Application Installation for information on uncompressing an installation archive after copying it to a client system.


Applet Installation

Unlike ActiveX controls and Netscape plug-ins, which are downloaded once and then saved for future use by client systems, Java applets are not stored by client systems and must be downloaded each time they are used. To execute the ICA Java Client in applet mode, the client system must be able to download the ICA Java Client class files from the Web server.

Note   See Copying the Installation Files to Your Web Server above before performing the following procedure.

Use the following procedure to make the class files accessible to client systems:

To install the ICA Java Client as an applet

1.	Create a directory off the Web server's Web root directory. For example, create a directory named \APPLET.

2.	If the \Icaclnt\Icajava directory on your CD-ROM contains JavaEnt.zip, JavaEnt.sea.hqx, and JavaEnt.tar.gz, extract one of these installation files into the directory created in Step 1. Use a decompression utility and the archive appropriate for the platform of your Web server: if the Web server resides on a Windows-based computer, extract JavaEnt.zip; if the Web server is UNIX-based, extract JavaEnt.tar.gz; if the Web server resides on an Apple Macintosh computer, extract JavaEnt.sea.hqx. Extracting the compressed installation file yields the ICA Java Client archives. These archives contain the ICA Java Client class files.

If the \Icaclnt\Icajava directory on your CD-ROM contains setup.class, use the JVM installed on your Web server to run setup.class. See Running setup.class for more information on executing this Java setup program on various platforms.

3.	Create an HTML page that users can access to initiate sessions on the Citrix server. Place this HTML page in the directory you created in Step 1. See Creating a Web Page for Applet Mode Installations for more information.


Application Installation

Note   See Copying the Installation Files to Your Web Server above before performing the following procedure.

To download and install the ICA Java Client

1.	Make sure the client system is properly configured and connected to the network.

2.	Start a Web browser. In the browser's address field, enter the IP address or DNS name of the Web server containing the ICA Java Client files, followed by the name of the ICA Java Client setup HTML file (download.htm). For example, if you copied the ICA Java Client installation files into a directory named /JICA on a Web server with IP address 126.4.2.7, enter http://126.4.2.7/JICA/download.htm. The ICA Java Client setup HTML page appears.

3.	If the \Icaclnt\Icajava directory on your CD-ROM contains JavaEnt.zip, JavaEnt.sea.hqx, and JavaEnt.tar.gz, then download.htm contains a link to each of these installation archives. Click the link corresponding to the desired client platform. Save the file to the client system's hard drive. You can create a directory named "Citrix" on the client computer and save the file to this directory. Then use a decompression utility to extract the installation archive. Extracting the installation file yields the ICA Java Client archives. These archives contain the ICA Java Client class files.

If the \Icaclnt\Icajava directory on your CD-ROM contains setup.class, click the link to setup.class in download.htm and save the file to the client system's hard drive. You can create a directory named "Citrix" on the client computer and save the file to this directory. Then use the JVM installed on the client system to run setup.class. See Running setup.class for more information on executing this Java setup program on various platforms.

4.	After you uncompress the installation archive or run setup.class, installation is complete for Windows, UNIX, and OS/2 client systems. For instructions on how to start the ICA Java Client in application mode, see Using the ICA Java Client as an Application.

Macintosh users may see an error message warning that some batch files were not created during installation. The batch file that cannot be created is a launching script used to automate starting the ICA Java Client in application mode. Macintosh users can create this batch file manually using the procedure in Creating a Macintosh Launching Script.

Application mode installations on JavaStation Servers and JavaOS for Business Servers require additional configuration, covered in Configuring the JavaOS for Business Server 2.0, Configuring the JavaOS for Business Server 2.1, and Configuring the JavaStation Server.

Note   If the operating systems of the Web server or the client systems do not support long filenames, you must rename the compressed installation files and edit the links in the download.htm file.


Running setup.class

The following procedures describe how to run setup.class on different platforms:

To run setup.class on a Windows PC

1.	Start a command prompt. On Windows 95, click Start and then click Run. In the Run dialog box, type command and press ENTER. On Windows NT 4.0, click Start and then click Run. In the Run dialog box, type cmd and press ENTER.

2.	Insert the CD-ROM in the CD-ROM drive. At the command prompt, type cd x:, where x is the letter of your CD-ROM drive. Press ENTER.

3.	Type cd icaclnt\icajava and press ENTER.

4.	Type x jvmpgm setup, where x is the full path of your JVM program and jvmpgm is the JVM program's name. Press ENTER. For example, if you use the Microsoft JVM program Jview and it is located in a directory called C:\Windows\, type c:\windows\jview setup. The ICA Java Client installation wizard appears.

To run setup.class on a UNIX system

1.	Log in as root.

2.	Start a shell.

3.	Insert the CD-ROM in the CD-ROM drive and mount the CD.

4.	Change to the /ICACLNT/ICAJAVA directory on the CD-ROM.

5.	Type x jvmpgm setup, where x is the full path of your JVM program and jvmpgm is the JVM program's name. Press ENTER. For example, if you use Sun's JVM program Java and it is located in a directory called /usr/bin, type /usr/bin/java setup. The ICA Java Client installation wizard appears.

To run setup.class on an OS/2 system

1.	Start an OS/2 command prompt. From the Start menu, point to OS/2 System and then point to Command Prompts. Click OS/2 Window.

2.	Insert the CD-ROM in the CD-ROM drive. At the command prompt, type cd x:, where x is the letter of your CD-ROM drive, and press ENTER.

3.	Type cd icaclnt\icajava and press ENTER.

4.	Type x jvmpgm setup, where x is the location of your JVM program and jvmpgm is the JVM program's name. Press ENTER. For example, if you use IBM's JVM program Java and it is located in a directory called C:\Java11, type
c:\java11\java setup. The ICA Java Client installation wizard appears.

To run setup.class on the JavaOS for Business Server

1.	Copy the ICA Java Client installation file setup.class from the installation media to some directory on your JavaOS for Business Server.

2.	Start a command prompt. On the JavaOS for Business Server, click Start, Programs, and then click Command Prompt.

3.	Change to the directory where you saved setup.class. At the command prompt, type cd x:, where x is the drive and path to setup.class

4.	Type x jvmpgm setup, where x is the full path of your JVM program and jvmpgm is the JVM program's name. Press ENTER. For example, if you use IBM's JVM program Java and it is located in a directory called C:\Java11, type c:\java11\java setup. The ICA Java Client installation wizard appears.

To run setup.class on a JavaStation Server

1.	Log in as root.

2.	Start a shell.

3.	Insert the CD-ROM in the CD-ROM drive and mount the CD.

4.	Change to the /ICACLNT/ICAJAVA directory on the CD-ROM.

5.	Type x jvmpgm setup, where x is the full path of your JVM program and jvmpgm is the JVM program's name. Press ENTER. For example, if you use Sun's JVM program Java and it is located in a directory called /usr/bin, type /usr/bin/java setup. The ICA Java Client installation wizard appears.

To run setup.class on a Macintosh system

1.	Insert the CD-ROM in the CD-ROM drive. Double-click the CD-ROM icon on your desktop.

2.	Double-click the ICACLNT folder and then double-click the ICAJAVA folder.

3.	Drag setup.class onto the JVM application on your desktop. For example, if you use the Macintosh JVM JBindery 2.0, drag setup.class onto JBindery 2.0 on the desktop.

4.	Execute setup.class. For example, in JBindery 2.0, click Run.

The ICA Java Client installation wizard appears. When using this wizard, make sure you change the destination folder to some location on the client system's hard drive; for example, /Hard%20Disk/Citrix/JavaClient.


Creating a Macintosh Launching Script

Macintosh users can create their own client launching file with the following procedure:

To create a Macintosh launching script

1.	Open the folder where you installed the Citrix ICA Java Client.

2.	Open the JVM program, JBindery 2.0.

3.	From the list of icons on the left of the JBindery dialog, click Command.

4.	In the Class Name field, type com.citrix.JICA

5.	In the Optional Parameters field, add the following parameter:
-address:CitrixServer, where CitrixServer is the name of a Citrix server to which you want to connect.

6.	In the list of icons on the left, click Classpath.

7.	Drag JICAEngJ.jar from the Citrix ICA Java Client installation folder onto the Additions to class path field. The file name appears in the field. Click Save Settings. You can create a folder on your desktop called Citrix Files and save the icon there. Enter a name for the launching file in the Save Settings field. Make sure Save as Application is checked. Click Save.

8.	Click Quit. To run the ICA Java Client, double-click the icon you created.

Note   You may want to run the ICA Java Client using the GUI Command Line feature. To use the GUI Command Line feature, create a script using the procedure above but instead of adding the -address:CitrixServer parameter and value, add the parameter -guicmdline in the Optional Parameters field. When you run this script, a dialog box appears that allows you to enter parameters to pass to the ICA Java Client. Type the address parameter and any other optional parameters in the dialog box and click Run. By doing this you avoid having to edit the launching file whenever you want to specify different command line parameters.


Configuring the JavaOS for Business Server 2.0

The following procedure describes how to set up the JavaOS for Business Server 2.0 to serve the ICA Java Client to its client systems. This procedure involves creating a specially formatted zip file that contains the ICA Java Client and then using the JCT tool to configure this file as the application client systems load.

To configure the JavaOS for Business Server 2.0

1.	Create the application zip file:

A.	On the JavaOS for Business Server, start a command prompt.

B.	Change to the directory where you installed the ICA Java Client. Make sure this directory contains the file JICAEngJ.jar.

C.	Type mkdir classes to create a directory called "classes" in the ICA Java Client installation directory.

D.	Type copy JICAEngJ.jar classes to copy JICAEngJ.jar to the classes directory.

E.	Use a compression utility, such as WinZip or PKZIP, to create a zip file named "jica.zip". Jica.zip must contain at its root the directory "classes" and the classes directory must contain JICAEngJ.jar. JavaOS for Business requires jica.zip be created with this specific configuration in order to load the ICA Java Client using the Application Load Settings file.

F.	Place jica.zip in the directory where you store the other application zip files (such as hotjava.zip) used by client systems.

2.	Start the JSD on the JavaOS for Business Server. Use Startjsd.bat to start the JSD if it is not already running.

3.	Start the JavaOS Configuration Tool (JCT) on the JavaOS for Business Server. Use Startjct.bat to start the JCT if it is not already running.

4.	In the JCT, select Users or Groups and then click Edit.

5.	In the Available list, select Application Load Settings. Click Add. The Application Load Settings dialog box appears. Enter the following values in the fields:

A.	In Service URL, type file:/SERVICES/AppLoad.jar, where SERVICES is the NFS mount point where the loadable services are located. You can change the path SERVICES as necessary, but not the service name (AppLoad.jar).

B.	In Main class, type com.citrix.JICA.

C.	In Location of ZIP file, type file:/APPS/jica.zip, where APPS is the NFS mount point where jica.zip is located.

Note   If you have not defined an NFS mount point for this directory, please follow the directions in JavaOS for Business Installation and Planning.

D.	In URL base path, leave the field blank (delete any value that appears in the field).

E.	In Application home property, leave the field blank (delete any value that appears in the field).

F.	In Startup arguments, type -address:CitrixServer, where CitrixServer is the name of the Citrix server to which you are connecting. Entering this parameter causes the ICA Java Client to immediately connect to the specified Citrix server when the client system loads jica.zip. Alternately, leave this field blank to run the ICA Java Client GUI Command Line. When jica.zip is loaded, the GUI Command Line dialog box appears so the user can enter connection parameters including server address.

6.	Click Save to exit the Application Load Settings dialog box.

7.	Reboot the client system and login as the modified user to load the Citrix ICA Java Client.

For more information, see JavaOS for Business Network Operations.


Configuring the JavaOS for Business Server 2.1

The following procedure describes how to set up the JavaOS for Business Server 2.1 to serve the ICA Java Client to its client systems. This procedure involves creating a specially formatted zip file that contains the ICA Java Client and then using the JCT tool to configure this file as the application client systems load.

To configure the JavaOS for Business Server 2.1

1.	Create the application zip file:

A.	On the JavaOS for Business Server, start a command prompt.

B.	Change to the directory where you installed the ICA Java Client. Make sure this directory contains the file JICAEngJ.jar.

C.	Type mkdir classes to create a directory called "classes" in the ICA Java Client installation directory.

D.	Type copy JICAEngJ.jar classes to copy JICAEngJ.jar to the classes directory.

E.	Use a compression utility, such as WinZip or PKZIP, to create a zip file named "jica.zip". Jica.zip must contain at its root the directory "classes" and the classes directory must contain JICAEngJ.jar. JavaOS for Business requires jica.zip be created with this specific configuration in order to load the ICA Java Client using the Application Load Settings file.

F.	Place jica.zip in the directory where you store the other application zip files (such as hotjava.zip) used by client systems.

2.	Start the JSD on the JavaOS for Business Server. Use Startjsd.bat to start the JSD if it is not already running.

3.	Start the JavaOS Configuration Tool (JCT) on the JavaOS for Business Server. Use Startjct.bat to start the JCT if it is not already running.

4.	In the JCT, select Users or Groups and then click Edit.

5.	In the Available list, select Application Load Settings. Click Add. The Application Load Settings dialog box appears. Enter the following values in the fields:

A.	In Service URL, type file:/SERVICES/AppLoad.jar, where SERVICES is the NFS mount point where the loadable services are located. You can change the path SERVICES as necessary, but not the service name (AppLoad.jar).

B.	In Main class, type com.citrix.JICA.

C.	In Base Classpath URL, type file:/APPS/jica.zip, where APPS is the NFS mount point where jica.zip is located.

Note   If you have not defined an NFS mount point for this directory, please follow the directions in JavaOS for Business Installation and Planning.

D.	In Package Names, leave the field blank (delete any value that appears in the field).

E.	In Startup arguments, type -address:CitrixServer, where CitrixServer is the name of the Citrix server to which you are connecting. Entering this parameter causes the ICA Java Client to immediately connect to the specified Citrix server when the client system loads jica.zip. Alternately, leave this field blank to run the ICA Java Client GUI Command Line. When jica.zip is loaded, the GUI Command Line dialog box appears so the user can enter connection parameters including server address.

6.	Click Save to exit the Application Load Settings dialog box.

7.	Reboot the client system and login as the modified user to load the Citrix ICA Java Client.

8.	For more information, see JavaOS for Business Network Operations.


Configuring the JavaStation Server

The following procedure describes how to set up the JavaStation server to serve the ICA Java Client to its client systems. This procedure involves creating a specially formatted jar file that contains the ICA Java Client and then using the NetraJ 2.0 server software to configure this file as the application client systems load.

To configure the NetraJ 2.0 Server software

1.	Create the application jar file:

A.	On the NetraJ 2.0 Server, start a shell.

B.	Change to the directory where you installed the ICA Java Client. Make sure this directory contains the file JICAEngJ.jar.

C.	Type mkdir classes to create a directory called "classes" in the ICA Java Client installation directory.

D.	Change to the classes directory, (type cd classes). Type jar -xvf ..\JICAEngJ.jar to extract the file JICAEngJ.jar.

E.	Change to the directory above classes (type cd ..).

F.	Create a jar file named "jica.jar" by typing jar -cvf jica.jar classes. Jica.jar must contain at its root the directory "classes" and the classes directory must contain ICA Java Client class files. JavaOS requires jica.jar be created with this specific configuration in order to load the ICA Java Client as an application.

G.	Place jica.jar in the directory that is accessible to the HTTP server where you store the other application jar files (such as Views.jar) used by client systems.

2.	In NetraJ 2.0 Network Computer Server Administration, select Client Application Administration under the Advanced NC Server Administration section, and then click Add.

3.	Enter the following values in the fields:

A.	In Application Name, type a title such as CitrixJICA to appear in an application menu item.

B.	In Main Class of the Application, type com.citrix.JICA.

C.	In Application Archive (ZIP) Path, type http://server/appsdir/jica.jar, where server is the server name and appsdir is the path where jica.jar is located. For example, if jica.jar is located on an HTTP server named \\Webserver in the /netra/hjv/classes directory off the Web server's root directory, type http://Webserver/netra/hjv/classes/jica.jar.

D.	In Home Property of the Application, enter null.

E.	In Application Startup options, type -address:CitrixServer, where CitrixServer is the name of the Citrix server to which you are connecting. Entering this parameter causes the ICA Java Client to immediately connect to the specified Citrix server when the client system loads jica.zip. Alternately, type -guicmdline to run the ICA Java Client GUI Command Line. When jica.jar is loaded, the GUI Command Line dialog box appears so the user can enter connection parameters including server address.

F.	Click OK to accept the changes and exit the Client Application Administration page.

4.	In NetraJ 2.0 Network Computer Server Administration, select Network Computer Administration under the Network Computers Administration section, and then click Modify for the respective network computer.

A.	In Default Application, select the name you entered previously in Application Name (in this example, CitrixJICA).

B.	Click OK to accept the changes and exit.

5.	Reboot the client system and log on as the modified user to load the Citrix ICA Java Client.

For more information, see the NetraJ 2.0 Administrator's Guide.


Creating a Web Page for Applet Mode Installations

After running setup.class to install the ICA Java Client on your Web server, you must create an HTML page that client system users can visit to initiate ICA sessions. Use the following procedure:

To create an HTML page that users can visit to launch the ICA Java Client in applet mode

•	Create an HTML page like the example below and place the file in the Web server's Web root directory with the ICA Java Client program files:

<html>

<body>

<applet code=com.citrix.JICA.class

codebase=http://webserver/directory

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

The parameters that need to be modified for your environment are:

Codebase. The codebase parameter is a URL that specifies the location of the ICA Java Client class files. This parameter is necessary only if the class files and the HTML page are located in different directories or on different Web servers. You do not need to specify this parameter if the class files and the HTML page are in the same directory on the Web server. For example, if the HTML page is in the \Page directory on the Web server and the ICA Java Client class files are in the \Applet subdirectory of the Web server Web root directory, enter codebase=/Applet. If the class files and the HTML page used to access the ICA Java Client are located on different Web servers, enter the full URL of the class files; for example, codebase=http://icasrv/jclient

Archive. The archive parameter specifies the name of the archive containing the ICA Java Client class files to use. Different browsers support different archives, and more than one archive can be specified (separate multiple archives with a comma and no spaces). See Using the ICA Java Client as an Applet for information on which archives work with several popular Web browsers.

Address. The address parameter specifies the name or network address of the Citrix server that will host the remote control session.

See Using the ICA Java Client as an Applet for more information on configuring the ICA Java Client for applet mode use. See ICA Java Client Parameters in Chapter 3, "Configuring the ICA Java Client" for a list of the parameters that can be used with the ICA Java Client.


Uninstalling the ICA Java Client

The way you uninstall the ICA Java Client depends upon the archive you used to install the client. The sections that follow describe how to uninstall the ICA Java Client installed using either setup.class or JavaEnt.zip, JavaEnt.sea.hqx, or JavaEnt.tar.gz.

Setup.class Installations

If you used the archive setup.class to install the ICA Java Client, your installation includes an uninstall program that you can use to remove the ICA Java Client application from individual client computers. The uninstall program does not apply to client computers that use the ICA Java Client in applet mode. The uninstall program removes all ICA Java Client files from the client system.

To uninstall the ICA Java Client application from a Windows, UNIX, OS/2, or JavaOS for Business client system

1.	Start a command prompt. (For JavaOS for Business installations, this procedure is done on the JavaOS for Business server.)

2.	Change to the directory where the ICA Java Client was installed.

3.	Type x jvmpgm uninstall at the command prompt, where x is the full path of your JVM program and jvmpgm is the JVM program's name. For example, if you use the Microsoft JVM program Jview and it is located in a directory called C:\Windows\, type c:\windows\jview uninstall. The ICA Java Client uninstall wizard appears. Follow the directions on your screen.

To uninstall the ICA Java Client from a Macintosh client system

1.	Locate the directory where the ICA Java Client was installed.

2.	Drag uninstall.class onto the JVM application on your desktop. For example, if you use the Macintosh JVM program JBindery 2.0, drag uninstall.class onto JBindery 2.0 on the desktop.

3.	Execute uninstall.class. For example, in JBindery 2.0, click Run. The ICA Java Client uninstall wizard appears. Follow the directions on your screen.

JavaEnt.zip, JavaEnt.sea.hqx, and JavaEnt.tar.gz Installations

To uninstall application mode installations of the ICA Java Client, delete all files in the ICA Java Client installation directory. Applet mode use requires no uninstallation on the client machines.


Configuring the Citrix ICA Java Client
Chapter 3 - Configuring the Citrix ICA Java Client

This chapter describes how to configure and start the ICA Java Client for applet and application mode installations on various platforms.


Tasks to Complete

In this chapter you will complete the following tasks.

Applet mode installations:

Choose an appropriate archive for applet mode use—(5 minutes)

Application mode installations:

Start the ICA Java Client in application mode—(5 minutes)

This chapter also describes some optional session customization tasks:

 Specifying parameters

Starting the ICA Java Client in a specific national language

Configuring printers

Configuring event logging

 Configuring keyboard support

Configuring hotkeys

Specifying Ini files on the command line


Using the ICA Java Client as an Applet

The last step of ICA Java Client setup is to configure your HTML pages to accommodate the requirements of the client systems that will download and run the ICA Java Client. When tailoring the HTML pages, there are two major considerations: which Java class file archives are supported by users' browsers and how to handle Java network security restrictions. Both issues are addressed by selecting the proper Java class file archive for your particular network setup.

Once the ICA Java Client is properly installed and configured, using it involves simply opening a browser and clicking the link in the HTML page to start an ICA session.


ICA Java Client Components

Because different implementations of the Java virtual machine (JVM) support different ways of storing class files, the ICA Java Client presents the class files in three different archive formats. When running the ICA Java Client in either application or applet mode, use an archive format supported by your JVM or the JVM of your Web browser. If your JVM does not support any of these archive formats, the ICA Java Client can also be run in application and applet mode from the extracted class files. Use the appropriate utility to extract the class files from an archive. A detailed description of the files follows:

JICAEngM.cab. A signed cabinet (cab) file containing the ICA Java Client class files. This file can be used with any browser that supports running Java programs from cab files. Using a signed archive allows applet mode users running Internet Explorer 4.x or greater to work around the Java network security restriction that prevents users from connecting to other computers on the network and/or writing files to the client's hard disk. Using this archive allows client system users to connect to a Citrix server that is not the same machine as the Web server, write log files to the client's drive, and print to the client's printers. (Internet Explorer users must set their safety level for active content to Medium to use the cab archive.)

JICAEngJ.jar. A signed jar file containing the ICA Java Client class files. This file can be used with any browser or JVM that supports running Java programs from jar files. Using a signed archive allows applet mode users running HotJava Browser to connect to other computers on the network and write files to the client's hard disk. Using this archive allows client system users to connect to a Citrix server that is not the same machine as the Web server, write log files to the client's drive, and print to the client's printers.

JICAEngN.jar. A signed jar file containing the ICA Java Client class files. This file can be used with any browser or JVM that supports running Java programs from jar files. Using a signed archive allows applet mode users running Netscape Communicator 4.0x to connect to other computers on the network and write files to the client's hard disk. Using this archive allows client system users to connect to a Citrix server that is not the same machine as the Web server, write log files to the client's drive, and print to the client's printers.


Supported Archives

Which archive you use to run the ICA Java Client in applet mode depends upon the types of archive formats supported by the client system's browser. The following list specifies which archives are supported by several popular browsers. In addition to the listed archives, each browser can also run the ICA Java Client from the extracted class files. To run from the extracted archives, use the appropriate utility to extract an archive and place the class files on your Web server. You can then remove the archive parameter of the applet tag from the HTML page that client system users visit to start the ICA Java Client sessions.

Browser	Supported archives
Netscape 2.02 for OS/2	jar or extracted
Netscape Communicator 4.05 with AWT 1.1 support or Netscape Communicator 4.06+ for Windows 95, Windows NT 4.0, Macintosh, and Solaris 2.6	jar or extracted
Internet Explorer 4.0x for Windows 95, Windows NT 4.0, Macintosh, and Solaris 2.6	cab, jar, or extracted
HotJava Browser 1.1 for Windows 95, Windows NT 4.0, JavaOS for Business, and Solaris 2.6	jar or extracted
HotJava Views for Sun JavaOS	jar or extracted
For example, to use the ICA Java Client with Netscape 4.0 to connect to a Citrix server named CitrixServer, specify JICAEngN.jar in the applet tag. Your HTML page might look like this:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

To use the ICA Java Client with Internet Explorer 4.0 to connect to a machine named CitrixServer, specify JICAEngM.cab as the archive. When using cab files, the parameter to add is not archive but cabbase. Your HTML page might look like this:

<html>

<body>

<applet code=com.citrix.JICA.class

width=640 height=480>

<param name=cabbase value=JICAEngM.cab>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

Note  Internet Explorer users must set their safety levels for active content to Medium to use the cab archive.


Applet Security

Due to network security restrictions imposed by Java, many Web browsers do not permit users to connect to other computers on the network when using Java applets. When the ICA Java Client attempts to make a connection to the Citrix server specified in the HTML page, the Java security manager detects the attempt to connect to another computer and cancels the operation. The result of this security restriction is that under normal conditions, a client system can connect to a Citrix server only if it is also the same machine as the Web server that contains the ICA Java Client class files.

One way to work around this restriction is to use signed archives. The signature confirms that the files being downloaded came from Citrix and have not been altered since the signature was applied. Many Web browsers allow connections to a Citrix server that is not the same machine as the Web server if a signed archive is used.

Tip  As a second Java security restriction workaround, a Web server can be installed on the Citrix server. This option might be preferable in the case where client systems have browsers that do not support signed archives. The HTML pages that client system users visit to initiate ICA sessions can be kept on another Web server (for example, your Intranet Web server) and point to the class files on the Citrix server/Web server machine by using the codebase parameter in the HTML file. See "Creating a Web Page for Applet Mode Installations" in this chapter for a description of the codebase parameter.

To connect to Citrix servers that are not the same machine as the Web server supplying the client system with the applet code, the client system's browser must support signed archives (jar or cab files). The list below specifies which ICA Java Client signed archives can be used with some popular browsers:

Browser and platform	Signed archive
Netscape Communicator 4.05 with AWT 1.1 support or Netscape Communicator 4.06+ for Windows 95, Windows NT 4.0, Macintosh, and Solaris 2.6	JICAEngN.jar
Internet Explorer 4.0x for Windows 95 and Windows NT 4.0	JICAEngM.cab
HotJava Browser 1.1 for Windows 95, Windows NT, JavaOS for Business, and Solaris 2.6	JICAEngJ.jar
HotJava Views for Sun JavaOS	JICAEngJ.jar
Notes  Internet Explorer users must set their safety levels for active content to Medium to use the signed cab file.

Although Netscape 2.02 for OS/2 supports running Java applets from jar files, it does not support jar file signatures. Netscape 2.02 for OS/2 users can connect to a Citrix server only if it is also the same machine as the Web server that contains the ICA Java Client class files.

Although Internet Explorer 4.0x for Solaris 2.6 and Macintosh support running Java applets from cabinet files, they do not support cabinet file signatures. Users of these browsers can connect to a Citrix server only if it is also the same machine as the Web server that contains the ICA Java Client class files.

Specify which signed archive you want to use in the HTML page. When attempting a connection to the Citrix server, the client system user is prompted with the Citrix signed certificate. Once the user accepts the signature, the connection is permitted.

For example, to use the ICA Java Client with Netscape 4.0 to connect to a Citrix server named CitrixServer that is not the same machine as the Web server, specify JICAEngN.jar in the applet tag. Your HTML page might look like this:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

When visiting an HTML page like the example above for the first time, the Java Security dialog box appears:

Click Remember this decision and then click Grant to begin the ICA session.

To use a signed cab file, include the statement <param name=cabbase value=JICAEngM.cab> in the HTML file and remove the archive parameter. For example:

<html>

<body>

<applet code=com.citrix.JICA.class

width=640 height=480>

<param name=cabbase value=JICAEngM.cab>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

When users visit this HTML page for the first time, the following dialog box appears:

Click Always trust content from Citrix Systems, Inc. and then click Yes to download and run the ICA Java Client.

You can configure a single HTML page so that users with Microsoft Internet Explorer 4.x and Netscape Communicator 4.x can connect and run the ICA Java Client:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=cabbase value=JICAEngM.cab>

<param name=address value=CitrixServer>

</applet>

</body>

</html>

In the example above, the Netscape users download and run JICAEngN.jar while Internet Explorer users use JICAEngM.cab.

When using the signed jar file for HotJava Browser (JICAEngJ.jar), client system users must manually configure their browsers. The following procedure describes how to use the signed jar file with HotJava Browser:

To configure HotJava Browser to use a signed jar file

1.	Start HotJava Browser. Enter the URL of the ICA Java Client applet.

2.	From the HotJava Browser Edit menu, click Preferences and then click Applet Security.

3.	On the Applet Security page, click Advanced. Select the Citrix certificate in the list and then click Details.

4.	In the Certificate Details dialog box, select Fingerprint Verified and then click OK.

5.	Using the browser's browse button, return to the URL of the applet and click Reload.

6.	Click on Click Here to Connect.

7.	When the Security Violation dialog box appears, click Allow All Connects Without Warning and then click OK.


Using the ICA Java Client as an Application

Once you have installed the ICA Java Client, use the included launching script to start an ICA session. You can also use optional parameters with the launching script to configure ICA session properties.


Starting the ICA Java Client Application

The Citrix ICA Java Client includes script files that can be used to automate starting sessions in application mode. This section describes their use. See Starting the ICA Java Client Without Using Script Files for information on running the ICA Java Client in application mode without using script files.

If you used JavaEnt.zip, JavaEnt.sea.hqx, or JavaEnt.tar.gz to install the ICA Java Client, your installation directory contains one of the following script files: jicasession for UNIX computers, jicasession.bat for Windows computers, or jicasession.cmd for OS/2 computers. Each of these files contains a command line that specifies a certain JVM to use when running the ICA Java Client. Edit the name of the Java program (and any other JVM specific parameters) listed in the script file to match the Java program used by your client system. By default, the script files specify SUN's JVM program "java". If you use another JVM, for example Microsoft's "jview", edit the script to specify "jview" instead of "java". Additionally, to use the script files, your JVM must be in your path.

If you used setup.class to install the ICA Java Client, the setup program detected the client machine's operating system and JVM during installation and created a script file usable with that platform and JVM. This file should not require any editing.

In either case, Macintosh users must create their own launching file. See Creating a Macintosh Launching Script for information on creating a launching script for Macintosh client computers.

The following procedures describe how to run the ICA Java Client on different platforms using script files:

To start the ICA Java Client in application mode on a Windows client PC

1.	Start a DOS prompt. On Windows 95, click Start and then click Run. In the Run dialog box, type command and press ENTER. On Windows NT 4.0, click Start and then click Run. In the Run dialog box, type cmd and press ENTER.

2.	Change to the directory where the ICA Java Client is installed. For example, if the ICA Client was installed in a directory called C:\Citrix\ and your command prompt displays D:>, type C: and press ENTER, and then type cd Citrix and press ENTER.

3.	Type jicasession -address:CitrixServer at the command prompt, where CitrixServer is the name of the Citrix server to which you are connecting.

To start the ICA Java Client in application mode on a UNIX client system

1.	Start a shell. Change to the directory where the ICA Java Client was installed.

2.	Type jicasession -address:CitrixServer at the command prompt, where CitrixServer is the name of the Citrix server to which you are connecting.

To start the ICA Java Client as an application on an OS/2 client system

1.	Start an OS/2 command prompt. From the Start menu, point to OS/2 System and then point to Command Prompts. Click OS/2 Window.

2.	Change to the directory where the ICA Java Client is installed. For example, if the ICA Client was installed in a directory called C:\Citrix\ and your command prompt displays D:>, type C: and press ENTER, and then type cd Citrix and press ENTER.

3.	Type jicasession -address:CitrixServer at the command prompt, where CitrixServer is the name of the Citrix server to which you are connecting. Depending upon your JVM, you might have to specify the -nojit system parameter on the command line or add it to your launching script.

To start the ICA Java Client as an application on a Macintosh client system

Macintosh users must create their own launching file as described in Creating a Macintosh Launching Script.

1.	Open the folder containing the Macintosh launching script.

2.	Double-click the launching script.

To start the Citrix ICA Java Client as an application on a JavaOS for Business client system

The following procedure assumes the JavaOS for Business server has been configured to load the ICA Java Client when an individual client system boots. See Configuring the JavaOS for Business Server or Configuring the JavaOS for Business Server in Chapter 2, "Installing the ICA Java Client" for further information.

Note  The procedure for starting the ICA Java Client on a JavaOS for Business client system does not use an ICA Java Client script file.

1.	Boot the JavaOS for Business client system.

2.	Log on as a user who has been configured to run the ICA Java Client.

To start the Citrix ICA Java Client as an application on a JavaStation client system

The following procedure assumes the NetraJ 2.0 Server software has been configured to load the ICA Java Client when an individual client system boots. See Configuring the JavaStation Server for further information.

Note  The procedure for starting the ICA Java Client on a JavaStation client system does not use an ICA Java Client script file.

1.	Boot the JavaStation client system.

2.	Log on as a user who has been configured to run the ICA Java Client.


Specifying Parameters

You can specify multiple parameters in application mode using the following syntax:

jicasession [-parametername:value]

where jicasession is the script file for your client platform, parametername is the name of a parameter, and value is the value for the parameter. You can specify multiple parameters in any order. The address parameter is the only required parameter. To pass parameters to the ICA Java Client, use a dash (-), followed by the parameter name, followed by a colon (:), followed by the parameter value.

For example, to connect to the Citrix server named CitrixServer as user Barry from a command prompt using the script file jicasession, type:

jicasession -address:CitrixServer -username:Barry

You can also connect to a Citrix server using an ICA file. Specify the name of the ICA file on the command line without a dash, followed by any optional parameters. For example, to start a session using an ICA file named Connection.ica, type:

jicasession Connection.ica -username:Barry

Important  If you specify both an ICA file and command line parameters, the command line parameters override the settings in the ICA file. For example, in the command above, the username Barry overrides any username specified in the ICA file.

For more information about parameters that can be used with the ICA Java Client, see ICA Java Client Parameters.


GUI Command Line

The ICA Java Client includes a feature called the GUI Command Line. The GUI Command Line is a graphical tool that simulates the command line for users of client computers that lack a command line (for example, Macintosh systems) or for users who find the command line cumbersome to use. Use the GUI Command Line dialog box to pass parameters to the ICA Java Client. The GUI Command Line requires the same syntax as the command line.

To start the GUI Command Line

•	Specify the parameter -guicmdline on the command line (without a value). For example, type: jicasession -address:CitrixServer -guicmdline. The GUI Command Line dialog box appears:

Type any additional parameters in the Enter command line parameters field. Use the same syntax used on the command line.

You can also start the GUI Command Line by specifying no parameters on the command line. For example if you type jicasession without any parameters, the GUI Command Line dialog box appears.


Starting the ICA Java Client Without Using Script Files

You can also run the ICA Java Client in application mode without using a script file. The class file to run is com.citrix.JICA. When starting the ICA Java Client without a script file, use the following syntax:

jvmpgm com.citrix.JICA [-parametername:value][-parametername:value]...

where jvmpgm is the name of your JVM program, parametername is the name of a parameter, and value is the value for the parameter. You can specify multiple parameters in any order. The address parameter is the only required parameter. To pass parameters to the ICA Java Client, use a dash (-), followed by the parameter name, followed by a colon (:), followed by the parameter value.

Important  When starting the ICA Java Client without a script file, you must have the ICA Java Client class files in your classpath and your JVM in your path. For example, if the ICA Java Client class file archive JICAEngJ.jar is stored in a directory called \Application on drive C, set your classpath to C:\Application\JICAEngJ.jar. If the class files have been extracted from an archive, specify the location only; for example, C:\Application. To place the JVM in the path, set the path to the location of the JVM.

For example, to connect to a Citrix server named CitrixServer from a command prompt using the Sun Microsystems JVM (named java), type:

java com.citrix.JICA -address:CitrixServer


ICA Java Client Parameters

The following parameters can be specified in the HTML file or on the command line to provide additional features and customization. The Address parameter is the only required parameter; other parameters in the lists are optional.

Parameter	Description
Address	The address of the Citrix server or the name of the published application. (If a published application is entered as an address value, TCPBrowserAddress and InitialProgram parameters must also be specified.)
TCPBrowserAddress	The address of a Citrix server, used when connecting to a published application instead of an explicitly named Citrix server.
Username	The user name to use during login.
Domain	The name of the domain for the user name.
Password	The password of the user. The Password parameter cannot be used to specify an encrypted password. To specify an encrypted password, use an ICA file or Ini file that contains an encrypted password.
InitialProgram	The name of the initial program to run after connecting to the Citrix server.
WorkDirectory	The path of the working directory where the initial program is run after the user connects to the Citrix server.
ICAPortNumber	The default ICA port number is 1494. A different port number can be specified using this parameter or by appending the port number to the address value; for example, "CitrixServer:1495."
Width	The width of the ICA session window. Used differently in applet and application modes. See the examples below.
Height	The height of the ICA session window. Used differently in applet and application modes. See the examples below.
The following parameters are used only in applet mode:

Parameter	Description
EndSessionTimeout	By default, when users leave a page containing an open ICA session for more than 300 seconds (five minutes), the session is disconnected. Use this parameter to specify a different value in seconds.
Border	This parameter turns the border around the ICA session in the browser window on or off.  Values for this parameter are on or off. The default value is off.
BorderWidth	This parameter allows the user to specify a border width in pixels.  The default value is 6.
Start	Values for Start are manual or auto.  This parameter is used to specify whether the ICA Java Client starts immediately (auto) or after user interaction (manual).  The default value is manual.
Language Country	These two parameters are used together to cause the ICA Java Client's user interface components to appear in a language other than the language of the client machine; for example, to display ICA Java Client components in French on a German machine. By default, the ICA Java Client displays the components in the language of the client machine. See Starting the ICA Java Client in a Specific National Language for more information.
Icafile	This parameter is used to specify an ICA file for the ICA Java Client to use. The value entered must be a valid URL.
The following parameters are used only in application mode:

Parameter	Description
Clientsn	Use the client serial number parameter when running the ICA Java Client in application mode to connect to a MetaFrame server that has a Terminal Server License. (A client serial number cannot be used when running the ICA Java Client as an applet.) This parameter is required when connecting to a server that has a Terminal Server License.
Iniappsrv	The URL of an Appsrv.ini file to use with the ICA Java Client.
Inimodule	The URL of a Module.ini file to use with the ICA Java Client.
Iniwfclient	The URL of a Wfclient.ini file to use with the ICA Java Client.
IniDir	The URL of a directory containing Ini files to use with the ICA Java Client.
Version	Use this parameter to display a dialog box that lists ICA Java Client version information. Version information includes OEM ID, version, build number, and build date and time. This parameter is specified without a value and cannot be used with any other parameters in a command line. For example, type jicasession -version.
Guicmdline	Use this parameter to display the GUI Command Line dialog box. The GUI Command Line dialog box is intended for use as a convenient tool for those platforms that lack a command line or for users who find the command line cumbersome to use. This parameter is specified without a value. For example, type jicasession -guicmdline.
See Specifying Ini Files on the Command Line for more information on specifying Ini files. See GUI Command Line for more information on the GUI Command Line dialog box.

Examples

The following examples illustrate a sample connection using several parameters from the parameter lists above. The first example is in application mode and the second is in applet mode.

To connect to a Citrix server named CitrixServer using a launching file named jicasession as user tonycarp from the test domain running Microsoft Word as an initial program with a window resolution of 1024 x 768, type (all on one line):

jicasession -address:CitrixServer -username:tonycarp -domain:test

"-initialprogram:C:\Program Files\Word\Winword.exe"

-height:768 -width:1024

Note  Parameters can be designated in any order. When entering a parameter value that contains a space, place the entire parameter (parameter name and value) in quotation marks.

To make the same connection in applet mode with the additional parameters of a 600 second end session timeout, a border of 10 pixels, and with a specified ICA file named "Connection.ica" that is stored in the C:\Citrix directory, create an HTML page like the following:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=1024 height=768>

<param name=address value=CitrixServer>

<param name=username value=tonycarp>

<param name=domain value=test>

<param name=endsessiontimeout value=600>

<param name=border value=on>

<param name=borderwidth value=10>

<param name=initialprogram

value="C:\Program Files\Word\Winword.exe">

<param name=icafile value=c:\citrix\connection.ica>

</applet>

</body>

</html>


Published Applications

To connect to a published application, use the following command syntax:

jicasession -address:Publishedappname -tcpbrowseraddress:ServerName
-InitialProgram:#Publishedappname

where Publishedappname is the name of the published application, ServerName is the name of a Citrix server used for TCP browsing, and #Publishedappname is the name of the published application preceded by a pound (#) symbol.

In applet mode, specify:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=Publishedappname>

<param name=tcpbrowseraddress value=CitrixServer>

<param name=initialprogram value=#Publishedappname>

</applet>

</body>

</html>


Starting the ICA Java Client in a Specific National Language

The ICA Java Client allows users to specify what locale to use to display the ICA Java Client's user interface (including various messages and dialog boxes). By default, if you do not specify a locale, your session will use the locale of your client machine to display the ICA Java Client.

The following locales are supported by the Citrix ICA Java Client:

en (English)

de (German)

fr (French)

es (Spanish)

ja (Japanese)

For example, to use Japanese as your locale on a non-Japanese machine when connecting  to the Citrix server named CitrixServer in applet mode, create an HTML page like the following:

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=1024 height=768>

<param name=address value=CitrixServer>

<param name=Language value=ja>
<param name=Country value=ja>

</applet>

</body>

</html>

Both Language and Country parameters must be specified and must be set to the same value.

When forcing a locale in application mode, you must define a system property to the JVM using the command line argument appropriate for your JVM. You must add this command line argument to the command line in your launching script.

For example, to force Japanese as your locale when using Microsoft's JVM, add /d:user.language=ja to the command line in your launching script.

To create the same connection using Sun's JVM, add -Duser.language=ja to the command line in your launching script.

To create this connection from a Macintosh client machine, you must use JBindery to add user.language as a system property with the appropriate language (en, de, fr, es, or ja) as its value to the launching script for Macintosh.

OS/2 systems require that you specify the command set LANG=x and press ENTER before using jicasession.cmd to start the ICA Java Client, where x is en, de, fr, es, or ja.

Important  In the application mode examples, note that you precede values with an equals sign (=) instead of a colon. These parameters are virtual machine parameters, not ICA Java Client parameters (which are preceded by a colon).


Printing

The ICA Java Client can be configured to map client printers to an ICA session so that client system users can print to their local or network printers. Printers can be auto-created; auto-created printers are configured in the HTML page or from the command line. When users log on to a Citrix server, their printers appear in Print Manager or in the Printers folder and are ready for use. When users log off, their local printers are deleted from the Citrix server.

To auto-create printers, the ICA Java Client must be passed three values:

Printer name. Can be any name by which you would like to identify the printer.

Port name. Specify a file name, port name, or printer IP address (or network name) and print queue.

When printing to a file, the output file is composed of printer machine code. This file can be sent to a printer using a platform-specific utility. For example, use a command prompt on Windows platforms to send the file to a printer by copying the file to a printer port.

When printing to a port, specify the port (for example, LPT1:).

When printing to a network printer, specify the printer's IP address or network name and print queue (for example, ipaddress:printqueuename).

The ICA Java Client also allows users to print to standard out or standard error. Specify stdout or stderr to print to standard out or standard error, respectively.

Driver. Specify the printer driver. This name must exactly match the driver name on the Citrix server. Check the driver list in the Print Manager Create Printer dialog box for driver names.

Note  To auto-create a printer, the Citrix server must have the printer driver installed. If the driver is not installed, the printer is not auto-created. In this case, install the printer on the console before attempting to auto-create the printer in an ICA session.

The parameter name to use when passing the printer name to the ICA Java Client is user.localclientprinters. When passing the port name, use the parameter user.printername.port, where printername is the name you specify in user.localclientprinters. When passing the driver, use the parameter user.printername.driver, where printername is also the name specified in user.localclientprinters.

The following example demonstrates auto-creating a printer by passing these values to the ICA Java Client in applet mode on a Windows client system. In this example, the printer's name is Laser. It is connected to the client's LPT1 port and has a driver named HP LaserJet 4/4M Plus PS.

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=CitrixServer>

<param name=user.localclientprinters value=Laser>

<param name=user.Laser.port value=lpt1:>

<param name=user.Laser.driver value="HP LaserJet

4/4M Plus PS">

</applet>

</body>

</html>

In this example, the printer's name is also Laser and has a driver named HP LaserJet 4/4M Plus PS. The printer is a network printer that exists on a network print server with an IP address of 127.0.0.0 and a print queue named LPT_PASSTHRU.

<html>

<body>

<applet code=com.citrix.JICA.class

archive=JICAEngN.jar

width=640 height=480>

<param name=address value=CitrixServer>

<param name=user.localclientprinters value=Laser>

<param name=user.Laser.port value=127.0.0.0:LPT_PASSTHRU>

<param name=user.Laser.driver value="HP LaserJet

4/4M Plus PS">

</applet>

</body>

</html>

To create the printer described in the first applet mode example above, type the following on the command line (all on one line):

jicasession -address:CitrixServer -user.localclientprinters:Laser

-user.Laser.port:lpt1: "-user.Laser.driver:HP LaserJet 4/4M Plus PS"

To create the network printer described in the second applet mode example above, type the following on the command line (all on one line):

jicasession -address:CitrixServer -user.localclientprinters:Laser

-user.Laser.port:127.0.0.0:LPT_PASSTHRU "-user.Laser.driver:HP LaserJet 4/4M Plus PS"

The following example illustrates configuring multiple printers, one of which is a network printer. The port name of a network printer may be a UNC name or the name of a local port that has a network printer mapped to it. In this example, the printer NetPrinter1 is a network printer mapped to the local LPT2 port and has a driver named HP Laser Jet 400 Series PS.

<html>

<body>

<applet code=com.citrix.JICA.class

width=640 height=480>

<param name="address" value=CitrixServer>

<param name=user.localclientprinters

value=Laser,NetPrinter1>

<param name=user.Laser.port value=lpt1:>

<param name=user.Laser.driver value="HP LaserJet

4/4M Plus PS">

<param name=user.NetPrinter1.port value=lpt2:>

<param name=user.NetPrinter1.driver value="HP LaserJet

400 Series PS">

</applet>

</body>

</html>

In application mode, type the following on the command line (all on one line):

jicasession -address:CitrixServer

-user.localclientprinters:Laser,NetPrinter1 -user.Laser.port:lpt1:

"-user.Laser.driver:HP LaserJet 4/4M Plus PS"

-user.NetPrinter1.port:lpt2: "-user.NetPrinter1.driver:HP LaserJet 400 Series PS"


Event Logging

Event Logging creates a log file of various events that occur while running the ICA Java Client. The following parameters can be specified:

Parameter	Description
LogFile	The name of the log file to be kept. Can be any name. Log data can alternately be sent to standard out or standard error by specifying stdout or stderr instead of a file name.
LogAppend	The event log can be overwritten by new events or new events can be added to the end of the existing file. Specify on to save old events and add new events to the end of the file. Specify off to overwrite old events.
LogConnect	Logs an event when the ICA Java Client connects to or disconnects from the Citrix server. Values are on or off.
LogErrors	Logs ICA Java Client errors. Values are on or off
LogTransmit	Logs data sent from the ICA Java Client to the Citrix server. Values are on or off
LogReceive	Logs data sent from the Citrix server to the ICA Java Client. Values are on or off
LogKeyboard	Logs keyboard data. Values are on or off
All parameters except Logfile are off by default.

When specifying parameters for event logging, the parameter names are preceded by the words user.wfclient. For example, the parameter LogConnect becomes user.wfclient.Logconnect.

The following examples demonstrate how to create an event log named Events.log that contains error and connection data. This log is not overwritten by new events.

<html>

<body>

<applet code=com.citrix.JICA.class

width=640 height=480>

<param name=address value=CitrixServer>

<param name=user.wfclient.logfile value=Events.log>

<param name=user.wfclient.logerrors value=on>

<param name=user.wfclient.logconnect value=on>

<param name=user.wfclient.logappend value=on>

</applet>

</body>

</html>

From the command line, type:

jicasession -address:CitrixServer -user.wfclient.logfile:Events.log

-user.wfclient.logerrors:on -user.wfclient.logconnect:on

-user.wfclient.logappend:on


Keyboards

The ICA Java Client lets users specify what type of keyboard to use in their ICA sessions. By default, if you do not specify a keyboard preference, your session uses the keyboard that is specified as the default keyboard for the Citrix server.

Note  Different JVMs interpret key detection differently.

The ICA Java Client supports using any keyboard supported by the Citrix server to which it is connecting.

To specify a keyboard other than the server's default for use in an ICA session, specify the parameter system.wfclient.keyboardlayout with a value from the server's list of supported keyboards. Values that contain a space (for example, Swiss German) should be enclosed in quotation marks.

The list of supported keyboards is in the following locations:

On MetaFrame servers: open Control Panel, double-click Keyboard, and then click the Input Locales tab. The Input Locales list in this tab includes all installed locales and layouts. You must use the value specified in the Layout column for your keyboard when specifying a keyboard other than the server's default.

On WinFrame servers: open Control Panel, double-click International. The Keyboard Layout field includes a list of all keyboards you can specify. You must use the value specified in this list for your keyboard when specifying a keyboard other than the server's default.

For example, to specify a Danish keyboard in applet mode, create an HTML page like the following:

<html>
<body>
<applet code=com.citrix.JICA.class
width=640 height=480>
<param name=address value=CitrixServer>
<param name=system.wfclient.keyboardlayout value=Danish>
</applet>
</body>
</html>

From the command line, type:

jicasession -address:CitrixServer -system.wfclient.keyboardlayout:Danish

The ICA Java Client supports the following keyboard types to distinguish between subtypes of the Japanese keyboard layout:

101 Keyboard (Japanese)

106 Keyboard (Japanese)

To specify a Japanese keyboard type, specify the system.wfclient.keyboardtype parameter.

For example, to specify a Japanese type 101 keyboard in applet mode, create an HTML page like the following:

<html>
<body>
<applet code=com.citrix.JICA.class
width=640 height=480>
<param name=address value=CitrixServer>
<param name=system.wfclient.keyboardlayout value="Japanese MS-IME98">
<param name=system.wfclient.keyboardtype value="101 Keyboard (Japanese)">
</applet>
</body>
</html>

From the command line, type:

jicasession -address:CitrixServer "-system.wfclient.keyboardlayout:Japanese MS-IME98" "-system.wfclient.keyboardtype:101 Keyboard (Japanese)"

Notes  As described in Specifying Ini Files on the Command Line, application mode users can use the Ini files of other Citrix ICA Clients by referencing the Ini files in command line parameters. Keyboard layout information is saved in Wfclient.ini; users can specify this file on the command line to make use of its keyboard configuration information.

To right-click when connected to a Citrix server, Macintosh users can hold down the command key and click the mouse button.


Hotkeys

The Citrix ICA Java Client provides hotkeys that can be used to control various Java Client functions. When the ICA session has the focus on the client system's desktop, pressing these hotkeys causes the associated action to occur.

The following hotkeys are available to client system users:

Parameter	Description
Hotkey2	Close Remote Application. The Close Remote Application hotkey closes programs opened in an ICA session. If no programs are open, this hotkey prompts the user that the ICA session will be shut down and then, if given permission, disconnects the ICA session. Hotkey2 is mapped by default to CTRL+F3.
Hotkey4	Substitute for the standard Windows hotkey CTRL+ALT+DEL. The CTRL+ALT+DEL hotkey displays the Windows NT Security desktop in the ICA session. Hotkey4 is mapped by default to CTRL+F1.
Hotkey5	Substitute for the standard Windows hotkey CTRL+ESC. On WinFrame servers, this hotkey causes the remote Task List to appear. On MetaFrame servers, the remote Windows NT Start menu appears. Hotkey5 is mapped by default to CTRL+F2.
Hotkey6	Substitute for the standard Windows hotkey ALT+ESC. This hotkey is used to bring the focus to maximized and minimized windows of programs that have been opened in an ICA session. Hotkey6 is mapped by default to ALT+F2.
Hotkey7	Substitute for the standard Windows hotkey ALT+TAB. Use this hotkey to cycle through applications that are open in the ICA session. A popup box appears and displays the programs as you cycle through them. The chosen application receives keyboard and mouse focus. Hotkey7 is mapped by default to ALT+PLUS.
Hotkey8	Substitute for the standard Windows hotkey ALT+BACKTAB. Like the ALT+TAB hotkey, this key sequence cycles through applications that are open in the ICA session but in the opposite direction. The chosen application receives keyboard and mouse focus. Hotkey8 is mapped by default to ALT+MINUS.
ICA Java Client hotkeys use a two key sequence. The first key defines the shift state and the second defines the character. To set the ICA Java Client hotkeys to key combinations other than their defaults, select a shift state value and a character value from the following lists:

Shift state: SHIFT, CTRL, ALT, any combination of these keys, or none

Character: ESCAPE, MINUS, PLUS, STAR, TAB, any of the F keys (F1 through F12), or none

These values are passed to the ICA Client as parameters in the HTML page or from the command line. For each hotkey, two parameters are specified: one for the shift state and a second for the character state.

When specifying parameters for hotkeys, the hotkey name (Hotkey2, for example) is preceded by the words user.wfclient. and followed by shift or char, depending upon whether the parameter describes the character or shift state key of the key sequence.

The following example describes how to create Close Remote Application and ALT+TAB hotkeys for use in an applet mode ICA session. The Close Remote Application hotkey will have the key sequence CTRL+F1 and the ALT+TAB hotkey key sequence will be SHIFT+TAB.

<html>

<body>

<applet code=com.citrix.JICA.class

width=640 height=480>

<param name=address value=CitrixServer>

<param name=user.wfclient.hotkey2shift value=ctrl>

<param name=user.wfclient.hotkey2char value=f1>

<param name=user.wfclient.hotkey7shift value=shift>

<param name=user.wfclient.hotkey7char value=tab>

</applet>

</body>

</html>

In application mode, type the following on the command line:

jicasession -address:CitrixServer -user.wfclient.hotkey2shift:ctrl
-user.wfclient.hotkey2char:f1 -user.wfclient.hotkey7shift:shift
-user.wfclient.hotkey7char:tab

To disable a hotkey, enter none as a value for one of the parameters.


ICA Java Client Advanced Syntax

Note  This section provides an explanation of the command line and HTML syntax used to configure the ICA Java Client. This explanation is intended to give users an understanding of the logic behind the examples presented in this chapter (such as client printing, event logging, and hotkeys) and to allow them to apply this logic to further customization of the ICA Java Client and ICA sessions.

To initiate an ICA session, the ICA Java Client engine must build an information base. This information base contains the settings that govern the client's general operation and settings that apply to the current connection (such as address, username, and password). In the case of other Citrix ICA Clients, such as the ICA Win32 Client or the ICA DOS Client, this information base is maintained by connection manager utilities such as Remote Application Manager. Client system users can customize the behavior of their ICA Client and individual ICA sessions by using Remote Application Manager to set various options and preferences. Remote Application Manager stores these settings in three Ini files (Appsrv.ini, Module.ini, and Wfclient.ini).

When the client system user initiates a connection, the ICA Client engine references the Ini files and configures the connection according to the settings in the Ini files.

Although the ICA Java Client does not include its own Ini files for maintaining the information base, you can create an information base by using command line or HTML parameters. When a user initiates an ICA session, the ICA Java Client engine references the parameters, builds its information base, and launches the session.

The information base created at the command line or in the HTML page is like a tree in structure. The tree is composed of four branches. Three of the branches correspond to the above mentioned Ini files. The fourth branch corresponds to a subsection of one of the Ini files.

The first branch, or "user" branch, corresponds to the file Appsrv.ini. An example of an Appsrv.ini file is excerpted below:

;*********************************************************************

;**

;** APPSRV.INI - Application Server Configuration File.

;**

;** This file contains user settings which define application

;** servers and other preferences.

;**

;*********************************************************************

 [WFClient]

Version=2

LogFile=error.log

LogFileWin16=wfcwin.log

LogFileWin32=wfcwin32.log

LogAppend=Off

LogConnect=On

LogErrors=On

LogTransmit=Off

LogReceive=Off

LogKeyboard=Off

Hotkey1Char=F1

Hotkey1Shift=Shift

Hotkey2Char=F3

Hotkey2Shift=Shift

Hotkey3Char=F2

Hotkey3Shift=Shift

Hotkey4Char=F1

Hotkey4Shift=Ctrl

Hotkey5Char=F2

Hotkey5Shift=Ctrl

Hotkey6Char=F2

Hotkey6Shift=Alt

Hotkey7Char=plus

Hotkey7Shift=Alt

Hotkey8Char=minus

Hotkey8Shift=Alt

DisableSound=Off

DisableCtrlAltDel=On

MouseTimer=100

KeyboardTimer=50

ColorMismatchPrompt_Have16_Want256=On

ColorMismatchPrompt_Have64K_Want256=On

ColorMismatchPrompt_Have16M_Want256=On

DosConnectTTY=On

ConnectTTY=Off

ConnectTTYDelay=1000

TcpBrowserAddress=

IpxBrowserAddress=

NetBiosBrowserAddress=

BrowserRetry=3

BrowserTimeout=1000

LanaNumber=0

PersistentCacheMinBitmap=8192

PersistentCachePath=D:\Program Files\Citrix\WinFrame Client\Cache

MRU Connection=Network Connection

 [Common Default Information]

ProgramGroup=WinFrame Client

WinStationDriver=ICA 3.0

Password=000100

 [llama4m]

TransportDriver=TCP/IP

Address=LLAMA4M

Compress=Off

PersistentCacheEnabled=Off

ClientAudio=Off

IconPath=D:\Program Files\Citrix\WinFrame Client\wfcmgr32.exe

EncryptionLevelSession=Basic

WinStationDriver=ICA 3.0

Username=duricova

Password=000100

 [ApplicationServers]

llama4m=

 [Default Network Connection]

Address=LLAMA4M

TransportDriver=TCP/IP

Published Application=No

;*********************************************************************

The settings other ICA Clients store in Appsrv.ini can be reproduced on the command line or in the HTML page for the ICA Java Client by using the proper syntax. The ICA Java Client engine accepts parameters taken from the Appsrv.ini branch of the information base if they are presented with the following syntax:

-metasection.section.key:val

In HTML, the syntax is:

<param name=metasection.section.key value=val>

This syntax has four parts:

Metasection is the name of one of the branches of the information base. In the case of parameters taken from AppSrv.ini, the metasection name is "user."

Section is the name of a section in an Ini file. Sections are denoted by [] symbols in the Ini file. For example, the excerpted AppSrv.ini file above contains four sections:[WFClient], [Common Default Information], [ApplicationServers], and [Default Network Connection].

Key is the basic unit of sections. For example, the [WFClient] section of the AppSrv.ini file above contains the keys LogFile, LogFileWin16, LogFileWin32, etc.

Val is a variable to which the key is set. For example, the key LogFile is set to the value error.log.

The file above contains the section [WFClient], which contains the key LogFile. LogFile is set to the value error.log.

To recreate this parameter on the command line, specify:

-user.wfclient.logfile:error.log

In HTML, specify:

<param name=user.wfclient.logfile value=error.log>

Parameters set in Module.ini and Wfclient.ini can be set in the same manner. The metasection name for parameters based on Module.ini settings is "global." Parameters based on Wfclient.ini settings have the metasection name "system."

The fourth branch of the information base is derived from Appsrv.ini. This branch is composed of parameters that describe the current connection the user is about to initiate. In the example Appsrv.ini file above, the section [llama4m] contains current connection parameters. Llama4m is a hypothetical Citrix server name. The section [llama4m] contains parameters that describe such settings as username, domain, password, address, and initial program.

The syntax for current connection settings is:

-key:value

In HTML, specify:

<param name=key value=val>

as in -address:CitrixServer or <param name=address value=CitrixServer>

Important  Parameters must apply to the ICA Java Client to be used with the ICA Java Client. For example, any parameters in the Ini files that pertain to modems or protocols other than TCP/IP cannot be used with the ICA Java Client.


Specifying Ini Files on the Command Line

The ICA Java Client also allows you to specify Ini files of other Citrix ICA Clients. Specifying the Ini files of another ICA Client causes the ICA Java Client to use the settings within those files. For example, if you have an Appsrv.ini file from another Citrix Client that contains useful default settings, you might find it convenient to specify this file when using the ICA Java Client.

Note  The ICA Java Client ignores parameters contained in Ini files if those parameters do not pertain to the functionality of the ICA Java Client. For example, any parameters in Ini files that pertain to modems or protocols other than TCP/IP are ignored.

To specify an Ini file, you must pass the name (including the path, if necessary) of the file to the ICA Java Client on the command line.

Ini file locations are passed using the following parameters:

Parameter	Description
Iniappsrv	Specifies the location and name of an Appsrv.ini file.
Inimodule	Specifies the location and name of a Module.ini file.
Iniwfclient	Specifies the location and name of a Wfclient.ini file.
IniDir	Specifies the location of a group of Ini files.
For example, to use an Appsrv.ini file named Appsrv.ini, specify:

jicasession -iniappsrv:C:\Citrix\appsrv.ini

You can also specify a connection entry in an Appsrv.ini file. For example, suppose you have an Appsrv.ini file that, like the excerpted Appsrv.ini file described earlier in this chapter, contains a section for a connection called [llama4m]. This section contains configuration information such as the address of the server, user name for logon, compression values, etc. To reference this information, you can add this section name to the parameters you specify on the command line. Assume that, like the example above, the file is located in a directory called C:\Citrix and is named Appsrv.ini. To specify this entry, type:

jicasession llama4m -iniappsrv:C:\Citrix\appsrv.ini

The IniDir parameter can be used to specify the location of a set of Ini files (Appsrv.ini, Module.ini, and Wfclient.ini) to the ICA Java Client. Ini file use is a three step process:

To pass Ini files to the ICA Java Client

1.	By default, the ICA Java Client checks if any (or any combination) of the following three Ini parameters (Iniappsrv, Inimodule, Iniwfclient) is specified on the command line.

2.	If a parameter is set, the ICA Java Client uses the Ini file located in the specified URL. If the ICA Client does not find one or all of the parameters to be set, the ICA Java Client checks if the IniDir parameter is specified. If IniDir is specified, the ICA Client then searches that location for each of the Ini files not specified on the command line.

3.	Finally, if IniDir is not specified on the command line, the ICA Java Client searches for Ini files in an Ini directory off the current working directory. For example, if you are running the ICA Java Client from a directory called C:\Java and have not specified IniDir on the command line, the ICA Client looks for Ini files in C:\Java\Ini\. If your working directory does not contain an Ini directory, you might find it useful to create an Ini directory and not specify Ini parameters on the command line when you run the ICA Client. Each time you run the ICA Client, it searches the Ini directory and uses any Ini files the directory contains.