How to Access Linux server Remote?
To use the Remote System Explorer communications server daemon you need to install Perl. Using the daemon helps eliminate some of the manual steps when you connect to the server.You can start the RSE communications server with the server daemon, or manually. Before starting the server, make sure the Java command is in your path, you can do this by running the following command:
java -versionYou should see something similar to the following:
java version "1.4.1" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1) Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxppc30301 (JIT enabled: jitc))If you receive a "command not found" error, then try creating a symbolic link to the java command in /usr/bin by running the following command:
ln -s /opt/IBMJava2-141/jre/bin/java /usr/bin/javaTo start the server with the server daemon
- Ensure that you are running using the root user ID. (If the daemon is not run under root, it will be unable to authenticate connecting users.) Run the following commands:
su -l root cd /opt/rseserver perl ./daemon.pl [daemonPort] [serverPortRange]
If your daemon runs behind a firewall, you may want to specify the optional serverPortRange argument to restrict selected server ports to the range given:
perl ./daemon.pl 4075 0
To start the server manually
Note: In the following discussion we assume that the RSE server has been installed on Linux. If you are running on a UNIX system the script name is "server.sh" rather than "server.pl".If you do not have root access on a remote machine, you can start the server manually for your particular user id only. Run the following commands:
cd /opt/rseserver perl ./server.pl [port] These commands run the server.pl script located in the /opt/rseserver directory. The port parameter to the server.pl script is optional. If you do not specify a port, then the server will pick the first one available and print the port number to standard out. By default, it is usually 4033. If you would like to use a different port, you will then have to enter this port number in port property for the Files subsystem for your connection in the Remote System Explorer (see Connecting to the Remote Server, below). Otherwise, you do not need to change this property.
Note: When you connect RSE to the server, the server will terminate as soon as you disconnect the client. The daemon, however, will not terminate.
Rexec Server Launcher
If you have Rexec access enabled to your remote system, you can also have the server started automatically by an Rexec command from the client, when you connect. To do so, use the Server Launcher Properties in the New Connection Wizard.
Running the daemon at startupYou might instead want to configure the daemon to run at start up for Linux. To do so, you need to append a call to the daemon to your startup script. Add the following lines to the bottom of the /etc/rc.d/rc.local file:
cd /opt/rseserver perl ./daemon.pl &
SSL Encryption and FirewallsBy default the RSE DStore connection is unencrypted. You can, however, configure it to use SSL encryption.
Because all dstore data transfer is done through a single TCP/IP connection, the connection can also be tunneled through an ssh channel. In fact, the same ssh channel can also be used to start the server, like in the following example:
ssh -l moberhuber build.eclipse.org -L27127:build.eclipse.org:27127 \ "sh -c 'cd ~/rseserver/latest; perl ./server.pl 27127'"
Here, the RSE Server is started on port 27127 through an ssh connection, and at the same time port 27127 is forwarded through ssh to the local host. You can now connect RSE to localhost:27127, and the connection will transparently be forwarded to the remote system.