ORBacus

ORBacus
Name	ORBacus
Developer	IONA Technologies; Progress Software
Released	1999
Latest release	4.x
Programming language	C++
Operating system	Cross-platform (Windows, Linux, Solaris, AIX)
License	Commercial

ORBacus is a commercial Object Request Broker (ORB) product that implements the CORBA standard for distributed object computing. It enables interoperability among applications written in C++, Java, and other languages across heterogeneous platforms such as Windows NT, Linux, and Solaris. ORBacus has been deployed in industries including telecommunications, finance, defense, and aerospace where integration with legacy systems, middleware frameworks, and standards like IIOP and CORBA is required.

Overview

ORBacus provides a CORBA-compliant runtime and suite of development tools for building, deploying, and managing distributed objects. The product targets system integrators, software vendors, and enterprise IT teams who need a robust middleware solution compatible with standards such as the Object Management Group specifications. Its feature set typically includes an ORB core, Portable Object Adapter (POA) implementations, an Interface Repository, an Implementation Repository, and management utilities for lifecycle and fault management. ORBacus has been positioned alongside other ORBs such as TAO (The ACE ORB), JacORB, and ORBexpress in vendor comparisons.

History and Development

Development of ORBacus originated at IONA Technologies in the late 1990s during a period of rapid adoption of CORBA across telecommunications and enterprise systems. IONA, known for products like IONA's Artix and the IONA Orbix line, focused ORBacus on standards compliance and cross-platform portability. Following industry consolidation, stewardship of ORBacus passed through acquisitions and corporate transitions involving vendors such as Progress Software Corporation. Over time, ORBacus evolved to support emerging platform releases from vendors like IBM and Sun Microsystems, add language mappings for C++, and adapt to integration patterns used by systems from Siemens, Ericsson, and Nortel Networks.

Architecture and Features

ORBacus implements key CORBA facilities including the Object Request Broker, the Portable Object Adapter, and support for the Internet Inter-ORB Protocol (IIOP). Its architecture emphasizes modularity with pluggable transports and protocol stacks to interoperate with systems using TCP/IP stacks on Linux, TCP listeners on Microsoft Windows, and network management platforms from HP (Hewlett-Packard). Features commonly cited in product descriptions include Object Activation via an Implementation Repository compatible with OMG specifications, an Interface Repository accessible to development tools, support for the CORBA Naming Service and Event Service, and tools for IDL compilation and stub/skeleton generation that interoperate with GNU Compiler Collection toolchains and Microsoft Visual Studio build environments.

ORBacus also offers enterprise-oriented services such as secure IIOP with SSL integration, thread-pool and concurrency policies to align with POSIX threading models, and facilities for logging and diagnostics compatible with vendor monitoring suites like HP OpenView and IBM Tivoli. Bridging options for interoperability with Web Services stacks and adapters for Java EE application servers have been provided by third-party integrators.

Implementation and Usage

Developers use ORBacus by writing CORBA IDL interfaces, invoking the ORBacus IDL compiler to generate language-specific bindings, and implementing server objects in supported languages such as C++, Java, and sometimes Python via available mappings. Typical deployment patterns include multi-tier architectures integrating Oracle Database backends, middleware message buses like TIBCO Enterprise Message Service, and front-end systems hosted on Apache HTTP Server or NGINX. ORBacus has been embedded in telecom elements interoperating with switching systems from vendors such as Alcatel-Lucent and Huawei, and in control systems for aerospace contractors like BAE Systems.

Administrators manage ORBacus instances with supplied tools for process activation, logging, and configuration; integration scripts often interface with configuration management tools from Puppet (software), Ansible, or Bash-based deployment environments. Integrations with LDAP directories and enterprise identity providers have been used to implement access controls consistent with organizational policies.

Performance and Scalability

ORBacus was engineered for low-latency remote method invocation and predictable behavior in high-throughput environments. Performance tuning options include object adapter policies, connection pooling, thread allocation, and transport-layer parameters to optimize throughput on platforms from Sun Microsystems SPARC servers to commodity x86 clusters. Benchmarks performed by system integrators compared ORBacus to alternatives such as TAO (The ACE ORB) and IORB under workloads typical of telecommunications signaling and financial transaction processing. Scalability is achieved through horizontal deployment of ORB instances, use of CORBA Naming and Trading Services for dynamic discovery, and integration with load-balancing appliances and software from vendors like F5 Networks.

Licensing and Support

ORBacus has historically been distributed under a commercial license with options for runtime deployment and developer editions. Support and maintenance contracts typically provide access to patches, updates, and technical support channels provided by commercial stewards such as Progress Software Corporation or authorised partners. Professional services, including porting, performance tuning, and protocol bridging, have been offered by systems integrators including Accenture, Capgemini, and niche consultancies specializing in CORBA migrations and legacy system modernization.

Category:Middleware Category:CORBA implementations