To use
IBM
Data Studio to
run SQL statements, utilities, and commands, or to browse and access
files on remote servers, you must ensure that the DB2® Administration Server (DAS), the Secure Shell
(SSH) protocol, or the Microsoft Windows Server Message Broker
(SMB) protocol and the Secure File Transfer (SFTP) protocol are properly
configured.
Depending on the operating system of the target server on which
you want to run commands or utilities,
IBM
Data Studio uses
the DB2 Administration Server
(DAS), the Secure Shell (SSH) protocol, or the Microsoft Windows Server
Message Broker (SMB) protocol. The following table shows which protocol
IBM
Data Studio uses.
Table 1. Protocol that is used to run commands and utilities on remote
serversOperating system |
Method for remote commands and utilities |
Windows |
For connecting to a local database on Windows, the SMB protocol or
SSH is used. For connecting to remote databases, SSH is first attempted.
If SSH is unavailable or is not set up properly, the SMB protocol
is attempted. If the SSH or the SMB protocol are unavailable, DAS
is attempted.
Note: Remote DB2 for Linux, UNIX, and Windows V8.2
servers use only DAS.
|
Linux or UNIX |
SSH is used. |
When you browse and access remote file systems, the SFTP protocol
is always used. For Windows systems
that run the supported OpenSSH service implementation from Cygwin,
when you browse for files remotely from within IBM
Data Studio, you
must look in the default directory (cygdrive)
to find the Windows drives
and the associated file systems paths. No other Cygwin file system
directory paths are valid when you use IBM
Data Studio to
run commands.
Requirements for DAS or SSH and SFTP on the computer
where you installed IBM
Data Studio
- DB2 Administration Server
(DAS)
- The IBM® Data Server Client
is required in order to communicate with the DB2 Administration Server (DAS).
The connectivity
libraries that are required for remote operations can be provided
by installing either of the following products:
- A local DB2 database server
instance
- IBM Data Server Client
- Secure Shell (SSH) and Secure File Transfer (SFTP) protocols
- To use the SSH and SFTP protocols, no additional configuration
is required on the client. IBM
Data Studio is
pre-configured with an SSH and SFTP client.
Requirements for DAS, SSH, or SMB and SFTP on the
remote server
- DB2 Administration Server
(DAS)
- To use DAS on a Windows system,
the DB2 Administration Server
(DAS) must be started, and port 523 must be open.
- Secure Shell (SSH) and Secure File Transfer (SFTP) protocols
- To use the SSH and SFTP protocols on Linux or UNIX system,
the SSH and SFTP daemons must be started. If they are not running,
start them or ask your system administrator to start them. SSH requires
that port 22 must be open.
To use the SSH and SFTP protocols on
a Windows system, an OpenSSH
environment must be set up. IBM
Data Studio supports
SSH communication to DB2 for Linux, UNIX, and Windows servers
that run in a Cygwin emulation environment through Portable Operating
System Interface for UNIX (POSIX).
In its Open Source distribution, the Cygwin environment includes the
OpenSSH server implementation of the SSH and SFTP protocol (Cygwin
Net packages openssl, openssh). IBM
Data Studio uses
the Secure File Transfer protocol (SFTP) for all file system browsing
and remote file transfer. Therefore, SFTP must be enabled.
Setting
up the OpenSSH environment on a target server that runs on a Windows system requires installing
Cygwin, configuring the daemon to run as an automatic service, and
synchronizing the Cygwin environment user accounts and groups with
the operating system user repository to allow remote login to the
remote Windows system. You
can download and install Cygwin from http://cygwin.com. For information about installing and configuring
Cygwin on a Windows server,
see Installing Cygwin on a Windows server and Configuring Cygwin on a Windows server.
- Microsoft Windows Server Message Broker (SMB) protocol
- To use SMB on a Windows system,
port 445 must be open. SMB also has the following requirements:
- The Remote Registry service must be started on the target computer.
- Access to the Interprocess Communications share (IPC$) must be
available.
- The Server service must be started.
Note: To start the service,
click .
- Simple File Sharing must be disabled.
For more information about the configuration that is required
for the various editions of the Windows operating
system for SMB, see Configuring Windows operating systems for using SMB.