Build Notes for RSE @buildId@
@dateLong@

• RSE ssh feature now supports connections via Proxy.
  • Re-uses ssh Preferences from Team > CVS > SSH2 Connection Method, and Team > CVS > Proxy Settings.
  • Ssh private key authentication is supported, but RSE requires entering a dummy password (bug 142471). As an alternative, passwords can also be maintained by RSE.
• Documentation is now available. Note that this documentation partially still refers to the older IBM RSE product and thus contains lots of outdated references.
• The New Connection Wizard is now completely replaceable for contributed system types. As a side effect of this, the ordering of subsystems for a connection may change (bug 149280).
• Use this query to show the list of bugs fixed for this build.
• Look here for the CVS changelog.

Download RSE SDK, and either

• Extract it into your installation of Eclipse 3.2, or
• Extract it into an empty directory and link it as product extension via Help > Install/Update, or
• (If you want to write code for RSE) extract it into an empty directory, and from an Eclipse PDE Workspace choose Import > Plug-in development > Plug-ins and Fragemtns. Select the RSE directory and import everything.

Even without an actual connection to a remote system, you can start experimenting with the RSE UI on the local host, which is shown by default:

• Browse the Filesystem, choose contextmenu > show in Table, and observe the Properties view
• Create a new Filter to show specific resources in the file system only
• Launch an RSE Shell (Shells node > Launch)

• use the "SSH Only" system type (New > Other > Remote Systems Explorer > Connection), or
• start a dstore server daemon on the remote system and use any of the other connection types.

RSE is a framework that supports plugging in many different communication protocols. By default, the dstore, FTP and ssh protocol plug-ins are provided, with dstore being the most richest in features.

Dstore requirs a server to run on the remote system. There are several methods to get a server launched for a particular user, the most easy one to set up is the daemon method. To start a dstore launcher daemon,

• On Windows:
  • Extract the rseserver-*-windows.zip package and cd to it.
  • Run setup.bat, then run daemon.bat.
• On Linux or AIX or other Unix:
  • Extract the appropriate rseserver-*.tar package.
  • Become root and cd to the package directory.
  • Make sure that a Sun or IBM JRE 1.4 or higher is in the PATH. The gcj-based java installation that comes with many Linux distributions will not do! You can download a Sun JRE from http://java.sun.com.
  • Run perl daemon.pl.

Note: In its default configuration for testing, the dstore daemon accepts unencrypted passwords from the RSE client. For production use, SSL can be enabled in order to encrypt connections, or the RSE server can be launched differently (e.g. through ssh).

When no root access is available on the remote system (typically UNIX), normal users can start a dstore server for themselves only, instead of a daemon:

• On the remote system, run perl server.pl [portname]
• On the RSE client, create the dstore connection
• After creating the connection, select it and choose Properties
  • On Server Launcher Settings, choose Connect to Running Server
  • On the Subsystem page, enter the port number you used for starting the server
• When connecting, enter just anything for username and password (these will be ignored).
• The server.pl script has more options, e.g. for using the first available port instead of a well-known one, or for restricting access to a single user ID. Since all dstore communication will be on the single TCP port, this port can also be forwarded through an ssh tunnel if desired.

• In the RSE Perspective, Remote Systems View, press the New Connection button.
  • Note: In the Preferences, you can enable displaying available new connection types in the RSE tree.
• Select the desired system type
  • Coose system type "SSH Only" for ssh servers, or any other for dstore.
• Enter an IP address for a remote system running an ssh server or dstore server. A connection name will be suggested automatically, but can be changed.
  • You can also run a dstore server on the local machine for testing. In this case, type "localhost" as address.
  • You can press Finish right away, the wizard defaults are usually fine.
• Fill in the username / password dialog.
  • Note: For ssh, if you have private keys, the password here is just a dummy. Enter anything and save it. You can setup ssh private key authentication through the Team > CVS > SSH2 Connection Method Preference page.
• Browse remote files, or open remote shells.
  • You can drag and drop files between local and remote file systems, between editors and any view. Files are transferred as needed.
  • On dstore, you can browse into remote archives (*.zip, *.tar) without having to transfer the entire contents. This works thanks to "miners" on the remote side. Custom miners can be plugged into the dstore server.
    Note: Some tar formats currently fail to work. See bug 139207.
  • On dstore, when you list directories in a remote shell, the shell output is parsed to identify files, folders and even line numbers from compiler error messages. These items can also be dragged and dropped, or double clicked to position an editor on them.
• On dstore, you can choose Search > Remote....
  • The dstore miners support searching a remote file system without having to transfer any data.
• On dstore, when the remote system is Linux, AIX or Other Unix:
  • Browse remote Processes.
  • Select "My Processes" and choose context menu > Monitor.
  • Enable polling, choose a short wait time. See processes appear and vanish as you perform commands in a remote shell.

• User Actions, and Import/Export were deferred. A new plan will be published.
• JUnit tests did not make it into the build due to pending IP review. They are available from Bugzilla bug 149080 instead.
• Examples are not yet available as downloadable package. A CDT Launch Integration Example and a sample custom subsystem called Daytime Example are available from the RSE CVS Repository instead.

• bug 149186 - maj - downloading in background can truncate the remote file
  -- In order to avoid this bug, do not put any data transfer into background.
• bug 143462 - maj - [updating] Dirty remote editors do not get notified
• bug 143292 - maj - [mac] Move Resource dialog causes hang/crash
• bug 139207 - maj - Browsing into some remote tar archives fails, and may crash the dstore server
  -- This problem was only observed with invalid tar archives.