Skip to main content
Technology Platforms

Application Framework · BX‑M / BX‑CM

Java application frameworks and tooling for teams building and operating banking systems.

BX-M targets on-premise development and BX-CM cloud environments. BX-CBP-based offerings require one of them; each also provides batch support and can be evaluated separately.

Java development and runtime platform
BX Studio connects design and source with application, batch and runtime capabilities. BX-M or BX-CM is selected for the environment.

Where BX-M and BX-CM sit

Standard framework

Banks adopt it as their standard framework for online and batch development.

Inside BX-CBP-based offerings

BX-CBP-based suites and solutions require BX-M or BX-CM as their Java development platform.

On-premise or cloud

BX-M serves on-premise development environments and BX-CM cloud development environments.

Where extensions are built

Controlled Extension and Additional Development for BX-CBP-based offerings are built on it.

What BX-M / BX-CM does and how it works

Application framework

Spring-based, with hierarchical transaction processing so business rules live in one place.

Spring-based, with hierarchical transaction processing so business rules live in one place.

Batch engine and scheduler

Spring Batch based, with parameter management, execution monitoring and intervention.

Spring Batch based, with parameter management, execution monitoring and intervention.

Hot Deploy and staged release

Supported service changes reach the running system after Pre-Deploy and Application Staging.

Hot Deploy applies within the supported change scope and validated deployment procedures. Supported product versions and edition compatibility are confirmed for the target deployment.

Supported service changes reach the running system after Pre-Deploy and Application Staging.

BX Studio

Eclipse-based environment that links design and source in both directions.

Eclipse-based environment that links design and source in both directions.

Runtime control

Timeouts, record limits and error thresholds that stop affected transactions.

Timeouts, record limits and error thresholds that stop affected transactions.

Standards and security

Code generation, inspection and impact analysis, plus masking and encryption APIs.

BX-CM adds field-level encryption; edition-specific coverage is confirmed for the target deployment.

Code generation, inspection and impact analysis, plus masking and encryption APIs.

How BX-M / BX-CM relates to other products

Required: one Java development platform in every BX-CBP-based suite and solution.

Every BX-CBP-based suite and solution requires BX-M (on-premise) or BX-CM (cloud), separately licensed products on which Controlled Extension and Additional Development are built. Select the platform for the target environment. Both are sold separately in Korea, Japan and Southeast Asia.

BX-CBP-based offering

BX-CBP · Main ProductBX-PF · Required

Java development and runtime platform

BX-M or BX-CM · RequiredControlled Extension + Additional Development

Separate composition roles

BX-I · OptionalBankware Mobile · Not included
Composition roles and conditions
BX-CBP · Main Product
BX-CBB technical foundation with 11 components, plus the Business Service Library across 11 domains.
BX-PF · Required
Product definition.
BX-M or BX-CM · Required
One platform matched to the environment.
Built on the framework
Controlled Extension and Additional Development.
BX-I · Optional
Interfaces to channels and partners; replaceable by a third-party product.
Bankware Mobile
Not part of this composition.

Composition applies to BX-CBP-based suites and solutions. Whether BX-M and BX-CM are used together is confirmed per engagement.

BX-CA

BX-CA, an AI development-support product, can connect to the BX-CM framework tools, as at Woori Bank.

Cloud & DevOps Platform

BX-CM supports application development. Cloud & DevOps Platform is a separate product for Kubernetes deployment and platform operations.

Application Monitoring

Application Monitoring is also separate; framework use does not establish monitoring coverage.

Product Foundation

What applies when you adopt BX-M or BX-CM

01

Availability

Sold separately in Korea, Japan and Southeast Asia.

02

Choice of edition

BX-M or BX-CM is chosen to match the bank’s development environment.

03

Language and frameworks

Java 21 (OpenJDK or Oracle JDK) with Spring, Spring Batch and Spring Boot 3 in the current technology stack. Supported product versions and edition compatibility are confirmed for the target deployment.

04

Application servers

WebSphere, WebLogic, JBoss, Resin or the internal Spring Boot 3 server. Supported servers and edition compatibility are confirmed for the target deployment.

05

Changes to running services

Hot Deploy supports changes within its supported scope, with Pre-Deploy and Application Staging first. The supported changes and validated procedures are confirmed for the deployment.

Banks and card companies that develop on BX-M and BX-CM

Shinhan Bank

One Java framework across banking applications

FRAMEWORK DELIVERY · BX-M

Shinhan Bank adopted BX-M as its standard Java framework and used it again for its next-generation system. BX-M also supports development and operation of the SOL banking app system.

Woori Bank

A channel framework extended with AI development support

Channel framework and AI development support

Channel standard framework and pilot system on BX-CM and extended with BX-CA generative-AI development support.

Hyundai Card

A next-generation card system built on BX-M

Card-system development

Next-generation card system developed on BX-M for Hyundai Card, with related framework deliveries to Hyundai Capital and Hyundai Commercial.

GMO Payment Gateway

Application and product technology in Japan

Technology adoption

Adopted BX-M and BX-PF; also a Bankware sales partner in Japan.

BX-M also delivered to K-Bank, LINE Bank Taiwan, OK Savings Bank and KB Kookmin Card.

07 / Contact

Tell us about your development environment, and we will show BX-M or BX-CM on it.

Describe your systems, your on-premise or cloud environment and the teams that will build on the platform.