Reflection Administrator 2011
Reflection Administrator 2008
Reflection for the Web 2014 (All Editions)
Reflection for the Web 2011 (All Editions)
Reflection for the Web 2008 (All Editions)
Reflection for IBM version 14.x
Reflection for UNIX and OpenVMS version 14.x
Reflection for HP with NS/VT version 14.x
Reflection for Secure IT Windows Client
This technical note explains how to use the Auto Update feature to centrally update and deploy changes to Reflection settings files using Reflection for the Web or Reflection Security Gateway. This feature can be used with these Windows-based applications: Reflection for IBM, Reflection for HP, Reflection for UNIX and OpenVMS, or Reflection for Secure IT Client for Windows.
With this feature, a settings update file is maintained in a central location. Whenever users launch a session, Reflection automatically incorporates any changes you saved to the central settings update file.
Configuring Automatic Updates for Sessions Not Yet Created
Follow these steps to automatically update the settings files in any new Reflection sessions that you might add later.
- Open the Administrative WebStation and click Settings in the navigation panel.
- On the General tab, select the check box to "Enable auto update when creating Windows-based Reflection sessions" (next to "Auto update files for Windows-based Reflection").
- In the "Location of auto update files" box, enter the URL or path to the folder you will use to store auto update files. The folder must be accessible to users running the applicable Windows-based Reflection sessions.
You can use a URL, a UNC path, or a mapped network drive. For example:
By default, each settings update file is assigned the same name as your Reflection session, followed by the appropriate file extension for updates in that session type. For example, if you add a new Reflection for IBM session called Joe and you set "Location of auto update files" to S:\rweb\, the session will look for updates in S:\rweb\Joe.rsu.
- Click Save Settings.
The result: When you create a new Windows-based Reflection session using the Administrative WebStation, the changes saved to the settings update file are automatically incorporated when the session is launched.
Enabling Automatic Updating in Existing Sessions
Follow these steps to configure automatic updates for an existing Reflection session.
- Launch the Administrative WebStation and open the Session Manager.
- Click the session you want to edit.
- Decide whether or not to change your selection about overwriting end user files. Click Launch.
Note: If overwriting of end-user settings files is not enabled, changes to the auto update settings may not get pushed out to some end user machines.
- In the Reflection session, go to Setup > View Settings, then search for Auto Update File.
- Under Settings details, enter the location of the settings update file. (This can be a UNC path or a URL.) For more information, click the Settings Help button.
- Click OK to close the View Settings dialog box.
- On the File menu, click Save to save this change.
Creating and Modifying a Settings Update File
Settings update files contain information about specific settings only. Whenever users launch sessions that have been configured to use Auto Updates, Reflection automatically incorporates the changes you saved to the settings update file.
To create or modify a settings update file:
- On the administrative workstation, use the Windows Start menuânot the Administrative WebStationâto launch a new (untitled) Windows-based session for any of these Reflection applications: Reflection for IBM, Reflection for HP, Reflection for UNIX and OpenVMS, Reflection for ReGIS Graphics, or Reflection for Secure IT Client for Windows.
- Configure just those settings you want to incorporate into the end user's settings files.
- Click File > Save As and select Settings update from the "Save as type" list.
- Enter the name and location of the auto-update files that you specified earlier in the Administrative WebStation (step 3 in Configuring automatic updates for sessions not yet created.)
- Save the file, and then copy it to a network folder where it is accessible to clients.