From 5d4c83c2e4bd11c683896a0a194da5058642fb11 Mon Sep 17 00:00:00 2001 From: David Dykstal Date: Mon, 31 Jul 2006 13:29:50 +0000 Subject: [PATCH] Bug 146839 - updating install instructions --- .../tasks/tbeginlinux.html | 93 ++++++++----------- .../tasks/tbeginwindows.html | 54 +++++------ 2 files changed, 62 insertions(+), 85 deletions(-) diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html index 464bf26b00b..4f5e1cac966 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html @@ -20,40 +20,39 @@ or UNIX server.

Prerequisites

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.Also note that Java Development Kit (JDK) -version 1.4 or higher is required.

+when you connect to the server.

Installing the server code

    -
  1. Ensure that Perl is installed.
    2. -
  2. Ensure that JDK version 1.4 or higher is installed.
    3. -
  3. Create a directory where you want to install the server code. The remainder +
  4. +Find the package that contains the server. +The server code is usually packaged with the containing product and you should refer to that +product's documentation for finding and installing the server package. +The server is also available, however, on the Eclipse DSDP Target Management download site as the package +rseserver-<version>-<os>.tar. For example, rseserver-1.0-linux.tar contains the release 1.0 server +for Linux. There are servers for Linux, AIX, a generic Unix version that can be tailored to your particular flavor +of Unix, and an experimental Mac OS X version.
    5. +
  5. Ensure that Perl is installed.
    6. +
  6. Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed.
    7. +
  7. Create a directory where you want to install the server code. The remainder of these instructions will assume the directory /opt/rseserver (suitable for team sharing), but you are free to use any directory.
    8. -
  8. Find the x:\product directory\eclipse\plugins\com.ibm.etools.systems.universal_version_number\serverruntime\rseserver.jar -file on your local workstation, where x:\product directory is the directory -where you installed the product, for example, c:\WSWB.
    9. -
  9. FTP the file rseserver.jar to the /opt/rseserver directory.
    10. -
  10. Switch to the /opt/rseserver directory by typing: - 
    cd /opt/rseserver
    -
    11. -
  11. Run the following command in the /opt/rseserver directory to extract the -server code:
    jar -xf rseserver.jar
    - Attention: The -jar command is shipped with the JDK and might not be in your path. If you -receive a "command not found" error when running the jar command then try -to qualify the jar command with the installation directory for the JDK. For -example: /opt/IBMJava2-131/bin/jar -xf rseserver.jar -
    -
    -
    12. -
  12. Still in the /opt/rseserver directory, run the following configuration -commands:
    dos2unix daemon.linux
-dos2unix server.linux
-chmod 755 server.linux
-chmod 755 daemon.linux
-chmod 755 auth.pl
    -
    13. +
  13. Upload the server package to this directory. You can use FTP.
    14. +
  14. Switch to the /opt/rseserver directory by typing: +
    cd /opt/rseserver
    +
    15. +
  15. Run the following command in the /opt/rseserver directory to extract the +server code from the package appropriate to your operating system. For linux this command is: +
    tar -xf rseserver-1.0-linux.tar
    +
    16. +
  16. Still in the /opt/rseserver directory, run the following configuration +commands: +
    +chmod 755 server.pl
+chmod 755 daemon.pl
+chmod 755 auth.pl
+
    +
@@ -70,42 +69,27 @@ Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxppc321411-20040301 (JIT enabled:
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-131/jre/bin/java /usr/bin/java
+to the java command in /usr/bin by running the following command:
ln -s  /opt/IBMJava2-141/jre/bin/java /usr/bin/java
To start the server with the server daemon
    -
  1. Ensure that you are running using the root user ID. (If the daemon is +
  2. 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.linux
    +perl ./daemon.pl
Note that the server daemon runs on port 4035. You can also start the daemon.unix in the same way.

-

To start the Linux server manually

+

To start the server manually

Run the following commands:
cd /opt/rseserver
-perl ./server.linux [port]
-These commands run the server.linux +perl ./server.pl [port] +These commands run the server.pl script located in the /opt/rseserver directory. If this does not work, try -changing the permission attributes on server.linux (for example, enter chmod -755 server.linux. The port parameter to the server.linux 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.
-

To start the UNIX server manually

-
To run the unix.server -script, enter the following commands:
cd /opt/rseserver
-perl ./server.unix [port]
-These commands run the server.linux -script located in the /opt/rseserver directory. If this does not work, try -changing the permission attributes on server.unix (for example, enter chmod -755 server.unix. The port parameter to the server.unix script is +changing the permission attributes on server.pl (for example, enter chmod +755 server.pl. 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 @@ -118,9 +102,8 @@ property.
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.linux &
-You can also add perl ./daemon.unix if -you want to run the UNIX daemon at startup.
+perl ./daemon.pl & +

Connecting to the Remote Server

diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html index 88a39d4ad48..b5244044243 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html @@ -14,41 +14,35 @@

Connecting to a remote Windows server

-

Installing the server code:

+

Installing the server code

    -
  1. Create a directory where you want to install the server code. The +
  2. +Create a directory where you want to install the server code. The remainder of these instructions will assume the directory name and location is -C:\rseserver, but you are free to use any directory you choose.
    3. -
  3. Find the x\eclipse\plugins\com.ibm.etools.systems.universal_version_number\serverruntime\rseserver.jar -file on your local workstation, where x is the directory where you -installed the product.
    4. -
  4. Copy the rseserver.jar to the C:\rseserver directory (this can be -on a different machine).
    5. -
  5. Open a command prompt, and run the following command in the -C:\rseserver directory to extract the server code: -
    jar xf rseserver.jar
    -
    If -you receive an error, ensure that you have an entry for the /bin JDK -directory in your Path environment variable. JDK version 1.4 is required.
    -
    6. +C:\rseserver, but you are free to use any directory you choose. +
  6. Find the package that contains the server. +The server code is usually packaged with a containing product and you should refer to that +product's documentation for finding and installing the server package. +The server is also available, however, on the Eclipse DSDP Target Management download site as the package +rseserver-<version>-<os>.zip. For example, rseserver-1.0-windows.zip contains the release 1.0 server +for Windows.
    7. +
  7. Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).
    8. +
  8. Using an unzip utility to extract the server code to the C:\rseserver directory.
-

Starting the server:

-

You can start the RSE communications -server with the server manually, or with a daemon.

-
To start the server -manually: +

Starting the server

+

You can start the RSE communications server with the server manually, or with a daemon.

+
To start the server manually:
    -
  1. First, you need to configure your CLASSPATH and then start the -communications server. In a command prompt, enter: +
  2. Configure your CLASSPATH and then start the communications server. In a command prompt, enter: 
     c:
    
-cd:\rseserver
    
-win.env.bat
    
-run.win.bat [port]
+cd \rseserver
    
+setup.bat
    
+server.bat [port]
    -The port parameter to the run.win.bat program is optional. If +The port parameter to the server.bat program is optional. If you do not specify a port, the server will pick the first port available and print the port number to standard out. By default, it is usually 4033. You will then have to enter this port number in the port property for the @@ -64,13 +58,13 @@ server daemon. In a command prompt, enter: 
     c:
    
 cd:\rseserver
    
-win.env.bat
    
-daemon.win.bat
+setup.bat
    
+daemon.bat
    Note that the server daemon does not enforce any user authentication. If you run the server daemon, any user can connect to the machine, work -with the file system and run commands. Use -of the server daemon on Windows systems is not recommended.
    3. +with the file system and run commands. +Use of the server daemon on Windows systems is not recommended.