blob: 8dfb4872c601cf185b2218018aaaa34521dee022 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
<html>
<head>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>RSE Connector Services</title>
<link rel="stylesheet" type="text/css" href="../book.css">
</head>
<body>
<h1>RSE Connector Services</h1>
<p>
Connector Services provide the mechanism for maintaining a connection to a particular remote system, requesting whatever credentials are
required for authentication, and for controlling the persistence of those credentials. A connector service is typically created
or referenced by a subsystem configuration when a new subsystem instance is being created.
</p><p>
Every subsystem has a connector service. Some subsystems will share a connector service among themselves.
Subsystems that share a connector service all connect and disconnect at the same time.
For example, a file subsystem and
a shell subsystem that are both using the SSH protocol will share the same connector service instance so that their connections are established and
removed at the same time.
</p><p>
Connector services use credentials providers (see <code>ICredentialsProvider</code>) to establish any credentials needed for authentication to a
remote system.
</p>
</body>
</html>
|
