SwisSQL - Oracle to Java Migration Tool helps you convert Oracle PL/SQL procedures to Java. With Oracle and other database vendors supporting Java based procedures to be run inside the database, it is worthwhile to move to a completely Java based environment. PL/SQL procedures are also not portable across databases as it is proprietary to Oracle. Also, with the advantages of the distributed multi-tier architecture, it is always good to have the flexibility of deploying the core business-logic of enterprise applications either in the middle-tier or the database-tier. PL/SQL does not offer such flexibility. Hence, translating the existing PL/SQL procedures to Java offers the developers code maintainability, portability, flexibility of deployment and numerous other benefits. It is also easier to find Java programmers than PL/SQL programmers thus keeping the cost of building and maintaining enterprise applications under control.

SwisSQL Oracle to Java Migration Tool Features:

1. Migrates PL/SQL stored procedures to Java.
2. Enables applications to be portable across databases.
3. Facilitates moving client-server applications to web architecture.
4. Facilitates deployment of business-logic both in the middle-tier and database-tier.
5. 100% java based implementation supports Windows, Solaris, Linux and other OSs with Java virtual machine.
6. Support for conversion of both PL/SQL Named blocks like Stored Procedures, Functions, Triggers, Packages etc. as well as Anonymous blocks to Java.
7. Support for conversion of all conditional Statements including IF - THEN - ELSE , IF - THEN - ELSIF Syntax etc.
8. Support for conversion of all control Statements including FOR loops, WHILE loops, Simple loops with EXIT or EXIT-WHEN, RETURN etc.
9. Support for both Implicit and Explicit CURSOR constructs and Cursor attributes facilitating data retrieval.
10. Support for procedure or function defined in declaration section of PL/SQL block (Local Modules) is provided.
11. Support for PL/SQL User Defined Data Types and Structures like PL/SQL Tables, Records, REF Cursor, Collections etc.
12. Collection Built-Ins methods like DELETE, NEXT, PRIOR etc. are supported.
13. INDEX BY VARCHAR2, PLS_INTEGER, POSITIVE, NUMBER etc in Associative Array is supported.
14. Supports FOR ALL Statement including RETURNING Clause in BULK COLLECT.
15. Support for almost all Native Datatypes in PL/SQL.
16. Supports converting PL/SQL Exceptions to Java SQL Exceptions.
17. Transaction features like 'COMMIT', 'ROLLBACK', 'SAVEPOINT' etc. are supported.
18. DBMS_SQL and DBMS_OUTPUT built-in Packages are supported.
19. Most PL/SQL functions are implemented in Java.
20. Package Elements access from other Procedures and Functions are supported.
21. Support for conversion of EXECUTE IMMEDIATE (Native Dynamic SQL) statements with both "INTO" and "USING" constructs.
22. Support for conversion of OPEN FOR (Native Dynamic SQL) statements with "USING" construct.
23. Support for VARRAY Collection.
24. Support for FETCH BULK COLLECT INTO Collections.
25. Support for HTP and HTF WebToolkit Packages.
26. OWA Packages such as OWA_UTIL, OWA_TEXT, OWA_PATTERN are supported.
27. Bulk SQL Statements are supported.
28. Support for PRAGMA is provided.
29. SQL 'FOR UPDATE' clause in 'SELECT' statement and 'CURRENT OF' clause in 'UPDATE' statement are supported.
30. 'BETWEEN' and 'LIKE' expressions are supported inside conditional statements.
31. Support for String, RAW and LONG RAW datatypes provided.
32. MOD operator and MOD function are supported.
33. JavaCC based PL/SQL parser implementation ensures easy enhancement of functionality.
34. Support for parsing and converting multiple Stored Procedures / Functions within a single PL/SQL file.
35. Oracle SQL queries are converted to equivalent Target Database SQL Queries (SQL Server, DB2, MySQL, AnsiSQL, PostgreSQL, Informix, TimesTen) and used within Java code.
36. Support for Nested Table in Collections.
37. Support for Case Statements.
38. Support for CursorReturn Clause.
39. NullValue Assignments is supported for Boolean operators.
40. Support for RETURNING..INTO Clause in DML Statements.
41. Option provided for users to configure Java datatype for each Oracle datatype.
42. Support for UTL packages like UTL_FILE, UTL_TCP, UTL_SMTP, DBMS_JOB have been provided.
43. Support for converting OUT arguments in PL/SQL procedures and functions.
44. Support for nested function calls and function definitions.
45. Migration progress & Migration summary views have been added to the Graphical User Interface.
46. Sophisticated reporting mechanism which enables user to view migration reports in a user friendly HTML format.
47. Provides an Intuitive and Easy to use GUI with the following features:
    1. One click conversion of PL/SQLs to Java.
       
    2. Provides a tree view of loaded PL/SQL files and converted Java files.
    3. Options to load PL/SQL files from local directory or import them from Oracle database for Java conversion.
    4. Project driven organization to ease maintenance.
    5. Generates formatted Java code with comments.
    6. Comprehensive migration reports with detailed information such as total number of files loaded, total number of files converted, total number of files not converted, destination directory of converted files.
    7. Provides a unified view with loaded PL/SQL file, converted Java file, log report and error reports.
    8. Provision to compile the converted Java code.

SwisSQL - Oracle to Java Migration Tool takes PL/SQL Packages, Procedures, Functions and Triggers as input and converts them into standard JDBC based Java code. PL2JSQL implements most PL/SQL functions as JAVA API. The converted Java code can be run standalone or in J2EE container with EJB wrappers for the converted Business-Logic code.

Features and Benefits

• Converted Java code is easily maintainable and portable.
• Standards based, no proprietary APIs.
• Converted Java code can be deployed in the middle-tier or the database-tier.
• Supports almost all PL/SQL constructs.
• Supports PL/SQL Packages, Procedures and Functions.
• Outstanding support directly from developers.