Tag: XPNET

BASE24 and core Networking Component XPNET timeline

The technical timeline for BASE24 and its core networking component, XPNET, reflects the evolution of high-availability payment switching on HP NonStop (Tandem) systems.

Technical Evolution Timeline

  • 1980s: The Foundation
    • BASE24 Release: Originally developed by Applied Communications Inc. (now ACI Worldwide), BASE24 was built for the Tandem Guardian operating system.
    • XPNET Introduction: Developed as the Message-Oriented Middleware (MOM) to handle all transaction routing and communications. It introduced a multi-node architecture allowing different “satellite” processes (ATM, POS, Host) to communicate.
  • 1990s: Scale and Maturity
    • Classic Era: BASE24 “Classic” became the industry standard for ATM and POS switching.
    • XPNET 3.x: Enhanced to support larger networks and more complex auditing through NCPCOM.
    • Language & DB: The system relied on TAL (Tandem Application Language), COBOL, and the Enscribe database.
  • 2000s: The Shift to BASE24-eps
    • 2003–2005: ACI introduced BASE24-eps (Electronic Payment Systems). This was a re-architecture using C++ and Java to provide platform independence.
    • XPNET 4.1: Released to support the transition, adding features like Common Transport Subsystem (CTS) for better Pathway integration and support for external processes.
    • z/OS Support: By 2009, BASE24-eps was fully ported to IBM z/OS using CICS and VSAM.
  • 2010s – Present: Modernisation & Cloud
    • 2014–2017: Continued updates to BASE24 Classic R6.0, maintaining its relevance for legacy users.
    • Cloud Enablement: Recent versions of BASE24-eps focus on REST API integration via tools like LightWave, allowing legacy XPNET paths to be exposed as web services.
    • Active/Active Environments: Modern implementations focus on “continuous availability” using GoldenGate for data replication between sites. 

Key Technical Components

  • NMM (Network Management Module): The core process of XPNET that manages the configuration of lines, stations, and links.
  • LCONF: The Logical Network Configuration File used by XPNET to define how messages route between processes.
  • Auditing: XPNET provides the primary transaction auditing mechanism, which is still utilized by both Classic and eps versions.

BASE24 and core Networking Component XPNET