If you have any comments or questions, send us an .
Caravel converts 100% of the source code. The conversion process also includes the control language (CLs and OCLs), Operating System functionality (WRKSBMJOB, WRKSPLF, etc.), data access and user interface. BASE100 delivers a 100% pure Java application that runs with exactly the same functionality as the original one. The converted system can be deployed on the same AS/400 or optionally on different platforms, (HW, OS and RDBMS), with a modern and versatile user interface.
RPG/COBOL on OS/400
Caravel implements all cycle programs functionality by means of classes and methods in Java that allow keeping their behavior in a very effective way.
Caravel translates each RPG/COBOL instruction into a method that keeps the same functionality of the original. The translation is done instruction by instruction, not in groups.
The aim of the conversion is to produce a system easily readable by the original technical team.
On the other side, the Java programmers found a 100% pure Java system, and they can work on in it as an ordinary Java system. The functionality of the converted system can also be invoked via a Rest services mechanism.
The converted programs are 100% pure Java code, so can be used on every standard environment available. Our customers have successfully worked with WebSphere, Eclipse, Net Beans, IntelliJ, JBuilder, among others.
A huge number of commands that are used in legacy AS/400 systems are implemented: CPYF, CRTPFM, ADDLIBLE, MONMSG, OVRDBF, OVRPRT, OVRDSPF, etc.
Caravel is a conversion service that guarantees 100% of the original functionality; therefore, all commands needed to achieve this goal are implemented.
In the exceptional cases that any functionality nonexistent in Caravel is required, BASE100 will proceed to develop and include it in the framework.
It is possible to keep the AS/400 as both, data server and application server. Under Client-Server architecture, we can maintain the AS/400 as the database server, while the converted system runs on an open platform. Same under i5/OS, Linux or AIX, the AS/400, the application server can be deployed on it.
The conversion doesn’t require an expansion of the existing hardware. The performance varies depending on the hardware configuration and the communications infrastructure, as well on the characteristics of each system.
The change in the hardware would be necessary only in case of evolution from a one-layer architecture into a two-layer (Client-Server).
(*) AS/400 means also: S/36, S/38, iSeries, System i.
It is well know that AS/400 is a very reliable and extremely high performance platform. Every component of AS/400 has been designed to work together, focusing reliability and performance over standardization or compatibility. So to maintain same performance level in the new converted system, it is necessary an intensive use of technology and know-how.
For over 10 years, the BASE100 technical team has analyzed the characteristics of many applications from the reliability and performance point of view. Modern open systems offer levels of reliability alike to the legacy systems, but performance is always an issue that must be considered.
The fast evolution of open systems has increased performance, especially when considered related to costs. This fact and the sharp evolution of Caravel technology have eliminated the prior performance gap we found several years ago. Now, in many cases, the converted systems are faster than the original one, just after an automatic modernization process and configuration tuning. Minor reengineering interventions can also be introduced at any time to improve performance. Only in few cases mayor reengineering or platform modifications are required.
When necessary, Caravel technology has developed many strategies to greatly improve performance.
(For more information please refer to the document: Performance analysis in modernization projects.)
The data areas are implemented converting them to SQL structures in a relational database.
Caravel implements a number of Java-compatible extensions for the Printer Files (PRTF) providing most of the functionalities of the AFP/400 module, such as: Image Printing, text, templates, bar codes, etc.
(For more information please refer to the documents related to Caravel OS/400 Framework.)
Caravel includes mechanisms that generate the same functionality to print bar codes. A table of correspondence is defined between the original codes (APW) and their equivalent fonts to obtain exactly the same barcode.
The largest batch application migrated with Caravel was a 25.000 employees payroll. The new migrated process required a short time to print all paper documents (lists, receipts, checks, duplicates, etc.). The database on which these processes are executed has a volume of approximately 24 GB.
In any cases the migrated applications run in the same time window or faster than the original AS/400 ones.
Additionally, the new system includes all the facilities to use electronic documents in very different formats.
Caravel has no dependence of any specific application server. Currently, all translated applications are compatible with the latest versions of most common application servers, for example:
Caravel supports JVM up to version Java 8 update 121.
Caravel implements the following specifications: Servlet 2.3 and JSP 1.1, 1.2 and 2.0.
Caravel converts to Java following the guidelines of the standard J2EE architecture. Therefore, you may deploy the converted system on any application server compliant with this standard.
In order to use the applications in Java with a Swing interface you need a client PC with a Java Virtual Machine (JVM). The application must be accessible from the client PC . Data may reside on this server, on the OS/400 or on any other server.
It is necessary a server with access to the Internet/Intranet containing a Java Application Server. The server may be WebSphere or any other server that fulfills J2EE standard. The workstations will need a browser (Firefox, Chrome and Internet Explorer, are supported).
Yes, a Caravel converted application separates User Interface components from application behavior. It also separates the application data access to the final data storage. As a result of this:
The integration is very simple due to the conversion process that includes an application structure with an architecture fully adapted towards its integration with an application server.
BASE100 has the experience after many projects using this application server.
Caravel migrates towards the most commonly used RDBMs on the market. Some examples are: DB400, DB2, Oracle, Postgress, MultiBase, SQL Server… In all cases a JDBC driver is required.
The security aspects are is not part of a migration. Once the application has been migrated to the new environment, is necessary to execute a Security Management Application for that platform (Operating system, Data base management system, etc.).
The classes used by BASE100 are 100% pure Java, clearly structured, and do not require any different knowledge that Java. Such classes are easily legible by an RPG or a COBOL experienced programmer.
In every conversion project is included a training section oriented to both RPG/COBOL and Java technicians.
To personalize a Swing interface can be used any standard Java platform such as WebSphere, Eclipse, JBuilder, Forte, etc.
To personalize an HTML interface, it is possible to use any HTML editor available on the market.
The personalization of the interface works as follows: When translating an application, you can choose between having the user interface automatically generated or personalizing single screens according to the preferences of the customer.
In the first case, the way the screens will look is based on certain transformation rules that Caravel provides and that allow to generate the equivalent HTML code for each field of the screen. The result will be an HTML code that generates the same fields, sizes and positions as the original. The color attributes, sources, background color, etc. that doesn’t affect the functionality can be personalized, being applied automatically to all the generated screens.
In the second case, the customer can create a JSP template for each screen that he wishes to personalize. This template can have any aspect and does not have to be similar to the original. With the purpose of making the preparation of the screens easier, Caravel provides the standard JSP mechanisms and uses the “JSP TagLibs”, which easily help with the use of the information from the application: records, subfiles, fields, attributes.
These two solutions are not incompatible; it is possible to personalize only some screens of the application. This process can be progressive or according to the customer's needs. The application will search for the personalized screen first and then, if it cannot find it, dynamically will create a screen in accordance with the parameters of the selected user interface.
The personalization process can be carried out completely by the customer or could be part of the project. In this last case, the customer can define the rules, standards and styles that he would desire. Since the aspect of the application is defined by a group of JSP templates, the customer can change any graphical element at any time.
In the Caravel Standard Questionnaire are reflected all the variables that can determine the complexity of a conversion project. Before start the project, BASE 100 will evaluate the complexity and therefore, the resources, time and costs of each project.
This estimation is based in a big number of migration projects already completed successfully. These projects cover a great diversity of sizes, architectures and specific legacy technologies.
Yes, by default, your migrated applications will look like batch applications to the iSeries, using ZERO interactive resources.
If the original application is multi-language, Caravel will migrate it with same functionalities. If the original is not multi-language, during the translation process, Caravel can be configured to extract the literals inherent to language and exports those to an external file. By editing and translating that file, you easily convert your application to a multi-language one.
Yes, a complete and detailed analysis report is generated in the first conversion phase. Caravel includes a specific tool Caravel Insight which does a complete inventory of all the legacy system components and analyses completeness, relationships, dependences, errors, etc.
The Caravel Insight report is a key piece in the conversion process.
Firefox, Chrome, Internet Explorer.
The converted Java application has no limitations concerning future programming or connectivity. We have vast experience in this field. Typically it is necessary to connect the new Java applications with previous developments made by that customer. Usually every conversion project includes a part of integration with other existing or future systems.
Caravel is not merely a screen transformation or a middleware. Our service is a project to go to Java at once. The features of WebFacing or HATS cannot be compared at all with a complete conversion to Java and to open platform. Our service migrates the whole application to Java, then analyses it, structures it into components and improves the application with our technical reengineering technology. Our approach is much wider than an interface make-up with some Internet connectivity provided by the mentioned products. Must be underlined, that the duration time can be similar or ever reduced with Caravel.
BASE100 requires a system that works correctly in the legacy platform. It is necessary to have all the objects to be converted (RPG and COBOL programs, CL, PF, LF with both compiled and source code), and a set of data and a functionality description of the original application to be tested.
BASE100 provides software tools (Caravel Test Maker) to help the customer in this functionality description process.
BASE100 delivers the Java application ready to be run on the new platform and environment, with exactly the same functionality as the original system, that includes:
Yes, it is possible to migrate only a part of the system, this case is considered in the Caravel technology. The original programs developed in RPG/COBOL no converted, can coexist with programs in Java.
They can share data and platform. In these cases data normally remains in the AS400 as PF/LF data files that are access by both, the original RPG/COBOL programs at the new converted to Java programs.
As a general rule, an AS400 physical file is migrated to SQL database table and a logical File is converted to a Database Index. Each field is converted to a table column and the column type will be the most appropriated according to the original data type (this process can vary depending on the specific database Server).
Additionally, an AS400 data file can define other attributes like (packed/zoned/binary numeric format, decimals positions, format, default value, editing masks, etc). Logical files can define for example SELECT/OMIT conditions. Most of this information has no correspondence to standard SQL attributes. For that reason, Caravel generates also a XML file containing all the original DDS source information (for PFs/LFs, DSPFs and PRTFs).
At runtime the converted program uses this information to generate the specific SQL statement or is used to convert the SQL data into the expected format.
For that reason if we change a converted database table, we have to do the following tasks:
Caravel is commercialized on a service base, therefore is not commercialized as a tool.
In case of a test is desired, the advisable way is to do a Proof of Concept with a part of your system. In the document Migration proposal and free PoC, there is all the information about how to prepare a sample of the system. The general lines for a PoC are:
It is advisable to choose those parts of the system that the customer estimates as more critical.
Caravel is a migration service, with the commitment to deliver the Java application with exactly the same functionality.
Consequently our business model does not include selling our translation tools to a third party. Several other tools included in the Caravel technology family such Caravel Insight can be purchased as a tool.
After the conversion process it is not necessary the use of any tool. The migrated programs are 100% Java. Our migration service provides total independence to our customers. Our business model does not include payments after the conversion itself.
We provide detailed information in our commercial proposals about the cost of every item.
Optionally is possible to subscribe maintenance updates and maintenance services for the Caravel Framework. Both are included in the conversion fees, during the first year after the conversion project.
Our pricing policy depends on the project size and complexity. We can give a precise estimate after the evaluation questionnaire has been completed and sent back to us.
In case your company does not know the exact volumes, we can provide an estimate based on a representative model.
Our pricing policy allows for ROI in a maximum of 12 months. The cost advantage of Caravel translates into 1/7 of the cost and 1/5 of the time needed for a re-programming process.
In an object-oriented language; a class is a program that implements the functionality relative to a specific type of object. Such functionality consists of methods and properties.
A method in an object-oriented language is a type of functionality of an object class.
J2EE (Java 2 Platform Enterprise Edition) defines the standard for developing component-based multitier enterprise applications. There are tools that create a perfect setting for the development and deployment of scalable applications for the Web. These tools have the following features:
Yes it is, the converted system adheres 100% to the standards of Java applications.
The converted application by means of Caravel tools has separated the logic from the interface structure.
So it is possible to personalize the interfaces without affect the converted program. It is consequently possible to include graphic standard components like: Buttons, Radio Buttons, Pull Downs, etc.
The converted program, manages the interchange of data with the user by means of a JSP. This JSP is in charge of representing the information to the user.
Personalization of screens can be made by groups or one by one. Using a shared JSP which will be used by a group of screens or using an individualized JSP for every screen.
During the conversion a CSS is generated by default for every JSP. It can be also modified any time.
There is not any restriction in the personalization of screens. The only limitations come from the way programs use the screen data.
As an example: a converted program may take in consideration cursor position or the function key that has been already pressed, so the personalization must take account of this behavior and respect it.
In Caravel conversion there is a default implementation to manage these situations.Additionally it is necessary to consider the navigation logic from screen to screen. According this behavior, the personalization of the screen can be more or less flexible.
As mentioned in point 1, there are different levels of personalization of screens. From low impact personaliza-tion (as example, only modify the CSS) to high impact ones that could require some modifications in the logic.
We include some images to illustrate these differences.
It is always possible to unify several screens in one single screen and modify the size of the screen. In both cases the logic of the application must be revised to assure the functionality keeps unchanged.
Yes. CCS can be used in a 100% standard way. Every JSP or HTML can include the desired CSS.
In the standard implementation of Caravel screens are included CSS by default.