EM: App Deployment > Global Settings

Overview

In BBj 19.20 and higher, Global Settings allows administrators to configure key deployment options for both Web and Desktop applications. Under General settings, you can specify secure connections and override host or port information. The Web App Only section provides controls for user interface behavior, development settings, and client response timeout to optimize web-based app performance. The Desktop App Only section enables you to manage distribution directories, cache settings, and custom error messaging for desktop deployments. These global settings help ensure consistent and flexible deployment across BBj application environment.

Location

EM Navigator → Web → App Deployment → Global Settings

Toolbar

Button	Function
	Removes/deletes selected application(s) or files from the system.
	Refreshes the displayed list of applications and their status.
	Creates a new folder within the current displayed directory.
	Enables to choose a folder/file from your local system.

App Deployment Global Settings

Global Settings: General

The General settings define default behaviors for all applications. These configurations, including secure connections and network overrides, directly control application operation and network access. Proper management of these global parameters is essential for consistent and secure application infrastructure.

General Properties

Setting	Description
Secure TC Connection	When unchecked, it disables Secure TC Connection. When checked, it enables a secure encryptedSecure TC Connection.
Host Override	Defines the host used by the desktop application client to connect to Jetty. If undefined, the host will be the Hostname defined for the Web server. To manage servers, select BBjServices Servers.
Port Override	Defines the port number used by the desktop application client to connect to Jetty. If undefined, the port will be the HTTP Port defined for the Web server. To manage servers, select BBjServices > Servers.

Web App Only

The Web App Only section contains settings specific to browser-based BBj applications. It allows administrators to control browser behavior, manage session handling, customize appearance, and define client-side response rules. These configurations enhance the user experience and optimize how BBj Web Apps behave in different browser environments.

Web App Only Properties

Setting	Description
Disallow Console	When unchecked, The interpreter session will not terminate and will allow interactive console access. When checked, the BBj interpreter session will immediately terminate if it attempts to drop to the console for any reason.
Show Browser Warning	When unchecked, no browser warning message will be shown, and the application will operate without displaying alert notifications to user. When checked, a browser warning message will be displayed to user under specific conditions or behaviors within the web application.
Show Confirm Close Dialog	When unchecked, the window or tab closes immediately without confirmation. When checked, a confirmation dialog appears before closing the window or tab.
Manage Browser History	When unchecked, data loss can occur if the user clicks the Back button while working in an unsaved state. When checked, the application manages the browser history and Back button to prevent accidental data loss.
Development Mode	When unchecked, it suppresses default browser handling of F1 and F12 keys. When checked, the application allows normal browser handling of function keys F1 and F12.
Omit BASIS CSS	When unchecked, the default BASIS CSS is included and applied automatically. When checked, the default BASIS CSS is omitted and the developer must provide all CSS rules.
Client Response Timeout	Sets the length of time in seconds a non-responsive BUI session will be considered active. If the session expires without response, the web tier will send a NET_DROPPED error back to the server. A value of -1 means no timeout. The default value is 300.

Desktop App Only

The Desktop App Only settings control options for locally deployed BBj applications. These apps run via a launcher JAR that creates a native application with its own JRE. Settings like Distribution Output Directory, Remote Cache Cleanup, Use Request Server Name and Custom Error Message customize app distribution and runtime behavior. Unlike Web Apps, Desktop Apps install per client with a dedicated JRE.

Desktop App Only Properties

Setting	Description
Distribution Output Directory	Specifies the local folder where the generated Desktop App distribution files will be saved; click the icon to browse and select the desired output from your local system directory. Note: Directory such as C:\ is selected, its name appears in the Directory Name field at the bottom. Clicking OK confirms the selection and updates the Distribution Output Directory field with the chosen path.
Remote Cache Cleanup	When checked, it automatically removes outdated or unused cached files from remote client systems. When unchecked, cached files remain on clients and may not be updated or cleaned automatically.
Use Request Server Name	When checked, the application uses the server name from the client’s HTTP request header. When unchecked, it uses the configured server hostname instead.
Custom Error Message	When filled, the specified text is shown as a custom error message for Desktop App launch issues; when left blank, the default system error message is used instead.
Windows Require Administrator	When unchecked, the Desktop App installs and runs without requiring administrator privileges, enabling setup in user accessible locations like %USERPROFILE% without triggering User Account Control (UAC). When checked, the Desktop App requires administrator privileges to install and run, which is necessary when using protected directories like %PROGRAMFILES%. Enabling this setting ensures full access to required directories and files during installation and execution.
Windows Base Install Directory	Displays the Windows base directory for installing the Desktop App. Accepts existing environment variables (e.g., %USERPROFILE%) or full paths. The directory must already exist and must not be set to a system root path (e.g., C:\). A subdirectory matching the app name will be created inside this location for installation. The default value is %USERPROFILE%.
macOS Base Install Directory	Displays the macOS base directory where the Desktop App will be installed. Accepts environment variables (e.g., $HOME) or absolute paths. The specified directory must already exist and cannot be the system root (/). A subdirectory named after the app will be created inside this location during installation. The default value is $HOME.
Linux Base Install Directory	Displays the Linux base directory where the Desktop App will be installed. Accepts environment variables (e.g., $HOME) or full paths. The directory must already exist and must not be the root path (/). A subdirectory named after the app is created within this location during installation. The default value is $HOME.