Solutions | J2EE to .NET 2.0 Migration
Since almost two years, there has been an active debate over the endurance of the two giant enterprise platforms, Microsoft‘s .NET and Sun‘s Java 2 Platform, Enterprise Edition (J2EE). Which technology would emerge as the leading platform for developing new web applications?

Now that the combat has settled down a bit, each platform has managed to capture a substantial share of market for itself. In fact, many organizations have arranged for a strategy for one or the other of these frameworks. But many (e.g. those which have large investments in the legacy systems) are still evaluating the merits of the two platforms. The IT personnel in those businesses is questioning as to what extent would choosing .NET or J2EE influence their host strategy, etc.
Read the rest of this entry »

• 0 Comments

DOT NET is one of the key products that enable application development under the new vision. However, DOT NET is not quite backward compatible with prior versions like visual basic version 6. This makes migration a serious issue. Converting existing source code to DOT NET architecture is not just a matter of loading it to the new version. DOT NET has its built-in migration tool, which performs the vital task of converting the source code syntax. But that’s just half of the work done. But before the converted code is actually compiled, the developer needs to enable it to smoothly fix lot of issues to fit into DOT NET architecture. In present efforts to find out solutions to these migration issues, a re-engineering Migration Model for Legacy Source Code (MMLC) has been proposed in this study. Proposed model has been further validated using a in-house project at one of the leading software development organisation. It is envisaged from the experimental try-out that the model would help the developer community to easily convert their legacy source code to DOT NET framework.
Read the rest of this entry »

• 0 Comments

Migrating to a new learning management system (LMS) has been likened to breaking into faculty classrooms, throwing their course materials into a moving van, and dumping them in a heap at the new location – leaving the faculty to sort and reorganize their course content long after IT support has driven off. This painful process can be averted by assessing faculty needs and expectations, and selecting a solution that supports seamless content migration and intuitive course management. That may be easier said than done. The $350 million market for LMSs is populated by more than 140 vendors whose mission is to support best practices in the preferred pedagogical approach of colleges and universities.
Read the rest of this entry »

• 0 Comments

Last month I was fortunate enough to be invited to a private roundtable of operator executives and entrepreneurs asked to share their ideas and opinions on the opportunities and challenges facing the mobile data industry. Now it’s a very rare day when these two constituencies can agree on anything, so imagine my surprise when both camps reached a consensus on the positive impacts that Web 2.0 services will have on non-voice revenues.
Read the rest of this entry »

• 0 Comments

This guide is intended for individuals who may be unfamiliar with Microsoft Outlook. The more advanced features of Outlook are not included. The guide begins by looking at different ways to view the Outlook screen. Other topics covered include: sending and receiving e-mail, contacts, calendars, saving and storing e-mail and using the Out of Office Assistant.
Read the rest of this entry »

• 0 Comments

JUDIE stands for Java Universal Database Import and Export. It was planned to allow users and developers to export data from one database to XML and import from this XML into another database. There are many use cases like data migration or setup of test databases. XML allows you to manipulate the data, maybe you already have XML export from legacy system and you can now transform this XML files (using XSLT) to JUDIE format. Also export from other tools (like db/Torque) can be easily transformed into JUDIE format and vice versa (see functional specification for more information about XML Schema/DTD).
Read the rest of this entry »

• 0 Comments

Migrating Atlas applications to ASP.NET AJAX sounds like a rather hard and messy task; all applications have to be changed. However, in most cases, not much effort is required for the migration. There are several reasons for this. First, the most important features of Atlas changed only marginally in ASP.NET AJAX. And second, the most convenient features already exist, not in the ASP.NET AJAX package itself but in the Atlas Control Toolkit, which is now called ASP.NET AJAX Control Toolkit.
Read the rest of this entry »

• 0 Comments

This document outlines the key steps that are required to migrate an existing Microsoft ASP.NET AJAX application created with the RC release to work with the final (RTM) release. This document is intended to be a quick reference. For more details, download the whitepaper Changes between the ASP.NET AJAX (“Atlas”) CTP and the RC and RTM Release from the http://ajax.asp.net Web site. Note This document assumes that you have an application created with the RC release. If you are migrating an application from the CTP release, see the document “Converting Applications from ‘Atlas’ CTP to ASP.NET AJAX RTM” on the http://ajax.asp.net Web site.
Read the rest of this entry »

• 0 Comments