Exceed 10 User’s Guideftp.iitm.ac.in/archive/Exceed10/Documentation/Exceed.pdf · ii Exceed...

Exceed®

User’s Guide

8370-5M

ii

Exceed User’s GuideVersion 10Part Number 8370-5MPublished in Canada — July 31, 2004

Hummingbird Ltd. — Corporate Headquarters1 Sparks Avenue • Toronto, Ontario • M2H 2W1 • CanadaToll Free Canada/U.S.A. 1 877 FLY HUMM (359 4866)Tel +1 416 496 2200 • Fax +1 416 496 2207 • E-mail [email protected]

For more information, visit www.hummingbird.com

RESTRICTED RIGHTS LEGEND Unpublished rights reserved under the copyright laws of the United States. The SOFTWARE is provided with restricted rights. Use, duplications, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (c) (1) and (2) (a) (15) of the Commercial Computer Software-Restricted Rights clause at 48 CFR 52.227-19, as applicable, similar clauses in the FAR and NASA FAR Supplement, any successor or similar regulation.

Information in this document is subject to change without notice and does not represent a commitment on the part of Hummingbird Ltd. Not all copyrights pertain to all products.

Copyright © 2004, Hummingbird Ltd. All rights reserved. Trademarks and logos are the intellectual property of Hummingbird Ltd.

Connectivity Kerberos, Connectivity Secure Shell, Connectivity SecureTerm, Connectivity SSL, Exceed, Exceed 3D, Exceed Connectivity Suite, Exceed onDemand, Exceed onDemand Client, Exceed onDemand Deployment Wizard, Exceed onDemand Server, Exceed onDemand Server Manager, Exceed PowerSuite, Exceed XDK, HostExplorer, HostExplorer Connectivity Suite, Host Access Services, HostExplorer Print Services, HostExplorer Web, Hummingbird Basic, Hummingbird Certificate Manager, Hummingbird Connectivity, Hummingbird Connectivity Suite, Hummingbird Core Services, Hummingbird Deployment Packager, Hummingbird Deployment Wizard, Hummingbird e-Gateway, Hummingbird FTP, Hummingbird InetD, Hummingbird Enterprise 2004, Hummingbird Proxy Server, Hummingbird SOCKS Client, NFS Maestro, NFS Maestro Client, NFS Maestro Gateway, NFS Maestro Server, NFS Maestro Solo, NFS Maestro Tuner, TXP, TXPM, and Xweb are trademarks of Hummingbird Ltd. and/or its subsidiaries.

All other copyrights, trademarks, and tradenames are the property of their respective owners.

ACKNOWLEDGEMENTS Portions of the code have been contributed by MIT. OpenGL is a registered trademark of Silicon Graphics Inc. This product includes software developed by the Apache Software Foundation (http://www.apache.org/). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.OpenSSL.org/). The technology used by Smart Card Manager is derived from the RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki).

FONTS The fonts distributed are included free of charge. Some of the fonts were donated towards Exceed development by Adobe Systems Inc., Bitstream Inc., MIT, and Sun Microsystems Inc. Each font contains a copyright message describing the owner of the font.

DISCLAIMER Hummingbird Ltd. software and documentation has been tested and reviewed. Nevertheless, Hummingbird Ltd. makes no warranty or representation, either express or implied, with respect to the software and documentation included. In no event will Hummingbird Ltd. be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect in the software or documentation included with these products. In particular, Hummingbird Ltd. shall have no liability for any programs or data used with these products, including the cost of recovering such programs or data.

mailto:[email protected]

http://www.hummingbird.com/

Related Documentation and Services

ManualsAll manuals are available in print and PDF. The PDF versions require Adobe Acrobat Reader and are installed only if you perform a Complete installation, or if you select them during a custom installation. Your Hummingbird product comes with the following manuals:

HelpThe online Help is a comprehensive, context-sensitive collection of information regarding your Hummingbird product. It contains conceptual and reference information, and detailed, step-by-step procedures to assist you in completing your tasks.

To view Help on any Windows NT 4.0 operating system, you must ensure that Internet Explorer v4.01 or later and the HTML Help viewer files are installed on your computer. The HTML Help viewer files are distributed in Hhupd.exe. If you have administrator privileges, Hummingbird Setup Wizard will install Hhupd.exe automatically if necessary.

Release NotesThe release notes for each product contain descriptions of the new features and details on release-time issues. They

are available in both print and HTML. The HTML version can be installed with the software. Read the release notes before installing your product.

Exceed User’s Guide Provides information on how to install and configure Exceed, connect to hosts, manage and explore services, and run X clients.

HostExplorer Host Access User’s Guide Provides information on how to access corporate mainframe data through HostExplorer terminal emulation components, as well as how to automate and configure host sessions.

HostExplorer Programmer’s Guide (PDF format only)

Provides programmers with information on how to customize HostExplorer, FTP, and WyseTerm through Visual Basic and Visual C++ scripts using HostExplorer APIs.

Hummingbird Basic Language Programmer’s Guide

Provides procedural and reference information, tips, and suggestions for working with Hummingbird Basic Language using Hummingbird Basic Workbench and Dialog Editor.

iii

Hummingbird Exposé Online

Hummingbird Exposé Online is an electronic mailing list and online newsletter. It was created to facilitate the

delivery of Hummingbird product-related information. It also provides tips, help, and interaction with Hummingbird users. To subscribe/unsubscribe, browse to the following web address:

http://www.hummingbird.com/expose/about.html

User Groups and Mailing ListsThe user group is an unmoderated, electronic mailing list that facilitates discussion of product-related issues to help users resolve common problems and to provide tips, help, and contact with other users.

To join a user group:

Send an e-mail to [email protected]. Leave the Subject line blank. In the body of the e-mail message, type the following:

subscribe exceedusers Your Name

To unsubscribe:

Send an e-mail to [email protected]. Leave the Subject line blank. In the body of the e-mail message, type the following:

unsubscribe exceedusers Your Name

To post a messages to the user group:

Send your e-mail to:

[email protected]

To search the mailing list archives:

Go to the following web site:

http://www.hummingbird.com/support/usergroups.html

iv


http://www.hummingbird.com/expose/about.html



http://www.hummingbird.com/support/usergroups.html

Contents

Chapter 1: Introducing Exceed 1

About Exceed ............................................................................................................. 3

X Window Systems and Exceed ................................................................................ 3Exceed Applications ................................................................................... 4Exceed Tools .............................................................................................. 5

Other Exceed Products .............................................................................................. 6Exceed XDK .............................................................................................. 6Exceed 3D .................................................................................................. 7

Chapter 2: Installing Exceed 9

Hummingbird Setup Wizard .................................................................................. 11Advanced Installation .............................................................................. 11

Preparing to Install .................................................................................................. 12Installation Requirements ........................................................................ 13Installation Directories ............................................................................ 14Installed Files ........................................................................................... 15Current User Versus “All Users” ............................................................. 17

Installation and Maintenance ................................................................................. 17Personal Installation ................................................................................ 17Program Maintenance for Personal Installations .................................... 20Administrative Installation ...................................................................... 21

Typical Installation Scenarios ................................................................................. 23Personal Installations Based on Administrative Privileges ...................... 23Installing onto a Terminal Server ............................................................ 24Advertised Product .................................................................................. 25Silent Installation ..................................................................................... 26Hummingbird Sconfig ............................................................................. 28

v

vi

Exceed User’s Guide

Preserving User Profiles .......................................................................................... 28

Registering and Updating ........................................................................................ 28Product Registration ................................................................................ 28Product Updates ....................................................................................... 29

Chapter 3: Advanced Installation 31

Product Access Control on a Terminal Server ....................................................... 33Stage 1: Creating an Administrative Image .............................................. 33Stage 2: Personal Installation ................................................................... 35

Removing Product Access Control from a Terminal Server ................................. 37

Customizing Installations with Sconfig .................................................................. 38About Windows Installer Database Files .................................................. 39Sconfig and Windows Installer Database Files ......................................... 40About Creating Transform Files in Sconfig ............................................. 41

Customizing Product Directories ........................................................................... 43Creating Custom Folders ......................................................................... 45

Selecting Features to Install ..................................................................................... 48Adding a Feature to an Installation Database .......................................... 48Modifying a Feature in an Installation Database ..................................... 49Removing a Feature from the Installation Database ................................ 49

Selecting Files to Install ........................................................................................... 50Adding a Custom File to an Installation Database ................................... 50Modifying a Custom File in an Installation Database .............................. 52Removing a Custom File from an Installation Database ......................... 52

Setting Product Properties ...................................................................................... 53Adding a Custom Property to an Installation Database .......................... 54Modifying a Custom Property in an Installation Database ..................... 55Removing a Custom Property from an Installation Database ................. 56

Setting the Registry .................................................................................................. 56Adding a Custom Registry Key to an Installation Database .................... 57Modifying a Custom Registry Key in an Installation Database ............... 58Removing a Custom Registry Key from an Installation Database ........... 59

Setting Shortcuts for Hummingbird Product Features ......................................... 60

Setting Hummingbird Metering Properties ........................................................... 62

Setting Properties for Hummingbird Directory Services ...................................... 63

Setting NFS Maestro Client Settings ....................................................................... 65

Contents

Setting Exceed Properties ........................................................................................ 66

Setting Custom Font Directories and Servers ........................................................ 67Setting Custom Font Directories ............................................................. 68Adding a Custom Font Directory and Font Files ..................................... 68Modifying a Custom Font Directory ....................................................... 70Removing a Custom Font Directory ........................................................ 71Removing a Custom Font File ................................................................. 71Setting Custom Font Servers .................................................................... 72Adding a Custom Font Server .................................................................. 72Modifying a Custom Font Server ............................................................. 73Removing a Custom Font Server ............................................................. 74

Setting Paths for Font Directories/Servers ............................................................. 74Setting Font Paths .................................................................................... 75

Saving the .mst File ................................................................................................. 75

Applying the .mst File to an Installation ............................................................... 76

Creating Multiple Custom Installations ................................................................. 77

Running Sconfig from a Command Line ............................................................... 77

Controlling Per-user Settings .................................................................................. 80Customizing Files and Folders ................................................................. 80Adding Registry Entries ........................................................................... 81Updating the Personal User Directory for All Users ............................... 82Passing Arguments to Per-user Settings .................................................. 83User Settings Migration ........................................................................... 83Controlling Uninstallation ....................................................................... 86

Chapter 4: Connecting to Hosts and Running X Clients 87

Connecting to Hosts ................................................................................................ 89Using the X Client Startup Wizard .......................................................... 89Running Multiple Exceed Sessions .......................................................... 91Creating a Startup File ............................................................................. 92Browsing for Hosts and Applications ...................................................... 95Load Optimization .................................................................................. 98Host and Application Files ..................................................................... 101Creating an Xstart Shortcut ................................................................... 102Running the Xstart File .......................................................................... 103About Password Aging ........................................................................... 105Launching Windows Applications ......................................................... 105

vii

vii


Using Xstart on VMS Systems .............................................................................. 106TCP/IP Transports ................................................................................. 106DECnet Transports ................................................................................. 107

Common Desktop Environment (CDE) .............................................................. 108Using Desktop Environments for Linux ................................................ 108

Window Modes ..................................................................................................... 109

Using Window Managers ..................................................................................... 110Starting HWM or MWM ....................................................................... 111Starting Remote X Window Managers ................................................... 111

Copying and Pasting .............................................................................................. 112Using a Temporary Storage Buffer ........................................................ 112Copying and Pasting Data ..................................................................... 113Copying and Pasting Graphics .............................................................. 114Copying and Pasting Between X Clients ................................................ 116Automatic Copy and Paste .................................................................... 117

Chapter 5: Advanced Connection Methods 119

Advanced Xstart Features ...................................................................................... 121Using Login Macros ............................................................................... 121Creating a Global Login ......................................................................... 122Optimizing System Loads ....................................................................... 123Running Multiple Xstart Sessions on One Host .................................... 124Password Expiry Prompts ...................................................................... 124

Running Multiple Xstart Profiles .......................................................................... 125Xsession File Sequence ........................................................................... 128Creating an Xsession Shortcut ............................................................... 128Running Multiple CDE Sessions ............................................................ 129Multiple X Display Support ................................................................... 130

Using Exceed on a Remote PC ............................................................................. 132Setting Up Xweb ..................................................................................... 133

Chapter 6: Xconfig—Configuring Exceed 135

About Xconfig ........................................................................................................ 137Xconfig Window ..................................................................................... 138Xconfig Password .................................................................................. 140

i

Contents

Mouse, Keyboard, and Other Input Devices ........................................................ 141Keyboard Input Settings ........................................................................ 141Mouse Input Settings ............................................................................. 144Input Methods for Chinese, Japanese, and Korean ............................... 148Special Considerations for Traditional Chinese .................................... 150

Network and Communication .............................................................................. 153Setting the Sequence of Events ............................................................... 153Communication Settings ....................................................................... 153About IP Discovery ................................................................................ 155Transports Settings ................................................................................ 158

Security, Access Control, and System Administration ........................................ 158Security and Access Control Settings ..................................................... 159System Administration .......................................................................... 163

X Server Protocol ................................................................................................... 164X Server Options and Extensions ........................................................... 164Extensions Settings ................................................................................. 166

Display and Video .................................................................................................. 167Configuring X Screens ........................................................................... 167Configuring Window Mode ................................................................... 168Common Settings ................................................................................... 173Monitor Information ............................................................................. 174Monitor Configuration .......................................................................... 175Video Settings ........................................................................................ 176Advanced Settings .................................................................................. 178

Copy and Paste, and X Selection ........................................................................... 180Specifying X Selection Type ................................................................... 180

Font Management .................................................................................................. 181Managing the Font Database ................................................................. 182Accessing the Font Server ...................................................................... 184Creating Font Aliases ............................................................................. 186Creating Several Aliases ......................................................................... 187

Other Server Settings ............................................................................................. 189Maximizing System Performance .......................................................... 189Power Management Settings .................................................................. 192Troubleshooting ..................................................................................... 193Accessibility ............................................................................................ 195

OpenGL .................................................................................................................. 195

ix

x


Xconfig Console ..................................................................................................... 196Remote Configuration ............................................................................ 196

Chapter 7: Hummingbird Directory Services 199

Hummingbird Directory Services Applications .................................................. 201Directory Services Explorer .................................................................... 201Hummingbird Directory Services .......................................................... 201Opening Directory Services Applications .............................................. 203

Directory Services Overview ................................................................................. 205Directory Service Protocols .................................................................... 205Directory Service Objects ....................................................................... 206Server Architecture ................................................................................. 207

Binding to Domains .............................................................................................. 208Locating Domain Servers ....................................................................... 208Directory Service Profiles ....................................................................... 210Creating Profiles ..................................................................................... 211Opening the Properties Dialog Boxes .................................................... 214

Binding to NIS ....................................................................................................... 214

Binding to NIS+ ..................................................................................................... 217Keylogin and the System Profile ............................................................ 219

Binding to LDAP ................................................................................................... 220Specifying LDAP Domains and Bind Methods ...................................... 221Retrieving Profiles from Directory Service Agents ................................ 223Securing LDAP with SSL/TLS ................................................................ 225Setting LDAP Search and Bind Options ................................................. 227Specifying Authentication Methods for LDAP Profiles ......................... 228Specifying Schemas for LDAP Profiles ................................................... 233

Exploring Directory Services ................................................................................. 236Querying Directory Service Objects ....................................................... 236Sorting Query Results ............................................................................. 237Saving Query Results .............................................................................. 238Viewing Object Properties ...................................................................... 239Modifying Profiles .................................................................................. 239Changing Domain Passwords ................................................................. 240

Specifying Name Mapping Servers ....................................................................... 242

Contents

Configuring Directory Services ............................................................................. 243Selecting Services ................................................................................... 243Modifying Profiles .................................................................................. 244Disabling User Profiles ........................................................................... 245Specifying Host Lookup Services ........................................................... 245Synchronizing Passwords ....................................................................... 246Running Keylogin .................................................................................. 247Running Command Line Applications .................................................. 247

Appendix A: Troubleshooting 249

Installation Troubleshooting ................................................................................ 251

Exceed Diagnostics ................................................................................................ 254Troubleshooting Xstart .......................................................................... 254Logs and Trace Operations .................................................................... 255

Appendix B: Connectivity Applications 259

Accessories .............................................................................................................. 261

Administrative Tools ............................................................................................. 262

HostExplorer .......................................................................................................... 265

Hummingbird FTP ................................................................................................ 265

Appendix C: HWM 267

A Quick Tour of HWM ......................................................................................... 269

The Virtual Desktop .............................................................................................. 271

HWM Configuration File ...................................................................................... 272Formatting Rules .................................................................................... 272

Functions ................................................................................................................ 274

Statements .............................................................................................................. 275Virtual Desktop ...................................................................................... 276Font Statements ..................................................................................... 279Window Statements ............................................................................... 279Color Statements .................................................................................... 280Icon Manager Statements ....................................................................... 281Menu Definitions ................................................................................... 282Mouse Button Bindings ......................................................................... 284Preprocessor Statements ........................................................................ 286

xi

xii


Appendix D: General Accessibility and Technical Support 289

General Accessibility .............................................................................................. 291Microsoft Accessibility Options ............................................................. 292

Technical Support ................................................................................................. 293

Index 295

Chapter 1

Introducing Exceed

About Exceed 3

X Window Systems and Exceed 3Exceed Applications 4Exceed Tools 5

Other Exceed Products 6Exceed XDK 6Exceed 3D 7

Chapter 1: Introducing Exceed

About Exceed

Exceed lets you access applications on UNIX workstations from existing Windows 2000/XP, Windows NT, and Windows 98/Me-based personal computers. It lets you run and display UNIX, Linux, VMS, or X Windows applications (X clients) and integrates your desktop with X Window Systems, IBM mainframes, and the Internet.

Exceed includes innovative features that accelerate performance, simplify system administration, optimize personal computing, and delivers ease of use. Users are shielded from the complexities of network computing by working within the familiar Microsoft Windows environment. Exceed is an integrated part of the Hummingbird Host Access Solutions product family which provide organizations with a comprehensive Host Access and Network Connectivity solution.

For an overview of the applications available in Exceed, see “Exceed Applications” on page 4.

By using Exceed to run remote applications on your local PC, you can:

• access powerful applications and information running on networked hosts

• establish simultaneous connections to different computers running X clients

• use an appropriate window manager to preserve your familiarity with the PC or X environment

For system administrators, Exceed provides tools to set up, configure and administer PCs remotely to ensure consistency among systems.

X Window Systems and Exceed

Exceed converts your PC into an Exceed X server. In the X Window environment, the Exceed X server is also referred to as an X window terminal or display server. Without Exceed X server software, X applications are accessible only via X terminals, UNIX, Linux, and VMS workstations.

3


Exceed works with your network transport software (TCP/IP, DECnet, or IPX/SPX) or your modem, to access X Windows applications on host computers running the X Window System. The host can be any operating system that is running the X Window environment.

The figure below shows how Exceed lets your PC access the X Windows environment.

Exceed ApplicationsExceed includes applications that serve distinct functions. Use the Exceed startup applications to connect to a host and display UNIX, Linux, VMS and X applications on your PC. Use the X Client Wizard to guide you through this process, or set up the connection manually.

Throughout this guide, xterm (a UNIX VT100 terminal emulator) is used as a sample X client. It provides a terminal emulation window on the host, and a command line where you can start other X clients.

The applications are listed and briefly described below.

Exceed Exceed X server is a PC X server that displays graphical UNIX, Linux, and X applications on your PC.

Exceed XDMCP Broadcast This shortcut lets you start the Exceed X server in XDMCP broadcast mode.

Host terminals

Applications

Your PC

Displays X Window applications on the Exceed X server

Transport software

UNIX Host

4


Exceed XDMCP Query This shortcut lets you start the Exceed X server in XDMCP query mode.

X Client Wizard This application guides you through the process of creating a connection to a host. See “Chapter 4: Connecting to Hosts and Running X Clients” on page 87 for details.

Xconfig Xconfig is a utility for configuring a variety of Exceed settings: input, communication, video, protocol, security, window modes, performance, X selection, fonts, troubleshooting, and transport settings. For details, see “Chapter 6: Xconfig—Configuring Exceed” on page 135.

Xsession Xsession lets you start multiple X clients (Xstart files) and Windows programs (Wstart files) simultaneously. For details, see “Chapter 4: Connecting to Hosts and Running X Clients” on page 87.

Xstart Xstart is an application for automating access to hosts and starting applications. Use Xstart to create Xstart (.xs) startup files and create shortcut icons to your UNIX, Linux and X applications. When you click on these icons, they automatically establish a host connection, log on, and then start an X client, a character-based host application in a terminal emulator window, or run a host-based script. For details, see “Chapter 4: Connecting to Hosts and Running X Clients” on page 87.

Exceed Connection Manager Lets you view, create, rename, delete, and modify Xstart, Xsession, and Xconfig profiles from a single user interface.

Xweb Wizard Lets you deploy and manage access to X applications by publishing Xstart profiles to a web server.

Exceed ToolsThe following tools are shipped with Exceed, and are located in the Tools folder:

HWM This tool is Hummingbird’s local Motif-like window manager. It is a local X client that provides you with a graphical interface that you can use to start and exit clients, and position and iconize the windows on your display. For more information, see “Starting HWM or MWM” on page 111 or the Exceed Help.

5


Smart Card Manager Lets you manage lists of hosts and user passwords stored on smart card devices. Xstart uses this information to authenticate users with remote hosts. (This feature is not available with 64-bit versions of the product.)

Transport Monitor This tool lets you monitor the status of current connections and the total number of open connections. It also indicates whether your transport is operating successfully. For more information, see the Exceed Help.

Xconfig Console Lets you modify Exceed X server properties through Microsoft Management Console.

Xdis The X disassembler is a diagnostic tool that lets advanced Exceed users and system administrators view Exceed trace files. It is a Java component and requires the Java Virtual Machine. For more information, see the Exceed Help. (This feature is not available with 64-bit versions of the product.)

Xsession Console Lets you modify Xsession options, open and save Xsessions, create Xstart nodes, and export lists through Microsoft Management Console.

MWM and KINPUT2 tools are shipped with Exceed XDK. For more information, see the Exceed XDK User’s Guide.

Other Exceed Products

These products are not included with Exceed. To acquire Exceed XDK and Exceed 3D, contact a Hummingbird sales representative.

Exceed XDK Exceed XDK lets you create your own local X clients and port programs originally developed for the X environment so that they run on your PC. For more information, refer to the Exceed XDK User's Guide.

6


Exceed 3D This application lets you display OpenGL-based X applications, and lets you create OpenGL X applications with Exceed XDK. OpenGL is a 3D graphics software interface that lets you create interactive programs that produce still or animated 3D color objects, including shading, lighting, and other effects.

Exceed 3D interprets OpenGL calls from an X application, and sends the information to the video card on your PC. For more details, refer to the Exceed 3D User’s Guide.

7

Chapter 2

Installing Exceed

Hummingbird Setup Wizard 11Advanced Installation 11

Preparing to Install 12Installation Requirements 13Installation Directories 14Installed Files 15Current User Versus “All Users” 17

Installation and Maintenance 17Personal Installation 17Program Maintenance for Personal Installations 20Administrative Installation 21

Typical Installation Scenarios 23Personal Installations Based on Administrative Privileges 23Installing onto a Terminal Server 24Advertised Product 25Silent Installation 26Hummingbird Sconfig 28

Preserving User Profiles 28

Registering and Updating 28Product Registration 28Product Updates 29

Chapter 2: Installing Exceed

Hummingbird Setup Wizard

Hummingbird Setup Wizard is the interface displayed by Windows Installer. Setup Wizard is based on three standard, top-level user interfaces or modes: installation, administration, and advertisement. Each defines a different installation path and user interface flow.

For common issues and questions about Hummingbird Setup Wizard, see ”Appendix A: Troubleshooting”.

Setup Wizard does the following:

• uses the Windows Installer service to maintain the applications and resources installed on the computer

• determines the correct path to specific components

• ensures that applications do not point to missing files

The Windows Installer service views all applications as three logical building blocks: products, features, and components.

Advanced InstallationSee “Chapter 3: Advanced Installation” for more information about:

• installing onto a Terminal Server using product access control

• customizing installations with Sconfig

• Hummingbird Administrator Toolkit (Files and Settings Transfer Wizard, Metering Client Settings, and Media Location Manager)

Note: You cannot preserve user profiles for products before version 7.0.

11


Preparing to Install

System and shared files currently in use cannot be updated. Close all applications before proceeding with the installation.

Hummingbird connectivity products (version 7.0 and later) use Windows Installer. It is included with Windows 2000/XP/Server 2003 and Windows Me.

If Windows Installer is not present on your Windows 98 or Windows NT 4.0 operating system, then Hummingbird Setup Wizard installs and configures the service.

If Windows Installer is present on the operating system, Setup Wizard checks the version. If necessary, Windows Installer is updated.

Note: Before installing on Windows NT/2000/XP/Server 2003, it is recommended that you log on with Administrator authority. You also require write access to the Windows system directory and registry. If necessary, consult your system administrator.

Note: The first time Hummingbird Setup Wizard installs and configures Windows Installer, you are prompted to restart the machine after installation is complete.

12


Installation RequirementsThe following table outlines installation requirements for Hummingbird connectivity products:

1 Approximate disk space for Typical and Complete setup types, and for local cache (if selected during setup).

2 Administrator privileges are required to install some portions of the product.

Product Operating SystemDisk Space (MB)1

Other RequirementsTypical Complete Cache

Exceed Windows 98

Windows Me

Windows NT2 (SP 6 or later)

Windows 2000/XP2

Windows Server 20032

94 187 205 Winsock compliant TCP/IP (Winsock 2 recommended)

Exceed XDK 18 63 87 Exceed or Exceed PowerSuite

Microsoft Visual C/C++ (MSVC) 5.0 or later, for X client development

Exceed 3D 4 7 14 Exceed or Exceed PowerSuite

Microsoft Visual C/C++ (MSVC) 5.0 or later, for X client development

Exceed PowerSuite


An assigned IP address and the ability to communicate with other computers on the network (Windows NT)

A HOSTS file if a domain name server is unavailable (Windows 98)—see the operating system documentation for details

Host Access Services

Windows 98

Windows Me

Windows NT2 (SP 6 or later)

Windows 2000/XP2

Windows Server 20032


13


Third Party SoftwareJRE consists of the Java Virtual Machine, the Java platform core classes, and supporting files.

Certain third party software must be installed to run some Hummingbird products. For example, Sun Java Runtime Environment (JRE) is required to run Java programs. You must install JRE before running Xdis, an Exceed diagnostic tool.

Hummingbird Master Setup also lets you install third party add-ons such as Adobe Acrobat Reader.

Installation DirectoriesHummingbird Setup Wizard installs program-specific and user-specific files to the directories described below.

Setup Wizard supports the Uniform Naming Convention (UNC) so you can begin path specifications with \\ in place of the disk drive to specify a shared directory on a file server. For example:

\\machine_specification\share_name

Installation Description Location/Type

Destination folder

Program files install into the destination folder (also known as the root home directory). It is recommended that you use the default directory:

C:\Program Files\Hummingbird\Connectivity\Version\

However, you can specify a different directory.

Location: a remote network drive or a local hard drive.

Can be a read-only directory.

User directory

User files install into the user directory.

These files are configuration files or related files that your Hummingbird product can change.

There are several kinds of user directories and user files. For more information, see “Installed Files” on page 15.

Warning: Do not make a user directory read-only.

Location: a remote network drive or a local hard drive.

14


where machine_specification is the name of the computer to which you are connecting, and share_name is the name of the shared directory. If you use UNC names to install to a Novell server, you must install the OS/2 support patch on the NetWare server as NetWare servers do not support UNC paths.

Installed FilesUser files for Hummingbird connectivity products fall into several categories: per-machine, per-user, and shared.

Per-machinePer-machine files are local so that key operating system components, such as device drivers and services, can reliably access them during login.

Per-machine files are those application or service files that, when changed, affect all users of the computer. An example is the inetd.ini file. If you change inetd.ini to stop the Telnet daemon from running, then regardless of which user is logged onto the computer, the InetD service rejects Telnet connections.

The following are the per-machine file locations:

Per-userPer-user files are all application or service files that, when changed, affect only the user who is making the change (that is, the currently logged in user). An example of a user-specific file is Exceed.xcfg. If you configure Exceed.xcfg with Xconfig to use a certain display, then other users of the machine are not affected.

Operating System Per-machine—File Location

Windows 98/Me

C:\Windows\System\Hummingbird\Connectivity\version\

Windows NT/ 2000/XP/Server 2003

C:\Winnt\System32\Hummingbird\Connectivity\version\

Note: Each user of the product on the machine receives a personal user directory.

15


The following are the default locations for per-user files:

Global UserSimilar to per-machine directories and files, the global user folder is available to all users of the machine. Generally, the global user folder is intended as writable by administrators and readable by all users. In certain cases, folder permissions might be changed to allow everyone write access.

Files such as user profiles and mandatory settings are accessible from the global folder on the local machine (regardless of the current user). They can also be made accessible from a central location (for example, a network share) to multiple users when they install the product. During installation (Windows NT/2000/XP/Server 2003), these files are copied locally to a shared folder under the “All Users” folder.

Operating System Per-user Files—Default Location (Current User)

Windows 98/Me C:\Windows\Application Data\Hummingbird\Connectivity\version\

Windows 98/Me (user profiles enabled)

C:\Windows\Profiles\%USERNAME%\Application Data\Hummingbird\Connectivity\version\

Windows NT 4.0 C:\Winnt\Profiles\%USERNAME%\Application Data\Hummingbird\Connectivity\version\

Windows 2000/XP/Server 2003

C:\Documents and Settings\%USERNAME%\Application Data\Hummingbird\Connectivity\version\

Note: This location is usually hidden (by default).

Operating System Global User Folder—Default Location (Current User)

Windows 98/Me C:\Windows\All Users\Application Data\Hummingbird\Connectivity\version\Global

Windows NT/2000/XP/Server 2003

C:\Documents and Settings\All Users\Application Data\Hummingbird\Connectivity\version\Global

16


Current User Versus “All Users”Since version 10, Hummingbird Connectivity products use individual or personal profiles even when a product is installed for all users of the machine. During product installation, you can specify that user settings are shared by all users of the machine by storing application settings in a common (shared) user directory. For more information about customizing individualized installations, see “Chapter 3: Advanced Installation”.

Installation and Maintenance

This section describes basic installation procedures and setup types:

• personal installation—one user installs the product on one computer

• administrative installation—systems administrators create an image of the product at a network location

For examples of how to implement these procedures, see “Typical Installation Scenarios” on page 23.

Personal InstallationAutorun launches the Hummingbird Master Setup application when you insert the CD into your drive. If Master Setup does not launch automatically, run Msetup.exe from the root directory of the CD.

To configure Windows Installer and prepare Setup Wizard:

1 In the Hummingbird Master Setup application window, you can install additional Hummingbird products (such as Hummingbird SOCKS Client), third party add-ons, register online, or view release notes. Otherwise, click Install Product, and then Personal Installation.

Note: For some installation scenarios (such as those involving advertised shortcuts), Windows NT 4.0 requires Internet Explorer 4.01 or greater, and Windows Desktop Update (shell32.dll version 4.72.3110.0). Otherwise, at least Internet Explorer 5.0 is required.

17


2 If you are prompted, select a setup language and click OK. English is the default.

3 Your Hummingbird product prepares Setup Wizard, checks the operating system, and checks the current Windows Installer version.

If necessary, the version is updated and the Setup Wizard continues. If Windows Installer is not present on your operating system, Setup Wizard installs the service.

4 Setup Wizard initializes and prepares Windows Installer.

If a previous version of this product or another compatible connectivity product is installed, the Product Migration dialog box opens. You can select whether to migrate settings (and remove that product). Click Next.

If there is no previous product, the Welcome dialog box opens. Click Next.

The Next button is dimmed if the terms of the license agreement are not accepted.

5 Read the licensing agreement. If you select the option that indicates the terms are acceptable, then click Next.

6 The Customer Information dialog box opens. Type the appropriate information and click Next.

Note: To quit installation, click Cancel in any Setup Wizard dialog box. Your computer is not affected if you do this before the Setup Wizard copies files. To review or change settings in a previous dialog box, click Back.

Note: Failure to read or understand the License Agreement does not affect the terms and conditions of the agreement.

18


7 The Destination Folder dialog box opens (except if you’re installing Exceed 3D or Exceed XDK).

Accept the default installation folder for the product, or click Change to open a dialog box for browsing to an alternate location. Click Next.

8 The User Directory Location dialog box opens. Select whether or not application settings are stored in a per-user or a (common) shared directory. Click Next.

9 The Setup Type dialog box opens. Select a setup type and click Next.

If Custom setup type is selected, the Custom Setup dialog box opens. Select whether or not specific features and sub-features are installed. Click Next.

10 If the metering client is selected for installation, then the Hummingbird Metering Client Settings dialog box opens. Type the required information and click Next.

11 The Additional Install Options dialog box opens. Select install options and click Next.

• Local Cache—Copies setup files locally so that future repairs or patches do not prompt for a source.

• Updates—If Hummingbird Update was selected (that is, as part of a Complete setup type or specifically in Custom Setup), the first option runs that utility after installation to determine if a product update is available. The last option launches the default browser and goes to the Hummingbird Update web site.

• Tuning—Runs Exceed X Server Tuning which lets you override the current drawing methods used by the server and determine the optimal graphics configuration for Exceed.

Note: This dialog box is visible but options are disabled if another Connectivity product is already installed.

Note: Some product features are not affected by changes to the destination folder.

19


12 The Introducing Exceed onDemand dialog box opens. Select whether or not to install the Exceed onDemand Client installer following this installation. Click Next.

13 A dialog box indicates Setup Wizard is ready to begin installation. Click Install.

14 A dialog box opens and indicates installation is complete. Click Finish and you are prompted to restart your computer.

For information about product modification, repairs, or removal, see below.

Program Maintenance for Personal InstallationsProgram maintenance lets you modify, repair, or uninstall existing Hummingbird products and features.

To launch Hummingbird Setup Wizard in maintenance mode:

1 You can open Program Maintenance by running Msetup.exe from the product CD. Alternatively, double-click Add/Remove Programs in Control Panel, select the Hummingbird program, and click Add/Remove.

The Welcome dialog box opens.

2 In the Welcome dialog box, click Next. The Program Maintenance dialog box opens where you can select a maintenance option.

For more information about maintenance options, see the following procedures.

To modify the install state of program features:

1 In the Program Maintenance dialog box, select Modify and click Next.

2 The Custom Setup dialog box opens. Expand the feature tree and change the install state, as necessary. Click Next.

3 Setup Wizard prompts when it is ready to modify the program. Click Install and the install state of program features changes according to your specifications.

4 Installation (modification) proceeds to completion. Click Finish to exit.

20


To repair a program:

1 In the Program Maintenance dialog box, select Repair and click Next.

2 The Ready to Repair the Program dialog box indicates Setup Wizard is ready. Click Install to repair errors such as missing or corrupt files, shortcuts, and registry entries.

3 Program repair proceeds to completion. Click Finish to exit.

To remove a program:

1 In the Program Maintenance dialog box, select Remove and click Next.

2 The Remove the Program dialog box indicates Setup Wizard is ready. Click Remove to uninstall the program.

3 Program removal proceeds to completion. Click Finish to exit.

Administrative InstallationAutorun launches the Hummingbird Master Setup application when you insert the CD into your drive. If Master Setup does not launch automatically, run Msetup.exe from the root directory of the CD.

Administrative installations let you create a centralized image of the product. This means that many users can install the product without the original CD media.

Note: With Windows Installer, you can uninstall (remove) only one program (product) at a time. Ensure that all programs associated with the product you are uninstalling are closed.

Note: If the current version 10 product is the last product (or only product) being removed, then the local cache folder is removed as well.

21


To run Setup Wizard in Administrative mode:

1 Run Msetup from the product CD. In the Hummingbird Master Setup application window, you can select options to install third party add-ons, register online, or view release notes. Otherwise, to run Setup Wizard, click Install Product, then click Administrative Installation.

Alternatively, from the product directory on the CD, run:

setup /a

2 Select a setup language and click OK. This language will apply to all installations from the copied image or shared image.


If necessary, the version is updated and the Setup Wizard continues. If Windows Installer is not present on your operating system, Setup Wizard installs the service.

4 After configuring Windows Installer and preparing to install, Setup Wizard proceeds to the Welcome dialog box. Click Next.

5 The Network Location dialog box opens. Accept the default installation folder for the product, or click Change to open a dialog box for browsing to an alternate network location. Click Next.

6 The Ready to Install Network Image dialog box opens. Click Install. Installation of the network image proceeds to completion.

Note: To quit the installation, click Cancel in any Setup Wizard dialog box. Your computer is not affected if you do this before the Setup Wizard copies files. To review or change settings in a previous dialog box, click Back.

22


Typical Installation Scenarios

This section describes installation scenarios. The conditions and parameters affecting implementation in your environment may vary from these examples.

Personal Installations Based on Administrative PrivilegesAdministrators, or users who do not have Administrator privileges (Windows NT/2000/XP/Server 2003), or “Any User” in Windows 98, are able to perform personal installations for Exceed products.

Connectivity Secure Shell, HostExplorer, Hummingbird FTP, Hummingbird InetD, and NFS Maestro products require Administrator privileges for personal installations in Windows NT/2000/XP/Server 2003. However, “Any User” in Windows 98 can install these products or features.

Installation—Without Administrator PrivilegesThis scenario assumes:

• you are logged in to the PC as a user, not as Administrator

• you do not have administrative privileges

• you are installing the product for one user (the current user) on one PC

• the product CD is available locally or on the network

To launch a personal installation without Administrator privileges:

1 Launch Setup Wizard in installation mode by one of the following methods:

• run setup.exe from the product CD or from a server image

• run Msetup.exe from the product CD

Note: Some product features are not available for installation if you do not have administrative privileges.

23


If setup.exe is run from a server image, you are not prompted to select an installation language. This is already selected during image installation.

2 If you are prompted, select a language for the installation. English is the default.

3 Dialog boxes provide information and prompt for input.

4 In the Setup Type dialog box, select either Typical, Custom, or Complete.

Installation—With Administrator PrivilegesThis scenario assumes:

• you are logged in to the PC as the (local) Administrator


To launch a personal installation as Administrator:

1 Launch Setup Wizard in installation mode by one of the following methods:

For more information about creating a server image, see “Silent Installation” on page 26.

• run setup.exe on the product CD or from a server image

• from the product CD, run Msetup.exe

2 Dialog boxes provide information and prompt for input.

3 The Setup Type dialog box opens. Select a setup type.

Click Next.


5 A dialog box opens and indicates installation is complete. Click Finish.

Installing onto a Terminal ServerYou can perform personal installations on a Terminal Server. However, there is no control over who can access shortcuts, user files, or use the product.

Note: For Custom setup type, a Custom Setup dialog box opens. Customize the installed program features.

24


An alternative option is to enable product access control—only users granted permission to use the product get access to shortcuts and user files. For more information about product access control on a Terminal Server, see “Chapter 3: Advanced Installation”.

Advertised ProductWindows NT 4.0 requires Internet Explorer 4.01 (SP1) or greater, and Windows Desktop Update (shell32.dll version 4.72.3110.0 or later). Advertised features are not recommended on a Terminal Server.

Advertisement (install on demand or deferred installation) means all features of a product are available even if they are not installed on the computer. This scenario assumes:



To advertise a product and all its features:

1 Launch Setup Wizard in advertisement mode by one of the following methods:

• on the command line, type E:\setup /jm—where E:\ is the CD-ROM drive

• run Msetup.exe from the product CD

2 Select the Complete setup type.

Shortcuts and registry entries exist on the computer, but files are not installed.

3 A Hummingbird product icon is installed on the PC desktop, and in the Windows program group (on the Star t menu), for each feature.

Note: Not all product features can be advertised.

Note: For a deferred installation, the product CD must be in the drive and the drive must be accessible.

Note: Shortcuts for features requiring Administrator privilege will not launch correctly if the user does not have the required privileges to install the feature.

25


Silent InstallationA silent installation runs in the background.

This scenario assumes:



To run a silent installation:

1 Launch Setup Wizard from the command line using the following syntax:

E:\setup /S /V/qn [/lnnnn]

where E:\ is the CD-ROM drive. The following describes options:

2 Installation proceeds to completion.

Note: This scenario describes a local installation.

Option Description

/S Specifies a silent installation.

Note: S is upper-case.

/V/qn /V passes parameters to Msiexec.exe.

Note: There are no spaces between the /V and /qn options and that V is upper-case. If a character string contains a space, put quotes around it. For example: /V”parameter space”

/lnnnn Overrides the default English language installation where nnnn is the transform file name.

Note: For nnnn, type only the number but not the .mst extension.

/RS|RE “command” Run the “command” either at the startup (/RS) or at the end (/RE) of setup.

For example, to launch a file in Notepad at startup:

/RS “notepad readme.txt”

26


Microsoft Systems Management Server (SMS)An Administrator can use SMS to manage network computers, distribute software from a central location, and perform a variety of other system management tasks. The Administrator can install a package of products simultaneously on multiple computers.

Requirements:

You can get the latest Service Pack for SMS from the Microsoft web site.

• SMS version 2.0 with Service Pack 2 (or greater)

• SMS Client (installed on each client computer) supplied with SMS Server

• Windows Installer on the client computer

A package contains source files for the program and various details for directing the software distribution process.

To distribute a product using SMS, the Administrator must create a package definition file according to SMS instructions. For convenience, Hummingbird provides default .sms files for all products.

These are the default scenarios in each package definition file:

• Typical

• Typical Language

• Silent Typical

• Silent Complete

• Uninstallation

When a package is run through SMS, it prompts you to select one of these options (scenarios). Use the following command line parameters to apply modifications or create new package definition files:

Command Line Parameter Description

/i Installs or configures a product.

/q Sets user interface level (silent).

INSTALLLEVEL=150 Does a complete install.

TRANSFORMS=nnnn.mst Specifies the product language where nnnn is the transform file name.

27


For more information about Msiexec command line options, see the Windows Installer documentation available in the MSDN online library at msdn.microsoft.com

Refer to Microsoft documentation for command line parameters, switches, and other information required for Windows Installer and Systems Management Server.

Hummingbird SconfigSconfig (Setup configuration) lets you customize the installation of software on local and network machines. Use it to customize the folders installed by Setup Wizard, determine what is installed (as well as limit functionality or optimize disk space), and simplify user input. For more details, see “Chapter 3: Advanced Installation”.

Preserving User Profiles

See Hummingbird Administrative Tools Help for more information on Files and Settings Transfer Wizard options.

If you choose to preserve user settings on the Product Migration page, Hummingbird Setup Wizard generates a .Humfst file (Files and Settings Transfer Wizard-compatible). After default settings from version 10 are installed, settings from this file are imported to the machine.

This allows for the replaying of the migration process at another time by using the Files and Settings Transfer Wizard. In addition, there are properties available in Sconfig that let you import a.Humfst file although an older product is not installed. This also allows for the migration of product settings across the usual product boundaries. For example, you can export settings from an HostExplorer installation into an Exceed installation during setup.

Registering and Updating

Product RegistrationOnline registration is available by:

• running Msetup from the product CD, then clicking Register Online

• completing and registering the form at the following URL:

http://www.hummingbird.com/register/

28

http://www.hummingbird.com/register/


Alternatively, complete the registration card provided in the product package and mail it to Hummingbird Ltd. Registration means that you and your organization are recognized as a licensed product owner with all rights and privileges. This makes you eligible to receive a wide range of customer services, such as a free subscription to our quarterly newsletter, Exposé Online, as well as notification of software updates and new products. If you and your organization move to a new location, complete and mail the change of address card included in the product package to ensure that you continue receiving update notices and other important information.

Product UpdatesWebUpdate options for your Hummingbird product are preset. For update options, right-click the Hummingbird product entry in the WebUpdate dialog box and select from the drop-down menu.

If necessary, you can modify connection settings for updating the product by using Hummingbird Update.

To update the product:

1 Click Hummingbird Update in the Administrative Tools folder of the Hummingbird Connectivity program group.

2 If an update is available, you are prompted to install it. Click Yes.

3 The update is downloaded. Setup Wizard prepares the setup process.

4 You are informed when Setup Wizard is ready. Click Next.

5 Installation proceeds to completion.

Note: The WebUpdate application is not available if you performed a personal installation without Administrator privileges. Instead, an HTML file is created that links to a web site for Hummingbird updates.

Note: You can also select the Hummingbird product entry and click Check for Update in the WebUpdate dialog box.

29

Chapter 3

Advanced Installation

Product Access Control on a Terminal Server 33Stage 1: Creating an Administrative Image 33Stage 2: Personal Installation 35

Removing Product Access Control from a Terminal Server 37

Customizing Installations with Sconfig 38About Windows Installer Database Files 39Sconfig and Windows Installer Database Files 40About Creating Transform Files in Sconfig 41

Customizing Product Directories 43Creating Custom Folders 45

Selecting Features to Install 48Adding a Feature to an Installation Database 48Modifying a Feature in an Installation Database 49Removing a Feature from the Installation Database 49

Selecting Files to Install 50Adding a Custom File to an Installation Database 50Modifying a Custom File in an Installation Database 52Removing a Custom File from an Installation Database 52

Setting Product Properties 53Adding a Custom Property to an Installation Database 54Modifying a Custom Property in an Installation Database 55Removing a Custom Property from an Installation Database 56

Setting the Registry 56Adding a Custom Registry Key to an Installation Database 57

Modifying a Custom Registry Key in an Installation Database 58Removing a Custom Registry Key from an Installation Database 59

Setting Shortcuts for Hummingbird Product Features 60

Setting Hummingbird Metering Properties 62

Setting Properties for Hummingbird Directory Services 63

Setting NFS Maestro Client Settings 65

Setting Exceed Properties 66

Setting Custom Font Directories and Servers 67Setting Custom Font Directories 68Adding a Custom Font Directory and Font Files 68Modifying a Custom Font Directory 70Removing a Custom Font Directory 71Removing a Custom Font File 71Setting Custom Font Servers 72Adding a Custom Font Server 72Modifying a Custom Font Server 73Removing a Custom Font Server 74

Setting Paths for Font Directories/Servers 74Setting Font Paths 75

Saving the .mst File 75

Applying the .mst File to an Installation 76

Creating Multiple Custom Installations 77

Running Sconfig from a Command Line 77

Controlling Per-user Settings 80Customizing Files and Folders 80Adding Registry Entries 81Updating the Personal User Directory for All Users 82Passing Arguments to Per-user Settings 83User Settings Migration 83Controlling Uninstallation 86

Chapter 3: Advanced Installation

Product Access Control on a Terminal Server

As of version 10, a personal installation on a Terminal Server means that all users of the machine can use the product. Providing the same level of access control that existed in previous versions requires a two-stage process. This process consists of creating an administrative image on the Terminal Server, and installing the Hummingbird product onto the Terminal Server from the newly-created copy. You can run a terminal server installation on Windows NT4 Terminal Server Edition, Windows 2000 Server, Advanced Server with Terminal Services enabled, and Windows Server 2003.

The following procedure assumes:

• you are logged onto the Terminal Server as the Administrator


Stage 1: Creating an Administrative ImageYou must apply the appropriate product-specific transform to your Hummingbird product before the product can be installed on a machine with Terminal Server capabilities.

To create an Administrative Image on the Terminal Server:

1 From the product directory on the CD, run the following commands from a command prompt.

For Exceed:

setup /a /v”TRANSFORMS=ExceedTSE.mst”

For Exceed 3D:

setup /a /v”TRANSFORMS=Exceed3DTSE.mst”

For Exceed XDK:

setup /a /v”TRANSFORMS=ExceedXDKTSE.mst”

33


For Exceed PowerSuite:

setup /a /v”TRANSFORMS=ExceedPSTSE.mst”

2 Select a setup language and click OK.


• If necessary, the version is updated and the Setup Wizard continues.

• If Windows Installer is not present on your operating system, Setup Wizard installs the service. Click Restar t System to continue installing the product.

Setup Wizard reboots the computer. This is necessary only the first time Windows Installer is configured and installed on your Windows NT 4.0 Terminal Server Edition operating system.

4 After configuring Windows Installer and preparing to install, Setup Wizard opens the Welcome dialog box. Click Next.

Warning! When creating the Administrative Image, you must apply the product-specific transform:

• Exceed—apply ExceedTSE.mst

• Exceed 3D—apply Exceed3DTSE.mst

• Exceed XDK—apply ExceedXDKTSE.mst

• Exceed PowerSuite—apply ExceedPSTSE.mst

Note: The language you select during this setup process will be the language of the administrative image.

Note: To quit the installation, click Cancel in any Setup Wizard dialog box. Your computer is not affected if you do this before the Setup Wizard begins copying files. To review or change settings in a previous dialog, click Back.

34


5 The Network Location dialog box opens. Accept the default installation folder for the product or click Change to browse to an alternate network location. A folder with the default name Admin is created on the terminal server. The Administrative Image will be placed in the Admin folder.

6 Click Next. The Ready to Install Network Image dialog box opens.

7 Click Install. Installation of the Administrative Image proceeds to completion.

Stage 2: Personal InstallationAfter creating an Administrative Image, you can install personal installations of your Hummingbird product onto the Terminal Server from this image.

To install Exceed, Exceed 3D, Exceed XDK, and Exceed PowerSuite onto the Terminal Server:

1 From the command line, change the directory to C:\Admin and run

setup.exe

where C:\Admin is the name of the drive and folder where the Administrative Image is located.

Note: Each user has private shortcuts, registry entries, and user files. User files are copied from the Admin folder. Each user must have at least read access to the Admin folder installation point.

Note: The Administrative Image must be readable by all users who are granted permission to use Exceed, Exceed 3D, Exceed XDK, and Exceed PowerSuite.

Note: The Admin folder and its contents must remain available during the lifetime of on the terminal server. Multiple terminal servers can share the same Admin folder.

35


2 Click OK.

3 Setup Wizard opens the Welcome dialog box. Click Next.

4 Read the Licensing Agreement. If you select the option that indicates the terms are acceptable, then click Next.

5 The Customer Information dialog box opens. Type the appropriate information and click Next.

Destination Folder is synonymous with home directory (the directory in which the product is installed).

6 The Destination Folder dialog box opens. Accept the default installation folder for the product or click Change to browse to an alternate location. Click Next.

7 The Setup Type dialog box opens. Select a setup type.

Click Next.


Note: Failure to read or understand the License Agreement does not affect the terms and conditions of the agreement.

Note: Some product features are not affected by changes to the destination folder.

Note: For Custom setup type, a Custom Setup dialog box opens. Customize the installed program features. For more information, see the previous chapter.

Note: The Hummingbird product installed on each user’s profile uses the setup type that the administrator chooses in the Setup Type dialog box.

36


You can perform this procedure later by using the Performance application in Xconfig.

9 A dialog box opens and indicates installation is complete. Click Finish.

Upon completion of Stage 2, the per-user installation of the Hummingbird product is enabled and your Hummingbird product will be automatically installed into the appropriate user profile the next time each user logs on.

For more information about setting up access permissions, see Hummingbird User Manager Help.

If users are granted product access permission through a Hummingbird Product User Group, your Hummingbird product automatically installs into the appropriate user profile the next time user group members log on. Alternatively, your product will automatically uninstall from profiles of users who are not user group members. Exceed10_Users is the default group name for Exceed, Exceed 3D, Exceed XDK, or Exceed PowerSuite users.

Removing Product Access Control from a Terminal Server

You must have administrative access to remove your Hummingbird product from the Terminal Server using the Add/Remove Programs option. The Add/Remove Programs procedure removes the binary files from the Program files folder and prevents existing users from using the product. Existing personalized user settings and shortcuts will be removed automatically for each user when each user next logs on.

For information about product modification, repairs, or uninstalling using the Add/Remove Programs option, see “Program Maintenance for Personal Installations” in Chapter 2.

Note: To uninstall a product from the Terminal Server for one or more users, but not for all users, remove the user(s) from the user group. Do not delete the user(s). For information on creating and managing user groups, see the Windows NT/2000 Help.

If the Exceed parent product is not available to the user—either because it is uninstalled or access permission has not been granted—Exceed 3D and Exceed XDK are removed as well.

37


The following conditions must be met before disabling UsrSetup and removing the UsrSetup file from the machine:

• You are not planning to install your Hummingbird product again.

For more information about uninstalling using the Add/Remove Programs option, see the previous chapter.

• The Terminal Server personal installation has been uninstalled using the Add/Remove Programs options. After this uninstallation, when a user logs on, customized settings and user files are automatically uninstalled from his/her user profile. You can disable UsrSetup and remove the UsrSetup file only after this process is complete.

If the above conditions have been met, you can disable UsrSetup.

To disable UsrSetup:

1 From the Terminal Server command line, run the following command:

%WINDIR%\System32\Hummingbird\Connectivity\UsrSetup /unregserver

2 Remove the UsrSetup file from the Terminal Server machine.

Customizing Installations with Sconfig

Users in an enterprise often have different software needs even within

applications, and, therefore, may require tailored installations of Hummingbird software to meet those needs. For example, some users may require Hummingbird product features, such as Telnet and FTP setting files, to connect to frequently used hosts, while other users have no need for this functionality. Instead, some users may require specific font settings and features to be installed with their Hummingbird products.

For more information on Windows Installer, see the installation chapter.

Sconfig works with Microsoft Windows Installer database files (.msi and .mst) to let you create tailored installations of Hummingbird software for users with different needs.

Note: Disabling UsrSetup is an optional procedure.

38


Sconfig lets you:

• Customize the directories in which the product is installed, and add custom folders.

• Tailor the list of applications or components to be installed. You can alter the list to limit the functionality available to users, or to optimize the use of disk space.

• Simplify user input during installation by preselecting information, such as the properties of the software being installed.

• Provide a uniform user experience, and maintain a uniform system configuration across the network.

About Windows Installer Database FilesSconfig works with Microsoft Windows Installer database files (.msi and .mst) to let you create tailored installations of Hummingbird software for users with different needs.

Microsoft Software Installation Files (.msi)Microsoft Windows Installer uses Microsoft Software Installation files (.msi) to install the Hummingbird product. An installation file is a database file that contains default installation information specifying which product components are installed and in which directories.

Microsoft Transform Files (.mst)When a user alters an installation in Microsoft Windows Installer, the changes are not applied directly to the installation files, but stored in another file called a Microsoft Transform file (.mst). Like the installation (.msi) file, the Microsoft Transform file is a relational database with information about product components and installation directories, but the transform file contains only the amendments a user wants to apply to the default settings contained in the installation file. The result is a customized installation.

Note: Sconfig does not install with a Typical installation. When installing the Hummingbird software on the administrator machine, you must choose Custom or Complete installation.

39


Sconfig and Windows Installer Database FilesSconfig makes use of the relationship between installation (.msi) files and transform (.mst) files.

Instead of changing the product’s preconfigured installation file itself, Sconfig saves all amendments in a transform file. You can then package the transform file with an installation (that is, apply it to an .msi file) and distribute the installation. If changes are required in the future, you can also use Sconfig to open and update a previously generated transform file.

When preparing for multiple custom installations, you need to create a separate transform file for each group of users. You can then apply each transform file to the Hummingbird product’s installation file, thus temporarily updating the installation file.

Before you can customize installation options, you must specify the transform (.mst) and installation (.msi) files with which you want to work. You can work with a new transform file or with a preconfigured file.

You can also indicate if the transform file you want to create is intended for installation on a terminal server.

To open an MSI/MST file:

1 After you open Sconfig from the Windows Star t menu, a welcome page appears. Click Next to continue.

2 On the Database Selection page, specify the installation file (.msi) that you want to customize and click Next. You can choose an installation file in one of the following ways:

• Specify an installation file that you previously configured.

• Browse for a new installation file.

Note: Sconfig is not installed in a Typical installation. It installs only if you choose Custom or Complete installation type.

40


3 On the Transform Selection page, specify the transform file (.mst) that you want to create. You can specify a transform file in one of the following ways:

• Specify a transform file that you previously configured.

• Browse for a new transform file by clicking the Browse button.

• Create a new one yourself. You can do this by clicking the Browse button and specifying a name and location for the file.

4 If the transform file you want to create is intended for installation on terminal servers, select Create Terminal Services (TSE) Client Transform.

5 Click Next to continue.

About Creating Transform Files in SconfigWhen you start Sconfig, the Sconfig Wizard opens. After you specify the installation file (.msi) you want to work with, and the transform file (.mst) you want to create or modify, the wizard displays the Customize page, which provides options and settings that you can use to customize the installation.

Note: If you selected a transform file that was generated with a previous version of Sconfig, the user interface may differ from what is documented.

Note: If you selected a TSE-specific .msi file on the Database Selection page, this option is not available.

Note: Some customization options are not available if you are creating a Terminal Services Client transform.

41


You can browse though the following configuration options by clicking them in the option tree located in the left pane of the wizard:

Product Directories The Directories option lets you customize product directories for the installation of the Hummingbird product. You can also access the Custom Folders option in the Product Directories folder to add custom folders to the installation. See “Customizing Product Directories” on page 43 for more information.

Product Features The Features option lets you specify which optional product features you want to install. See “Selecting Features to Install” on page 48.

Files This option lets you add external files to the Hummingbird product installation. See “Selecting Files to Install” on page 50 for more information.

Product Properties The Proper ties option lets you customize properties to change the behavior of the installation package and set properties for Hummingbird product features. See “Setting Product Properties” on page 53 for more information.

Registry The Registry option lets you preset the Registry editor for any Windows operating system registry. The advantage of editing the registry before the installation is that it saves time, especially when installing for multiple target machines. See “Setting the Registry” on page 56 for more information.

Custom Shortcuts The Shortcut option lets you create custom shortcuts on user machines for any Hummingbird product feature added to your installation database. See “Setting Shortcuts for Hummingbird Product Features” on page 60 for more information.

Metering Properties The Metering option lets you modify or remove properties for the Hummingbird Metering Server.

Directory Services Properties Available only in NFS Maestro and Exceed installations, the Directory Services options let you specify property settings for Hummingbird Directory Services as well as service-specific property settings for LDAP, NFSD, NIS and NIS+.

Exceed Properties Available only in Exceed installations, the Exceed Settings option lets you modify or remove properties. See “Setting Exceed Properties” on page 66 for more information.

42


NFS Properties Available only in NFS Maestro and Exceed PowerSuite installations, the NFS Settings option lets you modify or remove properties for NFS Maestro Client. See “Setting NFS Maestro Client Settings” on page 65 for more information.

Custom Font Directories and Servers Available in Exceed and Exceed PowerSuite installations, the Custom Fonts option lets you install customized font directories and servers to the Exceed Xconfig utility. See “Setting Custom Font Directories and Servers” on page 67 for more information.

Custom Font Paths Available only in Exceed and Exceed PowerSuite installations, the Font Paths Settings option lets you change the order in which font directories/servers are loaded by the X server. See “Setting Paths for Font Directories/Servers” on page 74 for more information.

After you make the necessary modifications in each of the above options, you can use the wizard to save the transform file.

Customizing Product Directories

To view the Directories options, click Directories in the option tree located in the left pane of the Customize page.

The Directories options let you specify where you want the Hummingbird product to be installed. Depending on the type of installation you are configuring, local or Terminal Server (TSE), you can set one or both of the following directories:

• Destination

• Current User

43


To customize directories:

1 Click Directories in the option tree. The Directories pane appears on the right.

2 If you are creating a terminal server transform, proceed to step 3. In the Destination Folder box, type the directory where all non-volatile files will be stored.

3 Select one of the two User Directory options. (In TSE mode, only the first of the following options appears.)

• Individual User directory—Type the directory where all volatile files will be stored for the current user. This path is used to generate the personal user directory for every user of the machine. Use a property that changes from user to user so that the path us unique for each. For example, you can use [%USERNAME] or [AppDataFolder].

• Single User directory—Type the directory where you want user files to be shared among all users of the destination machine. This could be any folder on the machine.

44


Creating Custom FoldersThis option is not available in TSE mode. You can access the Custom Folders options under the Directories option to add your own folders to the directory structure. For example, if you want add your own fonts to the installation and want them to install in their own folder, you can add a custom fonts folder.

Note: To add files to a newly created folder, click Files in the option tree, click Add, and then select the file you want to add. When the Add/Modify File dialog box opens, you will find the new folder in the Choose Destination drop-down list. (The folder will be listed under the directory macro name, which is also displayed on the Custom folder pane in the Directory Macro column.) After you add the file, it is listed on the Custom Folders pane in the Component column. For more information on adding files, see "Selecting Files to Install" on page 50.

45


To create a custom folder:

1 In the option tree click Custom Folders under Directories. The Directories: Custom Folders pane appears on the right.

2 Click Add New. The Add Custom Directory dialog box opens.

3 From the Choose Parent Directory Macro list, select the directory macro you want to use to create the new folder. The name of the macro appears in the New Directory Macro box with an new increment number. The Default Destination Path lists the directory in which the new folder will be created. The macro you select from the Choose Parent Directory Macro list determines the location of the new folder.

4 In the New Directory Name box, assign the new custom folder a name. If the custom folder name exceeds 8 characters or contains a space, you must use the following format:

shortname|longname

8.3 file names have a maximum of 8 characters optionally followed by a dot (.) and then a maximum of three characters. For example, you could use myfold~1 for My Folder.

where shortname is an 8.3 MS DOS name for the folder name and longname is the full folder name.

5 If you want the installation to create the folder even if the folder does not contain any files, select the Always Create This Folder check box.

46


6 Click OK to create the custom folder and return to the Directories: Custom Folders pane. The folder appears in the list of custom directories.

Creating SubfoldersIn TSE mode, you cannot add custom folders or subfolders.

Once you have created custom folders, you can then add subfolders.

To add a subfolder:

1 In the option tree, click Custom Folders under Directories. The Directories: Custom Folders pane appears on the right.

2 On the Directories: Custom Folders pane, select the folder where you want to add a subfolder and click Add Sub Folder. The Add Custom Directory dialog box opens with the parent directory macro set by the custom folder you selected.

The name of the macro appears in the New Directory Macro box with an new increment number. The Default Destination Path lists the directory in which the new folder will be created. The macro you select from the Choose Parent Directory Macro list determines the location of the new folder.

3 In the New Directory Name box, type the name you want to assign the new subfolder. If the subfolder name exceeds 8 characters or contains a space, you must use the following format:

shortname|longname


where shortname is an 8.3 MS DOS name for the subfolder name and longname is the full subfolder name.

4 If you want the installation to create the subfolder even if it does not contain any files, select the Always Create This Folder check box.

5 Click OK to create the custom subfolder and return to the Directories: Custom Folders pane. The folder appears in the list of custom directories.

47


Selecting Features to Install

To view the Features options, click Features in the left panel of the Setup Customization Wizard.

The Features options lets you choose which Hummingbird product features to install. Selecting features is similar to customizing your product installation using Windows Installer. Choose features that cater to the intended users in your enterprise. Sconfig also lets you specify sub-features for each feature you specify.

For quick access to these features on user machines, you can create shortcut icons for Hummingbird product features for users and groups. For more information see “Setting Shortcuts for Hummingbird Product Features” on page 60.

Adding a Feature to an Installation Database

Recognizing features commonly used by specific users is necessary to customize installations. Some use the Hummingbird product at an administrative level (system administrators) and will find features that monitor trace operations and troubleshoot logs to be a very important components of their installation. Others that use the product at an end-user level may have no use for those features.

48


To add a feature, in the Features pane, select the check box of the Hummingbird product feature(s) you want to add to the installation.

Modifying a Feature in an Installation DatabaseThe Features box lets you specify which sub-features get installed for any core feature during a Hummingbird product installation. This is especially useful when application requirements for a particular user change. Modifying the included sub-features with Sconfig changes the transform file (.mst). These changes must then be reapplied to the installation file.

To modify a feature:

1 In the Features pane, expand the tree of the Hummingbird product feature(s) you want to modify.

2 Select or clear the check box of the sub-feature(s) you want to add or remove for that Hummingbird feature.

Removing a Feature from the Installation DatabaseWhen users no longer require a feature, you can remove the product feature from the installation database. Removing a feature in Sconfig deletes it from the transform file (.mst). These changes must then be reapplied to the installation file (.msi) to reflect the update.

To remove one or more feature, in the Features pane, clear the check box of the Hummingbird product feature(s) you want to remove.

49


Selecting Files to Install

The File options are not available in TSE mode.

To view the Files options click Files in the left panel of the Setup Customization Wizard.

Sconfig lets you add external program files to the installation. You can specify the destination path of a file on a user’s computer and specify a feature to install with this file. The Files pane provides you with the opportunity to accessorize the installation database and optimize task efficiency amongst users while using the Hummingbird product.

Adding a Custom File to an Installation DatabaseThe Files box lets you add to the installation database external program files that are frequently required by users. You can add mini program files such as e-mail, drawing and graphics files, or other executable files that users need to carry out routine tasks.

50


To add a file:

1 In the Files pane, click Add. A standard Windows Open dialog box appears.

2 Select a file in the dialog box and click OK. The Add/Modify File dialog box opens.

3 From the drop-down list, select a destination path folder. This folder can be a Windows Systems folder, a Hummingbird folder, or a custom folder, depending upon where you want to store the file.

4 If you want to add the file to a subfolder within the destination folder, do the following:

a) Click Add Sub Folder. The Add Custom Directory dialog box opens.

b) In the New Directory Name box, type the name you want to assign the new subfolder and click OK. If the subfolder name exceeds 8 characters or has a space, you must use the following format:

shortname|longname

51



where shortname is an 8.3 MS DOS file name for the subfolder name and longname is the full subfolder name.

5 From the Install With Feature drop-down list, select a feature or select Always to include this file with every installation and click OK. The Files box appears listing the added file.

6 If you want to add another file, repeat steps 1-5.

Modifying a Custom File in an Installation DatabaseYou can modify a file in the installation database. This option provides you with the flexibility to change the associated feature that gets installed with the file and specify a new destination path for the file.

To modify a file:

1 In the Files pane, select a file and click Modify. The Add/Modify File dialog box opens.

2 If you want to change the destination folder in which your file gets stored, from the drop-down list, select a new destination path folder.

3 If you want to change the feature that the file gets installed with, from the Install With Feature drop-down list, select a new feature and click OK. The Files pane appears listing the files in your installation database.

Removing a Custom File from an Installation DatabaseYou can remove a file from the installation database when users no longer require that file with the installation of the Hummingbird product. Removing a file in Sconfig deletes it from the transform file. These changes must then be reapplied to the installation file to reflect the update when the application is installed.

To remove a file, in the Files pane, select a file from the list and click Remove.

52


Setting Product Properties

To view the Properties options, click Proper ties in the left panel of the Setup Customization Wizard.

Sconfig lets you specify the Hummingbird product properties you want installed. The Proper ties pane lists both the properties that are required for product functionality and the optional properties. You can set properties that customize Hummingbird product features, that control user input and that define the installation behavior of the product.

You can also set properties for Exceed. However, these properties become available only when installing the appropriate installation files. For more information on Exceed properties, see “Setting Exceed Properties” on page 66.

Hummingbird product properties can be added to, modified within, and removed from an installation database for different users in an enterprise.

53


Adding a Custom Property to an Installation DatabaseYou can add optional properties that customize Hummingbird product features, such as the COMPANYNAME property which includes the name of your organization in the product installation. You can also include properties that control user input during installation, such as the TransformSecure property, which protects your transform files from user modification. Other optional properties define the installation behavior of the product, such as the ALLOWBROWSE property, which lets the product browse to the home directory during an installation.

Set properties that make the best use of the Hummingbird software features and that facilitate a user’s installation session.

To add a property:

1 In the Properties pane click Add. The Add Proper ty dialog box opens.

2 From the drop-down list, select a property. The bottom panel of the dialog box provides the validation information for the property.

3 In the box, type or select a value for the new property and click OK. The Properties box appears listing any new properties you’ve added to the installation database.

54


Modifying a Custom Property in an Installation DatabaseAfter you add custom properties to the installation database, Sconfig lets you modify these property settings as needed. Modifications to property values become necessary when requirements for features and files added to the installation database change amongst users, or when existing properties need to be updated to reflect the current installation package.

To modify a property:

1 In the Properties pane, select a property.

2 Click Modify. The Modify Proper ty dialog box opens.

The bottom panel of the dialog box provides the validation information for the property.

3 In the box, type a new value for the property and click OK. The Proper ty box appears listing your properties in the installation database.

4 If you want to modify other properties, repeat steps 1-3.

55


Removing a Custom Property from an Installation DatabaseYou can clean the installation database of properties that are no longer in use. Properties can become obsolete when changes amongst users occur. Some scenarios that may require the removal of a property include changes made to:

• feature requirements

• user privileges during an installation session

• user permissions for the software

To remove a property, in the Properties pane, select a property from the list and click Remove.

Setting the Registry

Click the Registry option in the left panel of the Setup Customization Wizard to view the Registry options.

You can use Sconfig to customize the general software settings of your Hummingbird product. After your Hummingbird product installation file installs the custom components and files on the target machine, it can write the custom registry keys and values set in Sconfig to the system registry. You establish the keys and values your installation file writes to the system registry by setting them up in your transform file in Sconfig.

56


Hummingbird or system registry keys can be added to, modified within, and removed from an installation database for different users in an enterprise.

Adding a Custom Registry Key to an Installation DatabaseSconfig lets you make necessary registry key additions to the system registry. Making additions to the installation file reduces administration time as additions are made once for all target machines that will use that customized installation file.

57


To add a registry key:

1 In the Registry pane, click Add. The Add/Modify Registry Entry dialog box opens.

2 In the Root drop-down list, select a hive name.

3 In the Data Type drop-down list, select a data value type.

4 In the Key box, type the registry key name.

5 In the Value Name box, type the registry value name.

6 In the Value Data box, type the registry data value and click OK. The Registry pane appears listing your new keys.

Modifying a Custom Registry Key in an Installation DatabaseMake necessary registry modifications to the system registry from Sconfig. Making modifications from the installation file reduces administration time, as modifications are made once for all target machines that will use that customized installation file.

58


To modify a registry key:

1 In the Registry pane, click Modify. The Add/Modify Registry Entry dialog box opens.

2 If you want to change the existing hive name of the registry key, from the Root drop-down list, select the new hive name.

3 If you want to change the existing value type of the registry key, from the Data Type drop-down list, select the new data value type.

4 If you want to change the existing name of the registry key, in the Key box, type the new name for the registry key.

5 If you want to change the existing registry value name, in the Value name box, type the new registry value name.

6 If you want to change the existing registry data for the key, in the Value data box, type the new registry data and click OK. The Registry box appears listing your registry keys in the installation database.

Removing a Custom Registry Key from an Installation DatabaseTo remove a registry key, in the Registry pane, select a registry key from the list and click Remove.

59


Setting Shortcuts for Hummingbird Product Features

Click the Shortcut option in the left panel of the Setup Customization Wizard to view the Shortcut options.

This option enables quick access to commonly used Hummingbird components. While customizing your transform file in Sconfig, create custom shortcuts for Hummingbird product features for quick access on user machines.

To set a custom shortcut:

You can drag and drop items in the Shortcut tree.

1 In the shortcut tree displayed in the Shortcut pane, right-click the folder to which you want to add a new shortcut. In the menu, click Add Shortcut Here.

2 In the Name text box, type the name of the shortcut that you want add. To rename a shortcut, select the name of the shortcut in the Name box and enter the new name. The name must appear in the format:

short name|long name

60



where the short name is an 8.3 MS DOS name and the long name is the name of the shortcut as it appears on the Windows desktop. For example,

ExceedF|Exceed Finger

3 If you want to include a description for the shortcut, into the Description text box, type a description for the shortcut. This appears when you move your mouse pointer over the shortcut icon.

4 From the Install With drop-down list, select a component for which you want to provide a shortcut. The installer uses the installation state of this component to determine whether to create or delete the shortcut.

5 From the Target drop-down list, select a destination folder of the component for which you want to provide a shortcut.

6 The Default Path text box displays the destination path of the component for which you want to create a shortcut.

7 If you want to provide any arguments for this shortcut, type them into the Arguments text box.

8 In the Icon area, click Select to launch the Change Icon dialog box. In this box, select an icon to associate with the shortcut and click OK.

Note: For advertised shortcuts, the file launched by the shortcut is the file associated with this feature. When you activate this shortcut, Windows Installer verifies that all components in the feature are installed before launching the file. For non-advertised shortcuts, the field should contain a property identifier enclosed by square brackets.

61


Setting Hummingbird Metering Properties

The Sconfig interface provides you with the information you need to manage Metering settings. You can modify property settings or delete unwanted properties.

When you click Metering in the option tree, the Metering pane opens. This pane lists the available Metering properties. It also displays the setting or value currently associated with the property and defines the property so that you can make the necessary changes.

To modify a property setting:

1 In the option tree, click Metering.

2 In the Metering pane, select the property you want to modify. Its current setting (if any) and a description are provided in this pane.

3 Click Modify. The Modify Proper ty dialog box opens and identifies the property you are modifying and its current setting.

Note: Some properties cannot be deleted.

62


4 Specify the new value. Tips are provided at the bottom of the dialog box.

5 Click OK.

To remove a Metering property:

Select the property you want to remove, and click Remove.

Setting Properties for Hummingbird Directory Services

Before you configure Hummingbird Directory Services settings in Sconfig, it is recommended you configure a local installation of Hummingbird Directory Services. You can then import the settings into Sconfig to add them to the installation database. The Sconfig interface provides you with the information you need to then modify or remove the settings for LDAP, NFSD, NIS and NIS+ directory services if necessary.

When you click Directory Services in the option tree, the Directory Services pane opens. This pane lists the available properties. It also displays the setting or value currently associated with the property, if any, and defines the property so that you can make any necessary changes.

You can view and manage the properties for LDAP, NFSD, NIS and NIS+ by expanding the Directory Services option in the option tree and then clicking the service.

Note: The METERINGRETRYINTERVAL and METERINGRETRYCOUNT values must be numbers that are prefixed by the number (#) character.

63


To import Directory Services property settings:

1 Ensure that the local installation of Hummingbird Directory Services is configured as required.

2 In the Sconfig Customize window, expand the Directory Services option in the option tree, and click the item for which you want to import the property settings.

3 Click Import.

Sconfig reads and imports the values from all the registries for Directory Services. Sconfig lists the imported values in the Value column.

To modify Directory Services property settings:

1 In the option tree, expand the Directory Services option and click the item for which you want to view the properties.

2 In the pane that appears, select the property you want to modify. Its current setting (if any) and a description are provided in this pane.

Note: If you have not imported property settings from a local installation of Hummingbird Directory Services, no values will be displayed.

64


3 Click Modify. The Modify Proper ty dialog box opens and identifies the property you are modifying and its current setting if any.

4 Specify the new value. Tips are provided at the bottom of the dialog box.

5 Click OK.

To remove a Directory Services property:

Select the property you want to remove, and click Remove.

Setting NFS Maestro Client Settings

During NFS Maestro product or Exceed PowerSuite installations, the NFS Client Settings option becomes available to you. To view the NFS Client Settings property pane, click the NFS Client Settings option in the left panel of Setup Customization Wizard. This pane lets you modify or remove properties for NFS Maestro Client, such as Maestro.NFSClient.UseDOSStyleSharing, which enables file sharing common to most Windows file operations. Like Exceed, modifying a property for NFS Maestro Client adds it to the property table; while removing a property removes it from the property table in the Proper ties pane of the Setup Customization Wizard.

You can modify or remove the properties listed in the NFS Client pane as you would on the Properties pane. For more information, see:

• “Modifying a Custom Property in an Installation Database” on page 55

• “Removing a Custom Property from an Installation Database” on page 56

65


Setting Exceed Properties

If you are installing Hummingbird Exceed, Exceed XDK, or PowerSuite then the Exceed Settings option becomes available to you. To view the Exceed Settings options, click Exceed Settings in the option tree located in the left pane of the wizard. The Exceed Settings pane opens on the right. This pane lets you modify or remove Exceed properties, such as the Exceed.XServer.Tune property, which executes the Xperf application for optimal graphics performance.

When you modify or remove a property, the property gets added or deleted from the property table in the Proper ties pane. You can modify or remove properties in the Exceed Settings pane the same way you do in the Proper ties pane. For more information, see:

• “Modifying a Custom Property in an Installation Database” on page 55

• “Removing a Custom Property from an Installation Database” on page 56

66


Setting Custom Font Directories and Servers

These options are not available in TSE mode.

You can access the Exceed Settings: Custom Fonts pane by expanding Exceed Settings in the option tree and clicking Custom Fonts. When you execute custom installations for Hummingbird Exceed, Sconfig lets you control the directories and servers added to the font database. The font database is stored in the lfp.xdb file; Xconfig uses this file when locating font directories and servers. The end result of the customization is that users should see a new customized font directory or server in Xconfig.

Hummingbird font directories and servers can be added to, modified within, and removed from an installation database for different users in an enterprise.

Note: Plan your font directories and servers according to the demands of each user.

67


Setting Custom Font DirectoriesThis option is useful when accommodating Exceed users who require custom font files in the Xconfig utility. During a mass installation, you need to provide font directories that are tailored to meet the demands of each user. This means including only those font files (.fon) in each directory that are useful to each user.

With Sconfig, you can provide custom (.fon) files in each directory for

specific users to optimize disk space and to enhance productivity.

Adding a Custom Font Directory and Font FilesAdding font directories with Sconfig creates new font directories in the Xconfig font database. The font database in Xconfig is stored in the lfp.xdb file in the User directory. Specific fonts in the font database are stored in font directories and on font servers.

Before you can add the font directory to a custom installation database with Sconfig, you must do the following in the Exceed Xconfig utility:

• Create a custom font directory

• Add custom font files (.fon) to this directory

For more information, refer to the Exceed User’s Guide.

68


To add a custom font directory:

1 In the Custom Fonts pane, click Add. The Add/Modify Custom Fonts Settings dialog box opens.

2 From the Font Type drop-down list, select Directory.

3 In the Font Directory box, type the name of the custom directory. In the File Name box, click Browse and navigate to the font database file (.fdb). This file is created by Xconfig and stored in

For more information on Per User installations and the Default directory, see the Advanced Installation chapter in your manual.

Program Files\Hummingbird\Connectivity\version\Default User\Exceed\

where version is the version number of your Hummingbird product.

4 Select the status of the font directory. You can select Load, Keep, or Inactive.

5 To make matches to this directory using its physical font name as well as its logical font name, select the Match Physical Font Name box and click OK. The Custom Fonts pane appears listing the new directory added to the installation database.

6 If you want to add another font directory, repeat steps 1-5.

Note: The name of the custom font directory appears in the Custom Fonts pane. You can now add your custom font files (.fon) to the custom font directory you created.

69


7 In the Custom Fonts pane, select the font directory to which you want to add a custom font file(s).

8 In the Custom Fonts pane, click the Add Font Files button. A standard Windows Open dialog box appears.

9 In the box, browse to the custom font files (.fon) located in your custom font directory and stored on your local machine. Select and copy the custom font files (.fon) you need into your custom font directory and click OK. The Custom Fonts pane appears listing new font files added to the directory.

10 If you want to add new font files to the directory, repeat steps 7-9.

A new custom font directory along with (.fon) files is added to the installation database.

Modifying a Custom Font DirectoryModifying a custom font directory lets you change the specifications for the selected font directory in the Xconfig font database. You can change the font type from directory to server, change the name of the font directory, and add a new font database file (.fdb) to this directory.

If you are changing a font directory in the database, you need to know the name of the directory and the name of the font database file corresponding to the new font directory.

To modify a custom font directory:

1 In the Custom Fonts pane, click Modify. The Add/Modify Custom Fonts Settings dialog box opens.

2 From the Font Type drop-down list, select Directory to display directory settings.

3 If you want to rename the directory, in the Font Directory box, type the new directory name.

Warning! When changing the name of a font directory, you must add the font files (.fon) to that directory.

70


4 If you want to change the existing font database file, in the File Name box, click Browse and point to the new file (.fdb). This custom file is created by Xconfig and stored in

Program Files\Hummingbird\Connectivity\version\Default User\Exceed\

where version is the version number of the Hummingbird product.

5 If you want to change the status of the font directory, in the Status area, select the new status of the font directory. You can select Load, Keep, or Inactive.

6 If you want to make matches to this directory using its physical font name as well as its logical font name, select the Match Physical Font Name box and click OK. The Custom Fonts pane appears, listing any directories or servers in the installation database.

7 If you want to modify another font directory, repeat steps 1-6.

Removing a Custom Font DirectoryYou can remove a font directory from the installation database when users no longer require that directory in the Xconfig font database. Removing a font directory in Sconfig deletes it from the transform file. These changes must then be reapplied to the package to reflect the update.

To remove a custom font directory, in the Custom Fonts pane, select a directory from the list and click Remove.

Removing a Custom Font FileYou can remove a font file from the font directory when users no longer require that font file in the Xconfig font database. Removing the font file in Sconfig deletes it from the transform file. These changes must then be reapplied to the installation file to reflect the update.

In the Custom Fonts pane, select the font file(s) you want to remove and click Remove File.

71


Setting Custom Font Servers This functionality is not available in TSE mode.

This option is available for users that use Exceed and require a connection to custom font servers in the font database. During a mass installation, you can connect users to a customized font server tailored for their task requirements.

Adding a Custom Font ServerAdding a font server to the installation database connects users to a customized font database in Xconfig. You need to know the network node specification of the host where the font server is located and the port or object name (DECnet transports). You can also specify additional font catalogues.

To add a custom font server:


2 From the Font Type drop-down list, select a server.

3 In the Host Name box, type the server name.

4 In the Port box, type or select the port number.

5 If you want to specify a catalogue, type the catalogue name in the Catalogue box.

72


6 Select the status of the server directory. You can select Load, Keep, or Inactive.

7 To make matches to this directory using its physical font name as well as its logical font name, select the Match Physical Font Name box and click OK. The Custom Fonts pane appears listing the new font server added to the installation database.

8 If you want to add another font server, repeat steps 1-7.

Modifying a Custom Font ServerIf you are modifying a font server in the database, you need to know the network node specification of the host where the font server is located and the port or object name (DECnet transports). You can also specify additional font catalogues.

To modify a custom font server:


2 From the Font Type drop-down list box, select a new server.

3 If you want to rename the server, in the Host Name box, type the new server name.

4 If you want to connect to a new port, in the Port box, type the new port number.

5 If you want to specify a catalogue, type the catalogue name in the Catalogue box.

6 If you want to change the status of the server, from the Status area, select the new state of the server directory. You can select Load, Keep, or Inactive.

7 If you want to make matches to this directory using its physical font name as well as its logical font name, select the Match Physical Font Name box and click OK. The Custom Fonts pane appears, listing any directories or servers in the installation database.

8 If you want to modify other font servers, repeat steps 1-7.

73


Removing a Custom Font ServerYou can remove a font server from the installation database when users no longer require that server in the font database. Removing a font server in Sconfig deletes it from the transform file. These changes must then be reapplied to the installation file to reflect the update.

To remove a custom font directory, in the Custom Fonts pane, select a server from the list and click Remove and then click OK.

Setting Paths for Font Directories/Servers

To view the Font Path options, expand Exceed Settings in the left panel of the Setup Customization Wizard and click Font Path. This option lets you place font directories/servers in the most efficient search order for Xserver requests.

74


Setting Font PathsThe Font Path pane for Exceed fonts lets you change the order in which font directories/servers are loaded by the Exceed X server. Place font directories/servers containing the most commonly requested fonts at the top of the list to reduce the amount of time it takes to find a match.

To set font paths, in the Exceed Settings: Font Paths pane, select a font directory/server, click Move Up and Move Down to change the display (search) order.

Saving the .mst File

Once you have made your modifications to the Hummingbird product installation options, go through the following steps to save your transform file:

1 In Sconfig Wizard, click Next. The Ready to Commit page opens confirming that you are about to save your configurations to a transform file.

2 Click Next to create the transform file (.mst). This process is automatic and does not display on screen. The Complete page opens, stating that you have created your transform file.

3 If you want to create a Command (.cmd) or Batch (.bat) file that will launch Setup with the new transform file, select the option at the bottom of the wizard and use the browse button to specify the file name and location. If you do not select this option, you can follow the instructions provided by the wizard for adding the transform file to the CmdLine entry of the setup.ini file. For more information, see “Applying the .mst File to an Installation” on page 76.

4 Click Finish to exit Sconfig.

Sconfig saves the transform file in the same folder as the installation file. This makes it easier for users to find when they want to access the file from the administrative installation point.

75


Applying the .mst File to an Installation

After you have created a transform file (.mst), you can use it to customize Hummingbird product installations. If, on the last page of the wizard, you did not opt to generate a command file that launches Setup with the new transform file, you can apply the transform file to the installation file manually. To do this, you must tell the setup.exe where to find your transform file.

To change the setup.exe:

For more information on installing with an .mst file, see the Sconfig online help.

1 In Windows Explorer, browse to the folder that contains the setup.ini file of your Hummingbird product.

2 Open the setup.ini file.

3 On the line beginning with CmdLine, add the following text:

TRANSFORMS=”full path to the .mst file”

For example, the CmdLine for Hummingbird YourProduct would look like this:

CmdLine=TRANSFORMS=”c:\Hummingbird YourProduct.mst”

where YourProduct is the Hummingbird Connectivity product you are customizing.

4 On the File menu, click Save.

5 On the File menu, click Close.

The new CmdLine in the setup.ini file tells the setup program to incorporate the new transform file in the program installation. When you run setup.exe, it uses both the original installation file, and the transform file that you created using Sconfig.

76


Creating Multiple Custom Installations

Multiple custom installations are important for disparate users with different development needs. Users demand software that makes efficient use of both their time and disk space. Rather than having users sift through a large Hummingbird product installation, use the Sconfig utility to package custom installations for each user.

To create another .mst file:

1 Open Sconfig and browse to a new transform file (.mst).

2 Create and save the transform file (.mst) to the administration installation point.

3 If you want to create more transform files for custom installations, repeat steps 1-2.

4 To use your new transform file (.mst), launch the Setup Wizard by using the following command:

setup /v”TRANSFORMS=c:\YourTransform.mst"

This way, multiple transform files can exist in one source location, without repeated modifications to the setup.ini file.

Running Sconfig from a Command Line

You can use a command-line prompt to generate transform files and to apply them to an installation file (.msi).

Generating a TransformUse the following command to generate a transform file:

-g basedb newdb transform [error/validation conditions]

where:

• basedb is the installation file you want to use to create the transform file

77


• newdb is the name of the new installation file that contains changes that you want to add to the transform

• tranform is the file name of the transform file you want to create.

• error is the code for any errors you want to suppress

• validation conditions is the code for any conditions under which a transform can be applied to a package

Applying a Transform FileUse the following command to apply a transform file to an installation file (.msi):

-a transform database [error conditions]

where:

• transform is the transform file you want to apply

• database is the installation file to which you want to apply the transform

• error conditions is the code for any errors you want to suppress

Error Conditions

The following table lists the error that you can suppress when applying a transform:

Code Definition

a Add existing row.

b Delete non-existing row.

c Add existing table.

d Delete non-existing table.

e Modify existing row.

f Change codepage.

78


Validation Conditions

The following table lists the validation conditions you can apply to the transform file:

Code Definition

g Check upgrade code.

l Check language.

p Check platform.

r Check product.

s Check major version only.

t Check major and minor versions only.

u Check major, minor, and update versions.

v Applied database version < base database version.

w Applied database version <= base database version.

x Applied database version = base database version.

y Applied database version >= base database version.

z Applied database version > base database version.

79


Controlling Per-user Settings

During the installation of Hummingbird Connectivity products, default profiles and settings are installed in a common location for all users. This location, including all files and folders, acts as a template collectively known as the default user directory. When a user launches a component for the first time, this template is copied to a user-specific (per-user) location or personal user directory. The product CD is not required.

The following are the default (root) directories:

Administrators can refresh default files, profiles, and settings in the default user directory. Administrators control the global defaults contained in the default user directory; users control the contents of their personal user directory. Each application determines what personal data and what global data exists, but only reads user-specific settings from the personal user directory or from the current user's Windows Registry.

Customizing Files and FoldersAny user who has write access can modify the default user directory; typically, only Administrators have write access. Both files and registry entries can be added and removed. Such changes are reflected respectively in the personal user directory and the current user's Windows Registry.

Directory Location (Root)

Personal (Per-User)

AppDataFolder\Hummingbird\Connectivity\version\

Default Program Files\Hummingbird\Connectivity\version\Default User

Note: Administrators and users should change files and folders only below the root level.

80


Administrators can add files or folders below the level of existing root sub-folders. These files or folders are automatically copied to the personal user directory. New root level sub-folders are handled by PerUser Settings.ini located at the root of the Default User directory. This file determines whether or not an installation is required. Hummingbird Connectivity User Settings are automatically created when a user of the machine first launches a Hummingbird Connectivity application.

Administrators can change the location of the personal user directory where the template files and folders are installed. Default locations are based on registry values. An administrator can change these values (even remotely) after the initial install. Sconfig has the ability to modify the initial values through its Directory dialog box.

Adding Registry EntriesEach root-level folder in the default user directory has an associated registry file. These are stored in the Registry folder. The [Registry Files] section in PerUser Settings.ini provides a method of associating a .humreg file (which is actually .reg file format) with an internal folder name. This is only for installing registry keys and values to the HKEY_CURRENT_USER registry hive.

Entries in [Registry Files] use the following syntax:

FolderName=Short_humreg|Long_humreg

where Long_humreg represents the path of the file (for example, Registry\Accessories.humreg) relative to the default user directory root. Short_humreg is the proper MS DOS 8.3 path name. If the Long_humreg file is described as a MS DOS 8.3 path, then Short_humreg and the pipe (|) character can be omitted. Multiple .humreg files can be specified for a single folder by separating the paths with semi-colons.

Note: Sconfig is not applicable to Exceed 3D and Exceed XDK add-ons.

81


Updating the Personal User Directory for All UsersWhen the default user directory is updated, any newly created personal user directories automatically get the latest files. For users that already have a personal user directory, Administrators can use one of the following methods to update the user files.

Automatic UpdateTo update the personal user directory for each user automatically (the next time they use a Hummingbird Connectivity application), update the [Last Modified] section of PerUser Settings.ini.

Do this by running the following command:

HumSettings.exe UPDATELASTMODIFIED=FolderName

Available folder names are ExceedMP, HostExMP, ProfileMP, FtpMP, CommonMP, SecurityMP, HumNeighborhoodMP, DeploymentMP, and NFSClientMP.

where FolderName is the internal name for one of the top level, default user directory. Specify multiple directory names by separating the names with semi-colons. HumSettings.exe is located in Program Files\Hummingbird\Connectivity\version\Accessories.

Manual UpdateTo manually update the personal user folder for a specific user, at the command prompt type:

HumSettings.exe REFRESH=ALL USER=”user_profile_path”

where REFRESH=ALL re-installs, repairs, or refreshes all installed product folders. USER=”user_profile_path” specifies the profile path for the personal user directory.

Note: The time stamp is stored in binary format. If you change the time stamp values manually, you risk having the per-user installation run multiple times.

82


For example:

HumSettings.exe REFRESH=ALL USER="C:\Documents and Settings\user"

Passing Arguments to Per-user SettingsWhen using HumSettings.exe to invoke the per-user installation process, you can pass parameters that affect the current installation. However, in the case of a per-user installation triggered by an application, there is not a command line to pass arguments to the process.

Instead, there is a section in the PerUser Settings.ini file called [PerUser Installation Parameters] which accepts arbitrary Property names and values:

[PerUser Installation Parameters]

REINSTALLMODE = ud

"Property" = "Value"

Each key and value pair is treated as an argument to the current per-user installation.

User Settings Migration

Controlling Migration in Per-user InstallationsMigration of user settings can take place at any time after the initial installation. The per-user installation uses the settings found in PerUser Migration.ini to determine what, if any, migration sources to use. A migration source can consist of either existing registry values leftover from

Note: Do not include a backslash character (\) at the end of the USER command. Otherwise, the command line may be misinterpreted and lead to unexpected results.

Note: There are limitations on parameter usage. For instance, the INSTALL and USER parameters have no affect because the installation is being triggered for only the current user.

83


previous Connectivity products for the user, or a specified Hummingbird Settings Transfer file (.humfst). The per-user installation process searches one or both sources based on the value of the Migration Method key in the [Migration Control Options] section.

A sample section is as follows:

[Migration Control Options]

Migration Method= HUMFST, Registry Search

Migration First Time Only=2

HUMFST Path=C:\Program files\Hummingbird\Connectivity\10.00\Default User\MigBackupEx.humfst

The Migration Method accepts a comma separated list of migration sources. The current valid list of source names includes Automatic, HUMFST, Registry Search, and No Migration. If only one source name is listed, there is no need for a trailing comma. Sources are processed from left to right until a valid migration source is found. In the sample above, the list of sources starts with HUMFST and ends with Registry Search. If Migration Method is not defined, the default source is Automatic.

When Migration Method includes:

• Automatic—The source list first uses Registry Search, and then looks for a HUMFST. No further sources in the list are processed.

• No Migration—Migration is disabled during the per-user installation on this machine. No further sources in the list are processed.

• HUMFST—The value of the HUMFST Path key is assumed to be a .humfst file. The path can include Windows Installer style path expansion, for example, [%envariable].

• Registry Search—You can control which older Connectivity versions the migration looks for. This is done by changing the values found in the [Allow Migrate Current User] section from 1 to 0. By default, all versions are searched for.

The final value that affects migration detection is the Migration First Time Only key. This can have a value of 0, 1, or 2. If the value is set to:

• 0—the per-user installation ignores any existing migration cache and attempts to migrate each time it is activated

84


• 1—the per-user installation stops migration if any migration cache exists

• 2—the per-user installation, before stopping, further examines the migration cache to determine if any new folders require migration

Whenever a Connectivity 10 product upgrades another Connectivity product, a choice of whether or not to preserve previous settings is presented by the Hummingbird Setup Wizard (Product Migration dialog box). At the end of the installation process, if settings were preserved, the .humfst file generated during the process is put in the Default User template folder, and the HUMFST Path is updated to reflect this value.

In addition, [Directory Mappings.x.yz] sections are populated with old Home directory values from the previous versions. These values are necessary for the Registry Search migration method to complete successfully. In the case where a Registry Search migration method was attempted, and could not continue because of missing values, a list of the values required is placed in the HumSettings.log file generated by the per-user installation.

Distributing Customized files and SettingsAlthough the primary purpose of migration support in the per-user installation is to ensure that older product settings are preserved, the HUMFST migration method can also be used to distribute settings from one machine to another. The Administrator's Toolkit feature (Administrative Tools program group within the Hummingbird Connectivity program group) includes the Files and Settings Transfer Wizard. This wizard can produce .humfst files to use as the HUMFST Path value in the PerUser Migration.ini. Since per-user migration takes place after the Default User template files are already installed, any settings found in this new .humfst override those in the Default User template.

Disabling Migration for Per-user InstallationsIf the machine has an available migration source, you can disable the migration process for individual users by modifying PerUser Migration.ini. This file is used by Hummingbird Connectivity User Settings to determine whether or not the settings contained in the migration folder of the default user directory should be migrated to each user.

85


Change the [Active Migration Sources] section in PerUser Migration.ini so that all migration sources have a value of 0. This section determines whether or not a particular version should be considered for migration purposes.

Controlling UninstallationWhen a Connectivity product is uninstalled, Hummingbird Connectivity User Settings removes the personal user directory from the current user profile. In addition, the default behavior of the uninstall is to remove all key registry entries (including Hummingbird Neighborhood registration) from all local user profiles on the machine for which Hummingbird Connectivity User Settings were created.

Set the PREVENTALLUSERPROFILEUNINSTALL property to 1 in Sconfig, or manually on the command line of an uninstall operation. If the property is set to 1, the uninstall process removes only the personal user directory from the current user profile.

For complete control, set the property PERUSERUNINSTALLTYPE in Sconfig, or manually on the command line of an uninstall operation. It can be set to a string representing the exact command line parameters passed to HumSettings.exe.

86

Chapter 4

Connecting to Hosts andRunning X Clients

Connecting to Hosts 89Using the X Client Startup Wizard 89Running Multiple Exceed Sessions 91Creating a Startup File 92Browsing for Hosts and Applications 95Load Optimization 98Host and Application Files 101Creating an Xstart Shortcut 102Running the Xstart File 103About Password Aging 105Launching Windows Applications 105

Using Xstart on VMS Systems 106TCP/IP Transports 106DECnet Transports 107

Common Desktop Environment (CDE) 108Using Desktop Environments for Linux 108

Window Modes 109

Using Window Managers 110Starting HWM or MWM 111Starting Remote X Window Managers 111

Copying and Pasting 112Using a Temporary Storage Buffer 112Copying and Pasting Data 113Copying and Pasting Graphics 114Copying and Pasting Between X Clients 116Automatic Copy and Paste 117

Chapter 4: Connecting to Hosts and Running X Clients

Connecting to Hosts

You can connect to a host using a wizard or by creating startup files with Xstart or Wstart.

Using the X Client Startup WizardX Client Wizard guides you through the steps necessary for connecting to a host application from your PC.

To create a connection using the X Client Startup Wizard:

1 In the Exceed folder, double-click X Client Wizard.

2 On the welcome page, click Next.

3 On the host page, type the host name or IP address in the Host box, or select from the drop-down list.

4 Select a Host Type from the drop-down list.

5 Optionally, to connect to the most available host, select Load Optimization. Click Next.

6 On the host connection page, select a method from the drop-down list. If available, and if Telnet is the selected method, optionally select Kerberos Support as the authentication method. Click Next.

Note: If you have configured the NIS or FTP file method on your machine, you can click Browse to find the host you want.

Note: You can edit the Host Type default settings by editing the stdappdb file, located in the directory where Exceed is installed.

89


7 On the application page, select an X application from the drop-down list. After you have selected an application, the dialog box immediately displays the command and default parameters for the application. You can modify the parameters, but not the command.

Optionally, to specify multiple display and screen settings, click Advanced. Click Next.

8 On the login page, enter the login information to display each time this connection is made. You can leave the Password box blank, but not the User ID box.

Optionally, you can test the connection. To do this, select Display Host Replies and click Run. When you are satisfied with the connection, clear Display Host Replies and click Next.

9 In the shortcut page, you can create a shortcut to the application. To do this, complete the following information:

• Type a shortcut description and select the option immediately below this box.

• Select a shortcut location from the drop-down list (showing program groups on the Windows Start menu) or type a new group name. To create a menu item on the Exceed X Server Tools menu, select the check box immediately below this box.

Click Next.

10 This page confirms creation of the startup profile. Do one of the following:

• Optionally, select Yes to open the Xweb Wizard which lets you publish the profile to a web server. Follow the wizard instructions.

• Accept the default No option by clicking Next.

11 If you decided to not publish the profile, you can create another one by selecting Yes and return to the host page (see step 3). If you select No and click Finish, the wizard creates the specified connection file and shortcut.

90


Running Multiple Exceed SessionsYou can run multiple instances of the Exceed X server. If you double-click the Exceed icon in the Exceed folder while another instance of Exceed is running, the Exceed Multiple Sessions dialog box opens. It prompts you to decide whether to run multiple sessions or to run just one session.

For more information about the Xconfig Common Settings page, see “Common Settings” on page 173.

If you select Do Not Prompt for Multiple Sessions, this dialog box will not open when subsequent multiple Exceed sessions are run. To re-enable the appearance of this dialog box, clear the Do Not Prompt for Multiple Sessions check box on the Xconfig Common Settings page (Display and Video category).

To run another instance of Exceed, select Run Multiple Sessions. If it is not selected, when you click OK, the dialog box closes without opening another Exceed session.

Note: If the option Do Not Prompt for Multiple Sessions is selected on the Xconfig Common Settings page (Display and Video category), or if the option was selected in a previous Multiple Sessions dialog box, then this dialog box does not open.

91


Creating a Startup FileXstart lets you create (.xs) startup files and shortcuts for accessing UNIX, Linux, and VMS systems. You can also create script files for web-based applications that require a user name and password.

To create a startup file:

1 Double-click Xstar t in the Exceed program group.

2 Create and save a startup file by specifying information in the Xstar t window. By default, startup files are saved in the Exceed directory for the currently logged in user.

For example, in Windows 2000/XP/Server 2003:

C:\Documents and Settings\%USERNAME%\Application Data\Hummingbird\Connectivity\version\)

You can specify another location.

3 Create a shortcut.

4 Run the connection.

The following sub-sections provide more details about the Xstar t window.

92


Startup MethodSelect a method from the Method drop-down list. The start method that you use depends upon the transport that you are using and the host to which you want to connect.

• Secure Shell—Encrypts remote X windows communications. This option is available only if you have Hummingbird Connectivity Security Pack installed.

• REXEC—Requires a password to connect to the host. You can use REXEC to run local X clients on other PCs on your network if they are running the Xstartd service.

RSH is an abbreviation for remote shell.

• RSH —The same as REXEC except that no password is required. Before using RSH, your PC must be authorized for RSH access on your host.

RLOGIN is an abbreviation for remote login.

• RLOGIN—Requires a password.

• TELNET—Requires a password. This start method includes Kerberos V5 authentication and encryption for added security.

• PCX$SERVER (DECnet)—Requires a password.

hRPS is the Hummingbird remote application starter.

• hRPS—Requires that a client be included with Hummingbird Extend to establish the connection. To use this method, the client must be installed and running on the host. No password is required. hRPS is the only start method supported by all transports.

• Local Application—Lets you start Windows applications (such as Hummingbird FTP, Exceed, MWM, or HWM) on hosts.

The following table summarizes the startup methods supported by each type of transport:

Startup Methods DECnet IPX/SPX TCP/IP

REXEC X X

RSH X

RLOGIN X

93


If you are on a VMS system, see “Using Xstart on VMS Systems” on page 106.

ConnectionFor more information, see “Using Login Macros” on page 121 and “User ID and Password Macros” on page 121.

You must specify the information required to connect to a host, log on, and execute a command to start an application. Options that do not apply to the selected start method are dimmed.

To see a list of hosts on the network and the X applications available for each one, click Browse.

Host The host to which you want to connect. By default, the most recent host to which you connected appears at the top of the list in the Host drop-down list.

User ID The user ID on the host to which you want to connect.

Password The password on the host to which you want to connect. If you are unsure whether you typed your password correctly, delete the entire password and type it again.

Command The command that is sent to the host. The command that you type depends upon the program type (X Window or Windows application), your host system, and how it is set up. Type the host system command that you require.

For more information, see “Using Login Macros” on page 121 and “Command Macros” on page 121.

You can type the @d, @a, @:, and @# command macros as shortcuts in the Command box. The @d macro selects the proper IP address if the machine has more than one address.

PCX$SERVER X

dterm X

hRPS X X X

Secure Shell X

Startup Methods DECnet IPX/SPX TCP/IP

94


The following table lists typical commands you can type to start the xterm client on a UNIX host with either a DECnet, IPX/SPX, or TCP/IP transport.

The command definitions are as follows:

• path is the location of xterm on the host

• mypcname corresponds to your network node or address

• displaynumber is the display number you entered in the Xconfig Communication Settings dialog box. The display number is usually zero (0)

Browsing for Hosts and Applications

For more information about advanced features, see “Advanced Xstart Features” on page 121.

To browse for hosts and applications in Xstart, you must configure features accessible from the Browse Methods area of Xstar t Settings (click Settings in Xstart and then click the Other tab). Click the appropriate Configure button to display dialog boxes where you can specify methods and options.

MethodsThe following file retrieval methods are common to Browse Hosts and Browse Applications dialog boxes:

For more information about hostsdb.txt, see “Host Address File” on page 101. For more information about appdb.txt, see “Application Database File” on page 102.

• File—Uses the hostsdb.txt file as a source for the host browse and appdb.txt as a source for the application browse. You can create and maintain these files. The hostsdb.txt file lists IP addresses and their

Transport Command

DECnet

[path/]xterm -display mypcname:displaynumber &IPX/SPX

TCP/IP

95


associated hosts. The appdb.txt file lists hosts or aliases and application locations or names.

• FTP—Uses a file on an FTP server as a source for the host and application browse. You can only access a file this way, not edit it. The source file contains the file structure listed above. To properly configure the Browse Hosts or Browse Apps tabs using FTP, you must supply a server name, user name, password, account (if applicable) and path in the fields provided. In the File box, enter the name and location of the source file on the FTP server.

NIS, NIS+, and LDAP file retrieval methods are available only after configuring them in Directory Services Explorer.

• NIS—Uses NIS (Network Information Service) map hosts.byaddr as a source for the host browse and appdb as a source for the application browse. Before browsing, you must configure Hummingbird Directory Services. The system administrator on the UNIX side must create these maps.

• NIS+ —Uses NIS+ map hosts as a source for the host browse and appdb as a source for the application browse. Before browsing, you must configure Hummingbird Directory Services. The system administrator on the UNIX side must create these maps.

• LDAP—Uses the Lightweight Directory Access Protocol (LDAP). Like NIS+, LDAP secures its objects by requiring client authentication. Before browsing, you must configure Hummingbird Directory Services.

Note: The stdappdb.txt file, which contains applications and their typical locations on various servers, is located in the Exceed User directory. See “Installation Directories” on page 14. An application may be listed here and consequently appear when you browse for applications, but there is no automatic confirmation that the application itself is in the specified directory.

96


OptionsThe Browse Hosts, Options page contains the following options:

Browse Type options specify which host types are shown in a host browse. You can show hosts from a host browse, an application browse, or both of these. The default is to show only hosts from a host browse.

To refresh the Host browse, click Refresh in the Browse for Hosts dialog box which opens when you click Browse beside the Host box in Xstart or in the X Client Startup Wizard.

Remember Browse Information controls whether Exceed remembers (caches) browse information. If not remembered, each browse reloads the selected applications file. If remembered, you can use the cached or locally saved list of applications and only refresh the browse from the source Once a Day (the default) or Only on Manual Refresh. Even if you select Once a Day, you can still use Refresh to update the information.

Default restores Browse Hosts and Browse Applications default selections.

Note: To force a refresh (regardless of these settings), hold down the Shift key before launching Xstart or an Xstart startup file.

97


The Browse Applications, Options page contains the following options:

Browse Sor t Order options affect how applications (regardless of source) are listed. You can sort the list by application and its hosts (the default), or by host and its applications.

To refresh the applications browse, click Refresh in the Browse for Applications dialog box which opens when you click Browse beside the Xstart Command box or beside the Application box in X Client Startup Wizard.

Remember Browse Information indicates whether Exceed remembers (caches) browse information. If not remembered, each browse reloads the selected applications file. If remembered, you can use the cached or locally saved list of applications and only refresh the browse from the source Once a Day (the default) or Only on Manual Refresh. Even if you select Once a Day, you can still use Refresh to update the information.

Use Application Star tup Macro and Expand When Running Command determines whether the selected browse item is inserted in the Xstart Command box as an application macro, or as the full path and application name. If inserted as a macro, it expands when the startup session is run. What you specify in Append to Browse Dialog Selection is appended to the end of whatever you select from the browse dialog box.

Load Optimization This feature makes Xstart connections more efficient. Where the original host is already accommodating many connections, the connection may be diverted to another host. The methods and options pages are described as follows.

98


MethodsTo configure Xstart for load optimization, select a Method:

For more information about rupdb.txt, see “Host List File” on page 101.

• File—Xstart scans the rupdb.txt file for available hosts and tries to run the application on the least busy host. You can create and maintain this file, and save it in the User directory. This method is the easiest to run and is convenient if the desired application resides on every host in rupdb.txt (such as xterm). If the application runs on certain hosts only (not necessarily the least busy ones), then this method could fail.

For more information about appdb.txt, see “Application Database File” on page 102.

Alternatively, you can use rupdb.txt in conjunction with appdb.txt (provided you have previously created appdb.txt). In this case, select Use Apps File in the Options sub-tab. By comparing the two files, Xstart figures out what subset of hosts in rupdb.txt have the desired application and selects from those alone.

• FTP—Uses a file on an FTP server as the source available hosts. You can only access a file this way, not edit it. To properly configure Load Optimization by FTP, enter the server name, user name, password, and account (if applicable) in the fields provided. In the File field, enter the name and location of the source file on the FTP server.

NIS and NIS+ file retrieval methods are available only after configuring them in Directory Services Explorer.

• NIS—Uses an NIS (Network Information Service) map rupdb as a source for available hosts. Before browsing, you must configure Hummingbird Directory Services. The system administrator on the UNIX side has to create the map.

• NIS+ —Uses an NIS+ map rupdb as the source for available hosts. Before browsing, you must configure Hummingbird Directory Services. The system administrator on the UNIX side has to create the map.

• LDAP—Uses the Lightweight Directory Access Protocol (LDAP). Like NIS+, LDAP secures its objects by requiring client authentication. Before browsing, you must configure Hummingbird Directory Services.

• Broadcast—Sends out a broadcast on the network. This option is limited to queries within your subnet, unless you type an address for another subnet. If you selected Use Apps File in the Options sub-tab, then Xstart broadcasts the rup RPC to the subset of hosts in appdb.txt that run the desired application. If Use Apps File is not selected, then Xstart broadcasts to all hosts on the subnet. Using this method, you do not need a rupdb.txt file.

• Browse Applications—Uses an application database file (appdb.txt) to get a list of hosts to check.

99


OptionsThe following load optimization options are available:

Use Applications File specifies that Xstart uses rupdb.txt in conjunction with appdb.txt. In the Section Name(s) box, type one or more section names (separated by commas). These are defined in rupdb.txt. Each section name field can include just one section name or several section names (separated by commas).

In the Timeout box, set a timeout value from 0 up to 9999 milliseconds. If Broadcast was selected on the Method page, this time is the total time that Xstart waits for answers from remote hosts. If other methods were selected, this time is the maximum time to wait for an answer from each host.

Remember Browse Information determines whether Exceed remembers (caches) browse information. If not remembered, each browse reloads the selected applications file. If remembered, you can use the cached or locally saved list of applications and only refresh the browse from the source Once a Day (the default) or Only on Manual Refresh (when you click Refresh). Even if you select Once a Day, you can still use Refresh to update the information.

100


Host and Application Files

Host Address FileThe hostsdb.txt file lists IP addresses and corresponding host names. For example:

123.45.67.89 boethius

This information affects which hosts Xstart browses.

Host List File The rupdb.txt file lists hosts that are running an rpcd daemon that supports the rstatd service. This service is capable of running the rup command, which returns status information about the host, including the service load on the host. The rup command is a Remote Procedure Call (RPC) and the rpcd daemon handles all incoming RPCs.

Xstart consults rupdb.txt when running Load Optimization by sending a rup RPC to each host in rupdb.txt to find the least busy one. You can use section names in rupdb.txt to associate applications with host names. The following syntax rules apply:

• Lines beginning with # are comments and are ignored by the system.

• Section names are enclosed in square brackets [ ].

• If you do not specify a name in the Section name(s) box, the system inserts the name [Default Section].

• If you do not provide a name in the Section name(s) box on the Options sub-tab (Load Optimization tab), then the system inserts the name [Default Section] in the rupdb.txt file.

• You can use any combination of alphabetic characters, spaces, capitalization, and numbers in section names. If you want to list more than one application in section names, then separate them with commas.

• When you add the hosts, type only one host on each line. Host names may be in short or full form, for example, irix or irix.domain.com.

101


For example:

[xclock]onefishtwofish

[xterm]redfishbluefish

In this example, the hosts onefish and twofish support the xclock application; the hosts called redfish and bluefish support the xterm application. When you specify an application in the section, Xstart queries only those hosts following each section. This prevents Xstart from contacting a host that does not run the desired application.

Application Database File The appdb.txt file lists host names, application nicknames, and full path names for applications on remote hosts. Xstart uses appdb.txt to determine which hosts run a particular application. For example:

solaris/mailtool: /usr/bin/mailtool

solaris is the host, mailtool is the application, and /usr/bin/mailtool is the application path.

Creating an Xstart ShortcutAfter you have saved Xstart settings as an Xstart (.xs) file, you can install a shortcut that you can double-click to run the file. Xstart names the shortcut:

• using the entry from the Description box on the Other page of Xstar t Settings

• using the file name (without the extension) if the Description box is empty

Note: appdb.txt lists hosts that must be running rstatd. Therefore, the list of hosts in appdb.txt is a subset of the hosts listed in rupdb.txt, which is itself a subset of the hosts in hostdb.txt.

102


To create an Xstart shortcut:

1 Open the .xs file in Xstart or save the current startup profile.

2 On the Xstart File menu, click Create Shor tcut. The Browse for Folder dialog box opens.

3 Select a location to install the Xstart shortcut. If you do not specify a location and click OK in Browse for Folder, the shortcut is installed on the Windows program menu.

4 To change the default Xstart icon, use the Windows Properties dialog box (right-click the shortcut, click Proper ties, and then click Change Icon). To change the caption or description, right-click the shortcut and click Rename. For more information, consult your Windows documentation.

Running the Xstart FileWhen you run an Xstart file, the following events take place:

1 The Xstar t Information dialog box opens after clicking Run if one or more options in the Local Prompts area of Xstar t Settings—Startup are set to Ask User. In this case, specify your login/account information.

Exceed starts and retries the connection for the length of time specified in the Timeouts area on the Xstar t Settings—Network page.

2 After you have connected, the command specified in the Xstart Command box is sent to the host specified in the Host box. If the command starts a client, the client session begins. The initial socket closes after the length of time specified in the Close box (Timeouts area, Xstar t Settings—Network page).

3 If the Show Host Reply option on the Xstart Settings—Network page is selected, host or client messages are displayed in a window. You can copy text from this window to Clipboard.

103


Running the File from a Command Line You can also open Xstart from a command line in the Windows Explorer Run dialog box. The command-line syntax is:

home\xstart [settings.xs][-m method][-a type] [-h host] [-u userid][-p password][-c command] [-l|-l-][-t timeout]

The following table describes Xstart parameters:

Note: Any parameters you specify after the settings.xs parameter overrides the settings in the .xs file.

Parameter Description

home This is the directory where Exceed is installed.

settings.xs This is the name of the Xstart startup file you want to run. You do not have to type the .xs extension.

If the file name is preceded by a path, Xstart looks for the file in that directory. If no path is provided, the location of the Exceed user directory is assumed.

-m method This is the startup method, specified as one of the following: rexec, rsh, rlogin, pcx (for PCX$SERVER on DECnet), dterm (DECnet) or hrps.

-a type This specifies the program type and can be one of the following: xwin (for an X Window client) or term (for an application that does not require X and can be run using a VT terminal emulator).

-h host This is the host to which you want to connect. You can type either the host name or its network address.

-u userid This is the login name you use to log on to the host.

-p password This is your password on the host.

-c command This is the command that you want to execute on the host. If your command contains spaces, it must be enclosed in double quotes (“command”).

104


About Password AgingFor more information about password aging and specifing password expiry prompts, see Exceed Help.

Password aging is a common tool used to ensure a modest level of security. Changing the password periodically reduces the potential damage caused by intruders who gain access to the network by using stolen user credentials. However, frequent password change also inconveniences end-users and reduces productivity because, in some cases, the passwords are stored in many application profiles. Users must manually replace the aged password with the new password.

For more information, see “Password Expiry Prompts” on page 124.

Exceed can handle password aging events and automatically propagate the changes to other Xstart profiles. Users do not have to manually update Xstart profiles with the new password. Xstart detects UNIX password expiry prompts that require the user to change password. This applies to Rlogin, Telnet, and Secure Shell start methods.

Launching Windows ApplicationsTo launch Windows applications on hosts, select Local Application as the Star tup Method in Xstart and use the Command box to specify the application and related options. See the Exceed Help for an example that uses command line switches.

-l This option (minus sign, lowercase L) tells Xstart to prompt the user for login information. This option displays the Xstart Login Information dialog box at connect time and prompts the user to type a hostname, user ID, password, and a command.

-l- This option (minus sign, lowercase L, minus sign) tells Xstart not to prompt the user for login information.

-t timeout This is the time in seconds that the remote execution facility socket remains open after the host acknowledges receipt of the command.


105


Using Xstart on VMS Systems

You can use Xstart on VMS systems by selecting the correct start method for your transport software and entering all of the required information in the Xstart window.

TCP/IP TransportsYou can use Xstart on a VMS system running TCP/IP if your VMS system supports REXEC or RSH. You must create a script on the host containing the DISPLAY environment variable specification and the command to start the X client. You can then use REXEC or RSH to connect to the host and execute the script.

If your VMS system supports REXEC or RSH, and it is running Version 4.0 of the PCX$SERVER command processor, start an application by choosing the REXEC or RSH start method and type the following in the command box:

@sys$system:pcx$server 4,display-number, screen-number,tcpip,node-address, command <CR>

For example:

@sys$system:pcx$server 4,0,0,tcpip,2.10 DECW$TERMINAL <CR>

Otherwise, use Telnet to connect and start remote applications.

106


DECnet TransportsTo use Xstart on a VMS system running DECnet, choose the PCX$SERVER (DECnet) startup method. Depending upon which version of the PCX$SERVER command processor you are using, type one of the following in the Command box:

• By typing a command, you can select Version 2 of the PCX$SERVER command processor. For example,

DECW$TERMINAL

• You can specify that you want to use Version 3 of the PCX$SERVER command processor by typing the following command:

3,transport,node-address,command

For example, to send the command DECW$TERMINAL to your node address 2.10 on DECnet, type the following:

3,DECNET,2.10,DECW$TERMINAL

• You can specify that you want to use Version 4 of the PCX$SERVER command processor by typing a command as follows:

4,display-number,screen-number,transport,node-address,command <CR>

For example, to specify display number 0 and screen number 0, and send the command DECW$TERMINAL to your node address 2.10 via DECnet, you would type the following:

4,0,0,DECNET,2.10,DECW$TERMINAL

• You can also use command field macros when specifying this information. For example:

4,@#,0,DECNET,@a,DECW$TERMINAL

107


Common Desktop Environment (CDE)

A handshake is an activity that keeps two computers or programs synchronized (such as the CDE display manager and the X protocol). It usually involves the exchange of messages or packets of data between two systems.

When you log into the UNIX host via the CDE display manager using XDMCP, a handshake implemented by the X protocol is employed. CDE does not begin unless it detects a supported PC X server (that is, Exceed).

To start CDE:

1 Ensure CDE is configured properly on a UNIX host.

2 Select a window mode on the Xconfig Screen page (Classic View, Screen Definition).

3 Select XDMCP Broadcast from the Mode drop-down list on the Xconfig Communication page. Validate and apply changes in Xconfig.

4 Start Exceed.

5 From the XDMCP Display Manager Chooser, select a UNIX host. Click OK. The greeter opens.

6 Log into the UNIX host.

7 The CDE session manager starts and the interface displays on your PC.

Using Desktop Environments for LinuxThere are two types of X Graphical Desktop Environments in Linux. Depending on which one you chose when you installed Linux, either KDE or GNOME was set as the default desktop.

• GNOME—GNU Network Object Model Environment works with window managers such as Enlightenment, Sawmill, and Window Maker.

• KDE—K Desktop Environment uses KWM as its window manager.

KDE and GNOME run on a Linux host and are displayed on the remote PC using standard X protocol.

Note: If you select multiple window mode and you are using the Windows (Native) window manager, verify that the Cascade Windows option is not selected.

108


Window Modes

To access the Screen page, open Xconfig—in Classic View, click the Screen Definition icon/text in the right pane—in Category View, click the Display and Video icon/text.

A window mode determines the appearance of the X client windows on your PC. The window mode in which you operate depends upon your own preference. By default, the Exceed X server operates in multiple window mode and the window manager is configured to default to native.

To configure the PC screen to reflect the window mode, see “Configuring X Screens” on page 167.

Use Xconfig to select a window mode for the Exceed X server—Single or Multiple:

• Single window mode—Presents all clients in a single Exceed window. You can use any X window manager (local or remote) as your window manager.

For more inoformation, see “Configuring Window Mode” on page 168.

• Multiple window mode—Each client you start creates its own new window on your display. You can use either the Native (Microsoft Windows) or any X window manager (local or remote) as your window manager.

Note: If you minimize the Exceed X server to an icon in this mode, active client windows are no longer visible.

109


Using Window Managers

A window manager interprets requests or commands entered on the PC and sends them to the Exceed X server. The X server sends the request to the X application, and the application sends instructions to the Exceed X server to display.

If you run an X window session without a window manager, you cannot perform window operations such as resizing, moving, and iconizing. Overlapping windows can make hidden parts of underlying windows inaccessible.

Exceed uses two types of window managers: local and remote. Local window managers run on your PC, while remote window managers run on a remote host. Running Exceed with a remote X window manager generally increases network traffic and may decrease overall system performance.

On the Xconfig Screen page, select a window manager type:

• Native—Restricts you to using local managers. Local managers are located on the Exceed X server.

• X—Restricts you to using remote managers.

• Default—Instructs the system to use a remote manager if available, but otherwise use a local manager.

You can use any of the following window managers:

HWM (local) Uses the Hummingbird Motif-like window manager. If you are running the Exceed X server in either single window mode or in multiple window mode (with one of the X or the Default To Native options selected), double-click its icon to run HWM.

Microsoft Windows (local) Uses the Microsoft window manager on your PC. Windows automatically becomes the window manager when you select either the Native or Default to Native option in the Screen tab of the Screen Definition dialog box (with Multiple selected as the Window Mode). You cannot use Windows as your window manager in single window mode.

Remote X Window Managers Uses a window manager that resides on a host. You can use a remote window manager in multiple window mode (when either X or Default To Native as the Window Manager type).

110


Starting HWM or MWM MWM is available only with Exceed XDK.

HWM and MWM are located in the Exceed Tools folder. To open one of these window managers, double-click the appropriate icon.

Starting Remote X Window ManagersStart X window managers in the same way that you start any X client in Passive startup mode. If you are running an XDMCP startup mode, the remote window manager is likely specified in the hosts startup file.

To start a remote X window manager:

1 Connect to the remote host using any startup method such as Xstart, Xsession, or Telnet.

2 Provide a User ID, password, and any other login information required.

3 Type and execute the command to start the window manager.

Some typical window manager startup commands are listed below.

1 You must specify the DISPLAY environment variable or command line parameter so that the remote window manager knows which display it should use to connect.

Window Manager Startup Command Syntax1

DEC (UNIX) [path/]dxwm&

OpenLook [path/]olwm&

AIX [path/]aixwm&

DEC (VMS) [path/]SPAWN/NOWAIT/INPUT=NL RUN SYS$SYSTEM:DECW$WINMGR <CR>

Motif (VMS) [path/]SPAWN/NOWAIT/INPUT=NL RUN SYS$SYSTEM:DECW$MWM <CR>

111


Copying and Pasting

There are copy and paste commands on the Edit menu of most Exceed X windows applications. In most cases, these commands are the same as the copy and paste commands in other Windows applications.

Exceed provides copy and paste commands that can bridge the gap between X applications and Windows applications. They let you copy and paste between X and Windows, and X applications. These commands are listed on the Exceed X server Edit menu. Typically, you may want to copy and paste data such as long path specifications, command lines, and sections of script files.

To determine the copy or paste command you need, you may find it useful to think of the task in terms of the source and destination of the data. The copying and pasting procedure varies depending upon the source and destination.

If you are having difficulties with cutting and pasting data, ensure Clipboard contents appear in Clipboard (ClipBook) Viewer (on the Start menu, under the Accessories group).

The following sections describe copying and pasting procedures for the following scenarios:

• Between Windows-based applications (for example, Microsoft Word, Notepad, Paintbrush, Telnet, Hummingbird Basic, Xstart, and so on).

• Between Windows-based applications and X clients displayed on your PC (that is, displaying to your Exceed X server).

• Between X clients displayed on your PC.

Using a Temporary Storage Buffer The copying and pasting processes use a temporary buffer to hold data until it is cleared or replaced. This is similar to Windows Clipboard. The buffer being used depends upon whether you are running Windows applications or X applications.

If you are unsure, see your X client documentation.

The X selection an X client uses, and how it is used, depends upon the client. Most systems use the PRIMARY X selection, but other selections such as SECONDARY, CLIPBOARD, and CUT_BUFFER0 to CUT_BUFFER7 are also defined. Some clients can make use of more than one X selection.

112


To specify the X selection buffer:

1 Open Xconfig.

2 For Classic View, click the X Selection icon/text in the right pane. For Category View, click the X Selection icon/text.

For information on automatic copy and paste, see page 117.

3 On the X Selection page, select the correct buffer type, then click Validate and Apply Changes.

Copying and Pasting Data For information on copying and pasting between X clients, see page 116.

You can copy data to Clipboard, a file, or to the printer by using the methods listed below. If you copy and paste using the Clipboard, you can use csv and biff formats.

For more information, see the Help.

You can paste data from Clipboard or from a file, using the Paste to X Selection from Clipboard and the Paste to X Selection from File commands on the server Edit menu.

Copying

Copy Rectangle to Copies a selected rectangle of the active X client window (multiple window mode) or the Exceed X server root window (single window mode). After you choose Copy Rectangle to, the cursor changes to a camera icon. To define an area to copy, click anywhere within the window and drag the mouse to define a rectangle. When you release the mouse button, the Exceed X server copies the selected rectangle to the destination specified by the selected command.

Copy All to Copies all visible portions of the active X client window (multiple window mode) or the server root window (single window mode).

Copy X Selection to Copies the X selection.

For information on automatic copying and pasting, see page 117.

You can paste data from Clipboard to another Windows application as long as the destination application supports the data or format type.

Pasting

Paste to X Selection from Clipboard Pastes data from Clipboard to the X selection.

113


When you paste data from Clipboard to the X selection, Exceed assumes ownership for the X selection. You can then use the X client-specific method to paste X selection data into one or more X client windows (usually at the insertion point). If you are using the PRIMARY X selection, you can usually paste data into an X client window by clicking the middle mouse button.

Paste to X Selection from File Pastes data from a specified file to the X selection.

Copying and Pasting Graphics Exceed lets you copy images from X to Clipboard. You can copy an entire window or a partial window by dragging a rectangle over the window.

For more information, see “Installation Directories” on page 14.

The servers also let you paste images from Clipboard into an X client. The method of pasting an image to X is based on ICCCM (Inter-Client Communication Conventions Manual). For a technical description of the process, refer to seltest.doc, located in the Exceed installation directory.

An example of copying and pasting images is supplied in a file named seltest.c in

..Program Files\Hummmingbird\Connectivity\version\Exceed\Info

To build Seltest you must upload it to a host where an Xlib development environment is available. On a UNIX host compile Seltest as follows:

cc -o seltest seltest.c -lX11

where the library file libX11.a is on your path.

Note: If you are using a two-button mouse, start Xconfig, select Middle Button Emulation on the Mouse Input dialog box, then click OK. This lets you emulate a middle mouse button by clicking both the left and right mouse buttons simultaneously. For more information, see “Mouse Input Settings” on page 144.

Note: Many X clients support the copying and pasting of graphics to other X clients, but only through ICCCM X selections.

114


To copy images from Seltest to Clipboard:

You can find Clipboard (ClipBook) Viewer on the Windows Start menu, in the Accessories program group.

1 Clear the contents of Clipboard by selecting Delete from the Clipboard Viewer Edit menu.

2 Select Clear X Selection on the server Edit menu if you are running in single window mode, or from the Edit menu on Seltest system menu if you are running in multiple window mode. This causes the server to give up ownership of the primary selection.

3 Click the left mouse button in the seltest window. Seltest will request ownership of the primary selection and will associate the image it is displaying in its window with the primary selection.

4 Select Copy X Selection on the server Edit menu if you are running in single window mode, or on the Edit menu (the Seltest system menu) if you are running in multiple window mode. This causes the server to ask the primary selection owner (Seltest) for the primary selection image data. The server copies the image to Clipboard.

5 Display the Clipboard Viewer to verify the image was transferred from the Seltest client to Clipboard.

To paste images from Clipboard to Seltest:

1 Copy an image to Clipboard using an appropriate Windows application like Paintbrush.

2 Run Exceed and ensure the X selection option on the server Options menu is set to primary.

3 Run Seltest from an xterm or Telnet window as information is output to the standard output stream. Seltest initially displays an empty window.

4 Select Paste To X Selection on the server Edit menu if you are running in single window mode or on the Edit menu on Seltest system menu if you are running in multiple window mode.

115


5 Click the right mouse button in the Seltest window. Seltest will request the current primary selection information and display all of the selection target types, if any, which are available in the xterm or Telnet window.

If an image is available, it is displayed in the Seltest window. The amount of time it takes to display the image in the Seltest window varies depending on network load, image size, and color resolution, but should not be longer than 30 seconds in most cases.

Copying and Pasting Between X ClientsIf two X clients running on your PC support the same X selection, you can copy and paste between these X clients.

To copy and paste between X clients:

1 Place the data that you want to copy in the X selection buffer using the X client selection procedure.

2 On the Exceed X server Edit menu, click Copy X Selection to Clipboard. This places a copy of the X selection in Clipboard.

3 If necessary, start Xconfig, select the X selection type used by the destination client in the X Selection Settings dialog box, then click OK.

4 Choose Paste to X Selection from Clipboard on the server Edit menu.

5 Use the X client-specific method to paste the X selection data.

Note: Copying and pasting between locales is supported if you set up the input properly on your PC. To do this, open Control Panel and adjust the settings in the Regional Settings application.

116


Automatic Copy and Paste You can set your system to automatically copy and paste X selections. This saves time and is especially useful for high volume copying and pasting.

To set copying and pasting of X selections as automatic:

1 Open Xconfig.

2 For Classic View, click the X Selection icon/text in the right pane. For Category View, click the Copy and Paste, and X Selection icon/text.

3 On the X Selection page, select the following options, according to the automatic settings you want.

Select To do this

Auto Copy X Selection Copy the contents of the X selection to the Clipboard.

Copy On Focus Loss Copy the contents of the X selection to the Clipboard when the window containing the X selection is not in focus.

Auto Paste To X Selection Paste the contents of the Clipboard when the Clipboard contents change.

117

Chapter 5

Advanced Connection Methods

Advanced Xstart Features 121Using Login Macros 121Creating a Global Login 122Optimizing System Loads 123Running Multiple Xstart Sessions on One Host 124Password Expiry Prompts 124

Running Multiple Xstart Profiles 125Xsession File Sequence 128Creating an Xsession Shortcut 128Running Multiple CDE Sessions 129Multiple X Display Support 130

Using Exceed on a Remote PC 132Setting Up Xweb 133

Chapter 5: Advanced Connection Methods

Advanced Xstart Features

Using Login MacrosYou can use macros as shortcuts in the User ID, Password, and Command boxes of Xstar t.

User ID and Password MacrosYou can use the following macros to specify your User ID and Password in Xstart.

Command MacrosIn the Xstart Command box (in the Login area), you can type the command macros shown in the following table.

Macro Description

@u or @U Inserts your User ID

@p or @P Inserts your Password

Note: These macros are automatically defined by Xstart; you do not need to perform additional steps to define them.

Macro Description

@d or @D Inserts your display environment specification. Do not use with VMS systems. If you use the @d macro, type the following command to start xterm:

xterm -display @d &

@a or @A Inserts your network address. If you use the @a macro, type the following command to start xterm:

xterm -display @a:0 &

@: Inserts the correct display transport identifier (that is, “:” for TCP/IP and IPX/SPX, and “:” for DECnet). If you use the @: macro, type the following command to start xterm:

xterm -display @a@:0 &

121


Creating a Global LoginThis feature lets you cache your password, so that during an Xstart session, you need login just once. The system caches the password until you either exit Exceed or manually empty the cache. For example, you may need to manually empty the cache if you are leaving your PC unattended for an long period of time.

To create a universal login:

1 Create the Xstart file as usual. Refer to “Creating a Startup File” on page 92 for detailed instructions.

2 In Xstar t, click Options on the Tools menu. The Xstar t Global Options dialog box opens.

3 In the Login Macros area, do the following:

User ID (@u)—Type a global user name or type a login macro. For example, @u or @U automatically inserts your default User ID in the Xstar t Information dialog box.

Password (@p)—Type a global password or type a login macro. An asterisk displays for each character typed. For example, @p or @P automatically inserts your default password in the Xstar t Information dialog box.

4 In the Password List area, create a password list by providing a user ID and password for each host.

5 Select an option from the Remember Password drop-down list.

6 Click OK.

7 Click Save on the File menu.

@# Inserts your Display Number as configured in Xconfig's Communication Settings dialog box. If you use the @# macro, type the following command to start xterm:

xterm -display @a@:@# &

Macro Description

122


To manually empty the password cache:

1 Open an Xstart file.

2 In Xstar t, click Options on the Tools menu. The Xstar t Global Options dialog box opens.

3 In the Password List area, click Delete All. This empties the cache, so that the next time you run or create an Xstart connection, the system prompts for a password.

Optimizing System LoadsThis feature makes Xstart connections more efficient. It specifies that the connection is redirected to another host if the original host is already accommodating many connections.

When you run the Xstart file, the system locates the specified host. If that host is busy, the system finds the host best able to accommodate the connection, based on the search format you specified.

To optimize loads on host:

For more information, see “Creating a Startup File” on page 92.

1 Create the Xstart file as usual.

2 In Xstar t, click Settings. The Xstar t Settings dialog box opens.

3 Click Other, select Load Optimization and then click Configure. The Browse Load Optimization dialog box opens.

123


For more information about methods, see “Load Optimization” on page 98.

4 In the drop-down list, select a method. Depending on the method, provide information as required.

5 Click OK.

6 Click OK in Xstar t Settings.

Running Multiple Xstart Sessions on One HostWhen creating an Xstart file, you can put multiple commands in the Xstart Command box. This feature is useful for simultaneously starting X applications that you commonly use, such as expense reports, calendar, and mail applications. To use this feature, all of the X applications must reside on the same host.

Password Expiry PromptsXstart detects UNIX password expiry prompts that require the user to change password. This applies to Rlogin, Telnet, and Secure Shell start methods. You can use a text editor (such as Microsoft Notepad) to specify the password expiry prompts in passexp.ini (located in the home directory).

ExampleThe following specifies password expiry prompts for Linux and Solaris systems in passexp.ini:

# This is a comment line

[LINUX]Current_Password:(current) UNIX password:New_Password:Enter new UNIX password:Retype_New_Password:Retype new UNIX password:

[SUN]Current_Password:(current) SUN password:New_Password:Enter new SUN password:Retype_New_Password:Retype new SUN password:

Note: You may need to edit the command line to accommodate a particular host. For example, each command is separated by a semi-colon, but some UNIX hosts do not accept semi-colons.

124


Current_Password, New_Password, and Retype_New_Password are the prompt types. (current) UNIX/SUN password, Enter new UNIX/SUN password, and Retype new UNIX password are the password expiry text for prompts that are sent to Xstart from the Linux or Solaris systems.

If Xstart receives a password expiry prompt from a Linux host, the Password Expired dialog box opens requesting the following user input:

(current) UNIX password:

Enter new UNIX password:

Retype new UNIX password:

When the user enters the required passwords and clicks OK, Xstart negotiates with the host. If the new password is successful, Xstart automatically updates all Xstart profiles (that have the same host name and user ID) with the new password.

Running Multiple Xstart Profiles

To run multiple connections, create an Xsession file. Xsession lets you combine .xs files into a .ses file which can start multiple X clients or Windows programs (including Telnet, TN3270, and FTP settings files) simultaneously. You can specify whether the Exceed X server should list the file in its Session Star tup submenu or toolbar button, or if Exceed should automatically start before running the clients or programs. If you want Xsession to start the Exceed X server automatically, you can also specify the initial window and startup modes in the X Server Options dialog box.

You can create different Xsessions to run different window managers simultaneously.

Xsession provides other useful options such as specifying a configuration file with your own settings, window modes, and startup modes. If you select these settings within Xsession, they override Xconfig settings. For more information on Xconfig settings, see “Chapter 6: Xconfig—Configuring Exceed” on page 135.

Xsession

Note: By default, all Xsession files are saved in the user directory where Exceed is installed, but you can specify another location. The .ses file extension is appended automatically.

125


The following sub-sections describe how to create and run an Xsession file.

Entering Startup InformationYou may find it useful to create Xsession files that just start the X server with a specific startup mode and window mode. This lets you install custom icons to start the X server in different ways, to selectively override the default settings in Xconfig.

The Xsession displays information about Xstart files in the current session.

For information on creating an Xstart file, see “Creating a Startup File” on page 92.

Use Move Up, Move Down, Add, Remove to manage the Xstart files. Modify opens the selected file in Xstart where you can edit the profile. Reload updates and redraws the list of available Xstart files. This is useful if you are adding or deleting Xstart files while running Xsession.

File menu commands let you create new Xsessions, open existing Xsessions, and save Xsessions. You can also create shortcuts. View menu commands let you toggle the toolbar (on or off), set button size, or reload (update and redraw) the list of available Xstart files. This is useful if you are adding or deleting Xstart files while running Xsession.

Action menu commands let you run the current Xsession file, manage Xstart files listed in Session Contents, and open the selected file in Xstart for modification.

126


On the Tools menu, Repair lets you find and select a file which the application cannot locate (for example, if it was moved, deleted, or renamed since it was first added to the Xsession). The missing file is replaced by the selected file. Options opens the Xsession Options dialog box.

Use the General area to specify the interval between the startup of each Xstart file.

You can type a Session Description (up to 40 characters) which becomes the caption for the Session Star tup menu command (and when you click Client Star tup on the Exceed toolbar). To create this command, select Show on Exceed Star tup Menu. If you did not specify a Session Description, Xsession uses the file name (without the extension) for the (menu command) caption.

Note: Xstart Launch Interval applies to Xstart programs only. Local applications are started immediately.

127


Run X Server option starts Exceed automatically when the Xsession file is run. To restart the server with the server options specified in the Xsession file before running any programs, select Prompt for Server Restar t. You can specify an Exceed X server configuration file.

You can specify further overrides under Startup Option Overrides. Select Single, Multiple, or Default (specified on the Xconfig Screen page) Window mode. If the window mode is Multiple, select a window manager. Select a startup mode (Default is specified in Xconfig). If XDMCP Query or XDMCP Indirect is selected, specify the network address of the connect host.

Xsession File SequenceTo troubleshoot a connection, “Exceed Diagnostics” on page 254 and “Chapter 4: Connecting to Hosts and Running X Clients” on page 87.

This section describes the sequence of events when you run an Xsession session. Learning this sequence helps you troubleshoot your connections later on.

1 If Run Exceed X Server is selected in the Xsession Options dialog box, and the X server was not previously started, the X server starts. If the X server is already running and you have selected Prompt for X Server Restar t, Xsession prompts whether to restart the server.

2 After the time interval specified in the Xsession file has elapsed, the first profile listed in the Session Contents box starts.

3 There is a pause between the start of profiles corresponding to the Xstar t Launch Interval specified. They start according to the order listed in Session Contents.

Creating an Xsession ShortcutAfter you save an Xsession (.ses) file, you can install a shortcut.

Note: Xsession settings override the defaults in Xconfig.

Warning! To apply the new Xsession settings, you must restart the server.

128


To install an Xsession shortcut:

1 On the File menu, click Create Shor tcut. The Browse for Folder dialog box opens.

2 Select a location to install the Xsession shortcut. If you do not specify a location and click OK in Browse for Folder, the shortcut is installed on the Windows program menu.

3 To change the default Xsession icon, use the Windows Proper ties dialog box (right-click the shortcut, click Proper ties, and then click Change Icon). To change the caption or description, right-click the shortcut and click Rename. For more information, consult your Windows documentation.

Running Multiple CDE Sessions

To run multiple CDE sessions with Xsession:

1 Open Xstart and select Local Application as the startup method.

2 In the Command box, type parameters.

For example:

exceed.exe -d l -m query -h host -w single

In this example, the following parameters apply:

-d 1 specifies the display number

-m query specifies the startup mode

-h host specifies the connect host

-w single specifies the window mode

3 Click Settings and then click Other in the Xstar t Settings dialog box. In the General area, type an explanation or label (such as CDEHostA) in the Description box.

4 Click OK.

5 In Xstart, click Run to test the startup file. If it runs successfully, close it, and then click Save.

129


6 On the File menu, click New. Repeat steps 1 to 5 for each startup file, except type a different description (such as CDEHostB).

7 Open Xsession and click Add. Locate and select the multiple files created in Xstart. Click Open.

8 Xsession lists the files in Session Contents. Rearrange or modify the files as necessary.

9 On the Xsession File menu, click Save. Optionally, on the File menu, click Create Shortcut.

10 To run the multiple CDE sessions, click Run (or double-click the shortcut) to launch the multiple CDE sessions.

The next section contains more detailed information.

Multiple X Display SupportSupport for multiple X displays is available. It lets users run multiple simultaneous copies of the Exceed X server (limited only by available memory and resources) as long as each copy has a unique display number. This feature is useful for users who want to establish multiple XDM (X Display Manager) sessions with different hosts.

The following command line parameters are supported by the Exceed X server (Exceed.exe):

-d display#

-f filename.cfg

where display# represents the desired display number from 0 to 9999 inclusive and filename.cfg is the configuration file name.

The following command line parameters are optional:

-m [passive|query|indirect|broadcast]

-h hostname

-w [multiple|single]

where hostname represents the connect host for the XDMCP Query or XDMCP Indirect startup modes.

130


For example, to start the Exceed X server in single window mode on display 1 with a startup mode of XDMCP Query to host xdmhost specify:

exceed.exe -d 1 -m query -h xdmhost -w single

For a particular command-line parameter, if you want the setting to default to its current Xconfig value in the Exceed.xcfg configuration file, then omit its specification on the command line.

The easiest way to startup multiple simultaneous instances of the Exceed X server is to use Xsession.

To do this:

1 In Xsession, click Options on the Tools menu. In the Xsession Options dialog box, clear the Run X Server option.

2 Type an explanation or label in the Session Description box and save the session. Click OK.

3 Use Xstart to create and save a profile (specifying Local Application as the startup method) for each instance of the Exceed X server. For each profile, ensure:

• The command line is fully specified or that settings in Exceed.xcfg are suitable.

• A unique display number is used in each case.

4 Add the Xstart profiles to the Xsession. Save the Xsession.

5 Create a shortcut to enable a double-click startup of the session.

RestrictionsThe current implementation of multiple X display support has several restrictions or caveats. For example:

• Since certain X displays might share the same configuration file, do not make changes to your configuration while the Exceed X server is running.

Note: Multiple X display support has certain restrictions. See below.

131


• Since only one X display can own the desktop/root window and the configuration file is shared, do not enable the following multiple window mode Xconfig settings if you are using the multiple X display feature: Root Mouse Actions to X and multiple screens. The Root Drawing option should be None. You can still use the Root Mouse Actions to X toolbar button, but ensure the setting is selected for only one X display at a time.

• Colormaps are not shared between X displays which may result in color flashing in 256 color video mode when you change the focus between windows which are on different X displays.

• Multiple copies of the Exceed X server cannot share a single log file. To solve this problem, the name of the log file in your configuration file is used to construct the log file name for each copy of the Exceed X server.

This is done in the following manner: if the log file name in your configuration file is Exceed.log then each copy of the Exceed X server will use a log file whose name is exceeddisplay#.log where display# is the display number of the Exceed X server.

To disable support for multiple X displays, create an XServer key under the following key in Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Hummingbird\Connectivity\version\Exceed\

Create a (DWORD) value named DisableMultipleXDisplays and set the value to 1.

Using Exceed on a Remote PC

Xweb is also known as Broadway or X11R6.x

Xweb lets system administrators provide user access to X applications from a remote PC. The application is designed to extend X to the Internet, intranet, and extranet without making any modifications to the existing base of UNIX or X applications.

132


The system administrator embeds X application links on a web page for users to access from a remote PC. By using Xweb, users can access X applications from a central location without having to know the UNIX host name, or be familiar with UNIX or X Windows system protocol. The system administrator does not need to re-code the applications to make them available, and can control user access.

Xweb (Broadway) includes the Low Bandwidth X (LBX) application, a transparent extension to the X server that compresses X protocol and uses server-side caching to cut down X server requests. Overall, LBX improves the performance of X on WANs and slow dial-up connections. To use LBX, you must install lbxproxy on the host to which you are connecting.

To run Xweb, only the browser and the X server need be Broadway-compliant. However, each application on the UNIX server must now have three files associated with it:

Application-name.html—the page on which the URL resides.

Application-name.rx—An RX document describing the X server resources the application needs. For example, a data modeling application might specify the OpenGL extensions of Exceed for 3D rendering; if the X server does not support these extensions, an error dialog pops up.

Application-name.pl—the CGI (Common Gateway Interface) script that launches the application.

Setting Up XwebComplete the following general procedure to install and set up Xweb.

To set up Xweb:

1 If you have not already done so, install Exceed. Exceed fully supports X11R6.6 (Xweb).

2 Ensure the UNIX host can compile X11R6.3 or higher and you have installed a web server.

3 For each application on the UNIX server, install Application-name.html, Application-name.rx, and Application-name.pl on the web server. These files are outlined above.

133

Chapter 6

Xconfig—Configuring Exceed

About Xconfig 137Xconfig Window 138Xconfig Password 140

Mouse, Keyboard, and Other Input Devices 141Keyboard Input Settings 141Mouse Input Settings 144Input Methods for Chinese, Japanese, and Korean 148Special Considerations for Traditional Chinese 150

Network and Communication 153Setting the Sequence of Events 153Communication Settings 153About IP Discovery 155Transports Settings 158

Security, Access Control, and System Administration 158Security and Access Control Settings 159System Administration 163

X Server Protocol 164X Server Options and Extensions 164Extensions Settings 166

Display and Video 167Configuring X Screens 167Configuring Window Mode 168Common Settings 173Monitor Information 174Monitor Configuration 175Video Settings 176Advanced Settings 178

Copy and Paste, and X Selection 180Specifying X Selection Type 180

Font Management 181Managing the Font Database 182Accessing the Font Server 184Creating Font Aliases 186Creating Several Aliases 187

Other Server Settings 189Maximizing System Performance 189Power Management Settings 192Troubleshooting 193Accessibility 195

OpenGL 195

Xconfig Console 196Remote Configuration 196

Chapter 6: Xconfig—Configuring Exceed

About Xconfig

Xconfig includes applications for configuring the Exceed X server input, communication, video, protocol, security, window mode, performance, X selection, font, troubleshooting, and transport settings. In most cases, the default settings are sufficient. If the Exceed X server is running while you make changes to the configuration, the changes may take effect immediately or require a server reset, depending on the settings changed. If the change requires a server reset, a confirmation message appears. A server reset terminates all X clients.

For more information about user files and their location, see Exceed Help.

The default configuration file used by the Exceed X server is Exceed.xcfg. Per-user files, such as this one, affect only the user who is making the change (that is, the currently logged in user). For example, if you configure Exceed.xcfg to use a certain display, then other users of the machine are not affected.

For Windows 2000/XP/Server 2003 (for the current user), the default location is:

C:\Documents and Settings\%USERNAME%\Application Data\Hummingbird\Connectivity\version\Exceed

You can use Xconfig to make changes to Exceed.xcfg and create other configuration files (using Save As on the File menu). To have the Exceed X server use a configuration file other than Exceed.xcfg, you can either:

• Use the Xsession X server options to specify the configuration file in a session startup file and enable the Prompt For Server Restar t option.

• Specify /f and the full path to the configuration file on the Exceed X server command line.

Note: Each user of the product on the machine receives a personal user directory.

Note: This location is usually hidden (by default).

137


Consult Exceed Help to determine whether a particular configuration setting is global.

Certain settings, such as all security settings, are global to all configuration files. If you make a change to a global setting it changes in all configuration files.

Xconfig WindowThis window contains applications for configuring Exceed settings. To change settings, double-click the appropriate icon in Xconfig, or click a command from the Settings menu. The status bar at the bottom of the window indicates the various settings that you can configure with each application.

For more information about Xconfig, see the Exceed Help.

The Xconfig window consists of left and right panes. The left pane has menu boxes containing links for right pane views and for performing various actions. These links are also commands on the Xconfig menus.

The window can be resized. If you exit Xconfig and open it again, the size of your previous window is restored.

Menu Boxes

Xconfig This menu box is available for classic and category views. Click hypertext links that:

• toggle the right pane view of icons for configuration pages or configuration categories

• launch a new instance of Exceed using the current settings

Note: You can resize the Xconfig Window to the extent that only the right pane is visible.

138


• create a shortcut on the desktop and on the Windows Start menu

• launch Exceed Help and display the Xconfig topic

Quick Links This menu box is available for classic and category views. Click hypertext links that:

• let you change the Xconfig password

• display the Troubleshooting page

Common Actions This menu box is available when viewing settings pages for categories and tasks. Click hypertext links that:

• validate and apply changes to settings for the displayed category or configuration page

• discard configuration changes and exit the application

• restore default settings (the settings in Exceed.xcfg)

• launch Exceed Help and display the configuration topic

Switch Screens This menu box is available for the Display and Video category, as well as Screen Definition and Video pages. Click hypertext links to display a settings page for each screen. To select and configure multiple screens, press and hold Ctrl while clicking each screen link. The right pane tab displays a combination screen page according to your selection.

Add or Remove Screens This menu box is available for the Display and Video category, as well as Screen Definition and Video pages. Click hypertext links that:

• add screens (up to 8, the initial screen being screen 0)

• remove the highest numbered screen (except for screen 0)

139


Applying or Discarding Changes and Restoring DefaultsClick Validate and Apply Changes to apply your selections. Click Restore to Default Settings to restore the original settings for the Xconfig configuration file (Exceed.xcfg by default). Click Discard Changes to discard configuration changes and return to Classic or Category View.

Saving Changes and Creating Configuration FilesAll validated and applied changes are saved to the current configuration file. To save the configuration under a new file name, click Save As. To open another configuration file, on the File menu click Open.

Xconfig Password The Xconfig password protects access to the entire Xconfig application.

To change the Extend password, see “Modifying Extend Settings” on page 162.

To change your Xconfig password:

1 In the Quick Links menu box, click Change My Password. The Xconfig Password dialog box opens.

2 Type the current (old) password, type a new password, then confirm the new password by retyping it.

3 Click OK.

140


Mouse, Keyboard, and Other Input Devices

Use this Xconfig category to configure mouse and keyboard settings. If you are running a Chinese, Japanese, and Korean (CJK) Windows operating system or Windows 2000/XP (provided Microsoft IME is installed and enabled), this category includes a settings page for CJK input.

Keyboard Input SettingsThe Keyboard Input page lets you control Exceed X server settings for your keyboard. Keyboard files are provided, and contain keyboard layout and symbol mappings. You can create an entire custom keyboard manually, but usually it is better to start with one of the existing keyboard files, then customize it to suit your needs. You can also configure the keyboard file for the primary and alternate Exceed X server keyboards.

For more detailed information, see Exceed Help.

You can use the Keyboard Input page to:

• Customize the current keyboard file

• Select an alternate keyboard file

• Map Shift and Alt keys for Exceed

Customizing the Keyboard

To customize the keyboard:

1 Save a copy of the original keyboard file. This is a precaution in case you change a setting and it does not work, or you do not like the new settings.

2 In the Exceed folder, double-click Xconfig.

3 In Xconfig, do one of the following:

• select Classic View and click Keyboard Input

Keyboard Input

Note: By default, keyboard files (*.kbf) are stored in the directory where the Exceed user directory is installed.

141


• select Category View, click Mouse, Keyboard and Other Input Devices, and then click the Keyboard Input tab

4 Select the keyboard file you want to use. For both types of keyboards (Primary and Alternate), you can select a file from the corresponding drop-down list.

• Primary displays the name of the current primary keyboard file. The keyboard file contains the appropriate keyboard layout and alphabet for the language selected.

• Alternate displays the name of the current alternate keyboard file.

5 To change the individual settings of either the Primary or Alternate keyboards, click Edit. By customizing your keyboard file, you can associate keys with X keysyms and compose key sequences, and you can redefine keys.

Note: If you are not using one of the supported keyboards or if you are using a keyboard without a separate cursor keypad and 12 function keys, you can create a custom keyboard file to interact with Exceed.

142


6 To locate a keyboard file not listed in the drop-down lists, click Browse.

7 To allow users to modify keyboard files from their computers, select Allow Clients to Modify Keyboard Mapping.

8 For keyboards containing two Alt keys, you can select options to assign the left and right Alt keys. To direct Alt key sequences toward Microsoft Windows or X Windows clients, select an option from the Alt Key drop-down list:

• To Windows

• To X

• Left to Windows, Right to X

• Right to Windows, Left to X

9 For keyboards containing two Windows keys, you can select options to assign the left and right keys. To direct Windows key sequences to X Windows clients, select an option from the Windows Key drop-down list:

• To Windows

• To X

• Left To Windows, Right to X

• Right To Windows, Left to X

You can have each Windows key control a different function.

10 To define how the Shift keys on the keyboard are interpreted by Exceed, select an option from the Shift Key drop-down list:

• Map Both Left and Right

• Map Left as Right

• Map Right as Left

Note: The Windows key does not exist in the default keyboard file. To map a Windows key, you must add it manually. See the Exceed Help for details.

143


The Map Both Left and Right setting causes the left and right Shift keys to be treated and interpreted separately. When you select the Map Left as Right setting, any time you press a Shift key on your keyboard, it is treated as a right Shift. If you select the Map Right as Left setting, any time you press a Shift key on your keyboard, it is treated as a left Shift.

Mouse Input SettingsFor more detailed information, see Exceed Help.

The Mouse Input page lets you define mouse settings. You can:

• configure a middle button

• configure mouse wheel movement

• manage macros and map them to the mouse wheel

Customizing Mouse Settings

To customize mouse settings:


• select Classic View and click Mouse Input

• select Category View, click Mouse, Keyboard and Other Input Devices, and then click the Mouse Input tab

Mouse Input

144


2 Select an option for mouse wheel action:

• Wheel movement is ignored—Select this option to invalidate all mouse wheel input.

• Wheel movement scrolls Root windows (in Single Window Mode only)—Select this option to enable scrolling in the main root window only.

• Wheel movement invokes macro—Select this option to map the wheel movement to a macro. This is the only option that lets you scroll in multiple window mode. For instructions on how to map to a macro, see the procedure below.

• Wheel movement sends Mouse button event (button 4/5/6/7)—Use button 4/5/6/7 events to scroll the windows of existing X applications. ButtonPress and ButtonRelease events are sent according to the mouse wheel motion (up/down).

3 Make your two-button mouse into a three-button mouse for X client windows:

You can paste data (for PRIMARY X selection) into an X client window by clicking the middle mouse button. For more information, see “Pasting” on page 113.

• Selecting Middle Button Emulation enables the feature.

• Click Interval indicates the time lapse between clicking the left and right mouse buttons for middle-button emulation to occur.

• Movement Threshold indicates how much movement is allowed when you click the left and right mouse buttons. If you stay within the specified number of pixels, the system understands you are indicating middle button emulation.

145


Macro Mappings

To map the mouse wheel to a macro:

X windows does not recognize a mouse wheel. This application lets you translate it. You can map the mouse wheel for specific X applications.

1 On the Mouse Input page, select Wheel movement invokes macro, and then click Macro Mappings. The Mouse Wheel Macro Bindings dialog box opens.

2 On the Assigned Wheel Macros panel, select a mouse action combination, then click the adjacent browse button. The Macro Selector dialog box opens.

146


3 Click Add. The New Macro Proper ties dialog box opens.

4 In the Name and Description boxes, type the function and brief description. For example, type vi_scroll_up and Scroll Up.

5 After you have decided on the keys you want to map to the mouse wheel, in the Event List panel click Star t Record.

6 Enter the key sequence on the keyboard. When you are finished, the application stops recording automatically.

7 Click OK to return to the Macro Selector.

8 Select your new macro from the list, then click OK.

9 The new macro is associated with the wheel action you selected. Click OK to return to the Mouse Input dialog box.

147


Input Methods for Chinese, Japanese, and Korean This icon appears in Xconfig only if you are running a CJK Windows operating system or Windows 2000/XP (provided Microsoft IME is installed and enabled).

The CJK Input page lets you configure how to enter and pass Chinese, Japanese, or Korean (CJK) text to an X client.

The Exceed X server supports both Simplified and Traditional Chinese. To enter CJK text in an X client, you need to run an Input Method (IM) server.

You can configure the Exceed X server to use either an external X client as the IM server or an IM server built into the X server. To use the Microsoft Windows Input Method Editor (IME) to enter text in an X client, you must configure Exceed to use an IM server built into the X server.

You can select one of the following input methods to enter CJK text:

• Select Use Input Server on the host to use an input method server X client.

• Select Protocol to use an Input Method Server built into the Exceed X server.

• Select Copy and Paste to use copy and paste commands to input CJK text.

148


Using an Input Method Server X ClientFor information on the remote Input Method Server, refer to your host documentation.

The Use Input Method Server on the host option lets you enter CJK text using whatever mechanism the input method (IM) server X client supports. Select this option if you are using an external IM server X client. This means the Exceed X server will not support internal CJK input methods. This option does not permit the use of the Microsoft Windows IME to enter CJK text.

The available IM Server X clients vary by host type. The following table shows the IM Servers typically available on specific host types:

Using an Input Method Server Built into the Exceed X ServerSelect the Protocol option. The Exceed X server internally manages an Input Method Server and uses the Microsoft Windows IME to enter CJK text. When you enter text, the Exceed X server uses one of the selected protocols to pass text to the X client.

The Exceed X server registers and manages an Input Method Server for each protocol selected in the Protocol Selection area. This means that you can enable multiple protocols, and each X client can use the protocol of its choice. We recommend that you enable all available protocols.

Specifying Locale (Ximp/XIM)The Exceed X server supports most of the standard encoding names. In most cases, you do not have to specify the encoding name. However, if your X clients are running in a non-standard encoding environment, enter the appropriate locale name.

Host Type IM Server

HP xkim/xjim/xsim/stim

Solaris htt

Digital dxhangulim/dxhanyuim/dxhaziim/dxjim

149


Using Copy and Paste to Input CJK TextSelect the Copy and Paste option. The Exceed X server does not register an Input Method (IM) Server when this option is selected. Instead, it uses the Microsoft Windows IME to enter CJK text, and rather than using an IM Server to pass text to the X client, it copies the text into the X selection and tries to paste the X selection CJK text into the X client.

Exceed supports two copy and paste input methods. One is designed for Kterm and the other for OpenLook. Select the copy and paste method you want to use in the Use Environment area. If the CJK text is not automatically pasted into your X client, you need to use the X client Paste operation to paste the CJK text.

Special Considerations for Traditional ChineseBecause there is no standard encoding in Traditional Chinese environments, Exceed can support only one encoding name at a time. By default, the Exceed X server supports the HP-BIG5 (HP Traditional Chinese Environment) encoding. If you want to use the BIG5-0 (Digital Traditional Chinese Environment) encoding instead, you need to make changes to the Exceed initialization file and the xlc_locale file.

To input Traditional Chinese using the BIG5-0 (Digital Traditional Chinese Environment) encoding:

1 Open the Exceed.ini file in the directory where Exceed is installed and add the following line under the [Options] heading:

BIG5EncodingName=BIG5-0

2 Open the xlc_locale file on your PC and make the following changes:

a) under the heading fs1, modify as follows:

• # used for HP-UX

• # charset HP-BIG5:GLGR

Note: Remove this line to input Traditional Chinese in an HP environment (HP-BIG5).

150


• # used for Digital UNIX

• charset BIG5-0:GLGR

b) under the heading cs1, modify as follows:

• # used for HP-UX

• # ct_encodingHP-BIG5:GLGR:\x1b\x25\x2f\x30\x80\x8aHP-BIG5\x02

• # used for Digital UNIX

• ct_encoding BIG5-0:GLGR:\x1b\x25\x2f\x32\x80\89BIG5-0\x02

3 Restart the Exceed X server if it is running.

To view the Traditional Chinese HP Common Desktop environment:

1 Download the following Chinese Big5 fonts from ftp://ftp.edu.tw/Chinese/ifcss/software/fonts/big5/bdf or search for them at http://ftpsearch.lycos.com:

uwb5-16m.bdf.gz

eb5-24f.bdf.gz

2 Decompress the GZIP compressed fonts.

3 In Xconfig Font Settings, select Compile Fonts in the Font Settings dialog box and compile the downloaded .bdf fonts to the .fon format.

4 Copy uwb5-16m.fon and eb5-24f.fon to:

Program Files\Hummingbird\Connectivity\Exceed\version\Font\chinese

5 Import the font aliases:

a) Select Import Alias in the Font Settings dialog box.

b) Select chinese.ali in the directory where Exceed is installed.

c) For the Limit Import to Selected Font Directory option, select the directory shown in the previous step.

d) Click Import.

151


6 If the Exceed X server is running, point to Reload Database, then on the Exceed X server File menu, click Font.

To view the Traditional Chinese Digital Common Desktop environment:

1 Follow the steps in the above procedure.

2 Create a new font subdirectory under:

Program Files\Hummingbird\Connectivity\Exceed\version\Font

3 Download the following fonts from a Digital UNIX host that supports Traditional Chinese into the new font directory created in step 2:

• adecw_hei_cns11643_16_16_75.pcf

• adecw_screen_cns11643_16_18_75.pcf

• adecw_screen_cns11643_24_24_75.pcf

• jdecw_screen_decsuppl_8_18.pcf

• jdecw_screen_decsuppl_12_24.pcf

4 In Xconfig Font Settings, select Compile Fonts in the Font Settings dialog box and compile the downloaded .pcf fonts to the .fon format.

5 Add the new font directory to the font database and move it to the top of the font database list using the Move Up button.

6 Import the font aliases. To import the font aliases:

a) Select Import Alias in the Font Settings dialog box.

b) Select the dec_tw.ali file in the directory where Exceed is installed.

c) For the Limit Import to Selected Font Directory option, select the new subdirectory created in step 2 from:

Program Files\Hummingbird\Connectivity\Exceed\version\Font

d) Click Import.

7 If the Exceed X server is running, point to Reload Database, then on the Exceed X server File menu, click Font.

152


Network and Communication

Use this Xconfig category to configure communication and transports settings.

Setting the Sequence of EventsThe startup mode determines the sequence of events that occur when you start the Exceed X server, including whether a host connection occurs automatically. There are two basic types of startup modes: Passive and XDMCP. The mode you use depends on your transport, host, and preferences.

Passive Mode If you intend to use Telnet, Xstart, Xsession, or a remote process to connect to a host and start an X client, you should select Passive from the Modes drop-down list. This startup mode lets you start the Exceed X server without making any initial attempt to connect to a specific host.

XDMCP Modes The XDMCP (X Display Manager Control Protocol) modes lets you automatically activate the XDM connection process. After you start the Exceed X server, and successfully login to XDM, the clients listed in the XDM session script file are started.

XDM lets you manage X displays. It allows for centralized control over the X environment and provides an added measure of security. XDM provides an X-based login function and generates authorization information that can be used by the Exceed X server to control which users on which hosts may be given access to an Exceed X server display.

If you use an XDMCP startup mode, you do not need a separate startup application to start X clients (that is, Xstart, Xsession, or Telnet). However, you may use these applications to start additional X clients.

Communication SettingsThe Communication page in Xconfig lets you:

• select the startup mode used by the Exceed X server and define all related settings

• configure XDM display, key, class, and other startup options

Communication

153


• specify external addresses for connecting through a virtual private network (VPN)

• automatically close the connection under certain conditions

Startup

Mode This drop-down list contains two basic types of server startup modes: Passive and XDMCP (X Display Manager Control Protocol).

For more detailed information, see Exceed Help.

Configure Opens the XDMCP Star tup Modes dialog box where you can choose additional XDMCP settings.

Display Number Specifies which port is being monitored by the server for new clients. The default display number is 0. Change the default only if you are using a transport gateway product that shares a single network node address among all PC network users. In this case, your system administrator may ask you to change the value in this field.

Note: If you are using an IPX/SPX transport, ignore this field.

154


IP DiscoveryFor more information, see “About IP Discovery” below.

Use this area to specify addresses of remote servers running an IP address discovery service. Exceed queries these servers for an IP address so that the client can communicate with a remote host. Exceed translates the unique network IP address of the client PC (running Exceed) with the remote IP address.

Optionally, type one or two IP addresses (separated by a semi-colon) in the Server Address box. Specify a port number and timeout interval (applicable to both addresses).

Auto Close Connection

Enable Auto Close Connection Selecting this option means Exceed terminates a connection under one of the following two conditions:

Use X Screen Saver Time—The connection terminates when the screensaver activates.

After __ Hours __ Minutes—The connection terminates after the specified time.

Close Even When Application is Active The connection terminates if the host is still generating output, for example, during processes such as data compiling.

About IP DiscoveryThis feature supports multiple connections involving a network address translation (NAT) device or virtual private network (VPN) software. Exceed ensures that X applications from remote hosts reach the client PC.

IPDisCov DaemonIPDisCov is a daemon that runs on the remote UNIX or Windows host running X applications. By default, it listens on port 80 using HTTP. You can start IPDisCov on the UNIX host using the following command:

./IPDisCov -p listen_port_number

155


where listen_port_number is a port other than default 80. Use a browser to connect to the host and if the browsers displays the host IP address correctly then it means that the IPDisCov was started and is working.

Using IP DiscoveryThe environment variable DISPLAY tells the computer on which machine to display the X application.

To use Exceed in XDMCP mode or to use Xstart to start an X application on a UNIX host, Exceed and Xstart must construct the DISPLAY environment variable for the X application to display on the client PC. However, there may be VPN software that does not register the host IP address with the Windows system (to find out if this is so, use the DOS utility ipconfig to display the network settings). In this case, the only way for Exceed and Xstart to communicate with the remote host is by means of IP Discovery.

To use Exceed/Xstart where VPN software is present:

1 On the UNIX host, run ./IPDisCov -p listen_port_number. If necessary, specify another port number other than default port 80.

2 Use a browser to connect to IPDisCov and verify that the browser displays the correct IP address.

To access the Communication page, in Xconfig Classic View, click the Communication icon/text in the right pane. For Xconfig Category view, click the Network and Communication icon/text.

3 Open Xconfig. On the Communication page, select IP Discovery. Type the Server Address (the IP address where IPDisCov is running) and type the Port Number which IPDisCov is monitoring (if it is not the default 80).

4 Click Validate and Apply Changes.

Note: Only the root user has the authority to run the daemon on the UNIX host.

Note: You do not have to provide Server Address(es) at this stage. The Network Interfaces dialog box opens when Exceed or Xstart attempts to connect to the remote host. This gives you another opportunity to provide the IP discovery address(es).

156


For Exceed XDMCP startup modes:

1 On the Xconfig Communication page, select any XDMCP mode. Click Configure. The XDCMP Star tup Modes dialog box opens.

2 In the Network Adapter(s) area, select Network Interface and click Settings. The Network Interfaces dialog box opens.

3 There should be an entry in the list with the interface name “From IP Discovery Server”. The entry indicates the IP address (provided by the IPDisCov daemon) that Exceed uses to determine the DISPLAY environment variable. Select the entry and click OK.

4 Click Validate and Apply Changes.

For Xstart:

1 Open Xstart and click Setttings. The Xstar t Settings dialog box opens.

2 Click the Network tab, select Interfaces, and then click Settings. The Network Interfaces dialog box opens.

3 There should be an entry in the list with the interface name “From IP Discovery Server”. The entry indicates the IP address (provided by the IPDisCov daemon) that Xstart uses to determine the DISPLAY environment variable. Select the entry and click OK.

Note: If nothing is specified for Server Address in the IP Discovery area of the Xconfig Communication page, then the Network Interfaces dialog box opens when Exceed attempts to connect to the remote host. This gives you another opportunity to provide the IP discovery address(es).

Note: If nothing is specified for Server Address in the IP Discovery area of the Xconfig Communication page, then the Network Interfaces dialog box opens when Xstart attempts to connect to the remote host. This gives you another opportunity to provide the IP discovery address(es).

157


Transports SettingsThe Transports page lets you access transport-related settings used by the Exceed X server and local X clients.

Choose Transport Opens the Transpor t Chooser dialog box. If you installed multiple transport interfaces during setup, to switch transport interfaces, use this dialog box to select the correct interface.

Network Provider Opens the Provider List dialog box where you can set the order of transport service providers and protocols. You can also view details of each provider or protocol.

Security, Access Control, and System Administration

You can set security to either restrict or allow access to specific features of the Exceed X server. You can also use this category to:

• enable or disable host access

• create a security file (.xauth)

• modify Xweb security settings

• change security settings for Extend

• password-protect specific settings

Transports

158


Security and Access Control SettingsUse the Security page to restrict access to specific Exceed components.

Enabling and Disabling Host AccessUse the following options on the Security page to modify host access on your system.

Host Access Control List This area on the Security page lets you restrict access to your Exceed X server to specific hosts. By default, the Host Access Control List is the xhost.txt file, in the directory where the Exceed user directory is installed.

Note: If you select the xhost.txt file, you can use only the Passive startup mode in the Communication dialog box.

Security

159


Specify another file through one of the following methods:

• Type its full path (if other than the directory where the Exceed user directory is installed) and file name in the File box.

• Locate it by clicking Browse adjacent to the File box.

• Modify the Host Access Control List file in a text editor by clicking Edit.

No Host Access Instructs Exceed to use an empty Host Access Control List to regulate access. With an empty list, no hosts are allowed access. Optionally, you can select Prompt User to Add Host so that Exceed prompts for a host name which is added to a temporary host list. Not selecting this option means Exceed refuses a connection from an unknown host without prompting the user.

Any Host Access Terminates the use of the Host Access Control List and allows unrestricted access to all hosts on the network.

Allow Clients to Modify Host Access Control List This setting regulates client modification of the Host Access Control List (xhosts.txt).

Creating a Security File

Enable User Access Control List Lets you enable security at the user level (rather than at the host level) without using XDMCP. By default, this setting is not selected. For optimal security when using this option, clear the Allow Clients to Modify Host Access Control List check box and select an option in the Host Access Control List area.

User level security is controlled through an Xauthority file (by default .xauth) that is read each time the server is started or reset. You can create an Xauthority file using the host-based Xauth utility. To make this binary file available to Exceed, download it from the host and copy it to the directory where the Exceed user directory is installed. To select an Xauthority file other than the default xauth file, click Browse.

Unauthorized X Client Connections

Warn X Client Connection Attempt Displays a warning dialog box whenever a new X client tries to connect. This lets you prevent unwanted X applications from displaying on the Exceed X server while in passive mode.

160


Modifying Xweb SettingsYou can use Xweb security settings to control running X clients from web sites, either independently or embedded within the browser. Select from the options described below.

Security Policy File This file lets you specify certain restrictions on clients. Each line in the Security Policy text file starts with a keyword:

#—Lines starting with this symbol are treated as comments.

sitepolicy—Lines starting with this keyword are used to specify or name the policies that Exceed X server supports. These lines are characterized by a specific syntax: a collection of alphanumeric characters designed to match a similar collection in the configuration file of a firewall proxy.

property—Lines starting with this keyword are used to assign permissions to untrusted clients regarding access to window properties.

For more details about property access rules and keyword syntax, see the various comment lines in the security.txt file (click Edit in the Xweb area of the Security dialog box).

The syntax of property keyword lines are as follows:

In many cases, errors in the security policy file can cause applications to terminate, or even crash. The alternative is to specify ignore as the action, in which case, the operation is not carried out, but returns success.

Keyword Syntax

property The property name, such as, RESOURCE_MANAGER, WM_NAME, CUT_BUFFER0.

window The rule is applied to all windows.

propertyselector The rule is applied only to the root window.

permissions The rule is applied to windows having the specified property.

operation Denotes read, write, and delete respectively.

action Denotes allow, ignore, and error respectively.

161


Plug-in/Helper App Configuration Files The corresponding Edit buttons open Notepad with the respective configuration file loaded. This is the only place you can edit configuration files. If you edit them outside of Xconfig, the system returns a warning or error message, and ignores the configuration files.

Modifying Extend SettingsExtend is a suite of X Window clients that reside on the UNIX host.

Enable Extension If you select this box, the Extend extension is enabled. You must select this box to use Extend. This feature provides server support to the X Window clients. By default, this setting is not activated.

Password Opens the Extend Password dialog box, which lets you restrict access to the Extend extension by specifying a password. When the Extend clients are available on the host, authorized users with the password can:

• launch applications on the server PC

• access and transfer files between the host and PC

• print files

To change the extension password:

1 In the Extend area of the Security dialog box, ensure Enable Extension is selected, then click Password. The Extend Password dialog box opens.

2 Type the current (old) password, type a new password, then confirm the new password by retyping it.

Note: If you do not specify a Extend password, then anyone can access files on your PC.

162


3 Click OK.

System AdministrationThe System Administration page lets you password-protect specific settings categories. It also lets you disable some of the extensions and advanced functionality supported by Exceed. The settings in this page override the settings made on specific Xconfig settings pages.

Depending on how Exceed is installed, system administration may be preconfigured by the system administrator to protect Xconfig settings from accidental changes. If this is the case, only the system administrator can access this page. Similarly, you may not be able to access some setting categories or functionality because your system administrator has locked or disabled them.

Note: Remember the password. It is required to change the password again.

163


Password Protect Settings Selecting this option enables the lists and buttons in the Password Protect Settings area. Use the buttons to specify which settings are password-protected. By default, this box is selected.

Disable Features Selecting this option enables the lists and buttons in the Disable Features area. Use the buttons to specify which features are inaccessible to the user.

To disable access to the System Administration page:

1 Click Password.

2 Specify a system administration password. The next time Xconfig is run, the System Administration page is inaccessible.

To access the password-protected System Administration page:

1 Click Unlock on the Xconfig toolbar (or on the Actions menu).

2 Provide the system administration password.

X Server Protocol

X Server Options and ExtensionsThe Protocol page lets you control the options that regulate how the Exceed X server operates. This page also lets you enable, disable, and configure Exceed X server extensions.

Protocol

164


DECwindows Compatibility Provides DECwindows compatibility.

X Conformance Test Compatibility Configures the Exceed X server so it will pass certain tests in the X Conformance Test Suite (X Test Suite), which it would normally fail. These failures occur because some X clients have problems for which the Exceed X server has benign workarounds. You should also select Allow Clients to Modify Host Access Control List on the Security page, to pass certain X Test Suite tests.

To access the Delay Window Mapping option, in the Xconfig window (Classic View) click Screen Definition, click the Screen tab, and then click Advanced.

Additionally, selecting this option overrides the Delay Window Mapping option (in the Multiple Window Mode Advanced dialog box. If Allow Clients to Modify Host Access Control List is selected, there is no delay on window mapping.

Use 32 Bits Per Pixel for TrueColor Forces the Exceed X server to use 32 bits per pixel instead of 24 bits when using the TrueColor visual. Some X clients require this setting in order to draw properly. If your X client draws images incorrectly resulting in a scrambled image, enable this setting. By default, this setting is enabled.

Disabling this setting may result in an improvement in the performance of your Exceed X server; however, your images may draw incorrectly as a result. In that case, re-enable the setting.

Enable Custom Vendor String Lets you specify the vendor string that is passed to clients at connection time (in the connection block). If your client requires a specific vendor string, select Enable Custom Vendor String, type the Vendor String in the box, and click OK.

165


Extensions SettingsUse the Extensions page to enable and disable protocol extensions, and make certain ones available to untrusted clients. To select or clear extensions, click the box adjacent to each entry in the list boxes.

For information about default protocol extensions for Exceed.xcfg and individual protocol extensions, see Exceed Help.

You can allow access to extensions by untrusted clients (rendering the extension unsecured). You cannot do so for the following extensions: XC-APPGROUP, BIG-REQUESTS, Extended-Visual-Info, LBX, SECURITY, TOG-CUP, and XpExtension.

Otherwise, selecting extensions in the left list box enables them. Enabled extensions become available in the right list box. To make enabled extensions accessible by untrusted clients, select them in the right list box of the Extensions page.

For information about configuring GLX, see Exceed Help.

Configure Opens the Configure GLX dialog box if the GLX extension is selected in the left list box.

Warning! If All Extensions is cleared in the right list box after being selected, then extensions remain selected. You must clear each one to disallow access by untrusted clients.

Note: You can configure the GLX extension by selecting it and clicking Configure. In the Configure GLX dialog box, select options and click OK.

166


Display and Video

Configuring X ScreensThe Screen page lets you select the window mode (and related options), server visual, and monitors to use for each X screen. For more information, see “Window Modes” on page 109. In addition, you can add, enable or disable, and delete X screens. You can also provide information about your monitor configuration.

By default, one X screen (screen 0) is available. To add more X screens, click Add. To select and configure multiple screens, in the Switch Screens menu box, press and hold Ctrl while clicking each screen link.

Up to four X screens, and two hundred fifty six monitors, are supported. This feature is useful for users who need their data split across multiple monitors or divided into many screens.

Note: To use multiple monitors, you need to install multiple video cards on your PC.

Screen Definition

167


Configuring Four ScreensIf you configure four screens, they appear on the monitor as top left, top right, bottom left, and bottom right for screens 0, 1, 2, and 3 respectively. By default, one X screen is defined.

Deleting a ScreenTo delete a screen, select the tab for the screen, click Delete, then click Yes at the prompt. Screens must be deleted in reverse numerical order. That is, if you have four screens (0, 1, 2, and 3), you cannot delete Screen 2 before deleting Screen 3. You cannot delete Screen 0.

Disabling a ScreenAs an alternative to deleting a screen, you can disable it by clearing Enable Screen on the Screen tab. If you disable a screen, all higher numbered screens are disabled as well. You cannot disable Screen 0.

Performing Other Common Tasks• To add screens, click Add.

• To add monitors, select the Monitor(s) To Use For Screen option and type the number of monitors in the adjacent box.

• To customize screen focus changes, click the Common Settings tab and complete the information there.

• To indicate a custom monitor size, click the Monitor Info tab and type the monitor size in the boxes provided.

Configuring Window ModeCertain options in the Screen dialog box are window mode-specific; other options are common to single or multiple window modes. Selecting these options affects not only the appearance of your PC, but in certain instances, how it functions. The following sections describe these options.

Common OptionsThe following options are common to both single and multiple window modes.

168


Monitor(s) to Use for Screen Specifies virtual monitor numbers assigned to this screen. The default is 1; you can specify up to 256. You must enter a valid number of monitors. For example, to have the screen span the first two virtual monitors, enter 1,2. The numbering scheme of tiled monitors starts in the upper left, and then sequentially left to right, row by row. Using this sequential numbering, the monitor numbers specified must comprise a rectangle. See below.

For more information about this dialog box, see “Monitor Configuration” on page 175.

Click Edit adjacent to Monitor(s) to Use for Screen to open the Monitor Configuration dialog box. It displays a graphical representation of physical monitors and virtual monitors spanning them. The number of virtual monitors depends on the total resolution of all physical monitors attached to the system. Total resolution and resolution of a single monitor are displayed on the Monitor Info page.

Panning, Auto Load XRDB, and Root Size options are located on the Screen tab of the Screen dialog box.

Panning Lets you pan to view parts of client windows that are off-screen. By default, panning is enabled in multiple window mode; in single window mode, it is disabled. You can specify the following:

1 2 3 4

5 6 7 8

9 10 11 12

The shaded selection appears in Monitor(s) to Use for Screen as 3,4,7,8,11,12.

Assuming the shaded selection is assigned to another screen, then any combination of 1, 2, 5, 6, 9, 10 that form a rectangle can be specified for the current screen.

1024

768

256

256

Total resolution (pixels) of all (physical) monitors as determined by Exceed.

Single (virtual) monitor resolution (pixels).

The shaded selection appears in Monitor(s) to Use for Screen as 3,4,7,8,11,12.

Single (virtual) monitor resolution (pixels).

Option Description

Speed Select Slow, Medium, or Fast.

Amount Specify the incremental percentage of the window size in which panning occurs. You can enter any value between 1 and 100.

Note: In Multiple Window Mode, when you select Panning, do not select the Fit Window to Display option.

169


Auto Load XRDB Automatically loads the local resource database named in the File box each time the Exceed X server restarts or resets. Otherwise, you have to manually load it by choosing the corresponding command on the File menu in the Exceed X server. This file name is xrdb.txt by default.

Root Size Lets you set the size (in pixels) of the server root window. You can make the root window larger than your screen. The maximum root window size is 4096 by 4096 pixels. A width or height of zero implies the root size will be equal to the size of your screen. For certain applications to run, you may need to make the root size larger than your screen.

The server reset options and Close Warning on Exit option are located on the Common Settings tab of the Screen dialog box.

Enable Server Reset, Exit On Server Reset Located on the Common Settings page, this option resets the Exceed X server when the last client connection is closed. This option is enabled by default. When you enable this option, you can also enable Exit On Server Reset. This option lets you terminate the Exceed X server when the last client connection is closed.

Close Warning on Exit Exceed displays a warning message whenever you close a client window or choose a command that shuts down the server. This message prompts you to confirm or cancel the action.

These options are located on the Screen tab of the Screen dialog box.

Multiple Window Mode—Specific Options

Root Size Lets you set the size (in pixels) of the server root window. You can make the root window larger than your screen. The maximum root window size is 4096 by 4096 pixels. A width or height of zero implies the root size will be equal to the size of your screen. For certain applications to run, you may need to make the root size larger than your screen.

Note: You can find a sample xrdb.txt file in Program Files\Hummingbird\Connectivity\Exceed\version\Info. To use this file without changing the contents of the XRDB file box, copy it to the Exceed installation directory.

170


Window Manager Lets you select the window manager in Multiple Window Mode. You can select one of the following from the drop-down list:

If you are using an X window manager and want to display the X window manager menus, select the Root Mouse Actions To X option in the Advanced Multiple Window Mode Settings dialog box. By selecting this option, you can click the Windows desktop to access the X window manager menus. Normal Windows desktop mouse actions do not work when this mode is enabled. To change it immediately, toggle this option in Xconfig, or click a button on the server toolbar.

Fit Window To Display Makes the window of any client fit your screen if the window is larger than the physical screen.

Focus Policy Located on the Common Settings tab, this feature determines how a window is given focus if you are not using an X window manager. You can select one of the following from the drop-down list:

Window Manager Description

Native Microsoft Windows is used as the window manager.

X Any local or remote X window manager is used as the window manager. Since window managers do not start by default, you must start the window manager.

Default To Native By default, the native window manager (Microsoft Windows) is used. However, if a local or remote X window manager is started, it replaces Windows. After the X window manager is closed, Windows becomes the window manager again.

Note: If you enable Panning, do not enable Fit Window to Display.

Focus Description

Click Click the left mouse button on the window to give it focus.

Pointer Move the mouse pointer into the window to give it focus.

171


Cascade Windows Determines how to position client windows. It cascades all top-level windows for which a client does not specify any position.

These options are located on the Screen tab of the Screen dialog box.

Single Window Mode—Specific Options

Root Size Lets you set the size (in pixels) of the server's root window. In single window mode, you can make the size of the root window smaller (that is, if you have a high resolution display and want to restrict the size of the server window) or larger than your screen.

A width or height of zero implies the root size will be equal to the size of the client area of a maximized window when the Exceed X server menus appear on the Control menu (that is with no menu bars or scroll bars). If you make the root size larger than the client window, you can use the Panning feature or scroll bars to view any hidden parts of the root.

The root size group box also lets you enable Full Screen. This option sizes the Exceed X server window to the size of the entire screen. To open the server menu when you select Full Screen, select Panning. To open the server menu when you select Full Screen, press the ALT key and then the spacebar. The ALT key you press depends on your ALT key mapping.

Show Scroll Bars Lets you display scroll bars in the Exceed window. Scroll bars let you view hidden portions of the server root window when the Root Size option makes it larger than the workspace.

Save Geometry on Exit Saves the server window geometry (that is, its window position, size, and state) when you exit Exceed. When you restart Exceed, the options are restored.

Note: The window is not brought to the front when it is given focus with the pointer. To bring the window to the front, click your left mouse button on the window caption or on its sizing border.

172


Common SettingsThe Common Settings page contains the following list box and check boxes:

Native Window Manager Focus Policy Lets you choose whether a window has focus while the pointer is pointed only at the window or whether you need to click in the window.

Enable Server Reset Automatically resets the server when the last client connection is closed. This option is initially selected.

Exit on Server Reset Terminates the Exceed server when the last client connection is closed. This option is enabled along with the above option.

Close Warning on Exit Exceed presents a warning whenever you enter a command that shuts down the server or closes a client window (in multiple window mode only). This warning prompts you to confirm or cancel the action.

Hide X Server Menu Items Prevents users from performing tasks from the menu.

Exceed Multiple SessionsThe options you select in this area are reflected in the Exceed – Multiple Sessions dialog box after you validate and apply changes.

Do not Prompt for Multiple Sessions If enabled, Exceed does not open the Exceed – Multiple Sessions dialog box when other instances of Exceed are run.

Run Multiple Sessions Runs multiple instances of Exceed. If the Do not Prompt for Multiple Sessions check box is cleared, the Exceed – Multiple Sessions dialog box prompts you to select options for each session.

Note: The window is not raised when it is given focus with the pointer. To raise the window, click your left mouse button on the window caption or on its sizing border, if it has one.

173


Monitor InformationXconfig automatically determines the total resolution of all monitors attached to the system and displays width/height values on the Monitor Info page. For example, if you have one monitor set at a resolution of 800 x 600 pixels, the total resolution is 800 x 600; if you have two monitors next to each other set at 640 x 480 pixels, the total resolution is 1280 x 480.

Resolution of a Single Monitor lets Exceed determine the number of virtual monitors (maximum 256) that fit within the total resolution of all physical monitors. To create a uniform tile arrangement over your Windows desktop, specify a valid width and height for a single virtual monitor. Valid width and height values must produce a tiled array of monitors (256 or less—beginning in the upper left, then ordered from left to right, row by row) that exactly match the total resolution of all monitors. Using this technique, configure Exceed to treat multiple physical monitors as a single monitor, or configure Exceed to treat a portion of a physical monitor as a single monitor.

For example, if you have one physical monitor with a resolution of 800 x 600 pixels, you can configure Exceed to treat it as four monitors next to each other (in a row) by setting the Resolution of a Single Monitor width to 200 and height to 600. If you have two physical monitors next to each other, each with a resolution of 800 x 600 pixels for a total resolution of 1600 x 600 pixels. You can configure Exceed to treat them as a single monitor by setting the Resolution of a Single Monitor width to 1600 and height to 600.

Note: For Windows NT, Exceed only supports those configurations where all monitors are set to the same resolution (width, height, and color format). For example, if one monitor is set to 640 x 480 pixels with 256 colors, all monitors must be set to 640 x 480 pixels with 256 colors.

For Windows Me/98/2000/XP/Server 2003, Exceed supports monitor configurations where all monitors are not the same resolution (width, height, and color depth). For example, if one monitor is set to 640 x 480 pixels with 256 colors, other monitors can be set to a resolution of 1024 x 768 pixels with 32768 colors.

174


The Resolution of a Single Monitor width and height setting can also be set to 0. For Windows NT, if you set these values to 0, you are configuring Exceed to treat the entire Windows desktop (Total Resolution of All Monitors) as a single monitor. For Windows 98/2000/XP/Server 2003, you must set these values to 0 if your monitors do not form a uniform perfect tile over your Windows desktop. If you set these values to 0, Exceed queries the operating system to determine your monitor configuration and orientation.

Monitor ConfigurationMonitor Configuration is not available for Windows NT 4.0.

Use the Monitor Configuration dialog box to select and assign monitors to a particular screen. This dialog box displays the graphical representation of physical monitors attached to the system (similar to the Display Proper ties dialog box–Settings page, for Windows desktop). It also displays tiled virtual monitors spanning the physical monitors.

For more information about the Monitor Info page, see the previous section.

This arrangement is based on the width and height of the single monitor specified on the Monitor Info page. Select which virtual monitors apply to the current screen by using the rubber band feature: click, drag, and release the cursor to form a rectangle over contiguous virtual monitors. Alternatively, press and hold the Shift key while using arrow keys.

The selection must form a rectangle. Virtual monitors already assigned to another screen cannot be selected. If no virtual monitors are specified, then you can click only the one rectangle (physical monitor). In this case, only that virtual monitor applies to the current screen.

Assigned to another screen

Current selection

Rubber band

Click, drag, and release the cursor

175


Video SettingsVideo lets you customize the video mode and colors displayed by the Exceed X server. You can set the width and height of the your monitor, associate names with red-green-blue values in an RGB database and specify the icon defaults for native window manager mode.

Preserve System Colors Exceed attempts to preserve Windows system colors in newly created colormaps for as long as possible. By default, this setting is selected.

Pre-allocate System Colors in Default Colormap Exceed initializes the default X colormap with the Windows system colors in the first and last ten color cells. If you do not select this setting, Exceed initializes the default X colormap with:

If you are running an X client that requires white in Color Cell 1, disable this setting. By default, this setting is enabled.

Color Cell 0 Black

Color Cell 1 White

Video

176


This option is available only for Windows 98.

Enable System Pixels X applications expect to be able to change color 0 and 255 in application-allocated color maps when using a PseudoColor visual. Windows does not typically let applications change these color cells. An application that attempts to place a color other than black in color 0 or white in color 255 may not display the intended colors. This setting enables Exceed logic that removes this limitation.

ScreenSpecify In mm-Lets you adjust the screen size using the Width and Height text boxes. Width and height define the viewable portion of the screen in millimeters (1 inch equals 25.4 mm). If either of these fields is 0, the server uses the values returned by the Windows display driver. Because most X clients ignore the screen width and height data, the default values of 0 are sufficient in most cases.

Compute Based On Monitor DPI (dots per inch) Calculates the screen size based on the monitor dots per inch. Defaults are 75 and 100.

Palette

Defer Changes Determines whether palette changes are deferred to increase performance. The output of some applications may flash excessively if this option is not selected.

Optimize Colormaps To Reduce Flashing On Focus Change Determines how the Exceed X server interacts with the Windows color palette. Select this option to try reducing flash when changing focus from one window to another.

RGB DatabaseAssociates text names with the Red, Green, and Blue values displayed on your monitor. The RGB Database is the file in the User directory. To open the database in a text editor, click Edit. Select the appropriate keyboard file in the list or click Browse to select a file from another directory.

177


Native Window Manager Icon DefaultsLets you define the default foreground and background icon colors as well as which default client icon to use with the Native window manager. You can specify the icon colors using names that are listed in the RGB database, or you can specify an RGB triple (for example, 255 255 255). Click Change Icon to open a dialog box that lets you locate and select a different icon.

Advanced SettingsThis page contains the following options:

Map Window Without Motif Input Map window without Motif input. Motif input is a window property that specifies which window requires keyboard input. Selecting this option means the user can put input into any window.

Enable Full Drag Selecting this option means any window lying under a dragged window remains unpainted (it is not refreshed) until the user finishes dragging the window. Selecting this option saves bandwidth on the network.

No Focus on Window Raise This option (selected by default) keeps the focus on the lower window unless the X application sets the focus on the upper window.

Configure Window Position to Client Sets the window position to that of the client window.

Show Multiple Monitor Warnings This option (selected by default) displays a warning dialog box every time the user changes the system video settings.

Force X Application Window to Foreground This option (selected by default) forces the X application window to the foreground.

Pad Motif Window Puts one extra layer on the frame window. Certain applications expect this extra layer.

Allow Primary Window on Top Lets the primary window appear on top of any transient (secondary) dialog box.

178


On Focus Raise Window to Top Raises the window in focus to the top of the screen. Even if the X application doesn't require it, the window is restacked to the top.

Sun Microsystems Compatible Colormap Enables Sun Microsystems compatible colors.

For information about the Screen page, see “Configuring X Screens” on page 167.

User Installed Colormaps Use in pseudo color emulation mode only (select PseudoColor from the Server Visual drop-down list on the Screen page and select TrueColor in Windows' video settings). Exceed can emulate colormaps when in PseudoColor emulation mode. Most applications set each window to a certain colormap. For these applications, this option should be cleared. However, some applications (incorrectly) assume only one colormap is visible at any time. When this option is selected, windows that have requested the default colormap will use the installed colormap (via the InstallColormap protocol request) instead.

2D Overlay Treats the 2D overlay window as if it were placed on the main layer. This option avoids unnecessarily having to recalculate and redraw all windows on the main layer if the 2D overlay window were repositioned.

Depth-12 Psuedo Color Allow depth-12 psuedo color emulation for screens set to high color or true color.

This option is available only for Windows 2000/XP.

Win2K Layered Window Support Window layers do not have to be redrawn.

179


Copy and Paste, and X Selection

Specifying X Selection TypeYou can select the type of X selection commands on the Exceed X server Edit menu using the X Selection page. It also lets you set the Auto Copy X Selection and Auto Paste to X Selection options. The X selection setting and its options are saved when you terminate the server.

X Selection Associated with Edit Operations Lets you identify the correct X selection type. Most X applications use the PRIMARY X selection. With X clients that support SECONDARY or CLIPBOARD, you can change the X selection. For old X clients that do not support the X selection mechanism, you can choose from CUT_BUFFER0 through CUT_BUFFER7. If a client supports a different selection than those listed, then type the name of the custom X selection in the box.

For more information, see “Automatic Copy and Paste” on page 117.

Auto Copy X Selection When the X selection changes, the contents of the X selection are automatically copied to Clipboard.

Copy On Focus Loss Copies the X selection to Clipboard when the window containing the X selection loses focus.

Auto Paste X Selection When the content of Clipboard changes, it is automatically pasted to the X selection.

X Selection

180


Grab Clipboard Retry Time (ms) If Clipboard is unavailable, try again after the specified interval (in milliseconds).

Auto Paste Delay Time (ms) Copies the X selection to the windows clipboard after the specified time (in milliseconds).

Font Management

The Font page lets you view and edit the font database available to Exceed, import and export font aliases, compile BDF and PCF font files to the an Exceed format, and select default text and cursor fonts.

When you install Exceed, you automatically install font databases that support the International CDE.

Note: You do not have to modify the font database created during installation unless you want to use these new features.

Font

181


The font database includes support for scalable fonts and font servers. You can also create multiple font sets and load the one(s) you want to use at run-time. Exceed can automatically connect to a font server running on the XDMCP host server.

The font database is stored in the lfp.xdb file in the directory where Exceed is installed. Specific fonts in the font database are stored in font directories and font servers. Exceed also supports pseudo fonts for Unicode.

Managing the Font Database

To view and Edit the font database:


• select Classic View and click Font

• select Category View and click Font Management

2 On the Font page, click Edit. The Font Database: file - Xfonts dialog box opens listing all font directories and servers in the font database.

182


3 Use the buttons and options in the Font Database: file - Xfonts dialog box to make the following changes:

• add, change, or delete font directories in the database

• add, change, or delete font servers in the database

• change the paths of the font directories/servers

• determine (resolve) the physical font names of logical fonts

• rebuild the database

• enable automatic font substitution and advanced font server options

4 Place the font directories/servers containing the most commonly requested fonts at the top of the list to reduce the amount of time it takes to find a match. Click Move Up and Move Down to change the display (search) order.

To add, change, or delete fonts:

1 In the Font Database: file - Xfonts dialog box, select a font directory or server, and then click Font List. The Font List dialog box opens displaying the fonts contained in the selection.

183


2 Use the buttons in the Font List dialog box to make the following changes:

• add, change, and delete fonts

• load another font database file

• view font lists for each database, create aliases, and scale fonts

• rebuild font databases

3 After you have made changes, click OK in the Font List dialog box, and again in the Font Database dialog box. The modified file (.xdb extension) is saved in the directory where Exceed is installed.

Accessing the Font ServerAfter you have added a font server to your list of font databases, you can control how it is accessed. To access these options, click the Advanced Settings tab.

Note: When you install fonts, you should install both 75 dpi and 100 dpi fonts for best font matching. Additionally, if the monitor size is greater than 1024 x 768, in the Font Database dialog box, place the 100 dpi font in a higher priority than the 75 dpi font.

184


Font Servers

Synchronous Operation Font server requests are completely processed before Exceed continues servicing X clients. This option should be selected only for troubleshooting. By default, other X clients are serviced while an X client is waiting for the response from the font server.

Timeouts (secs.) Specify the read and write timeout values (from 0 through 999) for font servers. By default, the read timeout is 30 seconds and the Write timeout is 5 seconds. After timeout, Exceed assumes the font server is no longer available and closes the connection. If the timeout is too short, delays caused by network traffic might cause Exceed to unnecessarily disconnect from the font server. If the timeout is too long and the font server is unavailable, an excessive delay occurs before Exceed closes the connection. Default values favor a reliable connection, not the quick response. If the timeout is set for a quick response, the Enable Auto Reopen option should be selected.

Enable Auto Reopen Select this option to keep the font server available (active) at all times. This option requires your system to periodically check the font server and restart it, so it slows your system.

Enable Cache Select this option to automatically obtain or update a font cache on your local drive. This option is enabled by default.

Local Fonts First Select this option to search local fonts first select this option. Usually, the search priority is from top to bottom in the font database list.

Default Resolution for Scalable FontsFrom the drop-down list, select a resolution. Exceed uses this value to calculate font size in pixels. This is useful where the X client specifies size of a requested font in points but does not specify the resolution. If this value is set to zero, then the resolution is defined automatically by the screen resolution.

Other Options

Automatic Font Substitution Substitutes the closest matching font for any font request that cannot be filled and would otherwise result in an error.

185


Optimize for Java VM This option limits the behavior of Exceed to that acceptable by Java applications (Java applications are more restrictive than X applications).

Creating Font AliasesIn some cases, X clients may request a font not included in the database. The server responds by issuing a “Font not available” error message and logging the logical name or search pattern of that font in the log file.

You can use a font alias to link the requested font to an existing font with similar characteristics. After you create the font alias, clients can request the previously denied font so that the server can deliver the font alias.

To create a font alias:




2 On the Font page, click Edit. The Font Database dialog box opens.

3 Click Font List. The Font List dialog box opens.

4 Click Search to find an existing font resembling the requested font pattern. If you do not find one in this directory, try another directory until you find one that you consider a reasonable match.

5 Click Make Alias.

6 Type the font name in the box. If the font name is on the Clipboard, click Paste.

7 Click OK.

The font alias appears immediately below the logical font name in the second column of the Font List dialog box.

Note: Check the log file regularly for denied font requests.

186


Creating Several AliasesTo create several aliases at the same time, create an alias file containing all of the desired aliases. An alias file is a text file that you can create or edit in any text editor, such as Windows Notepad. You can then import the contents of the alias file into the font database.

Importing Alias FilesYou can import a file containing aliases into the font database.

To import an alias file:





3 Click Import Alias. The Import Alias dialog box opens.

4 Type the path of the alias file being imported in the From box or click Browse.

5 In the To box, select a destination path from the drop-down list. By default, the entry selected in the Font Database dialog box is initially displayed.

6 Click Import to start importing.

7 Repeat steps 4–6 for the each alias file you want to import.

8 Click Close.

187


Exporting Alias FilesThe Export Alias dialog box lets you export aliases from the font database. Using this feature, you can export a group of aliases to a file so that you can distribute them among other Exceed users in your company.

To export an Alias file:





3 Click Export Alias. The Export Alias dialog box opens.

4 In the From box, select a path from the drop-down list. By default, the entry selected in the Font Database dialog box is initially displayed. Select the desired Output Type.

5 Type the destination path in the To box or click Browse.

6 Click Export to start exporting.

7 Repeat steps 4 to 6 for the each alias file you want to export.

8 Click Close.

188


Other Server Settings

Maximizing System PerformanceThe Performance page lets you adjust the amount of Microsoft Windows system resources used by the Exceed X server to enable various performance-related drawing techniques. It also lets you tune the Exceed X server for optimal graphics performance for your current video configuration.

Drawing

Exact Zero-Width Lines To force exact line drawing for zero-width lines, select this option. By default, the Exceed server lets Microsoft Windows directly draw zero-width lines. This method is generally much faster than the exact pixel algorithm used by X to draw lines of other widths.

Note: Some video drivers ignore color information on some styles of zero-width line drawing. You should select this option if lines appear in an incorrect color, or do not appear at all.

Performance

189


Draft Mode Lets you improve performance through a slight and generally unnoticeable reduction in drawing accuracy. By default, this option is turned on.

Maximize X11Per Results If enabled, Exceed passes X conformance tests. Use this option only if you are performing X conformance testing.

Limit Window Exposures Preserves resources when many (or a few large) windows are open and allows pseudo color emulation (that is, pseudo color on true color screens). Unlike forced backing stores, this option does not save the bits of overlapping subwindows (windows that are a different depth from their parent window), or the (not visible) bits of very large subwindows. Selecting this option disables backing store options.

Use Disable Request Batching Flag This option processes similar requests independently.

Save Unders Lets you save parts of a window that become obscured by menus/windows in the foreground to system memory. The option eliminates the need to refresh the window when the menu rolls back up. The system ignores this check box if Maximum Backing Store is set to None.

Backing Store Options Refers to storing the information required to refresh the screen from the client in server memory. Backing store options let you specify the circumstances under which you want backing store to occur. Either the client requests a specific backing store, or the client leaves the type of backing store to the server.

You can specify a maximum and a default backing store value. Maximum governs when the client requests a type of backing store, and the default governs when the client leaves the backing store setting to the server. The following backing store settings are available:

• None—Never save the contents of the client window.

• When Mapped—Backing store is provided to all mapped windows. The storage of screen information only occurs when the client draws the screen in mapped mode.

• Always—Always attempt to preserve the contents of any window, whether it is mapped or not, as long as it is displayed on the Exceed X server. This option is available only for maximum.

190


Tune Starts the Xperf application. Xperf lets you override the current drawing methods used by the server and run tests to determine the optimal graphics configuration for your Exceed server. Before running Xperf, terminate all X clients since Xperf automatically terminates and restarts the server. If the server is already running, Xperf prompts you to confirm a server reset.

Advanced

Read on WriteBlocked This option continues processing X application requests even when the application temporarily stops responding to a reply or event.

SaveBits This option (selected by default) enables the Windows “save under” style for popup windows.

Enable OpenGL Backing Stores This option enables OpenGL backing stores.

Expose Event on Color Change For pseudo color emulation, this option asks the X application to redraw every time the colormap changes.

Oversized Cursors This option (selected by default—Windows NT only) enables the X application to create cursors larger than 32 by 32 pixels.

Note: If you change video cards, drivers, your video configuration, or the Accelerated Drawing Mode setting in the Performance Settings dialog box, run Xperf to ensure optimal server performance.

191


Power Management SettingsThe Power Management page lets you prevent your PC from entering standby or sleep mode.

Refuse Sleep Select an option to indicate under what circumstances the system should not enter sleep mode. If you are running connections to remote hosts, select the Always option.

User Interaction Select a time interval from the drop-down list to determine how long the system should standby before entering sleep mode.

Presentation This option maintains the display even if the system enters sleep mode.

Wake Up This option causes the system to reset after sleeping for a long period of time.

Power Managment

192


TroubleshootingThis page lets you view the log file, set what information is recorded in the log file, and enables tracing.

Enable LogThis setting activates the Exceed built-in logging functionality. Initially, the Enable Log option is selected, and Exceed logs information to the file specified in this textbox. By default, the Exceed.log file is stored in the User directory. You can specify another file by typing the full name and path in this textbox. To open this file in a text editor, click View.

When you select Enable Log, you can also enable and disable any of the following:

Log Font Opens Lets you log all requests to open fonts. Select this option only for troubleshooting purposes. Do not forget to clear this option when you are finished troubleshooting. By default, this setting is not selected.

Troubleshooting

193


Log Window and Command Names Causes Exceed to log the initial settings of the WM_COMMAND and WM_NAME properties on Input/Output root-level windows. This is useful when you are trying to determine which client is associated with a particular network socket. Select this option only for troubleshooting purposes. Do not forget to clear this option when you finish troubleshooting. By default, this setting is not selected.

Log GLX Information Logs all OpenGL requests. Select this option only for troubleshooting purposes. Do not forget to clear this option when you are finished troubleshooting. By default, this setting is not selected.

Log Xweb Information Logs significant Xweb events, such as security-related errors and connection anomalies.

Log Connection Error Logs connection errors.

TraceThe Trace group box lets you enable or disable any of the following:

Trace Initially On Do not select the Trace Initially On setting unless you want to trace the dialog between the server and the first client. When you select this option, the trace starts when the server does, and all dialog between the server and the first client, including XDM, is traced.

Xdis is not available with 64-bit versions of the product.

The trace file is output to the User directory with a .trx filename extension. You must disassemble these trace files into a readable format using Xdis before you can read its contents.

Slow Trace Lets you trace situations even when the server hangs. If the server hangs and the PC must be rebooted, the current trace file is likely unavailable; this setting lets you compensate for this situation.

Note: Select this setting only when absolutely necessary: it severely degrades server performance. Do not forget to clear this setting after performing your trace.

Warning! Use this setting only when absolutely necessary, as it severely degrades server performance.

194


Accessibility

This page lets you enable access to information about elements of the user interface. This improves the way accessibility aids or clients (for example: specialized programs, magnifiers, screen readers, and tactile mice) work with Exceed. You can select or specify the following:

Use Keyboard Hook Enables keyboard echo (keyboard input displayed on screen for collecting by a screen reader).

Interval to Check the Readiness of Accessibility The default is 5000 milliseconds. Setting it to 0 means that Exceed does not wait until all the information is ready for collecting by a screen reader when an X client window is created.

Maximum Times to Check the Readiness of Accessibility The default is 5. This determines the number of times Exceed tries detecting accessibility information. If accessibility information is ready for a screen reader, the X client window opens. If all attempts fail, the X client window still opens but without accessibility information. This happens when an X client is launched on a system without accessibility modules installed.

OpenGL

OpenGL is available only if you have Exceed 3D installed. The Open GL page provides the following options:

For more information about Exceed 3D and OpenGL X applications, see the Exceed 3D User’s Guide.

Enable OpenGL Enables GLX extension and Open GL interface options.

Direct Rendering Enables the local GLX client to send OpenGL rendering directly to the system without passing through the Exceed X server. This greatly enhances the OpenGL rendering performance. However, direct rendering cannot synchronize properties with other drawings done by the Exceed X server. By default, this option is not selected.

Accessibility

195


Hardware Acceleration Enables the use of OpenGL acceleration implemented by your graphics card driver. If this option is disabled, or if your hardware has no OpenGL acceleration, Microsoft's software implementation of OpenGL is used. To improve your OpenGL application performance, we recommend installing graphics cards with OpenGL acceleration.

One Visual Per Pixel Format Enables the server to create one GLX visual per pixel format supported by your graphics card rather than the default of creating four separate visuals (single-buffered RGBA, double-buffered RGBA, single-buffered color index, double-buffered color index). This gives GLX applications greater flexibility in choosing the best GLX visuals. By default, this option is selected.

Overlay Support Enables support for 3D overlays if supported by your video adapter.

Xconfig Console

Xconfig Console is a Microsoft Management Console snap-in for Windows 2000/XP. It has the same functionality as Xconfig, but with more administrative options.

Remote Configuration Xconfig Console lets you remotely configure computers that have the Xconfig Console component installed.

To connect to the remote computer:

1 Double-click Xconfig Console in the Exceed Tools subfolder (double-click the Hummingbird Connectivity desktop shortcut, then double-click Exceed).

2 In the left pane, right-click Xconfig, and select Connect to Another Computer.

196


3 Use the Select Computer dialog box to specify connection information.

Log in to the remote computer using your current account and password, or select Connect Using a Different User Name and specify that information.

Remote configuration uses the Xconfig System Administration password to open the remote configuration file. If a System Administration password was not set for the remote file, then leave the Password box blank.

Remote Xfonts ConfigurationFor more information about Xfonts, see “Font Management” on page 181.

Using remote configuration, users can configure Xfonts on another computer that is running Xconfig Console. With Xconfig Console in remote mode on the remote computer, launch Xfonts in the same way as you would locally, and then configure the remote font database file.

Comparing Configuration SettingsUsers can compare current configuration settings with a local configuration file. For example, the local file might contain the original default settings. This is useful for tracing modifications made in the current session and for troubleshooting the settings in local or remote configuration files.

Note: In Windows XP, if the network access policy “Sharing and security model for local accounts" is set to "Guest only" (the default), the local account login is authenticated to the guest account on the remote computer and the Xconfig Console remote setting is denied in most cases.

Xconfig Console remote settings should function properly if Windows XP was upgraded from Windows NT, or if you set the network access policy to "Classic". There is no restriction for remote Windows XP systems on a domain.

Note: Remote configuration of Xfonts is limited. Some functions, such as adding and viewing fonts, are not available.

197


Gnome Compliance of Native Window Manager The Native Window Manager is integrated with the Gnome desktop. The four workspaces on the Exceed menu and toolbar are associated with the icons on the Desk Guide and Gnome pager.

To use the Native Window Manager, open Xconfig or Xconfig Console, set the window mode to Multiple, and then select Native as the Window Manager.

Note: Using Native Window Manager with Gnome desktops over a slow network shortens the response times.

198

Chapter 7

Hummingbird Directory Services

Hummingbird Directory Services Applications 201Directory Services Explorer 201Hummingbird Directory Services 201Opening Directory Services Applications 203

Directory Services Overview 205Directory Service Protocols 205Directory Service Objects 206Server Architecture 207

Binding to Domains 208Locating Domain Servers 208Directory Service Profiles 210Creating Profiles 211Opening the Properties Dialog Boxes 214

Binding to NIS 214

Binding to NIS+ 217Keylogin and the System Profile 219

Binding to LDAP 220Specifying LDAP Domains and Bind Methods 221Retrieving Profiles from Directory Service Agents 223Securing LDAP with SSL/TLS 225Setting LDAP Search and Bind Options 227Specifying Authentication Methods for LDAP Profiles 228Specifying Schemas for LDAP Profiles 233

Exploring Directory Services 236Querying Directory Service Objects 236Sorting Query Results 237Saving Query Results 238Viewing Object Properties 239Modifying Profiles 239Changing Domain Passwords 240

Specifying Name Mapping Servers 242

Configuring Directory Services 243Selecting Services 243Modifying Profiles 244Disabling User Profiles 245Specifying Host Lookup Services 245Synchronizing Passwords 246Running Keylogin 247Running Command Line Applications 247

Chapter 7: Hummingbird Directory Services

Hummingbird Directory Services Applications

Hummingbird Connectivity applications include two directory services tools: Hummingbird Directory Services and Directory Services Explorer.

Directory Services ExplorerDirectory Services Explorer is a browsing tool that lets you access and query directory services without leaving the familiar Windows environment. Directory Services Explorer lets you do the following:

• bind your machine to multiple domains simultaneously

• browse object contents and properties

• run selective queries

• save query results to a file

• change your password in a directory service domain

Directory Services Explorer supports NIS, NIS+, and LDAP.

Hummingbird Directory ServicesHummingbird Directory Services provides access to directory services (NIS, NIS+, and LDAP) for Hummingbird Connectivity applications. Hummingbird Directory Services lets you do the following:

• Set up configuration profiles for your machine and for each user of that machine. Each profile stores the information necessary to bind to a given domain. Administrators can set up profiles on local and remote machines using the Hummingbird Directory Services snap-in for the Microsoft Management Console (MMC).

• Select the target service or services for host name resolution.

• Synchronize your Windows password with your password in a directory service domain.

• Retrieve the names of directory service, authentication, and name mapping servers by querying a DHCP (Dynamic Host Configuration Protocol) server, if one is available.

• Distribute directory service configuration information across nodes in a Windows cluster.

201


Once you have selected a service and established its domain profile, all directory service queries made by Hummingbird Connectivity applications target the domain you have specified.

Directory Services in a Cluster EnvironmentA cluster is a collection of independent computing devices that act as a single entity. Each device in the cluster is known as a node.

Hummingbird Directory Services supports Windows Clustering technology: if you configure the system profile on one node in a cluster, other Hummingbird Connectivity applications running in the cluster target the configured service.

Running Hummingbird Directory Services in a cluster provides the following advantages of the Cluster service:

High Availability If you configure directory services on a node that subsequently fails or is taken offline for maintenance, the cluster software transfers the configuration information to an available node in the cluster, with little or no interruption in service to applications using the directory service.

Failback If a node containing directory service configuration information fails, the cluster software automatically restores the information to the node when the node comes online again.

The Hummingbird Directory Services Snap-In for MMCThe Microsoft Management Console (MMC) lets Administrators configure various system and network components. The Console is actually a set of other tools, called snap-ins, that the console collects in a central access point. Each snap-in is an administrative interface, or console, for a given system or network component.

Note: To use Hummingbird Directory Services in a cluster environment, the cluster service must be running when you install the product.

202


For more information on the console, see Hummingbird Directory Services Help.

Hummingbird provides an MMC snap-in that lets you configure the system profile for local and remote instances of Hummingbird Directory Services through a console. The snap-in is installed whenever you install the NFS Administration feature for any NFS Maestro product.

Opening Directory Services ApplicationsFor more information on accessing the console, see Hummingbird Directory Services Help.

You can open both directory services applications from the Windows Star t menu. Administrators can open Hummingbird Directory Services from the console.

To open Directory Services Explorer:

1 On the Windows Start menu, point to Programs and navigate to Hummingbird Connectivity.

2 Point to Accessories, and then click Directory Services Explorer. The Directory Services Explorer window opens.

203


To open Hummingbird Directory Services from the Start menu:

1 On the Windows Start menu, point to Programs and navigate to Hummingbird Connectivity.

2 Point to Accessories, and then click Directory Services Proper ties. The Hummingbird Directory Services Proper ties dialog box opens.

The Hummingbird Directory Services Properties dialog box is also accessible in view mode through NFS Maestro Server. If you open the dialog box from this application, you can only view the properties of the user and system profiles. To create, modify, or select a profile, you must open the dialog box using the method described above.

204


Directory Services Overview

A directory service stores and discloses network information such as host names, user IDs, and available resources. The service works in essentially the same way as a phone directory: to phone someone, a caller uses a phone book to look up the number associated with the person’s name; to connect to a remote host, a client queries a directory service to retrieve the IP address associated with the name of the host.

Without a directory service, every host in a network needs to store and maintain its own copy of the network information. A directory service, on the other hand, centralizes network information in a single repository that each client can query. In this way, a directory service ensures the consistency of the information and simplifies network administration.

Directory Service DomainsDirectory services organize their information into domains. A domain consists of a group of computers and users that share the same network and configuration information. Typically, a domain corresponds to a particular organization or department within an organization. When you query a particular service, you must specify a domain for that service.

Directory Service ProtocolsClients communicate with a given service using a protocol specific to that service. Directory Services Explorer and Hummingbird Directory Services support NIS, NIS+, and LDAP.

NIS The Network Information System (NIS) protocol was developed by Sun Microsystems to simplify the administration of network and configuration data. NIS stores its information in objects called maps that can be accessed over the network using the Remote Procedure Call (RPC) protocol. NIS domains are flat and discrete: any map within a given domain belongs to and records information about that domain alone.

205


NIS+ NIS+ was developed by Sun Microsystems as an enhancement of the NIS protocol. NIS+ objects, called tables, can be searched on multiple columns (unlike NIS maps). Clients access NIS+ tables using the RPC protocol. Unlike NIS domains, NIS+ domains are hierarchical and can be extended to match the growth of the organizations they describe. NIS+ also protects its data using Secure RPC authentication.

For more information on supported LDAP schemas, see Hummingbird Directory Services Help.

LDAP The Lightweight Directory Access Protocol (LDAP) was developed by CCITT and ISO as a scaled-down version of the X.500 protocol. Unlike NIS and NIS+, which are proprietary protocols, LDAP is an open standard. Like NIS+, LDAP secures its objects by requiring client authentication. Hummingbird Directory Services and Directory Services Explorer have been thoroughly tested with the Sun One Directory Server (ranging from iPlanet 4.x to 5.x) and support the following servers:

• RFC2307-compliant servers

• RFC2307AIX servers

• Microsoft Active Directory servers that have been updated with AD4UNIX or VAS extensions

You can also configure Hummingbird Directory Services and Directory Services Explorer to bind to LDAP domains that use nonstandard schemas. For more information, see “Defining Custom Schemas” on page 234.

Directory Service ObjectsFor more information on directory service objects, see Hummingbird Directory Services Help.

NIS and NIS+ store their information in tabular form. Only NIS+ refers to its objects as tables. NIS objects are known as “maps” because each maps a particular value (a “key”) to a piece of network information. LDAP objects are known as entries.

NIS/NIS+ ObjectsNIS maps each consist of an information column, which stores the network information, and a key column, which serves as an index to the information column. The information column typically separates the various attributes of the object using a colon (:).

Each column in a NIS+ table defines an attribute of the type of information stored in the object. For example, a table containing password information typically has user name, user ID, primary group ID, and password columns.

206


Each row (or “entry”) in a NIS/NIS+ object represents one piece of network information, such as the complete password information for one user.

LDAP ObjectsLDAP entries correspond to the rows in a NIS map or NIS+ table. However, LDAP entries are discrete objects that can be selected and manipulated independently of one another. LDAP entries can also contain other LDAP objects.

Object ContentsThe type of information stored in a directory service generally reproduces the content of UNIX /etc files. For example, NIS stores password information (usually stored in /etc/passwd) in two maps, called passwd.byname and passwd.byuid. NIS+ stores the same information in a table called passwd. In the RFC 2307 schema, LDAP stores password information in entries that belong to the posixAccount class; in the AD4UNIX schema, LDAP stores this information in entries that belong to the User class.

Server ArchitectureThe repository for a directory service usually consists of one main server—the master server—and a group of supplementary servers. The master server stores and manages the network information. The supplementary servers store a copy of the master information. Supplementary servers in NIS are known as slave servers. Supplementary servers in NIS+ are known as replicas.

Whenever the network information changes on the master server, the changes propagate across the network to the copies. Therefore, at any given time, there are several hosts capable of disclosing network information to clients. This architecture lets the administrator evenly distribute the network load across more than one server. From the point of view of clients who access the service, the changes are automatic and transparent.

LDAP uses multiple servers that can independently update the network information and synchronize it with each other.

Directory Services Explorer and Hummingbird Directory Services let you target your queries to specific servers in a domain.

207


Binding to Domains

Before you can query a directory service, you must first bind to a domain. Each directory service domain is controlled by one or more servers that store and release the domain information. When you bind to a domain, you configure your system to send its queries to one of the servers that control that domain.

Bind InformationThe process of binding to a domain differs from service to service. In general, you need to supply the domain name and names of the servers you want to query. If the service (such as NIS+) uses an authentication protocol, you also need to supply valid credentials.

Directory Service ProfilesYou save the complete information for binding to a given domain in a profile. The profile records the details about the domain as well as the particular method by which you bind to it (for example, under user or machine credentials, or as one user or another).

Locating Domain ServersDirectory Services Explorer and Hummingbird Directory Services can automatically locate NIS/NIS+ servers that are part of your local subnet by sending a broadcast across the network.

To find the names of remote NIS+ and LDAP servers, contact your NIS+ or LDAP administrator. If you are using NIS as your directory service, you can use the ypwhich command to determine the names of NIS servers for a given domain.

For more information, see Ping Help.

If you know the name of the server, you can use the Ping accessory to determine if it is accessible from your machine.

208


Locating Servers Using DHCPIf your network has a Dynamic Host Configuration Protocol (DHCP) server that stores configuration information for network servers, such as directory service, name mapping, and authentication servers, Hummingbird Directory Services can query the DHCP server to retrieve the configuration information. Depending on the type of server represented in the DHCP server, the configuration information can include the name of the server, the directory service domain it supports, and the port number on which it operates.

For more information on Relay Agents, consult RFC 1542.

Retrieving configuration information from a DHCP server is usually quicker than scanning the network. Also, if DHCP Relay Agents are installed on other subnets, you can retrieve configuration information for servers outside your immediate subnet.

For more information on DHCP, see RFC 2131.

The Dynamic Host Configuration Protocol provides a mechanism for storing configuration parameters about network hosts (such as IP addresses) and delivering this information from a DHCP server to DHCP clients. The protocol also specifies a method to dynamically assign IP addresses to hosts on a network. The protocol simplifies network administration because administrators do not need to add or maintain addresses for each machine they support.

Configuring DHCP for Hummingbird Directory ServicesBefore you can retrieve server information from a DHCP server, either or both of the scope or server options on the DHCP server must be configured correctly. (If both are set, scope options take precedence.) There is a specific option code for each type of server information you can retrieve. The following table presents the options that need to be set:

Option Code Information Type Data Type Array?

040 NIS domain name String No

041 NIS servers IP address Yes

064 NIS+ domain name String No

209


For more information on DHCP options, consult RFC 2132 or visit the following web site:

http://www.dhcp.org

Directory Service ProfilesThe type of profile you create for a domain depends on the application you are using.

Directory Services Explorer ProfilesYou can create up to ten profiles for each directory service.

In Directory Services Explorer, you can create multiple profiles, each corresponding to a single domain and binding method. In other words, Directory Services Explorer lets you bind to and explore multiple domains simultaneously.

You can examine the objects in each domain as if they were directories in a mapped drive. (The process of binding to a server is analogous to mapping a remote drive.)

For easy reference, you can give the profile a descriptive name. This is the name under which the domain appears in Directory Services Explorer.

065 NIS+ servers IP address Yes

200 hclnfsd/pcnfsd server String No

201 Name mapping servers String No

202 LDAP servers String No

Note:

• The protocol reserves the option codes 040, 041, 064, and 065 for NIS and NIS+ server information. The other listed codes are not reserved. Make sure they are not already in use on the DHCP server.

• When setting server information for codes 201 and 202, separate multiple server names with a space.

Option Code Information Type Data Type Array?

210

http://www.dhcp.org


Hummingbird Directory Services ProfilesHummingbird Directory Services lets you create a directory service profile for your machine (the system profile) and for each registered user on that machine.

The profile contains the information necessary to bind to a domain for each service supported by Hummingbird Directory Services. For example, you can create different user profiles to bind to a NIS domain, a NIS+ domain, and an LDAP domain.

When you select a particular service from within a Hummingbird Connectivity application, the application sends your queries (such as host lookup) to the domain specified in your profile for that service. The system profile is selected by default.

User Profile Users can set up profiles that let them bind to domains of their choice. They supply the configuration information for one directory service (or more) and then select the service they want to use for a given task. A user profile is specific to a given user; the profile is in effect while the user is logged into the machine.

System Profile The system profile contains the default configuration information for any application or user that queries a directory service. A user that does not have a NIS account, for example, can still query the NIS domain specified in the system profile. The administrator for the machine can also configure Hummingbird Directory Services so that users can bind only to the domains specified in the system profile. (In this case, users cannot create their own profiles.)

If you have used Hummingbird Directory Services to set up user or system profiles, you can view those profiles (under those names) in Directory Services Explorer.

Creating ProfilesYou must be the Administrator for the machine to create the system profile. Any user, however, can view the settings for the system profile (in Hummingbird Directory Services) or the contents of its configured domains (in Directory Services Explorer).

211


To create a profile using Directory Services Explorer:

1 On the File menu of Directory Services Explorer, click Settings. The Directory Services Explorer Settings dialog box opens.

2 From the Directory Service list, select the service you want to target in the profile—NIS, NIS+, or LDAP.

3 Click Add. The Proper ties dialog box for the selected service opens. For example, if you have selected LDAP, the LDAP Proper ties dialog box opens.

4 In the Properties dialog box, specify the domain for the selected service and assign a name to the profile.

• For more information on specifying a NIS domain, see “Binding to NIS” on page 214.

• For more information on specifying a NIS+ domain, see “Binding to NIS+” on page 217.

• For more information on specifying an LDAP domain, see “Binding to LDAP” on page 220.

After you have specified the domain, its name appears in the Profile box of the Directory Services Explorer Settings dialog box.

5 In the Directory Services Explorer Settings dialog box, click OK. The dialog box closes and the profile is stored locally. You can browse the specified domain under the profile name you assigned to it.

To create a profile using Hummingbird Directory Services:

1 Open the Hummingbird Directory Services Proper ties dialog box.

2 Do one of the following:

• To create your user profile, select User Settings.

• To create the system profile, select System Settings.

Note: If the User Settings option is dimmed, the administrator for your machine has disabled user profiles. You must use the system profile. If you want to bind to a NIS+ domain, you can still run keylogin to retrieve your own DES credentials. For more information, see “Running Keylogin” on page 247.

212


3 From the Directory Service list, select a directory service.

For more information on DHCP servers, see “Locating Domain Servers” on page 208.

4 If there is a DHCP server on your network, and you want to use it to retrieve the server configuration information for the selected service, do the following:

a) Click DHCP. Hummingbird Directory Services queries the DHCP server to retrieve the server information. You can terminate the query by clicking Cancel in the progress dialog box.

b) In the dialog box that opens, examine the retrieved server information. If the information is correct, specify any additional configuration parameters for the service, and then click OK.

5 Click Proper ties. The Properties dialog box for the selected service opens. For example, if you selected NIS+ in step 3, the NIS+ Proper ties dialog box opens.

6 In the Properties dialog box, specify the domain information for the selected service.

• For more information on specifying a NIS domain, see “Binding to NIS” on page 214.

• For more information on specifying a NIS+ domain, see “Binding to NIS+” on page 217.

• For more information on specifying an LDAP domain, see “Binding to LDAP” on page 220.

7 In the Hummingbird Directory Services Proper ties dialog box, click OK. The dialog box closes. Any queries issued by a Hummingbird Connectivity application (except Directory Services Explorer) target the domain specified in the selected profile.

213


Opening the Properties Dialog BoxesFor each supported directory service protocol there is a Properties dialog box that lets you specify the domain for the service and configure other bind options.

To open a Properties dialog box in Directory Services Explorer:

1 On the File menu, click Settings. The Directory Services Explorer Settings dialog box opens.

2 From the Directory Service list, select the service you want to configure—NIS, NIS+, or LDAP.

3 Click Add.

To open a Properties dialog box in Hummingbird Directory Services:

1 From the Directory Service list of the Hummingbird Directory Services Properties dialog box, select the service you want to configure—NIS, NIS+, or LDAP.

2 Click Proper ties.

Binding to NIS

When you bind to a NIS domain, you can specify a primary and secondary domain server. Any queries sent to NIS target the primary server, or—if the primary server is unavailable—the optional secondary server. Your choice of primary and secondary servers can affect the distribution of network load across the NIS master and slaves.

Using Hummingbird Directory Services, you can also specify the maps for host resolution queries. Hummingbird Connectivity applications that run host name/address lookups consult the maps that you specify.

214


To bind the current profile to a NIS domain:

For more information, see “Opening the Properties Dialog Boxes” on page 214.

1 Open the NIS Proper ties dialog box.

2 Type the profile name for the domain into the NIS Profile Name box (Directory Services Explorer only).

3 Click Proper ties. The NIS Domain Configuration dialog box opens.

4 In the NIS Domain Name box, type the name of the NIS domain. NIS domain names typically consist of two labels separated by a period (for example, abcd.com). The first label indicates the organization; the second label can be an Internet domain name such as com, org, or edu.

5 If the NIS master server is in the same subnet as your machine, select Automatically Obtain Server List. Otherwise, select Manually Enter NIS Servers; then, type the name or IP address of your primary NIS server in the Primary Server Name or IP Address box. If you want to specify a secondary server, type its name or IP address into the Secondary Server Name or IP Address box.

215


6 Click OK. The NIS Domain Configuration dialog box closes. The NIS Properties dialog box displays the configuration information.

7 In the NIS Proper ties dialog box, set the server query order. The NIS Servers list displays the available servers. The top-to-bottom order of servers in the list corresponds to the query order. To change the query order of a server, select it from the list, and then click the Up or Down buttons at the right of the list to move the server to the correct position.

8 If you are creating a NIS profile in Hummingbird Directory Services, do the following:

a) In the Name Resolution Map box, type the name of the host name resolution map for the selected domain. In the standard NIS configuration, this map is called hosts.byname.

b) In the IP Resolution Map box, type the name of the host IP resolution map for the selected domain. In the standard NIS configuration, this map is called hosts.byaddr.

9 Click OK. The NIS Proper ties dialog box closes. The NIS service is configured for the specified profile.

216


Binding to NIS+

When you bind to NIS+, you can set a query order for NIS+ servers. Alternatively, to balance service loads across the network, you can specify random access to NIS+ servers. By default, your queries target the NIS+ master (if available), and then any available replica servers.

For more information on required NIS+ credentials, see “Keylogin and the System Profile” on page 219.

Hummingbird Directory Services lets you bind to a NIS+ domain as either a user or a machine, depending upon the profile you have selected in the Hummingbird Directory Services Proper ties dialog box. Certain tasks, such as connecting to an NFS resource or changing your password in a NIS+ domain, require user credentials.

To bind the current profile to a NIS+ domain:


1 Open the NIS+ Proper ties dialog box.

2 Type the profile name for the domain into the NIS+ Profile Name box (Directory Services Explorer only).

3 Click Proper ties. The NIS+ Domain Configuration dialog box opens.

217


4 In the NIS+ Domain Name box, type the name of the NIS+ domain. NIS+ domain names consist of two labels separated by a period and always end with a period (for example, abcd.com.). The first label indicates the organization; the second label can be an Internet domain name such as com, org, or edu.

For more information on NIS+ credentials, see Hummingbird Directory Services Help.

5 In the NIS+ Credentials area, enter your credential information:

• To set up the system profile, type the Secure RPC password for your machine into the Secure RPC password box. (The system profile is accessible in Hummingbird Directory Services only.)

• To set up a different profile, type your user name for the domain into the User Name box; then, type your Secure RPC password into the Secure RPC Password box. Usually, your Secure RPC password is the same as your domain password.

6 If the NIS+ master server is in the same subnet as your machine, select Automatically Obtain Server List. Otherwise, select Manually Enter a NIS+ Server; then, type the host name or IP address of the server into the Server Name or IP Address box.

7 Click OK. The NIS+ Domain Configuration area of the NIS+ Proper ties dialog box displays the name of the master server for the domain and the Secure RPC netname you are using to bind to the domain.

218


8 In the NIS+ Server Query Order area, set the server query order. The NIS+ Server Query Order area displays the list of available servers. The list of servers from top to bottom corresponds to the query order. To set the query order, do one of the following:

• To randomly target NIS+ servers during queries, select Use Random Server.

• To set a specific query order for a server, select the server from the list, and then click the Up or Down buttons at the right of the list to move the server to the correct position.

9 Click OK. The NIS+ Proper ties dialog box closes. The NIS+ service is configured for the specified profile.

Keylogin and the System ProfileCertain tasks involving NIS+ require user credentials. For example, you must supply user credentials if you want to connect to an NFS resource. You must also supply user credentials if you want to change your password in a NIS+ domain.

For more information on keylogin and NIS+ credentials, see Hummingbird Directory Services Help.

When you create a user profile, Hummingbird Directory Services runs keylogin based on the name and Secure RPC password you supply in the profile. It then stores the retrieved credential information locally. This information is available to any Hummingbird Connectivity application that needs to use your user credentials.

The system profile stores the credentials for your machine, not your user credentials. If you are using the system profile and you attempt a task that requires user credentials, Hummingbird Directory Services automatically runs keylogin on your behalf. In this case, Hummingbird Directory Services attempts to use your Windows user name and password as your NIS+ user name and Secure RPC password.

If this attempt fails and you have registered a user name and password using the nfs register command or the Connect As dialog box, Hummingbird Directory Services tries keylogin again with your registered credentials (Hummingbird NFS Maestro Client users only).

If the automatic keylogin fails, the NIS+ Keylogin dialog box opens to let you manually specify a user name and Secure RPC password for the NIS+ domain in the system profile.

219


Keylogin runs on a per-user basis. Once you have specified user credentials for the system profile, you do not need to supply this information again.

Binding to LDAP

Hummingbird Directory Services and Directory Services Explorer support LDAP domains that use one of the following schemas: RFC 2307, RFC2307AIX, or Active Directory with AD4UNIX/VAS extensions. To bind to a domain that does not adhere to any of the supported schemas, you can do either of the following:

• Customize your profile to reflect the nonstandard schema. For more information, see “Defining Custom Schemas” on page 234.

• Retrieve the profile from a Directory Service Agent (DSA) that is configured to return profile information about the domain. For more information, see “Retrieving Profiles from Directory Service Agents” on page 223.

These steps are described in detail in the following pages.

The basic procedure for binding to an LDAP is as follows:

1 Specify the information that defines the LDAP domain and the bind method you want to use.

2 Specify the credentials and authentication method you want to use to bind to domain.

3 Select the schema for the domain or, if necessary, configure the profile to reflect a nonstandard schema.

Note: If you are using the system profile, you can run keylogin explicitly to bind to NIS+ using specific credentials. You do not need to run keylogin if you are using the user profile. For more information, see “Running Keylogin” on page 247.

Note: If you configure the profile to retrieve profile information from a DSA, you do not need to continue with steps 2–3.

220


Specifying LDAP Domains and Bind MethodsThe first step in creating an LDAP profile is to specify the information that defines the LDAP domain and the bind method, including the following:

• the LDAP servers you want to target, their query order, and which servers (if any) act as Directory Service Agents for profile information

• the version of LDAP you want to use

• the search base for queries, the search timeout, and other search options

• the method for securing communication with the domain (SSL/TLS or none)

• the maximum time that the LDAP client attempts to bind to the domain

To specify an LDAP domain and bind method:


1 Open the LDAP Proper ties dialog box. The General page is selected by default.

221


2 In the LDAP Profile Name box, type the profile name for the domain (Directory Services Explorer only).

3 Specify the server(s) in the domain that you want to target. For each server, do the following:

a) On the General page, click Add.

Click the Default button to enter the default port numbers.

b) In the LDAP Server Configuration dialog box, specify the name of the server and the port numbers for the LDAP service and the secure LDAP service (using SSL/TLS). By default, the LDAP service listens for requests on port 389; the SSL/TLS service uses port 636.

A port number identifies a particular service on the server. Client requests to a server typically include a port number to identify which service should process the request.

c) To register the server as a Directory Service Agent for profile information, select This Server Stores Client Profiles.

To change the properties for a server, select it from the list and then click Properties.

d) Click OK. The LDAP Server Configuration dialog box closes and the name of the server you have added appears in the LDAP Servers area on the General page.

4 If you have added more than one server to the list, use the Up and Down buttons to change the position of selected servers in the list. The top-to-bottom order of servers in the list is their query order.


This option is available only if you have registered at least one server as a profile server.

• To use the profile stored in the domain, select Use Profile from Profile Server(s), and then click OK. The profile is retrieved from the first available DSA in the server list. Proceed to step 10.

• To create your own profile, or customize a loaded profile, proceed to the next step.

Note: If you have registered one or more servers as DSAs for profile information, you can view the stored profile by clicking Load Profile. The information for your profile, such as the authentication method and domain schema, appears in the LDAP Properties dialog box when you click the button. To clear the loaded profile, click Cancel.

222


For more information on certificates, see “Securing LDAP with SSL/TLS” on page 225.

6 To bind to the domain securely using the SSL/TLS protocol, select Use SSL Connection. Only LDAP version 3 supports SSL/TLS. To use SSL/TLS, you must first install a CA certificate.

For more information on LDAP search bases, see Hummingbird Directory Services Help.

7 In the Search Base box, type the search base for the directory information tree (for example, dc=abcxyz,dc=com). The search base and search options you specify apply to all servers listed in the LDAP Servers area.

8 Click Advanced. In the LDAP Advanced Options dialog box, open the Other page and then select the version of the LDAP protocol you want to use. If you use SSL/TLS authentication, you must use version 3. Most LDAP servers running version 3 also support version 2.

If you are not using SSL/TLS authentication and the server supports version 2 only, all LDAP queries made by you use the version 2 protocol (even if you specify version 3).

9 To specify additional search and bind options, open the Search page. For more information, see page 227.

10 In the LDAP Advanced Options dialog box, do one of the following:

• Click OK to complete the profile.

• Use the Security and Schema pages to define the authentication method and schema for the profile.

Retrieving Profiles from Directory Service AgentsIn LDAP, a Directory Service Agent (DSA) is a server that stores the directory information tree, in part or whole, for a given domain. LDAP clients, also known as Directory User Agents (DUAs) contact DSAs using LDAP to retrieve or modify domain information.

223


For more information about configuration profiles, see the Internet Draft “A Configuration Schema for LDAP Based Directory User Agents”.

Because different implementations of LDAP use different schemas, some LDAP domains store information about how the domain is configured. DUAs can retrieve this information to configure themselves to reflect the schema adopted by the domain. The configuration information includes the following attributes:

Attribute Description

attributeMap Specifies a mapping between an attribute defined by the client (the DUA) and an attribute defined in an alternative schema. This attribute lets you customize your profile to reflect the schema used by the domain.

authenticationMethod Specifies the default authentication method (None, Simple, or SASL/GSSAPI) for binding to the domain.

bindTimeLimit Specifies the maximum time in seconds that the client spends attempting to bind to the domain.

credentialLevel Specifies the type of credentials (Anonymous, Self, Proxy) the client uses for Simple authentication.

defaultSearchBase Specifies the search base DN for the profile.

defaultServerList Specifies the list of servers that support the domain.

defaultSearchScope Specifies the search scope (Base, Subtree, or One) for LDAP queries.

followReferrals Specifies whether LDAP queries follow referrals to other servers.

preferredServerList Specifies the list of preferred servers for LDAP queries.

profileTTL Specifies the expiration time (Time To Live) of the profile in seconds.

searchTimeLimit Specifies the maximum query time (in seconds) for LDAP queries.

224


To retrieve configuration information for your profile:

1 When you specify the servers for the domain, ensure that you identify which ones are DSAs for profile information: in the LDAP Server Configuration dialog box, select This Server Stores Client Profiles for each DSA.

2 On the General page of the LDAP Proper ties dialog box, select Use Profile from Profile Server(s). This option effectively makes your profile a DUA for profile information.

3 Click OK. Hummingbird Directory Services and Directory Services Explorer automatically update the profile with the configuration information from the first available DSA you specified.

Securing LDAP with SSL/TLSThe Transport Layer Security (TLS) protocol is an extension of SSL.

The Secure Socket Layer (SSL) protocol was developed by Netscape to secure communication over the Internet. The protocol provides a secure channel for client-server communication. The basis of SSL authentication is a digital certificate which one party sends to another to prove its identity. The certificate is issued by a third party, the Certificate Authority (CA), that both parties trust. LDAP version 3 supports SSL security.

Hummingbird Directory Services and Directory Services Explorer use server-side certificates, which authenticate an LDAP server to your machine. To use the server-side certificate from a given LDAP server, you must first retrieve a CA certificate from the root Certificate Authority used by the server. The CA certificate lets Hummingbird Connectivity applications (including Directory Services Explorer) authenticate the certificate sent from the LDAP server.

Contact your LDAP administrator for information about the applicable Certificate Authority. You can use most web browsers to download a CA certificate and save it on your machine.

Note: If you have set your profile as a DUA, Hummingbird Directory Services and Directory Services Explorer automatically refresh the profile whenever you try to bind to the domain after the expiration time defined by the profileTTL attribute.

225


Once you have retrieved the CA certificate, you need to install it using a version of Microsoft Internet Explorer that supports SSL/TLS. If you are using Internet Explorer to retrieve a certificate, you can install it directly during the download process.

SSL Requirements for Microsoft Active DirectoryIf you bind to a Microsoft Active Directory LDAP domain that is different from your Windows NT/2000 domain, you can change or synchronize your password in that domain only if you are using 128-bit SSL authentication. In this case, the LDAP server must have a server certificate for a 128-bit RSA connection and must support high (128-bit) encryption.

If you are installing Internet Explorer 5.5 on a Windows 2000 machine, you must also install the Windows 2000 High Encryption Pack to change the encryption level for the machine.

In addition to the requirements for the server, the version of Internet Explorer that you use to install the CA certificate must support 128-bit encryption. Internet Explorer versions 5.5 and higher automatically support 128-bit encryption. If you are not using one of these versions, you must either install a version that does support high encryption or upgrade your current version with the Microsoft Internet Explorer High Encryption Pack.

You can find more information about Microsoft’s encryption packs at the following site:

http://www.microsoft.com/windows/ie/downloads/recommended/128bit

Note: Before you can install an SSL certificate using Internet Explorer, you may need to update your Windows system. For more information, see article Q286158 in the Microsoft Product Support Services web site:

http://support.microsoft.com

226

http://support.microsoft.com

http://www.microsoft.com/windows/ie/downloads/recommended/128bit


Installing CA CertificatesAfter you have installed the certificate correctly, it appears in the Trusted Root Cer tification Authorities page of the Certificate Manager dialog box.

To install a CA certificate at download time (Internet Explorer only):

1 In the File Download dialog box, select Open This File From Its Current Location. Click OK. The Certificate dialog box opens.

2 On the General page, click Install Cer tificate. The Certificate Manager Import Wizard opens.

3 Follow the instructions in the wizard to install the certificate on your machine.

To install a CA certificate saved to disk:

1 Open Internet Explorer.

2 On the Tools menu, click Internet Options. The Internet Options dialog box opens.

3 Select the Content tab; then, click Certificates. The Certificate Manager dialog box opens.

4 Click Import. The Certificate Manager Import Wizard opens.

5 Follow the instructions in the wizard to install the certificate on your machine.

Setting LDAP Search and Bind OptionsUse the LDAP Advanced Options dialog box to set the following options:

Search Page

Search Timeout (Seconds)

Specifies the maximum query time for LDAP queries. If the service does not return any query results within the specified time, the query is aborted.

Bind Timeout (Seconds) Specifies the maximum time in seconds that the LDAP client spends attempting to bind to the LDAP domain.

227


Specifying Authentication Methods for LDAP ProfilesThe second step in setting up an LDAP profile is to specify the authentication method you want to use to bind to the domain and, if necessary, your authentication credentials (user name and password). The credentials you supply verify you as a legitimate client of the domain.

Maximum Number of Matches to Return

Specifies the maximum number of entries that an LDAP query returns. Type the number of matches into the box. Type zero (0) to specify no limit.

Follow Referrals Indicates that LDAP queries follow referrals to other servers. In LDAP, information can be distributed across multiple servers. Objects on one server may act as referrals to objects on another server. The target of the referral stores the actual information of the object. By following the referral, the query can retrieve the object information regardless of the network location of the object, but the query may take longer to process.

Search Scope: Base Indicates that LDAP queries begin at the search base for your profile and extend throughout the directory information tree until a match is found or the tree is exhausted. The search base is specified on the General page of the LDAP Properties dialog box.

Search Scope: Subtree Indicates that LDAP queries begin at the relevant subtree (container) in the directory information tree and extend throughout the subtree until a match is found or the subtree is exhausted.

Search Scope: One Indicates that LDAP queries begin at the relevant subtree in the directory information tree but do not extend beyond this container. (In other words, LDAP queries search a single level of the tree.)

Other Page

LDAP Version Specifies the version of LDAP for the profile. From the list, select the version of LDAP you want to use.

Search Page

228


Hummingbird Directory Services and Directory Services Explorer support the following options for LDAP authentication:

None Indicates that you are not sending any credentials to the server for authentication. This option effectively binds you to the server as an anonymous user. Anonymous users may not have access to all objects in the domain. By default, Microsoft Active Directory does not support anonymous user access to its containers.

Simple Sends your credentials to the server as is, with no encryption. You can send credentials for one or more of the following users:

• The Anonymous user.

• Yourself (using your own credentials). If you are binding to LDAP to retrieve NFS credentials for NFS Maestro Client, Hummingbird Directory Services uses one of the following credentials (in order of precedence):

a) the credentials you explicitly supply for the connection, or, if you do not specify any credentials,

b) the registered credentials (defined by the Administrator, or, if there are no Administrator-registered credentials, the credentials you have registered), or, if there are no registered credentials,

c) your Windows user account credentials

In all other cases, your Windows user account credentials are used.

• A proxy user (using a given user DN and password).

Warning! If you are not also using SSL/TLS authentication to secure the communication between you and the server, your credentials may be visible to any third party on the network. If you choose to use SSL/TLS, you must first retrieve a CA certificate from the same Certificate Authority that is used by the LDAP server. For more information, see “Securing LDAP with SSL/TLS” on page 225.

229


For more information on SASL/GSSAPI, see page 232.

SASL/GSSAPI Indicates that you are using the Simple Authentication and Security Layer (SASL) protocol and the GSSAPI authentication mechanism to authenticate yourself to the server. SASL/GSSAPI authentication is supported only for Active Directory domains. When you use this method to authenticate to an Active Directory domain, all LDAP transactions between you and the server are secured.

To specify an authentication method:

1 In the LDAP Properties dialog box, open the Security page.

2 From the Method list, select the authentication method you want to use to bind to the domain.

230


3 If you are using Simple authentication, do the following:

a) In the Credential Level Order area, select the check box for one or more of the credentials that you want to use (Anonymous, Self, Proxy).

If you want to use Proxy credentials, select Proxy, and in the Proxy Credentials area, specify the user DN and password for the proxy user.

b) To specify the order in which credentials are sent for authentication, select each credential and then click Up or Down to move the credential up or down the list. Repeat as necessary. The top-to-bottom order of credentials in the list corresponds to the order in which they are used for authentication.

The profile binds to the domain with the first successfully authenticated credential.

For more information on password verification methods, see page 232.

4 Specify a method for verifying your password:

• To verify passwords by comparing the encrypted version of your password in the LDAP domain against a one-way hash of your specified password, select Compare Crypted Values.

A hash function transforms a string of data into a number. The function is designed so that no two strings produce the same hash value. A one-way hash is an irreversible transformation: from the hash value, it is impossible to derive the original string.

• To verify passwords by initiating a bind operation, select Performing Bind Operation.

5 In the LDAP Advanced Options dialog box, do one of the following:

• Click OK to complete the profile.

• Use the Schema page to specify the schema for the profile.

Note: If the LDAP domain does not use default containers and attributes for user information, you must customize the profile to reflect the domain schema. For more information, see “Defining Custom Schemas” on page 234.

231


SASL AuthenticationFor more information on SASL, see RFC 2222.

The Simple Authentication and Security Layer (SASL) protocol provides a means for securing client-server communications. The protocol consists of an exchange between the client and the server in which the server sends a series of challenges and the client returns a series of responses to prove its identity. The protocol effectively adds a security layer to the existing communications protocol in operation between the client and server.

For more information on GSSAPI, see RFC 2078.

SASL supports several mechanisms that govern the exchange between the client and server. Hummingbird Directory Services and Directory Services Explorer support SASL using the GSSAPI mechanism. The Generic Security Service Application Program Interface (GSSAPI) provides a generic interface for other protocols requiring a security service. GSSAPI hides the implementation details of the security service from its users.

To use SASL authentication, you must meet the following requirements:

• your machine must be a part of the Active Directory LDAP domain

• your Windows user account must be the same as your account in the Active Directory LDAP domain

• you must log onto your machine using your user account

When you use SASL for authentication to an Active Directory LDAP domain, Hummingbird Directory Services and Directory Services Explorer automatically use the credentials for your Windows account. You do not need to specify additional credentials.

Password Verification MethodsWhen you use LDAP as your directory service, you can specify a password verification method. The method applies whenever you attempt to do the following:

• Change your password in an LDAP domain. In this case, Directory Services Explorer verifies your password before changing the password.

• Connect to an NFS resource using NFS Maestro Client. In this case, Hummingbird Directory Services verifies your password before the client can connect.

232


You can select one of the following verification methods:

Specifying Schemas for LDAP ProfilesThe third step in setting up an LDAP profile is to specify the schema used by the LDAP domain. Hummingbird Directory Services and Directory Services Explorer automatically support domains that adhere to one of the following schemas:

• RFC 2307

• RFC2307AIX

• Active Directory with AD4UNIX/VAS extensions

To specify a supported schema for your profile:

1 In the LDAP Properties dialog box, open the Schema page.

2 From the Type list, select the schema. Click OK to apply your selection.

Method Description

Compare Crypted Values Performs a one-way hash of the supplied password and compares it with the encrypted password stored in your user account object in the LDAP domain. This verification method is similar to authentication using PAM_UNIX.

Perform Bind Operation Attempts to bind to the LDAP domain using the supplied password. If the bind operation succeeds, then the supplied password is verified. This verification method is similar to authentication using PAM_LDAP.

233


Defining Custom SchemasFor more information on these components, see Hummingbird Directory Services Help.

If the domain you want to bind to uses a nonstandard LDAP schema, you can customize the following components of your profile to reflect the schema:

Class Names for Common Objects The classes that represent the User, Group, Policy, Automount, Host, Network, and RPC objects in the domain. Each class specifies the name and type of the attributes that make up the object. For example, in the RFC 2307 schema, the User object is defined by the posixAccount class. A nonstandard schema may use different classes to define these objects.

DNs for Common Objects The locations for the objects in the directory information tree. Each object is an LDAP container. The distinguished name (DN) of the container specifies its position in the tree. For example, the following DN specifies the location of the people container in a domain called abcd.com:

ou=people,dc=abcd,dc=com

The people container is the User object in the RFC 2307 schema. A nonstandard schema may locate the object in a different position and under a different container name in the tree.

User Attribute Names The names of attributes in the User container. Each entry in this container stores the account information for one user. If you need to supply authentication credentials when you bind to an LDAP domain, ensure that your profile defines the correct attribute names for the User container.

Contact your LDAP administrator to determine what customizations are required to configure your profile for the domain. The customizations you make can affect other Hummingbird Connectivity applications. For example, LDAP domains store automount information according to a specific set of attributes. If you want to use the Directory Service Automounts container of the network component in NFS Maestro Client, you must specify which classes define the automount information for the LDAP domain you are using.

234


To customize your profile for a nonstandard schema:

1 In the LDAP Properties dialog box, open the Schema page.

2 If the nonstandard schema is similar to a supported schema, select the supported schema from the Type list. The page updates with the correct settings for the selected schema.

3 From the Type list, select Manual.

For more information on the listed objects, see Hummingbird Directory Services Help.

4 For each object listed in the Account Object Definitions and Network Object Definitions areas, select the correct class that defines the object in the schema. Some objects are defined by more than one class.

5 Click Advanced.

6 On the Distinguished Names page of the LDAP Advanced Schema dialog box, specify the directory information tree location of each of the listed objects. The location of the object in the tree is the same as the distinguished name (DN) of the container. For each container, you can either select from a set of common DNs or type a specific DN.

235


7 Open the Attributes page. For any attribute in the User object that has a nonstandard name, select the name from the list of common names or type the name directly.

8 Click OK to close the LDAP Advanced Schema dialog box. In the LDAP Properties dialog box, click OK to complete the profile.

Exploring Directory Services

The following sections describe the tasks you can perform using Directory Services Explorer.

Querying Directory Service ObjectsFor more information on directory service objects, see Directory Services Explorer Help.

When you run a query, you can retrieve the contents of an entire object (for example, a NIS map, NIS+ table, or LDAP directory) or just the particular entry that matches a certain key value.

To retrieve the entire contents of an object:

1 From the drop-down list box of Directory Services Explorer, select the service you want to query. The left pane displays the profiles you have created for that service.

2 Click the plus sign to the left of an object to display the objects it contains.

3 Repeat step 2 until you find the object you want to query.

4 Click the object. The right pane displays the contents of the object.

Note: If you want to save the results of your query to a file, you must configure the file output settings of Directory Services Explorer prior to running the query. For more information, see “Saving Query Results” on page 238.

236


To retrieve a specific entry from a selected object:

1 Open the Select Entries dialog box using one of the following methods:

• Right-click the selected object; on the pop-up menu that appears, click Select Table Entries.

• Click the Select Table Entries button on the toolbar.

• On the Object menu, click Select Table Entries.

The Select Entries dialog box opens.

2 In the Column Restrictions area, type the desired key value or values into the Value column.

For example, if you have selected the hosts.byname map and you want to retrieve the IP address for the host called jane01, you would type jane01 into the Value column. (The hosts.byname map uses host names as its key.)

3 Click OK. Directory Services Explorer forwards your query to the domain server and displays the results (including any error messages).

Sorting Query ResultsYou can sort the results of a query returned by Directory Services Explorer, either in ascending or descending order, using any column as the sort key.

When you run a query, the results appear in tabular form in the right pane of Directory Services Explorer. The format of the table depends on the service.

NIS/NIS+ Each row in the table corresponds to an entry in the queried object. Each column corresponds to an attribute of the object.

LDAP Each row in the table corresponds to an attribute of the queried object. All attributes of the queried object appear in the first column.

Note: Queries based on key values are case sensitive. The key value you supply must be an exact match for the corresponding value in the object. You cannot specify a key value using pattern matching expressions.

237


To sort the results of a successful query:

Click the title bar at the top of the column you want to use as your sort key. The first time you click a given title bar, the values in the column sort in ascending order from the top of column to the bottom. The second time you click the title bar, the values sort in the reverse order. Thereafter, successive clicks alternate the sort order. To return the results to their original, unsorted order, re-run the query.

Saving Query ResultsYou can configure Directory Services Explorer to save your query results to a text file. You can then use this file to copy and paste directory service data into other applications. There are two output methods for building the file:

• Append—Adds successive query results to the end of the file; does not overwrite existing results in the file.

• Replace—Overwrites existing results with the current query results.

You must specify the name of the file and the output method before you can save any queries.

To specify an output file:

1 On the File menu of Directory Services Explorer, select Settings. The Directory Services Explorer Settings dialog box opens.

2 In the Output File area, select Output to File.

3 In the File Name box, type the name of the output file. You must supply an absolute path name for the file, including the drive letter (for example, c:\temp\results.txt). You must have permission to write to the specified path.


• To append query results to the output file, select Append.

• To overwrite the existing output file with the current query results, select Replace.

5 Click OK. The Directory Services Explorer Settings dialog box closes. The specified file stores the results from any subsequent queries.

238


Viewing Object PropertiesDirectory Services Explorer lets you view the contents of directory service objects as well as the properties of those objects. Depending upon the service and the type of object, the properties you can examine include the following:

• the name of the object

• the server that stores the object

• the access rights for the object, specified as a permission string

To view the properties of an object:

1 In the left pane of Directory Services Explorer, select the object.

2 Display the properties for the object using one of the following methods:

• Right-click the object; on the pop-up menu that appears, click Properties.

• On the Object menu, click Properties.

• Click the Proper ties button on the toolbar.

The properties of the object appear in a Proper ties dialog box named after the object.

Modifying ProfilesOnce you have created a profile, you can modify its properties at any time. You can also delete a profile.

To modify a profile in Directory Services Explorer:

1 On the File menu, click Settings. The Directory Services Explorer Settings dialog box opens.

2 From the Directory Service list, select the service whose profile you want to change. The Profile box lists the profiles you have created for the selected service.

3 In the Profile box, select the profile you want to modify. Click Properties. The Properties box for the selected service opens.

239


4 In the Properties dialog box, modify the domain information for the selected service. Click OK. The Properties dialog box closes.

5 In the Directory Services Explorer Settings dialog box, click OK. The dialog box closes. The specified profile updates according to your modifications.

To delete a profile in Directory Services Explorer:

1 Follow steps 1–2 in the previous procedure.

2 In the Profile box, select the profile you want to delete. Click Remove, and then click OK. The Directory Services Explorer Settings dialog box closes.

Changing Domain PasswordsUsing Directory Services Explorer, you can change your password for a selected service and domain. Specifically, you can change the entries for your account in the passwd.byname and passwd.byuid NIS maps, the passwd NIS+ table, and the LDAP entry for your user name. If you change your password in a NIS+ domain, Directory Services Explorer changes your Secure RPC password to the new value as well.

To change your password, you must meet the following requirements:

• You must have an account on the server or network on which a service runs in order to update password objects.

• If you are changing your password in an LDAP domain, you must change it for each of your profiles that bind to that domain.

• If you bind to a Microsoft Active Directory LDAP domain, you can change your password only if you are using 128-bit SSL/TLS authentication. For more information, see “SSL Requirements for Microsoft Active Directory” on page 226.

Warning! If you bind to an Active Directory LDAP domain that is the same as your Windows NT/2000+ domain, you will change your Windows password when you change your LDAP password.

240


To update your password information for a given domain:

1 Open Directory Services Explorer.

2 On the File menu of Directory Services Explorer, select Change User Password. The Change User Password dialog box opens.

3 From the Directory Service list, select the service that controls the domain. The Profile Name box lists the profiles you have created for the selected service.

4 In the Profile Name box, select the profile that specifies the domain. Click Change Password. The Change Password dialog box opens.

5 In the User Name box, type your user name.

6 In the Old Password box, type your old password for the domain.

7 In the New Password and Confirm New Password boxes, type your new password.

8 Click OK. If you are updating your password in a NIS+ domain and your domain password is not the same as your Secure RPC password, you must enter your Secure RPC password in the Secure RPC Password box; then, click OK again. The Change Password dialog box closes.

9 In the Change User Password dialog box, click Done. The dialog box closes. Directory Services Explorer updates your password (and Secure RPC password, if applicable) for the specified domain.

Note: The new information may take several minutes to propagate across supplementary servers in the domain.

If you have selected a replica server as the first server in the NIS+ query order, the new password information must first pass up to the master server before propagating across the other replica servers.

241


Specifying Name Mapping Servers

For more information on mapping names, see NFS Maestro Name Mapping Server Help.

NFS Maestro Name Mapping Server lets you map user and group names from Windows domains to their corresponding values in an NFS name space. If name mapping servers are available on your network, you can specify which servers you want to use for Hummingbird Connectivity applications. You can specify up to two servers: applications target the primary server first, if it is available; otherwise, applications target the secondary server.

To specify name mapping servers:


2 Click the Name Mapping tab.

3 On the Name Mapping page, do one of the following:

• If there is a DHCP server on your network, and you want to use it to retrieve the names of name mapping servers, click DHCP. Hummingbird Directory Services queries the DHCP server to retrieve the server names and then presents the result in the Primary and Secondary boxes.

• Type the name of the primary server in the Primary box. If you want to specify a secondary server, type its name in the Secondary box. You can specify a secondary server only if you have specified a primary server.

4 Click OK.

242


Configuring Directory Services

The following sections describe how you can configure directory services for Hummingbird Connectivity applications.

Selecting ServicesAfter you have established a user or system profile using Hummingbird Directory Services, you can select any service that has a domain specified in that profile. Any queries made by Hummingbird Connectivity applications target the domain for the selected service.

To select a service:


2 In the Directory Services Settings area, select the profile type you want to use (User Settings or System Settings).

3 From the Directory Service list, select the service you want to use. To specify no service, do one of the following:

• If you have installed NFS Maestro Client on your system, select HCLNFSD/PCNFSD with DNS. NFS Maestro Client uses the authentication agent you have specified in the HCLNFSD/PCSNFSD Properties dialog box to retrieve AUTH_SYS credentials.

• If you have not installed NFS Maestro Client on your system, select DNS.

4 Click OK. The Hummingbird Directory Services Proper ties dialog box closes.

Note: You do not need to select HCLNFSD/PCNFSD with DNS to use hclnfsd/pcnfsd for authentication: select any directory service (NIS/NIS+/LDAP) from the Directory Service list; then, in the Authentication area, select HCLNFSD/PCNFSD Only For AUTH_SYS Authentication. In this case, NFS Maestro Client uses the authentication agent you have specified in the HCLNFSD/PCSNFSD Properties dialog box, regardless of the currently selected directory service.

243


Modifying ProfilesOnce you have created a user or system profile, you can modify its properties at any time. You can also remove the bind information for a particular service.

To modify a profile:


2 In the Directory Services Settings area, select the profile you want to change (User Settings or System Settings).

3 From the Directory Service list, select the directory service whose domain information you want to change.

4 Click Proper ties. The Properties dialog box for the selected service opens.

5 In the Properties dialog box, modify the domain information for the selected service as necessary. Click OK. The Properties dialog box closes.

6 In the Hummingbird Directory Services Proper ties dialog box, click OK. The dialog box closes. The specified profile updates according to your modifications.

To remove a directory service from a profile:

1 Follow steps 1–3 in the previous procedure.

2 Click Reset.

3 From the Directory Service list, select a service that has a domain specified for it. Click OK. The Hummingbird Directory Services Properties dialog box closes. The specified service has been removed from the profile.

Note: You must be the administrator for the machine to modify the system profile or remove a service from it.

244


Disabling User ProfilesThe administrator for the machine can disable all existing user profiles (and prevent new ones from being created). In this case, all users must bind to directory service domains using the system profile.

To disable user profiles:

1 In the Hummingbird Directory Services Proper ties dialog box, select the Disable User Settings for All Users check box.

2 Click OK. The Hummingbird Directory Services Proper ties dialog box closes. Users can no longer create or bind to domains using a user profile.

Specifying Host Lookup ServicesHummingbird Directory Services lets you specify the target service for host name queries. Hummingbird Connectivity applications that need to resolve an IP address into a host name (or vice versa) send their queries to the selected target.

To specify a target for host name queries:


2 In the Directory Services Settings area, select the profile you want to use (User Settings or System Settings). If you want to target a directory service, select it from the Directory Service list. (The domain for this service must be specified in the selected profile.)

Note: If user profiles have been disabled, you can run keylogin to bind to NIS+ using your user NIS+ credentials. For more information, see “Running Keylogin” on page 247.

Note: Exceed users cannot use Hummingbird Directory Services to specify a host lookup service.

245


3 In the Host Name Lookup Using area, do one of the following:

• To send queries only to the Domain Name Service (DNS), select DNS.

• To send queries only to the service selected in the Directory Service list, select Directory Services.

• To send queries to both services, select Directory Services and DNS. If you select this option, you can also specify a query order by selecting the Check DNS First check box.

4 Click OK to apply your settings.

Synchronizing PasswordsYou can use Hummingbird Directory Services to automatically synchronize your password for a given domain with your Windows password. The domain is specified in the currently selected profile for the currently selected directory service. Anytime you change your Windows password, your password in the specified domain changes to the same value.

If you bind to a Microsoft Active Directory LDAP domain, you can synchronize your password only if the following conditions are true:

For more information, see “SSL Requirements for Microsoft Active Directory” on page 226.

• You are using 128-bit SSL/TLS authentication.

• The LDAP domain is not the same as your Windows NT/2000 domain. If it is, your LDAP password automatically updates whenever you change your Windows password.

To synchronize your passwords:

1 In the Hummingbird Directory Services Proper ties dialog box, select the Synchronize Windows Network Password check box.

2 Click OK.

Note: Users of NFS Maestro Server and Exceed cannot use Hummingbird Directory Services to synchronize passwords.

246


Running KeyloginYou can run the keylogin function to bind to NIS+ using specific user credentials. You need to do so only if you are using the system profile for NIS+ and you want to perform a task that requires user credentials.

To run keylogin:

1 Open the NIS+ Proper ties dialog box. Click Keylogin. The NIS+ Keylogin dialog box opens.

2 Type your user name for the NIS+ domain into the User Name box.

3 Type your Secure RPC password into the Secure RPC Password box.

4 Click OK. The NIS+ Keylogin dialog box closes. Hummingbird Directory Services uses the specified name and password to generate your DES credentials.

You can also run keylogin using the keylogin command line application. For more information, see Hummingbird Directory Services Help.

Running Command Line ApplicationsFor more information on the command line applications, see Hummingbird Directory Services Help.

The Hummingbird Directory Services command line applications let you browse and access directory service objects. By default, the applications target the domains specified in the currently selected profile. The following table summarizes the available applications.

Command Description

chkey Changes your private and public key pair or your Secure RPC password in a given NIS+ domain.

keylogin Retrieves and decrypts your secret key from the NIS+ cred table, and then stores it locally.

niscat Displays the contents of a given NIS+ table.

nisls Lists the contents of a given NIS+ domain.

nismatch Returns the entries in a given NIS+ table that match specific key values.

247


nispasswd Changes or displays your password information in a given NIS+ domain.

ypcat Displays the contents of a given NIS map.

ypmatch Returns the entries in a given NIS map that match a specific key value.

yppasswd Changes your password information in a given NIS domain.

ypwhich Displays the name of the master server for a given NIS domain or the NIS server for a given host.

ldappasswd Changes your password in a given LDAP domain.

Command Description

248

Appendix A

Troubleshooting

Installation Troubleshooting 251

Exceed Diagnostics 254Troubleshooting Xstart 254Logs and Trace Operations 255

Appendix A: Troubleshooting

Installation Troubleshooting

The following are common installation issues and questions along with suggested solutions. For further assistance with troubleshooting issues, contact Hummingbird Technical Support.

Another instance of Hummingbird Setup Wizard is running.Solutions:

• An information dialog box informs you that an instance of Setup Wizard is already running. Confirm whether the new instance can continue.

• If a product is not currently being installed, you can ignore this error message and run:

Setup /v"HCL_OVERRIDE_INSTANCE=1"

The message also appears if a non-privileged user tries to uninstall a product installed for “All Users” of the computer. In this case, the setup parameter does not work since only an Administrator of the computer can uninstall the product.

• This error message may display if installer is unable to remove a key created by the Setup Wizard. This may be because Setup Wizard encountered problems during a previous installation and the key was not removed.

Delete the following key from the registry:

HKEY_CURRENT_USER/Software/Hummingbird/Connectivity/version/installer/UserIni/InstallActive=1

251


The feature you are trying to install is on a network resource that is unavailable.Solutions:

• Click OK in the warning dialog box and try again.

• Enter an alternate path to the folder containing the installation package “Hummingbird Product .msi”. Run the install again and select Repair.

• Use Media Location Manager (part of the Administrator’s Toolkit feature) to specify an additional location for the product installation package. This lets Windows Installer find the required resource.

Patch - Sourcedir not found (when trying to install patch).This means the source files are unavailable. When installing a patch, you need to have the source from which you installed.

Solution: The original product CD must be in the drive. If necessary, use Media Location Manager (part of the Administrator’s Toolkit feature) to specify a location for the source files.

After installation the software does not work—services are not starting and/or files are missing.Solution: Ensure the Administrator account is used to perform the installation. For Windows NT/2000, installing HostExplorer and NFS Maestro Client requires Administrator privilege. Installing Exceed requires elevated privilege (that is, a user who is a member of the Administrator group).

When trying to install the product, a message says I must uninstall the product.Solution: You have version 7.0 of the product installed. The upgrade process requires the original version 7.0 source files to install a later version of the product. If necessary, use Media Location Manager (part of the Administrator’s Toolkit feature) to specify a location for the source files.

252


Are there other command line options for Msiexec?For more detailed information about Msiexec command line options, see the Windows Installer documentation in the MSDN online Library at msdn.microsoft.com or on CD-ROM via subscription.

The following are command line options for Msiexec:

Option Meaning

/i Package|ProductCode Installs or configures a product.

/f Package|ProductCode Repairs a product. For more information about various flags available for this option, see the MSDN Library.

/a Package An administrative installation option that installs a product on the network.

/x Package|ProductCode Uninstalls a product.

/j Advertises a product. For more information about various flags available for this option, see the MSDN Library.

/L Logfile Specifies path to log file and the flags indicate which information to log. For more information about various flags available for this option, see the MSDN Library.

/m filename Generates an SMS status .mif file. Use this option in conjunction with the install (-i), remove (-x), administrative installation (-a), or reinstall (-f) options. For more information about this option, see the MSDN Library.

/p PatchPackage Applies a patch. For more information about this option, see the MSDN Library.

/q Sets user interface level. For more information about various flags available for this option, see the MSDN Library.

/?

/h

Displays copyright information for the Windows Installer.

/y module Calls the system API DllRegisterServer to self-register modules. For more information about this option, see the MSDN Library.

/z module Calls the system API DllUnRegisterServer to unregister modules. For more information about this option, see the MSDN Library.

253


How do you create an installation log file?To generate a log file, users should run the following command:

setup /v"/1*v C:\install_log.txt"

where C:\ is the path to plaintext file install_log.txt.

Exceed Diagnostics

To find out tips for using Exceed, or to find out how other users solve common problems, join the Exceed User’s Group. See page iv for details.

This section describes possible solutions to problems that you might encounter while using Exceed. If you have problems, there are two main ways to determine the cause:

• Diagnosing using progress messages—see details below.

• Diagnosing using logs and trace operations—see details beginning on page 255.

Troubleshooting Xstart

Progress MessagesTo open the Other Settings dialog box, click Other in the Settings area of Xstart.

Usually, the first step in troubleshooting a connection is displaying system progress messages. On the Connection tab (Other Settings dialog box), select Show progress and Show host reply in the Status/Debug area.

• The Show progress option shows what is happening while you try to connect and start an application.

• The Show host reply option displays a summary of the startup information, the macros you used displayed in expanded form, and what reply was given by the host or application.

These options should help you determine the problem. The following sections detail common connection error messages.

Correct User Name and Password—System Does Not Connect If the host does not return an Invalid Name or Password message, there may be something wrong with the communications link. Maybe the host is not running or it does not support REXEC or RSH. There may also be a problem with your transport setup or configuration.

254


Host Returns Invalid Name or Password Message If you receive an Invalid Name or Password message but the system is connecting, there may be something wrong with either the syntax or the parameters of the command you typed in the Xstart Command box. You may need to type PATH or DISPLAY specifications on the command line.

Xstart Connects But the Client Does Not Start The client may not be getting enough time to start before the initial Xstart socket closes down. In the Other Settings dialog box (in Xstart, click Other in the Settings area), set the Close box in the Timeouts area to -1 (minus one), select the Show host reply option, then click OK.

This setting keeps the first socket open even after the client socket is established. It also shows all host-generated messages in a host reply window that may give you details about what is happening. If the client seems to start properly, try different values in the Close box until you find a value that gives the client enough time to start and then closes down the initial socket.

The Client is Not Authorized to Run on the Server To verify authorization, in the Xconfig Troubleshooting dialog box select View. In the Current Log Files dialog box, view the Exceed.log file and check for errors. To fix a problem with permissions, start Xconfig. In the Security dialog box, edit the Host Access Control List file (select File, browse if necessary, then click Edit). You may have to also edit the file (if it exists and if the option is enabled) indicated in the Enable User Access Control List area.

Logs and Trace OperationsExceed comes with two main tools for troubleshooting using logs and trace operations: Troubleshooting and Tranport Monitor.

Troubleshooting the Exceed X serverUse the Troubleshooting application in Xconfig to view the log file, to set what information is recorded in the log file, and to enable tracing. There are two main areas of active troubleshooting available with this application.

Troubleshooting

255


The first area lets you log information into a file for later inspection. You can log Font Open requests, the initial settings of the WM_COMMAND and WM_NAME properties on InputOutput root level windows and all OpenGL requests. You can also generate a security audit in the log file using Xweb Info Logging.

The second area is known as tracing. Tracing records all protocol traffic, between the Exceed X server and the host to a binary file. Options in Xconfig troubleshooting can help with the trace. For example, you can turn on tracing as soon as the Exceed X server starts, which means that the dialog with the first X client is recorded. You can also set Slow Trace in the Xconfig Troubleshooting dialog box which writes all information directly to the file without buffering any of the data. This is helpful if you are tracing a situation where the Exceed X server crashes because any buffered information would be lost.

The trace stops when the Exceed X server terminates. If you turned tracing on by clicking Trace on the Exceed X server File menu, you can terminate tracing by selecting Trace again. If tracing was turned on in the Troubleshooting dialog box, you should clear the Trace Initially On option as soon as possible. Otherwise, whenever the Exceed X server is restarted, tracing begins again.

For more information on Xdis, see the Help.

After the system performs a trace, disassemble the trace file to read it as a text file in Notepad. Xdis performs the disassembly process for you and lets you filter the data content of the disassembly.

Note: OpenGL support requires Exceed 3D. OpenGL is an industry-standard three-dimensional graphics software interface. It lets you create interactive programs that produce still or animated 3D color objects, with shading, lighting, and other effects. GLX is the X Window System extension which implements OpenGL.

Warning! Tracing creates large disk files on your system, and can impair Exceed X server performance. Therefore, use tracing only when you are troubleshooting a problem.

256


Transport MonitorThe Transport Monitor application (in the Exceed Tools folder) lets you monitor network connections by displaying all current connection activity. Use it to locate connections that are frozen. After you close a connection, the Transport Monitor should reflect this change. If the Transport Monitor continues to display a connection you have closed, then the connection is frozen.

257

Appendix B

Connectivity Applications

Accessories 261

Administrative Tools 262

HostExplorer 265

Hummingbird FTP 265

Appendix B: Connectivity Applications

Accessories

To quickly locate the help for an accessory, open the application and click Help from within the application.

Classic FTP This application lets you connect to a remote FTP server and transfer files between computers. FTP is only supported under TCP/IP transports. You cannot use this application with DECnet or IPX/SPX. A server implementation of the FTP protocol must run on the remote computer to allow for FTP communication. The remote computer is the FTP server (host), and the PC running Classic FTP is the FTP client.

Directory Services This application lets you configure the NIS, NIS+, and LDAP settings for Hummingbird Connectivity applications. All directory service queries made by Hummingbird Connectivity applications target the domains specified and selected by you. Hummingbird Directory Services also lets you synchronize your Windows and UNIX passwords and select a target service for host name resolution.

Directory Services Explorer This application lets you browse NIS, NIS+, and LDAP directory services without leaving the familiar Windows environment. Using Directory Services Explorer, you can bind your machine to multiple domains simultaneously, browse object contents and properties, run selective or global queries, and change your password in a directory service domain.

File Converter This application translates line feed control characters (also known as carriage return characters) between DOS and UNIX formats.

Hummingbird Basic This is a command language included with Hummingbird products. Hummingbird Basic can be used to create scripts for frequently performed tasks that you would like to automate. For more information, see the Hummingbird Basic Language Programmer’s Guide.

LPQ (Line Printer Query) This application is used to return the status of the print queue on either a UNIX system or another PC running a line-printer daemon.

261


LPR (Line Printer Requester) This application lets you print PC files to any host on a TCP/IP network running LPD. The LPR window displays a separate window for each printer queue to which you are connected. For more information, see the LPR help.

Network Time This application lets you synchronize the time on your PC with the Network Time Server.

NSLookup This application finds and displays information about hosts in a domain.

Ping This is a diagnostic tool that lets you quickly check the integrity of a network communications path and your TCP/IP configuration. Ping sends Internet Control Message Protocol (ICMP) echo requests to specified machines and displays the response in graphical form.

Quick Script Editor This application is a graphical development environment in which you can create and modify HostExplorer and FTP Quick Scripts. These scripts are made up of commands that help to automate tedious and repetitive tasks.

Remote Tools This application is an integrated version of several UNIX commands—Remote Shell, Remote Exec, Remote Copy (RSH), and Remote Copy (REXEC). You can execute commands and copy files to or from other machines on the network using the RSH and REXEC protocols.

Traceroute This application shows the route that packets take to the host. It lets you test, troubleshoot, and manage network connections and find the route used to connect to a specific host.

Administrative Tools

Deployment Packager Deployment Packager installs as part of Host Access Services. This application is an administrative tool that administrators can use to create and edit custom Package Assembly (.dpa) files, which define how and where deployment package (.dpf) files are deployed onto remote desktops. The deployment packages contain extra documents, data, and applications that administrators want to deploy along with the HostExplorer Deployment Wizard product.

262


Deployment Wizard Deployment Wizard installs as part of Host Access Services. With this wizard, you can create a web-deployable installation of HostExplorer, FTP for Windows Explorer and Connectivity Secure Shell for end users, complete with an automatic connection to a host. This feature leverages the capabilities of the modular HostExplorer architecture to give administrators more control over managing user’s desktops while reducing the amount of resources required to maintain these desktops.

Files and Settings Transfer Wizard This application lets you backup, restore, and migrate Hummingbird Connectivity product settings using .humsft files. Using this file, you can then export and import these settings to and from other host machines.

HostExplorer Management Console HostExplorer Management Console is an administrative, feature-lockdown tool. With it, you can specify which HostExplorer menu options you want to make available for end users. By default, all menu options are available.

HostExplorer Print Services Console HostExplorer Print Services installs as part of Host Access Services. This application is a server-based, scalable printing solution that lets you distribute reports from host computers to any LAN (local area network) printer in your enterprise network.

HTTP Proxy Server HostExplorer HTTP Proxy provides HostExplorer users access to hosts residing behind corporate firewalls with the benefit of and without breaching security features of the firewall. You can install this component from the Extras folder on the Hummingbird product CD.

Hummingbird InetD InetD is a super daemon that lets you enable and disable various daemon services through a single application. It determines the network services to which your PC responds when a client makes a network request. In a Windows 98/2000 environment, InetD runs automatically when placed in the Startup folder. The Startup folder is the usual location for InetD.

Hummingbird Update You can use Hummingbird Update to install the latest patch to your product. For more information, see the installation chapter.

Index Page Wizard Index Page Wizard installs as part of Host Access Services. This wizard lets you create or edit HTML indexes that contain links to multiple projects on a single web page.

263


Language Chooser Hummingbird Connectivity Language Chooser lets you specify the user interface language for Hummingbird Connectivity applications. The language you select will be used in Connectivity menus and dialog boxes.

Media Location Manager This application lets you manage your Windows Installer Media Source locations.

Metering Client Settings This application is a component of Hummingbird Metering Server. You can use it to configure metering client settings, which are used to establish communication between a metering server and its metering clients for a particular host machine.

Metering Server Hummingbird Connectivity products are now equipped with license metering capabilities. Metering Server is a reporting tool that lets administrators track the number of Hummingbird licenses deployed in their organization. You can install this component from the Extras folder on the Hummingbird product CD.

Proxy Server Console Hummingbird Proxy Server is a general proxy engine that lets you proxy emulation sessions. Proxy Server is composed of two components: a) the proxy engine, which is installed as a service on your workstation, and b) the proxy console, which lets you configure and monitor the proxy service. A shortcut to the Proxy Console is installed when you install the Proxy Server. Proxy Server Console installs as part of Host Access Services.

Sconfig Sconfig is a wizard that lets you customize the installation of software on local and network machines. With Sconfig, you can configure installations in the following ways:

• Customize the folders installed by Setup.

• Tailor the list of applications or components to be installed. You can alter the list to limit the functionality available to users or to optimize the use of disk space.

• Simplify user input during the installation by pre-selecting information, such as the names of the directories where the software is installed.

For more information on Sconfig, see the “Advanced Installation” chapter.

264


HostExplorer

3270 This application emulates an IBM mainframe (including 3179G, 3472G, 3278, and 3279 models), runs 3270 applications, and transfers files between a host machine and your PC using the IND$FILE file transfer application.

5250 This application emulates IBM AS/400 sessions and runs 5250 applications.

5250 Data Transfer Wizard This is a new HostExplorer component that lets you transfer data between a PC and an AS/400 host. If you transfer a file from an AS/400 host to your PC, you can specify standard SQL statements to execute in the file.

Macro and Profile Converter This utility lets you convert WallData Rumba or Attachmate Extra! macros into Hummingbird Basic macros and Attachmate Extra! profiles into HostExplorer session profiles.

VT This application emulates the DEC VT420 video terminal and includes support for VT52, VT100, VT101, VT102, VT220, VT320, VT420, ANSI, SCO ANSI, IBM 3151, and Linux Console.

WyseTerm This is a terminal emulator that emulates Wyse-50 and Wyse-60 terminals.

Hummingbird FTP

This application is a client implementation of the File Transfer Protocol (FTP). It lets you transfer both text (ASCII) and image (binary) files between your PC and a remote computer running a server implementation of FTP. You can also use it to perform file and directory management on your PC and a remote computer. For more information, see the HostExplorer User’s Guide.

265

Appendix C

HWM

A Quick Tour of HWM 269

The Virtual Desktop 271

HWM Configuration File 272Formatting Rules 272

Functions 274

Statements 275Virtual Desktop 276Font Statements 279Window Statements 279Color Statements 280Icon Manager Statements 281Menu Definitions 282Mouse Button Bindings 284Preprocessor Statements 286

Appendix C: HWM

This appendix describes how to use the Hummingbird local, Motif-like window manager, HWM. Like host-based window managers, HWM provides a graphical interface you can use to start and exit clients as well as position and iconify the windows on your display. Unlike other window managers, which run on the host and use the network for window management function, HWM is a local X client that runs on your PC. Running locally speeds up window management functions while reducing network traffic.

To start HWM, double-click the HWM icon in the Exceed Tools folder. Depending on how you configured HWM, the Virtual Desktop and/or the Icon Manager display.

A Quick Tour of HWM

This section briefly describes the HWM menus.

System menu Contains most of the HWM commands. In Single Window mode, display this menu by clicking the left mouse button anywhere in the X server window background. If the cursor is in a client window, you can also display this menu by holding down the Alt key and clicking the left mouse button.

For more information, see “Configuring Window Mode” on page 168.

In Multiple Window mode, displaying the System menu when you click the Windows desktop requires certain options selected. Open Xconfig, click Screen Definition in Classic View (or click Display and Video in Category View) and click Advanced. The Multiple Window Mode Advanced dialog box opens. Do one of the following:

• Select Full Support from the Root Drawing drop-down list and click OK.

• Select either Background Only or None from the Root Drawing drop-down list, select Root Mouse Actions to X, and then click OK. Alternatively, you can select one of the Root Drawing options (and click OK), and then click Root Mouse Actions to X on the Exceed X server toolbar.

Note: You can run HWM either when the X server is operating in Single Window mode, or in Multiple Window mode when configured for X or Default to Native Window Manager.

269


The System menu includes standard functions that let you raise a window, circulate a window up and down, refresh the display, and kill a client.

The System menu also contains the commands and submenus discussed below.

Window Ops menu Contains commands that let you iconify, move, resize, raise, lower, zoom/unzoom, refresh, and close a window. You can display this menu by choosing it from the System menu or by clicking Window Ops in the client window.

When you select a Window Ops command from the client window, the operation takes place on the client. When you select a Window Ops command from the System menu, the operation takes place on the next client that you click.

Desktop Settings menu Contains commands that show or hide the Virtual Desktop, the Icon Manager, or any X clients displayed as icons.

For more information about Local Commands or adding X clients to the X Commands menu, see the examples under “Active Functions” on page 283.

Local Commands menu Contains commands to open Xconfig, Xstart, or open Hwmcfg.src for editing in Notepad.

X Commands menu Initially, this is an empty menu. You can add commands that start X clients by editing the HWM configuration file. You can also display this menu by clicking the right mouse button on the X server window background.

Root Window menu Contains commands that let you change the pattern or color of the X server window (root window) background. Your selection is implemented immediately.

Note: When you choose the Kill Client command, the pointer changes to a skull and crossbones. You can exit an application by choosing this command, moving the pointer to the application window, and then clicking the left mouse button.

Note: If you are running in Multiple Window mode, you must make sure that Root Drawing (on the Xconfig–Screen Definition page, click Advanced settings) is set to either Background or Full Support. If Root Drawing is set to None, then the changes you make using the Root Window menu will not take effect.

270

Appendix C: HWM

Exit/Restart menu Contains commands that let you exit or restart HWM.

Help command Displays a quick reference table that shows you how to invoke various HWM and Virtual Desktop functions using keystroke or mouse button combinations.

The Virtual Desktop

The Virtual Desktop is a window that represents an area many times larger than the actual server root window. It displays an overview of the entire contents of the server root window, including those X clients that are currently off-screen.

For more information, see “Statements” on page 275.

You can enable the Virtual Desktop by including the VirtualDesktop statement in your HWM configuration file.

A thin frame outlines the portion of the Virtual Desktop that is visible on your display. This frame can be moved by clicking it with the right mouse button and dragging it to the desired location. If you move it to a client application, that gives it the focus. Each active client appears as a shaded box. When you click the left mouse button in a shaded box, the name of the client appears in the Virtual Desktop title bar. The client window with the focus appears with its title bar, border color, and shaded box in the highlight color.

You can position client windows anywhere within the Virtual Desktop by clicking the window with the left mouse button and dragging it to the desired location. When you release the mouse button, the window moves to the specified location.

271


HWM Configuration File

HWM operates according to the specifications in its configuration file, Hwmcfg.src, located in the Exceed default user directory:

“C:\Program Files\Hummingbird\Connectivity\version\Default User\Exceed”

This text file is loaded each time you start or restart HWM. You can customize HWM by editing Hwmcfg.src. You can display Hwmcfg.src when HWM is running by choosing the Edit HWM Config command from the Local Commands submenu on the System menu.

Formatting RulesThe sections below outline some basic formatting rules to consider when customizing the configuration file.

Configuration File Syntax

Note: This file is annotated to help you understand the functions and statements in it. We recommend that you make a backup of the configuration file before customizing it. This ensures that the original file remains intact if you need to revert to it later. Changes to HWM configuration file take effect when you restart HWM.

Component Formatting Rule

Statements

Exclamation Mark (!) Appears at the beginning of the line and indicates that this line is a comment.

#If...#Then Preprocessor statements must always begin with a number sign (#). For more information, see “Preprocessor Statements” on page 286.

Menus

Submenus Submenus must always be defined before they can be included in another menu.

272

Appendix C: HWM

Supported Character Escape Sequences

Lines

Backslash (\)Continued Rows

Indicates that this line continues onto the next line.

Continued rows must appear sequentially in the configuration file. You cannot have blank lines between continued lines.

Tokens

Usage/Spacing Each statement should consist of one or more tokens separated by one or more spaces.

Note: A token is either a series of non-space characters, or any sequence of characters enclosed by matching quotation marks (for example, “a b/c? d*e”).

Case Sensitivity Tokens that are HWM functions are not case-sensitive. Any string that displayed as text on the screen is case-sensitive.

Backslash (\) Within a string, the backslash character (\) starts an escape sequence (see the Supported Character Escape Sequences table below).

Sequence Function

\\ Represents a single backslash (\).

\n Generates a newline character (0x0A).

\r Generates a carriage return character (0x0D).

\xdd Formulates any byte value except 0. Each d is a hexadecimal digit.

\u Inserts the default user path. A trailing \ is also inserted, if needed. For example, "\uhwmcfg.src" is equivalent to:

..Program Files\Hummingbird\Connectivity\version\Default User\Exceed\hwmcfg.src

\i Inserts the home\info path. A trailing \ is also inserted, if needed. For example, "\ixrdb.txt" is equivalent to:

..Program Files\Hummingbird\Connectivity\version\Exceed\info\xrdb.txt

\h Inserts the home path. A trailing \ is also inserted, if needed. For example, "\hexceed.exe" is equivalent to:

..Program Files\Hummingbird\Connectivity\version\Exceed\Exceed.exe

Component Formatting Rule

273


Functions

Functions are commands in the configuration file that perform specific actions. If you invoke any of the functions that affect a single window (such as iconify, refresh, zoom) from a menu that is bound to that window, the function operates immediately. However, if you invoke the same function from a menu that is not bound to the window, you have to click the left mouse button in the appropriate window to perform the operation.

The following table lists the supported functions:

\ Continues a single line, onto the next line.

\? Enters a wildcard character that is otherwise used to delineate a string or start an escape sequence.

Note: A question mark (?) denotes any wildcard character.

Sequence Function

Function Description

Nop Specifies a no operation token.

Iconify Iconifies/restores a window.

Menu menu_name Activates the named menu—when this function is called, HWM places the upper left corner of the menu at the current mouse position.

Move Raises and moves a window or icon.

Resize Raises and resizes a window.

Zoom Zooms/unzooms a window.

Refresh Forces a redraw of the selected window.

RefreshScreen Refreshes the entire screen.

ShowIconMgr Shows/raises the Icon Manager.

HideIconMgr Removes the Icon Manager.

274

Appendix C: HWM

Statements

Statements are a sequence of actions in the HWM configuration file (Hwmcfg.src) that carry out a specific function in HWM. Editing the statements in Hwmcfg.src lets you customize HWM. When used in a Hwmcfg.src file, a single statement carries out a single action, while a series of statements carries out a complex sequence of actions.

The following sections describe the representative statements in the Hwmcfg.src file in the order they appear in the file. However, not all statements listed below are included in the default configuration. The supported HWM statements can be grouped into the following categories:

• Virtual Desktop statements

• Font statements

• Window statements

ShowIcons Displays client icons.

HideIcons Hides client icons.

Up Circulates a window up.

Down Circulates a window down.

Top Raises a window to the top.

Bottom Lowers a window to the bottom.

Kill Kills a client.

Exit Exits HWM.

Restart Restarts the window manager (and rereads the Hwmcfg.src file).

Freesel Releases ownership of the PRIMARY selection.

Setroot Changes the appearance of the root window.

Function Description

275


• Color statements

• Icon Manager statements

• Menu Definition statements

• Mouse Button Binding statements

Virtual DesktopThe Virtual Desktop is the first section in the configuration file. The following statements appear in the default configuration file.

VirtualDesktop Opens the Virtual Desktop when you run HWM. You can disable the Virtual Desktop by inserting an exclamation mark (!) at the beginning of this line. The syntax for this statement is as follows:

VirtualDesktop

VdeskScale Specifies the scale of the Virtual Desktop window. number defines the scale of the Virtual Desktop in comparison to your screen. This value indicates the number of screen pixels that each pixel of the Virtual Desktop represents. By default, the value is 20. Therefore, each pixel on the Virtual Desktop represents 20 pixels on your screen. The syntax for this statement is as follows:

VdeskScale number

StickyVdesk Places the Virtual Desktop within itself to prevent the Virtual Desktop itself from being displayed from within the Virtual Desktop window. This statement ensures that you will not inadvertently move the Virtual Desktop off the screen. The syntax for this statement is as follows:

StickyVdesk

If you want the Virtual Desktop to appear as a rectangle within the Virtual Desktop window, insert an exclamation mark (!) at the beginning of this statement.

Note: You can disable any of the statements in the configuration file by inserting a comment indicator, or exclamation mark (!), at the beginning of the statement.

276

Appendix C: HWM

DoubleClick Specifies double-click span in milliseconds. The default is 300 as shown in the following syntax:

DoubleClick_msec 300

FadedMenus To specify faded menus, remove the exclamation mark (!) from the beginning of the statement.

The syntax for this statement is as follows:

FadedMenus

borderwidth Sets the 3D border width to the desired number of pixels. The default is 8 as shown in the following syntax:

borderwidth 8

nocascade If you do not want to cascade windows, remove the exclamation mark (!) from the beginning of this statement:

!nocascade

positionisframe To specify (x, y) coordinates for your client window (not for its frame), remove the comment indicator (!) from the beginning of this statement:

!positionisframe 0

Other Supported Virtual Desktop StatementsThe following statements control the operation of HWM Virtual Desktop; they are not included in the default configuration file.

color vdesk Sets the foreground (screen frame) and background color of the Virtual Desktop. The syntax for these statements are as follows:

color vdesk foreground colorname

color vdesk background colorname

Note: The Render extension must be active.

Note: You must also uncomment (remove the ! from) nocascade to set (x, y) coordinates for the window.

277


VdeskGeom Specifies the placement of the Virtual Desktop window. The syntax for this statement is as follows:

VdeskGeom [+|-]x[+|-]y

This statement only works if windows are automatically placed (for example, if NoGhost is specified in Hwmcfg.src). A single + or - must precede each x and y.

The parameters are described in the table below.

VdeskButton Lets you configure which mouse button is needed to drag the server window frame or client windows to a new location. The syntax for this statement is as follows:

VdeskButton b1 b2


+x Specifies the horizontal position of the window, where x is the number of pixels from the left edge of the server root window to the left border of the Virtual Desktop.

-x Specifies the horizontal position of the window, where x is the number of pixels from the right edge of the server root window to the right border of the Virtual Desktop.

+y Specifies the vertical position of the window, where y is the number of pixels from the top edge of the server root window to the top border of the Virtual Desktop.

-y Specifies the vertical position of the window, where y is the number of pixels from the bottom edge of the server root window to the bottom border of the Virtual Desktop.

Note: b1 is the button that moves the frame; b2 is the button that moves the client windows. The values for b1 and b2 can be either 1, 2 or 3, which represent the left, middle and right buttons on the mouse, respectively. The values for b1 and b2 must be different. The default is VdeskButton 3 1, where the left button (number 1) moves the client windows and the right button (number 3) moves the frame.

278

Appendix C: HWM

For more information on bind statements, see “Mouse Button Bindings” on page 284.

ShowVdesk/HideVdesk Lets you show or hide the Virtual Desktop when the Virtual Desktop is enabled via an preceeding VirtualDesktop statement. The syntax for this statement is as follows:

ShowVdesk

HideVdesk

Font StatementsFor more information on preprocessor statements, see “Preprocessor Statements” on page 286.

The preprocessor statement shown below sets the font used by HWM. It uses the preprocessor #if...#else...#endif format to set one of two different fonts, depending on the size of the server screen.

#if Xpixels >= 1024

font 10x20

#else

font 6x10

#endif

Window StatementsWindow statements let you move, resize, and focus windows.

NoGhost Lets you instruct HWM to automatically place and size client windows. The syntax for this statement is as follows:

NoGhost

To move and resize client windows when they first appear on your screen, add an exclamation mark (!) to this statement. The windows then appear as outlines, which you can place anywhere on the screen or Virtual Desktop.

Note: Statements and functions can also be called using mouse-button bind statements. For example, to show the Virtual Desktop whenever you hold down Alt-Shift and then click the right mouse button, use the following statement:

bind alt shift b3 showvdesk

279


ClickToFocus Lets you focus client windows. This statement, by default, requires that you click with the left mouse button to focus and raise a client window. The syntax for this statement is as follows:

ClickToFocus [raise] 1

If you want the pointer to focus the window, insert an exclamation mark (!) before this statement. The raise parameter is optional. You can also specify one of 1 (left), 2 (middle), or 3 (right) to indicate which mouse button to click.

Color StatementsColor statements set the colors that HWM displays for windows, menus, icons, dialogs, and the Icon Manager.

3D Effect HWM achieves its 3D effect by using three colors. In each of the areas where you can set background and foreground color, HWM allocates a third color that is a shade of the background. If colors are not specified for WINDOW, TRANSIENT, ICON, ICONMGR, or MENU, HWM assumes the colors are black and white, with gray shading.

Setroot color_specification Specifies the color of the root server window. The syntax for this statement is as follows:

Setroot color_specification

The following table describes different types of color_specification.

Color_Specification Description

default Resets the server root window to its default.

solid color Changes server root window to a solid color, where color is any color defined in the RGB database. If the color name contains spaces or tabs, enclose it in quotation marks (" ").

bitmap filespec[fg color bg color]

Changes the server's root window to the pattern described in the file filespec, where filespec specifies a standard X11 bitmap. You can optionally specify the foreground and background color.

280

Appendix C: HWM

Icon Manager StatementsThis section describes the Icon Manager configuration statements that appear in the default configuration file.

IconMgrOn Enables the Icon Manager when you run HWM. The syntax for this statement is as follows:

IconMgrOn

This statement automatically displays the Icon Manager in the server window. You can disable the Icon Manager by inserting an exclamation mark (!) at the beginning of this line.

stickyIconMgr Prevents the Icon Manager itself from being displayed from within the Virtual Desktop window. This statement ensures that you will not inadvertently move the Icon Manager off the screen while using the Virtual Desktop. The syntax for this statement is as follows:

stickyIconMgr

If you want the Icon Manager to appear as a rectangle within the Icon Manager window, add a (!) before this statement.

HideIcons Hides any client that is currently iconified. The syntax for this statement is as follows:

HideIcons

If you want the icons displayed, you can replace this statement with the ShowIcons function.

Other Supported Icon Manager StatementsThis section describes additional supported statements that relate to the operation of HWM Icon Manager. These statements are not included in the default Hwmcfg.src file:

IconImage Associates a specific bitmap file to act as an icon for a particular client window. The syntax for this statement is as follows:

IconImage window-name bitmap

281


For example, you can use the Hummingbird bitmap file in the Info directory (by default, “C:\Program Files\Hummingbird\Connectivity\version\Exceed\Info”) as an icon for an xterm window by using the following statement:

IconImage xterm "\bird.bit"

You can also associate a pixmap to be used as the default HWM icon for clients that do not specify an icon by using the following statement:

IconPixmap filespec

For more information on the x and y variables, see “VdeskGeom” on page 278.

IconMgrGeom Specifies the placement of the Icon Manager window. The syntax for this statement is as follows:

IconMgrGeom [+|-]x[+|-]y

Menu DefinitionsThis section of the configuration file lets you configure how menus appear on HWM. Menu definitions start with the word menu, followed by the name of the menu enclosed in quotation marks (" ") and ending with the word endmenu. Any items that appear on the menu are defined on the lines in between these two words.

All HWM menus appear in the menu definition section and can be divided into two distinct categories: menus with inactive menu functions and menus with active functions. Both types are discussed below.

Inactive FunctionsMenus with inactive functions are menus that do not perform any operations. They present information, rather than provide menu commands.

Note: filespec must specify a standard X11 bitmap file.

Note: Menu names are case-sensitive.

282

Appendix C: HWM

For example, the VdeskHelp menu defined below has no active functions. Lines that do not invoke functions (or blank lines on a menu), are exited with nop, which indicates No Operation. Strings in the menu definition, or text enclosed in quotation marks (" "), display on the menu using the default font specified in this file.

menu VdeskHelp

"Click on With Mouse Button Function" nop

"-------- --------------- --------" nop

"anywhere Alt Shift right Show VirtualDesktop" nop

"anywhere Alt Shift left Hide VirtualDesktop" nop

" " nop

"in Vdesk left Move the view" nop

"in Vdesk on a window right Move and/or show the name of a window" nop

endmenu

Active FunctionsMenus with active function menu items execute a specific operation, or invoke a specific submenu, when the user chooses it from the menu. For example, the Window Ops menu includes items which perform various window functions:

menu "Window Ops"

"Iconify" iconify

"Move" move

"Resize" resize

"Raise" top

"Lower" bottom

"Zoom" zoom

Note: Blank lines on the menu are indicated with an empty string ("").

283


"Refresh" refresh

"Close" kill

endmenu

To start an application from an HWM menu, use “run” with the specified command. You can use the Local Commands menu to execute local Windows or X apps. For example:

menu "Local Commands"

"Xconfig" run "xconfig"

Xsession" run "xsession"

"Xstart" run "xstart"

"Hwm config" run "notepad hwmcfg.src"

endmenu

You can use the X Commands menu to start remote X clients using Xstart. For example:

menu "X Commands"

"XTerm Packard" run "xstart packard.xs"

endmenu

Mouse Button Bindings The mouse button bindings section of the Hwmcfg.src file lets you display a menu or perform a function by either binding it to a mouse button, or to a mouse button and keystroke combination.

In general, the syntax for a bind statement is:

bind [location] [modifier] button menu_or_function

284

Appendix C: HWM

Mouse button binding parameters are described in the chart below:

1 If none of Root, Window, Icon, Left, Right, InsideRight, or Middle is specified, then all are assumed.

2 Alt is used as a synonym for Mod1, as this is the modifier associated with the Alt key in the keyboard files supplied with Exceed.

3 Only one of B1, B2, or B3 can be specified in any one statement.

Mouse Button Binding Parameters

Location1 Description

Root (or R) Binding is valid on the root window.

Window (or W) Binding is valid on a window.

Icon (or I) Binding is valid on an icon.

Left (or L) Binding is valid on a window banner's left button (typically the Window Ops button).

OutsideRight (Right, OR, or R) Binding is valid on a window banner's outside right button (typically the zoom button).

InsideRight (or IR) Binding is valid on a window banner's inside right button (typically the button to iconify).

Middle (Mid or M) Binding is valid on a window banner's title bar, that is, outside of the buttons.

Modifier2 Description

Shift (or S) <Shift> required.

Control (CTRL or C) <Ctrl> required.

Mod1 (ALT or A) Mod1 required.

Mod2... Mod 5 Mod2... Mod5 required.

Button3 Description

B1 (or 1) Mouse button 1 (left).

B2 (or 2) Mouse button 2 (middle).

B3 (or 3) Mouse button 3 (right).

285


Preprocessor StatementsPreprocessor statements let you set if...else conditions that define which statements in the Hwmcfg.src file are processed. The following preprocessor statements are supported:

For example:

#if Planes == 8 !test for 256 colors

color active transient foreground blue

color inactive window background red

color... !specify colors

#else

color active transient foreground white

color inactive window background black

color... !different colors

#endif

Statement Description

#if expression Used to specify an expression. Expression format is described in the Expressions in Preprocessor Statements section below. If the expression is true, successive statements are processed. If the expression is false, successive statements are not processed.

#endif This statement marks the end of the range of the #if statement. For each #if statement there must be one #endif statement.

#else statement(s) You can use one #else statement within each #if...#endif range. If the expression in the associated if statement is false, all statements between #else and the associated #endif are processed.

Note: #if...#endif statements can be nested, that is if...#endif ranges can be placed within each other.

286

Appendix C: HWM

Expressions in Preprocessor Statements Expressions in preprocessor statements take the following format, and the fields must be separated by one space:

id operator constant

These fields are discussed in the following table:

Field Description

id

xpixels The width of the server screen in pixels.

ypixels The height of the server screen in pixels.

Planes Represents the number of video planes. The number of colors is 2planes, that is, 4 planes specifies 16 colors; 8 planes specifies 256 colors.

Color Used to test whether or not the server supports color. (for example: PseudoColor or StaticColor). If the default server supports color, Color is set to 1. Otherwise, it is set to 0.

Static Used to test whether or not the server supports static read-only colormaps or dynamic read/write colormaps. If the server supports only static colormaps, Static is set to 1. If the server supports dynamic colormaps, Static is set to 0.

VdeskOn Used to test whether the Virtual Desktop is specified in Hwmcfg.src. If the Virtual Desktop is specified, VdeskOn is set to 1, otherwise it is 0.

operator

== TRUE if ID is equal to constant.

<> TRUE if ID is not equal to constant.

< TRUE if ID is less than constant.

<= TRUE if ID is less than or equal to constant.

> TRUE if ID is greater than constant.

>= TRUE if ID is greater than or equal to constant.

constant

constant A decimal numeric value.

287

Appendix D

General Accessibility andTechnical Support

General Accessibility 291Microsoft Accessibility Options 292

Technical Support 293

Appendix D: General Accessibility and Technical Support

General Accessibility

Hummingbird products are accessible to all users. Wherever possible, our software adheres to Microsoft Windows interface standards and contains a comprehensive set of accessibility features.

Access Keys All menus have associated access keys (mnemonics) that let you use the keyboard, rather than a mouse, to navigate the user interface (UI). These access keys appear as underlined letters in the names of most UI items. (If this is not the case, press Alt to reveal them.) To open any menu, press Alt and then press the key that corresponds with the underlined letter in the menu name. For example, to access the File menu in any Hummingbird application, press Alt+F.

Once you have opened a menu, you can access an item on the menu by pressing the underlined letter in the menu item name, or you can use the arrow keys to navigate the menu list.

Keyboard Shortcuts Some often-used menu options also have shortcut (accelerator) keys. The shortcut key for an item appears beside it on the menu.

Directional Arrows Use the directional arrows on the keyboard to navigate through menu items or to scroll vertically and horizontally. You can also use the directional arrows to navigate through multiple options. For example, if you have a series of radio buttons, you can use the arrow keys to navigate the possible selections.

Tab Key Sequence To navigate through a dialog box, press the Tab key. Selected items appear with a dotted border. You can also press Shift+Tab to go back to a previous selection within the dialog box.

Spacebar Press the Spacebar to select or clear check boxes, or to select buttons in a dialog box.

Esc Press the Esc key to close a dialog box without implementing any new settings.

Enter Press the Enter key to select the highlighted item or to close a dialog box and apply the new settings. You can also press the Enter key to close all About boxes.

291


ToolTips ToolTips appear for all functional icons. This feature lets users use Screen Reviewers to make interface information available through synthesized speech or through a refreshable Braille display.

Microsoft Accessibility OptionsMicrosoft Windows environments contain accessibility options that let you change how you interact with the software. These options can add sound, increase the magnification, and create sticky keys.

To enable/disable Accessibility options:

1 In Control Panel, double-click Accessibility Options.

2 In the Accessibility Options dialog box, select or clear the option check boxes on the various tabs as required, and click Apply.

3 Click OK.

If you installed the Microsoft Accessibility components for your Windows system, you can find additional accessibility tools under Accessibility on the Star t menu.

292

Appendix D: General Accessibility and Technical Support

Technical Support

You can contact the Hummingbird Technical Support department Monday to Friday between 8:00 a.m. and 8:00 p.m. Eastern Time.

Hummingbird Ltd.1 Sparks Avenue, Toronto, Ontario, Canada M2H 2W1

Canada and the USA International

Technical Support: 1-800-486-0095 +1-416-496-2200

General Enquiry: 1-877-FLY-HUMM +1-416-496-2200

Main: +1-416-496-2200

Fax: +1-416-496-2207

E-mail: [email protected]

FTP: ftp.hummingbird.com

Web Support: support.hummingbird.com/customer

Web Site: www.hummingbird.com

293


ftp://ftp.hummingbird.com

http://support.hummingbird.com/customer

http://www.hummingbird.com

Index

Numerics5250 Data Transfer Wizard ......................... 265

AAccessibility page, Xconfig .......................... 195accessibility, general..................................... 291accessing the font server .............................. 184accessing X applications remotely............... 132accessories.................................................... 261

Classic FTP........................................... 261Directory Services Explorer ................. 261File Converter....................................... 261Hummingbird Basic............................. 261Hummingbird Directory Services ....... 261Line Printer Query ............................... 261Line Printer Requester ......................... 262Network Time ...................................... 262NSLookup ............................................ 262Ping....................................................... 262Quick Script Editor .............................. 262Remote Tools ....................................... 262Traceroute ............................................ 262

Active Directory........................................... 206changing passwords in ......................... 226

adding X screens .......................................... 167administrative tools ..................................... 262

Files and Settings Transfer Wizard ...... 263HostExplorer Management Console ... 263HTTP Proxy Server.............................. 263Hummingbird InetD ........................... 263Hummingbird Update......................... 263Language Chooser................................ 264

Media Location Manager ..................... 264Metering Client Settings....................... 264Metering Server .................................... 264Proxy Server Console ........................... 264Sconfig .................................................. 264

advertisement of products .............................25allocating system resources.......................... 189analysing

log file ................................................... 255progress messages................................. 254

application database file, syntax .................. 102applications

browsing for ........................................... 95included with Exceed ...............................4

applications, HostExplorer .......................... 2653270 ...................................................... 2655250 ...................................................... 2655250 Data Transfer Wizard.................. 265Macro and Profile Converter ............... 265Print Services ........................................ 263VT......................................................... 265WyseTerm ............................................ 265

authentication128-bit SSL ........................................... 226AUTH_SYS .......................................... 243CA certificates ..............................225, 229high encryption .................................... 226Secure RPC........................................... 206SSL/TLS ................................................ 225user credentials for LDAP .................... 228using SASL............................................ 232


automatically copying and pasting ..............117available Exceed products ................................6

Bbalancing system loads.................................123binding to a domain

overview ................................................208LDAP ....................................................220NIS ........................................................214NIS+......................................................217using user vs. machine credentials .......217

browsingfor applications .......................................95for hosts ..................................................95

buttons, configuring the mouse...................144

CCA certificate

definition ..............................................225installing................................................227

caching a password ......................................122CDE..............................................................108

traditional Chinese HP.........................151Certificate Authority (CA).................. 225, 229character escape sequences ..........................273Chinese environments .................................150Chinese, Japanese, & Korean

(CJK) Input ...........................148–152Classic FTP...................................................261cluster environment

defined ..................................................202advantages.............................................202directory services in ..............................202

color statements ...........................................280color specification types .......................280

command lineExceed X server parameters..................130running an Xstart file............................104window manager startup......................111

command line (Sconfig)error conditions ......................................78generating .mst files from.......................77invoking .mst files from..........................78

options.................................................... 77validation conditions ............................. 79

command line applicationsin Hummingbird Directory Services ... 247

command macros in Xstart ......................... 121commands, window managers.................... 111Common Desktop Environment. See CDE.configuration file ......................................... 272

comparing ............................................ 197formatting rules.................................... 272functions .............................................. 274Icon Manager configuration statements ..

281syntax.................................................... 272Virtual Desktop section ....................... 276Xconfig ................................................. 137

configuringfour screens .......................................... 168the mouse ............................................. 144X screens............................................... 167

connectingBroadway and LBX .............................. 133setting sequence of events .................... 153to hosts ................................................... 89

copying and pastingoverview ............................................... 112automatically........................................ 117between X clients.................................. 116data ............................................... 113–114graphics ................................................ 114storage buffer ....................................... 112to input CJK text .................................. 150

creating ........................................................ 255a password cache.................................. 122a security file......................................... 160font aliases ............................................ 186startup file............................................... 92startup file, Wstart ................................. 92Xstart shortcut...................................... 102

customizingfiles and folders ...................................... 80installation........................................ 80–86the keyboard......................................... 141

296

Index

customizing installations with Sconfigdirectories............................................... 42Directory Services properties ...........42, 63Exceed properties ................................... 42features .............................................42, 48files....................................................42, 50font directories and servers ....... 43, 68, 72font paths ............................................... 43for Terminal Services ............................. 40Metering properties .........................42, 62NFS properties ....................................... 43properties .........................................42, 54registry.................................................... 42registry keys ............................................ 57shortcuts ...........................................42, 60

DDECnet transports, using ............................ 107DECwindows compatibility ........................ 165default

configuration file.................................. 137root directories, connectivity settings.... 80user directory ............................ 80, 81, 82

default user directory................................... 272path, character escape sequence .......... 273

deletinga password cache.................................. 123a screen ................................................. 168Xscreens................................................ 167

Deployment Packager.................................. 262Deployment Wizard .................................... 263Desktop Settings menu................................ 270Destination directory..................................... 43destination folder, installation ...................... 14DHCP .......................................................... 209

configuring the server .......................... 209locating servers with............................. 209option codes ......................................... 209

diagnostics, Exceed...................................... 254directories

default user .......................................80, 81personal (per-user) ................................ 80

directories, customizing with Sconfig..... 42, 43creating custom folders ..........................45creating custom subfolders.....................47Current User directory ...........................43Destination directory..............................43

Directory propertiessetting with Sconfig ................................63

directory servicesdefinition ..............................................205domains ................................................205object types ...........................................206profiles ..................................................208protocol types .......................................205query order ..................214, 216, 219, 222repositories ...........................................207

Directory Services Explorer .........................261overview................................................201changing a domain password...............240profiles ..................................................210querying directory service objects ........236saving query results...............................238sorting query results .............................237viewing object properties......................239

directory services profilesdisabling user profiles...........................245for Directory Services Explorer ............212for Hummingbird Directory Services ..212modifying..................................... 239, 244removing...................................... 240, 244system profile........................................211user profiles ..........................................211

Directory Services propertiessetting with Sconfig ................................42

disabling a screen .........................................168DISPLAY environment variable 106, 111, 156,

157display, setting..............................................176displaying

scroll bars ..............................................172X window manager menus...................171

Dynamic Host Configuration Protocol. See DHCP.

297


Eediting

font database.........................................182fonts ......................................................183

enablinghost access.............................................159

encoding, traditional Chinese......................150environments

Chinese .................................................150Exceed

available products .....................................6diagnostics ............................................254included applications................................4on a remote PC.....................................132

Exceed 3D.........................................................7Exceed Connection Manager...........................5Exceed properties

setting with Sconfig ......................... 42, 66Exceed X Server

overview ....................................................4and Input Method server......................149configuring ...........................................164resetting ................................................170

Exceed XDK .....................................................6Exit/Restart menu ........................................271Exposé Online ................................................29Extend, modifying settings ..........................162

Ffeatures, customizing with Sconfig ......... 42, 48

adding .....................................................48modifying................................................49removing.................................................49

File Converter...............................................261files

converting .............................................261.mst .........................................................39.mst for Terminal Services......................40

Xsession sequence ................................ 128Files and Settings Transfer Wizard........85, 263files, customizing with Sconfig...................... 42

adding custom........................................ 50modifying custom .................................. 52removing ................................................ 52

folders, Sconfig. See directories, customizing with Sconfig.

font aliascreating................................................. 186creating several ..................................... 187exporting .............................................. 181importing and exporting files ...... 187–188

font databaseediting................................................... 182managing.............................................. 182selecting................................................ 181

font directories, setting with Sconfig ............43, 68, 75

adding..................................................... 68modifying ............................................... 70removing ................................................ 71

font files (Sconfig) ......................................... 68adding..................................................... 68removing ................................................ 71

Font page, Xconfig....................................... 181font server access ......................................... 184font servers, setting with Sconfig.............43, 72

adding..................................................... 72modifying ............................................... 73removing ................................................ 74

font statements ............................................ 279fonts, working with...................................... 183formatting rules ........................................... 272frozen connection, determining.................. 257FTP............................................................... 261

Hummingbird client ............................ 265functions ...................................................... 274

298

Index

GGeneric Security Service Application

Program Interface......................... 232GLX extension .....................................166, 195GNOME. See GNU Network Object

Model Environment.GNU Network Object

Model Environment ..................... 108graphics, copying and pasting ..................... 114GSSAPI. See Generic Security Service

Application Program Interface.

HHelp command............................................ 271high (128-bit) encryption............................ 226home

path, character escape sequence .......... 273host list file

syntax.................................................... 101host lookups

NIS maps .............................................. 214specifying a target service..................... 245

HostExplorer components .......................... 2653270 ...................................................... 2655250 ...................................................... 2655250 Data Transfer Wizard.................. 265Deployment Packager .......................... 262Deployment Wizard............................. 263Index Page Wizard ............................... 263Macro and Profile Converter ............... 265Print Services........................................ 263VT......................................................... 265WyseTerm ............................................ 265

HostExplorer Management Console........... 263HostExplorer Print Services ........................ 263hosts

browsing for ........................................... 95load balancing ...................................... 123optimizing loads................................... 123restricting access................................... 159

HTTP Proxy Server......................................263.humfst file .....................................................85Hummingbird accessibility..........................291Hummingbird Basic ....................................261Hummingbird Directory Services ...............261

overview................................................201command line applications ..................247profiles ..................................................211retrieving AUTH_SYS credentials .......243selecting a service..................................243specifying a host lookup service ...........245synchronizing directory service

and Windows passwords .................246Hummingbird FTP ......................................265Hummingbird InetD ...................................263Hummingbird Setup Wizard.........................11

maintenance mode .................................20Hummingbird Update.......................... 29, 263.humreg file ....................................................81HumSettings.exe ............................................86

location ...................................................82passing arguments ..................................83

HumSettings.log file ......................................85HWM, overview...................................... 5, 110Hwmcfg.src

HWM configuration file.......................272icon manager statements......................281location .................................................272mouse bindings ....................................284mouse button bindings ........................284preprocessor statements .......................286restart function .....................................275statements .............................................275VdeskGeom desktop statement ...........278VdeskOn field.......................................287

IIcon Manager statements.............................281improving system performance...................189Index Page Wizard .......................................263info directory

path, character escape sequence...........273

299


input method server.....................................149installation

advertised................................................25controlling per-user settings...................80current user versus "All Users"...............17destination folder....................................14disabling migration, per-user settings....85Master Setup ...........................................14Media Location Manager .....................264migrating user settings......................83–86passing arguments, per-user settings .....83personal, as Administrator .....................24personal, overview ..................................23personal, without

Administrator privileges ....................23requirements...........................................13scenarios .................................................23silent........................................................26third party add-ons.................................14troubleshooting ....................................251user directory ..........................................14

installationscreating multiple with Sconfig ........ 40, 77for Terminal Services..............................40setup type for Sconfig .............................39

Installer Database files. See MSI files.installing a shortcut

Xsession ................................................128Xstart.....................................................102

IP Discovery .........................................155–157IPDisCov daemon........................................155

JJava Runtime Environment (JRE), Sun.........14

KK Desktop Environment ..............................108KDE. See K Desktop Environment.keyboard

customizing ..........................................141Keyboard Input page, Xconfig.....................141keylogin

failure ....................................................219

running................................................. 247using a user profile ............................... 219using the system profile ....................... 219

Kill Client command ................................... 270

Llaunching

Windows applications.......................... 105launching personal installation

as Administrator .................................... 24without Administrator privileges........... 23

LDAP .......................................................42, 63definition.............................................. 206authentication .............................. 225, 228bind options ......................................... 220entries ................................................... 207objectclasses for automount

information...................................... 234objects................................................... 207posixAccount class ............................... 207query options, setting........................... 227query order........................................... 222schema style, setting............................. 233server architecture................................ 207specifying user credentials ................... 228supported schemas............................... 206version 2 vs. version 3 .......................... 223

Lightweight Directory Access Protocol (LDAP)............... 206

Line Printer Query....................................... 261Line Printer Requester................................. 262Linux

desktop environments ......................... 108GNOME............................................... 108KDE...................................................... 108

load optmization ........................................... 98loading resource databases .......................... 170Local Commands menu .............................. 270

example in Hwmcfg.src ....................... 284locale name

specifying.............................................. 149log files ......................................................... 255

analysing............................................... 255

300

Index

logging in to CDE ........................................ 108login macros in Xstart ................................. 121

command ............................................. 121user ID and password .......................... 121

login, special for Xstart ................................ 122LPQ. See Line Printer Query.LPR. See Line Printer Requester.

MMacro and Profile Converter ...................... 265master servers .............................................. 207Master Setup ..................................... 14, 17, 22Media Location Manager ............................ 264menu definitions.......................................... 282

active functions .................................... 283inactive functions ................................. 282

Metering Client Settings.............................. 264Metering properties

setting with Sconfig ..........................42, 62Metering Server ........................................... 264Microsoft Management Console (MMC)

snap-in for Hummingbird Directory Services............................................. 202

Microsoft Management Console, Xconfig.. 196Microsoft System

Management Server (SMS) ............ 27Microsoft Transform file. See MST files.Microsoft Windows manager, overview ..... 110middle button emulation ............................ 144migrating

files and settings ................................... 263MMC. See Microsoft Management Console.monitoring connections .............................. 257mouse button bindings ............................... 284

parameters............................................ 285Mouse Input page, Xconfig ......................... 144mouse wheel

Macro Selector ..................................... 146mapping to a macro ............................. 146New Macro Properties ......................... 147options.................................................. 145

mouse, adding 3-button function ...............144Msetup.exe ........................... 20, 21, 23, 24, 25

personal installation ...............................17MSI files

applying .mst files to...............................78customizing ............................................40

Msiexec.exe ....................................................26command line options .........................253

MST files ........................................................39applying error conditions.......................78applying to .msi files ...............................76applying validation conditions...............79creating ............................................ 41, 77creating for Terminal Services................40generating from a command line...........77invoking from a command line..............78saving ......................................................75Windows Installer...................................39

multiple custom installations.................. 40, 77multiple window mode................................109multiple X displays.......................................130multiple Xstart sessions per host .................124MWM. See Microsoft Windows manager.

NNetwork Information System (NIS)............205Network Time ..............................................262NFS Maestro Name Mapping Server...........242

specifying primary and secondary servers.............................242

NFS properties, setting with Sconfig ...... 43, 65adding, modifying, or removing ............65

nfs register command ..................................219NFSD....................................................... 42, 63NIS........................................................... 42, 63

definition ..............................................205bind options..........................................214objects ...................................................206query order .................................. 214, 216server types ...........................................207specifying a NIS domain.......................215

NIS+ ........................................................ 42, 63definition ..............................................206

301


bind options..........................................217objects ...................................................206query order ...........................................219server types............................................207specifying an NIS+ domain..................217

NIS+ Keylogin dialog box............................219NSLookup ....................................................262

OOpenGL........................................................195opening

.msi files ..................................................40

.mst files ..................................................40Sconfig ....................................................40Xstart.......................................................92

opening directory services applications.......203optimizing load ..............................................98overview

installation modes...................................11Windows Installer...................................11

Pparameters

Exceed X server.....................................130Xstart.....................................................104

passexp.ini ....................................................124passive mode, overview................................153password cache

creating .................................................122deleting .................................................123

passwordsaging......................................................105change password, UNIX prompt .........105changing................................................240changing in Xconfig..............................140expiry prompts, UNIX .........................124synchronizing Windows

and directory services.......................246verification methods.............................232

pasting data.................................................. 113patching Hummingbird products............... 263Performance page, Xconfig ......................... 189personal installations, overview .................... 23personal user directory ......................80, 81, 86

automatic update ................................... 82manual update ....................................... 82

PerUser Migration.ini[Active Migration Sources] section ....... 86[Directory Mappings.x.yz] section ........ 85[Migration Control Options] section.... 84controlling migration............................. 83disabling migration, per-user settings ... 85

PerUser Settings.ini[PerUser Installation

Parameters] section ........................... 83[Registry Files] section ........................... 81associating a .humreg file ....................... 81customizing files, folders........................ 81update personal user directory .............. 82

Ping ...................................................... 208, 262policy file, syntax ......................................... 161Power Management page, Xconfig ............. 192preprocessor statements .............................. 286

expressions ........................................... 287Print Services ............................................... 263product access control

creating administrative image.......... 33–35on a Terminal Server.............................. 33personal installation......................... 35–37removing from Terminal Server ............ 37

Program groupinstalling an Xsession shortcut ............ 128installing an Xstart shortcut................. 102

program maintenance ................................... 20modifying install state ............................ 20removing ................................................ 21repairing ................................................. 21

progress messages, analysing....................... 254prompts, password expiry ........................... 124properties, setting with Sconfig .........42, 53, 54

adding..................................................... 54modifying ............................................... 55

302

Index

removing ................................................ 56Protocol page, Xconfig ................................ 164Proxy Server Console .................................. 264

Qquery order

LDAP.................................................... 222NIS................................................214, 216NIS+ ..................................................... 219random................................................. 219

querying directory services .......................... 236Quick Script Editor...................................... 262

Rregistering the product .................................. 28registry entries

adding and removing ............................. 80adding per-user ...................................... 81removing per-user.................................. 86

registry keys, setting with Sconfig ...........42, 56adding..................................................... 57modifying ............................................... 58removing ................................................ 59

remote configuration, Xconfig Console...... 196Remote Tools............................................... 262remote window managers, starting ............. 111replica servers............................................... 207requirements for installation......................... 13resource databases

loading.................................................. 170restricting host access .................................. 159Root Window menu.................................... 270root window, setting size .....................170, 172running

an Xstart file ......................................... 103multiple Exceed X servers .................... 130multiple Xstart sessions per host ......... 124Xstart files from command line ........... 104

SSASL. See Simple Authentication and Security

Layer protocol.saving

a password ............................................122.mst files ..................................................75

saving query results ......................................238Sconfig............................................. 38, 39, 264Screen (definition) page, Xconfig................167Screen (definition), Xconfig ........................167screens

configuring ...........................................167configuring four ...................................168deleting .................................................168disabling................................................168

scroll barsdisplaying..............................................172

Secure RPCauthentication.......................................206password ...............................................219

Secure Socket Layer (SSL)............................225security

changing the Xconfig password ...........140controlling host access..........................159extension password ..............................162files ........................................................160password expiry prompts, UNIX .........124policy file...............................................161settings ..................................................158Xweb .....................................................161

selecting........................................................171fonts ......................................................181start method............................................93X selection type.....................................180

Seltestcopying images to Clipboard ...............115example, building .................................114pasting images from Clipboard............115

serversLDAP ....................................................207master ...................................................207replica....................................................207slave.......................................................207

303


settinga window manager................................171focus policy ...........................................171mouse options ......................................144root window size.......................... 170, 172security for Xconfig ..............................158startup mode.........................................153the display .............................................176window position ...................................172

setting the window modegeneric options .....................................168multiple specific options ......................170single specific options...........................172

settingsrestoring and migrating........................263

Setup Wizardadvertisement mode ...............................25overview of modes ..................................11

shortcutsinstalling, Xsession ...............................128installing, Xstart....................................102

shortcuts, setting with Sconfig ................ 42, 60silent installation ............................................26Simple Authentication and Security Layer

protocol .........................................232requirements.........................................232using GSSAPI .......................................232

single window mode ....................................109slave servers ..................................................207Smart Card Manager........................................6SMS, Microsoft System

Management Server ........................27sorting query results .....................................237specifying

a vendor string ......................................165locale name ...........................................149

SSL. See Secure Socket Layerstandby function ..........................................192starting

a host session ..........................................89a window manager................................111

CDE...................................................... 108remote window managers.................... 111

startup commands, window managers ....... 111startup file

creating for Xstart .................................. 92Xstart (settings.xs)................................ 104

startup mode, selecting................................ 153statements .................................................... 275

Virtual Desktop.................................... 276storage buffer, temporary ............................ 112system administration ................................. 262system display, setting ................................. 176system loads, balancing ............................... 123system menu................................................ 269

TTCP/IP transports, using............................. 106Technical Support ....................................... 293Telnet ........................................................... 265temporary storage buffer ............................. 112Terminal Server

product access control ........................... 33removing product access control........... 37

TN3270 ........................................................ 265TN5250 ........................................................ 265trace files ...................................................... 255Traceroute.................................................... 262transform files. See MST files.Transport Layer Security protocol (TLS).... 225Transport Monitor

overview ................................................... 6using ..................................................... 257

troubleshootingExceed diagnostics ............................... 254installation............................................ 251log and trace ......................................... 255log file, (Troubleshooting)................... 255logs and trace operations ..................... 255progress messages ........................ 254–255Transport Monitor............................... 257Xstart .................................................... 254

304

Index

tuning the system......................................... 191

Uuninstalling

controlling per-user ............................... 86UNIX

/etc files................................................. 207IP Discovery ......................................... 156

updating the product.............................29, 263user directory, installation............................. 14user files

for connectivity products ....................... 15per-machine and per-user ..................... 15

Vvendor string, specifying ............................. 165verifying passwords ..................................... 232Video page, Xconfig .................................... 176viewing

font database ........................................ 182log files.................................................. 255off-screen client windows .................... 169scroll bars ............................................. 172X window manager menus .................. 171

viewing directory service objects ................. 239Virtual Desktop ........................................... 271

placement parameters .......................... 278statements.....................................276, 277

virtual private network ................154, 155, 156VMS systems

DECnet transports ............................... 107TCP/IP transports................................ 106Xstart and Wstart ................................. 106

VMS, using Xstart........................................ 106VPN. See virtual private network.

Wwindow managers........................................ 171

HWM ................................................... 110Microsoft Windows ............................. 110Native, X, Default types ....................... 110overview ............................................... 110

Remote X ..............................................110starting HWM or MWM......................111starting remote managers .....................111startup commands................................111

window modesoverview................................................109configuring generic...............................168configuring multiple.............................170configuring single .................................172multiple.................................................109options ..........................................168–172single .....................................................109

Window Ops menu......................................270example in Hwmcfg.src ........................283

window statements ......................................279Windows

launching applications on hosts...........105Windows Installer

overview..................................................11installation and configuration ................12

Windows Installer Database file. See MSI files.Wstart

creating a startup file ..............................92start method............................................93using on VMS systems..........................106

WyseTerm ....................................................265

XX client

copying and pasting data......................116X Client Wizard

overview....................................................5creating a connection .............................89

X Commands menu.....................................270example in Hwmcfg.src ........................284

X screens, modifying....................................167X Selection page, Xconfig ............................180X selection type, setting................................180X Windows systems, overview.........................4xauth, creating..............................................160Xconfig .........................................................137

overview........................................... 5, 137changing the password .........................140

305


controlling host access..........................159creating a security file ...........................160setting security ......................................158

Xconfig applicationsAccessibility ..........................................195advanced settings

(Display and Video).........................178advanced settings

(Font Management).........................184CJK Input..............................................148Communication Settings......................153Font.......................................................181Keyboard Input.....................................141Mouse Input .........................................144Performance .........................................189Power Management..............................192Protocol ................................................164Screen (definition)................................167Screen Definition..................................167Security and Access Control Settings ...159System Administration.........................163Transports Settings ...............................158Video.....................................................176X Selection ............................................180

Xconfig Microsoft Management Console ...........196–198

Xdis.................................................. 6, 194, 256XDM mode, overview..................................153XDMCP modes, overview ...........................153Xfonts

remote configuration............................197Xperf.............................................................191Xsession

overview ........................................... 5, 125

file sequence ......................................... 128installing a shortcut.............................. 128running multiple sessions .................... 125

Xstartoverview ................................................... 5about the Xstart window........................ 92browsing for hosts.................................. 95change password, UNIX prompt......... 105command macros ................................ 121creating a startup file.............................. 92deleting a password cache .................... 123installing a shortcut.............................. 102login macros......................................... 121opening................................................... 92optimizing system loads....................... 123parameters............................................ 104password expiry, UNIX........................ 124running a file ........................................ 103running multiple sessions .................... 125running multiple sessions per host...... 124start method ........................................... 93universal login ...................................... 122using on VMS ...................................... 106using on VMS systems ......................... 106

Xwebinstallation............................................ 133security ................................................. 161setup ..................................................... 133

Xweb Wizard ................................................... 5

Yypwhich command...................................... 208

306

Exceed 10 User’s Guideftp.iitm.ac.in/archive/Exceed10/Documentation/Exceed.pdf · ii Exceed...

Documents

Transcript of Exceed 10 User’s Guideftp.iitm.ac.in/archive/Exceed10/Documentation/Exceed.pdf · ii Exceed...