The Caravel Technology

Transcription

1 The Caravel Technology

2 Caravel OS/400 is an automatic technology oriented to the modernization of systems developed in OS/400 environments for the migration and re-engineering toward.net or J2EE technologies. Caravel OS/400 allows the complete modernization of an Original System with all its components. Starting with an exhaustive analysis of the system that identifies its components, and suggesting, in a very precise manner, the necessary changes to be made in order to obtain a successful conversion. or RLA, thus keeping the original OS/400 system as a database server. The Caravel Technology completes the conversion in short periods of time, making the modernization of applications a highly automated and efficient task, particularly in those repetitive or mechanical processes. User s intervention becomes only necessary for validation or determination of re-engineering tasks and/or tools. The Modernization Process The Modernization Process performed by the Caravel Technology is structured in the following phases: I. Analysis Inventory Static Analysys Inventory Verification Architecture Analysis Pattern Analysis Database Analysis Dynamic Analysis II. Technological Re-engineering III. Conversion Modernization of Business Rules Objects Modernization of the Presentation Logic Modernization of Database Access Objects IV. Database Migration Analysis Validation Migration Image 1.Caravel OS/400 includes all the necessary elements for the modernization of a OS/400 system. Analysis and Re-engineering tasks The re-engineering of the Original Systems requires as a first step an exhaustive analysis. This analysis must be performed both in a static and dynamic manner. The static analysis are performed over the Original System s sources where the information is extracted. This information results somehow Afterward, the system is converted to a modern and highly automated technological platform. The modernization process allows for multiple steps of analysis, reengineering and conversion in order to obtain a resulting system that is well structured, easy to handle and fitted for a modern architecture and technological platform. During the modernization process, a database analysis is performed, verifying its consistency for its later automatic migration to a Relational Database with SQL such as Sql Server, Oracle, DB2 or Caravel Sql. As an alternate, the original database may be kept in the original platform with a PF and LF format that can be accessed through SNA Image 2. Analysis and Re-engineering activities during the modernization process. 2

3 limited because it does not guarantee that the performed analysis will correspond with the system s behavior during execution. Only a dynamic analysis provides the true information required for the re-engineering tasks. The analysis proposed by the Caravel technology includes an inventory and static analysis as well as an initial conversion of the Original System in order to obtain a first converted version. This version will be used to perform the dynamic analysis previously mentioned. The Analysis activities are divided in the following three phases. They can be performed as many times as necessary: Importation and Inventory of the elements to be analyzed. Static Analysis of the system. Dynamic Analysis of the system. Image 3. Caravel REPOSITORY: Center of the Caravel Technology. Static Analysis This analysis is performed over the sources and correlative elements inventory in the Caravel REPOSI- TORY. Inventory Analysis This analysis consists in the verification of the data imported from the Original System. Objects and sources are compared: Relationship between sources and objects. Missing Objects/Sources. Duplicated Objects/Sources. Verification of Object s type. Generation of audit reports. Importation and Inventory of elements to be analyzed The first activity to perform is the importation of the elements to be analyzed and an inventory of each one of their objects. With the information previously, a database in XML code is generated and may be exported to a relational database named Caravel REPOSI- TORY containing precise information about the imported elements. Caravel REPOSITORY Constitutes the center of the Caravel Modernization Technology. From this database information is extracted during the Modernization Process. As a first step all the information is stored in XML code, lately it can be exported to a Relational Database. Image 4 shows the relationship between the different elements that form part of the Caravel REPOSI- TORY. Image 4. Relationship between the components of the Caravel REPOSITORY. 3

4 Analysis of the System s Architecture From the sources that have been previously translated to XML and contained within the Caravel RE- POSITORY, new information is obtained and related to the following: Libraries with all their composing objects. Programs with all the information about definitions and instructions. Dates, screens and reports formats, with their registries, fields and attributes. After this analysis is completed, the Caravel REPOSITORY is updated with the enough information to perform the re-engineering tasks and later conversion. Analysis of Patterns With the information contained within the Caravel REPOSITORY, it is possible to find repeated patterns of the Original System. This analysis allows to individualize repetitive patterns and guide the manual processes of re-engineering. Database Analysis During this phase, the format of the contents of the database files is analyzed and verified. The objectives of this analysis are: Verify the contents of database files based on the specification of the data model described in the PF/LF. Analysis of data files Multiformat. Generation of models departing from the data. Image 6. Activities of Data analisys and re-engineering. Dynamic Analysis This analysis is performed over the Original System s sources after they have been converted into a preliminary version used for testing and analysis. It is also during this phase that we obtain detailed information about the original system. This level of detail is only obtained by performing the analysis of the Original System in real time, that is after a preliminary conversion that allows us to test the correct performance of the Original System. Image 5. Analysis and Re-engineering activities for the processes. Conversion Activity The modernization of an Original System includes its analysis, improvements and the conversion to a new platform (a new operating system and language). The Caravel technology greatly reduces the efforts involved to achieve this objective. The conversion process is structured in three sub-activities: Conversion of Business Rules. 4

5 Conversion of the Presentation Logic components. Conversion of the database access components. Automatic modernization of the components of Business Rules These components are automatically identified, separated and translated. In order to perform the conversion, we begin with the original source obtained after the analysis and reengineering processes. Automatic modernization of the components of Presentation Logic Components of this type are automatically identified, separated and converted to a JSP or ASP technology. The modernization is achieved taking into consideration stable transformation rules of programmable patterns. The automatic modernization of these components is achieved by converting the appearance of a 5250 interface into HTML (dynamic with ASP (.NET) or JSP (J2EE). Automatic Modernization of the Database Access Components The components of this type are automatically identified, separated and converted into SQL instructions specific to the relational database structure chosen for the destination platform. Image 7. Conversion activities during the modernization process. Database Migration The migration of the database requires an analysis that focuses into two complementary objectives: Search and definition of the Original System database structure. Verification of the contents and consistency of the Original System s database. Once the above mentioned analysis are performed, the database is migrated into the chosen RDBMS of the destination platform. Analysis: Search of the Original System s Database Structure Analysis of formats As a result of this process, we obtain all the models and descriptions of the database files to migrate. It will be used for the structure of the relational database chosen for the destination platform. Handling of files with multiple registry format In this case, Caravel defines in the model, some of the different structures of registry. In some cases, it also allows to define the generated table in the relational database of the destination platform. Analysis: Verification of the contents and consistency of the Original System s Database Database Models for database re-engineering Based on the database models of the Original System, Caravel allows to establish the rules for the database validation. These rules allow to define the range of values and their inherent statistic. Validation and Search of errors Once the model becomes available (with the file s structure) the Caravel technology performs the verification of data by starting with the file in the original format (EBCDIC). 5

6 The Caravel Technology Image 8. Example of a 5250 interface conversion into dynamic HTML. This process converts first characters EBCDIC to ANSII, and later verifies if the data to migrate is compatible with the structure defined in the resulting model of the analysis of formats process. Migration of Data As the final phase in the conversion process the database is migrated. This process involves the following actions: Creation of the database structure of the relational database chosen. Generation of the tables. Reading of the original EBCDIC files and conversion of data to ASCII. Implementation of the rules for error filtering. Data recording on the tables. Creation of necessary indexes. Verification of the complete migration of the data. Copyright BASE 100, S.A. All rights reserved. Information contained in this document is subject to changes without prior notice. These changes will be incorporated in new editions of the document. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in the United States, other countries or both. Every company name, product name, or service name may be trademarks or service marks of their respective owners. BASE 100, S.A. 6