Configuration for remote operations

To use the workbench to run SQL statements, utilities, and commands, or to browse and access files, on remote servers, 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 must be properly configured.
Depending on the operating system of the target server on which you want to run commands or utilities, the workbench 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 the workbench uses:
Table 1. Protocol that is used to run commands and utilities on remote servers
Operating system Method for remote commands and utilities
Windows When connecting to a local database on Windows, DAS is used.
When connecting to remote databases, SSH is first attempted. If SSH is unavailable or is not set up properly, then DAS is attempted, with these exceptions:
  • For remote DB2 for Linux, UNIX, and Windows V9.7 servers, protocols are attempted in the following order: SSH, SMB, and then DAS.
  • For remote DB2 for Linux, UNIX, and Windows V8.2 servers, only DAS is used.
Linux or UNIX SSH is used.

When you browse and access remote file systems, the SFTP protocol is always used. When you browse for files remotely on a Windows system from within the workbench product, you must look in the default directory (/cygdrive/c) to find the Windows drives and the associated file systems paths. No other Windows file system directory paths are valid when you use the workbench product to run commands.

Requirements for DAS or SSH and SFTP on the local client

To use DAS, a connection to a locally installed DB2 database or connection to a DB2 UDB Administration Client (DAC) is required. If you do not have a locally installed DB2 database, DAC is required to communicate with the IBM® Data Server Client and the DB2 Administration Server (DAS).

You must also have connectivity to the DAC that is running on the same machine as the database. You need a connection to the DAC to communicate with the IBM Data Server Client and the DB2 Administration Server (DAS). The IBM Data Server Client connectivity libraries can be provided by either of the following ways:
  • By a local DB2 instance
  • By the DAC

In either case, make sure the bin directory is in the path before you start the workbench. (In Linux, this is handled by sourcing $INST_HOME/sqllib/db2profile.) The DB2 UDB Administration Client is available from developerWorks® at http://www.ibm.com/developerworks.

For example, to install the IBM Data Server Client on a Linux system, complete the following steps:
  1. Install the IBM Data Server Client.
  2. Create a DB2 instance.
  3. Source db2profile in $INST_HOME/sqllib/ before you start the workbench. (For example, add it to your .bashrc.)

To use the SSH and SFTP protocols, no additional configuration is required on the client. The workbench product comes pre-configured with an SSH and SFTP client.

Requirements for DAS, SSH, or SMB and SFTP on the remote server

To use DAS on a Windows system, the DB2 Administration Server (DAS) must be started, and port 523 must be open.

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 be open.

To use the SSH and SFTP protocols on a Windows system, an OpenSSH environment must be set up. The workbench 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). The workbench 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 log in 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.

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 machine.
  • Access to the Interprocess Communications share (IPC$) must be available.
  • The Server service must be started.
    Note: To start the service, click Control Panel > Administrative Tools > Services > Server.
  • 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.

Feedback