diff --git a/rse/doc/org.eclipse.rse.doc.user/build.properties b/rse/doc/org.eclipse.rse.doc.user/build.properties index 80ac7cc0c67..4c488439d1b 100755 --- a/rse/doc/org.eclipse.rse.doc.user/build.properties +++ b/rse/doc/org.eclipse.rse.doc.user/build.properties @@ -8,5 +8,6 @@ bin.includes = META-INF/,\ tasks/,\ book.css,\ notices.html,\ - toc.xml + toc.xml,\ + gettingstarted/ \ No newline at end of file diff --git a/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html b/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html index d9ef6ed69b1..c8197d7307e 100755 --- a/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html +++ b/rse/doc/org.eclipse.rse.doc.user/concepts/cfilters.html @@ -98,10 +98,12 @@ you can always create a new profile. See the related links for more information.

+

Related Tasks
Configuring filter pools
- - - - - - -Team support - - - -

Team support

-
-

The team support model works with shared repositories that store -version-managed resources on servers that are accessible to the entire team. Usually -you would share the folders and files of an Eclipse project.  Each -team member sends their changes to the repository, and receives changes -that -were made by a team member from the repository. While the Remote System -Explorer -is not project-based, (it is designed for direct access to remote -resources), -there is a single project created for all the non-remote resources that -the -Remote System Explorer manages. Profiles are stored in that project and -so everything that belongs to a profile can be -shared with your teammates.

-
Profiles -contain: -
    -
  • Connections -- including various subsystem properties. User IDs -and passwords are not shared.
    • -
  • Filters, filter pools, and filters pool references
    • -
  • User-defined actions
    • -
  • Compile commands
    • -
-
-

Use the Team view of the Remote System Explorer perspective to -associate -and synchronize the project named RemoteSystemsConnection that contains -these profiles with a repository. After -synchronizing with the repository, you will receive all the shared -Remote System -Explorer resources from your team, including their profiles. You then -use the Reload Remote System Explorer action, located on the -pop-up menu, to make the Remote Systems Explorer know about these -changes.  You can also, of course, quit and restart the -workbench.  See the related tasks for more information.

-

Any resources received that are in a profile that you have already -active, such -as Team, will immediately be available and accessible to you. However, -resources -in other profiles will not be available unless you choose to make those -profiles -active. If you use multiple workstations, team support can also be used -to -make your own private configurations of filters, filter pools, and -connections available on all the workstations by making -your profile active on each workstation.

-
-
-

Related concepts
-Remote System Explorer Profiles
-

-

Related tasks
-Using team support
-Working with profiles and team support
-

-
- - + + + + + + + +Team support + + + +

Team support

+
+

The team support model works with shared repositories that store +version-managed resources on servers that are accessible to the entire team. Usually +you would share the folders and files of an Eclipse project.  Each +team member sends their changes to the repository, and receives changes +that +were made by a team member from the repository. While the Remote System +Explorer +is not project-based, (it is designed for direct access to remote +resources), +there is a single project created for all the non-remote resources that +the +Remote System Explorer manages. Profiles are stored in that project and +so everything that belongs to a profile can be +shared with your teammates.

+
Profiles +contain: +
    +
  • Connections -- including various subsystem properties. User IDs +and passwords are not shared.
    • +
  • Filters, filter pools, and filters pool references
    • +
  • User-defined actions
    • +
  • Compile commands
    • +
+
+

Use the Team view of the Remote System Explorer perspective to +associate +and synchronize the project named RemoteSystemsConnection that contains +these profiles with a repository. After +synchronizing with the repository, you will receive all the shared +Remote System +Explorer resources from your team, including their profiles. You then +use the Reload Remote System Explorer action, located on the +pop-up menu, to make the Remote System Explorer know about these +changes.  You can also, of course, quit and restart the +workbench.  See the related tasks for more information.

+

Any resources received that are in a profile that you have already +active, such +as Team, will immediately be available and accessible to you. However, +resources +in other profiles will not be available unless you choose to make those +profiles +active. If you use multiple workstations, team support can also be used +to +make your own private configurations of filters, filter pools, and +connections available on all the workstations by making +your profile active on each workstation.

+
+
+

Related concepts
+Remote System Explorer Profiles
+

+

Related tasks
+Using team support
+Working with profiles and team support
+

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html new file mode 100644 index 00000000000..e04920c8c04 --- /dev/null +++ b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g1installing.html @@ -0,0 +1,48 @@ + + + + + + + +Installing the RSE + + + +

Installing the Remote System Explorer

+
+The simplest way to get RSE is via the Update Manager: From your running instance +of Eclipse 3.2, choose Help > Software Updates > Find and Install.... +Choose "Search for New Features to Install", and add a new Remote Site named +"RSE" and pointing to +http://download.eclipse.org/dsdp/tm/updates/. +Select the RSE SDK feature, and perform the update process as usual.

+ +

If you prefer manual installation, you can download RSE SDK from the +DSDP Target +Management Download Site and extract it into your installation of +Eclipse 3.2 or later, or link it as product extension. +

Start Eclipse Workbench, and choose Window > Open Perspective > +Other > Remote System Explorer.

+
+ +
+ +

Follow-up tasks
+First Steps with the Remote System Explorer
+ +Using Remote System Explorer Connections
+

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html new file mode 100644 index 00000000000..6d97ee0e2be --- /dev/null +++ b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g2firststeps.html @@ -0,0 +1,59 @@ + + + + + + + +First Steps with RSE + + + +

First Steps with the Remote System Explorer

+
+Even without an actual connection to a remote system, you can start experimenting +with the Remote System Explorer UI on the local host, which is shown by default +under the Local node: + +For operations on an actual remote system, you can either + +

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 richest in features.
+Dstore requires 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.

+
+ +
+

Follow-up tasks
+Using Remote System Explorer Connections
+

+

Related concepts
+Remote System Explorer Connections
+Remote System Explorer filters, filter +pools, and filter pool references
+Universal Systems
+Connecting to a remote +Linux or UNIX server
+Connecting to a remote +Windows server
+

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html new file mode 100644 index 00000000000..c4ed4c896d7 --- /dev/null +++ b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/g_start.html @@ -0,0 +1,55 @@ + + + + + + + +Getting Started with RSE + + + +

Getting Started with the Remote System Explorer

+
+

The Remote System Explorer (RSE) is a perspective and toolkit in Eclipse +Workbench, that allows you to connect and work with a variety of remote +systems. With the predefined plug-ins, You can look at remote file systems, +transfer files between hosts, do remote search, execute commands and work +with processes.

+

Additional capabilities may be added by Software Vendors by providing new +System Types, Services and Subsystem implementations +for specific remote access protocols or resource kinds respectively. The framework +helps by providing lots of predefined re-usable components, like persistence +mechanisms, filtering and team sharing.

+ + +A sample RSE session
+ +

Here is a screenshot of a sample session with RSE (Click on the picture to +enlarge it). +This tutorial will guide you quickly through the most prominent features of +the Remote System Explorer: +

+ +
+ +
+

Related concepts
+Remote System Explorer Connections
+

+ +
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html new file mode 100644 index 00000000000..f74b44e338d --- /dev/null +++ b/rse/doc/org.eclipse.rse.doc.user/gettingstarted/gusing.html @@ -0,0 +1,66 @@ + + + + + + + +Using Remote Connections + + + +

Using Remote Connections

+
+Here are a few tasks that help you get acquainted with RSE. All tasks assume that you have +switched to the Remote System Explorer Perspective in your Workbench. Some of the tasks +can not be performed on all system types, although RSE tries to provide a consistent UI +across many different kinds of remote systems.. +
+ +
+

Related concepts
+Remote System Explorer Connections
+Remote System Explorer filters, filter +pools, and filter pool references
+Shells and commands in the +Remote Systems view
+

+

Related tasks
+Connecting to a remote +Linux or UNIX server
+Connecting to a remote +Windows server
+Running and viewing +commands and shells using the Remote Commands view
+

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif b/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif new file mode 100644 index 00000000000..4ddb991f3e1 Binary files /dev/null and b/rse/doc/org.eclipse.rse.doc.user/images/RSESample.gif differ 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 4f5e1cac966..d24a99578c9 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginlinux.html @@ -1,148 +1,165 @@ - - - - - - - - -Connecting to a remote Linux or UNIX server - - - - -

Connecting to a remote Linux or UNIX server

-

The following documentation explains how to install the Linux or UNIX server -code, start the server daemon, and make a connection to a remote Linux -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.

-

Installing the server code

-
-
    -
  1. -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.
    2. -
  2. Ensure that Perl is installed.
    3. -
  3. Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed.
    4. -
  4. 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.
    5. -
  5. Upload the server package to this directory. You can use FTP.
    6. -
  6. Switch to the /opt/rseserver directory by typing: -
    cd /opt/rseserver
    -
    7. -
  7. 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
    -
    8. -
  8. Still in the /opt/rseserver directory, run the following configuration -commands: -
    -chmod 755 server.pl
-chmod 755 daemon.pl
-chmod 755 auth.pl
-
    -
    9. -
-
- -

Starting 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 -version
-
-
You 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 cxppc321411-20040301 (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/java
-
-
To start the server with the server daemon -
    -
  1. 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
    -
    2. -
-Note that the server daemon runs on port 4035. You can also start the -daemon.unix in the same way.

-

To start the server manually

-
Run -the following commands:
cd /opt/rseserver
-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.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 -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.
-

Running the daemon at startup

-
You 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 &
-
-
-


-

Connecting to the Remote Server

-
To make a connection -to your remote server:
-
    -
  1. Switch to the Remote System Explorer perspective. From the workbench -menu, click Window > Open Perspective > Remote System Explorer.
    2. -
  2. In the Remote Systems view, New Connection is automatically -expanded to show the various remote systems you can connect to through the -Remote System Explorer. Expand Linux or Unix to -invoke the new connection dialog box and configure a connection.
    3. -
  3. Enter a name for your first profile and click Next. (This -step only occurs if you have never defined a connection before.)
    4. -
  4. Enter a connection name. This name displays in your tree view and -must be unique to the profile.
    5. -
  5. Enter the name or TCP/IP address of your Linux server in the Host -name field, for example, LINUX_A.
    6. -
  6. (Optional) Enter a Description. The description appears -in the Properties view after the connection is created.
    7. -
  7. Click Finish to define your system.
    8. -
-
-
Attention: To check your port number, right-click your -connection or subsystem from the Remote Systems view and select Properties. -Click Subsystem to view the relevant information. If your port is "0," -then your Remote System Explorer communications server will pick any free -port on the server. If you specified a port number when starting the server, -you need to enter it here, for example, to work with a firewall.
-
-
-
-
-
-
-

Related tasks -Connecting to a remote Windows -server -

-
- - + + + + + + + + +Connecting to a remote Linux or UNIX server + + + + +

Connecting to a remote Linux or UNIX server

+

The following documentation explains how to install the Linux or UNIX server +code, start the server daemon, and make a connection to a remote Linux +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.

+

Installing the server code

+
+
    +
  1. +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.
    2. +
  2. Ensure that Perl is installed.
    3. +
  3. Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed. +An IBM, Sun or equivalent JRE is required; The gcj-based jvm shipped with most Linux +distributions does not work. If in doubt, run the command
    java -version (see +below) and check if there is a reference to gcj. You can download a Sun JRE from +http://java.sun.com.
    4. +
  4. 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.
    5. +
  5. Upload the server package to this directory. You can use FTP.
    6. +
  6. Switch to the /opt/rseserver directory by typing: +
    cd /opt/rseserver
    +
    7. +
  7. 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
    +
    8. +
  8. Still in the /opt/rseserver directory, run the following configuration +commands: +
    +chmod 755 server.pl
+chmod 755 daemon.pl
+chmod 755 auth.pl
+
    +
    9. +
+
+ +

Starting 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 -version
+
+
You 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 cxppc321411-20040301 (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/java
+
+
To start the server with the server daemon +
    +
  1. 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
    +
    2. +
+Note that the server daemon runs on port 4035. You can also start the +daemon.unix in the same way.

+

To start the server manually

+
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. If this does not work, try +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 +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.
+

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 startup

+
You 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

+
By default the RSE Dstore connection is unencrypted. You +can, however, configure it to use SSL encryption. +
+
+


+

Connecting to the Remote Server

+
To make a connection +to your remote server:
+
    +
  1. Switch to the Remote System Explorer perspective. From the workbench +menu, click Window > Open Perspective > Remote System Explorer.
    2. +
  2. In the Remote Systems view, New Connection is automatically +expanded to show the various remote systems you can connect to through the +Remote System Explorer. Expand Linux or Unix to +invoke the new connection dialog box and configure a connection.
    3. +
  3. Enter a name for your first profile and click Next. (This +step only occurs if you have never defined a connection before.)
    4. +
  4. Enter a connection name. This name displays in your tree view and +must be unique to the profile.
    5. +
  5. Enter the name or TCP/IP address of your Linux server in the Host +name field, for example, LINUX_A.
    6. +
  6. (Optional) Enter a Description. The description appears +in the Properties view after the connection is created.
    7. +
  7. Click Finish to define your system.
    8. +
+
+
Attention: To check your port number, right-click your +connection or subsystem from the Remote Systems view and select Properties. +Click Subsystem to view the relevant information. If your port is "0," +then your Remote System Explorer communications server will pick any free +port on the server. If you specified a port number when starting the server, +you need to enter it here, for example, to work with a firewall.
+
+
+
+
+
+
+

Related tasks +Connecting to a remote Windows +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 b5244044243..86462dd5a4a 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tbeginwindows.html @@ -1,104 +1,105 @@ - - - - - - - - -Connecting to a remote Windows server - - - - -

Connecting to a remote Windows server

-
-
-

Installing the server code

-
-
    -
  1. -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.
    2. -
  2. 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.
    3. -
  3. Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).
    4. -
  4. Using an unzip utility to extract the server code to the C:\rseserver directory.
    5. -
-
-

Starting the server

-

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

-
To start the server manually: -
    -
  1. Configure your CLASSPATH and then start the communications server. In a command prompt, enter: -
    -c:
    
-cd \rseserver
    
-setup.bat
    
-server.bat [port]
-
    -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 -Files subsystem for your connection in the Remote System Explorer (see -Connecting below). -
    2. -
-
-
To start the server with a the server daemon: -
    -
  1. First, you need to configure your CLASSPATH and then start the -server daemon. In a command prompt, enter: -
    -c:
    
-cd:\rseserver
    
-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.
    2. -
-
-
-
To connect to a remote Windows server:
-
    -
  1. Switch to the Remote System Explorer perspective.
    2. -
  2. In the Remote Systems view, New Connection is -automatically be expanded to show the various remote systems you can connect to -through the Remote System Explorer. Expand Windows to invoke a dialog -and configure a connection.
    3. -
  3. Enter a name for your first profile and click Next. -(This step only occurs if you have never defined a connection before.)
    4. -
  4. Enter a connection name. This name displays in your tree -view and must be unique to the profile.
    5. -
  5. Enter the name or TCP/IP address of your Windows server in -the Host Name field, for example, jsandler.
    6. -
  6. Enter a Description(optional); the description -appears in the Properties view after the connection is created.
    7. -
  7. Click Finish to define your system.
    8. -
-
-
Note: To check your -port number, right-click your connection or subsystem -from the Remote Systems view and select Properties. Click Subsystem -to see the relevant information. If your port is "0," then your Remote -System Explorer communications server will pick any free port on the Windows -server. If you specified a port number when starting the server, you need to -enter it here, for example, to work with a firewall.
-
-
-
-

Related tasks
-Connecting to a remote Linux or UNIX server
-

-
- - + + + + + + + + +Connecting to a remote Windows server + + + + +

Connecting to a remote Windows server

+
+
+

Installing the server code

+
+
    +
  1. +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.
    2. +
  2. 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.
    3. +
  3. Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).
    4. +
  4. Using an unzip utility to extract the server code to the C:\rseserver directory.
    5. +
+
+

Starting the server

+

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

+
To start the server manually: +
    +
  1. Configure your CLASSPATH and then start the communications server. In a command prompt, enter: +
    +c:
    
+cd \rseserver
    
+setup.bat
    
+server.bat [port]
+
    +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 +Files subsystem for your connection in the Remote System Explorer (see +Connecting below). +
    2. +
+
+
To start the server with a the server daemon: +
    +
  1. First, you need to configure your CLASSPATH and then start the +server daemon. In a command prompt, enter: +
    +c:
    
+cd:\rseserver
    
+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.
    2. +
+
+
+
To connect to a remote Windows server:
+
    +
  1. Switch to the Remote System Explorer perspective.
    2. +
  2. In the Remote Systems view, New Connection is +automatically be expanded to show the various remote systems you can connect to +through the Remote System Explorer. Expand Windows to invoke a dialog +and configure a connection.
    3. +
  3. Enter a name for your first profile and click Next. +(This step only occurs if you have never defined a connection before.)
    4. +
  4. Enter a connection name. This name displays in your tree +view and must be unique to the profile.
    5. +
  5. Enter the name or TCP/IP address of your Windows server in +the Host Name field, for example, jsandler.
    6. +
  6. Enter a Description(optional); the description +appears in the Properties view after the connection is created.
    7. +
  7. Click Finish to define your system.
    8. +
+
+
Note: To check your +port number, right-click your connection or subsystem +from the Remote Systems view and select Properties. Click Subsystem +to see the relevant information. If your port is "0," then your Remote +System Explorer communications server will pick any free port on the Windows +server. If you specified a port number when starting the server, you need to +enter it here, for example, to work with a firewall.
+
+
+
+

Related tasks
+Connecting to a remote Linux or UNIX server
+

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html index 0a2246fac48..bfbcd22855a 100755 --- a/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html +++ b/rse/doc/org.eclipse.rse.doc.user/tasks/tteamsup1.html @@ -1,82 +1,84 @@ - - - - - - - - -Working with profiles and team support - - - - -

Working with profiles and team support

-
-
All connections, filter data, user actions, and compile -commands belong to profiles. Profiles can be shared by team members for the purpose of -team development. You can work with your profiles in the Team view to enable -greater control over team-sharable elements in the Remote System Explorer. -
Note: Because -the Remote Systems view only displays connections, filters, user -actions, and compile commands from active profiles, you need to be in the Team -view to work with or activate your non-active profiles. -
-
-
To manage your team profiles: -
-
    -
  1. In the Remote Systems perspective, select the Team tab which by -default is located in the same pane as the Remote Systems view.  -This will bring the Team view to the front of the Remote System -Explorer.  You can also use the  -menu -button on the Remote Systems view and select the Work With Profiles -action.
    -
    2. -
  2. In the Team view, expand the root element, RemoteSystemsConnections, -to see a list of your profiles. -
      -
    • To create a profile, right-click on the root element in the -Team view, and select New > Profile and complete the dialog box for the -profile.
      • -
    • To activate or deactivate a profile, right-click the profile -and select Active (if it is deactivated) or Not active (if it is active).
      • -
    • To duplicate a profile in the view, right-click the profile -and select Duplicate. This action copies all of the profile's connections, filters, user -actions, and compile commands.
      • -
    • To rename a profile, right-click the profile and select Rename.
      • -
    -
    3. -
  3. In the Team view, you can also expand your profiles to view -connections, filter pools, user actions, and compile commands that belong to each -profile. Right-click on any of your specific filters, user actions, and so on, -to open a Work with window. These are the same actions available in the -Remote Systems view. To work with filter pools, for example, right-click one -of your filters, and select Work with filter pools. Keep in mind that -the Remote Systems view is the more ideal environment to manipulate filters, -filter pools, compile commands, user actions, and so on. The Team view is designed to -manage profiles, and view the elements that belong to each profile. The Remote -Systems view is designed for you to work with all the items that belong to your -active profiles. It includes a greater number of right-click and menu options -for a development-focused approach.
    4. -
  4. When you have finished working with your profiles, switch back to -the Remote Systems view, by clicking the Remote Systems tab, to continue -working with active profile artifacts, or remain in the Team view to -synchronize your profiles with the repository.
    5. -
-
-
-
-
-

Related concepts
-Team support
-Remote System Explorer Profiles
-

-

Related tasks
-Using team support
-Managing user actions (user options)
-

-
- - + + + + + + + + +Working with profiles and team support + + + + +

Working with profiles and team support

+
+
All connections, filter data, user actions, and compile +commands belong to profiles. Profiles can be shared by team members for the purpose of +team development. You can work with your profiles in the Team view to enable +greater control over team-sharable elements in the Remote System Explorer. +
Note: Because +the Remote Systems view only displays connections, filters, user +actions, and compile commands from active profiles, you need to be in the Team +view to work with or activate your non-active profiles. +
+
+
To manage your team profiles: +
+
    +
  1. In the Remote Systems perspective, select the Team tab which by +default is located in the same pane as the Remote Systems view.  +This will bring the Team view to the front of the Remote System +Explorer.  You can also use the  +menu +button on the Remote Systems view and select the Work With Profiles +action.
    +
    2. +
  2. In the Team view, expand the root element, RemoteSystemsConnections, +to see a list of your profiles. +
      +
    • To create a profile, right-click on the root element in the +Team view, and select New > Profile and complete the dialog box for the +profile.
      • +
    • To activate or deactivate a profile, right-click the profile +and select Active (if it is deactivated) or Not active (if it is active).
      • +
    • To duplicate a profile in the view, right-click the profile +and select Duplicate. This action copies all of the profile's connections, filters, user +actions, and compile commands.
      • +
    • To rename a profile, right-click the profile and select Rename.
      • +
    +
    3. +
  3. In the Team view, you can also expand your profiles to view +connections, filter pools, user actions, and compile commands that belong to each +profile. Right-click on any of your specific filters, user actions, and so on, +to open a Work with window. These are the same actions available in the +Remote Systems view. To work with filter pools, for example, right-click one +of your filters, and select Work with filter pools. Keep in mind that +the Remote Systems view is the more ideal environment to manipulate filters, +filter pools, compile commands, user actions, and so on. The Team view is designed to +manage profiles, and view the elements that belong to each profile. The Remote +Systems view is designed for you to work with all the items that belong to your +active profiles. It includes a greater number of right-click and menu options +for a development-focused approach.
    4. +
  4. When you have finished working with your profiles, switch back to +the Remote Systems view, by clicking the Remote Systems tab, to continue +working with active profile artifacts, or remain in the Team view to +synchronize your profiles with the repository.
    5. +
+
+
+
+
+

Related concepts
+Team support
+Remote System Explorer Profiles
+

+

Related tasks
+Using team support
+ +

+
+ + diff --git a/rse/doc/org.eclipse.rse.doc.user/toc.xml b/rse/doc/org.eclipse.rse.doc.user/toc.xml index 27f03043ef7..e61264b4be4 100755 --- a/rse/doc/org.eclipse.rse.doc.user/toc.xml +++ b/rse/doc/org.eclipse.rse.doc.user/toc.xml @@ -1,48 +1,59 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file