 |
How would I implement COM for OpenVMS?
A developer might implement COM applications on OpenVMS
in the following ways:
- For existing OpenVMS applications, you can
encapsulate an OpenVMS application as a COM object.
A Windows COM client can then interact with the existing
OpenVMS application. This allows business-critical data
to stay on the OpenVMS system while
making the OpenVMS data accessible through a Windows
application.
- For existing COM applications on other operating
systems, you can port COM objects to OpenVMS
to take advantage of specific OpenVMS features. This
allows you to leave other COM objects associated with
the application unchanged on their current platforms,
and lets you port only the objects you need to your
OpenVMS system. You can then revise the ported code
to maximize OpenVMS benefits and at the same time,
minimize the change to the overall application.
- For new OpenVMS applications, you can create
a COM server on OpenVMS. COM client applications on
Windows NT systems, on other OpenVMS systems, or on
other COM-enabled operating systems can access this
OpenVMS COM server.
What other changes has HP made to OpenVMS to enable COM for OpenVMS?
To implement COM on OpenVMS, HP has made the following
changes to the OpenVMS system:
- Added COM APIs to OpenVMS.
HP has added
a complete set of Microsoft COM APIs to OpenVMS.
These APIs allow you to write
and debug COM objects on OpenVMS systems.
(For complete details about COM for OpenVMS development, see
the OpenVMS Connectivity Developer Guide that ships
with the COM for OpenVMS kit.)
- Added an OpenVMS Registry.
COM applications can add, read, change, and delete
the OpenVMS Registry contents. You can view and edit
the contents of the OpenVMS Registry either from
OpenVMS (using the REG$CP utility or Win32® API) or
from Windows NT (using Regedit).
- Extended OpenVMS security to enable secure connections
between Windows NT and OpenVMS.
These enhancements include support for
common user authentication and
authenticated RPC with NTLM security.
In addition, HP has moved some DCE RPC
functions into the base operating system to provide
limited support for Microsoft RPC calls.
- Added application event logging on OpenVMS.
Applications write system, security, and application activity
information to the OpenVMS event logs.
You can view the contents of the event logs on OpenVMS
either from OpenVMS (using the PATHWORKSTM Admin
utility) or from Windows NT (using the Windows NT
Event Viewer).
» Return to the COM for OpenVMS home page
|
