Basic Enterprise Application Realm

Basic Enterprise Application Realm Documentation
  • 1 About BEAR
  • 2 Release Notes
  • 3 Developer Toolkit
  • 4 Installation & Upgrades
    • 4.1 Installation Steps
    • 4.2 Network Requirements
    • 4.3 Application Server Initialization (First Run)
    • 4.4 Uninstallation
  • 5 Backend Adminitration
    • 5.1 Introduction
    • 5.2 Common Commands
    • 5.3 Application Server Commands
    • 5.4 Resource Monitor Commands
    • 5.5 Sharepoint Commands
    • 5.6 Database Commands
  • 6 Frontend Adminitration
    • 6.1 User Management
    • 6.2 Package Management
    • 6.3 Installing Documentation Packages
    • 6.4 Application Storage
    • 6.5 Resource Monitoring
    • 6.6 Resource Scaling
    • 6.7 Starting & Stopping BEAR
    • 6.8 Security
      • 6.8.1 TLS
    • 6.9 Physical Storage
      • 6.9.1 RAID
      • 6.9.2 File Systems
      • 6.9.3 Viewing the Storage Summary
      • 6.9.4 Decommissioning (wiping) Disks
      • 6.9.5 Storage Management
    • 6.10 Event Distribution
    • 6.11 Hostnames & Ports

5.3 Application Server Commands

January 24th, 2026

5.3.1 reload_appserver

Gracefully reloads the shared memory realm without bringing down the application server or causing a service interruption. This is primary used when making emergency live changes via the shell and provides a way to reload the shared memory in the same operation or when problems with the shared memory prevent access to the web UI.

Usage

reload_appserver

5.3.2 reset_https_ciphers

This resets not just the TLS ciphers but reverts the TLS configuration of the entire application server to the default settings (although user provided certificates remain in place).

This impacts the following:

  • API is reverted to TLS 1 and 1.2.
  • API security level is reverted to default.
  • API policies for key exchange, authentication, encryption, and cipher are removed.
  • UI is reverted to TLS 1 and 1.2.
  • UI security level is reverted to default.
  • UI policies for key exchange, authentication, encryption, and cipher are removed.
  • Certificate-based user authentication is disabled.

However, this does not impact the following:

  • Custom TLS certificates remain in place unchanged.
  • User authentication certificates remain in place - though not used until certificate-based authentication is re-enabled.
  • Custom ports for HTTPS remain unchanged.
Usage

reset_https_ciphers

5.3.3 restart_appserver

Handles non graceful restart of the application server via the following steps:

  1. Stops the httpd service.
  2. Kills the resource monitor process.
  3. Unloads the shared memory realm
  4. Loads the shared memory realm.
  5. Starts the httpd service.
  6. Starts the resource monitor process.
Usage

restart_appserver

5.3.4 start_appserver

Makes the BEAR application server persistently active by performing three steps in order:

  1. Loads the shared memory realm.
  2. Enables the httpd service.
  3. Starts the httpd service.
  4. Starts the resource monitor process.

If the BEAR database is installed on the same host, it will assume that is required and wait indefinitely until the database is detected as up and running and provide output to the terminal indicating that it is "Waiting for BEAR database to start".

It is important to note that this is not a normal startup command but a persistent state command. If called, then the BEAR application server will remain as an auto start service (starts after reboot) until stopped with stop_appserver.

Usage

start_appserver

5.3.5 stop_appserver

Stops and persistently disables the application server by performing the following steps:

  1. Stops the httpd service.
  2. Kills the resource monitor process.
  3. Disables the httpd service.
  4. Unloads the shared memory realm

Once stopped using this command, the BEAR application server will be completely disabled and will not restart following a reboot.

Usage

stop_appserver

previous: Common Commands next: Resource Monitor Commands