Have a Question?
< All Topics
Print

00967: Current BBj default ports for the various BBj servers

Title:

Current BBj default ports for the various BBj servers

Description:

Typically, there is no need to change these ports from the default settings. Occasionally other applications may be using one of these default ports. The default TCP/IP ports may be changed inside the BASIS Enterprise Manager Configuration window. 

Below is a listing of all BBjServices ports that the various BBj Servers use by default. 

Filesystem Server: 2000 – Provides access to the file system from a BBj Interpreter.

SQL Engine Server: 2001 – Provides SQL capabilities to the BBj Interpreter/ODBC/JDBC.

Admin Server: 2002 – Manages the BBj Services via the Enterprise Manager (EM).

Thin Client Server: 2003 – Provides a thin client BBj Interpreter session for local and remote clients.

Terminal Server: 2004 – Provides a TermConsole BBj Interpreter session under UNIX. Also provides IO interpreter sessions under UNIX and Windows.

Interpreter Server: 2005 – Provides access to a fat client BBj Interpreter session on the local machine.

Thin Client Proxy Server: 2006 – Provides access to Thin Client Servers, both local and on a remote machine, from a local BBj executable.

Bridge Server: 2007 – Provides access to the Java BBjBridge which enables a Java program to call a BBj program.

Port Request Server: 2008 – Interacts as a local server with the Proxy Manager Server to provide port information about the various servers to a BBj session when it starts.

Proxy Manager Server: 2009 – Maintains a list of currently active ThinClientProxyServers running on the local machine and interacts with the Port Request Server to ensure a thin client BBj session connects correctly.

BBj PRO/5 Data Server: 2100 – Enables clients running PRO/5 to access files through the BBj file system using normal Data Server syntax. BBx and BBj clients can coexist without running a PRO/5 Data Server as long as the BBx clients use Data Server syntax to open files. Since all file access is taking place through the BBj file system, no file locking conflicts will occur.

Thin Client Server (SSL): 2103 – Provides a secure connection to a thin client BBj Interpreter session for local and remote clients.

Filesystem Server (SSL): 3000 – Provides secure access to the file system from a BBj Interpreter.

SQL Engine Server (SSL): 3001 – Provides secure SQL capabilities to the BBj Interpreter/ODBC/JDBC.

BBj PRO/5 Data Server (SSL): 2100 – Enables clients running PRO/5 to securely access files through the BBj file system using normal Data Server syntax. BBx and BBj clients can coexist without running a PRO/5 Data Server as long as the BBx clients use Data Server syntax to open files. Since all file access is taking place through the BBj file system, no file locking conflicts will occur.

XCALL Server : 4444 – Enables the Java-based BBj XCALL Server, allows for the calling of a BBj program from PRO/5 or Visual PRO/5 10.0 and higher via the XCALL Verb.
The XCALL Server does not support rarely-needed client GUI features such as creating windows or calling BBjThinClient API methods. The XCALL Client Proxy Server continues to provide those client-side features.

Jetty Web Server (HTTPS): 8443 – Web Services, BUI programs, and DWC applications that use secure HTTPS communicate with BBjServices’ Jetty web server on this port.

Jetty Web Server: 8888 – Web Services, BUI programs, and DWC applications that use HTTP communicate with BBjServices’ Jetty web server on this port.

Status Server: 11057 – Returns an error when two or more BBjServices are running and provides various types of debugging status information.

Last Modified: 07/12/2023               Product: BBj           Operating System: N/A

Table of Contents
Scroll to Top