Evolution & Migration
Strategies for MPE
Let us help you to re-engineer your HPe3000 MPE applications
to the platform-neutral J2EE environment.
The end of support for e3000 hardware and the associated MPE operating system has arrived.
A strategy is required for HPe3000 sites needing to evolve or migrate either to non-HPe3000 or to a hybrid system where the HPe3000 remains, in the short to medium term, as the database server.....
What are the Migration Possibilties
  • Stay on the HPe3000

  • Follow HP's recommended migation route to HP-UX
  • Convert to 3rd party applications

  • Rewrite the applications

  • Evolve and migrate the applications using migration tools

  • Evolve, migrate, and re-engineer the applications using platform-neutral internet centric migration and re-engineering tools, programming languages, application servers, and design methods.
This option has only short-term viablity

These options potentially carry the highest long term costs since they involve moving from one proprietary solution to another. Also some previous investments may be compromised.

This caries the highest short-term cost and is high risk. Long-term benefits are high if care is taken to follow platform-neutral strategies, like Java, J2EE, and LAMP.

This option potentially carries a high long term cost since it involves moving from one proprietary solution to another, unless platform neutral design strategies are factored in.

This last option offers the most flexibility with high long term benefits and excellent investment protection. There will be an initial learning curve cost but long term financial benefits and savings will mitigate these costs.
Development and Evolution Approaches

For new development and for evolving legacy systems, employing a web centric 2-tier or n-tier component software design approach has a number of benefits over the traditional monolithic software and systems design methodologies.

But component software is only part of the design equation. Of equal importance is ensuring that investment is not compromised by following a proprietary route - platform-neutrality is the key word to watch.

On the basis of these criteria, a server-side JAVA, J2EE and Open Source centric approach is favoured, supported by platform-neutral open source or vendor centirc development tools and execution infrastructure

  • Open Platform & Open Source Centric
    (JAVA, J2EE, Linux, Eclipse, MySQL, MAXdB, LAMP)

  • Vendor Centric - platform neutral
    (IBM Websphere, DB2, Linux, Oracle)

  • Microsoft Centric - proprietary
    ( IIS, NT/2000, SQL Server, .NET)

  • Vendor Centric - proprietary
    generally platform-specific
    • Macromedia Cold Fusion
    • Cognos Powerhouse
    • Speedware
    • Others
Which DBMS to use

DB2 Universal Database is a powerful, feature-rich, enterprise scalable distributed RDBMS from IBM that is available in several versions and with a range of sophisticated features. It runs on all mainsteam OS's including NT/2000, HP-UX, and LINUX. Recent additions include comprehesive support for XML documents. The DB2 GUI administration console is a particularly powerful and intuitive management environment making it an attractive option for migrating Turboimage DB's
DB2 Express is free to download and use.

SqlServer from Microsoft is proprietary to the Microsoft platform and does not scale well to enterprise distributed environments. There is no support for J2EE standard middleware.

Oracle will easily meet the needs of existing TurboImage applications but is more complex and costly to manage and maintain than DB2. There are repots of a 1:6 perfromance drop going from MPE/IMAGE to HP-UX/Oracle. Oracle now ships with a J2EE application server licensed from Ironflare, the authors of the Orion Application Server. Until recently there was support for the Oracle RDBMS on MPE via the Oracle Bridge. The alternative now is to use the ANSI MPE/iX Enterprise Client

  Eloquence (with Turboimage migration features) is an attractive option to small to medium sized applications. Because it is very close to TurboImage, it will allow legacy code to run with little change for the short term, and offers an easy migration path from IMAGE. Among it's many attractive features is the solution to migrating secondaries. In a commissioned study, almost identical database performance was achieved comparing TurboIMAGE on MPE and HP Eloquence on HP-UX.

Open Source Options

MySQL - Not only is MySQL the world's most popular open source database, it's also become the database of choice for a new generation of applications built on the LAMP stack (Linux, Apache, MySQL, PHP / Perl / Python.) MySQL runs on more than 20 platforms including Linux, Windows, OS/X, HP-UX, AIX, Netware, giving you the kind of flexibility that puts you in control.

MaxDB is a heavy-duty, SAP-certified open source database for OLTP and OLAP usage which offers high reliability, availability, scalability and a very comprehensive feature set. It is targetted for large mySAP Business Suite environments and other applications that require maximum enterprise-level database functionality and complements the MySQL database server.
We believe Linux is now the optimum choice of open-source platform, IBM Websphere and DB2 the optimum choice of scalable enterprise middleware and DBMS, Java the optimum choice of platform-neutral development language, and Eclipse the optimum choice of open source defacto development environment.
Contact us for further information
Copyright 1997-2006 The InterNet Agency.    All rights reserved.
We welcome your comments to the Webmaster