EM: App Deployment > Global Settings

Overview

Global Settings enables administrators to configure deployment settings for BUI, DWC, Desktop, and WebUI applications. Under General, you can specify secure connections and override host or port information. The BUI/DWC 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. The WebUI Only section defines configuration properties for hosting WebUI applications, managing deployment parameters, and optimizing browser-based execution. These global settings help ensure consistent and flexible deployment across the 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.

BUI/DWC Only

The BUI/DWC Only section contains default settings for BUI and DWC web apps.

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

Note: This setting is Obsolete.

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.

Note: Desktop browser only show this warning if the user has interacted with the page. Mobile browsers never show this warning. See: beforeunload event.

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 through F24 keys.
When checked, the application allows normal browser handling of function keys F1 through F24.

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.

Note: This setting is intended for specialized applications. Significant BUI behavior is controlled by the default CSS; omitting it will break most applications.

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.

End Action

Dropdown selecting termination action: NONE, DEFAULT, URL, APP, MESSAGE. DEFAULT follows configuration. URL redirects to address, APP launches app, MESSAGE shows text, NONE does nothing. See: BBjBuiCloseAction.

Value	Description
NONE	Specifies that no special termination action occurs. The session ends normally and no redirect, application launch, or message display is triggered.
DEFAULT	Uses the context’s configured default behavior for termination, inherits global or parent-configuration action when the session ends.
URL	Redirects the terminated BUI/DWC session to the specified web address. Requires entering a fully qualified URL for correct redirection.
APP	Launches the specified secondary application when the session ends. Requires providing the application name; termination occurs only after that application starts.
MESSAGE	Displays the specified text message to the user when the session ends. User must provide the message content for display

End Application

Designates the application-name to launch when End Action: APP is selected; if blank, no additional application executes at session end.

End Message

Specifies the text to present to the user when End Action: MESSAGE is selected, replacing the standard termination outcome with that message.

End URL

Specifies the redirect address when End Action: URL is selected; the session navigates to this URL after termination.

Error Action

Controls how the BUI/DWC session behaves when an error occurs, inherit default action, perform no action, redirect, launch application, or display a message. See: BBjBuiCloseAction.

Value	Description
NONE	Indicates that no error-handling action will occur when the session fails. The session simply ends without redirect, application launch, or message.
DEFAULT	Inherits the termination behavior defined at the higher-level configuration (parent or global); no specific action is executed at session end. See: BBjBuiCloseAction.
URL	Redirects the session to a specified web address when Error Action: URL is selected, the URL must be provided in the field.
APP	Launches a specified secondary application when “Error Action: APP” is selected; the user must provide the application name for execution.
MESSAGE	Presents a custom text-message to the user when Error Action: MESSAGE is selected, requires providing the display message content.

Error Application

Specifies the application to launch when Error Action: APP is selected; if left blank, no application will be triggered upon error.

Error Message

Provides the custom text shown to the user when Error Action: MESSAGE is selected, replacing the default error notification display.

Error URL

Specifies the web address for redirection when Error Action: URL is selected; session ends and client navigates to that URL.

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.

WebUI Only

The WebUI Only section defines global configuration parameters for deploying BBj applications in the WebUI browser client. On UNIX systems, BBj automatically invokes xheadless or xvfb to create a virtual display when the DISPLAY environment variable is unset, ensuring proper WebUI initialization. By default, xheadless is used on Linux and xvfb on AIX. Note that xheadless requires glibc 2.18 or later; on older Linux distributions using glibc 2.17, administrators must set the WebUI Virtual Display Program to xvfb using /usr/bin/xvfb-run. See : Applications

Note: On UNIX systems, additional fields WebUI Display and WebUI Virtual Display Program, appear to manage virtual display initialization when the DISPLAY environment variable is not set.

WebUI Only Settings List

Settings	Description
WebUI App Enabled	When unchecked, the application cannot be accessed through the WebUI. When checked: Enables WebUI deployment for this application. Note: WebUI is a premium, licensed feature and isn’t available by default.
WebUI Context Mapping	The URL context path used for WebUI applications. The default is webui.
WebUI Display	The display value used for BBj WebUI sessions on UNIX systems. When unset, BBjServices exports a default display setting or invokes a virtual display.
WebUI Virtual Display Program	Specifies the executable invoked to create a virtual display when the DISPLAY variable is unset. Defaults to xheadless on Linux and xvfb on AIX platforms.