# Banalytics Agent Core 2.1.0

## Release summary

Banalytics Agent 2.1.0 is the JDK 25 release of the edge runtime. It updates the Core platform to Spring Boot 4.1.0, Spring Framework 7, Jakarta EE APIs, and Jackson 3 while retaining the existing Agent configuration model.

## Installation and runtime

- The Windows x64, Linux x86_64, and Linux ARM64 installation packages query the portal for the default Core release.
- The installer then requests a JDK download URL for that release and operating-system architecture, downloads the archive, and verifies its SHA-256 checksum before extraction.
- The Windows x64 package uses WinSW 2.12.0 to run Core as the `BanalyticsBox` Windows service. It starts the packaged JDK directly, writes wrapper diagnostics under `logs`, and configures restart after a service failure.
- Re-running the current Windows installer stops an existing `BanalyticsBox` service, replaces the JDK only after the new archive is verified, and starts the existing service registration again. WinSW reads the current service XML at service start, so no separate refresh is required. The local `config` directory is retained.
- Windows module upgrades run from the package directory, append diagnostics to `logs\upgrade-job.log`, wait up to 90 seconds for the service to reach `STOPPED`, swap `modules-upgrade` into `modules` while retaining `modules-backup`, and then wait up to 90 seconds for `RUNNING`. Service errors and timeouts return a non-zero status.
- A new installation starts with the Default installation profile, containing only Core. After the local agent is associated with a portal account, an operator can select an installation profile in the local console and install the corresponding modules through the normal software-upgrade workflow.

## Compatibility

- Existing Agent configuration remains supported. For an Agent earlier than 2.1.0, install the new package and copy the previous `config` directory before starting the replacement installation.
- The release uses JDK 25. The runtime is not changed while the Windows service is running: use the current installer package, which stops the service before replacing its JDK. Keep a backup of `config` when moving an older Agent to a different installation directory.
- Module builds that contain native dependencies are platform-specific. Install a module artifact matching the Agent operating-system identifier: `windows-x86_64`, `linux-x86_64`, or `linux-arm64`.

## Support

If the installer cannot resolve the default release or its matching JDK, use the Contact support link from the local Agent console or visit [Banalytics support](https://banalytics.live/contact-support/).