Information for Reflection X 14.1 Users Moving to Reflection X Advantage version 2.0 through 3.x
Technical Note 2390
Last Reviewed 12-Apr-2012
Applies To
Reflection X Advantage version 2.0 through 3.x
Summary

This technical note provides information about migrating from Reflection X 14.x (or earlier) to older releases of Reflection X Advantage.

Introductory List of Feature Differences

This section describes some of the first feature differences you may encounter when moving from Reflection X version 14.1 (or earlier) to Reflection X Advantage. Being familiar with these differences will help you get started using Reflection X Advantage.

Starting Servers and Clients

When you start Reflection X 14.1, the X server starts automatically and begins listening for incoming client connection requests. Because the server is already running you can start your X clients immediately.

When you start the Reflection X Advantage X Manager, the X server isn't started automatically. To start an X server, you need to start a session, You can do this by selecting a session name under "My Sessions" and clicking the green Start icon:

2390_0.gif

Once you've started your session, you can start your X clients.

Note: You can also configure Reflection X Advantage sessions to start one or more clients automatically as soon as the X server is running. Using this approach means that launching your X clients can still be a one-step operation.

Window Mode

In Reflection X 14.1, clients are displayed on the desktop by default. In Reflection X Advantage, X clients are displayed in an X terminal window by default, and XDMCP sessions must run this way. If you prefer to display clients in their own desktop windows, you can use either of the following approaches:

  • If you don't run XDMCP sessions:

In the left pane, select the X server definition you are working with. The default is named "Generic X Server." In the right pane under Windowing, select "Show clients on my desktop."

  • If you run both XDMCP sessions and individual X client sessions:

Create two X Server definitions, one with "Show clients on the X terminal desktop" selected and one with "Show clients on my desktop" selected. Use the X terminal desktop server for XDMCP sessions and the clients-on-desktop server for individual clients. (Note: If you have migrated Reflection X settings, servers with these options are created for you automatically, as needed, during the migration.)

User-based Security

User-based security is disabled by default in Reflection X 14.1, but enabled by default in Reflection X Advantage to provide greater security. This is an important difference if you like to launch X clients from a secondary tool such as Reflection for UNIX and OpenVMS or Reflection Workspace. When user-based security is enabled, X clients launched this way will be denied access and nothing will be displayed.

You can obtain your X client displays when using Reflection X Advantage by either of the methods below:

  • Launch your X clients from Reflection X Advantage instead of a secondary tool (more secure).
  • Disable “User-based authorization” in the session definition under Network Security (less secure).

Migrating Reflection X Settings to Reflection X Advantage

Note: This technical note describes migration to Reflection X versions 2.0 and 3.0. Starting with Reflection X Advantage version 4.0 (available in Reflection X 2011 and Reflection Suite for X 2011), the migration utility includes new features that make it easier to use your migrated settings. We recommend upgrading to the latest version of Reflection X Advantage before you migrate. (See Technical Note 2620.)

The first time you start Reflection X Advantage, you'll see a prompt asking if you want to import your settings. Click Migrate to import your settings. Your Reflection X files are not changed. Imported settings appear as a combination of session, client, and server definitions.

Understanding Migrated Reflection X Server Settings

Settings that you configure for an X server instance in Reflection X are migrated to both server definitions and session definitions in Reflection X Advantage.

For example, when the default “config” server instance is migrated, the results include both a server definition called “config” and a session definition called “config.” The session called config is configured to start the server of the same name.

Understanding Migrated Reflection X Client Settings

After migration, your original Reflection X client files (*.rxc) remain unchanged. The imported settings are saved within your Reflection X Advantage database.

Settings from Reflection X client files are migrated differently, depending on whether the file configures Client Startup or uses XDMCP.

  • Client Startup clients are migrated to Reflection X Advantage client definitions. To start a migrated client, you can start a session, and then start your client. Or, you can add the client to a session definition, and then start the session.
  • XDMCP clients are migrated to Reflection X Advantage session definitions. Launching the migrated session starts the migrated “config” server and initiates the XDMCP connection.

Note: In Reflection X, the “config” server is configured by default to display clients on the Windows desktop. If you used this default value for desktop display in Reflection X, you'll see the following error when you start your migrated XDMCP session in Reflection X Advantage:

"XDMCP cannot be used in conjunction with the 'Show clients on my desktop' feature selected in the server definition."

To resolve this error, you can use either of the following approaches:

    • Modify the migrated config server. Under Windowing, select Show clients on X terminal desktop.
    • Modify the migrated XDMCP client session. For Use X Server, specify the default “Generic X server” or another server that is configured to use Show clients on X terminal desktop.
Related Technical Notes
2234 Reflection X Advantage Technical Notes
2620 Information for Reflection X 14.1 Users Moving to Reflection X 2011

Did this technical note answer your question?

           



Need further help? For technical support, please contact Support.