EM: BBj Services > Servers

• When unchecked, the selected server does not automatically start when BBjServices are launched, requiring manual startup from the Servers panel.

• When checked, the server automatically starts as part of the BBjServices initialization sequence, ensuring it becomes available without manual intervention.

Defines the level of detail written to the server log, allowing administrators to control the amount and type of runtime information recorded.

• When unchecked, the server operates in non-blocking mode, allowing multiple client requests to be handled concurrently without waiting for one request to complete before starting another.

• When checked, the server runs in blocking mode, forcing each client request to complete in sequence before the next one begins, which may simplify troubleshooting but reduces concurrency.

• When unchecked, the server communicates over standard, unencrypted TCP/IP, leaving all connections in plain text.

• When checked, the server requires SSL/TLS encryption for all connections, using the configured keystore alias to provide security certificates. Enabling this option ensures encrypted client-server communication but requires a valid keystore and password to be defined.

• When unchecked, the selected server remains disabled at BBjServices startup and must be started manually from the Servers panel.

• When checked, the server automatically starts during BBjServices initialization, ensuring availability without manual action.

• When unchecked, client authentication using .rhosts files is disabled, preventing remote users from bypassing password entry through host-based trust.

• When checked, .rhosts authentication is allowed, enabling remote clients listed in trusted host files to connect without entering a password.

• When unchecked, the BBj Language Server does not launch with BBjServices and must be started manually before it can process program execution requests.

• When checked, the server initializes automatically during BBjServices startup, ensuring that BBj applications can run without requiring manual activation.

Defines the level of detail written to the server log, allowing administrators to control the amount and type of runtime information recorded.

• When unchecked, the server operates in non-blocking mode, allowing multiple client requests to be handled concurrently without waiting for one request to complete before starting another.

• When checked, the server runs in blocking mode, forcing each client request to complete in sequence before the next one begins, which may simplify troubleshooting but reduces concurrency.

• When unchecked, the server communicates over standard, unencrypted TCP/IP, leaving all connections in plain text.

• When checked, the server requires SSL/TLS encryption for all connections, using the configured keystore alias to provide security certificates. Enabling this option ensures encrypted client-server communication but requires a valid keystore and password to be defined.

• When unchecked, the server performs .rhosts verification, requiring validation of trusted remote host entries before allowing client access.

• When checked, .rhosts verification is bypassed, permitting connections without host-based authentication checks.

• When unchecked, the server performs Ident protocol verification to confirm the identity of the remote user associated with a TCP connection.

• When checked, Ident verification is bypassed, allowing connections without requiring user identity confirmation from the remote host.

• When unchecked, only explicitly defined root paths are scanned and made available to clients.

• When checked, all accessible root directories are scanned automatically, exposing every root location to the server for client access.

• When unchecked, the PRO/5 DS server does not start automatically and remains inactive until it is manually launched.

• When checked, the server instance starts automatically, enabling immediate handling of PRO/5 DS connections based on the defined configuration.

Defines the level of detail written to the server log, allowing administrators to control the amount and type of runtime information recorded.

• When unchecked, client operations proceed without waiting for a locked resource, potentially returning errors if the resource is busy.

• When checked, the server blocks operations until the requested resource becomes available, ensuring sequential access control.

• When unchecked, the PRO/5 Data Server remains disabled and cannot accept client requests or process operations.

• When checked, the server is enabled, allowing client connections and handling requests according to its configured resources.

• When unchecked, client-server communication occurs without encryption, leaving data in transit exposed to interception.

• When checked, Secure Sockets Layer(SSL) enforces encrypted communication, ensuring data privacy and integrity between clients and the PRO/5 Data Server.

• When unchecked, the server validates the client’s remote host (rhost) information to confirm the origin of the connection.

• When checked, this validation is bypassed, allowing connections without verifying the remote host identity.

• When unchecked, the server performs an ident protocol check to confirm the identity of the client connecting to the service.

• When checked, this verification step is skipped, reducing authentication overhead but lowering connection validation security.

• When unchecked, client authentication does not integrate with Windows NT Directory Services (NTDS), and access is validated only through standard server credentials.

• When checked, authentication integrates with NTDS, allowing centralized identity and permission management through Windows Active Directory, a feature available only when BBjServices is running on Windows.

• When unchecked, access requires authentication and open access is not allowed.

• When checked, the server permits open access by bypassing NTDS authentication, which reduces connection security and should be used only in trusted environments.

• When unchecked, the PRO/5 Data Server uses its standard (non-advisory) locking behavior, enforcing normal record/file locks under the server’s control.

• When checked, the server applies advisory (cooperative) locks on data files. All access must be coordinated through the Data Server; direct access from outside sources is not supported and may result in file corruption. See: Setting Advisory Locking for the Data Server - Windows NT.

• When unchecked, new MKEYED files use the legacy format, restricted to a maximum size of 2 GB (or up to 4 GB on certain PRO/5 versions and platforms).

• When checked, new MKEYED files use the 64-bit format, supporting file sizes larger than 4 GB as allowed by the operating system and filesystem. See: MKEYED Verb - Create MKEYED File.

• When unchecked, files are created without tagged record support, meaning only fixed or variable-length records can be used.

• When checked, enables tagged record format, allowing records to include named fields and supporting more flexible data structures within PRO/5 Data Server files.

• When unchecked, MKEYED file identifiers (FIDs) are fully exposed to client applications, allowing direct visibility of internal file IDs.

• When checked, masks the MKEYED file identifiers so they are hidden from client applications, enhancing security and preventing reliance on internal FID values. See: FID() Function - Get File Identification BBj.

• When unchecked, backslashes in pathnames are automatically converted to forward slashes for cross-platform compatibility.

• When checked, original backslashes are preserved in pathnames exactly as entered.

• When unchecked, the server scans only the explicitly configured root directories.

• When checked, every available root directory is scanned automatically, ensuring full directory coverage.

• When unchecked, the Memory Mapped Protocol service remains inactive, preventing client applications from establishing connections through memory-mapped access.

• When checked, the service becomes active and available, enabling clients to communicate with the PRO/5 Data Server using memory-mapped file operations for faster, low-level access to data. See: PRO/5 Memory Mapped Data Server Access.

• When unchecked, the BBj Language Server does not accept encrypted connections, leaving communication unprotected over plain sockets.

• When checked, Secure Sockets Layer (SSL) is enforced, ensuring encrypted client-server communication to protect sensitive data during transmission. See: Secure Sockets Layer.

Provides PRO/5 applications with direct file access through the BBj PRO/5 Data Server without going through the TCP/IP layer. It works when both systems run on the same host and connect using 127.0.0.1 , configuration is handled through !DSOPEN or the config.bbx file, and remains transparent to application code. This approach delivers significant performance gains, especially in multi-user, read-heavy environments. Security and performance are managed with the same controls available to other connections, including SSL, file permissions, locking, and timeout settings.

• When unchecked, file access is not controlled by advisory locks, allowing external processes to access the same files directly, which risks corruption if not properly managed. See: An introduction to advisory locking.

• When checked, the server enforces advisory locking so that all access must pass through the Data Server, ensuring coordinated and safe file operations.. See: Setting Advisory Locking for the Data Server - Windows NT.

• When unchecked, new MKEYED files are created in the legacy 32-bit format, which restricts file sizes to 2 GB (or up to 4 GB on some older PRO/5 systems).

• When checked, the server creates MKEYED files in the 64-bit format, allowing significantly larger file sizes and overcoming the 32-bit limitations. See: MKEYED Files.

• When unchecked, MKEYED file records are created without tags, storing only untagged key and data values.

• When checked, each record includes tag metadata, allowing applications to organize and retrieve data using tagged fields in addition to keys.

• When unchecked, file identifiers (FIDs) for MKEYED files are exposed in their original form, allowing applications to access and display them directly.

• When checked, FIDs are masked for enhanced security, preventing applications from revealing or misusing the underlying file identifiers.

• When unchecked, backslashes in pathnames are automatically converted to forward slashes for cross-platform compatibility.

• When checked, original backslashes are preserved in pathnames exactly as entered.

• When unchecked, the server scans only the explicitly configured root directories.

• When checked, every available root directory is scanned automatically, ensuring full directory coverage.

• When unchecked, the Proxy Manager service does not start automatically with BBjServices, requiring manual startup before any client connections can be managed.

• When checked, the Proxy Manager service starts automatically with BBjServices, making it immediately available to handle client connection requests and manage communication routing.

• When unchecked, the SQL Engine service does not start automatically with BBjServices, requiring manual startup before any client connections can be managed.

• When checked, the SQL Engine service starts automatically with BBjServices, making it immediately available to handle client connection requests and manage communication routing.

Defines the level of detail written to the server log, allowing administrators to control the amount and type of runtime information recorded.

• When unchecked, the server processes requests in non-blocking mode, immediately returning control if a resource is not available, which may cause retries at the application level.

• When checked, the server processes requests in blocking mode, holding the operation until the requested resource becomes available, ensuring predictable sequencing at the cost of potential wait time.

• When unchecked, the BBj Language Server does not accept encrypted connections, leaving communication unprotected over plain sockets.

• When checked, Secure Sockets Layer (SSL) is enforced, ensuring encrypted client-server communication to protect sensitive data during transmission. See: Secure Sockets Layer.

• When unchecked, the server scans only the explicitly configured root directories.

• When checked, every available root directory is scanned automatically, ensuring full directory coverage.

• When unchecked, the Terminal server does not initialize during BBjServices startup, preventing any terminal sessions from connecting through this service.

• When checked, the Terminal server automatically starts with BBjServices, making it available for client connections according to the configured bind address, port, and client limits.

• When unchecked, the Thin Client service does not start, preventing any client sessions from connecting.

• When checked, the service launches automatically, allowing Thin Client connections to the BBjServices instance based on the configured port, bind address, and client limits.

• When unchecked, the Thin Client permits console sessions, allowing direct server access from the console.

• When checked, console sessions are blocked, ensuring only network-based Thin Client connections are accepted for improved control and security. See:Unresponsive Thin Client.

• When unchecked, host-based authentication through .rhosts is disabled; all Thin Client connections require standard login credentials.

• When checked, .rhosts authentication is enforced, allowing connections from hosts listed in the server’s trusted files without requiring a password. This configuration is only appropriate for secure, tightly controlled networks.

Start

• When unchecked, the Thin Client (SSL) service remains inactive, and no secure client sessions can be established through SSL/TLS, even if other configuration values are present.

• When checked, the service automatically starts with BBjServices, enabling encrypted Thin Client connections that use the configured bind address, port, and keystore for certificate validation.

• When unchecked, the Thin Client permits console sessions, allowing direct server access from the console.

• When checked, console sessions are blocked, ensuring only network-based Thin Client connections are accepted for improved control and security. See:Unresponsive Thin Client.

• When unchecked, host-based authentication through .rhosts is disabled; all Thin Client connections require standard login credentials.

• When checked, .rhosts authentication is enforced, allowing connections from hosts listed in the server’s trusted files without requiring a password. This configuration is only appropriate for secure, tightly controlled networks.

• When unchecked, the Thin Client Proxy service does not run, and clients cannot connect through the proxy layer.

• When checked, the service automatically starts with BBjServices, allowing clients to connect using the defined bind address and port, while enforcing the configured maximum client limit.

Start

• When unchecked, the Web server remains inactive, and no HTTP or HTTPS connections are accepted.

• When checked, the Web server starts automatically, enabling browser-based access to BBj applications through the configured HTTP and SSL ports.

• When unchecked, the BBj Web server does not accept unencrypted HTTP requests, requiring clients to connect securely through SSL if enabled.

• When checked, the Web server listens for and accepts standard HTTP requests on the configured port, allowing unsecured client connections in addition to any SSL connections.

• When unchecked, the BBj Web server does not support encrypted connections, allowing only unsecured HTTP traffic.

• When checked, the Web server requires a valid SSL configuration and accepts secure HTTPS connections on the defined port, ensuring encrypted communication between clients and the server.

• When unchecked, the Web server accepts requests only for the exact hostname specified in the Hostname field. Requests that use alternate names are rejected.

• When checked, the Web server accepts requests for both the configured hostname and additional aliases, providing flexibility for environments with multiple valid DNS names or host headers.

• When unchecked, the XCALL server does not start, preventing remote procedure calls and external access to server-side functions.

• When checked, the service initializes and runs, allowing configured clients to connect and execute calls through the defined interface and port settings.

Defines the level of detail written to the server log, allowing administrators to control the amount and type of runtime information recorded.

• When unchecked, client connections are handled in non-blocking mode, allowing the server to manage multiple requests concurrently without waiting for any single operation to complete.

• When checked, connections are processed in blocking mode, requiring each request to finish before the next begins, which can simplify handling but may reduce performance under heavy load.

• When unchecked, the XCALL server communicates over plain TCP, transmitting data without encryption and leaving connections vulnerable to interception.

• When checked, the service uses SSL/TLS encryption, requiring a valid keystore and password configuration to secure traffic between clients and the server, ensuring data confidentiality and integrity.

• When unchecked, the XCALL server enforces verification of the client’s rhost identity, requiring that the connecting host match trusted configuration files before granting access.

• When checked, rhost verification is bypassed, allowing connections without host identity checks, which may ease connectivity but significantly reduces security.

• When unchecked, clients can authenticate with their own usernames, and the default user is only applied when no credentials are provided.

• When checked, all client connections are forced to run under the configured default user account, regardless of the credentials. This simplifies authentication but removes individual accountability, so it should be limited to controlled environments where user-specific access is unnecessary.

• When unchecked, client sessions may override the default configuration by specifying their own config file, allowing custom runtime environments.

• When checked, all sessions are required to use the defined default configuration, preventing overrides and enforcing a consistent execution environment across all clients.

• When unchecked, client sessions may override the default working directory with their own specified path.

• When checked, all sessions are locked to the defined default working directory, preventing overrides and ensuring consistent file access and execution behavior across every client connection. See: Configuring BBx.