Switching to a graphical interface without losing the business logic written in COBOL

Question

We support a system containing over a million lines of COBOL code. Does anyone have any suggestions on how to switch to a graphical interface (possibly based on Windows) without losing all the business logic written in COBOL? And yes, some business logic is hidden inside the current user interface.

Answer 1

If it were me, I would look at something like this:

NetCobol for Windows

Simply wrap COBOL with an interface that provides functionality (if it is not already written in this way), and then call it from a .NET application.

15 , , - .

Answer 2

, , . ERP 3- . , , , , .

, , .

, , , , java .net -.

Answer 3

Microfocus Enterprise Server, COBOL -.

COBOL A, COBOL B A B , B -.

A , A B -.

, B -, ( , Windows, Java, ASP ..) .

, " ", , - ASP, - COBOL.

-, , COBOL .

Answer 4

ESB, , ESB.

. , - ESB.

-, , - , ESB.

As for choosing a platform for the new graphical interface, why not consider the web user interface and not the native Windows platform, at least updates for the user interface should only apply to the web server, and not to deploy the changes on each separate working station.