Direct Transaction Engine Connection

SSH Tunneling is supported with the direct property. By default, direct is set to false. When set to true, the property indicates the Connection will be made directly to a TE (instead of to a broker). This enables a connection string to be set up in a third party tool, for example, DBVisualizer, on a tunnel you have set up to a specific TE.

The syntax for setting up a JDBC connection to an SSH tunnel is:


To find the TE's host and port, use the show domain summary command in NuoDB Manager.

$ nuodbmgr --broker host --password domainPassword
NuoDB host version: 2.6: Professional Edition
nuodb [domain] > show domain summary
[broker] * ip-172-31-40-24/ (us-east-1)
Database: test, template [Single Host] MET, processes [1 TE, 1 SM], ACTIVE
[SM] ip-172-31-40-24/ (us-east-1) [ pid = 32594 ] [ nodeId = 1 ] RUNNING
[TE] ip-172-31-40-24/ (us-east-1) [ pid = 32611 ] [ nodeId = 2 ] RUNNING

The JDBC URL can then be constructed using the TE's port.


Multiple TEs can be specified in the JDBC URL as follows:


Tunnel Options

The ssh command allows you to establish a tunnel into a remote machine and to execute commands on that remote machine.

Direct localhost Tunnel

In this example, a direct tunnel is established between a local machine (localhost) and a target Amazon EC2 NuoDB TE instance, going from port 48005 on localhost to an open port, 48010, of the EC2 host ( as user ec2-user.

$ ssh -L 48005:localhost:48010 ec2-user@

Using a Jump Server

In this example, an Amazon EC2 instance acts as the jump server (Host A),, with user ec2-user. The jump server opens an SSH connection to a known host, (Host B), that has an open port on 48010 and creates a port locally on port 48005.

# ssh -L 48005:<Host B>:48010 ec2-user@<Host A>
$ ssh -L 48005: