Degenio MouliForms Migration Oracle forms 6-10g
Introduction Phases during forms conversion Options and Tools for conversion Mouliforms Presentation Conversion process with MouliForms Messages during conversion 2
Phases Phase 1 : Organization / tracking / framework Phase 2 : Putting in place the environnement / Evaluation of MouliForms and other options Phase 3 : Conversion Phase 4 : Tests 3
Conversion Tools Built-in in Forms conversion tool in batch mode Built-in in Forms compiler in batch mode JDAPI API programmation/batch mode Available commercial tools (pitss-imex imex and others $$$$$$$) 4
5 JDAPI API JAVA Update fonts, color attributes on the fly (visual attributes) Add new objects (example: report object) Flag deprecated built-ins Replace some of the depracted built-ins Replace Run_Product(REPORTS) par Run_Report_Object Attach new PLLs Detect usage of client functions such as text_io, ole2, forms_ole, dde, host(), ora_ffi, etc.
Changes 9i-10g Support for mouse navigation Support for web environment Support for object oriented concepts Update to PL/SQL Better GUI Better visual aspect for forms application 6
Conversion steps on Windows (developer machines) Source Source code code inventory inventory Conversion Conversion Deploy Deployto to Windows Windows (OC4J) (OC4J) Validate Validate deployment deployment 7
Preliminary steps Convert PLL to 9i-10g Convert Object Libraries Convert Menus Prepare Jar file with the application icons 8
Potential problems 6-10g Deprecated Built-ins ins replacements Updates to the PL/SQL code Integration with Reports (?) Visual attributes: Color and fonts Client-side functionnalities 9
MouliForms- some features Based on JDAPI Batch changes to: Color Fonts Adding new objets Adding new PLLs 10
Conversion options - MouliForms 11
MouliForms- some features (2) Can check for client side calls Search for objects and Strings Modules Compilation Execution of modules under OC4J Adaptation of WebUtil on-the-fly Object Hierarchies in a module Comparaison of modules (before( and after) JAVADOC style documentation 12
Mouliforms- the facts Can perform several iteration on the same module Interactive tool Use a working directory for batch processing Can be extended by adding new migration rules Has some other modules that can be used during forms development 13
Interface Toolbar with access to the most used functionnalities Field that shows the current work directory. A A directory selector that shows all the available local and network folders. A A panel that indicates the current modules being processed with MouliForms. Tab panel that shows the details of the process being carried out. 14
Interface (2) 15
Conversion steps Step 1 : Select work directory Step 2 : Connect to schema (if compiling) Step 3 : Start automatic conversion Step 4 : Compile modules Step 5 : Inspect form modules Step 6 : Output conversion report 16
Steps (1) Step 1 : Select work directory 17
Steps (2) Step 2 : Connect to schema (if compiling) 18
Steps (3) Step 3 : Start automatic conversion 19
Steps (4) Step 4 : Compile modules 20
Steps (5) Step 5 : Inspect form modules 21
Steps (6) Step 6 : Output conversion report 22
Messages in MouliForms Listing of modules during conversion with total of current changes made to each module 23
Messages in MouliForms (2) Message related to a deprecated forms trigger. A dialog is shown with the PL/SQL code. Code inspection is required before asking MouliForms to keep or delete the trigger. 24 the trigger.
Messages in MouliForms (3) Processing steps shown in the bottom tab. 25
Messages in MouliForms (4) Processing steps are shown for each module in this tab. All the specifics changes are shown here. 26
Messages in MouliForms (5) Processing steps on one module after you select it from the output table. Détails are shown in this tab. 27
Conclusion MouliForms can handle around 90% of the conversion needs from 6 to 10g Some bugs still there related to the UI and messages display. 28