Microsoft® Windows® Distributed interNet Applications Architecture (Windows DNA) is the application development model for the Windows platform. Windows DNA is the first application architecture that integrates the Internet, client/server, and PC models of computing into a framework of distributed computing solutions. Windows DNA specifies how to:
Because Windows DNA relies on a comprehensive and integrated set of services provided by the Windows platform, developers are free from the burden of building or assembling the required infrastructure for distributed applications and can focus on delivering business solutions.
Windows DNA platform technologies and services address the requirements of all tiers of modern distributed applications–user interface and navigation, business process, and storage.
The heart of Windows DNA is the integration of Web and client/server application development models through the Component Object Model (COM). Windows DNA services are exposed in a unified way through COM for applications to use. These services include component management, Dynamic HTML, Web browser and server, scripting, transactions, message queuing, security, directory, database and data access, systems management, and user interface.
Windows DNA also fully embraces an open approach to Web computing, building on the many important standards efforts approved by bodies such as the World Wide Web Consortium and the Internet Engineering Task Force. Adherence to open protocols and published interfaces make it easy to integrate other vendor solutions and provides broad interoperability with existing systems.
Because Windows DNA is based on COM and open Internet standards, developers can use any language or tool to create compatible applications. COM provides a modern, language-independent object model that provides a standard way for applications to interoperate at all tiers of the architecture. Through COM, developers can extend any part of the application via pluggable software components that can be written in C++, Microsoft® Visual Basic®, Java, or other languages. Because of this open approach, Windows DNA supports a broad range of development tools today, including tools from Microsoft, Borland, Powersoft, and many other vendors.
The Microsoft SDK for Java includes the following packages and .cab files for use in integrating Java with other technologies:
| Technology | Package |
| IIS (Active Server Pages) | com.ms.asp com.ms.iis.asp |
| MDAC (OLE DB Simple Provider) | com.ms.osp |
| MTS | com.ms.mtx |
| Microsoft® Internet Explorer classes | iejava.cab |
To install these packages on machines running versions of Microsoft® Windows® prior to Windows 2000, run IntegrationClasses.exe, which is located in the %SDKDIR%\Bin directory.
To install the com.ms.iis.asp package on machines running Windows 2000, run IntegrationClasses2000.exe, which is located in the %SDKDIR%\Bin directory. This package is required to run the ASP Java Component Framework samples that are included with the Microsoft SDK for Java. IntegrationClasses2000.exe also installs iejava.cab, which contains classes that are hooks from Java into Internet Explorer. The other packages cannot be installed on Windows 2000 machines.
Important Iejava.cab uses system tools that are installed by Internet Explorer 4.0 or later. You should not run the Integration .exe files on early Windows 95 machines that have no browser, or that have a version of Internet Explorer prior to 4.0.
Important Windows 2000 installs updated versions of the com.ms.asp and com.ms.mtx packages in the Java\trustlib directory rather than into the Java Package Manager. If you run the IntegrationClasses.exe that was included in the Microsoft SDK for Java version 3.2 to install these packages into the Java Package Manager on a Windows 2000 machine, the older versions of these packages will override the newer versions installed in Java\trustlib. (The IntegrationClasses.exe in the version 4.0 SDK will not update a Windows 2000 system.)
To fix this, follow these steps to remove the com.ms.asp and com.ms.mtx packages from the Java Package Manager:
Warning Using the Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of the Registry Editor can be solved. Use the Registry Editor at your own risk.
For information on editing the registry, see the Changing Keys and Values Help topic in regedit.exe or the Add and Delete Information in the Registry and Edit Registry Data Help topics in regedt32.exe. Note that you should back up the registry before editing. You should also update your Emergency Repair Disk (ERD).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Global Namespace\Java Packages\com\ms
"Path"="C:\WINNT\JAVA\Packages\MHZ9VDRB.ZIP" "Signer"="C:\WINNT\JAVA\Packages\Data\W13XZL3Z.DAT" "Info"=hex:00,00,05,00,5f,0c,00,00,1a,00,00,00
"Path"="C:\WINNT\JAVA\Packages\HGZQ9UUOX.ZIP" "Signer"="C:\WINNT\JAVA\Packages\Data\Q24YAM4A.DAT" "Info"=hex:00,00,05,00,5f,0c,00,00,1a,00,00,00
The documents included here are reproduced by permission from the originating technology group at Microsoft. In many cases they are only a subgroup of the entire documentation for that technology. These documents were chosen because of their connection with Java.
Internet Information Server (IIS) is an Internet file and application server included with the Microsoft® Windows NT® Server operating system. IIS can be used alone as a Web server, or in conjunction with compatible technologies to set up Internet commerce, to access and manipulate data from a variety of data sources, and to build Web applications that take advantage of server script and component code to deliver client-server functionality. The Integrating Java with IIS documents show how IIS functionality is exposed to Java, concentrating on Active Server Pages (ASP). The section includes several white papers on ASP and reference information on the com.ms.iis.asp and com.ms.asp packages.
Microsoft Data Access Components (MDAC) enable Universal Data Access (UDA). UDA provides tool- and platform-independent access to information across the enterprise, including relational and non-relational. The Integrating Java with MDAC section focuses on the Microsoft® ActiveX® Data Objects (ADO) component of MDAC, and includes several white papers on ADO and reference information on the com.ms.wfc.data package.
Microsoft Transaction Server (MTS) is a component-based model and runtime environment that simplifies the task of developing application components by allowing you to perform work using transactions. The Integrating Java with MTS section includes several white papers, tutorials on building MTS applications and building MTS components in Java, and reference information on the com.ms.mtx package.
Microsoft Visual Studio is a complete suite of tools that meets both technical and business requirements for enterprise development. The Integrating Java with Visual Studio section focuses on Microsoft® Visual J++®. The documents provided include white papers on Microsoft® Visual Studio® extensibility and the use of Windows Foundation Classes for Java (WFC). Reference information on Visual J++ extensibility and the COM interfaces of the Visual J++ Code Model are also included.
In addition to describing Java's integration with Windows DNA, the integration documents include information on using Java with Microsoft® DirectX® media. DirectX media is a family of high-level APIs and multimedia controls that provide rich support for animation, streaming, and integration of the different media types. The Integrating Java with DirectX Media section provides reference information on Microsoft® DirectAnimation™, a DirectX media component that enables you to integrate different media types.