89
11
cáäÉë=rëÉÇ=Äó=oÉÑäÉÅíáçå=Ñçê=emI=rkfu=~åÇ=léÉåsjpI=
~åÇ=oÉdfp=dê~éÜáÅë
This chapter describes files that store information for these Reflection applications: Reflection for HP
Reflection for UNIX and OpenVMS Reflection for ReGIS Graphics
pÉííáåÖë=cáäÉë
Reflection settings files generally contain information your users need for connecting to your host. They can also include any customizations you’ve made to the display, toolbars, menus, macros, keyboard, or mouse setup. By default, Reflection saves settings to a complete settings file. Double-clicking a complete settings file launches Reflection with the configurations specified in that file.
Administrators can make settings files available to users in a number of ways, including: • Using the Reflection Customization Manager (described in Chapter 3) to add
settings files to a customized Reflection installation.
• Creating web pages with links that download and launch settings files. See Chapter 6 for details.
• Copying settings files to a shared network location and providing users with shortcuts that point to these files.
`çãéäÉíÉ=EaÉÑ~ìäíF=pÉííáåÖë=cáäÉë
When you save a settings file using the default values in either the Save As or Save dialog box, Reflection creates a complete settings file. Opening a complete settings file configures all of your Reflection settings.
Settings files are specific to individual Reflection applications. The Reflection applica- tions covered in this chapter use the following file extensions:
m~êíá~ä=pÉííáåÖë=cáäÉë
By default, settings files contain information about every aspect of your Reflection configuration. To save or load a settings file that contains information about only a specific aspect of Reflection’s configuration, you can use a partial settings file. When you save or open a partial settings file, you save or update only the relevant part of your configuration.
Partial settings files are not supported in Reflection for Secure IT. Partial settings files can be shared among Reflection for HP, Reflection for UNIX and OpenVMS, and Reflection for ReGIS Graphics. These products use the following file extensions: Reflection Application Settings File Extension
Reflection for HP .r1w Reflection for UNIX and OpenVMS .r2w Reflection for ReGIS Graphics .r4w
Type of Partial Settings File Extension
Key/Mouse map .rkm Toolbar .rtb Colors .rcr Menus .rmu Hotspots .rhs Connection .rco
pÉííáåÖë=réÇ~íÉ=cáäÉë
Settings update files contain information about specific settings only. When you open a settings update file, only those settings are changed. Settings update files allow you to share one or more settings with other Reflection users without changing their other settings. For example, you could create an update file that specifies a new printer destination. When other users open this file, the printer name is updated without affecting any other settings. Users who open this file can open the File menu and click Save to incorporate this change into their existing settings file.
Settings update files are similar to partial settings files, as both update a subset of Reflection settings. However, partial settings files save every setting in a related group of settings, while settings update files include only those settings that are changed from the default when you create the update file. Use settings update files when you want to share only specific settings without overwriting others.
To create a settings update file, use the Save or Save As command on the File menu, and change Save as type to Settings Update. Reflection applications covered in this chapter use the following file extensions for update files.
Reflection Application Settings Update File Extension
Reflection for HP .r1u Reflection for UNIX and OpenVMS .r2u Reflection for ReGIS Graphics .r4u
`çåÑáÖìêáåÖ=^ìíçã~íáÅ=réÇ~íÉë=çÑ=rëÉê=pÉííáåÖë=cáäÉë
You can use settings update files to configure ongoing, automatic updates of end-user settings. To do this, maintain a settings update file on a shared network server, and create end-user settings files that specify the location of the update file using the
Auto Update File setting (Setup > View Settings > Auto Update File). Reflection
checks for new settings in the update file each time the end user opens this settings file. You can use UNC path names or URLs to specify an update file located on a network server, as shown in these examples.
Sample UNC path:
\\MyServer\Reflection\Update Demo.rsu
Sample URL:
HTTP://Myserver.com/Update Demo.rsu
Note: By default, Reflection looks for a settings update file called Settings.r<n>u in the Reflection user folder. This means that you can place a settings update file in this default location and the updates will be applied automatically even if you have not explicitly specified a value for Auto Update File. For example, if you are running a default configuration of Windows XP or Windows 2000 and installed Reflection for HP using default values, Reflection will automatically check for updates in the following location:
C:\Documents and Settings\<user>\My Documents\Reflection\Settings.r1u You can change the default value of the Auto Update Setting using the “Folder for the default Auto Update file” Group Policy setting. See Chapter 4 for more information.
For more information about working with settings update files, including step-by-step
iáåâáåÖ=pÉííáåÖë=cáäÉë
Reflection for HP, Reflection for UNIX and OpenVMS, and Reflection for ReGIS Graphics support an advanced feature that lets you link partial settings files to complete settings files. This is useful if you want to:
• Share a partial settings file, such as a toolbar, among users of a variety of complete settings files. This way when you update the toolbar, the changes are automatically distributed to the linked complete settings files.
• Distribute some special settings, such as customized colors or mouse mappings, to a group of users.
• Keep partial settings files on a shared network drive so that users can link to them from their complete settings files stored on their local drives. Again, changes made to the partial settings file are automatically updated and distributed via the link.
Because linking is an option typically reserved for advanced users, the Link to file check box is hidden for convenience. To show this option, in the View Settings dialog box (Setup > View Settings), select the setting Show Link to File Check Box and change the value in the Setting details box to Yes. Now, when you use the Open Settings dialog box to load a partial settings file, you’ll see the Link to file check box.
For more information about working with linked settings files, see Linked settings files
i~óçìíë
If you frequently run two or more Reflection sessions simultaneously, you can use layout files to streamline your work. Layout files save your Reflection window arrangement. For example, if you regularly work with both an IBM and an HP host, you can create a layout to launch both sessions using your preferred arrangement. Layouts include all the saved Reflection sessions that are running when you create the layout. Layouts can include any combination of the following applications:
Reflection for HP
Reflection for UNIX and OpenVMS Reflection for ReGIS Graphics Reflection FTP Client
Reflection for IBM Reflection for Secure IT Reflection SFTP Client
To create a layout use File > Layout > Save Layout As.
Click the Shortcut button if you want to create a shortcut to open your layout. You can open layouts using shortcuts, or from a Reflection session using File > Layout > Open
Layout.
Layout files use an *.rlo file extension.
`çåîÉêíáåÖ=oÉÑäÉÅíáçå=pÉííáåÖë=íç=líÜÉê=cçêã~íë
You can convert Reflection settings to the following formats:• Reflection for the Web (*.config) files • XML Settings (*.xml)
jáÖê~íáåÖ=pÉííáåÖë=íç=~åÇ=Ñêçã=oÉÑäÉÅíáçå=Ñçê=íÜÉ=tÉÄ
Reflection for the Web provides easy and secure access to host applications from within a web browser. If you are currently using Windows-based Reflection applica- tions, you may find that you can reduce the cost of deploying and maintaining host access to some users by using Reflection for the Web. If you are currently using Reflection for the Web, you may want to install Windows-based Reflection on some workstations to take advantage of its full range of features. You can use the Reflection for the Web Adminstrative WebStation (described on page 59) to administer all of your Reflection sessions.Converting Reflection settings that are supported in both Windows and Web-based Reflection products is a simple, one-step process. To import Reflection for the Web files, you can use either of these methods:
• File > Open, then set Files of type to Reflection for the Web • File > Import and Export > Import XML
Reflection for the Web settings that can be converted are imported into your current session. To export supported settings to Reflection for the Web format, use File >
fãéçêíáåÖ=~åÇ=bñéçêíáåÖ=pÉííáåÖë=rëáåÖ=uji
Extensible Markup Language (XML) is an industry standard markup language for identifying and displaying structured information retrieved from a wide variety of applications. Reflection settings can be exported into XML and, in turn these Reflection settings can be openend in another Reflection session or displayed in a readable format. Exporting settings as XML allows you to take Reflection settings as a source, translate them using XSL stylesheets, and open them in Reflection as XML files (*.xml), or in Reflection for the Web as configuration files (*.config) to replicate the session. To do this, supply the basic information using options in the Reflection Export and Transform XML dialog box, where you can specify the source data for export, the output, the location to save the output file, and whether the resulting content should be automatically displayed.
Using Reflection data as the source, you can export:
• Current or changed settings: Your current Reflection settings.
• Screen data: Data from the Reflection terminal window and display memory. • Other: A prior Reflection session saved in XML format, filtered output, or
Reflection for the Web configuration file settings.
To transform your Reflection settings, use the Export and Transform XML dialog box (File > Import and Export > Export and Transform XML).
Note: This feature is not available in Reflection for Secure IT.