valutazioni - 0, GPA: 0
(
)
)
|
da questo dispositivo ha anche altre istruzioni :
Facilità d'uso
HP OpenVMS Application Modernization and Integration Infrastructure Package, Version 2.2
• Distributed NetBeans Client for OpenVMS, which is a plug-in for NetBeans running on your
desktop. You install the NetBeans IDE (from NetBeans.org) and the Distributed NetBeans Client
for OpenVMS on your desktop system.
• IDE Server for OpenVMS, which runs on OpenVMS, and provides remote services for the client
plug-in. You install the IDE Server on your OpenVMS system. Communication between the
client system and the remote server system is encrypted using SSL. Only the Java SE JDK is
required on the OpenVMS server system; NetBeans or any additional plug-in modules are not
required.
BridgeWorks (Available on OpenVMS Alpha only)
BridgeWorks is an automated component-creation tool that exposes existing 3GL-based applications and
modules as components using the JavaBeans, Enterprise JavaBeans, or COM object models and thus
facilitates the development and deployment of distributed applications.
BridgeWorks can "componentize” or "wrap" applications written in COBOL, Pascal, BASIC, C,
FORTRAN, Ada, and any other 3GL language that supports the OpenVMS Calling Standard. Such
applications must have routines that are externally callable. BridgeWorks can also wrap DCL procedures,
ACMS applications, and aggregate datatypes (structures and arrays).
BridgeWorks consists of a GUI development tool on the Windows NT/2000 desktop, a server manager
component on OpenVMS, and extensive online help. All the necessary files and code are generated to
build the selected application or module into a component in a three-tier, distributed architecture. Web
and desktop clients can then communicate with these new distributed components using industry-standard
technologies as if they were the application that enables the development and deployment of solutions for
the widest range of client platforms and the Internet.
OLE for Process Control (OPC) for OpenVMS (Available on OpenVMS Integrity only)
OLE for Process Control (OPC) is an open standards specification based on the OLE, COM, and DCOM
technologies developed by Microsoft, used in industrial automation and enterprise systems. OPC
Transport is intended for use in OPC environments and is a subset of COM. Only unauthenticated COM
is supported.
COM for OpenVMS (Available on OpenVMS Alpha only)
Component Object Model (COM) is a technology from Microsoft Corporation that allows developers to
create distributed network objects. The former Digital Equipment Corporation and Microsoft jointly
developed the COM specification. First released by Microsoft on Windows NT as Network Object
Linking and Embedding (NetOLE), and then renamed Distributed COM (DCOM), the COM specification
now includes network objects.
COM is used to create distributed applications made up of reusable objects. COM locates objects locally
or in a network and uses the Remote Procedure Call (RPC) wire protocol to communicate between these
objects across the network.
COM on OpenVMS delivers connectivity and interoperability between OpenVMS Alpha and Windows
NT systems. With COM for OpenVMS, programmers write distributed applications that run across
systems in a heterogeneous environment. COM for OpenVMS is based on the Microsoft COM shipped on
Windows NT 4.0 SP5 and implements many of the features of Microsoft COM including activation,
automation, monikers, type libraries, structured storage, and NTLM authentication on OpenVMS.
COM is not available on OpenVMS VAX. For more information, refer to the HP COM for OpenVMS
Software Product Description (SPD 70.45.xx).
Software Product Description
5
...