Tooling

The core of Eranea’s technology is clearly its transcoder (NeaTranscoder) moving Cobol to Java 100% automatically and its runtime framework (NeaRuntime) providing all the functions needed to deliver exact same results “to very the last bit”.

But, at the same time, surrounding components and tools are also critical to the smooth and efficient execution of transformation projects at very large scale. It is not uncommon to transcode applications with a size over 10 millions lines of source code and up to several tenths of millions lines of source code.

To execute migrations efficiently at this scale, you clearly need a “transcoding factory” with a real-time dashboard allowing active supervisions of all activities taking place.

That is the role of NeaControlCenter, the web-based application supplied by Eranea to :

  • analyze and improve the legacy source code
  • monitor recurring application transcoding and dual Java / Cobol test replays
  • measure and manage the private cloud installed on new x86 systems while the migration is happening and also after project, when mainframe has been stopped

NeaControlCenter is rich of 200+ screens and functions tailored to the needs of various stakeholders in the project :

  • managers and project leaders who need summary reports on project progress : they want to see which parts of the applications have been tested, where they stand in their incremental rollout and if the new x86 server behaves properly from a performance and availability standpoint
  • developers who need to migrate their part of the application portfolio : they seek tools to spot (potential) defects in their legacy source code, to monitor the transcoding of this source code as well the good replay of the test scenarios that they captured to validate the new Java source code
  • system administrators and engineers as well as operations helpdesk who need to respect very stringent service level agreements and deliver high quality operations : they must be able to monitor hundreds of probes and values (user sessions, database activity, messaging, resource consumption, etc.) in the system to guarantee high quality to their end-users. Aslso, they have to make mure that continuous deployment of new application versions on numerous Linux instances is flawless.

NeaControlCenter is web-based so that it can be easily accessed from anywhere by anyone within the enterprise but also from home (through VPN) by engineers on duty at night when important batch jobs are run.

NeaControlCenter provides, for example, following functions :

  • monitoring of all jobs (Cobol transcoding, Java compilation, packaging, deployment, etc.) happening on the Continuous Integration (CI) engine at the heart of the transcoding factory
  • accessing all the reports generated by those jobs : cross-references JCLs/ programs / copybooks, list of warnings / errors on Cobol objects, recommendations to improve legacy source code, SQL statements details, API (CICS, etc.) statements details, file descriptors analysis, etc.
  • access to source code and all objects within the browser with ability to edit them through a web-based editor
  • services to examine the original capture of test scenarios on the legacy system as well as their replay on Java system to check if results remain identical run after run.
  • analysis tools to validate the quality of the tests according to the resulting code coverage in both Cobol and Java
  • functions to request for deployments of new versions  and monitoring of rollouts with reports status : which version is where, when it was deployed, etc. Possibility for “hot” replacement (no stop of Java application server) of new versions when application bugs are spotted.
  • centralized supervision of all instances of Java Application Servers, extremely important when tenths of them are being deployed. Many of their health variables appears on the dashboard in NeaControlCenter in order to be able to check at a glancethat operations are ok
  • services to centrally request and monitor execution of many batch programs who can be run on many various servers. Those services work in coordination with the batch scheduler in place (BMC Control/M, IBM TWS, CA Autosys, etc. ) to supply complementary functions : ad hoc submissions, job customization, etc.
  • services to visualize / edit files that must remain encoded in EBCDIC even when stored and used on Linux through Java during and after the migration.

So, core technology (NeaTranscoder + NeaRuntime) what enables the project. But, NeaControl is the mean to make it industrial, efficient and transparent.