Using the Citrix XML Service

Configuring display settings. You can configure your applications for use with the Web Interface using the ctxappcfg command. Using ctxappcfg, you can configure display settings that include the name of the folder containing the application and the icon that the Web Interface displays, and the window size and color depth. For more information about configuring application display settings, see “Publishing Applications and Desktops” on page 61.

Configuring the XML Service port. By default, the Web server communicates with the XML Service using port 80. If port 80 is already in use on the server running the XML Service, assign the XML Service to an unused port. See “Configuring the Server Port” on page 174 for more information.

Configuring the SSL Relay port. To enable your users to make SSL-secure connections to applications through the Web Interface, you must configure the XML Service for use with SSL Relay. To do this, you use the ctxappcfg command to specify whether SSL is used to secure connections on all published

applications or on a particular application only (see “Publishing Applications and Desktops” on page 61 for more information). If you are not using TCP port 443, which is the standard port for SSL-secured communications, you must specify the port number that SSL Relay listens for connections on using the ctxnfusesrv command. For information about how to do this, see “Configuring the XML Service for Use with SSL Relay” on page 175.

Note: If you configured a particular server to be the master browser, Citrix recommends that you direct the Web Interface to this server. For more

information about the ICA browser, see “XenApp for UNIX and the ICA Browser Service” on page 147. Also, if plugins are using HTTP browsing, it is best to direct plugins to the master browser server. See your plugin documentation for more information.

Starting and Stopping the Citrix XML Service

When you start and stop XenApp, the Citrix XML Service automatically starts and stops. Using the ctxsrv command, you can start and stop the Citrix XML Service on the local server.

To start the Citrix XML Service

1. Log on to the server as an administrator. 2. At a command prompt, type:

Starting a server causes an election, and the master browser may change. The master browser takes some time to acquire information about applications available on the farm. If the Citrix XML Service is started at the same time as a XenApp server, it can take up to 10 minutes before these applications are visible through the Web Interface.

To stop the Citrix XML Service

1. Log on to the server as an administrator. 2. At a command prompt, type:

ctxsrv stop msd

Configuring the Server Port

By default, the Web Interface communicates with the Citrix XML Service using port 80. If port 80 is already in use on the server running the XML Service, assign the XML Service to an unused port.

Note: The XML Service port number must be unique. If the port is already in use by another process, results may be unpredictable. You must configure the Web Interface to use the same port number as you specified for the XML Service—see the Web Interface Administrator’s Guide for information about how to do this.

To configure the Citrix XML Service port

1. Log on to the server as an administrator. 2. At a command prompt, type:

ctxnfusesrv -port portnumber

where portnumber is an unused port; for example, 8080. Note: You must restart the XML Service for the new port to be used.

To display the current port number

At a command prompt, use ctxnfusesrv with the -l (list) option: ctxnfusesrv -l

9 Using the Citrix XML Service 175

Configuring the XML Service for Use with SSL Relay

SSL Relay is included automatically when you install XenApp for UNIX. To allow users who connect to the server through the Web Interface to make SSL- secure connections to applications, you must configure the XML Service for use with SSL Relay. To do this you use the:

• ctxappcfg command to specify whether SSL is used to secure connections on all published applications or on a particular application only. For more information, see “Publishing an Application, Shell Script, or Desktop” on page 64.

• ctxnfusesrv command to specify the port number on which SSL Relay listens for connections. You need to run this command only if you are not using TCP port 443, which is the standard port for SSL-secured

communications. The SSL Relay port number you specify must be the same on every server in the farm.

For more information about configuring and using SSL Relay, see the Citrix XenApp SSL Relay for UNIX Administrator’s Guide.

To configure the SSL Relay port number

1. Log on to the server as an administrator.

2. If SSL Relay listens for connections on a port other than 443, specify this port number. At a command prompt, type:

ctxnfusesrv -ssl-port port-number

where port-number is the port number on which SSL Relay listens for connections. For example, if SSL Relay listens on port 444, type: ctxnfusesrv -ssl-port 444

Troubleshooting SSL

If you configured your server to use NIS for name resolution, the server cannot support SSL-enabled ICA connections because NIS does not supply the fully qualified domain name (FQDN). The FQDN is required by the XML Service to direct requests from the Web Interface and client devices.

To solve this problem, configure the server to use DNS, in preference to NIS, for name resolution, because DNS supplies the FQDN.

Configuring DNS Address Resolution

By default, servers reply to browsing requests with an IP address. However, a server can respond with the fully qualified domain name. This feature, called Domain Name System (DNS) address resolution, is available to client devices using the XML Service. In most situations, the use of IP addresses works well and with less overhead.

You can enable DNS address resolution using the ctxnfusesrv -dns command.

To enable DNS address resolution

1. Log on to the server as an administrator. 2. At a command prompt, type:

ctxnfusesrv -dns enable

Note: If DNS addressing is enabled, client devices can connect reliably to servers only if they can resolve the fully qualified domain name. If the plugin is not configured correctly, it cannot connect. Ping a server with its DNS host name to verify this.

Displaying the Current Setting

You can display the current DNS address resolution setting using ctxnfusesrv and the -l (list) option.

To display the current DNS address resolution setting

10

Using Client Drive Mapping

Overview

This chapter discusses client drive mapping. Topics discussed include: • An introduction to client drive mapping

• Enabling client drive mapping • Configuring client drive mapping

• Features and limitations of client drive mapping • Troubleshooting client drive mapping

Introducing Client Drive Mapping

The client drive mapping feature enables users to access their local drives from within an ICA session. When a user makes an ICA connection to a XenApp server, the user’s local drives are mounted automatically, such as floppy disk drives, network drives, CD-ROM drives, and hard disk drives.

These drives are available for the duration of the session. When a session is disconnected, all the mapped drives belonging to the session are released immediately. If you shadow a users’s session using ctxshadow, you can also access the local, mapped drives belonging to the shadowed session.

For users to take advantage of client drive mapping: • Users must be running Version 6.0 or later plugins.

• You use ctxcfg to enable client drive mapping. By default, the client drive mapping feature is disabled because it consumes server resources, and so that you can be certain that no one is moving files between the server and client devices. For information about enabling and configuring client drive mapping, see “Enabling and Configuring Client Drive Mapping” on page 179. ICA session XenApp Server Floppy drive Hard disk drive CD-ROM drive moun ted lo cal driv_es User