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

4.1 Installation Steps

January 23rd, 2026

The following steps are applicable to all versions of BEAR.

4.1.1 Before You Begin

Prior to installing BEAR, you should prepare the ACHE host correctly and only proceed once the following steps are complete.

  1. Successfully install the ACHE operating system.
  2. Ensure that you have access to the ACHE root user password (Abcd1234 by default).
  3. Set a desired hostname for the system. This can be done with the following command:

# echo <HOSTNAME> > /etc/hostname

where <HOSTNAME> is replaced with your desired hostname.

  1. Configured the network interface as required. This can be done via the nmtui command and following the on-screen menus.
  2. [optional] If users are expected to reach this host via a hostname rather than an IP address, you should ensure that the host is registered to your organisation's DNS server. Ensure that both forward (A) and reverse (PTR) records are created.
  3. With the hostname set and network configured, reboot the host once to ensure the settings have persisted.
  4. [optional] If desired, obtain the latest full release of bear from the BEAR Download Center. By default, ACHE comes preloaded with BEAR installation binaries located at /root/BEAR. If you download a newer full release, unzip the file to a desired location as shown in the example (assumes the bear archive has been placed in /tmp).

# cd ~ # tar-xzf /tmp/bear_1.1.0_base.tgz

4.1.2 BEAR Installation Types

Because BEAR is made up of several components, there may be different installation patterns depending on whether you are installing all components on a single host, or dedicated hosts. Each installation scenario is described below.

Installation types

Server Type Installation Components (in order)
Complete 1. File Server
2. Database
3. Application Server
Database 1. Resource Monitor
2. Database Server
File Server 1. Resource Monitor
2. File Server
Application Server 1. Resource Monitor
2. Application Server

All commands are assumed to be run as the root user.

If you have downloaded a newer release of BEAR than the one supplied with ACHE, then the installation files may be located in a different location to the default used in these examples.

4.1.3 Installation Commands

All installers are automated with no user interaction required during execution. Post installation configuration is described in each component's Backend Administration chapter.

  1. As root, switch to the directory that contains the installation commands. By default this is /root/BEAR.

# cd ~/BEAR

  1. Install the components required for your server type as described in BEAR Installation Types.
File Server # ./install_bear_sharepoint_*
Database # ./install_bear_database_*
Resource Monitor # ./install_bear_resmon_*
Application Server # ./install_bear_appserver_*

Do not install the Resource Monitor if installing the Application Server.

4.1.4 Next Steps

After installation, each component must be set up correctly. The application server must be set up last. Configuration steps should be performed in the following order:

  1. Database and file server
  2. Resource monitor
  3. Application server
previous: Developer Toolkit next: Network Requirements