Compare

Wider Language Support

Many ORB's - including OmniORB and TAO - actually offer only C++ language support. This can be quite restrictive, particularly from the client-side perspective. With only C++ support, developers are forced to obtain and support a second, Java ORB from a different vendor. Orbacus is designed for rapid development, deployment and support in your choice of C++ or Java in one integrated environment. The OMG has not standardized on how to do administration of CORBA applications.

So configuration of a CORBA application or registering a server with the Implementation Repository varies a lot from one CORBA product to another. If you deploy only Orbacus/C++ and Orbacus/Java applications then you need to learn just one set of administration techniques. But if you deploy TAO (C++) applications and JacORB (Java) applications then you need to learn two sets of administration techniques. This can be an extremely difficult task because of the lack of good documentation for TAO.

Wider Platform support - ability to porting to others

Orbacus supports a wide range of platforms from various variants of Windows and Linux to Irix. Besides the wide platform coverage that Orbacus provides as standard, we will also consider ports to currently unsupported platforms such as AS/400, SCO Unix, OpenVMS. We will support these platforms at the appropriate support level for your company - standard, silver or gold.

Future-proofing CORBA Investments- Compliance

Many vendors claim to fully support CORBA. In reality, most have only selectively implemented elements of the specification. For example, OmniORB claims CORBA 2.6 compliance, but the product does not implement core features such as the Interface Repository (IFR), Implementation Repository (IMR) or portable interceptors. Not having an IMR means that OmniORB servers cannot be auto-launched. They must be started manually.

Orbacus provides its own implementation of the Interface Repository, V2.5 compliant, and the Interoperable Naming Service. It also operates with the Orbix telecom logging, events, notification and trader services, all of which are compliant with their OMG standard specification.

Orbacus is compliant with both the C++ and Java Language Mappings (formal/99-07-41 and formal/99-07-53, respectively), including abstract interfaces, fixed data types, and valuetypes. Additionally, in the C++ mapping, Orbacus provides support for real namespaces, exceptions and modules.

Now, iCMG (third party vendor) provides the implementation of CORBA Component Model (CCM) for Orbacus. Orbacus users can program in the OMG's standard component model along with a container runtime environment. In addition, there are tools for supporting assembly, deployment and management of CORBA3.0 components. For details please visit http://www.icmgworld.com/.