[Paper Review] On the Use of CORBA in High Level Software Applications at the SLS

M. Boege, J. Chrin|arXiv (Cornell University)|Nov 2, 2001

Distributed and Parallel Computing Systems3 citations

TL;DR

This paper presents a CORBA-based middleware framework for high-level beam dynamics applications at the Swiss Light Source (SLS), enabling distributed, interoperable, and persistent access to accelerator physics, control systems, databases, and logging services. The framework leverages CORBA's Portable Object Adaptor (POA), Implementation Repository (IMR), and Event Service to provide scalable, reliable, and language- and platform-independent communication, proven stable during SLS commissioning and first operation with minimal operator intervention.

ABSTRACT

Beam dynamics applications at the Swiss Light Source (SLS) have benefitted from a distributed computing environment in which the Common Object Request Broker Architecture (CORBA) forms the middleware layer and access point to several different software components.A suite of remote CORBA server objects provides the client with a convenient and uniform interface to the CDEV (Common DEVice) controls library, the TRACY accelerator physics package, the Oracle database, and en event logging facility. Use is made of methods provided by the CORBA Portable Object Adaptor for accessing ORB functions, such as object activation and object persistence, the Implementation Repository for the automatic reactivation of servers, and the CORBA Event Service for the propagation of controls and physics data. An account of the CORBA framework, as used by applications in the commissioning and first operation of the SLS, is presented.

Motivation & Objective

• To develop a scalable, distributed computing environment for high-level beam dynamics (BD) applications at the SLS.
• To enable seamless interoperability between software components written in different programming languages and running on diverse platforms.
• To provide persistent, remotely accessible services for accelerator modeling, device controls, databases, and event logging.
• To reduce client-side complexity by abstracting low-level communication protocols and APIs through CORBA's standardized interface layer.
• To ensure system reliability and minimal operator intervention during SLS commissioning and operation.

Proposed method

• Employed CORBA's Object Request Broker (ORB) as the core communication middleware to enable remote method invocations across distributed components.
• Used the CORBA Interface Definition Language (IDL) to define type-safe interfaces, compiled into stubs and skeletons for C++ and Java clients and servers.
• Leveraged the Portable Object Adaptor (POA) to manage object activation, persistence, and request dispatching with configurable policies.
• Utilized the Implementation Repository (IMR) to automatically reactivate CORBA servers on demand, ensuring service availability.
• Implemented the CORBA Event Service for asynchronous, push-based propagation of control and physics data to clients via event channels.
• Integrated legacy systems (EPICS, Oracle) through CORBA-bridged servers, using ORB marshaling for data transfer.

Experimental results

Research questions

• RQ1 How can a standardized, platform- and language-agnostic middleware improve the integration of heterogeneous beam dynamics software components at the SLS?
• RQ2 To what extent can CORBA's POA and IMR features ensure persistent, scalable, and self-recovering server operation in a real-time accelerator environment?
• RQ3 Can CORBA-based remote method invocation and event-driven communication reduce client-side complexity while maintaining performance and reliability?
• RQ4 How does CORBA-based data access compare to native APIs (e.g., JDBC) in terms of performance for database operations?
• RQ5 What role does the CORBA Event Service play in enabling real-time monitoring and data distribution for accelerator control systems?

Key findings

• The CORBA framework successfully enabled reliable, low-intervention operation of multiple beam dynamics applications during SLS commissioning and first operation.
• The use of the Implementation Repository (IMR) with POA-based servant management ensured automatic server reactivation, enhancing system robustness and availability.
• Database access via CORBA’s marshaling mechanism was observed to be approximately 50% faster than using the JDBC API, indicating performance benefits from CORBA’s optimized data transfer.
• The CORBA Event Service enabled effective asynchronous propagation of recalibrated data and device monitoring events, supporting both push and pull-based communication.
• The framework abstracted low-level communication and API differences, allowing developers to focus on application logic and user interface design rather than system-level integration.
• The entire system demonstrated stability and scalability, supporting complex, real-time applications such as the 3 Hz global orbit feedback system.