Microsoft Java Virtual Machine Support
Updated: July 1, 2009
Recognizing the need to provide a smooth transition for current users of the Microsoft® Java Virtual Machine (MSJVM), Sun Microsystems and Microsoft have agreed to extend Microsoft's license to use Sun's Java source code and compatibility test suites. This extension allows Microsoft to support the MSJVM until December 31, 2007, providing customers with the ability to transition from the MSJVM on a schedule and plan that is most effective for them. That date subsequently was extended until June 30, 2009.
The MSJVM reached the end of its life as of June 30, 2009. Customers are encouraged to take proactive measures to stay informed about obsolete software and move away from the MSJVM in a timely fashion. The MSJVM is no longer available for distribution from Microsoft and there will be no enhancements to the MSJVM. Microsoft products and SKUs currently including the MSJVM have been retired or replaced by versions not containing the MSJVM.
Obsolete software, whether in the form of unsupported products, old service packs, or even expired certificates, is an issue every customer needs to be concerned with. Microsoft software life cycle communications help customers identify obsolete software in a proactive and ongoing fashion.
Customers are encouraged to stay informed about obsolete software and to transition from the MSJVM in a timely fashion. Guidance and tools are available to help customers make this transition.
* MSJVM Transition Guide–IT Pro Version. Technical guidance on transition planning and tools for identifying MSJVM site and application dependencies.
o Get the transition guide for IT pros (224 KB Portable Document file)
* MSJVM Transition Guide–Developer Version. Technical guidance on MSJVM decision-making approaches with related migration and transition options.
o Get the transition guide for developers (389 KB Portable Document file)
* Frequently Asked Questions (FAQ) . Get answers to such questions as which versions of Microsoft Windows® include the MSJVM, where to find the latest security updates, and what support options are available today.
* Microsoft Dependent Application List. Microsoft applications that have been tested for MSJVM dependencies.
o Review the application list (149 KB Portable Document file) Software
* MSJVM Diagnostic Tool . Assesses and reports MSJVM dependencies on one machine or across the enterprise. Only for customers who are interested in running a comprehensive MSJVM dependency analysis.
* Microsoft J# Browser Controls (JBC) . Recompiles applets to run on the Microsoft .NET Framework.
* Java Language Conversion Assistant (JLCA) . Converts Java applications to Microsoft Visual C#®.
* Daylight Saving Time changes in 2007. Changes to daylight saving time ("DST") and some time zones in 2007 affects all builds of the Microsoft JVM up to and including VM version 3812. Microsoft has worked cooperatively with Sun Microsystems to provide a hotfix to the MSJVM that will make it compatible with DST 2007 rules and updates as of October 18, 2007 applied to the operating system. MSJVM was shipped as part of a number of products that are currently in Extended Support. For those products, the MSJVM update for DST in 2007 is available through the Extended Support program. Premier Support customers should work with their local Microsoft account team to discuss options to obtain the hotfix. Non-Premier Support customers should go to http://support.microsoft.com/gp/lifean22
and follow the steps listed under “Option 2: DST Update” to obtain the hotfix.
* MSJVM newsgroup . Get quick assistance and see how other firms are managing this transition.
Transitioning Options: Alternative Java Technology Solutions
Although Microsoft cannot vouch for the security and reliability of Java Runtime Environment (JRE) solutions offered by other companies, customers deciding to pursue this option as they transition off the MSJVM are strongly encouraged to migrate to the Sun JVM versions that support their current operating systems or one of the other third-party Java Runtime Environments (JRE) solutions. Customers choosing to explore such solutions should engage in testing prior to pursuing this migration path.