Reflection for the Web 7.0: Additional Help Topics
Technical Note 1802
Last Reviewed 09-May-2005
Applies To
Reflection for the Web version 5.x through 7.x
Summary
This technical note provides details for three topics in Reflection for the Web version 7.0: upgrading static sessions, upgrading external keyboard mapping files, and automatically starting and stopping the security proxy server on UNIX/Linux.
Upgrading Static Sessions to version 7.0
When Reflection for the Web terminal sessions are created or modified using the Session Manager (or the Terminal Session tool in earlier versions), the protected sessions are upgraded during the upgrade procedures when using auto-installer or during Startup (when the Tomcat server is started) after a manual installation.
Follow the steps in this section if any of these conditions exist:
- The sessions were not saved using Session Manager or the Terminal Session tool.
- The HTML in your sessions was manually modified.
- If you want to upgrade the static sessions for any reason.
Note: If you have keyboard map files that are not contained within a configuration file, then you must upgrade these files before you upgrade the sessions. First, follow the steps in Upgrading External Keyboard Map Files.
- Install Reflection for the Web version 7.0. See the Installation Guide for more information. (InstallGuide.html is located on the product CD.)
- Open a Command Prompt, and change directories to find this location:
<installation path>\ReflectionServer\jakarta-tomcat-<version number>\webapps\rweb\WEB-INF\lib>
- On the same command lineon one continuous lineenter the appropriate syntax (displayed below) to upgrade your specified configuration files. You must specify the items displayed in red:
- Language. On the command line, include the language you want use: German (de), English (en), French (fr), or Japanese (ja).
- Name of relative or absolute directory or file that contains the configuration files. (You must be able to access this file or folder from the machine where you are upgrading.)
If you are running the Microsoft JVM, enter this command as one continuous line:
jview -cp:p microstar.jar;RWebServlet.jar com.wrq.util.upgrade.ConfigUpgrade -locale <de|en|fr|ja> <file name|directory>
If you are running the Sun JVM, enter this command as one continuous line:
java -classpath microstar.jar;RWebServlet.jar com.wrq.util.upgrade.ConfigUpgrade -locale <de|en|fr|ja> <file name|directory>
Sample Command Line Entry
For example, if you are running the Sun JVM and you want to upgrade the configurations files in the session folder for use with the English version of Reflection for the Web, you would enter this information:
- In the Command Prompt, change directories to arrive at this location:
C:\Program Files\ReflectionServer\jakarta-tomcat\webapps\rweb\WEB-INF\lib>
- On the same continuous line, enter the command, language, and location of the session folder:
java -classpath microstar.jar;RWebServlet.jar com.wrq.util.upgrade.ConfigUpgrade -locale en C:\Program Files\Reflection Server\jakarta-tomcat\webapps\rweb\session
Upgrading External Keyboard Map Files
If you exported keyboard map files (using the Export Keymap command in the Reflection terminal session), then these keymap files are not contained in a configuration file and should be upgraded when you upgrade other files.
To upgrade Reflection for the Web keyboard map files:
- Create a temporary folder named KeymapConvert on your local computer for storing the files used in this procedure.
- In version 6.x: Open Administrative WebStation > Session Manager.
In version 5.x: Open Administrative WebStation > Deployment Director.
- Add a session of the type that matches the keyboard map you are upgrading, and name the session KeymapConvert.
- In version 6.x: Click Launch, and then click Import Keymap on the Administration menu.
In version 5.x: Skip to the Configuration tab, click Configure to start the terminal session, and then click Import Keymap on the Administration menu.
- Browse to the outdated keyboard map file, and click Open.
- In version 6.x: Close the session window, and then click Save/Exit.
In version 5.x: On the Configuration tab, click Save and Exit Session.
- Close Reflection for the Web.
- Your sessions will be upgraded when you upgrade to Reflection for the Web 7.0 and start the Reflection management server.
Automatically Starting and Stopping the Security Proxy on UNIX/Linux
Follow these steps to start or stop the proxy at system Startup or Shutdown.
- In a text editor, open SecurityProxy.sh, a shell script located in this folder:
<Reflection for the Web installation path>/securityproxy/bin/
- Edit the script to set the required variables described in the file:
WRQ_PROXY_HOME (must be an absolute path)
JAVA_HOME
- Save the revised SecurityProxy.sh and copy it to /etc/rc.d/init.d
- Modify the following steps according to your operating system.
- On SunOS 5.6 for instance, make a link to the copy from the /etc/rc3.d directory with a name S##SecurityProxy.sh, where ## is a unique number that follows a startup order of the scripts in the /etc/rc3.d folder.
- Make another symbolic link to the copy of this file from the /etc/rc2.d directory. The name of the link should be K##SecurityProxy.sh, where ## is a unique number that reflects a shutdown order of the scripts in the /etc/rc2.d directory.
As a result, when the UNIX/Linux system is started or shut down, the proxy server should automatically be started or stopped.
Related Technical Notes
| 9988 |
Reflection for the Web Technical Notes |