EM: BBjServices > Settings

Admin Keep Log (days)

Number of days to retain the Admin Server log files.

*Admin Log

Full path and primary filename for the Admin Server log files. Filenames will be appended with a number such as AdminServer.log.0.

*Admin Log Max Size (MB)

Maximum size for the Admin Server log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

BBjServices Keep Log (days)

Number of days to retain the BBjServer log files.

*BBjServices Log

Full path and primary filename for the BBjServices log files. Filenames will be appended with a number such as BBjServices.log.0.

Defines how much detail BBjServices records in its logs, from basic informational messages to highly detailed diagnostic entries that help with monitoring and troubleshooting.

BBjServices Log Max Size (MB)

Maximum size for the BBjServices log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

Config Change History

Maintain a history of all changes made to configuration options and files.

BBjServices consists of a number of components requiring a variety of configuration options and files. Maintaining a history of all changes made to these files makes it possible for administrators to better manage system.

Debug Keep Log (days)

Number of days to retain the Debug log files.

*Debug Log

Full path and primary filename for the Debug log files. Filenames will be appended with a number such as Debug.log.0.

Determines how much detail is captured in debug logs, ranging from targeted configuration details to full system activity, helping administrators choose the right depth of information for monitoring and troubleshooting.

Debug Log Max Size(MB)

Maximum size for the Debug log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

File Open Statistics

• When unchecked, file-level access activity is not tracked.

• When checked, detailed statistics on file openings are collected for performance monitoring and diagnostic purposes.

Filesystem Keep Log (days)

Number of days to retain the Filesystem Server log files.

*Filesystem Log

Full path and primary filename for the Filesystem Server log files. Filenames will be appended with a number such as FilsystemServer.log.0.

*Filesystem Log Max Size(MB)

Maximum size for the Filesystem Server log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

*Heapdump Directory

The full path to a directory to hold future BBjServices heap dump files. Heap Dump file names will follow the format.

Max Log File Viewer (MB)

Maximum size of log files that can be opened in the log file viewer.

Mem Stats Freq (minutes)

Interval in minutes between logging of the current memory statistics.  If you set it to 5 min, then it logs the current memory usage every 5 minutes. This is the information that shows up in the memory usage graph. For finer control and more detailed metrics related to memory usage and other JVM-related information in BBj 18.00+, see BBj Metrics.

Number of days to retain the PRO/5 DS Server log files.

*PRO/5 DS Log Max Size (MB)

Maximum size for the PRO/5 DS Server log file before rolling over to a new file. Old files will be kept for the number of days specified in the keep setting.

SQL Engine Debug Level

Level of debugging output to display in the SQLEngineServer.log files.

SQL Engine Log Level

Level of optimization and query-related logging to display in the SQLEngineServer.log files. Note that including optimization logging will drastically increase the size of the log files. Logging levels include: Partial Optimization, Complete Optimization, and User/SQL Statement. The optimization levels include information typically useful for BASIS Support/Engineering when looking into query performance issues. User/SQL Statement logging logs all SQL statements executed and includes the user who executed the statement.

SQL Keep Log (days)

Number of days to retain the SQL Engine Server log files.

*SQL Log

Full path and primary filename for the SQL Engine Server log files. Filenames will be appended with a number such as SQLServer.log.1, SQLServer.log.2, etc., as the log is rotated according to the configured size and retention settings.

*SQL Log Max Size (MB)

Maximum size for the SQL Engine Server log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

Web Server Keep Log (days)

Number of days to retain the Jetty Web Server log files.

*Web Server Log

Full path and primary filename for the Jetty Web Server log files. Filenames will be appended with a number such as Jetty.out.0.

Web Server Log Level

Level of logging to include in the Jetty.out file.

*Web Server Log Max Size (MB)

Maximum size for the Jetty Web Server log file before rolling over to a new file. Old files will be kept for the number of days specified in the “keep” setting.

• When unchecked, interprocess communication through BBj named pipes is disabled, preventing applications from exchanging data using this method.

• When checked, pipe functionality is enabled, allowing processes to communicate and transfer information efficiently within the BBj environment.

• When unchecked, function-level debugging in BBj remains disabled, ensuring normal execution without detailed diagnostic tracking.

• When checked, debugging is enabled, capturing granular information about BBj function calls to assist with troubleshooting and performance analysis.

• When unchecked, the system verifies whether a local Data Server is available before processing database requests, ensuring standard connection validation.

• When checked, this verification is skipped, allowing database operations to proceed without performing the local server check.

Change the default location for caching.

• When unchecked, only the main filesystem error is logged, showing limited detail.

• When checked, the complete error chain is logged, including all underlying causes, to provide clearer insight for troubleshooting.

• When unchecked, process termination proceeds without generating a thread dump.

• When checked, BBjServices captures a thread dump immediately before terminating one or more server processes to aid diagnostics.

• When unchecked, BBj network communication relies on older Transport Layer Security (TLS) versions with lower security guarantees.

• When checked, the server enforces TLS 1.3 to provide stronger encryption, and improved overall protection for client-server data exchange.

• When unchecked, files can be opened simultaneously by multiple processes, which may increase flexibility but risks data conflicts.

• When checked, each file is locked for exclusive access by a single process, ensuring data integrity and preventing concurrent write operations.

• When unchecked, the BBj interpreter runs with debugging disabled, preventing debugger attachment and avoiding any added diagnostic overhead.

• When checked, interpreter debugging is enabled so the interpreter can be debugged from compatible tools.

Set the default log directory.

Defines the maximum allowable size (in bytes) for ASCII-based BBj programs, limiting how large a program can be when saved or compiled.

NVARCHAR as Fixed Length CHAR

• When unchecked, NVARCHAR columns retrieved from third-party SQL database channels remain variable-length fields, preserving their original behavior and storage characteristics.

• When checked, NVARCHAR columns are automatically converted into fixed-length CHAR fields, ensuring compatibility with systems or applications that require consistent field lengths.

• When unchecked, internal server errors are only written to the logs without user notification, limiting visibility to administrators reviewing log files.

• When checked, the system actively alerts administrators of internal errors in real time, ensuring immediate awareness for faster troubleshooting.

• When unchecked, BBjServices skips printer discovery during startup, reducing service start time but leaving the printer list to be resolved later the first time printing is used.

• When checked, BBjServices queries the host operating system at startup and caches all available printers so they are immediately available to BBj printing features. See: BBjPrinter.

• When unchecked, a dropped client session can leave its in-use resources (such as open files or locks) in place until normal cleanup occurs.

• When checked, the server automatically frees resources held by the disconnected session, preventing stale locks and allowing other users to proceed.

• When unchecked, files can be opened in read-only mode without requiring the explicit O_RDONLY option in the OPEN verb.

• When checked, the OPEN verb enforces explicit use of the O_RDONLY option before granting read-only access, ensuring stricter control over file operations.

• When unchecked, SQL ENCRYPT and DECRYPT functions may follow database-specific behavior that differs from BBj’s native encryption functions.

• When checked, SQL ENCRYPT and DECRYPT functions align with BBj’s native behavior, ensuring consistent handling of encryption and decryption across both environments.

Secure NTDS Encrypter

The class that is used as the secure NTDS encrypter.

• When unchecked, stored procedures and triggers can run in multi-threaded interpreters, allowing concurrent execution for higher performance.

• When checked, stored procedures and triggers run in single-threaded interpreters, ensuring serialized execution for consistency and easier debugging.

• When unchecked, program executions make use of the cache file to improve performance by reusing previously compiled versions.

• When checked, each program execution bypasses the cache file, forcing recompilation for every run and ensuring the most current version is always executed.

• When unchecked, SQL statements are analyzed and optimized before execution to improve query efficiency and performance.

• When checked, query analysis is bypassed, and statements are executed directly without optimization, which may reduce processing overhead but can result in slower performance for complex queries.

Thin Client JVM Wait Time

Set thread pool size Default: -1.

• When unchecked, file creation runs within the current process, which may slow down performance if the operation is resource-intensive.

• When checked, file creation is handled in a forked process, improving responsiveness and isolating the operation to reduce the impact on the main server thread.

• When unchecked, BBjServices performs filesystem operations over a non-encrypted channel without SSL/TLS.

• When checked, filesystem I/O is secured with SSL/TLS (property Use SSL on Filesystem) and takes effect after a BBjServices restart.

• When unchecked, Windows permissions integration is disabled for BBjServices.

• When checked, Windows permissions are enabled and enforced for the service.

• When unchecked, BBjServices does not enforce login at connection time, so sessions run without credential checks and any authorization must be handled by the application or operating-system context.

• When checked, BBjServices requires valid user credentials and applies the configured security model (BBj Users/Groups or, if enabled, Windows permissions) before granting access.

Set default user for use with BUI. Default is nobody.

Set BBjServices working directory.

Allow Trigger Debugging

• When unchecked, triggers run without developer-level diagnostic output, keeping execution silent and streamlined.

• When checked, triggers generate detailed debugging information to help identify logic or runtime issues during development or troubleshooting.

*Password

Password field secures trigger configuration access by requiring an authentication credential, ensuring only authorized administrators can define, modify, or manage trigger settings.

*Trigger Config File

Designates the location of the configuration file that defines trigger behavior, and clicking the icon opens a file selection dialog to browse and assign the desired file path directly.

*User Name

Set the user name for the trigger.

*Working Directory

Click the icon to set the working directory for triggers.

BBj Build Date

BBj build data and time.

BBj Build ID

BBj build ID.

BBj Version

BBj version.

BBjServices Start Time

Time and date that BBj Services was started.

Defines the text displayed at the top of the login screen when accessing the Enterprise Manager through a browser.

Specifies an optional link to a Grafana dashboard for visualizing BBjServices metrics and performance data.

Check DB For Encryption Passwords

• When unchecked, replication proceeds without validating database encryption credentials, permitting access attempts without any credential verification.

• When checked, replication enforces validation of encryption passwords before granting access to encrypted content.

Deny as Replication Target

• When unchecked, the server can participate as a valid target in BBj replication configurations.

• When checked, the server is explicitly blocked from serving as a replication target, preventing any replication data from being directed to it.

• When unchecked, index writes are buffered and committed in batches, improving performance at the cost of possible data loss if the system fails before flushing.

• When checked, each FULLTEXT index write is immediately flushed to disk, ensuring maximum data safety and consistency but with potential impact on write performance.

Max Document Size(MB)

Maximum size of the documents or records stored in a Lucene index. This include document indexes as well as FULLTEXT indexes in SQL.

Max Search Results

Maximum number of search results that a Lucene-related search can return. This applies to document indexes and FULLTEXT indexes in SQL. The larger the value, the more memory will potentially be utilized when performing search queries, which may impact performance depending on system resources.

• When unchecked, FULLTEXT index updates occur synchronously with data writes, ensuring immediate consistency between content and index but potentially slowing write operations.

• When checked, index updates are performed asynchronously in the background, improving write performance while introducing a short delay before new or updated content appears in search results.

Iterations Before Pause

Number of times a table is analyzed before it is paused.

Pause Time (ms)

The length of time for each pause.

Java DATE Types (Uncheck for MS Access)

• When unchecked, DATE type columns are returned to Microsoft Access in its expected legacy integer format, ensuring compatibility with Access despite the behavior being non-standard per ODBC and JDBC specifications.

• When checked, DATE type columns follow the correct Java DATE standard, providing specification-compliant metadata handling for all other databases and drivers.

64/32 Bit

Bit mode of the system.

Java Vendor

JVM vendor.

Java Version

Current Java version installed.

A Java module is a packaging mechanism that enables you to package a Java application or Java API as a separate Java module, allowing better encapsulation, dependency management, and control over access to internal code.

License Attempt Timeout

Longest time to wait (in ms) for a license. Default is 5000 ms.

Max BBJSP Licenses

Maximum number of licenses for BBJSP applications.*

Max License Usage

Maximum number of servlet and service licenses BBjServices can allocate, ensuring balanced resource use and preventing performance issues. See: BBjServlets.*

Max Web Services Licenses

Maximum number of licenses for Web Services.*

Queue Size

How many requests can wait for a license.*

Retry Interval

Length of the pause, in milliseconds, between attempts to obtain a license. Default is 200 ms.

OS Name

Name of the operating system.

OS Version

Current version of the operating system.

Pin Programs and Resources

• When unchecked, programs and resources are released from memory after use, requiring reloading each time they are accessed.

• When checked, programs and resources remain pinned in memory, reducing reload overhead and improving performance for repeated access.

Pin by BBj Session

• When unchecked, BBj does not retain the session in memory, releasing resources after the session ends.

• When checked, BBj keeps the session in memory, reducing reload overhead and improving performance for recurring session use.

Recheck Session Classpath

• When unchecked, BBj runs the session using the existing classpath without revalidating it, reducing overhead but ignoring potential updates.

• When checked, BBj revalidates the session classpath on each use, ensuring any changes are applied at the cost of additional processing.

Suppress Client Object Errors

• When unchecked, client object error messages are written to the system console, making all errors visible for diagnostic purposes.

• When checked, client object error messages are suppressed, reducing console output and avoiding unnecessary error reporting during execution.

Suppress Printer Ack Back

• When unchecked, printer acknowledgment messages are written to the system console, providing confirmation of printer communication.

• When checked, printer acknowledgment messages are suppressed, reducing console output and avoiding unnecessary logging during normal operation.

Suppres UI Ack Back

• When unchecked, user interface acknowledgment messages are sent back to the client, confirming UI actions but increasing network traffic.

• When checked, acknowledgment messages are suppressed, lowering network overhead and improving performance in environments with frequent UI interactions.

Use DVK License If Present

• When unchecked, BBj operates without using a DVK license, even if one is available.

• When checked, BBj automatically consumes a DVK license when present, ensuring that DVK-licensed features are enabled.

System Connection User

User account used by the SQL engine for system-level database access operations such as reading/writing to data dictionary files. This is typically used when using data server syntax to access data dictionary files remotely. In most cases, this setting should be left blank unless a specific system-level SQL user is required.