How do I launch a root shell from within Eterm?

It is sometimes useful to spawn a UNIX shell from within an Eterm session. Here is the procedure:

  • From within your active Eclipse session in Eterm
  • Press F2
  • Press T to launch the TCL shell
  • Type the following to launch a UNIX shell:
  • Type the following to escalate the shell to superuser (root) mode:
    su -
  • Enter the root user’s password when prompted
  • You are now at the root (#) prompt
  • To exit, type:
  • Press ESC at the TCL (;) prompt
Note: the user logged into Eclipse must have access to TCL, and you must know the root password.

For further reference, view a screencast of this procedure.

Unable to display content. Adobe Flash is required.

Why doesn’t Eterm look right when logged in as root on a Linux server?

Eterm uses a proprietary terminal emulation and does not transmit this information to the Linux server upon login. If you don’t manually set the terminal type, you will experience issues (vi won’t work, backspace will result in strange characters, etc.).

After logging in, type:

export TERM=vp60
Backspace will not work, but you can use CTRL-BACKSPACE or the LEFT ARROW keys at the login screen.

How do the Solar and Eterm clients communicate with the server?

The Eterm (TUI) client communicates with the UniVerse database server via the telnet protocol (TCP port 23). It uses a proprietary implementation of the ViewPoint terminal type to offer additional features in Eclipse (send/receive files, drag/drop, hyperlinks, etc.).

The Solar (GUI) client communicates with the JBoss application server via the HTTP and HTTPS protocols (default TCP ports 2080 and 2443). It is deployed using Java Web Start.

In both cases, the business logic is performed on the database and application servers, not in the client installed on each workstation.

Eclipse Network Utilization

We are often asked how much bandwidth is used by Eclipse for planning new deployments. Here are some guidelines for estimating the network utilization of Eclipse users based on real-world data we’ve gathered from existing Eclipse customers:

  • Solar customers: 3 KB/s (24 kbps) per user
  • Eterm customers: 1 KB/s (8 kbps) per user

As you can see, the bandwidth requirements for Eclipse are quite low, but it’s important to take into consideration that users’ Internet usage is not limited to Eclipse, and Eclipse performance will suffer if the software has to fight for bandwidth being used for other means (i.e. streaming video and audio, file sharing, etc.). As such, we recommend prioritizing the following protocols used by Eclipse through QoS whenever possible:

  • The Eterm client communicates using the telnet protocol (TCP port 23).
  • The Solar client communicates using a proprietary web service protocol (TCP ports 2080 and 2443).
  • The Eclipse signature capture and document imaging processes communicate over standard Microsoft file sharing protocols.
  • The Eclipse printing processes communicate over standard Windows and UNIX printer ports (i.e. socket, LPD, etc.).

During the initial Solar client installation and after each Eclipse “point” upgrade, the Solar client will perform a one-time download of approximately 20 MB of data. For branches with large numbers of users, this can cause a temporary spike in bandwidth consumption when a large number of users launch the new version of Solar for the first time.

For analyzing your users’ unique usage patterns, we recommend using your network hardware’s built-in tools bandwidth utilization monitoring, or by runningĀ Wireshark on a workstation.