Technical Notes |
|
Reflection X version 11.0 or higher enables you to create and run concurrent X server instances whose registry-based settings can be exported and shared with other users. You do this by creating a Windows shortcut that references a server instance (*.rxs) and a client connection (*.rxc) file. When double-clicked at a second machine, the shortcut updates the registry and starts the server instance and client under the X Manager.
This technical note describes how to create and export the X server setting, associate it with a client connection, and create the shortcut to start the two in the X Manager. The Windows shortcut you create can then be distributed for use by end users in any fashion available to you, including using Reflection Customization Manager.
For details on getting started with multiple X server instances, see Technical Note 1751.
The example in this technical note follows three steps to share multiple X server instances with other users:
In this section, you will create and optionally customize an X server instance, and then export the settings to an *.rxs file.
There are two ways to create a new X server instance. You can use one of the X server templates provided with Reflection X, or you can create and customize a new instance without using a template. Choose your preferred method and follow the corresponding steps to create and export the instance.
The new server instance inherits the settings of the active server and appears in the Reflection X Manager's list of X Server Instances.
When prompted to complete the conversion, click Yes; then click OK in the confirmation box.
When prompted to complete the conversion, click Yes; then click OK in the confirmation box.
Follow these steps to associate a client connection with the currently-running server instance (from the steps above). Then, save this association in a Windows shortcut.
The shortcut you have created above references both the client connection and the server instance files. This means that this combination of server and client will start when the shortcut is double-clicked and the X Manager starts. However, you will need to remove machine-specific references in order to share this shortcut with other users. Follow the steps below to do this.
You now need to edit the X Server instance to remove machine-specific information so that the shortcut can be shared with other users.
DetectedLocalAddress=150.123.45.67
To add the path and file extension, change this reference (-s "serverinstance") to include the full path to the file:
-s "C:\Documents and Settings\<user>\My Documents\Reflection\serverinstance.rxs"The Windows shortcut can now be distributed using whatever deployment mechanisms are available. This might be as simple as email or more complex, involving for example Active Directory or SMS.
Note: When deploying shortcuts, the associated RXS and RXC files must be located on a shared server or distributed with the shortcut.
The shortcut can also be made available to an end user through Reflection Customization Manager (called Reflection Deployment Manager in versions earlier than 12.0). This is done using Customization Manager's Edit Product Shortcuts feature that enables you to add a shortcut to your customized installation of Reflection X (in this case, the shortcut is the one created above). When this shortcut is double-clicked on the end user's machine, the server settings are imported into the user's registry, Reflection X Manager starts, and the server instance and client connection is executed.
For more information, see the Reflection Deployment Guide, available at http://www.attachmate.com/docs/reflection/14.0/deploy.pdf.
Whenever the Windows shortcut you have created starts the X Manager the information in the server instance (*.rxs) and client connection (*.rxc) files is re-read and any changes applied to the machine's registry. This means that an administrator can update the server instance and client connection files and have these updates appear when the shortcut is double-clicked at the end user's machine.
To do this, edit the shortcut's Target field to reflect an identical shared network folder for both of these files. Be sure that each user's machine shares identically mapped drives or Universal Naming Convention (UNC) mapping as noted above.