Question

Imagine a C++ framework as a business layer, but with controlling logic as well. E.g. user rights, state of the webflow etc. With some plain C code to access DB2. The whole framework is host based. We are looking for a way to replace the existing framework gradually with a java framework. The main challenges are: the application is already huge, there are several application clients connected to the c++ framework at the same time (it's one web application with many instances), my knowledge of what is possible today with java on host is very limited (since all people I work with stick with C++)

Do some good ideas exist for gradually moving the old framework without breaking existing code? I guess as entry one would expect a web service or RMI server for transactions. But how to replace the business/controlling logic gradually is still a black box to me.

Answer 1

Honestly this sounds like technology for the sake of it. Its one of the main reasons why businesses mistrust their IT departments.

Look at at from the business point of view -- you want to do a ton of work, which will almost certainly introduce a new set of bugs, and, end up with a system that does the same as the current system but more slowly.

I wouldn't suggest you write a new system in C++ anywhere on any platform, and Java has superlative support on the mainframe (assuming you mean IBMs Zos) so it would be a good choice for a new system.

But if it ain't broke don't fix it.

If you really want to go ahead with this then you need to do:

Use Websphere application server (runs in USS so its mostly the same JAR files as any other websphere application server.) which will provide you with a ready made framework.

Avoid using the fancy EJB beans to access the DB2 data, stick with POJOs and plain SQL to access the existing DB2 tables. IBATIS is a good bet to ease the ORM coding.

Use the existing DB2 database as the main communication medium between the 'old' C++ and the new Java components.

Where you need more direct communication between the old and new applications use MQ if possible it's easy reliable and works anywhere, avoid JNI, RPC and CORBA as they will dump you in a world of pain.

Do not redevelop components piecemeal, choose a business function and refactor everything related to that function.