Bundle Management Framework

• Introduction
• Directory Structure
• Repositories Involved

Introduction

The bundle management framework is provided by OpenHarmony for you to manage application bundles (installation packages). The following figure shows the architecture of the bundle management framework.

Figure 1 Bundle management framework architecture

• BundleKit includes external APIs provided by the Bundle Manager Service, including the APIs for application installation and uninstallation, bundle information query, and bundle state change listeners.

• The bundle scanning sub-module parses pre-installed or installed bundles on the local device and extracts information from them for the bundle management sub-module to manage and make the information persistent for storage.

• The bundle installation sub-module installs, uninstalls, and updates a bundle.

• The bundle installation service is an independent process used to create or delete installation directories and has high permissions.

• The bundle management sub-module manages information related to application bundles and stores persistent bundle information.

• The bundle security management sub-module verifies signatures, and grants and manages permissions.

Directory Structure

/foundation/bundlemanager/bundle_framework_lite
     ├── frameworks
     │      └── bundle_lite                # Client code used for communication between the BundleKit and Bundle Manager Service
     ├── interfaces
     │      ├── kits
     │      │     └── bundle_lite         # BundleKit APIs exposed externally
     │      └── inner_api
     │             └── bundlemgr_lite      # Core implementation code of BundleKit and internal APIs provided by the Bundle Manager Service for other subsystems
     ├── services
     │      └── bundlemgr_lite             # Implementation code of the Bundle Manager Service
     └── utils
             └── bundle_lite                # Utility code used during the implementation of the Bundle Manager Service

• The Bundle Manager Service is running in the foundation process.
• The Bundle Manager Service is registered with sa_manager. sa_manager runs in the foundation process and sets up a thread runtime environment for the service. For details about how to create and use the Bundle Manager Service, see SA Framework.
• The Bundle Manager Service starts upon OS startup.
• You can use the bm tool to install the specified HAP. (Taking hispark_taurus as an example, you can obtain the bm tool from the out/hispark_taurus/ipcamera_hispark_taurus/dev_tools/bin directory after the version building.)

./bin/bm install -p /nfs/xxxx.hap

Repositories Involved

ability_ability_lite

bundlemanager_bundle_framework_lite