1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-04 07:35:24 +02:00

Add gettingstarted guide to userdoc; Update TOC; Remove links to User Actions, compile commands and import/export features.

This commit is contained in:
Martin Oberhuber 2006-08-19 02:09:30 +00:00
parent 98d8b37a2b
commit 9ec21d5100
12 changed files with 715 additions and 453 deletions

View file

@ -8,5 +8,6 @@ bin.includes = META-INF/,\
tasks/,\
book.css,\
notices.html,\
toc.xml
toc.xml,\
gettingstarted/

View file

@ -98,10 +98,12 @@ you can always create a new profile. See
the related links for more information.</p>
</div>
<div>
<!-- TODODeferred
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="cuseractions.html" title="">User actions (user options)</a><br/>
<a href="cremcompile.html" title="">Compiling</a><br/>
</p>
-->
<p><b>Related Tasks</b><br/>
<a href="../tasks/tmanagepools.html" title="">Configuring filter pools</a><br/>
<a href="../tasks/tmanageedit.html"

View file

@ -1,71 +1,71 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Team support</title>
</head>
<body id="cteam">
<a name="cteam"><!-- --></a>
<h1 class="topictitle1">Team support</h1>
<div>
<p>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.&nbsp; 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.</p>
<div class="p" id="cteam__profilelist"><a name="cteam__profilelist"><!-- --></a>Profiles
contain:
<ul>
<li>Connections -- including various subsystem properties. User IDs
and passwords are not shared.</li>
<li>Filters, filter pools, and filters pool references</li>
<li>User-defined actions</li>
<li>Compile commands</li>
</ul>
</div>
<p> 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 <b>Reload Remote System Explorer</b> action, located on the
pop-up menu, to make the Remote Systems Explorer know about these
changes.&nbsp; You can also, of course, quit and restart the
workbench.&nbsp; See the related tasks for more information.</p>
<p>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.</p>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="cprofile.html" title="">Remote System Explorer Profiles</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="../tasks/tteamsup.html" title="">Using team support</a><br/>
<a href="../tasks/tteamsup1.html" title="">Working with profiles and team support</a><br/>
</p>
</div>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Team support</title>
</head>
<body id="cteam">
<a name="cteam"><!-- --></a>
<h1 class="topictitle1">Team support</h1>
<div>
<p>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.&nbsp; 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.</p>
<div class="p" id="cteam__profilelist"><a name="cteam__profilelist"><!-- --></a>Profiles
contain:
<ul>
<li>Connections -- including various subsystem properties. User IDs
and passwords are not shared.</li>
<li>Filters, filter pools, and filters pool references</li>
<li>User-defined actions</li>
<li>Compile commands</li>
</ul>
</div>
<p> 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 <b>Reload Remote System Explorer</b> action, located on the
pop-up menu, to make the Remote System Explorer know about these
changes.&nbsp; You can also, of course, quit and restart the
workbench.&nbsp; See the related tasks for more information.</p>
<p>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.</p>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="cprofile.html" title="">Remote System Explorer Profiles</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="../tasks/tteamsup.html" title="">Using team support</a><br/>
<a href="../tasks/tteamsup1.html" title="">Working with profiles and team support</a><br/>
</p>
</div>
</body>
</html>

View file

@ -0,0 +1,48 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Installing the RSE</title>
</head>
<body id="g1installing">
<a name="g1installing"><!-- --></a>
<h1 class="topictitle1">Installing the Remote System Explorer</h1>
<div>
The simplest way to get RSE is via the Update Manager: From your running instance
of Eclipse 3.2, choose <i>Help &gt; Software Updates &gt; Find and Install...</i>.
Choose "Search for New Features to Install", and add a new Remote Site named
"RSE" and pointing to <a href="http://download.eclipse.org/dsdp/tm/updates/">
http://download.eclipse.org/dsdp/tm/updates/</a>.
Select the RSE SDK feature, and perform the update process as usual.</p>
<p>If you prefer manual installation, you can download RSE SDK from the
DSDP <a href="http://download.eclipse.org/dsdp/tm/downloads/">Target
Management Download Site</a> and extract it into your installation of
Eclipse 3.2 or later, or link it as product extension.
<p>Start Eclipse Workbench, and choose <i>Window &gt; Open Perspective &gt;
Other &gt; Remote System Explorer</i>.</p>
</div>
<div>
<!--
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
-->
<p><b class="reltaskshd">Follow-up tasks</b><br/>
<a href="g2firststeps.html" title="">First Steps with the Remote System Explorer</a><br/>
<!--
<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote
Linux or UNIX server</a><br/>
<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote
Windows server</a><br/>
-->
<a href="gusing.html" title="">Using Remote System Explorer Connections</a><br/>
</p>
</div>
</body>
</html>

View file

@ -0,0 +1,59 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>First Steps with RSE</title>
</head>
<body id="g2firststeps">
<a name="g2firststeps"><!-- --></a>
<h1 class="topictitle1">First Steps with the Remote System Explorer</h1>
<div>
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 <i>Local</i> node:
<ul>
<li>Browse the Filesystem, choose <i>contextmenu &gt; show in Table</i>, and
observe the Properties view.</li>
<li>Create a new <a href="../concepts/cfilters.html">Filter</a> to show
specific resources in the file system only.</li>
<li>Launch an <a href="../concepts/crunremcmds.html">RSE Shell</a>
(Shells node &gt; Launch)
<ul><li>In the Shell, perform commands such as ls, dir, ps, gcc, make and see
the output interpreted</li>
<li>Use Ctrl+Space Content Assist on the shell command entry field</li>
</ul></li>
</ul>
For operations on an actual remote system, you can either
<ul>
<li>use the "<b>SSH Only</b>" system type (<i>New > Other > Remote System Explorer > Connection</i>), or</li>
<li>start a <a href="../tasks/tbeginlinux.html">dstore server daemon</a>
on the remote system and use any of the other connection types.</li>
</ul>
<p>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.<br/>
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.</p>
</div>
<div>
<p><b class="reltaskshd">Follow-up tasks</b><br/>
<a href="gusing.html" title="">Using Remote System Explorer Connections</a><br/>
</p>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/>
<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter
pools, and filter pool references</a><br/>
<a href="../concepts/cuniversal.html">Universal Systems</a><br/>
<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote
Linux or UNIX server</a><br/>
<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote
Windows server</a><br/>
</p>
</div>
</body>
</html>

View file

@ -0,0 +1,55 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Getting Started with RSE</title>
</head>
<body id="gstart">
<a name="gstart"><!-- --></a>
<h1 class="topictitle1">Getting Started with the Remote System Explorer</h1>
<div>
<p>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.</p>
<p>Additional capabilities may be added by Software Vendors by providing new
<i>System Types</i>, <i>Services</i> and <i>Subsystem implementations</i>
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.</p>
<a href="../images/RSESample.gif">
<!-- <img src="../images/RSESample.gif" alt="A sample RSE session" width="917" height="659"/><br/>
-->
<img src="../images/RSESample.gif" alt="A sample RSE session" width="459" height="330"/><br/>
</a>
<p>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:
<ul>
<li><a href="g1installing.html" title="">Installing the Remote System Explorer</a></li>
<li><a href="g2firststeps.html" title="">First Steps with the Remote System Explorer</a></li>
<li><a href="gusing.html" title="">Using Remote System Explorer Connections</a></li>
</ul>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/>
</p>
<!--
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote
Linux or UNIX server</a><br/>
<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote
Windows server</a><br/>
</p>
-->
</div>
</body>
</html>

View file

@ -0,0 +1,66 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Using Remote Connections</title>
</head>
<body id="gusing">
<a name="gusing"><!-- --></a>
<h1 class="topictitle1">Using Remote Connections</h1>
<div>
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..
<ul>
<li>In the RSE Perspective, Remote Systems View, press the <b>New Connection</b> button.<ul>
<li>Note: In the Preferences, you can enable displaying available new connection types in the RSE tree.</li></ul></li>
<li>Select the desired system type<ul>
<li>Coose system type "SSH Only" for ssh servers, or any other for dstore.</li></ul></li>
<li>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.<ul>
<li>You can also run a dstore server on the local machine for testing. In this case,
type "localhost" as address.</li>
<li>You can press Finish right away, the wizard defaults are usually fine.</li></ul></li>
<li>Fill in the username / password dialog.<ul>
<li>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 <b>Team &gt; CVS &gt; SSH2 Connection Method</b> Preference page.</li></ul></li>
<li><b>Browse remote files</b>, or open remote shells.<ul>
<li>You can <b>drag and drop</b> files between local and remote file systems, between editors and any view.
Files are transferred as needed.</li>
<li>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.<br>
Note: Some tar formats currently fail to work. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139207">bug 139207</a>.</li>
<li>On dstore, you can choose <b>Search &gt; Remote...</b>.<ul>
<li>The dstore miners support searching a remote file system
without having to transfer any data.</li></ul></li>
<li>On dstore, when the remote system is Linux, AIX or Other Unix:<ul>
<li>Browse remote <b>Processes</b>.</li>
<li>Select "My Processes" and choose context menu &gt; <b>Monitor</b>.
<li>Enable polling, choose a short wait time. See processes appear and vanish as you perform commands in a remote shell.</li></ul></li>
</ul>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cbegin.html" title="">Remote System Explorer Connections</a><br/>
<a href="../concepts/cfilters.html" title="">Remote System Explorer filters, filter
pools, and filter pool references</a><br/>
<a href="../concepts/crunremcmds.html" title="">Shells and commands in the
Remote Systems view</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="../tasks/tbeginlinux.html" title="">Connecting to a remote
Linux or UNIX server</a><br/>
<a href="../tasks/tbeginwindows.html" title="">Connecting to a remote
Windows server</a><br/>
<a href="../tasks/truncmdsview.html" title="">Running and viewing
commands and shells using the Remote Commands view</a><br/>
</p>
</div>
</body>
</html>

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

View file

@ -1,148 +1,165 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Connecting to a remote Linux or UNIX server</title>
</head>
<body id="tbeginlinux">
<a name="tbeginlinux"><!-- --></a>
<h1 class="topictitle1">Connecting to a remote Linux or UNIX server</h1>
<p>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.</p>
<div>
<div class="p">
<p><b>Prerequisites</b></p>
<p>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.</p>
<p><b>Installing the server code</b></p>
<div class="p">
<ol>
<li>
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-&lt;version&gt;-&lt;os&gt;.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.</li>
<li>Ensure that Perl is installed.</li>
<li>Ensure that a Java Runtime Environment (JRE) version 1.4 or higher is installed.</li>
<li>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.</li>
<li>Upload the server package to this directory. You can use FTP.</li>
<li>Switch to the /opt/rseserver directory by typing:
<pre>cd /opt/rseserver</pre>
</li>
<li>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:
<pre>tar -xf rseserver-1.0-linux.tar</pre>
</li>
<li>Still in the /opt/rseserver directory, run the following configuration
commands:
<pre>
chmod 755 server.pl
chmod 755 daemon.pl
chmod 755 auth.pl
</pre>
</li>
</ol>
</div>
<p><b>Starting the server</b></p>
<div class="p">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:<pre>java -version</pre>
</div>
<div class="p">You should see something
similar to the following:<pre>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))</pre>
</div>
<div class="p">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:<pre>ln -s /opt/IBMJava2-141/jre/bin/java /usr/bin/java</pre>
</div>
<div class="p"><b>To start the server with the server daemon</b>
<ol>
<li>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:<pre>su -l root
cd /opt/rseserver
perl ./daemon.pl</pre>
</li>
</ol>
Note that the server daemon runs on port 4035. You can also start the
daemon.unix in the same way.<br></br>
<p><b>To start the server manually</b></p>
<div class="p">Run
the following commands:<pre>cd /opt/rseserver
perl ./server.pl [port]</pre>
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 <samp class="codeph">chmod
755 server.pl</samp>. 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 <span class="uicontrol">Connecting to the
Remote Server</span>, below). Otherwise, you do not need to change this
property.</div>
<p><b>Running the daemon at startup</b></p>
<div class="p">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:<pre>cd /opt/rseserver
perl ./daemon.pl &amp;</pre>
</div>
</div>
</div><br></br>
<p><b>Connecting to the Remote Server</b></p>
<div class="p">To make a connection
to your remote server:</div>
<ol>
<li><span>Switch to the Remote System Explorer perspective. From the workbench
menu, click <span class="menucascade"><span class="uicontrol">Window </span> &gt; <span class="uicontrol">Open Perspective </span> &gt; <span class="uicontrol">Remote System Explorer</span></span>.</span></li>
<li><span>In the Remote Systems view, <b>New Connection</b> is automatically
expanded to show the various remote systems you can connect to through the
Remote System Explorer. Expand <b>Linux</b> or <b>Unix</b> to
invoke the new connection dialog box and configure a connection.</span></li>
<li><span>Enter a name for your first profile and click <b>Next</b>. (This
step only occurs if you have never defined a connection before.)</span></li>
<li><span>Enter a connection name. This name displays in your tree view and
must be unique to the profile.</span></li>
<li><span>Enter the name or TCP/IP address of your Linux server in the <b>Host
name</b> field, for example, LINUX_A.</span></li>
<li><span>(Optional) Enter a <b>Description</b>. The description appears
in the Properties view after the connection is created.</span></li>
<li><span>Click <b>Finish</b> to define your system. </span></li>
</ol>
<div class="skipspace">
<div class="attention"><span class="attentiontitle">Attention: </span>To check your port number, right-click your
connection or subsystem from the Remote Systems view and select <b>Properties</b>.
Click <b>Subsystem</b> 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.</div>
</div>
<div class="p">
<div class="note"></div>
</div>
</div>
<div>
<p><b class="reltaskshd">Related tasks</b>
<a href="tbeginwindows.html" title="">Connecting to a remote Windows
server</a>
</p>
</div>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Connecting to a remote Linux or UNIX server</title>
</head>
<body id="tbeginlinux">
<a name="tbeginlinux"><!-- --></a>
<h1 class="topictitle1">Connecting to a remote Linux or UNIX server</h1>
<p>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.</p>
<div>
<div class="p">
<p><b>Prerequisites</b></p>
<p>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.</p>
<p><b>Installing the server code</b></p>
<div class="p">
<ol>
<li>
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
<a href="http://download.eclipse.org/dsdp/tm/downloads/">Target Management download site</a>
as the package <b>rseserver-&lt;version&gt;-&lt;os&gt;.tar</b>. 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.</li>
<li>Ensure that Perl is installed.</li>
<li>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 <br/><tt>java -version</tt> (see
below) and check if there is a reference to gcj. You can download a Sun JRE from
<a href="http://java.sun.com">http://java.sun.com</a>.</li>
<li>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.</li>
<li>Upload the server package to this directory. You can use FTP.</li>
<li>Switch to the /opt/rseserver directory by typing:
<pre>cd /opt/rseserver</pre>
</li>
<li>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:
<pre>tar -xf rseserver-1.0-linux.tar</pre>
</li>
<li>Still in the /opt/rseserver directory, run the following configuration
commands:
<pre>
chmod 755 server.pl
chmod 755 daemon.pl
chmod 755 auth.pl
</pre>
</li>
</ol>
</div>
<p><b>Starting the server</b></p>
<div class="p">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:<pre>java -version</pre>
</div>
<div class="p">You should see something
similar to the following:<pre>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))</pre>
</div>
<div class="p">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:<pre>ln -s /opt/IBMJava2-141/jre/bin/java /usr/bin/java</pre>
</div>
<div class="p"><b>To start the server with the server daemon</b>
<ol>
<li>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:<pre>su -l root
cd /opt/rseserver
perl ./daemon.pl</pre>
</li>
</ol>
Note that the server daemon runs on port 4035. You can also start the
daemon.unix in the same way.<br></br>
<p><b>To start the server manually</b></p>
<div class="p">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:<pre>cd /opt/rseserver
perl ./server.pl [port]</pre>
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 <samp class="codeph">chmod
755 server.pl</samp>. 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 <span class="uicontrol">Connecting to the
Remote Server</span>, below). Otherwise, you do not need to change this
property.</div>
<p><b>Rexec Server Launcher</b></p>
<div class="p">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.
</div>
<p><b>Running the daemon at startup</b></p>
<div class="p">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:<pre>cd /opt/rseserver
perl ./daemon.pl &amp;</pre>
</div>
<p><b>SSL Encryption</b></p>
<div class="p">By default the RSE Dstore connection is unencrypted. You
can, however, configure it to use SSL encryption.
</div>
</div>
</div><br></br>
<p><b>Connecting to the Remote Server</b></p>
<div class="p">To make a connection
to your remote server:</div>
<ol>
<li><span>Switch to the Remote System Explorer perspective. From the workbench
menu, click <span class="menucascade"><span class="uicontrol">Window </span> &gt; <span class="uicontrol">Open Perspective </span> &gt; <span class="uicontrol">Remote System Explorer</span></span>.</span></li>
<li><span>In the Remote Systems view, <b>New Connection</b> is automatically
expanded to show the various remote systems you can connect to through the
Remote System Explorer. Expand <b>Linux</b> or <b>Unix</b> to
invoke the new connection dialog box and configure a connection.</span></li>
<li><span>Enter a name for your first profile and click <b>Next</b>. (This
step only occurs if you have never defined a connection before.)</span></li>
<li><span>Enter a connection name. This name displays in your tree view and
must be unique to the profile.</span></li>
<li><span>Enter the name or TCP/IP address of your Linux server in the <b>Host
name</b> field, for example, LINUX_A.</span></li>
<li><span>(Optional) Enter a <b>Description</b>. The description appears
in the Properties view after the connection is created.</span></li>
<li><span>Click <b>Finish</b> to define your system. </span></li>
</ol>
<div class="skipspace">
<div class="attention"><span class="attentiontitle">Attention: </span>To check your port number, right-click your
connection or subsystem from the Remote Systems view and select <b>Properties</b>.
Click <b>Subsystem</b> 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.</div>
</div>
<div class="p">
<div class="note"></div>
</div>
</div>
<div>
<p><b class="reltaskshd">Related tasks</b>
<a href="tbeginwindows.html" title="">Connecting to a remote Windows
server</a>
<!-- TODO SSL configuration -->
</p>
</div>
</body>
</html>

View file

@ -1,104 +1,105 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Connecting to a remote Windows server</title>
</head>
<body id="tbeginlinux">
<a name="tbeginlinux"></a>
<h1 class="topictitle1">Connecting to a remote Windows server</h1>
<div>
<div class="p">
<p><b>Installing the server code</b></p>
<div class="p">
<ol>
<li>
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.</li>
<li>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-&lt;version&gt;-&lt;os&gt;.zip. For example, rseserver-1.0-windows.zip contains the release 1.0 server
for Windows.</li>
<li>Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).</li>
<li>Using an unzip utility to extract the server code to the C:\rseserver directory.</li>
</ol>
</div>
<p><b>Starting the server</b></p>
<p>You can start the RSE communications server with the server manually, or with a daemon.</p>
<div class="p">To start the server manually:
<ol>
<li>Configure your CLASSPATH and then start the communications server. In a command prompt, enter:
<pre>
c:<br/>
cd \rseserver<br/>
setup.bat<br/>
server.bat [port]
</pre>
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).
</li>
</ol>
</div>
<div class="p">To start the server with a the server daemon:
<ol>
<li>First, you need to configure your CLASSPATH and then start the
server daemon. In a command prompt, enter:
<pre>
c:<br/>
cd:\rseserver<br/>
setup.bat<br/>
daemon.bat
</pre>
Note that the server daemon <b>does not</b> 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.
<span style="font-weight: bold;">Use of the server daemon on Windows systems is not recommended</span>.</li>
</ol>
</div>
</div>
<div class="p">To connect to a remote Windows server:</div>
<ol>
<li><span>Switch to the Remote System Explorer perspective.</span></li>
<li><span>In the Remote Systems view, <b>New Connection</b> is
automatically be expanded to show the various remote systems you can connect to
through the Remote System Explorer. Expand <b>Windows</b> to invoke a dialog
and configure a connection.</span></li>
<li><span>Enter a name for your first profile and click <b>Next</b>.
(This step only occurs if you have never defined a connection before.)</span></li>
<li><span>Enter a connection name. This name displays in your tree
view and must be unique to the profile.</span></li>
<li><span>Enter the name or TCP/IP address of your Windows server in
the <b>Host Name</b> field, for example, jsandler.</span></li>
<li><span>Enter a <b>Description</b>(optional); the description
appears in the Properties view after the connection is created.</span></li>
<li><span>Click <b>Finish</b> to define your system. </span></li>
</ol>
<div class="p">
<div class="note"><span class="notetitle">Note: </span>To check your
port number, right-click your connection or subsystem
from the Remote Systems view and select <b>Properties</b>. Click <b>Subsystem</b>
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.</div>
</div>
</div>
<div>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="tbeginlinux.html" title="">Connecting to a remote Linux or UNIX server</a><br/>
</p>
</div>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Connecting to a remote Windows server</title>
</head>
<body id="tbeginlinux">
<a name="tbeginlinux"></a>
<h1 class="topictitle1">Connecting to a remote Windows server</h1>
<div>
<div class="p">
<p><b>Installing the server code</b></p>
<div class="p">
<ol>
<li>
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.</li>
<li>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
<a href="http://download.eclipse.org/dsdp/tm/downloads/">Target Management download site</a>
as the package <b>rseserver-&lt;version&gt;-&lt;os&gt;.zip</b>. For example, rseserver-1.0-windows.zip contains the release 1.0 server
for Windows.</li>
<li>Copy the rseserver.zip to the C:\rseserver directory (this could be on a different machine).</li>
<li>Using an unzip utility to extract the server code to the C:\rseserver directory.</li>
</ol>
</div>
<p><b>Starting the server</b></p>
<p>You can start the RSE communications server with the server manually, or with a daemon.</p>
<div class="p">To start the server manually:
<ol>
<li>Configure your CLASSPATH and then start the communications server. In a command prompt, enter:
<pre>
c:<br/>
cd \rseserver<br/>
setup.bat<br/>
server.bat [port]
</pre>
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).
</li>
</ol>
</div>
<div class="p">To start the server with a the server daemon:
<ol>
<li>First, you need to configure your CLASSPATH and then start the
server daemon. In a command prompt, enter:
<pre>
c:<br/>
cd:\rseserver<br/>
setup.bat<br/>
daemon.bat
</pre>
Note that the server daemon <b>does not</b> 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.
<span style="font-weight: bold;">Use of the server daemon on Windows systems is not recommended</span>.</li>
</ol>
</div>
</div>
<div class="p">To connect to a remote Windows server:</div>
<ol>
<li><span>Switch to the Remote System Explorer perspective.</span></li>
<li><span>In the Remote Systems view, <b>New Connection</b> is
automatically be expanded to show the various remote systems you can connect to
through the Remote System Explorer. Expand <b>Windows</b> to invoke a dialog
and configure a connection.</span></li>
<li><span>Enter a name for your first profile and click <b>Next</b>.
(This step only occurs if you have never defined a connection before.)</span></li>
<li><span>Enter a connection name. This name displays in your tree
view and must be unique to the profile.</span></li>
<li><span>Enter the name or TCP/IP address of your Windows server in
the <b>Host Name</b> field, for example, jsandler.</span></li>
<li><span>Enter a <b>Description</b>(optional); the description
appears in the Properties view after the connection is created.</span></li>
<li><span>Click <b>Finish</b> to define your system. </span></li>
</ol>
<div class="p">
<div class="note"><span class="notetitle">Note: </span>To check your
port number, right-click your connection or subsystem
from the Remote Systems view and select <b>Properties</b>. Click <b>Subsystem</b>
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.</div>
</div>
</div>
<div>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="tbeginlinux.html" title="">Connecting to a remote Linux or UNIX server</a><br/>
</p>
</div>
</body>
</html>

View file

@ -1,82 +1,84 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Working with profiles and team support</title>
</head>
<body id="tteamsup1">
<a name="tteamsup1"></a>
<h1 class="topictitle1">Working with profiles and team support</h1>
<div>
<div class="p">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.
<div class="note"><span class="notetitle">Note: </span>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.
</div>
</div>
<div class="p">To manage your team profiles:
<div class="p">
<ol>
<li>In the Remote Systems perspective, select the Team tab which by
default is located in the same pane as the Remote Systems view.&nbsp;
This will bring the Team view to the front of the Remote System
Explorer.&nbsp; You can also use the&nbsp;
<img src="../images/gsarrow.gif" title="" alt="menu" style="width: 24px; height: 23px;"/>
button on the Remote Systems view and select the <span style="font-weight: bold;">Work With Profiles</span>
action.<br/>
</li>
<li>In the Team view, expand the root element, <b>RemoteSystemsConnections</b>,
to see a list of your profiles.
<ul>
<li>To create a profile, right-click on the root element in the
Team view, and select <b>New &gt; Profile</b> and complete the dialog box for the
profile.</li>
<li>To activate or deactivate a profile, right-click the profile
and select <b>Active</b> (if it is deactivated) or <b>Not active</b> (if it is active).</li>
<li>To duplicate a profile in the view, right-click the profile
and select <b>Duplicate</b>. This action copies all of the profile's connections, filters, user
actions, and compile commands.</li>
<li>To rename a profile, right-click the profile and select <b>Rename</b>.</li>
</ul>
</li>
<li>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 <b>Work with</b> 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 <b>Work with filter pools</b>. 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.</li>
<li>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
<a href="tteamsup.html">synchronize your profiles with the repository</a>.</li>
</ol>
</div>
</div>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cteam.html" title="">Team support</a><br/>
<a href="../concepts/cprofile.html" title="">Remote System Explorer Profiles</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="tteamsup.html" title="">Using team support</a><br/>
<a href="tworkuseract.html" title="">Managing user actions (user options)</a><br/>
</p>
</div>
</body>
</html>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2004, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<link rel="stylesheet" type="text/css" href="../book.css"/>
<title>Working with profiles and team support</title>
</head>
<body id="tteamsup1">
<a name="tteamsup1"></a>
<h1 class="topictitle1">Working with profiles and team support</h1>
<div>
<div class="p">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.
<div class="note"><span class="notetitle">Note: </span>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.
</div>
</div>
<div class="p">To manage your team profiles:
<div class="p">
<ol>
<li>In the Remote Systems perspective, select the Team tab which by
default is located in the same pane as the Remote Systems view.&nbsp;
This will bring the Team view to the front of the Remote System
Explorer.&nbsp; You can also use the&nbsp;
<img src="../images/gsarrow.gif" title="" alt="menu" style="width: 24px; height: 23px;"/>
button on the Remote Systems view and select the <span style="font-weight: bold;">Work With Profiles</span>
action.<br/>
</li>
<li>In the Team view, expand the root element, <b>RemoteSystemsConnections</b>,
to see a list of your profiles.
<ul>
<li>To create a profile, right-click on the root element in the
Team view, and select <b>New &gt; Profile</b> and complete the dialog box for the
profile.</li>
<li>To activate or deactivate a profile, right-click the profile
and select <b>Active</b> (if it is deactivated) or <b>Not active</b> (if it is active).</li>
<li>To duplicate a profile in the view, right-click the profile
and select <b>Duplicate</b>. This action copies all of the profile's connections, filters, user
actions, and compile commands.</li>
<li>To rename a profile, right-click the profile and select <b>Rename</b>.</li>
</ul>
</li>
<li>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 <b>Work with</b> 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 <b>Work with filter pools</b>. 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.</li>
<li>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
<a href="tteamsup.html">synchronize your profiles with the repository</a>.</li>
</ol>
</div>
</div>
</div>
<div>
<p><b class="relconceptshd">Related concepts</b><br/>
<a href="../concepts/cteam.html" title="">Team support</a><br/>
<a href="../concepts/cprofile.html" title="">Remote System Explorer Profiles</a><br/>
</p>
<p><b class="reltaskshd">Related tasks</b><br/>
<a href="tteamsup.html" title="">Using team support</a><br/>
<!-- TODODeferred after RSE 1.0
<a href="tworkuseract.html" title="">Managing user actions (user options)</a><br/>
-->
</p>
</div>
</body>
</html>

View file

@ -1,48 +1,59 @@
<?xml version="1.0" encoding="utf-8"?>
<?NLS TYPE="org.eclipse.help.toc"?>
<toc label="RSE User Guide">
<topic label="Universal Systems" href="concepts/cuniversal.html"/>
<topic label="Remote System Explorer Connections" href="concepts/cbegin.html">
<topic label="Connecting to a remote Linux or UNIX server" href="tasks/tbeginlinux.html"/>
<topic label="Connecting to a remote Windows server" href="tasks/tbeginwindows.html"/>
<topic label="Disconnecting from a remote server" href="tasks/tbegindiscon.html"/>
<topic label="Creating a second connection to a remote server" href="tasks/tbeginsecond.html"/>
<topic label="Deleting a connection" href="tasks/tbegindelete.html"/>
<topic label="Configuring environment variable support for connections" href="tasks/tbeginenv.html"/>
</topic>
<topic label="Remote System Explorer filters, filter pools, and filter pool references" href="concepts/cfilters.html">
<topic label="Creating filters" href="tasks/tmanagemem.html"/>
<topic label="Changing filters" href="tasks/tmanageedit.html"/>
<topic label="Deleting filters" href="tasks/tmanagedel.html"/>
<topic label="Configuring filter pools" href="tasks/tmanagepools.html"/>
<topic label="Configuring filter pool references" href="tasks/tmanagepoolsref.html"/>
</topic>
<topic label="Remote System Explorer Profiles" href="concepts/cprofile.html">
<topic label="Creating a second profile" href="tasks/tbeginsecprofile.html"/>
<topic label="Deleting a profile" href="tasks/tbegindeleteprofile.html"/>
</topic>
<topic label="Team support" href="concepts/cteam.html">
<topic label="Using team support" href="tasks/tteamsup.html"/>
<topic label="Working with profiles and team support" href="tasks/tteamsup1.html"/>
</topic>
<topic label="Shells and commands in the Remote Systems view" href="concepts/crunremcmds.html">
<topic label="Running and viewing commands and shells using the Remote Commands view" href="tasks/truncmdsview.html"/>
<topic label="Working with command shells" href="tasks/twrkcmdshl.html"/>
</topic>
<topic label="User actions" href="concepts/cuseractions.html">
<topic label="Managing user actions" href="tasks/tworkuseract.html"/>
<topic label="Editing an existing type" href="tasks/tedittype.html"/>
<topic label="Removing an existing type" href="tasks/tremtype.html"/>
</topic>
<topic label="Search for text and files on remote servers" href="tasks/tmanagesearch.html">
<topic label="Using search parameters with special characters" href="ref/rsearch.html"/>
</topic>
<topic label="Compiling programs" href="concepts/cremcompile.html"/>
<topic label="Managing archived files" href="tasks/tarchive.html"/>
<topic label="Importing resources from a remote file system" href="tasks/tremoimp.html" />
<topic label="Exporting resources to a remote file system" href="tasks/tremoexp.html" />
<topic label="Building programs on a remote system" href="tasks/tbuild.html" />
<topic label="Accessing Remote System Explorer preferences" href="ref/rrsepref.html"/>
<topic label="Saving User IDs and passwords" href="tasks/tbeginpass.html"/>
<topic label="Legal" href="notices.html"/>
<?xml version="1.0" encoding="utf-8"?>
<?NLS TYPE="org.eclipse.help.toc"?>
<toc label="RSE User Guide">
<topic label="Getting Started" href="gettingstarted/gstart.html">
<topic label="Installing the Remote System Explorer" href="gettingstarted/g1installing.html"/>
<topic label="First Steps with the Remote System Explorer" href="gettingstarted/g2firststeps.html"/>
<topic label="Using Remote Connections" href="gettingstarted/gusing.html"/>
</topic>
<topic label="Remote System Explorer Connections" href="concepts/cbegin.html">
<topic label="Universal Systems" href="concepts/cuniversal.html"/>
<topic label="Connecting to a remote Linux or UNIX server" href="tasks/tbeginlinux.html"/>
<topic label="Connecting to a remote Windows server" href="tasks/tbeginwindows.html"/>
<topic label="Disconnecting from a remote server" href="tasks/tbegindiscon.html"/>
<topic label="Creating a second connection to a remote server" href="tasks/tbeginsecond.html"/>
<topic label="Deleting a connection" href="tasks/tbegindelete.html"/>
<topic label="Configuring environment variable support for connections" href="tasks/tbeginenv.html"/>
</topic>
<topic label="Remote System Explorer filters, filter pools, and filter pool references" href="concepts/cfilters.html">
<topic label="Creating filters" href="tasks/tmanagemem.html"/>
<topic label="Changing filters" href="tasks/tmanageedit.html"/>
<topic label="Deleting filters" href="tasks/tmanagedel.html"/>
<topic label="Configuring filter pools" href="tasks/tmanagepools.html"/>
<topic label="Configuring filter pool references" href="tasks/tmanagepoolsref.html"/>
</topic>
<topic label="Remote System Explorer Profiles" href="concepts/cprofile.html">
<topic label="Creating a second profile" href="tasks/tbeginsecprofile.html"/>
<topic label="Deleting a profile" href="tasks/tbegindeleteprofile.html"/>
</topic>
<topic label="Team support" href="concepts/cteam.html">
<topic label="Using team support" href="tasks/tteamsup.html"/>
<topic label="Working with profiles and team support" href="tasks/tteamsup1.html"/>
</topic>
<topic label="Shells and commands in the Remote Systems view" href="concepts/crunremcmds.html">
<topic label="Running and viewing commands and shells using the Remote Commands view" href="tasks/truncmdsview.html"/>
<topic label="Working with command shells" href="tasks/twrkcmdshl.html"/>
</topic>
<!-- TODODeferred after RSE 1.0
<topic label="User actions" href="concepts/cuseractions.html">
<topic label="Managing user actions" href="tasks/tworkuseract.html"/>
<topic label="Editing an existing type" href="tasks/tedittype.html"/>
<topic label="Removing an existing type" href="tasks/tremtype.html"/>
</topic>
-->
<topic label="Search for text and files on remote servers" href="tasks/tmanagesearch.html">
<topic label="Using search parameters with special characters" href="ref/rsearch.html"/>
</topic>
<!-- TODODeferred after RSE 1.0
<topic label="Compiling programs" href="concepts/cremcompile.html"/>
-->
<topic label="Managing archived files" href="tasks/tarchive.html"/>
<!-- TODODeferred after RSE 1.0
<topic label="Importing resources from a remote file system" href="tasks/tremoimp.html" />
<topic label="Exporting resources to a remote file system" href="tasks/tremoexp.html" />
<topic label="Building programs on a remote system" href="tasks/tbuild.html" />
-->
<topic label="Accessing Remote System Explorer preferences" href="ref/rrsepref.html"/>
<topic label="Saving User IDs and passwords" href="tasks/tbeginpass.html"/>
<topic label="Legal" href="notices.html"/>
</toc>