Why DCOM on non-Microsoft Platforms?
EntireX DCOM brings the DCOM programming model to non-Microsoft platforms in a
manner that is true to the original programming model and wire protocol. DCOM offers
sufficient technical and semantic advantages over existing communications solutions to
justify the effort of bringing it to platforms such as UNIX (IBM S/390 UNIX System
Services, formerly Open Edition, also supported).
EntireX DCOM allows transparent access to in-process, local out-of-process or remote
objects in a heterogeneous distributed environment. Like the Windows NT and 2000
release, EntireX DCOM has support for object naming with monikers, hierarchical object
storage using compound files, binary reuse via COM aggregation, and accessibility from
interpretive/scripting environments via Automation.
EntireX DCOM provides the object-oriented systems-programming services available in
DCOM in a manner that is true to the original programming model, and yet interacts
properly with native programming styles and idioms.
What does EntireX DCOM consist of ?
EntireX DCOM is an implementation of the non-graphical part of Microsoft's DCOM
technology. EntireX DCOM allows DCOM-enabled applications running on non-
Windows platforms to communicate with DCOM components in a heterogeneous
network, i.e. a network with mixed architectures. So, for example, EntireX DCOM allows
DCOM-enabled server applications running on UNIX or UNIX System Services to be
accessed by DCOM clients on Windows NT and 2000, and vice versa.
EntireX DCOM consists of the following main parts:
• Runtime environment
• Software Development Kit (SDK)
In order for DCOM applications and components to run and communicate, it is necessary
to have an EntireX DCOM runtime environment. This consists of a set of shared libraries
(DLLs) and tools to monitor and manage the DCOM multiuser environment.
Software Development Kit (SDK)
The SDK is a collection of tools, libraries and examples which enable the DCO