C2J-Kics

The architecture of C2J-Kics is centered around three primary components: the Converter, the Runtime Environment, and the Configuration Manager. The Converter is responsible for parsing COBOL source code and generating equivalent Java code. It handles the translation of COBOL data types, CICS commands, and business logic.

The Runtime Environment provides the execution environment for the migrated Java applications. It includes components for transaction management, data access, and interaction with external systems. The Configuration Manager allows administrators to define data mappings, transaction definitions, and other parameters that control the behavior of the migrated applications.

Communication between these components is primarily internal, with the Converter generating code that interacts with the Runtime Environment. The Configuration Manager provides settings that are used by both the Converter and the Runtime Environment. The system uses file-based storage for configuration files and log files.

The product supports REST APIs for integration. Authentication is handled through user ID and password. The product supports RBAC with role-based permissions.

The network requirements include access to the z/OS system where C2J-Kics is installed, as well as access to any external systems that the migrated applications interact with. The Converter uses XML configuration files for data mapping and transaction definitions. The Runtime Environment provides the necessary infrastructure for executing the migrated applications.

The Configuration Manager handles the settings for data mapping, transaction definitions, and other parameters.