FAQFrequently Asked Questions

About Our ServicesBack to top

QWhat services can Transware provide?

A

Please see the description pages for each service below.
[Transware Services],[Mainframe Support Status List],[Midrange Support Status List]

QWhat is the approximate cost of migration?

A

Costs vary widely depending on the size and complexity of the project. Estimated costs can be calculated by filling out the survey sheet.

QAt what point do you know exactly what tasks must be accomplished and their costs? Is that information available before the project begins? Is some analysis required before the contract is signed?

A

The survey sheet you complete as a prerequisite to your estimate reflects items that may determine the complexity of your conversion. Before beginning a project, we will evaluate and estimate the complexity of each project, i.e., the resources involved, the time required, and the cost.
This estimate is based on a number of migration projects that have already been successfully completed. These projects cover a great variety of sizes, architectures, and specific legacy technologies.
We can also provide estimates for each phase of the project (PoC, analysis and planning, program conversion, and data conversion).

QIs there a downloadable trial version of the tools used for conversion?

A

Caravel? is a migration and conversion service, and there is no trial version of the tool alone.
If testing is required to determine the feasibility of migration, we recommend that a Proof of Concept (PoC) be conducted using some of the existing system assets.
The general flow of a PoC is as follows.
　　-　A fully functional subset of your system (program and data) is carried out (provided to us). (a separate non-disclosure agreement is required)
　　-　We check and analyze the resources (programs) received from the customer, and confirm the analysis results with the customer.
　　-　We convert the resources (programs and data) received from the client into a form that will work in the new environment. We then deploy them to the client's environment after confirming that they are running on our machines.
　　-　After deploying to the customer's environment, we ask the customer to check the operation.
We recommend that you select some of the more important systems for the PoC.

QCan I purchase a license for Caravel™ as a conversion tool?　

A

Caravel™ is a migration and conversion service and does not sell conversion tools to third parties.

QAre there any additional licensing requirements after migration? Also, does the system need to use any special tools after Java conversion?

A

After the conversion process, your assets are your assets. Migrated programs are 100% Java, so no special tools are required. Our migration services offer you complete independence. No license fees of any kind will be incurred after conversion.
Detailed information about each cost will be provided during the proposal phase.
For Caravel™ Express conversions, maintenance updates and maintenance services for the Caravel™ Framework can be optionally contracted; for Caravel™ Converter, a customer-specified version of an open, major framework is used. version of the major open framework, so maintenance is dependent on the respective open system. In both cases, defect handling is included in the conversion cost for the first year after the conversion project.

QDo you provide support for each phase of the migration (analysis, conversion, testing, and post-operational maintenance)?

A

The analysis, conversion, and testing processes include technical support from our engineers. You can enter into a separate contract to receive support from our engineers for issues outside the scope of our standard services (such as when individual tool development is required at the migration destination), testing, and maintenance after going live.

QHow much modernization is possible?

A

Modernization” includes optimizing existing legacy systems to the latest technology and trending industry standards, as well as adapting component structures to meet future change needs.
As for adapting the UI to the latest technologies and trends, we can provide web browser support for screens (to match the existing CLI or a web-compliant GUI), PDF for terminal printouts, and display and print via a browser as a standard feature.
Regarding data access, we can convert hierarchical DB, network DB, relational DB, VSAM, ISAM, etc. to SQL-based relational DB. We can also implement DAO according to the latest technologies and trends.
Caravel™ Insight provides a function to identify duplicate code in the system, which allows us to consider the commonization of important business logic.
In our conversion service, UI, data access, and business logic are separated into three layers for conversion, but the business logic is dependent on the customer's business content, so the functionality is converted as it is today.
For future DX promotion, we are converting to a structure that is easy to maintain and to a Java language that is easy to attract engineers.

Environment of the targetBack to top

QIs it possible to maintain the current mainframe*1 or AS/400*2 as a database server and application server? *1: Mainframe includes IBM (z/OS), Fujitsu (MSP), Hitachi (VOS3), NEC (ACOS4), etc. 2： AS/400 includes S/36, S/38, iSeries, and System i.

A

Mainframes and AS/400s can be used as database servers and application servers.
If you want to use your current machine as a database server, you can access it as a client using the JDBC driver from Java running in the new Linux or Windows environment.
There are several ways to use a mainframe or AS/400 as an application server running Java. One is to run an AP server that can run Java directly under an existing OS, another is to run the JVM under the Linux service of an existing OS, and another is to build a Linux environment by adding a logical partition to an existing machine. If you choose these options, you do not need to add a new machine (depending on the load status of the current machine).

QIs it possible to migrate only a part of the information system? Can it coexist with newly converted Java programs?

A

It is possible to migrate only a part of the system. In this case, it is absorbed by Caravel™ technology and can coexist with Java programs.
In such cases, the DB is usually left on the original platform, and the original DB is accessed from Java on the new platform.
We have experience with DB2 on IBM z series and DB (PF, LF) on IBM i series.

QWhat will be the machine environment at the destination?

A

The migration destination requires a machine capable of running Java, including Linux servers (often RHEL-based), Windows servers, Linux servers that are logically partitioned from existing hosts, and Amazon, Google, and Microsoft cloud environments. Both on-premise and cloud environments are acceptable.
Batch job systems run the framework and Java applications on the JVM.
Terminal processing (online and time-sharing) is accessible via a web browser (Microsoft Edge, Google Chrome, Apple Safari, browser embedded devices, etc.) and runs the Java application on a Java application server (WAS Liberty, Tomcat, etc.) Java applications are executed on a Java application server (WAS Liberty, Tomcat, etc.).

QHow do I make it a 3-layer application when migrating/converting with Caravel™?

A

Applications converted with Caravel™ separate the user interface components from the application behavior. It also separates data access for the application.
The resulting 3-tier application can be very easily customized by creating or modifying user interface screens.
Some program logic can be immediately converted to Java Web services (SOAP or REST).
The database server you access allows you to change the data access components without modifying your application.
Java applications created with the Caravel™ conversion service can be deployed on a Java application server. The converted program meets the requirements of a “3-tier architecture” according to the rules of Jakarta EE (J2EE). The new client tier consists of a set of client Java components (Java JSPs provided by the Caravel™ conversion process, TypeScript (JavaScript), and client components such as HTML and CSS (style sheets) for screens). The converted Java classes become part of the business logic layer. Finally, the data layer corresponds to the server and data, and possible stored procedures. It is also possible to use DAOs corresponding to the data layer. As for the DB, in addition to using the SQL-based DB server in the new environment, it is also possible to use the original mainframe or AS/400 DB in combination.

QDo I need a special application server to run the converted application?

A

The batch job system runs the framework and Java application on the JVM (Java Virtual Machine).
The processing of terminal systems does not depend on a specific application server. At this time, converted applications are compatible with the latest versions of the most common application servers, for example
- WebSphere (WAS Liberty)
- Tomcat
- Apache/TomEE
- WebLogic
- JBoss, etc.
Application servers can be run as standalone servers, linked with front-end web servers, or load-balanced with load balancers.

QWill Caravel™ migrate system security and original platform user and device IDs?

A

Security aspects are not included in the migration. When an application is migrated to a new environment, it is necessary to run a security management application for that platform (e.g., operating system or database management system).
For online-based applications, there are many cases where terminal IDs and user IDs/passwords are used for processing within the business system. In such cases, it is possible to provide a mechanism to use terminal IDs (LU names) and user IDs/passwords for processing under the new Web browser environment that is tailored to the current situation and to the new environment.

QWhich web browsers are supported?

A

Standard support for Microsoft Edge, Google Chrome, Mozilla Firefox, and Apple Safari. We also have experience in providing custom support for browsers built into dedicated terminals and embedded devices.

Advance preparationBack to top

QWhat is required to convert an existing application system to Java?

A

The system must function properly on the current platform.
As sources for job execution, source code for JCL, Catalog Procedures, CLIST, and CL.
As high-level languages, COBOL, PL/I, and RPG source code, and the COPY, INCLUDE, and MACRO source code they use.
*If the COBOL source code was developed using a COBOL source generator, the source code after running the generator.
As for 4th generation languages (4GL), source code for Easytrieve, Natural, COBOL/S, and IDL II, and correct file layout information omitted in 4GL.
*For 4GLs other than the above, we can consider supporting them based on marketability and scale.
As for machine language equivalents, only MVS-based Assembler is supported; Assembler source code and MACRO source code.
As resource definition information (correspondence table between programs and transactions) for online systems, source codes such as IMS STAGE1 and CSD (PPT and PCT).
Source codes for MFS, BMS, PSAM, MED, MFD, PSAM, etc. as screen definitions (*including for printing terminals).
For report definition overlays, source code such as OGL, PSAM, etc.
As for DB layout information, source codes of DDL information related to DB such as DB2 DDL, DBD, PSB, CICS CSD (FCT), PED, AS/400 PF and LF information, and source codes of mapping information between DB and programs.
For flat files, the file layout should be clear (i.e., fields are not omitted in programs or COPY clauses). If a field is omitted in a program or COPY clause, the file layout must be provided separately.
*We can also discuss sources other than those listed above. Caravel™ Insight and Converter are tools with expandable functions, and may be able to be incorporated into the development roadmap after considering marketability and scale.

QWhat do I need to do to make sure it works in the new environment?

A

In most cases, we use both our in-house test machines (Windows server, Linux server, IBM i series (AS/400), and IBM z series (z/OS)) and the client's in-house test machines for operation checks and verification of the conversion target environment.
On our in-house test machines, we use a small amount of test data to verify operation based on test scenarios created by the client.
For this reason, we request that you provide us with a small amount of test data acquired in cross sections before and after the execution of the process, as well as a test scenario for us. The data you provide will be used for operational testing and to establish procedures for converting and importing the data into the new environment.
After deploying the program and data resulting from the conversion (with support from our engineers) on the client's in-house test machine, we ask that the client perform an operation verification using various types of data.
Operation verification requires appropriate test data and test scenarios based on that data.
For conversion of test data, we provide data conversion services.

QWhat content (missing sources, conversion issues, etc.) will be provided once the various sources have been imported into Caravel™ Insight?

A

Once Caravel™ Insight is performed, the results of the analysis can be viewed in the Discovery Viewer, allowing each object (each source) to be viewed from different perspectives.
*Discovery Viewer will not be provided to customers in the PoC, but will be provided to customers in this conversion project.
- Unresolved objects: List of unresolved objects such as missing necessary sources, OS-provided utilities and programs → For additional import of necessary sources and consideration of alternatives for functions that do not exist in the new environment
- List of quality information for each source (reports on complexity, dead code, conversion issues) → for migration planning and alternatives
- Check dependencies among objects (dependencies among programs, files, DBs, screens, jobs, etc. starting from each object) by object or network diagram
- Duplicated code in multiple sources → Consideration of common parts
- For COBOL, PL/I, and RPG, flowcharts and Java pseudo code can also be displayed → Reference for componentization without conversion services

Migration planning using Discovery Viewer
The following reports can be generated by using Discovery Viewer to define specific objects to be grouped (e.g., by subsystem, etc.) and perform function and wave analysis using these multiple groups.
- Clearly identified list of common objects among groups → Use for planning migration schedules
- Confirmation of the size of each group → Utilized for planning migration schedules

Conversion processBack to top

QWhat percentage of the original program can be converted to Java?

A

Caravel™ Converter converts 100% of the source code.
The conversion process reaches 100% through a series of automatic conversions by the tool and the setting of additional conversion specifications (parameters) to the conversion tool based on the results of those conversions.
For high-level languages (COBOL, PL/I, RPG), the conversion rate is often around 98% for the first conversion, reaching 100% with additional parameters.
In the case of 4GL, because there is a lot of omitted (undocumented) information in each language, in most cases, the conversion rate is about 50% on the first conversion, and reaches 100% with additional parameters.
In the case of Assembler, since there are many OS-dependent codes that cannot be realized in high-level languages, in many cases, the conversion rate is about 50% on the first conversion, and even with additional parameters, 100% is not reached in many cases. In this case, if an alternative solution is clear, the technician completes the conversion manually. If no alternative solution can be found, we may discuss the conversion with the customer.
Job processing control languages (JCL, catalog procedures, CLIST, CL) often have a conversion rate of about 98% on the first conversion, reaching 100% with additional parameters.
In the case of screen and ledger sources (MFS, BMS, PSAM, OGL, etc.), the tool is modified and parameters are added until the conversion reaches 100%.
Some OS utility functions (SORT, IDCAMS, IEFBR14, CPYF, OVRDBF, OVRPRTF, WRKSBMJOB, etc.) will be provided with Java classes corresponding to those functions as standard.
The Caravel™ Converter service provides 100% pure Java applications that run with the same functionality as the source application.

QWhat versions of RPG and COBOL on IBM i Series AS/400 (OS/400) are supported?

A

RPG Language: All versions (RPG II, RPG III, RPG/400, and ILE RPG)
COBOL language: COBOL/400
Embedded SQL is supported in both RPG and COBOL.
Conversion of Cycle RPG programs can be kept very effective in its behavior because the Caravel™ framework implements all the features of Cycle programs using Java classes and methods.

QWhich COBOL and PL/I versions can be converted for the IBM Mainframe z-series environment?

A

COBOL languages: ANSI COBOL 85-level, OS/VS COBOL and VS COBOL II, COBOL MVS, COBOL 390, Enterprise COBOL, etc.
PL/I languages: OS PL/I, PL/I MVS, Enterprise PL/I, etc.
The following preprocessors are supported for both COBOL and PL/I
- CICS preprocessor (EXEC CICS level source code support)
- DB2 preprocessor (EXEC SQL level source code support)

QIs the program converted separately? That is, is each instruction in the original source converted to a Java instruction?

A

Converts each source instruction into a method that retains the same functionality as the original. The conversion is done instruction by instruction.
In some cases, multiple lines of instructions may become a single method, and in other cases, a single instruction may become multiple instructions.
One purpose of the conversion is to make the source readable for the current technical team, which includes existing comment lines on the Java source.
On the other hand, for the Java programmer, the system is a 100% pure Java system and can be handled as normal.
Functions of the converted system can also be invoked via the REST service mechanism.

QOnce the program is converted, what development environment is it compatible with?

A

The converted programs are 100% pure Java code, so any standard development environment can be used. Our clients also work well with Eclipse, NetBeans, JBuilder, etc.

QAre various OS utilities and OS commands (JCL, CLIST, CL) implemented?

A

On the IBM z series mainframes, SORT, IEFBR14, IDCAMS, IEBCOPY, and IEBGENER are implemented.
On the IBM i series AS/400 (OS/400), CPYF, CRTPFM, ADDLIBLE, MONMSG, OVRDBF, OVRPRT, OVRDSPF, WRKSBMJOB, and WRKSPLF are implemented.
If your Caravel™ conversion service requires a functionality that does not exist, please contact us for further development and inclusion in the framework.

QWhat do I get after migration with Caravel™ Converter?

A

Provides Java applications that run on the destination platform and environment with the same functionality as the source system.
*Functions for hardware dependencies, communication control, and UI control (screen and form printing) will be tailored to the destination environment.
- Java source classes and object classes for conversion results
- XML files and DAO classes generated from the conversion of data definition file structures
- A set of user interface components (JSP, CSS, HTML, TypeScript (JavaScript), etc.)
- A set of standard Java libraries (jar files) used by the application and core class libraries (jar files) to support individual environments
- Database migration copy backup (for data migration)
In addition to the above, we also provide Javadoc and other related documentation and training in the Java programming environment using the Caravel™ framework.

QDoes converting a program to Java speed up the performance of the application? Will it slow it down?

A

Mainframes and i-series midrange are extremely reliable, high-performance platforms. Therefore, maintaining the same performance levels on the servers (Linux or Windows IA servers) where the newly converted systems will be installed requires a combination of technology and know-how.
For more than a decade, manufacturers' technical teams have analyzed the characteristics of many applications in terms of reliability and performance. Modern open systems offer the same level of reliability as legacy systems, but performance is always an issue to consider.
The rapid evolution of open system platforms has improved performance, especially when considered in relation to cost. This fact, coupled with the rapid evolution of Caravel™ technology, is closing the performance gap seen a few years ago. In addition, reengineering can be done to improve performance, and Caravel™ technology has developed a number of strategies that can significantly improve performance.
However, depending on actual hardware specifications and network speeds, current performance may not be guaranteed.

Screen ConversionBack to top

QIs the screen user interface automatically converted by Caravel™ or does it need to be set up manually?

A

Customizing a screen user interface is done as follows:
When converting an application, you can choose to either generate the user interface automatically according to the user's wishes, or customize a single screen.

In the first case, the appearance of the screen is based on certain transformation rules provided by Caravel™ that allow generating equivalent HTML code for each field of the screen. The result will be HTML code that generates the same fields, sizes, and positions as the original. Color attributes that do not affect functionality, source, background color, etc. can be customized and applied automatically to all generated screens.

In the latter case, you can create a JSP template for each screen you want to customize. This template can be any screen, it does not have to be the same as the original. To facilitate the preparation of screens, Caravel™ provides standard JSP mechanisms and uses a "JSP TagLib" that facilitates the use of information from the application (records, subfiles, fields, attributes).

Caravel™ also provides JavaScript functions to manage these fields and send information back to the application (e.g. function keys). This solution gives all the flexibility to achieve the exact look the designer desires.

These two solutions are not interchangeable. It is possible to customize only some screens of an application. This process can be done incrementally or according to the customer's needs. The application first searches for customized screens, and if it does not find them, it dynamically creates them according to the selected user interface parameters.

The customization process can be performed by the customer or integrated as part of the project. In the last case, the customer can define the desired rules, standards and styles. Since the look of the application is defined by a set of JSP templates, any graphical element can be changed at any time.

QCan I convert a screen into multiple languages? Can I convert a Japanese screen into multiple languages (e.g., Japanese and English)?

A

If the original is not multilingual, it can be configured to extract language-specific literals during the conversion process and export them to an external file. By editing and translating that file, the application can be converted to be multilingual.

QIs it possible to change the HTML format to something like radio buttons or pull-downs? If possible, how would this be described in the screen definition file? We would like to change some frequently used features.

A

The converted application has the logic separated from the interface structure.
Therefore, it is possible to customize the interface without affecting the converted program. Thus, it is possible to include graphic standard components such as buttons, radio buttons, pull-downs, etc.
The converted program uses JSP or TypeScript to manage data exchange with the user. This JSP or TypeScript is responsible for representing information to the user.
Screens can be customized in groups or one at a time. You can either use shared components used by a group of screens or individual components (JSP or TypeScript + HTML + CSS) for each screen.
During conversion, CSS (style sheets) are generated by default for all screens and can be changed at any time.
In addition, the Caravel™ architecture allows converted applications to be used in a REST service architecture. In this case, HTML + CSS + (JavaScript or Angular TypeScript) can be used by the REST service to the converted application.

QIn relation to the above question, are there any features that are not available? Also, I would like to know about restrictions on developing new screens with the same architecture.

A

There are no major restrictions on screen customization.
It relates to how the program uses the screen data.
Specifically, the converted program may need to take into account the cursor position or function keys already pressed, and the customization must take this behavior into account and respect it.
Caravel™ conversion provides default implementations to manage these situations.
In addition, the navigation logic between screens must be taken into account. This behavior may affect the flexibility of screen customization.

QDue to the huge number of columns, the screen is currently divided into multiple screens. However, in the future we would like to integrate them into one screen. Therefore, are there any restrictions on displaying screens larger than 24 x 80 or on rows and columns?

A

It is possible to merge multiple screens into one screen and change the screen size.

There are different levels of screen customization. They range from low-impact customizations (e.g., CSS changes only) to high-impact customizations that require logic changes.

In either case, the logic may need to be changed to ensure that the functionality of the application is maintained. (e.g., logic changes related to the number of items displayed on a screen, or changes to accommodate changes in screen layout).

QIs JavaScript available? If so, how would you define it in the screen definition file? We would like to add new functionality, e.g., check values when TAB is shifted. We would also like to develop a new screen with the same architecture, using a screen component with JavaScript such as jQuery.

A

JavaScript is available.
It is possible to use a framework like JavaScript or jQuery; this is possible even if you are using JSP, if your application uses HTML + JavaScript, or if you are using Angular.
The standard implementation of Caravel™ offers the choice of JSP, HTML + JavaScript, or HTML + Angular + TypeScript, depending on your requirements.

QHow is CSS defined?
How to define CSS files and the class attributes of each tag. In the future, when we develop new screens, we would like to integrate CSS design.

A

CSS can be used in a 100% standard way. All JSPs or HTML can include the desired CSS.
In the standard implementation of Caravel screens, CSS is included by default.

Terminal printBack to top

QCan the mechanism for printing to the printer terminal be converted?

A

In many cases, terminal printing is done by sending print data via a TP monitor (CICS, IMS DC, etc.) to a printing terminal tied to the currently used screen terminal.
Since the Web application server to be migrated does not have such a function, an alternative solution must be constructed.
Examples of alternative measures include the following responses.
　　-　Output print data from the application to the directory for the current print terminal ID (e.g., print image text or print image PDF).
　　-　Provide a function to display a list of files in the directory for the printing terminal ID corresponding to the screen terminal as a web function for terminal printing.
　　-　Select file display or deletion from the file list as a web function for terminal printing.
　　-　Print the displayed print data to a printer using Windows PC functions.

Conversion of printing functionsBack to top

QHow are advanced printing features implemented? Can form overlays be converted?

A

Caravel™ has implemented several Java-compatible extensions for print files (PRTF) that support most features of the AFP/400, AFP for z/OS, and PSF for z/OS modules (image printing, text, templates, bar codes, etc.).
Regarding the use of form overlays such as OGL, there are some that have been implemented and some that have not yet been implemented at this time. For those that are not yet implemented, please contact us for a new implementation.

QHow will the application behave when printing large quantities of paper? Will a printing mechanism be provided?

A

Migrated applications will output form data to a print queue, and a new system of print tasks will be considered for implementation when printing on printing devices in the migrated environment.
This new print task can include functionality to enable the use of electronic documents in a variety of formats, thus facilitating a paperless environment. Please contact us for more information about our multiple development projects.

If you wish to continue to use the printing devices connected to your existing machine environment as before, the migrated application can create print files with the same file layout and character codes as before. In this case, it is also possible to transfer files created at the migrated site to the existing machine and print them as before.。

Database conversionBack to top

QCan Caravel™ migrate existing data to any RDB? Or is there some limitation in the support of the destination RDB?

A

Caravel™ can migrate to any RDB that supports the most commonly used SQL on the market. Examples include DB2, Oracle, PostgreSQL, and Microsoft SQL Server. In all cases, a JDBC driver is required.

QHow is the DBMS and files implemented?

A

Not only RDBs, but also hierarchical DBs, network DBs, relational DBs, VSAMs, and ISAMs are converted to and implemented in RDBs that support SQL.
The recommended character encoding of the RDB to be migrated is UTF-8 for Linux systems and SJIS for Windows systems.

Sequential files will be implemented as Linux or Windows TEXT files or data files (binary data is also acceptable).
When converting existing EBCDIC + shift-coded Kanji code files to UTF-8 or SJIS-based files, it is essential to deal with the change in data length.
Since numerical data may be stored in PACK decimal or binary in the source system, care must be taken in data conversion.
For sequential files, although the field data length will be expanded at the migration destination, the conversion rules based on a fixed-length file layout should be determined and implemented.

java TechnologyBack to top

QWhat are Java classes?

A

A class in an object-oriented language is a program that implements functionality associated with a particular type of object. A class consists of methods and properties.

QWhat are Java methods?

A

Methods in object-oriented languages are a type of object class functionality.

QWhat JVM versions does Caravel™ support?

A

Caravel™ supports Java 8 or later JVM versions.

QWhat versions of Servlets and JSPs does Caravel™ support?

A

Caravel™ supports Servlet 2.3 or later and JSP 1.1 or later specifications.

QWhat is the Jakarta EE (J2EE) standard?

A

Jakarta EE, J2EE (Java 2 Platform Enterprise Edition) defines a standard for developing component-based multi-tier enterprise applications. optimal configuration for developing and deploying scalable applications for the Web. tools to create them. These tools have the following features
- Compatibility on different platforms

Simply create your application on Windows or Linux and it will be available on all platforms with a Java Virtual Machine (JVM).

- Scalability

As your business grows, you can simply add new J2EE components to your web application to support that growth. There is no need to rewrite code.

- Extensive Support

Many large software companies, including IBM (WebSphere Application Server Liberty, commonly known as WAS Liberty), Oracle (WebLogic Server), Apache (Tomcat, Apache TomEE), and Adobe (JRun), offer web component containers (or application servers) that are compatible with Jakarta EE (J2EE).

- Improved Security

While other business application models require specific security measures for each application, the Jakarta EE (J2EE) platform security environment allows security restrictions to be defined at application deployment time. This isolates the complexity of the security implementation and provides portable security.

QIs it possible to deploy the converted system on an application server, specifically WAS Liberty?

A

Caravel™ converts to Java following the guidelines of the standard J2EE architecture. The converted system can therefore be deployed on any application server that conforms to this standard.
IBM (WebSphere Application Server Liberty, also known as WAS Liberty), Oracle (WebLogic Server), Apache (Tomcat, Apache TomEE), etc., can deploy the converted application without modification.

QWhat changes to hardware and software are required to use the Swing application?

A

To use a Java application with a Swing interface, a client PC with a Java Virtual Machine (JVM) is required. The application must be accessible from this client PC. Data can reside on this server, on OS/400, on a mainframe, or on any other server.
Caravel™'s standard conversion is to a Web application, but conversion to a Swing application is available upon request.

QWhat changes are required to use the web application?

A

You will need a server with Internet/Intranet access that contains a Java Application Server. The server can be any server that meets the Jakarta EE (J2EE) standard, such as WAS Liberty. The client PC must have an Internet browser; Microsoft Edge, Google Chrome, Firefox, etc. are supported.

QCan I integrate other Java applications once the migration is complete?

A

The converted system is 100% Java application standards compliant and can be integrated.

Post-transition maintenanceBack to top

QDo I need special training on the methods and classes developed by Caravel™ Converter?

A

The classes used by Caravel™ are clearly structured in 100% pure Java and require no other special Java knowledge. The classes are easily understood by programmers with extensive COBOL or RPG experience.

All conversion projects include training sections for both COBOL/RPG and Java technicians.

QAre there any other tools needed to further customize the application, other than the customizations provided in the Caravel™ migration?

A

After conversion, program assets need to maintain sources such as Java, JSP, JavaScript (TypeScript), HTML, CSS, XML, etc. Using an IDE (Integrated Development Environment) such as Eclipse (Eclipse), source code editing, compilation, IDEs, such as Eclipse, provide a single environment for editing, compiling, debugging, testing, and packaging source code (plug-ins are available for each type of source). The use of such an IDE not only contributes to increased productivity, but also allows for development by multiple people within a project by utilizing version control plug-ins, and data can be checked by using DB-related plug-ins.
Eclipse is the most widely used IDE, but customers who have traditionally used NetBeans or JBuilder may continue to use them. When I want to easily check or change the source code, I sometimes use a text editor or MS Visual Studio Code (VS Code). For detailed debugging of the web front-end, I sometimes use the developer tools of Chrome or Edge.

QWe need to maintain a SQL-based DB that has been migrated with Converter. What are some examples of post-conversion processes for these various object types? For example, adding new fields (columns: columns) to the DB.

A

In the case of SQL-based DBs migrated with Converter, the conversion is based on the specifications of the DAO (MyBatis, Hibernate, etc.) used for the conversion. In this case, in addition to the expansion to database tables and database indexes, the conversion is performed in a form that includes supplementary information that cannot be expressed in the database definition alone in the DAO's Java source. Table columns (columns) will be most appropriate for the original data type. (This process varies from database server to database server.)
In addition, if the conversion source is a non-SQL-based DB (e.g., IMS DB or VSAM), columns to guarantee unique keys and relationships between tables are automatically added, which are also reflected in the program conversion and data conversion. In addition, AS/400 data files can define other attributes (packed / zone / binary numeric format, decimal places, format, default values, edit masks, etc.). Logical files can define SELECT / OMIT conditions, for example. Since most of this information does not correspond to standard SQL attributes, it is described in the DAO as complementary information and data access is performed.
Therefore, if the converted database table is modified, the following operations must be performed
　　1. Execute the corresponding ALTER TABLE instruction to change the database table structure.
　　2. Modify the corresponding DAO class (Java source). (e.g., declare new field variables and write access patterns)
　　3. Modify the programs that use the new fields accordingly. (e.g., describe the process using the new field variables)

QWe need to maintain a SQL-based DB that was migrated with Express. What are some examples of post-conversion processes for these various object types? For example, adding new fields (columns: columns) to the DB.

A

AS/400 physical files (PF) are migrated to SQL-based database tables, and AS/400 logical files (LF) are converted to database indexes. Each field is converted into a table column, and the column type is optimized according to the original data type. (This process varies from database server to database server.)
In addition, AS/400 data files can define attributes such as packed/zone/binary numeric format, decimal places, format, default values, and edit masks. Logical files can define SELECT/OMIT conditions. Much of this information does not correspond to standard SQL attributes. Therefore, Caravel? also generates XML files containing all original DDS source information (for PF/LF, DSPF, and PRTF).
Similarly, SQL-based databases migrated from mainframe databases (DB2, IMS DB, VSAM, etc.) are converted to database tables and indexes on those tables. Each field is converted into a table column, and the column type is optimized for the original data type. An XML file is generated as information to complement the destination SQL-based database with the attributes of the conversion source.
At runtime, the converted program will use this information to generate specific SQL statements or convert SQL data to the expected format. Therefore, if you modify a converted database table, you must do the following
　　1. Modify the database table structure by executing the corresponding ALTER TABLE instruction.
　　2. Add this change to the XML file representing the program's data file.
　　3. Modify the program to use the new fields (e.g., declare new field record variables and add processing).