- Channel HP
- :
- Enterprise Business Blogs
- :
- Servers
- :
- Mission Critical Computing Blog
- Mark all as New
- Mark all as Read
- Float this item to the top
- Bookmark
- Subscribe to RSS Feed
- Invite a Friend
Transitioning Applications from HP 9000 to HP Integrity Servers
Since I often speak with customers in my role, I tend to run into some scenarios on a regular basis. As part of the worldwide team, I also get to spend time with people who understand certain areas of our business at great depth, and learn about offerings we have that can help our customers. This was the case the other day when I was speaking with Swaroop, a co-worker who works on compilers, Java, and transition tools.
We were speaking about a common scenario that we often come across - lots of HP 9000 PA-RISC servers functioning perfectly well at a customer site. The customer would like to get rid of the old servers and consolidate on something more efficient, but their code runs on PA-RISC and they don't want to upgrade or re-write their code to work on HP Integrity servers. I've known about the Aries translator, but Swaroop gave me an in-depth view of the "Over Easy" portfolio.
As I've heard for years, the Aries translator runs HP 9000 PA-RISC binaries on HP Integrity servers. It works well, but like any translation, it isn't as efficient are recompiling the code to a native mode, although the translator gets more efficient the longer that it runs. Naturally, if you take an old server, the performance per core of a new server is so much higher that even with the translator the performance might improve compared to the old environment.
The next tool is for Java environments. It is called HP Mixed Mode Translator (MITR). Essentially, this runs the HP Integrity Java Virtual Machine instead of the HP 9000 JVM. However, if the Integrity Java JVM calls a HP 9000 library, MITR automatically makes sure that the library runs under the Aries translator. This gives you the benefit of a native JVM (such as performance improvements), but still using the rest of your HP 9000 libraries.
Third, for developers, there is the HP XPADE - namely the HP 9000 Cross Development Environment for Integrity. This allows you to develop your HP 9000 code on newer HP Integrity servers. HP XPADE provides a self-contained and fully functional HP 9000 HP-UX C/C++ development environment on HP-UX 11i for HP Integrity servers.
Finally, if you are at the point that you want to move code from HP 9000 to HP Integrity servers, HP offers a number of HP Software Transition Kits. There is a Software Transition Kit from HP 9000 and HP-UX to HP HP-UX on Integrity. There are other software transition kits as well - Linux, Solaris, Tru64, and AIX. There are other tools as well. And naturally, HP is has a lot of upgrade, transition, and migration expertise, including Migration Competency Centers. If you need help, HP is happy to help provide it.
As I mentioned, I learned a lot about how to get HP 9000 code onto newer HP Integrity servers, which often reduces maintenance activities, support costs, power, cooling, and floor space costs, and more. Hopefully you find this information useful as well.
Jacob
