For a Few Dollars Less - Migrating FlyBuys from MicroFocus to Fujitsu COBOL

Read on for a high level overview of the activities involved in this project, and how it ultimately turned out.

Attachments:

FlyBuys - For A Few Dollars Less.pdf

[ ]

346 Kb

Service-Oriented Architecture (SOA) is a widely used - and misused - phrase in IT, having evolved to have different meanings to different people.

For some it is no more than a re-branding of an architectural approach used for decades on large scale enterprise applications. Examples include CORBA Services in the 1990s, RMI from Java 1.1 onwards and DCOM.

For others, SOA is a new nirvana; a place where where corporate services are exposed via Web Services to be discovered and consumed by a multitude of clients (using any technology), the end-result being rich and productive new systems built from standard building blocks. To quote Wikipedia :

"SOAs build applications out of software services. Services are relatively large, intrinsically unassociated units of functionality, which have no calls to each other embedded in them."

Continuous Integration with CruiseControl is a standard part of the development process here at Shine Technologies. All new projects kick off with a new build server and a CruiseControl install that calls out to the standard Ant build files and jUnit tests. Continuous Integration is a well proven process that both gets a new project up and running quickly and provides long-term support and infrastructure - even for legacy Cobol systems.

We all know the theory of distributed computing: by dividing tasks among several computers rather than having all processes originating from one central computer, we can increase overall throughput. The problem is that in reality the actual implementation of such a scheme is often quite complex.

Recently I was asked to develop a mobile phone application for a customer using Java Micro Edition